Database Info

[Q] Can't Get Custom Kernel To Stick

This probably belongs in Dev forum, but can't post there yet - How do I get MY custom kernel to "stick"?
I have a new kernel compiled for TF300T and repackaged it into a new boot.img - I am banging my head against the wall to get it reflashed.
fastboot does not work (per other users - it says it writes, but on reboot if reverts to orig and "fastboot boot <new boot img>" also fails):
fastboot flash boot newbootTF300.img
sending 'boot' (5196 KB)...
OKAY [ 1.699s]
writing 'boot'...
OKAY [ 2.174s]
tried - building a CWM update.zip - says it updates, but on reboot - back to other kernel.
even tried directly dding to boot partition when in CWM but - yet again - boots back to previous kernel:
~ # dd if=/data/media/newbootTF300.img of=/dev/block/mmcblk0p4
10392+0 records in
10392+0 records out
5320704 bytes (5.1MB) copied, 2.677940 seconds, 1.9MB/s

Perhaps my answer in the below thread can be helpful ?
http://forum.xda-developers.com/showthread.php?t=1931202

[GUIDE] [HOW TO] Return Your Huawei Watch 2 to Stock

Hi, everyone. After reading posts of (and having experienced my own) boot loops and seeing as how there is a guide for the first Huawei watch,
I've decided that there should also be a guide for restoring the Huawei Watch 2 to stock ROM.
Getting Prepared
The bootloader unlocked on the watch. For instructions on how to do so, read janjan's TWRP Recovery guide.
ADB/fastboot and drivers already setup on your computer
ADB debugging enabled on the watch. You can find instructions for this at the same URL link above.
Restoring Via Batch/Shell Executable
The stock image files in janjan's thread are no longer available, so you'll have to go to this Reddit thread for the file.
Under the "Flashing back to stock" section, download the appropriate version for your watch.
Reboot your watch to bootloader either manually or via the ADB command:
Code:
adb reboot bootloader
Unzip the file
For Sawfish Devices:
At the command line, type in the following:
Code:
flash-all.bat (for Windows) or .flash-all.sh (for Linux)
fastboot oem lock
fastboot reboot
For Sawshark Devices: (or if you were having trouble executing the flash-all file successfully. NOTE: There's a missing image
file in the Sawshark stock file, so the flash-all file will not run successfully.)
Go to the folder where you extracted the stock image file and extract the zip file that's there.
Then go to the command line and type in the following:
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot oem lock
fastboot reboot
Credits/Thanks
janjan - HUAWEI WATCH 2 (LTE-Sawshark) & (BT-Sawfish)-OWDE.180926.001.A1
- [RECOVERY]+[sawshark(4G)+sawfish(BT)]Unofficial TWRP 3.1.1-0-[29-3-18]
travis82 - [ROM] [KERNEL] [SAWSHARK] Oreo OWDE.180215.017 [DEC/24/2018]
Skin1980 - [GUIDE] [HOWTO] Return to stock for Huawei Watch
davpel - [GUIDE][HOW TO]Boot into Fastboot Mode
CadBuRy.VN - [Rom][NXG46W] Huawei Watch 2 4G L-09S Global Fastboot [Factory Images]

Great guide.
Will try this on my watch.
Thanks.

does not work on leo-dlxx...it will kill the device i restored via twrp another rom
anyone have a stock rom for leo-dlxx?

Timewolf said:
does not work on leo-dlxx...it will kill the device i restored via twrp another rom
anyone have a stock rom for leo-dlxx?
Click to expand...
Click to collapse
I actually have the Leo-DLXX and I wrote this guide mainly for that watch. Do you remember what error messages you received? How does it kill the device?

How prevent upgrade after this? I flash it and all good, but it upgrades to last firmware and I see no solution to stop it

"Invalid sparse file format at header magi" while trying to flash system.img

Thanks!!! You saved my Smartwach because it was bricked and I couldn't find orginal stock firmware

not work with sawshark leo-dll only stuck in logo

Hi. I purchased this watch for a specific medical reason, because the developer of an app xDrip (for continuous glucose monitoring), produced a patch for it to work with my medical device (works around a common buggy Wear OS implementation across many manufacturers.) Unfortunately their patch seems to only work on the firmware OWDD.180215.018, but mine came with OWDD.180926.001.A1.
Any tips to downgrading to OWDD.180215.018? I have the files and tried flashing the zip from TWRP and also Fastboot with flash-all.sh. Both fail.
% ./flash-all.sh
Sending 'bootloader' (10020 KB) OKAY [ 0.468s]
Writing 'bootloader' OKAY [ 3.323s]
Finished. Total time: 4.139s
Rebooting into bootloader OKAY [ 0.115s]
Finished. Total time: 0.116s
--------------------------------------------
Bootloader Version...: SAWFISHV6.5
Baseband Version.....: N/A
Serial Number........: YGV7XXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.111s]
Checking 'version-bootloader' OKAY [ 0.115s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
A little bit of info on the patch (if that is of any use - maybe it can be tweaked itself) https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5

square_eyes said:
Hi. I purchased this watch for a specific medical reason, because the developer of an app xDrip (for continuous glucose monitoring), produced a patch for it to work with my medical device (works around a common buggy Wear OS implementation across many manufacturers.) Unfortunately their patch seems to only work on the firmware OWDD.180215.018, but mine came with OWDD.180926.001.A1.
Any tips to downgrading to OWDD.180215.018? I have the files and tried flashing the zip from TWRP and also Fastboot with flash-all.sh. Both fail.
% ./flash-all.sh
Sending 'bootloader' (10020 KB) OKAY [ 0.468s]
Writing 'bootloader' OKAY [ 3.323s]
Finished. Total time: 4.139s
Rebooting into bootloader OKAY [ 0.115s]
Finished. Total time: 0.116s
--------------------------------------------
Bootloader Version...: SAWFISHV6.5
Baseband Version.....: N/A
Serial Number........: YGV7XXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.111s]
Checking 'version-bootloader' OKAY [ 0.115s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
A little bit of info on the patch (if that is of any use - maybe it can be tweaked itself) https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5
Click to expand...
Click to collapse
Well, I haven't ever seen sth like you're trying to do, but can you point me to the source of the rom you're trying to flash?

square_eyes said:
Hi. I purchased this watch for a specific medical reason, because the developer of an app xDrip (for continuous glucose monitoring), produced a patch for it to work with my medical device (works around a common buggy Wear OS implementation across many manufacturers.) Unfortunately their patch seems to only work on the firmware OWDD.180215.018, but mine came with OWDD.180926.001.A1.
Any tips to downgrading to OWDD.180215.018? I have the files and tried flashing the zip from TWRP and also Fastboot with flash-all.sh. Both fail.
% ./flash-all.sh
Sending 'bootloader' (10020 KB) OKAY [ 0.468s]
Writing 'bootloader' OKAY [ 3.323s]
Finished. Total time: 4.139s
Rebooting into bootloader OKAY [ 0.115s]
Finished. Total time: 0.116s
--------------------------------------------
Bootloader Version...: SAWFISHV6.5
Baseband Version.....: N/A
Serial Number........: YGV7XXXXXXXXXXXX
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.111s]
Checking 'version-bootloader' OKAY [ 0.115s]
Snapshot cancel FAILED (remote: 'unknown command')
fastboot: error: Command failed
A little bit of info on the patch (if that is of any use - maybe it can be tweaked itself) https://github.com/NightscoutFoundation/xDrip/wiki/Patching-Android-Wear-devices-for-use-with-the-G5
Click to expand...
Click to collapse
And the second question: Do you own sawfish (WiFi) or Sawshark (LTE) watch?
(I'm going to sleep soon but I'll take a look on this tomorrow)

