[ROM] Droidian Poco X3/NFC [SURYA][KARNA] - Xiaomi Poco X3 NFC ROMs, Kernels, Recoveries, & Ot

{
"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"
}
Droidian for Poco X3/NFC​
ABOUT:
Droidian is a Gnu/Linux Distribution which uses Halium to have compatibility with android smartphones
Website: https://droidian.org
Telegram: Device Group | Global Group
Github: https://github.com/droidian
WHAT WORKS?
- Almost everything
WHAT DOESN'T WORK?
- Audio
- You tell me..
DOWNLOADS:
GSI rootfs
Adaptation package
boot-surya.img
boot-karna.img
dtbo-surya.img
dtbo-karna.img
vbmeta-surya.img
vbmeta-karna.img
Surya Installation:​
Flash boot.img: fastboot flash boot boot-surya.img.
Flash dtbo.img: fastboot flash dtbo dtbo-surya.img.
Flash vbmeta.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-surya.img.
Flash your favorite recovery ( TWRP Recommended ).
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-rootfs-api29gsi-arm64-xxxxxxxx.zip: adb sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip
Now extract adaptation-surya-script.zip on your PC/Laptop and push it to your device: adb push adaptation-surya-script /tmp
Get a shell into your device: adb shell
Change directory to /tmp and run the script: cd /tmp/adaptation-surya-script && chmod +x install.sh && ./install.sh
Now boot into your device.
The first boot will take a while.
Karna Installation:​
Flash boot.img: fastboot flash boot boot-karna.img.
Flash dtbo.img: fastboot flash dtbo dtbo-karna.img.
Flash vbmeta.img: fastboot --disable-verity --disable-verification flash vbmeta vbmeta-karna.img.
Flash your favorite recovery ( TWRP Recommended ).
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-rootfs-api29gsi-arm64-xxxxxxxx.zip: adb sideload droidian-rootfs-api29gsi-arm64-xxxxxxxx.zip
Now extract adaptation-surya-script.zip on your PC/Laptop and push it to your device: adb push adaptation-surya-script /tmp
Get a shell into your device: adb shell
Change directory to /tmp and run the script: cd /tmp/adaptation-surya-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.
If you see a black screen, don't worry it takes a long time to boot.
Droidian GSIs are experimental! Bugs and missing features are expected.
You need this miui build LINK
Thanks to: Barry, Javad and myself for making this rom possible

Does VOIP VoLTE work?

im not being sketchy... when you say audio doesnt work... is that global for the phone or glitchy... or because i so want to use a linux os for my phone but i do still need it to be a phone.... i was hoping you might say that phone calls work but the external speaker has a bug or something.... (praying)

nakedpwr said:
im not being sketchy... when you say audio doesnt work... is that global for the phone or glitchy... or because i so want to use a linux os for my phone but i do still need it to be a phone.... i was hoping you might say that phone calls work but the external speaker has a bug or something.... (praying)
Click to expand...
Click to collapse
Nope, they don't work, you can use something like telegram if your headphones have a microphone

Srilakshmidaran said:
Does VOIP VoLTE work?
Click to expand...
Click to collapse
Doesn't work with any Halium-based distro right now, but some people are working on it

Related

[TUTORIAL LINUX]flash TWRP onto Mediapad 7 Lite

