If the UEFI firmware can be ported for "almost" every single device that is powered by a Qualcomm® Snapdragon™ SoC, and it was even successfully ported to the Broadcom BCM2711 on the Raspberry PI4 and the BCM2837B0 on the Raspberry PI3 that are not Snapdragon SoCs, then can it ported to MediaTek devices? Plus if it is possible, can someone help me port it to my MediaTek devices "Infinix X692" ? Btw I don't have a very good knowledge about porting the UEFI firmware. Thanks.
I don't think much people have actually worked on that front.
TORNADO9224 said:
If the UEFI firmware can be ported for "almost" every single device that is powered by a Qualcomm® Snapdragon™ SoC, and it was even successfully ported to the Broadcom BCM2711 on the Raspberry PI4 and the BCM2837B0 on the Raspberry PI3 that are not Snapdragon SoCs, then can it ported to MediaTek devices? Plus if it is possible, can someone help me port it to my MediaTek devices "Infinix X692" ? Btw I don't have a very good knowledge about porting the UEFI firmware. Thanks.
Click to expand...
Click to collapse
What has this to do with Windows OS this forim is dedicated to? Take note that UEFI ( formerly called BIOS ) isn't part of Windows OS.
I will figure out more on this topic. ReadyPay Online
TORNADO9224 said:
If the UEFI firmware can be ported for "almost" every single device that is powered by a Qualcomm® Snapdragon™ SoC, and it was even successfully ported to the Broadcom BCM2711 on the Raspberry PI4 and the BCM2837B0 on the Raspberry PI3 that are not Snapdragon SoCs, then can it ported to MediaTek devices? Plus if it is possible, can someone help me port it to my MediaTek devices "Infinix X692" ? Btw I don't have a very good knowledge about porting the UEFI firmware. Thanks.
Click to expand...
Click to collapse
It's technically possible to port UEFI firmware to MediaTek devices as long as the hardware is compatible and there is sufficient documentation available. However, the process of porting UEFI firmware is highly technical and requires a significant amount of expertise and resources. wordle unlimited
Without detailed technical information and documentation from MediaTek, it would be difficult to port UEFI firmware to your specific device (Infinix X692) without a lot of trial and error. Porting UEFI firmware typically requires a deep understanding of low-level hardware programming and firmware development.
If you don't have experience with porting UEFI firmware, it's not recommended to attempt the process on your own, as it could potentially damage your device. You may want to seek assistance from experienced developers or hire a professional firmware development company to help you with this task.
It's worth noting that the process of porting UEFI firmware to MediaTek devices may also be limited by legal restrictions, as some device manufacturers may not allow users to modify the firmware. You should also be aware of any potential risks associated with modifying the firmware on your device, including voiding the device's warranty or rendering it unusable.
You can give this a try, but I haven't verified it: https://www.androguider.com/2016/10/efidroid-takes-booting-to-completely.html?m=1
Apparently since mediatek uses partition tables it's similar to uefi and thus compatible.
Related
Has anyone put work into bringing windows to the non-pro Dell Venue 8? I have a Dell Venue 8 3830 I can dedicate to testing if anyone is willing to attempt it. Not sure if it's based on a uefi like it's pro version counterpart or if it could be hacked to support it from existing images for the pro.
Shouldn't be restricted to Windows. I'm sure if a UEFI based firmware can run on this tablet, it could be used for Linux just as easily as windows.
They're not uefi sorry only the Venue 10 5050 is uefi
social-design-concepts said:
They're not uefi sorry only the Venue 10 5050 is uefi
Click to expand...
Click to collapse
Very similar tablets by Dell exist (the Pro versions) which are UEFI based. In theory it's possible to adapt it's firmware for this tablet due to the nearly identical hardware.
Synthax said:
A very similar tablet exists (the 5830) which is UEFI based. In theory it's possible to adapt it's firmware for this tablet due to the nearly identical hardware.
Click to expand...
Click to collapse
Good luck : but those two are not even close to identical hardware
3830 Clovertrail Plus
5830 Baytrail
social-design-concepts said:
Good luck : but those two are not even close to identical hardware
3830 Clovertrail Plus
5830 Baytrail
Click to expand...
Click to collapse
Are you saying it's not possible, or that it would just take too much work by too many people and there aren't nearly enough people interested in trying it?
Synthax said:
Are you saying it's not possible, or that it would just take too much work by too many people and there aren't nearly enough people interested in trying it?
Click to expand...
Click to collapse
All the above biggest hurdle would be that the windows bootloader doesn't support sfi and then there are the proprietary graphics.
Really the only way it could be done would be by building a intel android boot image that supported xen and then boot windows as a VM. The bootstub used on the devices does support xen kernels but there is next to no documentation on how to build or set it up. Also I don't remember if the virtualization of the clovertrail plus soc supports hardware pass through or not.
social-design-concepts said:
All the above biggest hurdle would be that the windows bootloader doesn't support sfi and then there are the proprietary graphics.
Really the only way it could be done would be by building a intel android boot image that supported xen and then boot windows as a VM. The bootstub used on the devices does support xen kernels but there is next to no documentation on how to build or set it up. Also I don't remember if the virtualization of the clovertrail plus soc supports hardware pass through or not.
Click to expand...
Click to collapse
Makes sense. Was hoping to run Windows on it just because I tinker with things in my spare time. Guess I'll search around for one of those Android/Windows dual boot tablets since those are usually not to expensive and less of a pain to get working than dual booting with Android manually. Thanks for the info.
Hi,
CPU of my android device is MT6592 (8xARM Cortex –[email protected] MHz) with instruction set 32-bit ARMv7. Board and product is ht1_107a_iball_mjk. Apart from this, Codename is REL, Internal Memory is 16GB and RAM is 2GB. And I searched many times on https://download.cyanogenmod.org/ for compatible CM 13 but I didn’t find.
If no CM 13 is exists for my device, it’s unacceptable for me. Like system requirements for Windows 7, Windows 8.1, Windows 10, etc, I would like to know the hardware requirements for android 6 and android 7.
Also I noticed, all builds on https://download.cyanogenmod.org/ are for Snapdragon Processors only. Is it right?
Please let me know about the compatible CM 13 from https://download.cyanogenmod.org/.
Regards
GNS
u forgot the most important part xD , what's ur device model ?
Modal Number is iBall Brace-X1. It really more unfortunate for me that there is no release from my device manufacturer related to boot-loader, Custom Recovery, Custom ROM or anything related to this. Also I do not find any helpful developer release for my device. As I do not get helpful tools, release, Custom Recovery and Official Custom ROM for my device, however I am ready to try for unlocking boot-loader, flashing Custom Recovery and Custom ROM multiple times but while doing all these procedures sometimes I get scared of any faults in terms of hardware.
Hello I am Jimmy and I am starting on ROM development for mobile and PC. I have a few doubts regarding that.
1> Android-x86 Oreo is the latest build on their website, But roms like Bliss, they ported Pie on PC. How to do that? I mean how to get Android-x86 pie?
2> How much average time does it take to compile the source of Android(both x86 and arm64)? [Specs for consideration: Intel Core i7-8750H 2.2 Ghz 6 cores, 16 GB RAM, Ubuntu 18.04 ]
3> What IDE/Development softwares should I use for modifying the original source code that is? Android Studio? Netbeans? Notepad++? Or what??
And a question not regarding development:
I have a device lying around my drawer. My bro used to use it until he bought a new one. Its LAVA Z60 which is based on MTK MT6737 chipset. I researched but found out that there are very few MTK devices with custom roms. Is LAVA Z60 one of em? And if so, where to get the Device Tree, Vendor, Kernel etc.. for the device? Also, note that MTK Droid tools does identify the device, but I cant create scatter file cuz there is just one item on the list with location and every other thing as 0.
Soo.. yeah thats all. Please help me if you can. Thanks in advance.
Help
Hi XDA.
Its been a long since people could run big OSes(like win10) on the Intel Atom android phones. That of course because the have the KVM technology support. So can we be able to bring this technology to our ARM64 phones? What i found intersting is that all the processors that have Cortex-a15 or higher will support KVM!!!! the real problem is that we need a moded kernel in order to enable KVM:crying:.
I already have a Pocophone F1 are there any chances that we can get that smooth Windows runnin' on the poco( or any other arm64 phone)?
Hi everyone,
After a few hiccups, I successfully rooted my Leagoo T5c, thanks to the excellent tutorial posted here. The phone works fine, thank you, but now, I'd like to know how to proceed to, say, upgrade the phone from its current Android version (7.0) to a more recent version.
Where to start?
Since this phone has a Spreadtrum/Unisoc SC9853i SoC (Intel-based), I suppose the custom ROMs and upgrade possibilities are few and far between, but I'd like to give it a shot.
I'm open to ideas, tips, tricks, voodoo moves and Santeria incantations, but I'm still a noob when it comes to Android, so please, be patient, and methodical... :good:
@UglyStuff
If you can unlock phone's boot-loader then you should be able to flash any Custom Recovery and/or Custom ROM that's suitable to 100% to phone's CPU-architecture. Who is the supplier of phone's SoC isn't of any interest at all.
Hi,
Thing is, as I said, I'm a noob when it comes to Android, so I don't want to brick my phone by trying to make it ingest a ROM that's not suitable for it.
If my phone came with a MediaTek or Qualcomm SoC, I wouldn't worry, because there are plenty of ROMs out there, custom or not, to play with, but this Spreadtrum/Unisoc SoC is a thing of its own.
It's based on Intel's Airmont architecture, and few phones or tablets use it, at least this specific version (SC9853i). Maybe I just don't understand too well how a ROM is built.
UglyStuff said:
Hi,
Thing is, as I said, I'm a noob when it comes to Android, so I don't want to brick my phone by trying to make it ingest a ROM that's not suitable for it.
If my phone came with a MediaTek or Qualcomm SoC, I wouldn't worry, because there are plenty of ROMs out there, custom or not, to play with, but this Spreadtrum/Unisoc SoC is a thing of its own.
It's based on Intel's Airmont architecture, and few phones or tablets use it, at least this specific version (SC9853i). Maybe I just don't understand too well how a ROM is built.
Click to expand...
Click to collapse
For example, I found this article where they explain how to flash LineageOS 17 (based on Android 10) on a Panasonic Eluga Ray 800 that uses the same SoC as my Leagoo T5c.
The thing is, I don't know if this is transposable to my device, though the two share the same SoC. As I said earlier, I don't want to permanently brick my phone...
@UglyStuff
The mentioned Intel Airmount SoC's instruction set architecture is x86_64 , the also mentioned Intel Spreadtrum SC9853i SoC's instruction set architecture is x86_64, too. Hence in order to upgrade yor phone's Android you need a Custom ROM compiled for x86_64 architecture. GIYF ...
OK, but since this Panasonic and my Leagoo share the same SoC, they also share the same x64 instruction set, so do I get it right if I say that the custom ROM built for the Panasonic would fit on my Leagoo, or am I missing something?
In theory it should.
OK, I guess I'll have to chance it, and use recovery in case things so south. My phone isn't compatible with Treble, according to this app. Does it mean anything in terms of installing one of the generic system images found here or not?