Lord Sithek said:
And the second question: Do you own sawfish (WiFi) or Sawshark (LTE) watch?
(I'm going to sleep soon but I'll take a look on this tomorrow)
Click to expand...
Click to collapse
sawfish sorry! Will update post. ROM is in the link but I'll have to ask the dev for the source.

Lord Sithek said:
square_eyes said:
sawfish sorry! Will update post. ROM is in the link but I'll have to ask the dev for the source.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Can you share the link or the site where it was posted?.I just wanted to take a look Anyway, maybe you could try the approach from the instructions for sawshark from the opening post here. I mean extract zip and flash images separately in fastboot mode.
Also make sure you have the correct rom version for wifi variant

Lord Sithek said:
Can you share the link or the site where it was posted?.I just wanted to take a look Anyway, maybe you could try the approach from the instructions for sawshark from the opening post here. I mean extract zip and flash images separately in fastboot mode.
Also make sure you have the correct rom version for wifi variant
Click to expand...
Click to collapse
I ended up getting it working. See here for how I rolled back the Wear OS version... https://github.com/NightscoutFoundation/xDrip/issues/749#issuecomment-850037862
Below is the link from above with the files (not source sorry - I'm not sure where that's kept). If you know how to make the demigod patch compatible with the latest official firmware/or even an unofficial ROM, that would be awesome.
See Huawei Watch 2 Care Pack .zip on...
Patching Android Wear devices for use with the G5
Nightscout version of xDrip+. Contribute to NightscoutFoundation/xDrip development by creating an account on GitHub.
github.com
the zip has two patches, and instructions.

square_eyes said:
I ended up getting it working. See here for how I rolled back the Wear OS version... https://github.com/NightscoutFoundation/xDrip/issues/749#issuecomment-850037862
Below is the link from above with the files (not source sorry - I'm not sure where that's kept). If you know how to make the demigod patch compatible with the latest official firmware/or even an unofficial ROM, that would be awesome.
See Huawei Watch 2 Care Pack .zip on...
Patching Android Wear devices for use with the G5
Nightscout version of xDrip+. Contribute to NightscoutFoundation/xDrip development by creating an account on GitHub.
github.com
the zip has two patches, and instructions.
Click to expand...
Click to collapse
Great, glad it worked for you. Unfortunatelly, Im not that skillfull to help you with latest firmware...

[Guide][GSI][13] GSI Install Guide for ROG Phone zs600kl