Introduction
Try at own risk
I am a Linux user. Commands are Debian or Ubuntu so you may need to check your package manager for
Linux software for adb if different distro.
If you do not have sudo enabled, then use su - please
On tablet, I use "reboot" by Petrus, as recommended by pogs24ever
I have also installed app= adbd insecure........YMMV
Know that when TWRP is used on removeable sdcard = /sdcard2, you will have a folder
called TWRP so I prefer to rename my image as twrp.img
Credits
Vampirefo for his wonderful help with adb and root id test
pogs24ever for his XDA post for TWRP
AbduL_PT for TWRP for Rockchip
Method
SPOILERS= Click to show content ..... hides images only
Ensure your device is rooted.
{
"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"
}
If your method to root is failing try my method here.
http://forum.xda-developers.com/hua...t-huawei-mediapad-7-lite-alternative-t2996675
On tablet go to system settings and enable USB debugging.
Don't worry about setting media transfer, camera or Hisuite
Download and unpack the TWRP* zip to PC and copy TWRP.img to your home folder.
See Original post for latest download
http://forum.xda-developers.com/showthread.php?t=2693100
Latest download is found at
"Dowload the zip file to this"
Install latest adb to Linux PC
Code:
sudo su
apt-get update
apt-get install android-tools-adb
Do NOT close terminal please
Create udev rule if you don't yet have Huawei mentioned in your rules
Code:
echo 'SUBSYSTEM=="usb", ATTRS{idVendor}=="12d1", MODE="666", GROUP="plugdev" ' > /etc/udev/rules.d/55-huawei.rules
Refresh udev for distros running "service" such as distros like Ubuntu with next command or
bottom line for distros not running service like Debian.
Code:
service udev restart
udevadm control --reload-rules
Now open terminal as local user please.
I prefer to kill the server and restart it with
Code:
adb kill-server
adb devices
If you do not get a device showing a serial number, you can NOT continue.
Recheck you have enabled USB debugging, kill the server and retry adb devices command.
If you are not sure what device your recovery is on, recheck it please with
Code:
adb shell cat /proc/mtd | grep recovery
Now we need to translate that into a device which is /dev/mtd/mtd3
Now we can flash with
Code:
adb push TWRP.img /sdcard2/twrp.img
# above line copies TWRP to removeable sdcard, change sdcard2 if you
don't use one please.
adb shell su -c "dd if=/sdcard2/twrp.img of=/dev/mtd/mtd3"
adb kill-server
Second last command may fail if you don't yet have a rooted device
also if size of bytes of TWRP image is wrong, recheck it please.
6717440 bytes = 6560 Kb = 6.41 Mb which is far less than max size of recovery image.
Before you test, ensure you have a backup of current recovery on removeable sdcard please.
Now use app to reboot into recovery to test.
Nice.. Hope you can find time to port some Cm rom for this.. I stop digging for this device for sometime now.. We have manage to boot on cm9 but it goes bootloop due to kernel compatibility ..
pogs24ever
I have not attempted to port anything yet. Feel free to pm or post here any links you would like me to look at please.
nor have I attempted to cross compile a kernel for this device but I can see Huawei appear to have source here
http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=18334
cheers
just to make it clear in case others drop by via google
this is the mediapad with model showing as S7-931W
and
ro.product.device=hws7930w
2) you can use huawei and 7930 to see one entrant here
https://www.otaupdatecenter.pro/device-lookup
good luck

[MOD][TWRP] Change boot-logo

