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

[Q&A] [ROM] [5.0.2] [AOSP Grogg's Way]

Q&A for [ROM] [5.0.2] [AOSP Grogg's Way]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [5.0.2] [AOSP Grogg's Way]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

celkon mobile A119Q
Can i use this rom for my mobile celkon a119q
if yes how can i install it

samarjitt said:
Can i use this rom for my mobile celkon a119q
if yes how can i install it
Click to expand...
Click to collapse
You're in the Nexus 5 section of XDA-Developers and this thread is dedicated to the Nexus 5 only. If you want to find ROMs for your Mobile Celkon A119Q try searching this device in the forums. Maybe you've got luck

Tried in Multirom for my Nexus 5. Not going to the next stage from Bootanimation
Any solution?

Is it possible to install any customed kernel?
Grogg, I just install your ROM.
It works well but I need some features in another customed kernel.
So Is it possible to install any customed kernel into your ROM?
Thanks

Problem after Grogg's way installation
Hi to all,
i'm new on this forum; i have a Nexus 5 with the official rom Lollipop 5.0.1 .
i've tried to install Grogg's way with TWRP and it worked fine, but after reboot i don't have gsm signal.
if i try to entry in settings-More-Cellular Networks it crashes; if i try to dial, it crashes.
Can you help me?
Thanks very much

shmshd12 said:
Tried in Multirom for my Nexus 5. Not going to the next stage from Bootanimation
Any solution?
Click to expand...
Click to collapse
I do not use multirom. Some users report that it works and others have issues. Maybe something to address in a multirom thread.
pongkiat said:
Grogg, I just install your ROM.
It works well but I need some features in another customed kernel.
So Is it possible to install any customed kernel into your ROM?
Thanks
Click to expand...
Click to collapse
I personally use elementalx. Works great!
Monster84 said:
Hi to all,
i'm new on this forum; i have a Nexus 5 with the official rom Lollipop 5.0.1 .
i've tried to install Grogg's way with TWRP and it worked fine, but after reboot i don't have gsm signal.
if i try to entry in settings-More-Cellular Networks it crashes; if i try to dial, it crashes.
Can you help me?
Thanks very much
Click to expand...
Click to collapse
Start with booting in safe mode to see if issues persist. If so, then factory reset. The ROM is 100% stable.

GROGG88 said:
I personally use elementalx. Works great!
Click to expand...
Click to collapse
Thanks
I'm also prefer elementalx.

GROGG88 said:
Back it all up, fastboot flash the factory image, boot, fastboot flash recovery, flash ROM, and restore media after initial setup.
That is all I have to say about that...
Click to expand...
Click to collapse
I can't go straight from stock 4.4.4 to your 5.0.2 ROM?

GROGG88 said:
Back it all up, fastboot flash the factory image, boot, fastboot flash recovery, flash ROM, and restore media after initial setup.
That is all I have to say about that...
Click to expand...
Click to collapse
But for going from stock 4.4.4 rooted -> 5.0.1(rooted), can I just flash the rom from here 1) http://www.androidrootz.com/2014/12/stock-android-501-lollipop-rom-for.html after wiping with no problem, or would I still have to fastboot flash the factory image found here 2) https://dl.google.com/dl/android/aosp/hammerhead-lrx22c-factory-0f9eda1b.tgz
OR
Can I simply flash the OTA found here 3) http://android.clients.google.com/p...ed-hammerhead-LRX22C-from-KTU84P.6dadaf47.zip

GROGG88 said:
Look at the bottom line of the post you have now quoted twice.
I have shared with you the most failsafe method. It is not the only way, but it is the only way I recommend.
If you have further questions regarding upgrading I would recommend that you run a search on the forum. There are already many threads/tutorials regarding it, but this is not one of them.
Click to expand...
Click to collapse
Mann...I guess just upgrading from 4.4.4 to 5.0.x isn't as simple as just taking x file and flash it, but rather a specific file to go that route.
Okay, so after downloading the FactoryImage.tgz, no need to rename the extension, but fastboot flash the .TGZ file?

GROGG88 said:
I am beginning to feel like you are trolling...
{
"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"
}
Click to expand...
Click to collapse
What? No! I'm not..I'm not trying to troll the thread here...anywhale, technically when you say "fastboot flash the factory image", what you're saying is to unzip the content in the tgz file and double clicking the .BAT file, right?

Okay, so I just finished flashing via this route http://www.talkandroid.com/guides/b...-lollipop-factory-image-on-your-nexus-device/
Inside there was the .bat file, went the route of removing the "-w", now I'm thinking if I should reflash, but keep that "-w" in the line in that .bat file?