{
"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"
}
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
Introduction​ROG Phone 1 is no longer receiving any update since android 9 and no custom rom were made, which is sad since s845 is still a well performed CPU even now. However, by the help of Project Treble, we're able to install the latest android 12 (and so on) on this device.
The guide requires some basic knowledges of using SDK Platform Tools and recovery. But feel free to ask if you don't understand anything.
Hardware support​
ComponentCommentCameraWorksSpeaker / MicWorksBluetoothWorks** (Bluetooth in call, all Bluetooth codec supported by the hardware) *(No A2DP)
(Update: All bluetooth functions was now fixed on A13 and above)WiFiWorksSIM / Mobile Data / VoiceWorksVoLTEUnknownFingerprintWorks (see "workarounds and recommendations" to enable fingerprint wakeup)NFCWorksOffline ChargingBroken90Hz Refresh RateWorksAuto-brightnessWorks (May depend on the Rom)Proximity sensorWorksVibrationBrokenRGB backlight on the logoWorks* (Basic functions with an app on google play) *(Will need to set the light again whenever restart the phone)HDR content playbackBroken (Have some wired lines on the screen)
Steps to install​We have 2 ways to install, either through Fastboot or with TWRP. For data safety, I do not recommend break the force encryption whatsoever.
Make sure to Unlock Bootloader before proceeding any further!
A. Install through fastboot:
1. Extract vbmeta.img from the offical rom you're running.​
File attached is from version "WW-16.0420.2009.39", so upgrade to this version if you dont know how to extract vbmeta.img.
2. To disable dm-verity, do "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img".​3. Flash the gsi you choose in fastboot. Do "fastboot flash system (system image name.img)" .​4. Reboot to offical recovery and do a factory reset.​5. You are good to go!​
If you wish to use Magisk (I recommend Lygisk over Magisk since these gsi are force encryped), patch the boot image extract from the offical rom and flash it through Fastboot.
You can also boot to TWRP without flash it onto the device and use adb sideload to install zips, not recommend if you don't know what I'm talking about!
B. Install through TWRP:
1. Extract vbmeta.img from the offical rom you're running.​
File attached is from version "WW-16.0420.2009.39", so upgrade to this version if you dont know how to extract vbmeta.img.
2. To disable dm-verity, do "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img".​3. Flash the TWRP(attached) in fastboot. Do "fastboot flash boot twrp-3.4.0-0-Z01Q-16.0410.2003.24.img" .​4. Reboot to TWRP. Do "fastboot oem reboot-recovery".​5. Format data, cache and system parition in recovery.​6. Flash the gsi you choose in recovery. (flash the "image" into "system partition").​7. Flash any modification zips now.​8. (Optional) Flash "disforsenc_daisy__zero.zip"(attached) in TWRP to disable force encryption.​
It is not recommend to do this step if you really care about your data safety. If someone get your phone, they will be able to access all the files.
9. You are good to go!​
You can still use adb sideload to install zips(and lots of other functions) without disable force encryption. So it's really not recommend to disable it.
Workarounds and Recommendations​
To fix Bluetooth not opening or other Bluetooth related issue, refer to this guide I made. You will need Magisk to enable Aptx. This should NOT be needed anymore, since A13 builds have fix this.
Recommend to use this Gcam. It can utilize all the camera moudules and it's stable.
If you have any problem with mobile network/phone call, try to install and enable the ims apk in "phh/IMS features".
Most builds based on phh's build(which were listed on the wiki page) have a working safetynet, and the Universal Safetynet Fix will work with Magisk installed.
However some of them are still broken. So make sure the safety net is working without Magisk, then install Magisk.
RGB backlight of the ROG logo in the back can be control with this app found in google play. It's not made for this device, but basic functions will work.
My personal recommendation of gsi is crDroid maintain by Nazim. It have working safetynet and lots of customizable features I like. (Especially it can get rid of the search bar and at a glance which I HATE A LOT)
If you do want to enable fingerprint sensor while screen is off, set these two props using adb.
Code:
persist.asus.fp.wakeup=true
If you do want to use bottom usb port rather than the one on the side, set this prop. Also, to go back to the bottom one, set it to a600000.dwc3 .
Code:
persist.vendor.usb.controller.default=a800000.dwc3
If you do want to use double tab to wake, enable related settings in the GSI you use (also settings in "phh treble settings") if needed, and set this prop.
Code:
persist.asus.dclick=1
Credits​Rocky7842​xspx for testing the device with me​Numerous people and threads on the forum for some workaround or inspiration
And all the other devs for creating these wonderful modules/ROMs​

reserved

whats ver. i download from crDroid ??
crDroid-8.8-a64_bgN-slim-Unofficial.img.xz2022-09-03917.6 MB
69crDroid-8.8-a64_bgN-Unofficial.img.xz2022-09-031.1 GB
60crDroid-8.8-a64_bvN-Unofficial.img.xz2022-09-03756.4 MB
45crDroid-8.8-arm64_bgN-slim-Unofficial.img.xz2022-09-031.1 GB
268crDroid-8.8-arm64_bgN-Unofficial.img.xz2022-09-031.3 GB
523crDroid-8.8-arm64_bvN-Unofficial.img.xz2022-09-03944.5 MB
230
a64 or arm64 ?
bgN-slim , bgN or bvN ??

Dj.GriM said:
whats ver. i download from crDroid ??
crDroid-8.8-a64_bgN-slim-Unofficial.img.xz2022-09-03917.6 MB
69crDroid-8.8-a64_bgN-Unofficial.img.xz2022-09-031.1 GB
60crDroid-8.8-a64_bvN-Unofficial.img.xz2022-09-03756.4 MB
45crDroid-8.8-arm64_bgN-slim-Unofficial.img.xz2022-09-031.1 GB
268crDroid-8.8-arm64_bgN-Unofficial.img.xz2022-09-031.3 GB
523crDroid-8.8-arm64_bvN-Unofficial.img.xz2022-09-03944.5 MB
230
a64 or arm64 ?
bgN-slim , bgN or bvN ??
Click to expand...
Click to collapse
arm64 versions are all fine.

I got a rog phone 1 for a little more than a year now or so, its nice to see that we can at least have a update even if its not oficial. Im getting tyred of the same look of the UI and the aod, my god the stock ones are horrible but if i use another app for the aod it just drains the battery so fk quick. I will give a try to the pixel experience gsi

