ads

Affichage des articles dont le libellé est mediatek. Afficher tous les articles
Affichage des articles dont le libellé est mediatek. Afficher tous les articles

dimanche 27 septembre 2015

wanna meet the person who said development is easy for sd rather than mediatek



Hi Dev.

I have used all my phones which have mediatek processor and that phones development is started immediate after their release .

now the thing is when i was using mediatek processor phone people said that snapdragon have more development than mediatek now nearly 1 month passed for zenfone 2 laser to release there is no sign for development nor root method so in my openion there is no limit for development even its mediatek or snapdragon there should be smart and well knowledge dev needed to develop a rom



vendredi 25 septembre 2015

[ROM][CM12.1][MT6572] CyanogenMod 12.1 for my Mediatek Device



Ive been messing around my phone lately. A few days before, I came across a CM12 built for another mediatek device from source running on stock kitkat kernell. So, me and my friends tried to port it to our phones running MT6572 chipset and it worked! :D

Now, I am posting here to ask for help in fixing the bugs.
Heres a list of what works and do not work.


What is WORKING:
- Philz Touch Recovery 6.59
- Everything except for things in the "What is NOT WORKING" list.

What is NOT WORKING:
- Bluetooth
- Sim
- Wifi
- Camera
- No sound comes out from the Speaker( But in headphones, it does)
- No USB Mass storage(But in recovery, it has)
- Probably some unencountered bugs.


Help would be highly appreciated :D :D :D



How to port new mediatek 64bit processors mt6732/mt6752 roms



Recently I brought a mobile which runs mt6732 chipset . unlike previous mediatek
32bit processors .it have some new features in it like "support fastboot commands"
And also able to handle apps without any lag . I try to port some ROM to my device
But its not working .all the porting procedures present available in the internet are only able to work with 32 bit processors only . there is not even a single method is
Present in internet .I request the developers to write a working procedure to port a mediatek mt6732 processors .
Not only me there are lots of people want a proper method to port 64bit mediatek processors ROMs.it will very helpful for all .so provide a proper procedure for these new chipset devices.
Thank you XDA. Love you xda dev for your support and development in Android OS.



mercredi 23 septembre 2015

[Q] MTK (Mediatek) Repartitioning 101 gone wrong



Hello guys, for the previous year I would say, I have read about repartitioning MTK phones, starting with my old Cubot MTK6572 (Rest In Peace) to my current Doogee MTK6582.

I have tried countless times to repartition using the EBRTweak utility, or changing the EBR1 & EBR2 files myself but it never, ever works.. :( I always manage to get in the first initial boot and have a false victory where I see that I have re partitioned successfully, but after I reboot after, I always get a boot loop after that initial boot.

For editing the EBR files, I have tried:
-Using EBRTweak
-Editing myself by changing the values from scratch by making calculations with sectors, bytes and addresses
-Editing myself by
First adding a value in the /data partition length, adding that value
Second adding that same value to the start address of the FAT partition
Third removing that same value to the length of the FAT partition

For flashing the EBR files, I have tried:
-Flashing all the patitions with SP flash tools with the new EBR files (without changing the Scatter file)
-Flashing all the patitions with SP flash tools with the new EBR files (changing the Scatter file)
-Flashing only the EBR partitionsa on a working ROM
-Flashing the EBR files using an updater-script via a custom recovery

With each of these methods, all my calculations were exact when I verified everything (to the byte), including using "disktype" command in Linux.

So after one year of failure, I finally decided to post on XDA to ask for help... please, please, does anyone know why the first boot works but the second boot always ends up in a boot loop? :silly: