Database Info

CyanogenMod 11.0 for HTC One Mini - m4

CyanogenMod 11.0 is a free, community built distribution of Android 4.4 (KitKat) which greatly extends the capabilities of your phone.
These are nightly builds of CM11.0 for the HTC One Mini.
To hear about the latest updates and changes to CyanogenMod as a whole, please follow +CyanogenMod on Google+!
You can follow h8rift on Google+
You can follow u-ra on Google+​
Device Maintainers:
u-ra and h8rift
Code:
#include
/*
* 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.
*/
Installation Instructions
You must unlock your bootloader or be S-OFF.
You must have a custom recovery installed that allows SELinux.
Download the HTC One Mini build http://download.cyanogenmod.org/?device=m4.
Locate 4.4 Gapps here.
Fully wipe your device from Recovery if you are not coming from CM11.0 already.
Reboot into recovery and install.
Huge thanks:
u-ra - Co-Maintainer and helped plug alot of holes I missed. Great to have him aboard .
intervigil, Flemmard - Great friends that helped with the HTC One Mini.
XDA:DevDB Information
CyanogenMod 11.0 for HTC One Mini - m4, ROM for the HTC One Mini
Contributors
h8rift, u-ra
Source Code: https://github.com/CyanogenMod
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Beta
Created 2013-11-24
Last Updated 2014-11-13

Borrowing this post...

Wow I didn't think I'd see a cm11 rom anytime soon, can't wait to try this rom. What kernel is used?
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
Just seen this is at+t will it work on wwe?

cyberdude020 said:
Wow I didn't think I'd see a cm11 rom anytime soon, can't wait to try this rom. What kernel is used?
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
Just seen this is at+t will it work on wwe?
Click to expand...
Click to collapse
It should. i didn't put any specific AT&T APNs or anything in there.

yeeeah! thanks!
but I'm sorry, I need my phone during the week for the job - cant test it now.

just trying to install this, how do i mount data? when installing the .zip it fails but i'm unsure how to mount. also which type of wipe is required? A reset factory settings or more? (will it delete my external data? thanks

looping
successful install ....but is its looping on HTC screen

@h8rift thanks for giving us official cm
Sent from my HTC One using Tapatalk

That's possibly you haven't flashed boot.img in fastboot I'm guessing

tr1gg3r84 said:
That's possibly you haven't flashed boot.img in fastboot I'm guessing
Click to expand...
Click to collapse
Are we supposed to?. The instruction says install only (with TWRP)

eeter said:
Are we supposed to?. The instruction says install only (with TWRP)
Click to expand...
Click to collapse
Yeah but sense and cm boot.img are different so you will still need to flash boot.img in fastboot for cm

tr1gg3r84 said:
Yeah but sense and cm boot.img are different so you will still need to flash boot.img in fastboot for cm
Click to expand...
Click to collapse
So it should be like this?
You must unlock your bootloader.
You must have a custom recovery installed that allows SELinux (please see here for TWRP with SELinux support for 4.4 KitKat)
Download the HTC One Mini build here.
Locate 4.4 Gapps here.
1 Fully wipe your device from Recovery if you are not coming from CM11.0 already.
2 Reboot into recovery and install. (Unfortunately, you will need to mount /data manually and then go to /data/media/0 to locate the zip files until this recovery gets cleaned up.)
3 Unzip ROM and flash boot.img in fastboot
4 Reboot

eeter said:
Are we supposed to?. The instruction says install only (with TWRP)
Click to expand...
Click to collapse
Take out the boot.img from the zip file and place it in your fastboot folder and fastboot flash boot boot.img then reboot after installing

tr1gg3r84 said:
Take out the boot.img from the zip file and place it in your fastboot folder and fastboot flash boot boot.img then reboot after installing
Click to expand...
Click to collapse
still looping on htc screen
---------- Post added at 07:55 PM ---------- Previous post was at 07:52 PM ----------
when you load a file with "adb pushcm11xxx /data/media/0/...
what happened if I do not have the "0" folder??

How do i mount data? In TWRP or fastboot?

hey,
did someone actually succed in booting it ?
additional question, why flash the twrp recovery, i mean, fastboot boot recovery.img should be ok, no ?
and that would allow to keep OTA update working

As someone that has CM on multiple android devices (Samsung Galaxy Note II, Nexus 4, Nexus 7 & Samsung Galaxy Note 8.0) I would try reflashing, I find that usually the first flash doesn't go well with CM. I just got an HTC One Mini so excited to see this development. I was a little bummed that their was no CM for it ATM.