Microsoft Windows [Version 10.0.19044.2006]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>fastboot.exe devices
K7AZGV03070237J fastboot
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.030s
C:\platform-tools>fastboot flash system C:\platform-tools\crDroid-8.9-arm64_bgN-Unofficial.img
Sending sparse 'system_b' 1/7 (521508 KB) OKAY [ 12.520s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/7 (523009 KB) FAILED (remote: 'Error: Last flash failed : Volume Full')
fastboot: error: Command failed
C:\platform-tools>
i got error !!

Dj.GriM said:
Microsoft Windows [Version 10.0.19044.2006]
(c) Microsoft Corporation. All rights reserved.
C:\platform-tools>fastboot.exe devices
K7AZGV03070237J fastboot
C:\platform-tools>fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
Finished. Total time: 0.030s
C:\platform-tools>fastboot flash system C:\platform-tools\crDroid-8.9-arm64_bgN-Unofficial.img
Sending sparse 'system_b' 1/7 (521508 KB) OKAY [ 12.520s]
Writing 'system_b' OKAY [ 0.000s]
Sending sparse 'system_b' 2/7 (523009 KB) FAILED (remote: 'Error: Last flash failed : Volume Full')
fastboot: error: Command failed
C:\platform-tools>
i got error !!
Click to expand...
Click to collapse
i fixed now i chaneg the rom to another rom slim and working now
how to patch the boot image for lygisk ?? from offical rom asus rog phone ASUS_Z01QD or from crDroid-8.9-arm64_bgN-slim-Unofficial.img
i want to fix the bluetooth is not working now !
sorry for thats i am noob

Dj.GriM said:
i fixed now i chaneg the rom to another rom slim and working now
how to patch the boot image for lygisk ?? from offical rom asus rog phone ASUS_Z01QD or from crDroid-8.9-arm64_bgN-slim-Unofficial.img
i want to fix the bluetooth is not working now !
sorry for thats i am noob
Click to expand...
Click to collapse
First of all, since the system partition on this phone is designed for android 8/9, it didn't leave much spare space. So a lot of highly modified gsi is too big for the phone. If you wish to flash them, you'll need to follow along this guide to resize partitions (tested and work).
As for the lygisk (magisk) part, take the boot image of the stock ROM you were running (the exact same version is recommended), and use the app to patch the boot.img.
Or if you have installed TWRP, simply flash the zip file through TWRP. If it's encrypted, flash it through adb sideload and it'll be fine too.

does this still apply until date? is it worth it? does upgrading it will make my device performs better? dont get me wrong, i really want to upgrade, but i just need more insights.

edzraaa said:
does this still apply until date? is it worth it? does upgrading it will make my device performs better? dont get me wrong, i really want to upgrade, but i just need more insights.
Click to expand...
Click to collapse
Yes, the guide is still valid for now.
The performance overall is pretty good.
If what I mentioned that's not working is acceptable for you, I would recommend you to try it out. Plus you can always revert it to stock.

Rocky7842 said:
Yes, the guide is still valid for now.
The performance overall is pretty good.
If what I mentioned that's not working is acceptable for you, I would recommend you to try it out. Plus you can always revert it to stock.
Click to expand...
Click to collapse
Which version would you recommend based on the builds now?
I'm using it most for games and daily use. The reason i wanna upgrade is i noticed the game i played started to become laggy and it was not 60fps like it used to after update and update so I dont think it is optimized for the phone? The FPS drops when theres a teamfight. The game run SMOOTHLY on my friends phone which specs is lower than my ROG Phone 1. But his phone run on Android 11 if im not mistaken which i got an idea maybe its the Android version that have something to do with optimization?
I have the latest stock version same as yours stated in the post above. And your guide recommended crDroid which was Android 12 (at that time and it was crDroid 8.8 based on the user above) but that was last year. And by A13 fixed the Bluetooth thingy, by A13 does that mean Android 13? I'm having trouble to choose which ROMs. Or should I just upgrade to Android 12?
Sorry for asking but i just wanna be safe and Thank you for your time. Appreciate it

edzraaa said:
Which version would you recommend based on the builds now?
I'm using it most for games and daily use. The reason i wanna upgrade is i noticed the game i played started to become laggy and it was not 60fps like it used to after update and update so I dont think it is optimized for the phone? The FPS drops when theres a teamfight. The game run SMOOTHLY on my friends phone which specs is lower than my ROG Phone 1. But his phone run on Android 11 if im not mistaken which i got an idea maybe its the Android version that have something to do with optimization?
I have the latest stock version same as yours stated in the post above. And your guide recommended crDroid which was Android 12 (at that time and it was crDroid 8.8 based on the user above) but that was last year. And by A13 fixed the Bluetooth thingy, by A13 does that mean Android 13? I'm having trouble to choose which ROMs. Or should I just upgrade to Android 12?
Sorry for asking but i just wanna be safe and Thank you for your time. Appreciate it
Click to expand...
Click to collapse
There are crDroid 9 A13 builds maintain by Nazim.
I'd recommend you to try different ROMs and versions to see which one serve you the best.

i cant seems to get my wifi to work on crDroid. NEED HELP! Its on the latest crDroid. Or is it just me?

edzraaa said:
i cant seems to get my wifi to work on crDroid. NEED HELP! Its on the latest crDroid. Or is it just me?
Click to expand...
Click to collapse
Welp, i think i F'd it up . Do i need to do the vbmeta.img everytime? And im not sure what to do now. Changing back to partition A stuck on ROG loading. Since i f'd up i might play around and see what i can do.
UPDATE: I got it to work finally. Flashed EVERYTHING back to "WW-16.0420.2009.39" payload.bin incase you got an error and get stucked (bootloop, wont boot). THEN follow the steps above WITH NO MISTAKES!

I need to unlock the bootloader of my rog 1, but do you guys know how? The unlocktool.apk asus has provided is not working anymore

Yusop said:
I need to unlock the bootloader of my rog 1, but do you guys know how? The unlocktool.apk asus has provided is not working anymore
Click to expand...
Click to collapse
That is the only way AFAIK. Try to contact Asus for help.

[ROM][LINUX][ANGELICA][ANGELICAN] Droidian Bookworm

{
"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"
}
Requirements​
Android 10 firmware for your device:
Redmi 9C/9C NFC angelica: LINK.
Angelica​
Download the latest fastbootable image: droidian-UNOFFICIAL-phosh-phone-xiaomi_angelica-api29-armhf-nightly_XXXXXXXX.zip
Installation​
Extract the archive
run the flash_all script
Boot to fastboot and let the script flash everything.
UBports Installer
Alternatively the UBports installer can also be used to install Droidian.
Notes​
The default password is 1234.
List of working things can be found at https://github.com/droidian-mt6765/device-page
Bugs​
Encryption is not supported.
Mobile data needs an APN to be set up from Settings -> Mobile -> Access Point Names.
RIL gets broken after switching airplane mode or modem off/on.
Mobile data might stop working after making or receiving phone calls. Toggle Mobile Data from the settings off/on.
Mobile data quick toggle doesn't work.
Bluetooth can be used via the terminal using bluetoothctl command or using blueman sudo apt install blueman but does not work via the settings app.
GPS works partially via Epiphany (tested with open street map).
Signal strenght is reported at 1% but Mobile data and calls work just fine.
Anything related to cameras do not work it is a global issue across all devices, it does however work in Waydroid.
Changing audio to speaker in calls does not work on dandelion but works on angelica.
When a headphone is plugged in audio output must be changed manually in the settings.
Dual SIM functionality is currently not implemented in Phosh so only one SIM works at the moment.
Mobile hotspot does not work.
Final notes​
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support​
Device specific telegram group: @ut_angelica.
Droidian telegram group: @DroidianLinux.
All the sources are available at
Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
All repositories related to Droidian on Redmi 9A/9AT and Redmi 9C/9C NFC (MT6765/MT6762) - Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
github.com
Attached images are from different devices but the interface looks and acts the same.

will it work on redmi 9c nfc ?

skrepka287 said:
will it work on redmi 9c nfc ?
Click to expand...
Click to collapse
Not tested

FakeShell said:
Not tested
Click to expand...
Click to collapse
Ok

It looks very promising. Isn't this something similar to Ubuntu Touch? I'd love to set this rom as my daily driver, but the bug list and its seriousness is way too much for a daily driver phone. I will, however, try it as a tester. Nice work though!

i trying it on my device rn, will give some responses for the system later.
<edit>
i just already install it on my device i trying the wifi is working perfectly and can play youtube video (via firefox) normally at 320p resolution (sorry but i just doing some slight test here.)
the DE just slower (remember, this is a freshly ported linux to for this device / Redmi 9C angelica)
but the main problem is when i try to lock the phone as usual, the display not showing anything. then forcing the phone for rebooting it sometime not help, just showing a white blank screen but the device gives a response when i pressing volume buttons (except if the device stuck at redmi logo), and i can look around for errors / problems (maybe) using "dmesg -w" command from ssh via putty.
i attach some photos where the device (under laptop's display) stuck at blank white display after reboot, and the device can comunicate via putty (the usb connection managed to be an RNDIS device when connected to the laptop)

Hanhan.i7 said:
i trying it on my device rn, will give some responses for the system later.
<edit>
i just already install it on my device i trying the wifi is working perfectly and can play youtube video (via firefox) normally at 320p resolution (sorry but i just doing some slight test here.)
the DE just slower (remember, this is a freshly ported linux to for this device / Redmi 9C angelica)
but the main problem is when i try to lock the phone as usual, the display not showing anything. then forcing the phone for rebooting it sometime not help, just showing a white blank screen but the device gives a response when i pressing volume buttons (except if the device stuck at redmi logo), and i can look around for errors / problems (maybe) using "dmesg -w" command from ssh via putty.
i attach some photos where the device (under laptop's display) stuck at blank white display after reboot, and the device can comunicate via putty (the usb connection managed to be an RNDIS device when connected to the laptop)
Click to expand...
Click to collapse
This is a known issue with droidian on MTK devices
Screen touching and power button not work on Dandelion · Issue #1 · droidian-mt6765/adaptation-droidian-garden
Hi @FakeShell: Thanks for your porting Droidian to Redmi 9A (Dandelion), is amzing! I followed the guide and got it running successfully! I'm having some problems with the touch screen and power bu...
github.com

skrepka287 said:
will it work on redmi 9c nfc ?
Click to expand...
Click to collapse
hello i doing exacly like in solution but it wont boot ;/ dont work on redmi 9c NFC Angelican

Not tested on angelican
only dandelion and angelica

FakeShell said:
View attachment 5665903​Requirements​
Android 10 firmware for your device:
Redmi 9A dandelion: LINK.
Redmi 9C angelica: LINK.
Dandelion​
Download the latest rootfs: droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip.
Download the adaptation package: adaptation-droidian-garden.zip.
Download boot-dandelion.img, dtbo-dandelion.img, vbmeta-dandelion.img.
Download our customized version of OrangeFox recovery OrangeFox-R11-garden-droidian.img
Angelica​
Download the latest rootfs: droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip.
Download the adaptation package: adaptation-droidian-garden.zip.
Download boot-dandelion.img, dtbo-dandelion.img, vbmeta-dandelion.img.
Download our customized version of OrangeFox recovery OrangeFox-R11-garden-droidian.img
Dandelion installation​
Flash boot-dandelion.img: fastboot flash boot boot-dandelion.img.
Flash dtbo-dandelion.img: fastboot flash dtbo dtbo-dandelion.img.
Flash vbmeta-dandelion.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-dandelion.img.
Flash OrangeFox-R11-garden-droidian.img: fastboot flash recovery OrangeFox-R11-garden-droidian.img.
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip: adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip
Go into sideload mode and sideload adaptation-droidian-garden.zip: adb sideload adaptation-droidian-garden.zip
Now boot into your device.
If for some reason sideload or recovery did not work out for you should try my second installation method:
Download the adaptation script (not the adaptation package): [adaptation-garden-script.zip] (https://garden.bardia.tech/adaptation-garden-script.zip).
Download PBRP: [PBRP-3.1.0.img] (https://garden.bardia.tech/PBRP-3.1.0.img)
Flash PBRP-3.1.0.img: fastboot flash recovery PBRP-3.1.0.img.
Now boot into recovery
Now extract adaptation-garden-script.zip on your PC/Laptop and push it to your device: adb push adaptation-garden-script /tmp
Change directory to /tmp and run the script: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Angelica installation​
Flash boot-angelica.img: fastboot flash boot boot-angelica.img.
Flash dtbo-angelica.img: fastboot flash dtbo dtbo-angelica.img.
Flash vbmeta-dandelion.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img.
Flash OrangeFox-R11-garden-droidian.img: fastboot flash recovery OrangeFox-R11-garden-droidian.img.
Format userdata as ext4 from inside the recovery or via fastboot: fastboot format:ext4 userdata.
Now boot into recovery.
Go into sideload mode and sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip: adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api29-armhf-nightly_XXXXXXXX.zip
Go into sideload mode and sideload adaptation-droidian-garden.zip: adb sideload adaptation-droidian-garden.zip
Now boot into your device.
If for some reason sideload or recovery did not work out for you should try my second installation method:
Download the adaptation script (not the adaptation package): [adaptation-garden-script.zip] (https://garden.bardia.tech/adaptation-garden-script.zip).
Download PBRP: [PBRP-3.1.0.img] (https://garden.bardia.tech/PBRP-3.1.0.img)
Flash PBRP-3.1.0.img: fastboot flash recovery PBRP-3.1.0.img.
Now boot into recovery
Now extract adaptation-garden-script.zip on your PC/Laptop and push it to your device: adb push adaptation-garden-script /tmp
Change directory to /tmp and run the script: cd /tmp/adaptation-garden-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Notes​
The default password is 1234.
Xiaomi has not updated their kernel source tree and as a result some models of 9A and 9C have non functional display panels with our kernel.
Droidian GSIs are experimental! Bugs and missing features are expected.
List of working things can be found at https://garden.bardia.tech
Bugs​
Mobile data needs an APN to be set up from Settings -> Mobile -> Acess Point Names.
RIL gets broken after switching airplane mode or modem off/on.
Mobile data might stop working after making or recieving phone calls. Toggle Mobile Data from the settins off/on.
Mobile data quick toggle doesn't work.
Bluetooth can be used via the terminal using bluetoothctl command or using blueman sudo apt install blueman but does not work via the settings app.
GPS works partially via Epiphany (tested with open street map).
Signal strengh is reported at 1% but Mobile data and calls work just fine.
Anything related to cameras do not work it is a global issue across all devices, it does however work in Waydroid which is currently not available on angelica and dandelion.
Changing audio to speaker in calls does not work on dandelion but works on angelica.
When a headphone is plugged in audio output must be changed manually in the settings.
Dual SIM functionality is currently not implemented in Phosh so only one SIM works at the moment.
Just like bluetooth, hotspot does not work from settings either and has to be used from a GUI application (such as the default advanced network app) or from terminal
Flashlight can be used via the desktop icons only.
Final notes​
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support​
Device specific telegram group: @ut_angelica.
Droidian telegram group: @DroidianLinux.
All the sources are available at
Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
All repositories related to Droidian on Redmi 9A/9AT and Redmi 9C/9C NFC (MT6765/MT6762) - Droidian for Redmi 9A/9AT and Redmi 9C/9C NFC
github.com
Click to expand...
Click to collapse
Hello
I can't get the OS to work on my device. Please help.
Device Name: Xiaomi Redmi 9C Angelica prep
Initial Process Completed
- Switched device to developer mode
- Rooted device
- Fastbooted device
- Downloaded and setup installation kit/packages
Commands and Results
>fastboot flash boot boot-angelica.img
Sending 'boot' (25000 KB) OKAY [ 0.692s]
Writing 'boot' OKAY [ 0.326s]
Finished. Total time: 1.130s
>fastboot flash dtbo dtbo-angelica.img
Sending 'dtbo' (115 KB) OKAY [ 0.009s]
Writing 'dtbo' OKAY [ 0.006s]
Finished. Total time: 0.019s
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.006s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.014s
>fastboot flash recovery OrangeFox-R11-garden-droidian.img
Sending 'recovery' (65536 KB) OKAY [ 1.962s]
Writing 'recovery' OKAY [ 0.846s]
Finished. Total time: 2.813s
>fastboot format:ext4 userdata
Warning: userdata type is f2fs, but ext4 was requested for formatting.
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
>fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.113s]
Finished. Total time: 0.117s
I booted into recovery. Device booted OrangeFox successfully.
I initiated sideload.
>adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip
serving: 'droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip' (~38%) adb: failed to read command: No error
Device booted up, showed Redmi logo. A day later ther device is still at the Redmi logo.
--- sideload fails a 38% everytime. Even if I use the arm64 droidian image.
--- tried the alternative method. It doesn't work as well.
Please assist anyone. If you require logs or details, let me know where to locate them or how to generate them and I will post them.

MarvinG_88 said:
Hello
I can't get the OS to work on my device. Please help.
Device Name: Xiaomi Redmi 9C Angelica prep
Initial Process Completed
- Switched device to developer mode
- Rooted device
- Fastbooted device
- Downloaded and setup installation kit/packages
Commands and Results
>fastboot flash boot boot-angelica.img
Sending 'boot' (25000 KB) OKAY [ 0.692s]
Writing 'boot' OKAY [ 0.326s]
Finished. Total time: 1.130s
>fastboot flash dtbo dtbo-angelica.img
Sending 'dtbo' (115 KB) OKAY [ 0.009s]
Writing 'dtbo' OKAY [ 0.006s]
Finished. Total time: 0.019s
>fastboot --disable-verity --disable-verification flash vbmeta vbmeta-angelica.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.006s]
Writing 'vbmeta' OKAY [ 0.002s]
Finished. Total time: 0.014s
>fastboot flash recovery OrangeFox-R11-garden-droidian.img
Sending 'recovery' (65536 KB) OKAY [ 1.962s]
Writing 'recovery' OKAY [ 0.846s]
Finished. Total time: 2.813s
>fastboot format:ext4 userdata
Warning: userdata type is f2fs, but ext4 was requested for formatting.
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
>fastboot erase userdata
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.113s]
Finished. Total time: 0.117s
I booted into recovery. Device booted OrangeFox successfully.
I initiated sideload.
>adb sideload droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip
serving: 'droidian-OFFICIAL-phosh-phone-rootfs-api30-armhf-nightly_20220822.zip' (~38%) adb: failed to read command: No error
Device booted up, showed Redmi logo. A day later ther device is still at the Redmi logo.
--- sideload fails a 38% everytime. Even if I use the arm64 droidian image.
--- tried the alternative method. It doesn't work as well.
Please assist anyone. If you require logs or details, let me know where to locate them or how to generate them and I will post them.
Click to expand...
Click to collapse
hey
try another recovery such as pbrp. also make sure you use armhf and not arm64 and it must be api29 not api30 (look in the image name)
make sure to also reflash stock a10 before even starting the process

FakeShell said:
hey
try another recovery such as pbrp. also make sure you use armhf and not arm64 and it must be api29 not api30 (look in the image name)
make sure to also reflash stock a10 before even starting the process
Click to expand...
Click to collapse
pbrp worked . Thanks for the guidance!

Hi, I have successfully installed Droidian on my device but I have run on these issues:
- Landscape is broken (it turns on landscape but register touches in wrong positions) and because of that I have to use portrait all times
- Sim card not recognized, so no calls and texts
- Sometimes scrolling is slow on some apps
What I need to do to solve these problems? I really want to use real Linux on my phone. It is a Redmi 9C NFC

Mario6w891 said:
Hi, I have successfully installed Droidian on my device but I have run on these issues:
- Landscape is broken (it turns on landscape but register touches in wrong positions) and because of that I have to use portrait all times
- Sim card not recognized, so no calls and texts
- Sometimes scrolling is slow on some apps
What I need to do to solve these problems? I really want to use real Linux on my phone
Click to expand...
Click to collapse
Landscape issue is present in a few other mediatek devices as well (there was also a touch issue on all mediateks which we fixed) no fix for that yet
Check which slot your simcard is in and change it in /etc/ofono/ril_subscription.conf
change the values ril_0 to ril_1 and slot1 to slot2
systemctl restart ofono ofono2mm
you also have to set your apn settings manually in gnome control center/settings app
its a low end device and mediateks were always in the slower end on linux so you will experience slow downs nothing we can do

Thank you, Sim works now! But all of my contacts are gone now. Shouldn't I ejected the Sim card before flashing the OS?
Also I do not know how to set Access Point settings :/

Mario6w891 said:
Thank you, Sim works now! But all of my contacts are gone now. Shouldn't I ejected the Sim card before flashing the OS?
Also I do not know how to set Access Point settings :/
Click to expand...
Click to collapse
You can find your carriers APN in their website or by just searching the web

Thank you again, but I switched my OS due to missing features I needed like WhatsApp.

xT2213-1 (Austin) Moto G 5G 2022, S1SAS32.47-59-3

Any custom roms like lineage for this device? This is not kiev.

Well, the phone barely launched. It does not have even a year. Since the phone is in order to get another 1 -2 updates, wait for those. Moto can develop faster than any individual dev. If you want lineage or other custom rom, wait a couple more months

Fytdyh said:
Well, the phone barely launched. It does not have even a year. Since the phone is in order to get another 1 -2 updates, wait for those. Moto can develop faster than any individual dev. If you want lineage or other custom rom, wait a couple more months
Click to expand...
Click to collapse
I tried using a stock firmware and patched magisk but when I booted up the phone I got this

gr3uh said:
I tried using a stock firmware and patched magisk but when I booted up the phone I got this
Click to expand...
Click to collapse
{
"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"
}

You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked.

Fytdyh said:
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked. .
Click to expand...
Click to collapse
I think I used the wrong firmware possibly

Fytdyh said:
You cannot bypass that. That carrier lock is in place to ensure you won't sell the device as something else. You would need to talk to your carrier and pay to get it unlocked.
Click to expand...
Click to collapse
Makes no sense since I was perfectly able to unlock the bootloader using Motorola's official guide.

I recommend posting your questions here :
https://forum.xda-developers.com/t/...noob-friendly.2257421/page-2453#post-87357675
Do say what you did, what you flashed. Everyone can help you faster if you are concise and say what did you flash or did to that device. Whenever you try something, write it down.

mine did that too and i just kept trying different sim cards untill i found one that worked and it unlocked it

Hi all, I have a couple questions about this:
My ultimate goal is to get a custom firmware on this (Lineage). I have seen a few threads floating around here, recommending an alternate method for rooting the device, and offering a link to the stock firmware.
However, even if this is successful, I will end up with a rooted, stock-Android phone at the end of it, and since there's still no Lineage release for this phone (or any other alternate firmare, from what I can tell), this effort is not going to get me any closer to a custom ROM. Am I understanding this correctly?
If I'm understanding point 1 correctly, then I need to decide whether to keep this phone, or return it. If a custom OS never becomes available, I don't want the phone. Even in github, there's no indication I could see that Austin is even under development.
However, if this phone is likely to end up with a LineageOS version, I'll just wait a few months. For those of you who spend more time on XDA than I do, how likely is it that this will get a release candidate?
Thanks for your help!

3×5 said:
Hi all, I have a couple questions about this:
My ultimate goal is to get a custom firmware on this (Lineage). I have seen a few threads floating around here, recommending an alternate method for rooting the device, and offering a link to the stock firmware.
However, even if this is successful, I will end up with a rooted, stock-Android phone at the end of it, and since there's still no Lineage release for this phone (or any other alternate firmare, from what I can tell), this effort is not going to get me any closer to a custom ROM. Am I understanding this correctly?
If I'm understanding point 1 correctly, then I need to decide whether to keep this phone, or return it. If a custom OS never becomes available, I don't want the phone. Even in github, there's no indication I could see that Austin is even under development.
However, if this phone is likely to end up with a LineageOS version, I'll just wait a few months. For those of you who spend more time on XDA than I do, how likely is it that this will get a release candidate?
Thanks for your help!
Click to expand...
Click to collapse
I've been told there will never be any progress on custom roms and firmware for this device since it is mediatek and mediatek is locked down their binaries making it hard for people to make custom rom. That being said you can try porting your own twrp or flashing a GSI.

KParsons0697 said:
mine did that too and i just kept trying different sim cards untill i found one that worked and it unlocked it
Click to expand...
Click to collapse
My phone I bought it from a carrier and it was locked until payed off, paid it and waited a few days and it worked. Rooting this device was easy, just wish rom development would come sometime. I hear android 13 should be coming to this device around the beginning of Q2 of 2023

@gr3uh, thanks for the reply. I could try a GSI, but really my goal is to have an open-as-possible, de-Googled phone. I don't even really care about MicroG, or any of this. Even with no services at all, I can use Google Maps in a browser.
I assume if I install the stock firmware from lolinet, it'll have all the Google Play services. Will the phone also be rooter at that point? Or do I have to also root the phone, and then manually remove all the play services?
The big picture question is this: what's the simplest route to me De-Googling this phone?
Bonus question: why is the stock firmware hosted on a site called 'lolinet'? Maybe I don't want to know...

Alright, here's an update on my progress:
I downloaded a Lineage GSI image from Andy Yan. His site said to install an app called 'Treble Info' to get device information. I did this and got the version that matched this device: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
(b means "AB", i.e. system-as-root. VNDKLITE = Read/Write Super partition. Treble info said VNDKLITE was enabled on this device).
I restarted in fastboot mode and ran
Code:
fastboot erase system
and got:
Code:
erasing 'system_b'...
OKAY [ 0.054s]
Then I ran:
Code:
fastboot -u flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
and got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164341876 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
OKAY [ 9.599s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
So then I downloaded an empty vbmeta.img file, and flashed that:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That appeared to work, because I thought my issue might be that dm-verity was enabled. However, I think the real issue is that I flashed this wrong, because I was looking at a tutorial that didn't apply to a system with a super partition. So my hope is that I can still flash my GSI image to the super partition, but I'm not totally sure how to do this. It might be as simple as
Code:
fastboot flash super lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
But I don't want to make things worse. At this point, my system partition is corrupted. The first time I tried to flash system I got "no such device", and the second time I got
Code:
(bootloader) Invalid partition name system
Anyway, I can only boot into fastboot mode. I do have that stock ROM from lolinet, so I could try flashing the super partition, chunk by chunk. There are 26 sparsechunks. Maybe this would get me back to square 1, but I'd rather press forward at this point, if possible, and try to get this GSI image flashed.

I should also point out that when I boot into fastbootd on the phone, it says 'Secure boot - yes' even though I flashed that empty vbmeta image and got:
Code:
target reported max download size of 268435456 bytes
sending 'vbmeta_b' (4 KB)...
OKAY [ 0.000s]
writing 'vbmeta_b'...
OKAY [ 0.073s]
finished. total time: 0.074s

3×5 said:
Alright, here's an update on my progress:
I downloaded a Lineage GSI image from Andy Yan. His site said to install an app called 'Treble Info' to get device information. I did this and got the version that matched this device: lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
(b means "AB", i.e. system-as-root. VNDKLITE = Read/Write Super partition. Treble info said VNDKLITE was enabled on this device).
I restarted in fastboot mode and ran
Code:
fastboot erase system
and got:
Code:
erasing 'system_b'...
OKAY [ 0.054s]
Then I ran:
Code:
fastboot -u flash system lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
and got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 164341876 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 432773236 is not a multiple of the block size 4096
OKAY [ 9.599s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
So then I downloaded an empty vbmeta.img file, and flashed that:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
That appeared to work, because I thought my issue might be that dm-verity was enabled. However, I think the real issue is that I flashed this wrong, because I was looking at a tutorial that didn't apply to a system with a super partition. So my hope is that I can still flash my GSI image to the super partition, but I'm not totally sure how to do this. It might be as simple as
Code:
fastboot flash super lineage-20.0-20230115-UNOFFICIAL-arm64_bvS-vndklite.img.xz
But I don't want to make things worse. At this point, my system partition is corrupted. The first time I tried to flash system I got "no such device", and the second time I got
Code:
(bootloader) Invalid partition name system
Anyway, I can only boot into fastboot mode. I do have that stock ROM from lolinet, so I could try flashing the super partition, chunk by chunk. There are 26 sparsechunks. Maybe this would get me back to square 1, but I'd rather press forward at this point, if possible, and try to get this GSI image flashed.
Click to expand...
Click to collapse
There should be a batch file in the zip you can use to flash the dynamic partition covers everything just edit it to fit your need. And run as betch

Thanks for the reply, but the link in my post is just to a .img.xz file. It doesn't have any zip and no "batch/betch" file (I assume you meant bash?)

3×5 said:
Thanks for the reply, but the link in my post is just to a .img.xz file. It doesn't have any zip and no "batch/betch" file (I assume you meant bash?)
Click to expand...
Click to collapse
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.

radosomalo said:
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
Click to expand...
Click to collapse
Thanks for the clarification. Unfortunately, my image is just an img.xz file. There's no .bat script and no zip.
I ran fastboot getvar current-slot and it says 'current-slot: b'. Then I ran fastboot flash system_b imagefile.img.xz and I got:
Code:
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 165282916 is not a multiple of the block size 4096
sending sparse 'system_b' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 433714276 is not a multiple of the block size 4096
OKAY [ 9.401s]
writing 'system_b' 1/3...
FAILED (status read failed (No such device))
finished. total time: 14.558s
So basically the same problem as before. I tried running 'fastboot delete-logical-partition product_b' and got:
Code:
fastboot: usage: unknown command delete-logical-partition
I could try 'fastboot flash super imagefile.img.xz' but I don't know if I'm supposed to delete super first, and I don't want to make things worse. So any advice would be appreciated.

radosomalo said:
.bat or batch is a file that contains a compiled list or a batch of commands that can run the commands in chronological order so you don't have any error and it makes the installation data redundant. It's really a helpful tool that automates workflow.
Click to expand...
Click to collapse
Alright, I was able to flash the GSI ROM, but it didn't work. My phone thinks the OS is corrupted. I think my only choice now is to go back to my stock ROM. I tried to flash the super partition but running
Code:
./fastboot flash super ../super.img_sparsechunk.0
and it did this through sparsechunk 26. Then I rebooted and I still have no OS.
Now this stock ROM does not have a .bat file, but it does have flashfile.xml. Is there any way I can use this to automate the flashing process? At this point, I'm thinking I'm going to have to flash every partition.
Related question: In the flashfile, it specifies partitions as logo_a, vbmeta_system_a, etc. But when I run '
fastboot getvar current-slot' it says my current slot is 'b'. So should I replace every instance of _a with _b?