I'm looking possibility to make custom image to Lenovo Tab 2 A10-30F/L but i have stuck.
system.img is divided to system_*.unsparse files.
one user has done unsparse file joiner application but it doesn't work and no sources available from it. https://forum.xda-developers.com/showthread.php?t=2647429
I have also looked different custom rom kitchens but those doesn't have any file joining solution for joining unsparse files.
Not sure if this is a common method for qualcomm products to have system.img divided to unsparse files.
Any help would be much appreciated.
Jugehuge said:
I'm looking possibility to make custom image to Lenovo Tab 2 A10-30F/L but i have stuck.
system.img is divided to system_*.unsparse files.
one user has done unsparse file joiner application but it doesn't work and no sources available from it. https://forum.xda-developers.com/showthread.php?t=2647429
I have also looked different custom rom kitchens but those doesn't have any file joining solution for joining unsparse files.
Not sure if this is a common method for qualcomm products to have system.img divided to unsparse files.
Any help would be much appreciated.
Click to expand...
Click to collapse
Would it be possible to unpack system.new.dat and repack it as system.img?
https://forum.hovatek.com/thread-15855.html
I unzipped the TB2-X30F_S113_160816_ROW_FULLOTA rom and can only see system.new.dat, not system.img. Where did you get the system.img from?
kreator83701 said:
Would it be possible to unpack system.new.dat and repack it as system.img?
https://forum.hovatek.com/thread-15855.html
I unzipped the TB2-X30F_S113_160816_ROW_FULLOTA rom and can only see system.new.dat, not system.img. Where did you get the system.img from?
Click to expand...
Click to collapse
Isn't that FULLOTA image for updating sw from SDcard??
I have downloaded SW from here. https://cloud.mail.ru/public/3Kcw/Mm9WDWTWH
I have unzipped TB2-X30F_S000113_160816_ROW_qpst.7z and it has system.img divide to Unsparse images.
Jugehuge said:
Isn't that FULLOTA image for updating sw from SDcard??
I have downloaded SW from here. https://cloud.mail.ru/public/3Kcw/Mm9WDWTWH
I have unzipped TB2-X30F_S000113_160816_ROW_qpst.7z and it has system.img divide to Unsparse images.
Click to expand...
Click to collapse
Pardon my lack of knowledge on roms but what would be the issue if using the OTA Rom?
kreator83701 said:
Pardon my lack of knowledge on roms but what would be the issue if using the OTA Rom?
Click to expand...
Click to collapse
Probably not an issue. If i remember some other forum correctly that FULLOTA update fails if you have rooted your tablet.
Also same problem that i have with those unsparse files but it seems that for system.new.dat there seems to be solution.
https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Jugehuge said:
Probably not an issue. If i remember some other foorum correctly that FULLOTA update fails if you have rooted your tablet.
Also same problem that i have with those unsparse files but it seems that for system.new.dat there seems to be solution.
https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Click to expand...
Click to collapse
So can use the ota Rom?
kreator83701 said:
So can use the ota Rom?
Click to expand...
Click to collapse
I don't see reason why not.
Look forward to seeing a CM based ROM!
Have you had much luck getting the source code for the Mediatek chip? Appears to not be readily available
chibot75 said:
Have you had much luck getting the source code for the Mediatek chip? Appears to not be readily available
Click to expand...
Click to collapse
Lenovo Tab 2 A10-30 doesn't have Mediatek chip.
It's using Qualcomm 1.3 GHz quad-core Snapdragon 212 (APQ8009) processor with a Adreno 304 GPU
Would it be possible to build lineage OS for this device using this guide?
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
chibot75 said:
Would it be possible to build lineage OS for this device using this guide?
http://www.lineageosrom.com/2017/01/how-to-build-lineageos-rom-for-any.html
Click to expand...
Click to collapse
I haven't much experience of LineageOS so can't say sure. Could be.
Jugehuge said:
I haven't much experience of LineageOS so can't say sure. Could be.
Click to expand...
Click to collapse
I'm following the above guide in order to build Lineage 14.1 for my Lenovo Tab A10-30F. The guide is intended for Lineage 13.0, so a few minor tweaks are needed. Will keep you updated here, but it's the first time I try to build Lineage from scratch, I only do it because I softbricked my tablet, and I don't manage to find a build for it, so I'm not very optimistic
EDIT: I gave up, it does not look too difficult, but unfortunately I underestimated the amount of time and disk space needed, I need to switch to a better machine... Could someone try?
I found this thread, but I think the device it refers to is different.
It looks strange that nobody built lineage for this tablet though... it's a good piece of hardware, cheap and functional... Did I search in the wrong places?
Up
News anybody?
Up <.<
On the Russian forum http://lenovo-forums.ru/topic/23256-lenovo-tab-2-a10-30-achilles-lineageos-141 someone reports having installed LineageOS 14.1 on the Lenovo Tab 2 A10-30.
Fraxel said:
On the Russian forum ... reports having installed LineageOS 14.1 on the Lenovo Tab 2 A10-30.
Click to expand...
Click to collapse
I have installed this rom today on my TB2-X30L and succesfully tested Wifi, mobile data (LTE/4G), camera (photos only - video does not work) and even FM radio.
I tried to make a phone call what of course did not work.
It´s an unofficial build from July 31st, 2019 (meaning only 5 months old). Security patches from July 5th, 2019.
14.1-20190731-UNOFFICIAL-achilles
Does anybody use this ROM?
Or any other ROM with current security patches?
I actually gave up with Lineage on this device but just because I turned it into a kind-of ebook reader: I removed all the crapware and set it to bare minimal functionality for reading scanned color pdf (D&D manuals mostly) and with the original firmware this yields a monstruous battery life. Like, I can forget it for weeks in my closet and pull it out still half battery
Guys for that tablet the latest custom ROM is lineages 16.0 and the latest twrp is 3.1.1
ROM: https://androidfilehost.com/?fid=7161016148664803115 (tested working fine , RIL not working)
TWRP: https://drive.google.com/file/d/1Z5g-AJXypO0b-_pvJR8TMk7I9cAyREa9/view (tested evrythink working)
Related
hi
been trying to download repo for cynogenmod but have failed with numerous attempt. it is a huge file. is it possible to download just the required files to make cwm recovery 11 ? for kitkat? if possible how ?
Regrettably, no. You will need to repo sync the entire source code
shoey63 said:
Regrettably, no. You will need to repo sync the entire source code
Click to expand...
Click to collapse
alrite,
Code:
:git fetch aosp --tags tag android-4.4.4_2 +refs/tags/android-4.4.4_r2:refs/tags/android-4.4.4_r2
getting error on this one, can i download it manually from ?
https://android.googlesource.com/platform/prebuilts/sdk/+refs
Before going through the pain of doing that, does your device have Cm11 device tree?
shoey63 said:
Before going through the pain of doing that, does your device have Cm11 device tree?
Click to expand...
Click to collapse
no. as per my knowledge . My device is Lg g3 f460 k (snapdragon 805 variant). on kitkat 4.4.2. i searched far and wide but nothing related to it.
I only have 2 options now,
sync cm 12 (not sure if i could build a recovery here that will work in kitkat)
download individual files and put it the respective folders.
It would be better to start with cm11, which is known to be compatible with your device, as you have kitkat. But Cm12 has, at least in the later revisions, his own Recovery, which only offers a part of the options.
Spartaner25 said:
It would be better to start with cm11, which is known to be compatible with your device, as you have kitkat. But Cm12 has, at least in the later revisions, his own Recovery, which only offers a part of the options.
Click to expand...
Click to collapse
okay got everything but there is sdk folder missing in prebuilts.. help me download it manually perhaps ? my version of android is 4.4.2
How to Build new recovery modded for Zopo Speed 7 (Zp951/952) Mtk 6753
In this thread we will discuss how to create or build new recovery modded for Zopo Speed 7
Everybody are Welcome!
MANY THANKS TO OUR MODERATORS TO OPEN AGAIN THIS THREAD !
More attention to the Xda-developers Rules:
http://forum.xda-developers.com/announcement.php?f=256
Many thanks to "SUPER ADMIN" MR. MIKE
XDA:DevDB Information
How to Build new recovery modded for Zopo Speed7 Mtk 6753, Tool/Utility for the Zopo Speed 7 Plus
Contributors
ghost45, Carliv, Yuweng, Marsapa,Codelover,Bigrammy,SevenMaxs,HypoTurtle,
Version Information
Status: Testing
Created 2015-08-22
Last Updated 2015-08-22
Software section
Firmware
http://forum.xda-developers.com/devdb/project/?id=11352#downloads
Recovery
CWM Base no touch
https://copy.com/Of0epSHxRkpwoJkX
Section Procedure
Details
zz
Video Procedure
Details
zz
During the my last attempt to decript the boot and the recovery images from one new Zopo called Speed 7 (Zp951) octa core Mtk 6753 3gb Ram,
i receive this message from the Carliv v.1 program:
This errors appear during the boot decripting and during the recovery decripting.
If i Check well with other tools like "Bigrammy tools or also Yuweng tools" but i do not remember well who is the owner, i see that in the new boot and recovery is present the Kernel compressed and the ramdisk compressed.
kernel.gz
and
ramdisk.gz
If i decompress them the kernel became too big more than the 15 mb.
I tryied to leave it so big in new recovery but flashtool not recognize the files recovery,maybe i'm have passed the memory block ...but i don't know well.
These are the two files:
http://d-h.st/a380
What happened in these new two files?
Possible that mediatek create new compression?
Why these two files are compressed?
...
According The Great Carliv seems that in the Images (recovery and boot) probably isn't present anymore Mediatek header .
Still have no Speed7 (waitingfor it), so I can't help right now. This message is just to let you know I will be contributing to this thread as soon as possible .
TWRP
@ghost45 ported my UMi TWRP v2.8.7.0 so give it a try :fingers-crossed:
Download Here from Copy.com
@bigrammy: Original recovery is 8.27 MB, yours is 13.47 MB. Do you think this fits? Right now I don't know the structure of the Speed7-ROM, but I think other parts of the ROM have to be moved. Can you upload the scatter you used so we can have a look at the allocation? Thanks.
AP756 said:
@bigrammy: Original recovery is 8.27 MB, yours is 13.47 MB. Do you think this fits? Right now I don't know the structure of the Speed7-ROM, but I think other parts of the ROM have to be moved. Can you upload the scatter you used so we can have a look at the allocation? Thanks.
Click to expand...
Click to collapse
64bit SoC recovery partitions are generally 16mb in size.
I do not have the zopo speed myself. Maybe ghost45 could upload the scatter as I assume he got the .img's from a stock rom.
EDIT: Scatter here http://forum.xda-developers.com/devdb/project/?id=11352#downloads
EDIT EDIT: Confirmed recovery partition is 16mb in size
bigrammy said:
64bit SoC recovery partitions are generally 16mb in size.
I do not have the zopo speed myself. Maybe ghost45 could upload the scatter as I assume he got the .img's from a stock rom.
EDIT: Scatter here http://forum.xda-developers.com/devdb/project/?id=11352#downloads
EDIT EDIT: Confirmed recovery partition is 16mb in size
Click to expand...
Click to collapse
Thanks to arrive here Big!
I have check inside your recovery and i saw that you are able to leave the file compressed inside (kernel.gz) ...but you have update your repack and unpack tool?
:silly:
bigrammy said:
64bit SoC recovery partitions are generally 16mb in size.
I do not have the zopo speed myself. Maybe ghost45 could upload the scatter as I assume he got the .img's from a stock rom.
EDIT: Scatter here http://forum.xda-developers.com/devdb/project/?id=11352#downloads
EDIT EDIT: Confirmed recovery partition is 16mb in size
Click to expand...
Click to collapse
Big this is the result:
The twrp start but i receive this message:
And the touch seems do not respond at all......but this is first step ....
To the contrary i have tryied again my cwm base (not touch) sorry but i'm fixed for the cwm...and run well but i must see the memory sector to understand why i can't able to see the sd ext card.
see you and thanks for your work.
:good:
ghost45 said:
Thanks to arrive here Big!
I have check inside your recovery and i saw that you are able to leave the file compressed inside (kernel.gz) ...but you have update your repack and unpack tool?
:silly:
Click to expand...
Click to collapse
Sorry I am working now and the PC at work blocks images
bigrammy said:
Have you deleted a post
Does my recovery work or not
Click to expand...
Click to collapse
No i do not deleted no one post....
but before i have had problem with see my last post, maybe xda forum have some problems today!
Your recovery start but do not run the touch at all and do not run also with the volume button.
So is unusable for now.
To the contrary my cwm run well but i must check well the memory sectors to understand why the sd ext is not seen.
(The memory internal is visible the sd ext not)
https://www.copy.com/s/t:CSIJeykJT1iaUKQP;p:%2Frecovery_Cwm_Speed7_102530_Roby.img;oid:1
ghost45 said:
No i do not deleted no one post....
but before i have had problem with see my last post, maybe xda forum have some problems today!
Your recovery start but do not run the touch at all.
Click to expand...
Click to collapse
No problem we both have PC issues :laugh:
The company PC's block lot's of content :crying:
It sounds like you have the same issue as our Elephone P6000 with no touch function.
You will need to ask zopo to fix the touch in the kernel...
hi,
2° test Cwm modded :
https://copy.com/QQxDjuqIf0CCzA2S
in this second is not visible no one memory...(no SD internal and SD ext)
But i must have more time to check the memory sector!
Hi ,
finally i have decompressed the Big Kernel and i have reduce the real dimension.
I Have attached in Download Section.
ghost45 said:
Hi ,
finally i have decompressed the Big Kernel and i have reduce the real dimension.
I Have attached in Download Section.
Click to expand...
Click to collapse
Ok, great.
You can do a thread about CWm and TWRP on speed 7 developement. By the way when the source will be release, i will creat cm12.1 rom, you will help to do this if there some bug ? (i will received my zopo about 10 sept)
flavien317 said:
Ok, great.
You can do a thread about CWm and TWRP on speed 7 developement. By the way when the source will be release, i will creat cm12.1 rom, you will help to do this if there some bug ? (i will received my zopo about 10 sept)
Click to expand...
Click to collapse
Hi Flavien,
I have already opened this thread about the recovery.. I not think is good to open one other about the recovery.
About the source... I know that Mediatek seems will release them in the next month... But i don't know the real date.
About the help to build one new rom is always one great and good idea to change opinions and to change hands.. Yes.
Sent from my GT-I9505 using XDA Free mobile app
ghost45 said:
Hi Flavien,
I have already opened this thread about the recovery.. I not think is good to open one other about the recovery.
About the source... I know that Mediatek seems will release them in the next month... But i don't know the real date.
About the help to build one new rom is always one great and good idea to change opinions and to change hands.. Yes.
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
Hi bro,
Just some advice here as we have already been down this road with the Elephone P6000.
1. CWM recovery is pretty much dead as of KitKat 4.4.4 and is not supported in Lollipop 5.0 > so any CWM recovery's are likely to have been compiled using KK. This means they will never be 100% perfect for your Lollipop 5.1 device.
2. The TWRP I have ported for you is obviously working and has been compiled for Lollipop so If you had a working touch I am sure it would be 100% perfect. :good:
So what should you do ??
1. Get on to Zopo and demand they fix the touch in the Kernel I would guess it's a goodix GT9xx touch screen the same as the Elephone :laugh:
2. You could still use the CWM to do most things like flash supersu.zip to root etc etc.
3. You could probably use TWRP with a Mouse and OTG cable too.
4. Once rooted you can use wanam's Partitions Manager Here To back and even restore you partitions but it's a little slow Thread Here :good:
5. Last but not least use SPFlashtools for backup and restore. :good:
Regards bigrammy.
bigrammy said:
Hi bro,
Just some advice here as we have already been down this road with the Elephone P6000.
1. CWM recovery is pretty much dead as of KitKat 4.4.4 and is not supported in Lollipop 5.0 > so any CWM recovery's are likely to have been compiled using KK. This means they will never be 100% perfect for your Lollipop 5.1 device.
2. The TWRP I have ported for you is obviously working and has been compiled for Lollipop so If you had a working touch I am sure it would be 100% perfect. :good:
So what should you do ??
1. Get on to Zopo and demand they fix the touch in the Kernel I would guess it's a goodix GT9xx touch screen the same as the Elephone :laugh:
2. You could still use the CWM to do most things like flash supersu.zip to root etc etc.
3. You could probably use TWRP with a Mouse and OTG cable too.
4. Once rooted you can use wanam's Partitions Manager Here To back and even restore you partitions but it's a little slow Thread Here :good:
5. Last but not least use SPFlashtools for backup and restore. :good:
Regards bigrammy.
Click to expand...
Click to collapse
Hi Bro,
Thanks for the answer, but actually we are waiting for the source from Mediatek.
When i will have some little time ...first, i want to create a new porting with cwm to have, almost, one recovery usable.
After yes probably we must studied these new sources....when their will arrive.
I had made a thread about creating a custom ROM for Android over here: http://forum.xda-developers.com/general/xda-assist/building-custom-android-rom-t3526514#post70277383 and Art Vanderlay suggested I post here, so here it is.
I own the BLU Energy X 2, and I am in need of the Device Tree and Vendor Blobs for the phone to create a custom ROM based off of CyanogenMod. My device currently has CyanogenMod on it, however it's an unofficial port for the BLU Studio Selfie. I am not sure how the dev of that ROM got these files, however the Infinix Hot 2 is a "clone" of that device, so he may have just ported it from there, or it may have not even needed porting at all Anyways, for me to create a custom ROM based off of CyanogenMod, I need the Device Tree and Vendor Blobs. I do have the ProjectConfig file if that helps.
These files are usually somewhere on GitHub, but due to the development community for BLU devices in general being almost non-existant, these files are nowhere to be found. So, how can I get these files for my device to start building a custom ROM? Thanks
If you need any other information, please reply.
Device Specs:
BLU Energy X 2
Model #: E050U
Android Version: 5.1 Lollipop
Kernel Version: 3.10.74+
Chipset: MT6580
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Audriuskins said:
Use Device and Vendor trees from similar devices, change names and other stuff like your device in the configs...
I'm noobie too, but this is how people make it for MTK devices
Click to expand...
Click to collapse
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
NateDev473 said:
Ok, thanks, I'll look for some similar devices. Will any similar MTK device work? What needs to be similar? OS versions? Chipset? Kernel version?
What do I need to look for?
Thanks
Click to expand...
Click to collapse
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Audriuskins said:
Must be on the same chipset from my experience, Kernel and OS doesn't matter.
Click to expand...
Click to collapse
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
NateDev473 said:
So all I need to do is find a device with similar specs, and same chipset that has device tree and vendor blobs already created? And then I just modify it to fit my specific device?
Click to expand...
Click to collapse
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Audriuskins said:
Something like that, you should look up :
http://forum.xda-developers.com/showthread.php?t=2274332
Click to expand...
Click to collapse
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
These come from the oem. While the directions posted sometimes work it is dirty hacking at best and never stable. This is why developers stay away from mtk devices and they are really only used in cheap devices.
NateDev473 said:
Do the devices need to be officially CM supported, to get the device tree and vendor blobs? Because I found a couple of devices like the ZenFone Go that has an unofficial version of CM, but I can't find the device tree for that device.
Click to expand...
Click to collapse
Search on Github
Audriuskins said:
Search on Github
Click to expand...
Click to collapse
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
NateDev473 said:
Ok, so I've discovered that the Infinix Hot 2 has mostly the same specs as my device, and that it's basically a clone of the Studio Selfie, which is the device that I used to unofficially port CyanogenMod to my device, so that's a good sign. Anyways, CyanogenMod was built for the Infinix Hot 2 from source, and they provided links to GitHub. It does say though that the Infinix Hot 2 is Android One. Is that a big problem?
Thanks
Click to expand...
Click to collapse
No idea x)
I guess you can try xd
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
Ok, thanks
Audriuskins said:
No idea x)
I guess you can try xd
Click to expand...
Click to collapse
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
NateDev473 said:
I found this on GitHub, is that what I am looking for in terms of the vendor files and stuff like that? http://imgur.com/a/KUcxC
Click to expand...
Click to collapse
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Audriuskins said:
Clone whole tree, rename everything to yours.
In device tree check if configs are like your device
Click to expand...
Click to collapse
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
NateDev473 said:
Ok, I will. If some of the configs are different for my device, I can just replace the values with the ones that work for my device right? Also in that other device's lib volder, they have a lot less stuff then my stock ROM lib folder, is that fine?
Click to expand...
Click to collapse
I can't help you very much, because I'm new in MTK development ://
Audriuskins said:
I can't help you very much, because I'm new in MTK development ://
Click to expand...
Click to collapse
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
NateDev473 said:
Would it be possible to then just upload my own files? Because on my phone I have all those files that are there for the other device. That would be better, I think, because they would be specific to my phone... If you don't know it's fine
Click to expand...
Click to collapse
I dont know
[continuation of title]
And this is my way of trying to contact him about His pixel experience Project which He seems to be Working on
So If you read this
Please provide information so that we can contact you
Thx in advance! (If read)
Some random said:
[continuation of title]
And this is my way of trying to contact him about His pixel experience Project which He seems to be Working on
So If you read this
Please provide information so that we can contact you
Thx in advance! (If read)
Click to expand...
Click to collapse
NO luck,stuck at G logo :crying:
lookmanns said:
NO luck,stuck at G logo :crying:
Click to expand...
Click to collapse
Me 2
Even with A CRAP TON
Of patches
Some random said:
Me 2
Even with A CRAP TON
Of patches
Click to expand...
Click to collapse
btw I found this dev in galaxy s2 plus forum,and his name is ud4
lookmanns14 said:
btw I found this dev in galaxy s2 plus forum,and his name is ud4
Click to expand...
Click to collapse
Oh
Nice!
UPDATE:
I was able to contact him and got an answer
He stated that he did not have an Xperia x to test this ROM
But told that I could test and send feedback if it works or not.
Maybe you can write a PM asking if you can test too! (Anyone who reads this can ask!)
This whole thing feels weird.
On first flash, recovery says the ROM was created by jhenrique09, who is an official maintainer of PE. But after searching both jhenrique09 and PE's official Github, there's no sign of suzu on the list. I'm assuming this is a port. This brings us to another problem.
A quick look at the file name reveals this ROM is based on 4.4 kernel. As far as I know, there is no Pie ROM out there that is using 4.4 kernel (Chippa_a's LOS uses 3.10, Omni and Treble uses 4.9). The closest thing I could think of is Omni 8, but why port a Pie ROM using an Oreo base?
Lastly, who would make a ROM for a phone they don't have?
iH8Ecchi said:
This whole thing feels weird.
On first flash, recovery says the ROM was created by jhenrique09, who is an official maintainer of PE. But after searching both jhenrique09 and PE's official Github, there's no sign of suzu on the list. I'm assuming this is a port. This brings us to another problem.
A quick look at the file name reveals this ROM is based on 4.4 kernel. As far as I know, there is no Pie ROM out there that is using 4.4 kernel (Chippa_a's LOS uses 3.10, Omni and Treble uses 4.9). The closest thing I could think of is Omni 8, but why port a Pie ROM using an Oreo base?
Lastly, who would make a ROM for a phone they don't have?
Click to expand...
Click to collapse
IT seemed kindof fishy to me too but....well....it kind of boots
We could try an android 8.1 OEM file and see if it boots
Some random said:
IT seemed kindof fishy to me too but....well....it kind of boots
We could try an android 8.1 OEM file and see if it boots
Click to expand...
Click to collapse
If not.....extract kernel and see what's wrong I guess
Some random said:
IT seemed kindof fishy to me too but....well....it kind of boots
We could try an android 8.1 OEM file and see if it boots
Click to expand...
Click to collapse
it will not boot with android 8.1 an 9 oem..you just got infinity restart
I think oem already include in this rom,you can check oem file after flash the rom in /root/oem using twrp file manager
Someone needs to take some logs without patches of any sort
On the 4.4 kernel Version
(Got private message about this 45 minutes ago)
Hi everyone, I've been trying to find a custom rom for Xiaomi Mi 12X, but none found so far. I tried to port Pixel Experience rom using the Xiaomi Mi 11X (alioth) device tree and changed accordingly, since the SOC and almost all specs are the same except Camera. Can anybody shed some light in how to correctly port the ROM for my devices without official device tree from LineageOS or Pixel Experience? Thank you.
Anybody has any suggestions?
JChanMe said:
Anybody has any suggestions?
Click to expand...
Click to collapse
Hi, right now I'm using crdroid gsi, which works pretty good. Except of fp, everything works as it should. It's smooth, has a good bb and even MGC's Gcam 8.1, last stable, works incl. portrait, nightmode and with all lenses (ok, no pixelbinning). Installing is pretty simple: use fastbootd and just fash img to system. That's it....
Voodoojonny said:
Hi, right now I'm using crdroid gsi, which works pretty good. Except of fp, everything works as it should. It's smooth, has a good bb and even MGC's Gcam 8.1, last stable, works incl. portrait, nightmode and with all lenses (ok, no pixelbinning). Installing is pretty simple: use fastbootd and just fash img to system. That's it....
Click to expand...
Click to collapse
Thank you but I don't see it on crdrood website, did you build it yourself?
JChanMe said:
Thank you but I don't see it on crdrood website, did you build it yourself?
Click to expand...
Click to collapse
It's a gsi treble rom (that works with many vendors)... Just search for project treble on xda!
Voodoojonny said:
It's a gsi treble rom (that works with many vendors)... Just search for project treble on xda!
Click to expand...
Click to collapse
Thank you. I figured it out and tried a few treble roms including pixel experience, there are a few problems including auto brightness, fingerprint and vibrator. You had the same problems?
JChanMe said:
Thank you. I figured it out and tried a few treble roms including pixel experience, there are a few problems including auto brightness, fingerprint and vibrator. You had the same problems?
Click to expand...
Click to collapse
Yes, especially the sound makes problems... When usung videocall, it's awfully distorted. I'm using stock for now. With Lawnchair and some modifications it's ok for now.
Do you know, why there's no thread for our phone here?
Just seen, you are forking some repositories... Have you been successful in building?
Voodoojonny said:
Just seen, you are forking some repositories... Have you been successful in building?
Click to expand...
Click to collapse
I successfully build the ROM without errors, just some warnings, but it didn't boot aftter flashing it.
JChanMe said:
I successfully build the ROM without errors, just some warnings, but it didn't boot aftter flashing it.
Click to expand...
Click to collapse
Did you flash with vendor or system only?
Voodoojonny said:
Did you flash with vendor or system only?
Click to expand...
Click to collapse
No, I used the same procedure as described for Alioth device, fastboot flash boot boot.img, then from recovery use adb push to update the zip ROM file.
JChanMe said:
No, I used the same procedure as described for Alioth device, fastboot flash boot boot.img, then from recovery use adb push to update the zip ROM file.
Click to expand...
Click to collapse
But how did you built the rom. Did you get out a flashing zip directly? Normally, you create different partitions as fas as I know... Would you share your rom? Btw. which one did you build?
Voodoojonny said:
But how did you built the rom. Did you get out a flashing zip directly? Normally, you create different partitions as fas as I know... Would you share your rom? Btw. which one did you build?
Click to expand...
Click to collapse
Yes, after building I got a zip and flashing it using update by adb push. I built Pixel Experience Android 11
JChanMe said:
Yes, after building I got a zip and flashing it using update by adb push. I built Pixel Experience Android 11
Click to expand...
Click to collapse
But you used the lineage device tree. And PE is aosp not lineage. Might that be the problem? Would you try to build crdroid? Or instruct me how to setup a build environment?
No, I used the PE device tree, not Lineage. I used the build instructions provided by Pixel Experience for Alioth.
JChanMe said:
Anybody has any suggestions?
Click to expand...
Click to collapse
Yesterday xiaomi released kernel for 12x on GitHub. So I think now you can build pe/los without troubles
Maxletsplay_1 said:
Yesterday xiaomi released kernel for 12x on GitHub. So I think now you can build pe/los without troubles
Click to expand...
Click to collapse
Didn't they release the kernel when the phone was released?
JChanMe said:
Didn't they release the kernel when the phone was released?
Click to expand...
Click to collapse
Technically yes, but i've checked GitHub(about month ago) and I didn't saw kernel for this phone, just an empty folder
JChanMe said:
Didn't they release the kernel when the phone was released?
Click to expand...
Click to collapse
Did you replaced vendor libs with libs from 12x and other stuff like fstab, bins, rc files..configs? Attach logs from boot if you decide to build again. My advice is to build as eng and disable encryption, put selinux to minimal mode, nuke livedisplay, import vendor modules if you build with stock prebuilt kernel. Always look for F Linker errors in log and resolve them.
I'm waiting for AOSP rom too.