Related
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, thermonuclear war,
* or you getting fired because the alarm app failed.
* 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.
*/
I've made a very fast rom, without a lot of stupid apk and with ext4 system for modifing /system.
You must say thanks to other people, I'm only a stupid "aggregator"....
But thanks also to @Cameo164, after his experience i've made a more little system.img, changing the partions size.
- Download my rom, unzip
http://www.mediafire.com/file/ke5h46vy86o23tl/DF0.1.zip
- Reboot into fastboot
- Install this Recovery (you'll find also here: http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 )
fastboot flash recovery path/to/twrp-3.0.0.img
- Reboot into recovery and Make a backup of your Rom/data/system with this recovery!!!! It's very important!
- Wipe cache and data via recovery, reboot into bootloader
- Install my boot.img
fastboot flash boot boot.img
- Go to this thred ( http://forum.xda-developers.com/g-watch-r/development/getting-ext4-instead-squashfs-6-0-1-t3341166 ) and follow the steps 4-15 and then come back here
- Then:
fastboot flash system systemimageresized.img
- Reboot recovery and install supersu: Wear-SuperSU-v2.67.zip (you'll find in my zip)
- Restart system and wait..........
- Don't care for the google play error on your smartwatch, if you have
- Enable adb debug under dev options on your watch, you can also enable before paring, pushing the hardware button for about 2 seconds
- Pair with your phone
- Install busybox (you'll find in my zip)
adb install busybox.apk
- Install advanced settings for wear http://forum.xda-developers.com/android/apps-games/advanced-settings-t3341722
adb install com.sssemil.advancedsettings.apk
It's very usefull for change the screensaver brightness and other things
- Install Kernel Auditor http://forum.xda-developers.com/android-wear/development/app-kernel-audiutor-4-wear-t3126122
adb install KernelAudiutor4Wear.apk
For enable/disable cores and other things
- on your smartwatch if you have issue, reboot and clear data to google.play. framework (with advanced settings), reboot again
This rom is without a lot of things (like lg wathfaces, tutorial.apk and other things that i don't remeber, i'm sorry).
I use other watchfaces (with facer, this is mine: https://www.facer.io/watchface/hLzCJbTR3Z?draft=true )
Don't ask for add apks, or other things, thank you!
I suggest disable with advanced settings under apps also Bug report sender com.google...wearable.bugreportsender
Remember:
Don't change kernel or rom because you'll corrupt the new ext4 partition and you'll lose your data.
In any case before make a backup,
So, when you'll change rom/kernel you must install again the right kernel and the right rom.
If you have adb error ($ADB_VENDOR_KEYS is not set; try 'adb kill-server'), from recovery:
On your pc search adbkey.pub
cd user/.android
adb push adbkey.pub /data/misc/adb/adb_keys
You must say thanks to:
For stock Image thanks to @intersectRaven and also @vt0r http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
For This great Kernel thanks to @dirtyhank http://forum.xda-developers.com/g-watch-r/development/kernel-frankenlenok-t3342054 (look at the last page)
windroid toolkit http://forum.xda-developers.com/showthread.php?t=2499926
@Chainfire
@suleymanovemil8
@Xmaster24
@Grarak
@dirtyhank
@Cameo164
Changelog
I've uploaded my things.
Hi, thanks for your work, but for me restoring your system in twrp fails. It show's me an "ERROR: 255" close to the end. I re-downloaded the backup files, so that I can be sure that the files aren't damaged, but still no luck. I'm using the twrp.img you provided and did it like you described.
And btw. When I'm right, it should be called "adb push" not "adb pull".
http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Did you mount system in recovery?
Or try installing before leedroid rom.
Yes... is push! I'm sorry!
dettofatto said:
http://forum.xda-developers.com/showthread.php?t=2236620&page=48
Did you format your system, cache and data?
Or try installing before leedroid rom.
Click to expand...
Click to collapse
Yes I did. But it's not important if I did it, because TWRP does it before restoring anyways.
What difference would it make if install leedroid rom before restoring, when TWRP formats /system before restoring your backup ?
If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.
dettofatto said:
If you read the link that I've posted you'll see that the issue is in some files on your phone (probably).
Leedroid use ext4, mm only f2fs (I don't remember name exactly) on system. So, probably, if you install leedroid rom, you'll format your system partition to ext4.
Click to expand...
Click to collapse
To have ext4 I don't need to install a non-mm rom like leedroid's. I can just format /system to ext4 in TWRP.
Yes I have read it. The file that causes problems is "/system/usr/icu/icudt55l.dat". I removed it from the backup file and pushed the new file to the watch. And now the restoring works. But I ended up with a bootloop (tried with SuperSu flashed & without SuperSu). I don't know if it's because I removed the file or if it has any other reason.
Thanks for trying to help me.
Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...
dettofatto said:
Did you wait about 5 mins? Because the first time is very long!
Try also with several reboot!
Which boot animation you see?
After I'll see that file!!
But I don't understand... in your log which error is it?
Did you correct permission? In any case you can't remove I file from backup and restore.
Because if you format system and data you don't have any files, restoring stops for an error rewriting your files?
I've restored full m1d63x stock and then I've checked my backup and steps and I didn't find any stop...
Click to expand...
Click to collapse
Yeah I waited 30 minutes, rebooted, waited another 30 minutes and again, again...
The bootanimation I see on watch is in the attachments but because the watch screen is too small there's only "ndroi" instead of "android" visible. And there's that darker font shadow, like a fade-out animation which is going through continuously.
I know that I can't just delete one file, but with that file I can't even restore the backup.
Then I get this error :
Code:
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/")
item name: '/usr/icu/'
dir
==> extracting: /system//usr/icu/ (mode 40755, directory)
==> setting perms: /system//usr/icu/ (mode 40755, uid 0, gid 0)
Restoring SELinux context u:object_r:system_file:s0 to file /system//usr/icu/
tar_extract_all(): calling th_get_pathname()
tar_extract_all(): calling tar_extract_file(t, "/system//usr/icu/icudt55l.dat")
item name: '/usr/icu/icudt55l.dat'
reg
==> tar_extract_regfile(t=0xb56a9300, realname="/system//usr/icu/icudt55l.dat")
==> extracting: /system//usr/icu/icudt55l.dat (file size 23068784 bytes)
FAILED RESTORE OF FILE i: /system//usr/icu/icudt55l.dat
I:Unable to extract tar archive '/data/media/0/TWRP/BACKUPS/411KPFX0122123/DF/system.ext4.win'
Fehler während der Wiederherstellung. *should be "Error during restore process" in english
Prozess extractTarFork() endete mit FEHLER: 255 *should be "Prozess extractTarFork() ends with ERROR:255" in english
I:Failed to reset capabilities of /system/bin/run-as binary.
Can you send me the file icudt55l.dat from your running watch and then I can try replacing the file in the backup?
I'll send you icudt55l.da after, when I come back at home. But is very strange...
Anyone has this issue?
icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat
dettofatto said:
icudt55l.dat rw-r-r-
http://www.mediafire.com/file/kjge1s3ox561s5g/icudt55l.dat
Click to expand...
Click to collapse
I tried everything I'm able to do : First pasting your new icudt55l.dat file into the backup, just gives me the same error as before. Then I tried restoring the backup without the icudt55l.dat file and push the file with adb push to /system/usr/icu, just gives me a "no space left on device error" and at last I tried to extract the system.ext4.win file on the watch with adb shell instead of twrp, this gives me a "no space left on device" error too, but it seams that I does it anyways. But still stuck on bootanimation. I just can't get this rom to work on my watch :|
After I'll try tu upload another backup...
Ok i've created a system.img_sparsechunk1 flashable via fastboot
Backup everything.
Then download: http://www.mediafire.com/file/d3yo1opb4i7j7at/system.img_sparsechunk1
Reboot into bootloader and:
fastboot erase system
fastboot erase data
fastboot erase cache
fastboot flash system system.img_sparsechunk1
Flash also (I don't know if is necessary for you, but you must use mine boot.img) boot.img http://www.mediafire.com/file/w11byay60nwy5xb/boot.img
fastboot flash boot boot.img
Reboot into recovery and
Wipe data, davlink and cache
Reboot
How I've obtained this system.img_sparsechunk1?
I've extracted my system.img with: dd if=/dev/block/mmcblk0p19 of=/sdcard/system.img
but when i reflashed via fastboot I had an error because was bigger than system partition.
So i've compressed with SparseConverter v1.0.1 http://forum.xda-developers.com/showthread.php?t=2749797
to correct size: sparseconverter /compress system.img .\ 2684354560
and I've obtained the righht system.img
I hope...
In any case i've reflashed on mine and is ok
Thanks a lot for your hard work but my watch still refuses to flash the system -.-
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.288s]
sending sparse 'system' 1/2 (252175 KB)...
OKAY [ 8.280s]
writing 'system' 1/2...
FAILED (remote: size too large)
finished. total time: 8.651s
I have tried it with the latest fastboot version for windows and linux too, but both fail on "size too large". I have even downloaded SparseConverter myself, decompressed the "system.img_sparsechunk1" to "system.img" and then compressed it back into two 100MB and one 61MB sparsechunk files. Still fastboot gives me the "size too large" error.
I can flash the stock "M1D63X_system.img" successfully and it boots too.
I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe
dettofatto said:
I have this
Code:
D:\Hack\Android\LG\extracted>fastboot flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.375s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.551s]
writing 'system'...
OKAY [ 81.913s]
sending sparse 'system' (15336 KB)...
OKAY [ 0.632s]
writing 'system'...
OKAY [ 31.335s]
finished. total time: 122.806s
try with this fastboot http://www.mediafire.com/file/rbz0qqlbb0hty9r/fastboot.exe
Click to expand...
Click to collapse
I tried your fastboot version, but it happens the same :
Code:
fastboot.exe flash system system.img_sparsechunk1
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.300s]
sending sparse 'system' (252175 KB)...
OKAY [ 8.332s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 8.711s
Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)
dettofatto said:
Ok... I don't have any idea for this.
I'm uploading another backup, and another system.img extracted (this is more big, because is uncompressed)
Click to expand...
Click to collapse
I don't have any ideas too, I would be very good if anyone else could try your rom and tell if installing and booting works. Then we would know if it's my watch's or my' fault or the rom's fault.
System uncompressed extracted: http://www.mediafire.com/file/g481ae7m3ayrjmb/systemuncompressed.zip
New Backup from System:
http://www.mediafire.com/file/4jc5a31xe2insc6/TWRP.7z
May be is my rom
@VigneshS007
test system-arm64-ab.img
boot to custom-recovery
wipe cache (formatting cache .. down)
wipe data/factory reset / confirm yes / confirm yes - format 0..100%
vol-up and power and usb-wire in phone and pc : boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 1.547s
usb-wire out phone / return in phone
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 14.497s]
writing 'system'...
OKAY [ 3.356s]
sending sparse 'system' (421628 KB)...
OKAY [ 13.025s]
writing 'system'...
OKAY [ 2.928s]
sending sparse 'system' (388444 KB)...
OKAY [ 11.666s]
writing 'system'...
OKAY [ 2.704s]
finished. total time: 48.177s
now is in phone custom-recovery, data fresh formated, system-arm64-ab.img
usb-wire is in phone
fastboot reboot
phone boot... / black screen / <- 3x / Huawei eRecovery "Factory data reset(recommended)" yes(do it)
low-level format 0..5% / reset failed! / reboot system now
phone boot 2x and go to Huawei eRecovery (this flash dont work / shutdown)
vol-down press and hold, usb-wire put in phone, phone boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 14.281s]
writing 'system'...
OKAY [ 3.511s]
sending sparse 'system' (421628 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 21.386s
usb-wire out phone
usb-wire in phone
fastboot devices (phone is online!)
fastboot flash system system-arm64-ab.img
target reported max download size of 471859200 bytes
sending sparse 'system' (460796 KB)...
OKAY [ 14.359s]
writing 'system'...
OKAY [ 3.235s]
sending sparse 'system' (421628 KB)...
OKAY [ 12.947s]
writing 'system'...
OKAY [ 2.931s]
sending sparse 'system' (388444 KB)...
OKAY [ 11.664s]
writing 'system'...
OKAY [ 2.710s]
finished. total time: 47.846s
fastboot reboot and fast usb-wire out phone
You device is booting now... /black screen <- 2x /Huawei eRecovery /THIS way not work!!!
vol-down press and hold, usb-wire put in phone, phone boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' (458906 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 14.487s
usb-wire out phone
vol-up press and hold and power /boot to eRecovery/ factory reset
phone off
vol-down press and hold, usb-wire put in phone, phone boot to bootloader
fastboot devices (phone is online!)
fastboot flash system system.img
phone off
power
phone boot to factoryOS !!! this is the best: my phone work, no bootloop or other error
i think, the problem is "i am" or the instructions or "what else"
i think, if i do factory-reset the phone low-level format "data" and set inside instructions "test by next boot what system.img is installed" or other test
this test i now 5x do and the way is by all the same.
anyone info i missing to get out of this loop
i hope very powerful: anyone developer write twrp and system(LOS or RR) for this phone !
at the moment i could nail it to the wall / i am very frustrated / a little bit
excuse me for long writing text, i hope the mistake is easier to find
Flash this https://forum.xda-developers.com/pr...opment/resurrection-remix-phh-treble-t3767688 ARM 64 A only device @JamesBott
now, lets go, next test :good:
download run... finish
test system-arm64-aonly.img
fastboot devices (phone is online!)
fastboot flash system system-arm64-aonly.img
fastboot reboot
the rest is "the same procedure as test bevor"
this phone (my H9L) not boot in other system.img
by now in nothing else
the problem must inside my phone
or other question : have anyone other system.img in H9L and this work ? H9L with LLD-L31 ? not from india or ..., from EU (European Union)
what is different in my phone than other users ? i don't know it
now is custemOS inside again. different to last rom-install: SU is now outside! only different what i see
For everyone who is interested: I have build my first treble build based on pure AOSP 8.0... As my 6X didn't received EMUI 8.0 already I would be glad if some Honor 9 Lite or P Smart user could try to install and run my build on his device as it is based on P Smart blobs: Install it like a normal treble build. Extract the zip (it isnt flashable zip !), unlock BL, flash system.img via fastboot - boot to stock recovery and perform a factory reset - reboot... if booted up report back and provide some screenshots! Here is DL: https://www.androidfilehost.com/?fid=962187416754471220
JamesBott said:
now, lets go, next test :good:
download run... finish
test system-arm64-aonly.img
fastboot devices (phone is online!)
fastboot flash system system-arm64-aonly.img
fastboot reboot
the rest is "the same procedure as test bevor"
this phone (my H9L) not boot in other system.img
by now in nothing else
the problem must inside my phone
or other question : have anyone other system.img in H9L and this work ? H9L with LLD-L31 ? not from india or ..., from EU (European Union)
what is different in my phone than other users ? i don't know it
now is custemOS inside again. different to last rom-install: SU is now outside! only different what i see
Click to expand...
Click to collapse
Firstly... Honor 9 lite dont have a/b partition so you have to take the a-Partition images...
Secondly... V9 of the treble image would work (its on android 8.0)...
Hi @felix-development,
that what i reed - sounds very interesting. my next test is your download.
question : have you "twrp full function" ?
i mean twrp backup/restore "system, data..." ?
my twrp do backup/restore system "yes" data "no" (de- en-cryption ?)
JamesBott said:
Hi @felix-development,
that what i reed - sounds very interesting. my next test is your download.
question : have you "twrp full function" ?
i mean twrp backup/restore "system, data..." ?
my twrp do backup/restore system "yes" data "no" (de- en-cryption ?)
Click to expand...
Click to collapse
you should be on normal emui 8 with just bl unlocked... flash system.img via fastboot - and after that do a factory reset in erecovery (if didn't do by unlocking bl already)
Gesendet von meinem BLN-L21 mit Tapatalk
---------- Post added at 09:35 AM ---------- Previous post was at 09:33 AM ----------
JamesBott said:
Hi @felix-development,
that what i reed - sounds very interesting. my next test is your download.
question : have you "twrp full function" ?
i mean twrp backup/restore "system, data..." ?
my twrp do backup/restore system "yes" data "no" (de- en-cryption ?)
Click to expand...
Click to collapse
by the way you are free to pm me as i saw we speak the same lanuage
Gesendet von meinem BLN-L21 mit Tapatalk
Hi @felix-development,
ALL Test's ending in eRecovery, "Download latest version and recovery / Reboot / Shutdown"
That's no problem, i flash stock and all good! Phone work with stock It's only work.
Procedure:
flash other system; reboot; (phone boot / black screen) 3x / eRecovery "reset data" .... low-level-format 0..100% / reboot / (phone boot / black screen) 3x / eRecovery, "Download latest...
i think, the problem sit on the frontside from phone
any idea, what i doing false ?
or is in this moment fact: no other rom work on H9L ?
last step: flash system system.img (stock) phone boot "normal" and work !
My daily driver is my old elephon p8 mini.
Honor 9 Lite sleep and wait for next test
JamesBott said:
Hi @felix-development,
ALL Test's ending in eRecovery, "Download latest version and recovery / Reboot / Shutdown"
That's no problem, i flash stock and all good! Phone work with stock It's only work.
Procedure:
flash other system; reboot; (phone boot / black screen) 3x / eRecovery "reset data" .... low-level-format 0..100% / reboot / (phone boot / black screen) 3x / eRecovery, "Download latest...
i think, the problem sit on the frontside from phone
any idea, what i doing false ?
or is in this moment fact: no other rom work on H9L ?
last step: flash system system.img (stock) phone boot "normal" and work !
My daily driver is my old elephon p8 mini.
Honor 9 Lite sleep and wait for next test
Click to expand...
Click to collapse
A logcat could help to fix or to see wheres the problem...
@Darkest-Dark
logcat is a good word: how & who i find on end test (stand in eRecovery) the logcat ?
or if i reflash stock: if logcat from last test available ( how & who) ?
i can all do what hav to do with system and recovery. that's no risk. reflash system and/or recovery and stock work!
@Darkest-Dark
logcat is a good word: how & who i find on end test (stand in eRecovery) the logcat ?
or if i reflash stock: if logcat from last test available ( how & who) ?
i can all do what hav to do with system and recovery. that's no risk. reflash system and/or recovery and stock work!
JamesBott said:
@Darkest-Dark
logcat is a good word: how & who i find on end test (stand in eRecovery) the logcat ?
or if i reflash stock: if logcat from last test available ( how & who) ?
i can all do what hav to do with system and recovery. that's no risk. reflash system and/or recovery and stock work!
Click to expand...
Click to collapse
Look here...
https://forum.xda-developers.com/showthread.php?t=2303834
i found
Now type this in the terminal
Code:
adb logcat -v long > logcat.txt
or
Code:
adb logcat > logcat.txt
you shall have a log file called name of logcat.txt inside your ADB folder.
i test next day !
if this work we have backup from stock without twrp, simple & good
i write my experiences after test !
Hi, TWRP now available. Look https://forum.xda-developers.com/9-lite/development/honor-9-lite-twrp-3-2-1-0-available-t3771358
From now Backup/Restore NO problem
principle question & understand question
all test's NOT work.
last test made with twrp : twrp/install system.img, twrp flash this image with no errors.
now reboot to system : twrp write "no OS is installed .."
i mean, the problem is the differences from Android 7 and 8
i mean : in Android 8 is boot-sequence other as in Android 7
why : i have updated one+ 3T and Sony Z 2, inside LOS 14.1, updated to LOS 15.1, this 2 phones work no with OREO.
i mean, this updates for Android 7 core and i need now LOS 15.1 for installing on Android 8 core.
my knowledge : i am wait on LOS 15.1, written for OREO-Core.
the first version H9L came with factory-Android 7, all LOS 14.1 (RR ...) work on this
my phone is from February 2018 and have factory-OREO on board
with OREO begin a new era
essence : i am to fast with this phone and OREO wait on developer's
but - the factory-OREO work good enough for me (with root) - only : i am LOS-fan since many year :angel:
i am test https://forum.xda-developers.com/9-lite/development/kangvip-rom-emui-8-0-t3775904
for first oreo-developer-rom work good. it is stock-rom with modified menu ( menu / advanced settings).
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!
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
Code:
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption work
- Otg work
- Vibrator
- Zip Flash
- Mtp/adb
- F2FS support
- Fastbootd
- Adb sideload
- Backup restore and image flash
Not working:
-Tell me
INSTALLATION:
1. Download the TWRP image file to your PC.
2. Put your device into fastboot.
3. Type the following command to flash the recovery:-
Code:
fastboot flash recovery "name_of_recovery.img"
4. On installation of TWRP , to boot the recovery do:-
Code:
fastboot boot "name_of_recovery.img"
The device will automatically reboot into TWRP.
5-A. You are using Xiaomi.eu Miui or custom Rom?
You can enjoy with a functional Data Decrypt
5-B You are using Miui EEA - Global -Cn or any custom rom that doesn't ship custom vbmeta.
6. Download this zip, copy by pc or using otg and flash this zip that will prevent twrp replacing.7. 7. Download VbMeta and flash by fastboot
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img"
7. Reboot into twrp (Take longer Time)
Code:
fastboot boot "name_of_recovery.img"
8. Format Data and Reboot
NOTES:
By Command fastboot boot, recovery will decrypt everytimes you need, also with Global Rom and without patched vbmeta.
Download:
TWRP
VbMeta
(Version tag will follow vendor, a lower version tag than your vendor does not mean that recovery will not work)
Donation:
PayPal: paypal.me/manuelbiancodev
Kernel Source: Prebuilt kernel extracted from https://bigota.d.miui.com/V12.2.6.0.RJBMIXM/miui_UMIGlobal_V12.2.6.0.RJBMIXM_2bd819937d_11.0.zip
Telegram Group: @MBsRoom
Can it be flashed through TWRP?
What's the preferred option - installation as a default recovery or rather booting from PC?
I ask because majority of recent recoveries tend to fall in fastboot bootloop and were not working properly with MTP nor decryption once flashed
New instructions for eea and global miui user, post updated
Firmware xiaomi.eu 21.2.24, installed recovery 3.5.0_10 (MBTWRP_12.2.5_CMI), accepts the password, decryption is successful, the system section in the recovery explorer sees but, when trying to create a backup, writes that "not all users are decrypted" and asks decrypt user XSpace (999) and enter his password. My current password is failing. If you ignore the decryption of this user, and try to continue creating the archive, the system partition is not in the backup list (although it is mounted beforehand).
What could be the problem and how to fix it?
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
manuelbianco said:
New Release!
-Merged 3.5.1 teamwin recovery changes
-Cleaned and ordered twrp flags
-Support to system_ext ro mount
-Improvements into usb managing
Click to expand...
Click to collapse
when i boot in this latest, i can't flash all custom, like hentaiOS.
When i am on 12.2.5 ( previous ) it works.
But how can i switch/flash twrp img file when i a, on your twrp?
When i choose install and use image, in wich slot is recovery?
New Release!
-Merged teamwin recovery changes
-Workaround for mtp after format data
(After format data, reboot to recovery, now mtp is working, unmount data and re-mount data or reboot to recovery to flash or manage data files)
Thanks
Gr8 work! decryption and data workarounds are working as described
Hi,
I flash my mi 10 pro with the Mi flashtool to V12.2.5.0.RJAMIXM_20210123.0000.00_11.0_global and after that I follow your description.
After:
- C:\adb>fastboot flash recovery MBTWRP_14-03-2021_CMI.img
target reported max download size of 805306368 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.890s]
writing 'recovery'...
OKAY [ 0.476s]
finished. total time: 3.367s
- install no_replace_twrp_avb2.zip under TWRP
- C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.008s]
writing 'vbmeta'...
OKAY [ 0.010s]
finished. total time: 0.018s
- fastboot boot MBTWRP_14-03-2021_CMI.img
It is not possible to mount the storage
Maybe someone have an idea?
why you trying to boot from local img in the last step?
mi 10 pro andriod11 test ok~
great work~~~thx
manuelbianco, I love you. This is awesome! Finally someone solving the TWRP problem on CMI. We should all donate money for your efforts! Any patreon or paypal link to send you a beer or dinner?
underlines said:
manuelbianco, I love you. This is awesome! Finally someone solving the TWRP problem on CMI. We should all donate money for your efforts! Any patreon or paypal link to send you a beer or dinner?
Click to expand...
Click to collapse
Thanks
Pay Manuel Bianco using PayPal.Me
Go to paypal.me/manuelbiancodev and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.me
manuelbianco said:
Thanks
Pay Manuel Bianco using PayPal.Me
Go to paypal.me/manuelbiancodev and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.me
Click to expand...
Click to collapse
I moved to Thailand and just wanted to open a Paypal account to donate to you. Turns out, Paypal isn't accepting registrations from Thailand since August 2020.
Hello, I can decrypt it directly after flashing in, but it can’t be decrypted normally after updating the flashing package. What should I do with this?
Twrp 3.5.2 Released !
manuelbianco said:
Twrp 3.5.2 Released !
Click to expand...
Click to collapse
I use 3.5.1. I updated it from with in twrp. There is no problem and no bug. But I did not see any changes. And it still opens late.
My device mi 10 pro
slawekking said:
Hi,
I flash my mi 10 pro with the Mi flashtool to V12.2.5.0.RJAMIXM_20210123.0000.00_11.0_global and after that I follow your description.
After:
- C:\adb>fastboot flash recovery MBTWRP_14-03-2021_CMI.img
target reported max download size of 805306368 bytes
sending 'recovery' (131072 KB)...
OKAY [ 2.890s]
writing 'recovery'...
OKAY [ 0.476s]
finished. total time: 3.367s
- install no_replace_twrp_avb2.zip under TWRP
- C:\adb>fastboot flash vbmeta vbmeta.img
target reported max download size of 805306368 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.008s]
writing 'vbmeta'...
OKAY [ 0.010s]
finished. total time: 0.018s
- fastboot boot MBTWRP_14-03-2021_CMI.img
It is not possible to mount the storage
Maybe someone have an idea?
Click to expand...
Click to collapse
Damn, I have the same Problem. I used a older Version and it worked to mount /Data. But sadly the /system_root is not compatible with the MIUI 12.5 EU Rom.
Dont know, maybe it's a bug in the recent Version. I get the Error "unable to mount /data/media/TWRP/.twrps", when I try to change the File Format.
But TWRP is installed on the System and I can access the folder under /data, and see the folders, but no data.
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