reubendevries said:
As someone that has CM on multiple android devices (Samsung Galaxy Note II, Nexus 4, Nexus 7 & Samsung Galaxy Note 8.0) I would try reflashing, I find that usually the first flash doesn't go well with CM. I just got an HTC One Mini so excited to see this development. I was a little bummed that their was no CM for it ATM.
Click to expand...
Click to collapse
I tried everything ...This ROM is not working

eeter said:
I tried everything ...This ROM is not working
Click to expand...
Click to collapse
I am willing to try it once they fix speakerphone and wifi. Camera I don't really care if it works or not. Unfortunately the HTC One Mini is currently my daily driver so I can't afford to lose the wifi or speakerphone.

reubendevries said:
I am willing to try it once they fix speakerphone and wifi. Camera I don't really care if it works or not. Unfortunately the HTC One Mini is currently my daily driver so I can't afford to lose the wifi or speakerphone.
Click to expand...
Click to collapse
same for me :crying:

SlimLP for Thea

I will not maintain this rom from now on, since I cant test and there is close to zero interest in this rom for this device.
UNIFIED
Disclaimer
Code:
Your warranty is void. Unless you are from europe xD.
Backup, always!!! I am not responsible for bricked devices,
dead SD cards, you getting fired because the alarm app failed,
thermonuclear war, or anything else.
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. Hard. A lot.
Go into custom recovery
Download the ROM
Put ROM on SDCARD
Go to install and select the rom zip.
Click install and wait.
Hit the Thanks! button (right bottom corner of this post)
Not working:
Tell me!
Thanks: LuK1337 for helping with build errors.
XDA:DevDB Information
SlimLP for Thea, ROM for the Moto G 2015
Contributors
gregor160300, gregor160300
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: SlimLP
Version Information
Status: Testing
Created 2015-06-22
Last Updated 2015-06-22

Mine

Too

Hello, Just tried to flash SlimLP, The flash is OK but When I reboot the phone, it's stuck on the "Unlocked Bootlader" Screen.....
I did a semi-clean flash (just wype system, cache and dalvik before flashed the ROM)
It seems that the Boot.img does not work. I deleted the boot.img and replaced it with the one from CM Rom Zip and now it boots.
EDIT: Endless Bootanimation, Back on CM for now

No GAPPS needed?

I did some tests back home:
- The Zip provided is stucked on "Bootlader Unlocked" screen
- The zip modified with bootimg from CM is stucked on Bootanimation.
Does it run on your phone ?

sossio18 said:
No GAPPS needed?
Click to expand...
Click to collapse
They are not included, so if you want them you flash them

metalmoot said:
I did some tests back home:
- The Zip provided is stucked on "Bootlader Unlocked" screen
- The zip modified with bootimg from CM is stucked on Bootanimation.
Does it run on your phone ?
Click to expand...
Click to collapse
Forgot to mention was going to, but I dont have thea, I do have Titan so I base my roms on commits, they are not tested, but I can see what I can do about it.
Edit: I have a fix for now I think and I would be happy if you tested the fix. Since Thea and Titan use the same kernel, I will provide you with a working boot.img from SlimLP Titan you can then flash that over this SlimLP zip after doing a full clean install. https://drive.google.com/file/d/0By3hc0o4u0zSdGRCOW8wUXZjcHM/view?usp=sharing

Ok I just flashed your .img.
Now the phone boots but soft reboot when it lands on "Starting apps" screen. Thus the screen corners flicker and go red for a few seconds
Good Job by the way but it is not a working ROM yet

metalmoot said:
Ok I just flashed your .img.
Now the phone boots but soft reboot when it lands on "Starting apps" screen. Thus the screen corners flicker and go red for a few seconds
Good Job by the way but it is not a working ROM yet
Click to expand...
Click to collapse
So it now goes further, but still doesnt work, as for the screen I really dont know how to fix that without a test device.
Edit: Red pixels are there because this is a -eng build, usually only for testing, I am building a better zip now.

metalmoot said:
Ok I just flashed your .img.
Now the phone boots but soft reboot when it lands on "Starting apps" screen. Thus the screen corners flicker and go red for a few seconds
Good Job by the way but it is not a working ROM yet
Click to expand...
Click to collapse
New build is up, I would really appreciate it if you could test it, first without flashing custom boot.img and if that doesnt work with custom boot.img