Is it normal for the factory image to contain 2 phone apps and 2 photos app?
edit: so, i've tried fastboot flashing again, this time with the "-w" left in, and these are the results:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows\system32>cd\
C:\>cd androidsdk/platform-tools
C:\androidsdk\platform-tools>flash-all
sending 'bootloader' (2579 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
OKAY [ 0.466s]
finished. total time: 0.670s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (45521 KB)...
OKAY [ 1.648s]
writing 'radio'...
OKAY [ 3.116s]
finished. total time: 4.765s
rebooting into bootloader...
OKAY [ -0.000s]
finished. total time: -0.000s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12d
Baseband Version.....: M8974A-2.0.50.2.22
Serial Number........: 03518af7216116ed
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.085s]
checking version-baseband...
OKAY [ 0.095s]
sending 'boot' (8852 KB)...
OKAY [ 0.705s]
writing 'boot'...
OKAY [ 0.768s]
sending 'recovery' (9552 KB)...
OKAY [ 0.577s]
writing 'recovery'...
OKAY [ 0.785s]
sending 'system' (981472 KB)...
OKAY [ 33.217s]
writing 'system'...
OKAY [ 66.624s]
erasing 'userdata'...
OKAY [ 14.930s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 125.346s
Press any key to exit...

What happened to the light notifications on screen lock?
Hi,
First of all let me say that this is my favorite ROM, so thank you for your hard work.
Now I really miss one feature that was lost somewhere between the 12th of March release and this last one from 16th.
I had notifications showing up on the locked screen in a very light way, but the screen would wake up slightly and show them. Was there a reason for removing this feature? How can I get it back without having to flash the version from 12th of March.

rinatdasaev said:
Hi,
First of all let me say that this is my favorite ROM, so thank you for your hard work.
Now I really miss one feature that was lost somewhere between the 12th of March release and this last one from 16th.
I had notifications showing up on the locked screen in a very light way, but the screen would wake up slightly and show them. Was there a reason for removing this feature? How can I get it back without having to flash the version from 12th of March.
Click to expand...
Click to collapse
The removal and reasoning was listed in the changelog. You can add it back by reverting the commit from my source and compiling a new build.

About update rom with new version
Hello everyone, I installed this rom and now I saw that there is a new version, in the instructions for the flash, it does not say how to do the update, it would be better to add, however, I will wipe cache and Dalvik from TWRP although Dalvik is gone and then I will flash the new rom. someone could write to Grogg's?

Trevis72 said:
Hello everyone, I installed this rom and now I saw that there is a new version, in the instructions for the flash, it does not say how to do the update, it would be better to add, however, I will wipe cache and Dalvik from TWRP although Dalvik is gone and then I will flash the new rom. someone could write to Grogg's?
Click to expand...
Click to collapse
If a full wipe was required I would note it in the changelog.
In the future, if you need to poke someone just throw a mention their way by putting a "@" before their username. ie:
@Trevis72

auto rotate
Great 5.1.1 ROM and very fast, but I'm not seeing where I can get the auto rotate feature to work. Is that included in a patch somewhere or does 5.1.1_r1 fix this? Any help would be appreciated. Thanks!

HuskW said:
Great 5.1.1 ROM and very fast, but I'm not seeing where I can get the auto rotate feature to work. Is that included in a patch somewhere or does 5.1.1_r1 fix this? Any help would be appreciated. Thanks!
Click to expand...
Click to collapse
Quick setting tile or accessibility settings.

[Recovery][Snapdragon][R7S/r7sf] Official TWRP for Oppo R7Sf (3.1.1-0)

Team Win Recovery Project 3.1.1-0
This is for the International Oppo R7S, Snapdragon models only! Do not flash on Mediatek R7Sm models!
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
https://twrp.me/devices/oppor7sf.html
For Official TWRP Changelog see Official TWRP News page:
https://twrp.me/
Old changelog listing:
CHANGELOG for 3.0.2-2:
-Fix subpartition restore bug (ex: EFS)
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords).
This fixes decrypt of full device encryption on devices that support decrypt.
This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese
won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_oppo_r7sf (master)
Thanks! & Contributors!
My wife for her patience love you baby!
Team Win, especially Dees-Troys, MSF, Captain_Throwback
Most of all! Uberlaggydarwin , without you this would not have been possible
As promised I have created a Guide on how to install TWRP permanently on the Oppo R7S. It is attached. See below!
Update: Updated Guide to V3 due to TWRP Update and minor fixes in the Guide.
Counter:
GuideV1.pdf = ~1000 Downloads
GuideV2.pdf = 3700 Downloads
GuideV3.pdf = 2918 Downloads

Does it mean that bootloader is unlocked ?

lapocompris said:
Does it mean that bootloader is unlocked ?
Click to expand...
Click to collapse
You are able to unlock the bootloader. For me it's just not possible to enter twrp. Everytime gets overwritten by color os recovery.

OK. Just tested it on the R7 Lite. It works well. Also, as expected, it has soft keys and the hard keys dont work.

Could anyone point me to a step by step instruction on how to install twrp recovery. Sorry for the novice question. Sorry without Root as I'm on latest 5.1.1 and cannot root with oppo tools.

smokeyrider said:
Could anyone point me to a step by step instruction on how to install twrp recovery. Sorry for the novice question. Sorry without Root as I'm on latest 5.1.1 and cannot root with oppo tools.
Click to expand...
Click to collapse
Just head over to the twrp page. The is an instruction written down. Don't forget to unlock your bootloader.