Just for fun I changed the boot logo of my phone. Since it was such an easy a thing to do, here are some logos you can use.
Just boot in to TWRP and flash.
This is how I did it (in linux):
1. extract an original miui-rom. As long as it has the logo.img, it will do.
2. download the wonderful logo-xiaomi.py-script that penn5 has created.
(Link: https://github.com/penn5/logo-xiaomi)
3. extract the logos from logo.img
$ python3.9 logo-xiaomi.py extract -i logo.img -o output
4. edit (using what ever editor or tool you prefer) the images logo-0.bmp (boot logo for locked phone) and logo-2.bmp (boot logo for unlocked phone). Don't edit either of the other two. They're familiar for people, so they know their phone is either in fastboot mode or has been soft bricked. If you do edit logo-1.bmp and/or logo-3.bmp people will be confused if either something soft bricks the phone, or they try to enter fastboot mode. Yes, if you haven't done so in a while this might confuse you. Leave logo-1.bmp and logo-3.bmp alone.
logo-0.bmp and logo-2.bmp is what you want to edit.
IMPORTANT - remember to save as bmp and in the correct resolution. If you save it in the wrong format and/or the wrong resolution, your phone might not show any boot logo on boot.
5. repack the logo.img-file.
$ python3.9 logo-xiaomi.py -i logo.img -o logo.new.img -a logo-0.bmp -a logo-1.bmp -a logo-2.bmp -a logo-3.bmp
Yes, in that order. The logo-xiaomi-script creates the new image of the files in that order. If you change the order of the logo-files, they'll end up in the wrong order on the new logo.img.
6. either create a flashable zip, using one of my zips, adb push the logo and adb dd it on the logo-partition, or fastboot flash the logo.
fastboot flash logo logo.new.img
OR
adb push logo.new.img /tmp
adb shell dd if=/tmp/logo.new.img of=/dev/block/bootdevice/by-name/logo
This is what the bootlogos I've made look like:
AOSCP
{
"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"
}
G-BLACK
GOOGLE-BLACK
HAVOC
SNAPDRAGON
XIAOMI-EU
Standard is just the standard boot logo, in case you wish to revert back to the normal one.
This is great As soon as I get a little free time I am going to change my boot logo to something personal. Even if it's just for showing off to some friends
@Verbato isn't xiaomi logo in logo.bin not logo.img?
i've try and its gave me error
langithitam said:
@Verbato isn't xiaomi logo in logo.bin not logo.img?
i've try and its gave me error
View attachment 5752805
Click to expand...
Click to collapse
No, it's in logo.img. I did all this in linux (Arch). You might get this to work in WSL. But I'm not guaranteeing anything other than I had no problems under linux (others might not have the same luck).
@Verbato
Sir, can you please make this logo?
device unlocked
twrp and magisk installed

[Help URGENT] Can not find Nexus 9 Radio Image

Hi all,
I been trying to restore my Nexus 9 LTE to latest factory image download from Google Developer, follow the step from this 11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact).
The command I trying to apply though adb tools are:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Click to expand...
Click to collapse
I can't seem able to flash the radio which I read from other forum the "radio" is "vendor.img", below is the screenshot.
My bootloader was using TWRP and I managed to flash the "bootloader" but not the "radio".
Do I missed something? Anyone can help or experience restroing stock image using TWRP?
{
"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"
}
Managed to restored to stock Nexus 9 LTE.
Correct, it seem "vendor.img" contain "radio" for Nexus 9 LTE.
Command that I performed while my Nexus 9 LTE under recovery mode:
fastboot devices
fastboot flash bootloader D:\Downloads\platform-tools\volantisg-n4f27p\image-volantisg-n4f27p\bootloader-flounder-3.50.0.0143.img
fastboot reboot-bootloader
fastboot flash boot D:\Downloads\platform-tools\volantisg-n4f27p\image-volantisg-n4f27p\boot.img
fastboot erase cache
fastboot flash cache D:\Downloads\platform-tools\volantisg-n4f27p\image-volantisg-n4f27p\cache.img
fastboot flash recovery D:\Downloads\platform-tools\volantisg-n4f27p\image-volantisg-n4f27p\recovery.img
fastboot flash system D:\Downloads\platform-tools\volantisg-n4f27p\image-volantisg-n4f27p\system.img
fastboot flash vendor D:\Downloads\platform-tools\volantisg-n4f27p\image-volantisg-n4f27p\vendor.img
Click to expand...
Click to collapse
Reboot back to TWRP recovery and wipe cache and dalvik cache.
Command:
fastboot boot D:\Downloads\platform-tools\twrp-3.6.0_9-0-flounder.img
Click to expand...
Click to collapse

Development [ROM][Redmi Note 10][OFFICIAL][13][TIRAMISU] StatiXOS v6.1

{
"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"
}
StatiXOS for Redmi Note 10 (sunny/mojito)
What is StatiXOS?
StatiXOS is a custom ROM based on the Android Open Source Project aiming to be minimal while providing quality of life improvements and up to date security patches.
Spoiler: Known Issues
None!
Please report anything you run into!
Spoiler: Download StatiXOS Here!
Primary
SourceForge Mirror
Spoiler: How To Flash (Sideload Method)
1. Download recommended fw, ROM zip, boot.img and vendor_boot.img.
2. Boot to bootloader.
3. Run fastboot flash boot boot.img.
4. Run fastboot flash vendor_boot vendor_boot.img.
5. Run fastboot reboot fastboot
6. Unzip the recommended fw
7. Open a terminal inside the firmware-update directory.
8. Flash all .img files with the command syntax being fastboot flash --slot=all partition partition.img.
An example of such can be fastboot flash --slot=all abl abl.img.
Alternatively, you can run the following command:
- If you're on windows: for %i in (*.img) do fastboot flash --slot=all %~ni %i
- If you're on linux: for i in *.img; do fastboot flash --slot=all "${i/.img/}" "$i"
9. Run fastboot reboot recovery.
10.Format Data with the Recovery.
11. Click apply for update.
12. Run adb sideload statix_sunny*
13. Reboot to system.
Spoiler: How To Flash (Fastboot Method)
1. Download recommended fw and ROM zip.
2. Boot to recovery and Format Data.
3. Boot to bootloader
4. Now ensure your drivers are proper. Type in .\fastboot.exe devices. If it shows nothing, it means that your drivers are not proper, google search on how you should fix them as it is out of the scope of this guide. Once you get an output like 2398534953 fastboot, it means that your device is detected.
5. Now, type in .\fastboot.exe update ''path\to\StatiXOS\Build\zip'' (replace path\to\StatiXOS\Build\zip with actual path to the fastboot images zip file) Pro Tip: You can right click and copy the zip and then paste into powershell window. Make sure you paste in between the quotes ' '.
6. It should show some details and start flashing immediately. It will reboot your device automatically to fastbootd mode in Statix Recovery. DO NOT DISCONNECT THE DEVICE DURING THIS PROCESS!
7. Wait till the process finishes, it will reboot the device automatically.
8. Enjoy using StatiXOS on your device!
Spoiler: Stay in touch with our Telegram channels!
Official Chatroom
Official Releases & Announcements Channel
​
Android version: 13
Linux Kernel Version: 4.14.206
Source code: GitHub
Code Review: Gerrit
Changelogs:
- Initial Build
Hey does your build have fixes which enable ANX to work properly?
AaxyatXDA said:
Hey does your build have fixes which enable ANX to work properly?
Click to expand...
Click to collapse
no it does not but you could try it yourself.
Changelogs: (02-14-2023)
- Feb Patch
- Updated blobs from mojito V14.0.1.0.SKGMIXM
- Implemented dt2w sensor
- Fixed dt2w on aod
- Dropped XiaomiParts
- Included Smartspace