gregor160300 said:
New build is up, I would really appreciate it if you could test it, first without flashing custom boot.img and if that doesnt work with custom boot.img
Click to expand...
Click to collapse
OK Just tested the new build, It boots and works great however I will not stay on SlimLP. I wanted to test because I had a really great Experience with SlimICS and SlimJB back on my Nexus. SLimLP seems good but beside Slimrecent it's no as tweaked as I wanted it to do.
Will continue to test your builds if you are in need
Thanks

metalmoot said:
OK Just tested the new build, It boots and works great however I will not stay on SlimLP. I wanted to test because I had a really great Experience with SlimICS and SlimJB back on my Nexus. SLimLP seems good but beside Slimrecent it's no as tweaked as I wanted it to do.
Will continue to test your builds if you are in need
Thanks
Click to expand...
Click to collapse
Well thanks for testing my builds, is my new build working without custom boot.img, or is the custom boot.img still needed?

gregor160300 said:
Well thanks for testing my builds, is my new build working without custom boot.img, or is the custom boot.img still needed?
Click to expand...
Click to collapse
it works with custom boot.img.
xt1077
---------- Post added at 12:08 PM ---------- Previous post was at 12:03 PM ----------
gregor160300 said:
Well thanks for testing my builds, is my new build working without custom boot.img, or is the custom boot.img still needed?
Click to expand...
Click to collapse
it seems break my ril...

bushibaa said:
it works with custom boot.img.
xt1077
---------- Post added at 12:08 PM ---------- Previous post was at 12:03 PM ----------
it seems break my ril...
Click to expand...
Click to collapse
If custom boot.img is from titan then it's pretty normal to break your RIL XD

LuK1337 said:
If custom boot.img is from titan then it's pretty normal to break your RIL XD
Click to expand...
Click to collapse
It's wired. i can't use cdma card (only carrieroperator service call works, no other call, no sms, no data connection, it shows signal normally) unless insert a wcdma card before. is it ril erro? How could it be normal when inserting a wcdma card...

Build 2 worked without the custom boot.img for me

metalmoot said:
Build 2 worked without the custom boot.img for me
Click to expand...
Click to collapse
Could you confirm if ril works for you and please tell me your modelnumber.

[TWRP] (ish) TWRP 3.2.1 for honor 9 running GSI 8.1 ROMs

lets make this very clear:
I HAVE NOT DEVELOPED THIS, IT WAS LINKED IN ANOTHER FORUM BY ANOTHER MEMBER WHO ALSO DID NOT DEVELOP IT
this is actually developed by a member over at the Chinese website '7to' http://www.7to.cn, so its a recovery based on TWRP 3.2.1 but seems to have its own UI and feature set.
WORKING
Code:
[COLOR="Black"][LIST]
[*]Boots to TWRP!
[*]Can flash images to system (MUST BE ON SD CARD!!!!)
[*]ADB
[*]Mount system R/W
[/LIST][/COLOR]
NOT WORKING
Code:
[COLOR="Black"][LIST]
[*]Decryption
[*]Data backup
[*]Flash from internal storage (since it cant be decrypted)
[/LIST][/COLOR]
I am not responsible if you brick your device, flash with caution and ONLY on an 8.1 GSI where your current TWRP doesn't work.
This does not do anything to capacitive keys, if they work before flashing they will work after flashing
INSTALLATION
'fastboot flash recovery_ramdisk recovery.img
DOWNLOAD
https://drive.google.com/file/d/1RgerdkXY-B-8XV5buloeCyKYrA2B3Bvf/view?usp=sharing
Credit to whoever the creator of this is!​

it boots up with TWRP, but flashing Gapps was failure.
UPDATE: I used Open Gapps, better try Ground Zero GZR Gapps...

TASON42 said:
it boots up with TWRP, but flashing Gapps was failure.
Click to expand...
Click to collapse
GZR apps 180313 works good.

GZR-GaPPs-arm64REv4-Zero-8.1-20180628 worked. thx.
UPDATE: HuRUpdater_0.4, Magisk 16.7 worked.

Flashed a kernel, magisk and xposed with this. Seems to be working great.