Hi I have followed the instructions. I can "adb reboot bootloader" and get oppo bootloader screen. When I enter "fastboot flash recovery twrp.img" My phone just reboots to normal and the CMD prompt just hangs "waiting for device". Any assistance appreciated. I have latest 5.1.1 Color OS and Windows 10 machine. Thanks.

Ravikirancg said:
OK. Just tested it on the R7 Lite. It works well. Also, as expected, it has soft keys and the hard keys dont work.
Click to expand...
Click to collapse
if you have root and could provide me with the output of the partition details I can build a TWRP specific for the R7 Lite. if it has not been done yet.
I will need information output of:
ls -l /dev/block/bootdevice/by-name/
and
cat /proc/partitions
you will need to have root and switch to "su" in the shell before entering the commands.

celoxocis said:
if you have root and could provide me with the output of the partition details I can build a TWRP specific for the R7 Lite. if it has not been done yet.
I will need information output of:
ls -l /dev/block/bootdevice/by-name/
and
cat /proc/partitions
you will need to have root and switch to "su" in the shell before entering the commands.
Click to expand...
Click to collapse
Your alive celoxocis!
Do you have some news on twrp for ps, your cm build etc?

MacLaughlin said:
Your alive celoxocis!
Do you have some news on twrp for ps, your cm build etc?
Click to expand...
Click to collapse
CM is still work in progress. I will be leaving tomorrow for a one week getaway. After that I plan to write a PDF guide for those with PS how to install TWRP as PS fastboot allows for bootloader unlocking.

celoxocis said:
CM is still work in progress. I will be leaving tomorrow for a one week getaway. After that I plan to write a PDF guide for those with PS how to install TWRP as PS fastboot allows for bootloader unlocking.
Click to expand...
Click to collapse
I thought you need to update the twrp version? The only problem was twrp didn't get recognized and gets overwritten by color os recovery.

MacLaughlin said:
I thought you need to update the twrp version? The only problem was twrp didn't get recognized and gets overwritten by color os recovery.
Click to expand...
Click to collapse
the overwrite of the coloros recovery only happens if the bootloader is not unlocked.

celoxocis said:
the overwrite of the coloros recovery only happens if the bootloader is not unlocked.
Click to expand...
Click to collapse
But I get a success notification...? Fastboot oem unlock

MacLaughlin said:
But I get a success notification...? Fastboot oem unlock
Click to expand...
Click to collapse
if you do "fastboot OEM unlock" twice. does it show "already unlocked" the second time?

celoxocis said:
the overwrite of the coloros recovery only happens if the bootloader is not unlocked.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Device already : unlocked!
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.874s
So the bootloader is unlocked. DTB stands for Device Tree Blob and is a mechanism to pass low level hardware information between bootloader and kernel. So I guess it's just not for PS.
---------- Post added at 07:05 PM ---------- Previous post was at 06:44 PM ----------
celoxocis said:
if you do "fastboot OEM unlock" twice. does it show "already unlocked" the second time?
Click to expand...
Click to collapse
Yes!

MacLaughlin said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) Device already : unlocked!
OKAY [ -0.000s]
finished. total time: -0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.811s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.874s
So the bootloader is unlocked. DTB stands for Device Tree Blob and is a mechanism to pass low level hardware information between bootloader and kernel. So I guess it's just not for PS.
---------- Post added at 07:05 PM ---------- Previous post was at 06:44 PM ----------
Yes!
Click to expand...
Click to collapse
I know what DTB stands for I can see that you are on Project Spectrum. The DTB for PS (Marshmallow) is different than that for ColorOS (Lollipop) there fore it is not working. The offical TWRP is based on ColorOS for the mainstream available. Project Spectrum is only available for beta testers. However "fastboot flash recovery TWRP. IMG" should work. To enter TWRP simply hold down volume-down + power button. When I finish CM I will release a TWRP with kernel+DTB based on Android 6.0!

celoxocis said:
I know what DTB stands for I can see that you are on Project Spectrum. The DTB for PS (Marshmallow) is different than that for ColorOS (Lollipop) there fore it is not working. The offical TWRP is based on ColorOS for the mainstream available. Project Spectrum is only available for beta testers. However "fastboot flash recovery TWRP. IMG" should work. To enter TWRP simply hold down volume-down + power button. When I finish CM I will release a TWRP with kernel+DTB based on Android 6.0!
Click to expand...
Click to collapse
Sadly this is not working. I can flash TWRP but if I try to enter TWRP the screen just stays black. At the moment I'm not able to enter recovery, with key buttons. Also Color Os recovery isn't working at the moment.

just reflash PS and you will have stock recovery back. for now CM and new TWRP for CM is not done.

celoxocis said:
just reflash PS and you will have stock recovery back. for now CM and new TWRP for CM is not done.
Click to expand...
Click to collapse
I will flash stock recovery again. Maybe later on the new version of ps.

celoxocis said:
just reflash PS and you will have stock recovery back. for now CM and new TWRP for CM is not done.
Click to expand...
Click to collapse
Okay stock recovery isn't working anymore as well. The screen just stays black. Got exactly the same error as when flashing twrp. Now I'm without a working recovery ???? maybe I can extract the recovery img. from spectrum. See if this is working.

[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?