Themes / Apps / Mods Degoogle (LeOS-T April 2023 Only ) A13 GSI Run with exFAT SD card supported.

Supported exFAT only 1 Variant
LeOS-T April 2023 Only
============================​
Step to install LeOS-T GSI Variant.
DOWNLOAD--firmware from https://samfw.com/
0. Create patch-recovery for fastbootD
☆☆☆ FastbootD video tutorial : https://m.youtube.com/playlist?list=PLvggR4skCxYzhB3SXxpSx4LvRzGwx9k45
1.Create Magisk_patch
patch 2 files (boot.img ,vbmeta.IMG) with Magisk.
2.Include 3 patched files into one tar called 3in1.tar
Enter into Download Mode.[Tablet]
3.flash Stock firmwares(AP, BL,CP, CSC,) and patched file
(USERDATA 3in1.tar)with Odin.
(Flashing Clean Stock Firmware with Root & Recovery patched)
{
"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"
}
3.1 Reboot with no log-in google account or updated anythings.
3.2 Connect internet.
3.3 Open Developer options.
-Enable OEM unlock
-Enable USB Degugging
-Test Authorizing to your Computer for accessing this tablet.
Code:
adb devices
3.4 Download GSI
and (extract "xxx.img" to platform-tools folder on Computer.
3.flash GSI with fastbootd commands.
Code:
adb reboot fastboot
fastboot erase system
fastboot flash system LeOS-T-VNDKLITE-arm64-bvN.img
# If founded "No spaces to resize partition error"
Code:
fastboot erase product
fastboot resize-logical-partition product 0x0
fastboot getvar all
# (bootloader) partition-sizeroduct:0x0
# FastbootD Menu select
-Enter Recovery
# Recovery Menu select
-Wipe data/Factory reset
confirm
-Reboot system now
------End install GSI-----
**Note: Default Launcher (LeOS Launcher + Neo Launcher) are not suitable for tablet.(lot of bugs) then i try to uses new default AOSP home launcher.
Remove: (if your had RW System)
Code:
adb shell
su
mount -o rw,remount /
rm -R /system/app/Launcher
reboot
​4. CREATE NEW LAUNCHER.
4.1)-Flash Magisk modules. and reboot
4.2)-(1.run"Launcher3QuickStep.apk" 2.run"ThemePicker.apk"
New Pop-up Taskbar Navigation.​(Split screen /MultiTask by float Taskbar navigation.)
(works when Smallest width > 600 dp )
Vertical screen view
Horizontal screen view.
Home Settings
Dev options to open float taskbar menu.
5.Changes Offline Charging behavior. (Testing)
-Copy hw to /sdcard/Download
Code:
adb shell
su
mount -o rw,remount /
cd /sdcard/Download/hw
cp -R *.* /etc/init/hw/
HOWTO CHARGING:
1. Switch On
2. Insert power cable during Screen Locked .
3. Press power On-off button for checks remain battery .
6.List of testing software
FairEmail
Simple Gallery Pro
Nekogram X
Launcher 3
Retro Music
Vega Bobo DSU
file app (tablet view)
reserved. no.1
Update new version without lost your data.
1. Test new update GSI is compatible with current your installation. with Vega Bobo DSU SideLoader. new version 2.03
2. Flash the new update overwritten old GSI by fastbootD. (Dirty Flash)

Categories

Resources