olishadyx said:
Flashed a kernel, magisk and xposed with this. Seems to be working great.
Click to expand...
Click to collapse
I haven't flashed anything with this yet, but at least it can do the basic stuff. Also, what kernel did you flash, I know there's the proto8 kernel (or whatever it's called) but I'm not too keen on it.

ambitiousButRubbish said:
I haven't flashed anything with this yet, but at least it can do the basic stuff. Also, what kernel did you flash, I know there's the proto8 kernel (or whatever it's called) but I'm not too keen on it.
Click to expand...
Click to collapse
Proto8 is what I installed. Haven't made my mind up on it yet. Battery drain is definitely worse so far but apparently it takes a few cycles to adapt.

[RECOVERY][3.2.3-0][shark]Unofficial TWRP recovery for BlackShark (Testing)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- Decrypt is not working for now
- Backup still have some problems use it carefully
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot recoveryimgfilename.img" in command line (if you want to have it permanently you should flash the installer)
5. If you will flash the installer and you are stock you need also to flash magisk or your phone will not boot again
6. Enjoy it
How to flash a custom Rom:
Boot twrp
Flash rom
Flash twrp installer
Boot twrp
Wipe data & art cache
Flash magisk
Reboot
Tips:
If you alread have a twrp flashed you can only flash the new installer zip to update your TWRP (remember to flash again magisk or your system will not boot).
If you have some problems with backup, like 255 error or something similar please check this guide: https://forum.xda-developers.com/oneplus-6/how-to/255-error-twrp-backup-restore-999-t3801632
For the Bacups use always "system_image" and "vendor_image" instead of "system" and "vendor".
Download:
TWRP 3.2.3-0 Unofficial by mauronofrio
TWRP 3.2.3-0 Unofficial Installer by mauronofrio
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/mauronofrio/android_device_blackshark_shark
Donations:
Credits:
Thanks to @kanded for the testing
Created 2019-01-23

finally. thanks for the hardworking. i will check if it works or not.

Thank you for your hard work.
Seem this rec was for international version, as it showed SKR-H0 when I connected to the phone to PC.
As for CN ver in which I made the try, it reverses the screen.
To me, the decryption has gone after wiping /data and booting again using fastboot.
Backup was smooth. MTP mount was also great.
Now I'm trying flashing magisk. Will update ASAP
---------- Post added at 08:10 AM ---------- Previous post was at 07:42 AM ----------
Updating
CN version works great with back up and magisk using the TWRP from the OP, just remember to boot into stock recovery to wipe after magisk flashing as I could not reboot successfully from TWRP.
As for installing this rec permanently, I have not tried.
Once more time, thank you.

This is great news! I really love the progress we have made as a community!
Thank you for your hard work, I'll be testing it today
EDIT: tested, here are the problems found so far testing it on a chinese SKR-A0:
- the image on the display is upside down but the touch is right, so navigating the menus requires some effort

loriz said:
This is great news! I really love the progress we have made as a community!
Thank you for your hard work, I'll be testing it today
EDIT: tested, here are the problems found so far testing it on a chinese SKR-A0:
- the image on the display is upside down but the touch is right, so navigating the menus requires some effort
Click to expand...
Click to collapse
If needed i can fix upside down display, but why one version is upside down and the other one not?

mauronofrio said:
If needed i can fix upside down display, but why one version is upside down and the other one not?
Click to expand...
Click to collapse
I got no idea on this actually it works, just the cosmetic issue. I think spending on next release with other issue is better than concentrating on this small one.
Appreciated your work and hope to see the update

ndt192 said:
I got no idea on this actually it works, just the cosmetic issue. I think spending on next release with other issue is better than concentrating on this small one.
Appreciated your work and hope to see the update
Click to expand...
Click to collapse
Test this twrp, if the screen is good and touchscreen works:
https://www.androidfilehost.com/?fid=11410963190603906667

mauronofrio said:
Test this twrp, if the screen is good and touchscreen works:
Click to expand...
Click to collapse
Nothing changed.
The screen is turned upside down as in the first version

Hello guys. I installed TWRP, well, when I tried to put Magisk, something went wrong, and now I can not log in to the system, the boot sign in the system constantly hangs. I can not delete Magisk using magisk uninstaller, it gives an error that I need to mount the system. With TWRP, I can not do this. The section is, well, you can not mount. I need your help, please skip the Boot section from the global version, it may still be possible to start the system.

3gpaBcTByuTe said:
Hello guys. I installed TWRP, well, when I tried to put Magisk, something went wrong, and now I can not log in to the system, the boot sign in the system constantly hangs. I can not delete Magisk using magisk uninstaller, it gives an error that I need to mount the system. With TWRP, I can not do this. The section is, well, you can not mount. I need your help, please skip the Boot section from the global version, it may still be possible to start the system.
Click to expand...
Click to collapse
I think you should:
- wipe data
- install Magisk
- boot into original recovery
- wipe data again from there
- reboot
And you should be able to boot!

loriz said:
I think you should:
- wipe data
- install Magisk
- boot into original recovery
- wipe data again from there
- reboot
And you should be able to boot!
Click to expand...
Click to collapse
Thanks for the answer, well the fact that I do not have the original boot.img (I made a backup system when I already rewrote the original boot(
If you have the opportunity, throw off please original boot.img from global version. I will be very grateful and grateful!

3gpaBcTByuTe said:
Thanks for the answer, well the fact that I do not have the original boot.img (I made a backup system when I already rewrote the original boot(
If you have the opportunity, throw off please original boot.img from global version. I will be very grateful and grateful!
Click to expand...
Click to collapse
If needed i can explain on how to extract the stock boot.img, i have not the black shark so i can't do it by me

mauronofrio said:
If needed i can explain on how to extract the stock boot.img, i have not the black shark so i can't do it by me
Click to expand...
Click to collapse
Write a way to do this. I would be very grateful, there may be people who will want to help me, and I’ll draw out the original boot.img. Maybe I'm not the first, and not the last who will face this situation, and already it will be for all the same as I have an airbag.

3gpaBcTByuTe said:
Hello guys. I installed TWRP, well, when I tried to put Magisk, something went wrong, and now I can not log in to the system, the boot sign in the system constantly hangs. I can not delete Magisk using magisk uninstaller, it gives an error that I need to mount the system. With TWRP, I can not do this. The section is, well, you can not mount. I need your help, please skip the Boot section from the global version, it may still be possible to start the system.
Click to expand...
Click to collapse
i sent you mssg

They threw me the original boot.img from the December update, well, this did not save the system. Permanent reboot of the phone goes on the letter "S". What could be the reason?
http://transfiles.ru/qqpem

thanks for your work . how can i decript???
i´ll wait for the next update thanks!!!!

mauronofrio said:
If needed i can explain on how to extract the stock boot.img, i have not the black shark so i can't do it by me
Click to expand...
Click to collapse
Can you please explain how to extract the stock boot.img? Nice work btw!

After flash magisk I hung up the logo, what should I do now

kanded said:
i sent you mssg
Click to expand...
Click to collapse
Thank you very much Brother !!! You really helped me a lot !!! There would be more people like you in our world, and in this community !!!

3gpaBcTByuTe said:
Thank you very much Brother !!! You really helped me a lot !!! There would be more people like you in our world, and in this community !!!
Click to expand...
Click to collapse
To extract the stock boot, you should boot the twrp and from the pc using adb run these commands (remember if you have already rooted or if you flashed the twrp installer, you have no more the stock boot on your deivce:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/boot.img
adb pull /boot.img <pcpath>
For example in my case to copy it on desktop:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot of=/boot.img
adb pull /boot.img D:\Desktop

Project Treble for Xperia X compact

Project Treble For Xperia X Compact
Based on Sony Open Devices
I am not responsible for bricked devices, dead SD cards,.
Big thanks to Sjll member and his tuto to go treble
Suitable for F5321, A-ONLY GSI ROM​
Required files:
[SODP Kernel version]
All necessary files
[OEM-File]
Download Link
[SYSTEM-File]
Tested with some system gsi files, these work properly :
Pixel experience
/e/
POSP
ArrowOS
[SYSTEM-File WITH FixZygote installed via twrp]
Android Q developer preview
Find all GSI system image here and here
How to go Treble ?
First: Flash recovery
Code:
fastboot flash recovery < Path of recovery.img >
Second: Flash boot image
Code:
fastboot flash boot < Path of boot.img >
Third: Flash vendor file
Code:
fastboot flash cache < Path of vendor.img >
Fourth: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Fifth: Flash a GSI compatible System image (arm64 A-ONLY) and boot !
Code:
fastboot flash system < Path of GSI-System.img >
Look here first for questions resolving Xperia X thread
Source Codes
Sjll
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2020-05-09
Last Updated 2020-05-23

Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.

maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced

maluus said:
Hello mate. It's interesting to see different options come up when we started to think that development for XC come to an end. Thanks for this valuable effort. I want to ask a few things.
1- What is your opinion about dreaded problems with 4.9 kernel like random reboots and some reported Wi-Fi issues (although I don't remember I ever had this) etc.
2- recovery is independent of this setup right? I mean can I use twrp as recovery?
3- I suppose we'll be stuck with this boot.img unless personally build another one with synced sources right?
4-One of your cautions was about dead sd card? Is there a predicted risk or was it a general warning?
Again thanks a lot for this. I think I'll give it a try tomorrow may be.
PS: I also would like to know what to look for compatible GSIs. (I tried Phhs' and some other Android 10 GSIs with zygote and permissiver patches but they didn't past the sony logo. Stuck at sony logo or bootloop)
Update: Question 2 answered. No problem with twrp. Erfan's generic 10 gsi booted with zygote and permisiver patches. But stuck at setup screen.
Click to expand...
Click to collapse
1 - I don't know about these problems, I was with 3.x kernel before but you can rebuild the kernel of your choice (it doesn't take too much time) by changing the .dtsi file corresponding to our device
2 - Yes but do not wipe the cache, as the vendor image is in it
3 - Yes, but it doesn't take too much time to build it, share if you do
4 - Just a general warning, not experienced
Normally I set the selinux to permissive so no need to apply the permissiver patch
PS : sometimes it goes into bootloop but if you reboot it starts like a charm (test that with POSP 10)
PS2 : Mobile network does not work with Q roms, if you success to make it work please share
PS3 : POSP Pie works fine

Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.

bioshp said:
Tell me if I'm thinking of installing Project Treble.
1.Flash all sections through the fastboot?
2.Ask for recovery what is in the link on the github?
3.Ask for a boot link on github?
4.Select vendor.img in the cache section?
5.What to ask for?
6.Select a suitable GSI image and boot again?
If somewhere I am wrong correct me. I'm sorry I'm new to this.
Click to expand...
Click to collapse
You can get twrp as recovery but do not wipe cache, as vendor img is flashed in it

Good news that /e/ is working correctly, I was about to try to build a e variant on Chippa's build.
I do have one question. Really new to trebble.
If we wanna root it, we apply usual procedure*? flash the root zip(magisk) in recovery

This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?

can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP

zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Xperia UI GSI also does not start for me. What could be?

zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.

zetchonok said:
can't boot any FW excluding /e/, but /e/ don't satisfy me at all.
bootloops miui
bootloops PE
bootloops native xperia gsi
anybody know's why?
all of needed img's are flashed: boot, vendor, oem. Only recovery left TWRP
Click to expand...
Click to collapse
Try to flash userdata also

bioshp said:
Xperia UI GSI also does not start for me. What could be?
Click to expand...
Click to collapse
Q or Pie ROM ?

maluus said:
I tried a lot of them to both android 9 and 10 only /e/ boots and works as 9. For the 10 erfans boots but it includes gapps and that stucks at setup. You can leave it as it s but didn't thoroughly tested it.
Click to expand...
Click to collapse
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)

betacrypt said:
This is amazing!! Breathing new life in to my XC. Thank you for sharing. Just flashed /e/ and it's working really well so far. Although I see that selinux is not enforced, anyone know why?
Click to expand...
Click to collapse
To avoid SELinux policy errors and fail to boot

nervousapp said:
POSP boots as much of the Pie Gsi, 10 are more capricious (POSP 10 boots for example, but sim is not detected)
Click to expand...
Click to collapse
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.

I flashed /e/ and it's pretty stable and smooth but my device is overheating when charging and even when it's idle and the display is off. I'm getting severe battery drain from it.
EDIT: Wiping all the partitions and flashing from scratch seems to have done the trick.

I've been using Arrow OS and it's pretty stable and smooth so far. Comes with GApps built-in and Jan 2020 security patch:
https://sourceforge.net/projects/arrow-os/files/arrow-9.x/GSI/27_Jan_2020/

maluus said:
Then probably erfans 10 is better. Because sim Wi-Fi camera etc works. Just didn't tested thoroughly. Only downside setup doesn't complete. Personally I don't use Google services so no problem for me but setup notification persists like it tries to complete setup but doesn't actually progress.
Click to expand...
Click to collapse
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.

mister-13x said:
Hello! You can describe in detail how you installed it, how many have not tried to get further Sony does not work.
Click to expand...
Click to collapse
I didn't anything extraordinary follow the steps in the first post. (Since android version would change I formatted data) use erfanoabdis' unofficial Q gsi which you can find a link at phhusson' gsi images link list. (You can also find the link to phussons list in the first post)