hi, I own several Chinese tablets. precisely because they are Chinese they are stuck with their Android (8-9) and will never be updated. I intend to understand how to unlock these devices and understand how they work, and create a custom rom based on lineageos to try to do this. I've seen several threads on this forum but I've never figured out how to actually work with it.
do you have kernel source code and binary blobs for that tablet?
no. its china tablet. can i extract it?
my tablet: Vankyo S20 matrixpad
no, you can't extract kernel source code from tablet.
so what i can do?
nothing. you can port precompiled ROM, but that only works on between same android version.
you can run GSI but requires treble device (separate vendor partition) or DSU loader
ok, can you give me the istructions?
instructions for what?
https://www.google.com/search?q=rom+porting+guide+site:xda-developers.com
https://forum.xda-developers.com/t/what-is-treble.3815957
https://www.xda-developers.com/dsu-sideloader-boot-custom-android-gsi
my device supports treble and VDNK 28.0. I checked with the app. https://play.google.com/store/apps/details?id=com.kevintresuelo.treble
so unlock bootloader, disable avb/dmverity (vbmeta) and flash system.img from fastboot
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Thanks!
i can also flash on the chinese tablet (treble compatible as the app), right? Can I already insert android 12/13 or risk weighing down the tablet and it is better that I use 11?
what is avb dmverity? how i can disable it?
and for the Gapps?
after unlocking, create vbmeta_disabled.img with this python script avbtool.py and flash it from fastboot
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta_disabled.img
then you can install GSI. I personally prefer android 10 because higher versions are too restricted for me.
how can i execute the script? I tryed to execute it in Python but gives me error.
this can work? https://forum.xda-developers.com/t/guide-unlocking-bootloader-and-disabling-verifiedboot.4104045/
without knowing what error I can't help you with python script.
if python don't work for you, you can try with stock vbmeta instead. the fastboot --disable-verity --disable-verification flag will change a byte during flashing process so avb becomes disabled. I do not recommend to flash random vbmeta of foreign devices.
you can backup own stock ROM off device with spd-research-tool (do your homework, I never used and can't assist)
https://androidmtk.com/download-spd-research-tool
so i need to write --disable-verity --disable-verification flash "image.img" in the flashing fastboot command?
yes, for vbmeta partition (like post #12, #13) once you have unlocked bootloader.
ok
when trying to unlock the bootloader with "fastboot flashing unlock" this happens
{
"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"
}
FAILED (remote: Not implemet.)
finished. total time: 0.001s
i have an already unlocked bootloader? or i cannot unlock it?
edit: i executed this command: fastboot getvar unlocked
-----------
unlocked:
finished. total time: 0.001s
----------
????
i cannot determine if is locked or not XD
you can determine by doing something that is only allowed in unlocked state, such as formatting cache partition (does not harm)
Code:
fastboot format:ext4 cache
you can try different cmd
Code:
fastboot oem unlock
make sure in android you have set oem unlocking allowed in developer options as prerequisite for fastboot unlock.
aIecxs said:
you can determine by doing something that is only allowed in unlocked state, such as formatting cache partition (does not harm)
Code:
fastboot format:ext4 cache
you can try different cmd
Code:
fastboot oem unlock
make sure in android you have set oem unlocking allowed in developer options as prerequisite for fastboot unlock.
Click to expand...
Click to collapse
Ok, i try.
I already tried oem unlock, but it does not recognize the command.
some OEMs use different command (like Vivo fastboot bbk vivo_bsp unlock_vivo) some use special app or other tools (Xiaomi Unlock tool) and some devices aren't unlockable at all.
try to dump ROM with SPD research tool for further analysis, maybe bootloader lock state can be modified offline (like devinfo frp or config partition)
you can examine android bootloader (aboot/sboot/lk/...) for hidden fastboot commands
How to Discover Hidden Fastboot Commands
There are many hidden fastboot commands on your device. In order to find them, we will need to dump the bootloader and examine the contents!
www.xda-developers.com
Related
Most Qualcomm-based Android PDAs support emergency download (EDL) mode allowing to unbrick device, unlock bootloader or modify protected device parameters. If ADB interface is accessible, "adb reboot edl" can be used to reboot to EDL mode.
Many bricked PDAs cannot be booted with full ADB support while FastBoot mode is accessible. But if bootloader is locked, there is no way to flash a partition or boot an image.
Some firmwares support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device.
Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
In the attached example, the mentioned string is located at offset 2685c.
I occasionally locked bootloader in my unlocked/rooted Xiaomi Redmi Note 3 Pro (Snapdragon) so it could boot to FastBoot or Diagnostic 900E modes. Tried to swich from 900E to 9008 with QPST but it reported unspecified error.
Analyzing aboot (emmc_appsboot.mbn), found that it supports "reboot-edl" so the only remaining thing was to find a way to send it to the bootloader.
With the attached fastboot.exe, successfully rebooted to EDL mode (9008) and re-flashed proper partition images.
Of course, patched version does not support "reboot-bootloader" command because it has been replaced by "reboot-edl".
There also is a detailed guide.
Works perfectly for me
It's working and for me also! Great work!
Many users can to reject the test point method.
s_wheel said:
It's working and for me also!
Click to expand...
Click to collapse
Please don't forget to vote to collect a proper statistics.
Thank you very much. You are a genius ;D
Thank you so much.
I was able to enter edl-mode but miflash gives error 0x80070008 max buffer sector is 256. What can i do?
Unfortunately, I'm not familiar with MiFlash so cannot help you. It is better to search other threads (here and on Xiaomi).
It doesn't work on xiaomi Mi5
What a pity, I saw for the moment the hope
tecno789 said:
It doesn't work on xiaomi Mi5
Click to expand...
Click to collapse
Will take a look at Mi 5 bootloader. Maybe there is a solution too.
emuzychenko said:
Will take a look at Mi 5 bootloader. Maybe there is a solution too.
Click to expand...
Click to collapse
Thanks too much.
I will appreciate it
Who has no success with this method, please upload somewhere (or post URL to an existing file) the image file of your "aboot" partition from FastBoot firmware, I will try to analyze them. For Redmi Note 3 Pro, image file is named "emmc_appsboot.mbn". If your FastBoot firmware contains a batch file that calls fastboot.exe, the appropriate image file name can be found there.
hi i can't get it work on xiaomi mi max
here is my aboot and emmc_appsboot.mbn
https://drive.google.com/open?id=0B2M9hEQgSgheZjFNeFR4U2tCb00
scarletnokarasu said:
can't get it work on xiaomi mi max
Click to expand...
Click to collapse
Your bootloader supports the following oem commands in FastBoot mode:
oem unlock
oem lock
oem edl
oem device-info
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem poweroff
oem select-display-panel
So "oem edl" should switch the phone to EDL mode (any fastboot.exe will support that).
Additionally, "oem poweroff" should power the phone off.
Checked Mi 4c, Mi 5 and Mi Max bootloaders - all of them support "oem edl" to switch to EDL mode. Looks like a kind of "protection" is implemented in RN3P bootloader that supports only "reboot-edl" command.
emmc_appsboot.mbn file from Fastboot firmware of 7.3.5.0 MAAMIDD Global Stable of Mi 5 - https://mega.nz/#!OUZ1QaoI!EIgsKTOn6PQZ236pluhHmVRQ5D9HCKWeNRfzqgFbkgM
This will support all of that mentioned by @emuzychenko
{
"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"
}
But it is mentioned that edl is blocked in 7.3.x.x firmware, so how to check whether edl is working or not ??
Thanks
anil4523 said:
https://mega.nz/#!OUZ1QaoI!EIgsKTOn6PQZ236pluhHmVRQ5D9HCKWeNRfzqgFbkgM
Click to expand...
Click to collapse
Sorry but cannot download the file - mega.nz asks me for creating an account.
you are a genius . I can now say bye bye to testpoint method
Awesome guide ...
Worked for me also....
Here is google drive link of boot.img & emmc_appsboot.mbn file of 7.3.5.0 MAAMIDD Global Stable for Mi5 - https://drive.google.com/open?id=0B0M_ponZ2Qxjd0lueS1fREtWRkE
Video - https://www.youtube.com/watch?v=4GOi61S-qUs
my miflash is giving error 0x80070008 Open Serial Port "\\.\COM8"
{
"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"
}
Lenovo M7 3rd Gen (TB-7306F) Unlock Bootloader and Root Android 11
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
Requirements
PC
MTK drivers , Adb and Fastboot drivers Installed
Magisk APP
Drivers and Softwares
MTK Drivers
ADB and FastBoot Drivers
SDK (in attaeched files)
Vbmeta files (in attaeched files)
Magisk App
Method
1. Install the all things in given above
Extract SDK.zip and open that folder
2. Type cmd in address bar
3. go to about device . tap 7 times on build number and go to developer options and enable oem unlock
4. Reboot to Fastboot Mode
adb reboot bootloader or using recovery
5.Connect the tablet to Pc using data cable.
5.Type in CMD,
fastboot flashing unlock (automatically wipe data)
press vol.up key
fastboot reboot
______________________________________________________________________________________________________________________
Root______________________________________________________________________________________________________________________
1.Make a patched boot.img or download the patched boot.img (Attached files)
2.Flash all empty Vbmeta Files according to the Partition (Vbmeta.zip) Type these in CMD
Code:
adb reboot fastboot
fastboot flash vbmeta_system_a {path to vbmeta_vbmeta_system_a.bin}
fastboot flash vbmeta_system_b {path to vbmeta_system_b.bin}
fastboot flash vbmeta_a {path to vbmeta_a.bin}
fastboot flash vbmeta_b {path to vbmeta_b.bin}
fastboot flash boot_a {path to boot_a.img}
fastboot flash boot_b {path to boot_b.img}
fastboot reboot
Example
3.Reboot to device to recovery mode by Pressing Vol. UP + Vol. Down + Power.
4.Wipe Data and Reboot. if you didnt wipe data you will get Bootloop.
Note
if you flash full stock rom through lenovo rescue and smart assitant, it will automatically lock the boot loader
you need to unlock the bootloader using above steps
______________________________________________________________________________________________________________________
Remove the Warning
___________________________________________________________
1.Download the Waring_Remove.zip extract it
2.Type these in CMD
Code:
adb reboot bootloader
fastboot flash lk_a {path to lk_a.bin}
fastboot flash lk_b{path to lk_a.bin}
fastboot reboot
Fastboot mode vs Bootloader mode
Fastboot mode
Bootloader mode
Outstanding work, thank you. I have been hassling with this tablet for a month and just today I figured out how to unlock the bootloader. This is great work sir, thanks
If I didn't enjoy wrecking tech toys, I'd quit. Twice now I had to rescue the tablet because after flashing patched boot_a and b it loops even wipe a wipe.
It just finished restoring and it relockes the bootloader in the process.
Lenovo rescue tool works great
I think I will take a day off from this uninspiring tablet
toddy127 said:
If I didn't enjoy wrecking tech toys, I'd quit. Twice now I had to rescue the tablet because after flashing patched boot_a and b it loops even wipe a wipe.
It just finished restoring and it relockes the bootloader in the process.
Lenovo rescue tool works great
I think I will take a day off from this uninspiring tablet
Click to expand...
Click to collapse
Did you flashed the vbmeta?
I will admit I got a little confused with the process and forgot to flash the meta.
Thanks again. I am unlocked and rooted finally. I used the Linux on a stick and Windows. It was very easy thanks to you and the other developers work.
I left the bootloader warning on the tablet lol
Man, you are a life saver! Spent hours looking for a write up on this tablet. I actually ended up stuck in a bootloop after flashing vbmeta and then writing fastboot reboot according to the image above. (Im sort of a noob when it comes to this stuff.) After a while of tinkering was able to fix it simply by holding the vol + and vol - and plugging in usb from PC. Got it to load into fastboot and was able to wipe. But for real much appreciate the time and effort put into this write up especially for a niche tablet like this one. + Respect
smiley9000 said:
fastboot flash vbmeta_system_a {path to vbmeta_vbmeta_system_a.bin}
Click to expand...
Click to collapse
this command fails for me :/
>
Downloads/vbmeta/vbmeta_
❯ fastboot flash vbmeta_system_a vbmeta_system_a.bin
Sending 'vbmeta_system_a' (8192 KB) OKAY [ 0.343s]
Writing 'vbmeta_system_a' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
any ideas?
Everything is at your own risk!!!
GSI select only with architecture A64-AB (also may be called arm32-binder64-ab) starting from Android 10
This method really works, no one expected that redmi 9A can run gsi arm-64ab now there is such a possibility
You do it on your own, I don't belong to this
Installing the driver for fastboot
USB DRIVER
on your phone go into fastboot mode connect usb phone to computer
open cmd, go to the Redmi + 9A + GSI + Installer folder, there we will have the path, copy it and go to cmd, cd the path of the folder.
prescribe
fastboot reboot fastboot - our phone has rebooted
We go to the folder Redmi + 9A + GSI + Installer and copy the system image there necessarily A64-AB or arm32-binder64-ab
this image.img needs to be renamed > system.img then we press flash-twrp.bat and we have the installation
We extract from the archive https://drive.google.c...8AJoGd&export=download folder to the root of drive C, connect the phone in fastboot mode to the computer and open the command line on the computer, into which we insert the lines in turn:
cd C:\9A\fastboot
Fastboot flash dtbo dtbo.img
Fastboot flash boot boot.img
fastboot flash super super.img
Fastboot flash vbmeta_vendor vbmeta_vendor.img
Fastboot flash vbmeta_system vbmeta_system.img
Fastboot flash recovery recovery.img
Fastboot flash vbmeta vbmeta.img
fastboot --disable-verification --disable-verity flash vbmeta vbmeta.img
Fastboot erase userdata
fastboot reboot
fastboot
Click to expand...
Click to collapse
When the device successfully reboots into the system, we transfer it back to fastboot mode and again open the command line on the computer, into which we insert the lines in turn:
fastboot reboot fastboot
Click to expand...
Click to collapse
GSI auto installer for Redmi 9A
1) Download the GSI image and rename it to system.img (GSI can also be in *.xz and *.zip archives, you need to unpack) https://sourceforge.net/p/amber-gsi/activity/?page=0&limit=100#60984432478b418cb8a7ea05
2) Unzip the archive Attached fileRedmi+9A+GSI+Installer.zip ( 3.84 MB )
3) Put system.img in it
4) Run flash-twrp.bat
5) The smartphone will reboot and you will get a working unofficial firmware
First, unlock the bootloader!
https://sourceforge.net/p/amber-gsi/activity/?page=0&limit=100#60984432478b418cb8a7ea05
{
"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"
}
It's applicable for redmi 9AT too?
I found that Treble Info apk , gives good info about the device, it tells you if it works for your device, and if it works, it recommends which GSI image to download/flash
https://play.google.com/store/apps/details?id=tk.hack5.treblecheck&hl=&gl=US
another mirror:
https://www.apkmirror.com/apk/hacki...lease/treble-info-5-0-6-android-apk-download/
I also made a guide on how to flash it. No fishy .bat files.
Xiaomi Redmi 9A 9i 9AT 10A
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Download link doesn't properly work.
NorthenPL said:
Download link doesn't properly work.
Click to expand...
Click to collapse
It's fake because coincidentally the download link is the only one that is incorrectly inserted
Phone: Realme V11 5G (RMX3121)
I wanted to flash a GSI image to my phone yesterday, but after flashing the system.img, I couldn't boot it. So I decided to go back to realme UI. I found an `ofp` image for my device and decrypted it using `mct ofp extractor` and merged `super.img` using `simg2img` tool. I use `MTK Flash Tool` to flash the image. But it still didn't work. When I reboot, it stays on the white "realme" screen for a long time and then goes to another screen. At that time, `adb` can relocate my phone. But after about 10 minutes, it will reboot.
{
"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"
}
With regards to your ADB issue:
ADB client on PC finds its host counterpart ADBD on phone, but can't talk with it because of missing RSA key: the device is shown as unauthorized,
Possible fix
1. Revoke USB debugging authorization in Developer options.
2. Restart ADB Server:
Code:
adb kill-server
adb start-server
3. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
4. Now Check the device
It is now authorized!
jwoegerbauer said:
With regards to your ADB issue:
ADB client on PC finds its host counterpart ADBD on phone, but can't talk with it because of missing RSA key: the device is shown as unauthorized,
Possible fix
1. Revoke USB debugging authorization in Developer options.
2. Restart ADB Server:
Code:
adb kill-server
adb start-server
3. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
4. Now Check the device
It is now authorized!
Click to expand...
Click to collapse
I can't boot into the system and authorize the device XD
Hello, thank you so much for your development work
alfaputra said:
Hello, thank you so much for your development work
Click to expand...
Click to collapse
So strange, it makes me wonder if you're a robot. I'm just facing a problem and need to solve it. I am not a developer.
you forgot to disable dm-verity. assuming your phone has vbmeta partition and supports fastboot mode, flash the vbmeta.img with following flags
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
btw by "merged super.img using simg2img tool" you probably mean "extracted" - simg2img is a decompression conversion from OTA to raw partition image
WinghongZau said:
I can't boot into the system and authorize the device XD
Click to expand...
Click to collapse
But anyone can boot a phone into recovery mode and then issue the mentioned ADB commands there
aIecxs said:
you forgot to disable dm-verity. assuming your phone has vbmeta partition and supports fastboot mode, flash the vbmeta.img with following flags
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
btw by "merged super.img using simg2img tool" you probably mean "extracted" - simg2img is a decompression conversion from OTA to raw partition image
Click to expand...
Click to collapse
yeah now i have disabled it. but I actually use `simg2img` to merge 3 `super.x.img.xxxxx` file into `super.img`. now I flashed a Android 11 GSI for it and stuck in `android` screen.
WinghongZau said:
yeah now i have disabled it. but I actually use `simg2img` to merge 3 `super.x.img.xxxxx` file into `super.img`. now I flashed a Android 11 GSI for it and stuck in `android` screen.
Click to expand...
Click to collapse
can you explain how you merge 3 super.x.img.xxxxx with simg2img?
aIecxs said:
can you explain how you merge 3 super.x.img.xxxxx with simg2img?
Click to expand...
Click to collapse
Code:
simg2img super.0.img.xxx super.1.img.xxx super.2.img.xxx super.img
maybe it is the extract, i'm not sure.
didn't know simg2img accepts more than two arguments (haven't used for while)
maybe concatenate parts yourself (windows/linux?)
or try this ROM maybe
https://forum.xda-developers.com/t/discontinued-gsi-11-lineageos-18-x-gsi-all-archs.4205461
aIecxs said:
didn't know simg2img accepts more than two arguments (haven't used for while)
maybe concatenate parts yourself (windows/linux?)
or try this ROM maybe
https://forum.xda-developers.com/t/discontinued-gsi-11-lineageos-18-x-gsi-all-archs.4205461
Click to expand...
Click to collapse
Maybe we're not talking about the same thing XD.
> simg2img
Usage: simg2img <sparse_image_files> <raw_image_file>
yes we do, but the usage has changed
nevertheless, you could try old usage (linux)
Code:
cat super.?.img.xxx > super.img.xxx
simg2img super.img.xxx super.img
aIecxs said:
yes we do, but the usage has changed
nevertheless, you could try old usage (linux)
Code:
cat super.?.img.xxx > super.img.xxx
simg2img super.img.xxx super.img
Click to expand...
Click to collapse
could you tell me why I flashed AOSP for my phone but it got stuck on the "android" logo and when I flashed Pixel Experience it got stuck on the google logo? I'm so irritable due to it.
it stuck on it's logo, what's the difference?
possible reasons
- avb/dm-verity not disabled
- broken encryption
- broken ROM
- interrupted flashing progress
- you did not factory reset
- you did not wait long enough
aIecxs said:
it stuck on it's logo, what's the difference?
possible reasons
- avb/dm-verity not disabled
- broken encryption
- broken ROM
- interrupted flashing progress
- you did not factory reset
- you did not wait long enough
Click to expand...
Click to collapse
thx. if I have some questions I will reply you tomorrow. maybe my english isn't good. never mind it.
{
"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"
}
A beautiful ROM based on AOSP and Pixel with good quality of features
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
Click to expand...
Click to collapse
Screenshots
First Time Install / Clean Flash
Flash Instructions
//plug in USB while holding VOL+ during boot, make sure charge LED is blue
//reboot to fastbootd:
fastboot reboot fastboot
//flash the ROM:
fastboot set_active a
fastboot flash boot boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot erase metadata // only on first install, ignore on upgrading
fastboot delete-logical-partition product_a
fastboot delete-logical-partition system_a // so that fastboot won't complain about disk space
fastboot create-logical-partition product_a 0 // size is 0, will auto-resize during flash
fastboot flash product product.img
fastboot create-logical-partition system_a 0
fastboot flash system system.img
//erase userdata:
fastboot erase userdata // also only on first install
fastboot flash vendor vendor.img
fastboot flash odm odm.img
fastboot flash recovery recovery.img
//boot the ROM:
fastboot reboot
Click to expand...
Click to collapse
Download:
ROM
kernel(SU)
fuji-kernelSU
Support Group: Telegram
CherishOS for Xperia 5 II
Build Type: Unofficial
ROM Kernel: Linux 4.19.272
ROM Firmware Required: Latest fw 58.2.A.10.126 Recommended.
Based On: AOSP
Android OS version: 13
Security patch level: 05 February 2023
Sources: https://github.com/XperiaBrickers
Thanks for this beautiful ROM for 5 II. But fast charge is not working. The phone charges really slow or doesn't charge at all unless I restart the phone and do not unlock my lockscreen. After unlocking lockscreen, the same issue continues. Maybe have a fix?
raspingcoot said:
Thanks for this beautiful ROM for 5 II. But fast charge is not working. The phone charges really slow or doesn't charge at all unless I restart the phone and do not unlock my lockscreen. After unlocking lockscreen, the same issue continues. Maybe have a fix?
Click to expand...
Click to collapse
turn on/off this
tuan94_bg said:
turn on/off this
View attachment 5846421View attachment 5846419
Click to expand...
Click to collapse
Thanks a lot brother. Pause charging was sett to "on". I changed it to "off" and it fixed my problem so easily. I was flashing multiple kernals to fix this with no vain. Can you suggest me which one of the kernals should I flash?
raspingcoot said:
Thanks a lot brother. Pause charging was sett to "on". I changed it to "off" and it fixed my problem so easily. I was flashing multiple kernals to fix this with no vain. Can you suggest me which one of the kernals should I flash?
Click to expand...
Click to collapse
if you want performance then you should choose fuij, if you want stability use perf. you can also use extra fkm to customize cpu as you like