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

dimanche 4 janvier 2015

Porting CyanogenMod 12 topic






URGENT!
Found a man on the xda ready to help porting CyanogenMod 12 on our apparatus (g800h);
(he ported it to s3 Neo (this appart has exactly the same characteristics as our: Snapdragon 400, Adreno 305, 1.5Gb RAM, 16Gb built, the resolution is the same);

He is already trying to collect firmware, but he needs someone who knows English and can communicate with him, as well as understand what firmware, android and rom
Here is his gmail for communication (for example through the hangouts): r.rozic97@gmail.com
(do not forget to say about the CM12 port on s5 mini (g800h));

This issue should be solved as soon as possible.






lundi 29 décembre 2014

porting topic






how can i port rom from kk to jb same mtk device...pls help me its urgent






[Q] Porting CM11 to my device topic






Hello, i've found out that Galaxy mini 2 have same chipset as mine. I have GSmart g1345, its pretty rare phone and theres no updates for this device. Last one is GingerBread 2.3.4. I also got sources for it:

Code:


repo init -u git://codeaurora.org/quic/qrd-android/platform/manifest.git -b refs/tags/R7227TCNCJNLYA71542302
repo sync


How can i port CM11.0 from to my device?






samedi 27 décembre 2014

[Q] MT6572 ROM Porting Question topic






Hey guys, I was referred over here from XDA Assist so lets try this again:

So I am thinking of porting a custom rom for my MT6572 device which I am sure you have never heard of: QMobile A170. I already have it rooted using Farmaroot 1.9.3 (thankgod for generic tools) and seeing as there are no roms for this specific model out there, was thinking of porting one myself. So here are my queries.

1. Which ROM do you suggest I port (in terms of features, ui, stability and chance of success etc)? Where can I find an android 4.4+ rom? I only found one but it has an annoying dev picture everywhere: droidbuzzz.blogspot(dot)com/2014/10/mt6572-custom-rom-pure-l-custom-rom-for(dot)html

2. Which porting guide do i follow for MT6572 porting? there are alot of guides out there, and more alarmingly, with different steps and procedures.
I had this in mind: en.miui(dot)com/thread-32469-1-1(dot)html

3. Should I use a porting tool or something?

4 Any tips, wise words etc?






vendredi 26 décembre 2014

jeudi 25 décembre 2014

Porting Firefox OS to FP1 topic






Continuing the discussion from Firefox OS is the way to go!

Hi guys!

I am new to xda-devs, but have been visiting it for useful information in the past.
I own a FP1 (First Edition) and am seeking to port FFOS to the FP1.
I do not have any developing experience, I have just done C and Java and I am comfortable with Linux's CLI.

- I am following this guide: Porting Firefox OS
- Currently I am stuck at the following: Create a manifest for the new device.
- Which changes do I have to make to the hamachi manifest mentioned there?
- What do I insert at the *device specific things* for "path", "name" and "revision"?
- (I assume I can leave the other parts (like Stock Android things) as they are?)

These files are at hand:

Quote:










Originally Posted by madde, post:9, topic:3116


Well there already is a recovery file for the fp1 + fp1u by chrmhoffmann up and running. The MTK6589 source code is kind of released and there has been a lot of work on the android code by the omnirom project, which might come in handy.

Should be definitely manageable to build and try out Firefox OS on the FP1. UnfortunatelyI'll just don't have the time to really dig into that. Maybe someone with a bit more experience can give it a shot. I'd love to see and try out the result...





I am inviting @Madde, I hope you, or others, can help me out.

Cheers, Stefan

PS.: As I am new to xda-devs, I do not know, if my thread is in the right position and/or tagged correctly. Please give some advice on how to improve my original post.






mercredi 24 décembre 2014

[Q] MTK6572 - Help please with ROM porting topic






I have a MTK6572 (Doogee DG300) and I need to install the cleveri rom on it, the only problem is that the tutorial I found about ROM porting says to get files from META-INF folder of the base rom and send them to META-INF folder of the custom Rom, but I don't have a META-INF folder on the base rom, I not even have it on my device, which I flashed and installed the base rom already.

Is the META-INF really necessary? Can't I just edit the one from the custom rom, as the tutorial suggests in the end?






dimanche 21 décembre 2014

ROM Porting problems help!!! topic






Guys I am having a problem I tried to port a Nexus 5 rom to the zr from this post - http://forum.xda-developers.com/show....php?t=1908008
OK...So I was trying to port a rom of Nexus 5 to the Xperia ZR
My port ROM is Paranoid Android 4.6 BETA 5 and my base rom is cm-11-20141209-NIGHTLY
So I did everything and it was just fine till the bootanimation and its just booting and booting and booting then I followed the steps for the bootloop but still...Same problem..
I am a beginner...Any solutions????






Help with porting Android Lollipop ? topic






Ok, how do I unpack these files, so I can try porting the ROM for our device?
file_contexts
system.new.dat
system.patch.dat
system.transfer.list






vendredi 19 décembre 2014

Request for porting topic






Can anyone port kitkat drivers from adreno205 to 203???pls help.
I have a galaxy core duos
All core users will be happy to see kitkat on core.






jeudi 11 décembre 2014

[PORT][RECOVERY] Carliv Touch Recovery v3.0 [Kitkat] for porting to MTK phones topic






If you don't have experience in MTK phones, stay away, use your phone as it came from store, and just start reading and learning. Don't jump to do things you don't understand. These resources are for experienced users. I'm tired of hundred PM's with "Help I bricked my phone" because I flashed a wrong recovery or "I did something stupid".

DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.


It is a CWM based recovery and is compatible with it. In this version I used Napstar-xda's full touch module as base. The navigation it is posible by touching the menu item. In long display menu (as choose zip from sdcard) for scroll page down Swipe Right and for scroll page up Swipe Left. For Go Back also Swipe Left.
If the Swipe doesn't work (usually if your phone is multitouch but has only 2 points of touch), use bottom virtual navigation keys or volume buttons Down for Scroll down, Up for Scroll up, and the back button for Go Back.

Version 3.0 first release (11-dec-2014):

- based on cwm (cwm 6.0.5.1) and added improvements on top.
- bottom virtual navigation keys, to compensate the non-function of swipe in some phones
- a "nvram backup/restore" menu: the nvram partition will be backed up in clockworkmod/backup/.nvram/nvram-xxxxx folder as nvram.img. This will help if you lose IMEI and other communication features. It will work only if you have the nvram partition defined in recovery.fstab. If the nvram partition is damaged (as in flashing an oversized recovery) this will not help you, and you need SPFlashTools to reflash with format your phone official firmware, and after that flash this recovery, boot in recovery and restore nvram.
- a new advanced backup/restore menu
- separate power and wipe menu
- aroma file manager integration
- new GUI images, very light (the difference between non-touch modded cwm and this one is only 14 Kb, for 720x1280 resolution)
- some other.


For port follow my new guide from here.
In kitkat recovery, the lunfile isn't used anymore. Sdcards are voldmanaged, and it is used fstab version 2.
There are 15 images for 15 resolutions. Choose the one that match exactly your phone resolution. If your phone has the resolution 720x1280, then take an image with "720x1280" in name. There are few landscape versions for tablets with landscape format, so don't confuse "720x1280" with "1280x720".

Regular MTK phones:
Download your resolution from HERE.

MTK phones with "custpack" partition (Alcatel or TCL):
Download your resolution from HERE.

MTK phones with UBIFS file system:
Download your resolution from HERE.



IMPORTANT:

These are compiled recoveries for porting purposes only. DON'T take any of them and flash it in your phone as it is. It won't work, they include a dummy kernel. You need to port it to your device as I show in my guide, to make it work. Use them only if you have a kitkat kernel for your phone


CREDITS:
- Napstar-xda - for touch module;
- Philz-cwm6 - for get partition size method;
- xiaolu - for the new fonts;
- C3C0 - for initial mtk tweack hint - Unused now;
- Koush and all CWM team for the recovery;
- bgcngm for unpack/repack utils;
- sk8erwitskil for aromafm menu


RULES for posting your ports!
If you manage to port this to your device, add proper credits in your thread, post or article.
If you want that to be posted in a list with working devices, then post here a link to the thread or the post on xda (only on xda). Why not a free hosting link, like google drive, dev-host, mega-coz or other? Because if in the future you will port a new version, you have to replace it in that thread or post and the link from list remain the same.


My github source.


ATTENTION:
There is a possibility that the touch feature to not work in all phones. It was tested in many phones, and in some of them it doesn't work. There isn't a switch, a toggle or other method to make it to work, it depends on your phone touchscreen capability from recovery. If this doesn't work in your phone, I'm sorry, it happens, and my advice is to try something else.


Few clarifications:
  • I provided all necessary infos to help you to port it to your devices.

  • So, don't ask me anymore to port or to compile some recovery for your phone.

  • If you can't follow all these clear steps (with images) to do it by yourself, then maybe you are on the wrong forum.

  • It is ment to be ported to all MTK devices, but this doesn't mean it will work in all.

  • In some devices with a cheap screen display (usually those with anly one or two points of touch) there is a big chance to not work, or to work only partial.

  • If the recovery has the screen flipped, you need to use the non-touch version, and to compile it by yourself from source, or to ask a developer from your device to do it, with BOARD_HAS_FLIPPED_SCREEN true flag in device BoardConfig.

  • The main purpose for this recovery was to keep it under 6Mb, to fit in that small recovery partition that was used in these MTK phones.

  • If your phone's kernel is bigger than 4.3Mb and the recovery size is 6Mb, don't botter to try it. It won't work, because it will exceede those 6Mb.









Attached Thumbnails


Click image for larger version<br/><br/>Name:	CTR-3_0-kk-01.png<br/>Views:	N/A<br/>Size:	55.5 KB<br/>ID:	3059413
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-02.png<br/>Views:	N/A<br/>Size:	58.2 KB<br/>ID:	3059414
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-03.png<br/>Views:	N/A<br/>Size:	54.8 KB<br/>ID:	3059415
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-04.png<br/>Views:	N/A<br/>Size:	57.9 KB<br/>ID:	3059416
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-05.png<br/>Views:	N/A<br/>Size:	59.4 KB<br/>ID:	3059417
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-06.png<br/>Views:	N/A<br/>Size:	57.2 KB<br/>ID:	3059418
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-07.png<br/>Views:	N/A<br/>Size:	56.6 KB<br/>ID:	3059419
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-08.png<br/>Views:	N/A<br/>Size:	52.6 KB<br/>ID:	3059420
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-09.png<br/>Views:	N/A<br/>Size:	54.5 KB<br/>ID:	3059421
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-10.png<br/>Views:	N/A<br/>Size:	58.6 KB<br/>ID:	3059422
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-11.png<br/>Views:	N/A<br/>Size:	54.4 KB<br/>ID:	3059423
 

Click image for larger version<br/><br/>Name:	CTR-3_0-kk-12.png<br/>Views:	N/A<br/>Size:	78.9 KB<br/>ID:	3059424
 

Click image for larger version<br/><br/>Name:	port_recovery3.png<br/>Views:	N/A<br/>Size:	107.0 KB<br/>ID:	3059425
 

















mardi 9 décembre 2014

Need help porting a recovery to my device topic






i i tried cwm builder thingie but it doesnt work now and im not smart enough to compile a recovery so i was wondering if someone can do it for me here is my stock recovery img please help me

http://d-h.st/9Dp

this is the device http://www.technodoze.com/2014/08/uf...and-price.html






 

© 2013 Mobile Probleme. All rights resevered. Designed by Templateism

Back To Top