Related
Hey im porting this rom to the Jewel or HTC EVO 4G LTE and I see no HTC related files for kernel, build, and Vendor folders.
Should I use the same folders from a different port like Evervolv and just copy and paste the folders or should I do all the stuff manually?
EDIT: Should I just edit the local manifest so it can pick up the appropriate files?
I was hoping it would be as easy as that but something tells me no (still hoping)
lreyes said:
EDIT: Should I just edit the local manifest so it can pick up the appropriate files?
Click to expand...
Click to collapse
yes - that would be the start if you already have an
existing device kernel and vendor folder for your device
It may require some minor changes in the device tree to
work with the pure AOSP build we are using.
So the closer the original device is to AOSP the better
maxwen said:
yes - that would be the start if you already have an
existing device kernel and vendor folder for your device
It may require some minor changes in the device tree to
work with the pure AOSP build we are using.
So the closer the original device is to AOSP the better
Click to expand...
Click to collapse
I'm using Evervolv source and its pure AOSP with some changes. Also it supports my device. So ill just move the folders to the OMNI source and then I'd do lunch or do I do brunch?
Sent from my EVO using XDA Premium 4 mobile app
I was thinking the same thing I now see that they added android_device_htc_msm8960-common to the omnirom repository so we may just be able to edit the localmanifest to pull some of the device specific stuff from another AOSP based rom repository (like CM) and preform an extractfiles for the device specific blobs and it should work . I am going to try when I have some time for the One S.
Code:
/*
* ~ DO READ THIS BEFORE ATTEMPTING~
* Iam not here to guarantee any successful PORTING. nor i am responsible
for bricked devices, dead SD cards, or a broken device. 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. But I will try
my best to explain all the necessities, so you won't mess up your Device.
*
~END
*/
Hello XDA'S Today i'm back with a useful guide/tutorial for ANDROID ROM PORTING
may have tried porting roms to their phones and has been succefull but most of the case is that we being end up in bootloops or cwm errors
So i'm dedicating this post for all users how are having a craze of rom porting or for atleast those wgo wanted to try rom porting
SO LETS START
There are two phases or rom porting
1) Its finding the correct port and source roms for ROM PORTING copying the files which is explained here
2) After a succefull port also the rom may not work properly ,we have to sort out the bugs to for a rom to become perfectly working
So with no more blahh blahh blahh Lets start the PORTING procedure :fingers-crossed: :fingers-crossed:
Click to expand...
Click to collapse
And lastly Before you a port a ROM, make sure you asked permission from the Developer!
What you'll need:
WinRAR/7zip
Notepad++ (When developing, always use this)
Android SDK (For Logcatting & DDMS)
Some basic knowledge about Android
If you are on Linux/Unix/BSD use your favorite Archiving Tool & Text Editor.
Click to expand...
Click to collapse
What is base Rom:
The ROM which is Developed For your Mobile..
You can use either CM or any other AOSP roms as your Base ROM
Click to expand...
Click to collapse
What is Port Rom:
The Rom Which you want to port to your Device.
Make sure that the rom has most of the hardware specifications as of your base rom
Click to expand...
Click to collapse
STEP1;
Take any clean CM9, AOSP, CM7, CM10 ROM which is running on your device as Base ROM
Click to expand...
Click to collapse
STEP2:
Extract it Using Winrar.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
STEP3:
Take the ROM you want to port. This Port ROM. Extract it also using Winrar.
Click to expand...
Click to collapse
STEP4:
Delete app, Framework, Fonts and Media folder in System Folder of Base ROM.
Click to expand...
Click to collapse
STEP5:
Now copy app, Framework, Fonts and Media folder in System Folder from Port rom to base rom system folder.
Click to expand...
Click to collapse
STEP6:
Now open etc folder in both the ROMs folder.
Click to expand...
Click to collapse
STEP7:
In etc folder of base ROM open permissions folder and copy all the permissions files in Port rom to your base ROM folder except platform and handheld_hardware
Click to expand...
Click to collapse
STEP 8: .And Then open init.d Folder in Base ROM and Delete Every thing except banner and then copy all the files inside init.d folder of port ROM to Base ROM.
Click to expand...
Click to collapse
STEP9:
Now open buid.prop file using Notepad++ and make changes to these of Base Rom as you wish.
ro.build.id=
ro.build.display.id=
ro.build.date=
ro.modversion=
Click to expand...
Click to collapse
STEP10:
In build.prop file change these to same as Port Rom build.prop values.
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
ro.cmversion=
ro.modversion=
Also Copy anything you Find Extra in ADDITIONAL BUILD PROPERTIES related to theme..
Click to expand...
Click to collapse
STEP11:
COPY THE set_perm Lines in META-INF/com/google/android/updater-script From Port to Base ROM After Deleting set_perm lines in Base ROM's Updater-Script.
Click to expand...
Click to collapse
STEP12:
If You find any extra file or folder in system folder of PORT rom than copy them to your base rom system folder.
Click to expand...
Click to collapse
STEP 13:
Last Step to ZIP THE FOLDERS IN ONE..
SELECT META-INF, system, boot.img(if it is having), data(if it is having).
Right Click and Select Add to Archive..
Select Zip..
Type the Name.
Click OK..
Click to expand...
Click to collapse
HERE THE BASIC ROM PORTING IS OVER BUT FOR SOME SPECIFIC COSTUME ROMS WE NEED LITTLE MORE STUFFS TO WORK ON ,THEY ARE SHOWN BELOW
ONLY FOR MIUI ROMS :
Copy telocation.db and yellowpage.db From /system/etc folder to yours..
Copy content-types.properties file From /system/lib to yours..
Copy invoke-as from miui4 rom to /system/xbin and give it permissions on updater-script
set_perm(0, 0, 06755, "/system/xbin/invoke-as");
Note:It is needed for backup & themes app to work
Copy liblbesec.so from miui 4 to /system/lib and give permission on updater-script
set_perm(0, 0, 0755, "/system/lib/liblbesec.so");
It is needed for superuser app from miui to work
Change values Some of the Values in build.prop of your ROM:
ro.build.id=MIUI
ro.build.display.id=MIUI
ro.build.version.incremental=2.x.x (version number)
ro.config.ringtone=MI.ogg
ro.config.notification_sound=FadeIn.ogg
ro.config.alarm_alert=GoodMorning.ogg
ro.config.sms_received_sound=FadeIn.ogg
ro.config.sms_delivered_sound=MessageComplete.ogg
Click to expand...
Click to collapse
FOR ParanoidAndroid And PAC:
Copy paranoid folder inside system/etc to yours..
Go to META-INF/com/google/android/Updater-Script of your base ROM and open it with Notepad++
Copy this line:
set_perm(1000, 1000, 0644, "/system/etc/paranoid/properties.conf");
Specially For PA:
Now Open Build.prop in /system with Notepad++
Copy these lines in Additional Properties of Build.prop:
Depends on Resolution Of your device can be pa_hdpi/pa_mdpi/pa_xhdpi. Change it according to your device.
ro.pa.family=pa_mdpi
Depend on pa version. Replace x.xx with the version of PA you are porting.
ro.pa.version=x.xx
Click to expand...
Click to collapse
Specially For PAC Rom:
Now Open Build.prop in /system with Notepad++
Copy these lines in Additional Properties of Build.prop:
Replace the x.x.x with your PAC Rom version
ro.pac.version=x.x.x
Customize these lines according to your wish.
ro.pacrom.version=mesona_PAC_jb-alpha-v19.0.0
ro.modversion=mesona_PAC_jb-alpha-v19.0.0
Depends on Resolution Of your device can be pa_hdpi/pa_mdpi/pa_xhdpi. Change it according to your device.
ro.pa.family=pa_mdpi
Depend on pa version. Replace x.xx with the version of PA you are porting.
ro.pa.version=x.xx
Modify this line according to your AOKP version
ro.aokp.version=mesona_jb-Milestone-1
Modify it according to your base ROM's build.prop
ro.cm.version=xxxxxxxxxxxx
Replace any line in Your build.prop which appear twice mainly ro.cm.version and ro.modversion
Click to expand...
Click to collapse
FOR SPECIFIC MANUFACTURE DEVICE
For HTC Devices:
To fix network auto select-
Decompile framework-res.apk
Go to \framework-res\res\values\bools.xml and change change <bool name="skip_restoring_network_selection">true</bool> to false
To Fix Graphichal issues:
Code:
Decompile framework.jar
Change these files with your base
smali\smali\android\os
Environment
SystemProperties
smali\smali\android\view
HardwareCanvas
HardwareRenderer$Gl20Renderer
HardwareRenderer$GlRenderer
HardwareRenderer
Click to expand...
Click to collapse
IF YOU ARE HAVING BOOTLOOP THEN COPY THESE LIB FILES TO BASE ROM FROM PORT ROM:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
Click to expand...
Click to collapse
IF YOUR BASE ROM HAS ISSUES LIKE CAMERA ISSUE THAN YOUR PORTED ROM TOO WILL HAVE ISSUES.
NOW ZIP YOUR ROM AND POST IT BUT DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
TROUBLESHOOTING AFTER SUCCEFULL PORT
After a succefull port also there can be many bugs present which has to soved logically
here are somethings which can help in DEBUGGING
1) IF GALLERY FC :
open the system/framework and find framework-res.apk file[can use any extracting app]
in both the roms and go to res folder then to xml subfolder and copy and replace the storage_list.xml file from source to port rom
( framework-res.apk\res\xml\storage_list.xml)
Porting Wallpapers | Lockscreen Wallpapers | bootanimation
Usually you get a wallpaper/bootanimation that doesn't fit your device. Here's a quick tutorial on how to port it to your device.
Download & Install FreeImageConverter then launch it.
For Wallpapers & Lockscreen Wallpapers:
Click Add Folder... and add the folder were the wallpapers are
Then click Advanced Convert...
Select Exact Size and set the image quality to 100
Set your Width and Height resolutions for your device.
Uncheck Add "Converted by www.freeimageconverter.com"
Select Leave the same file name and leave the Postfix & Prefix empty. Then set your output in a folder.
For bootanimation:
Extract /system/media/bootanimation.zip OR /data/local/bootanimation.zip OR /system/customize/resource/bootanimation.zip (For Oxygen ROM, the bootanimation is built into the framework-res)
Do the steps above
Move the new resized folder(s) into your bootanimation workspace
Edit the desc.txt to match your device resolutions
Zip the contents ( folder_name desc.txt )
Set compression method to Store
Delete the extracted bootanimation files
Make sure this new bootanimation.zip is in PORTED
Click to expand...
Click to collapse
Sources
http://cleanimport.xda/index.php?threads/1598713/
http://cleanimport.xda/index.php?threads/1908008/
Click to expand...
Click to collapse
Credits & Thanks to
# rishabh.raj37
# Peteragent5
Happy porting!
:laugh:
Click to expand...
Click to collapse
reserved
for clarification
This method gives bootloop too often. It works only for very similar devices like Xperia J & Arc or Huawei u8818
Yes. This method gives a lot of bootloops. It only can be used on devices with hairline differences between specs.
Sent from my GT-N7000 using XDA Premium 4 mobile app
lozohcum said:
This method gives bootloop too often. It works only for very similar devices like Xperia J & Arc or Huawei u8818
Click to expand...
Click to collapse
not really ,,i have tried porting with this and it worked succefullyy
:laugh:
may be you have to try it perfectly
1c3_5n0w said:
Yes. This method gives a lot of bootloops. It only can be used on devices with hairline differences between specs.
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
have you tried this methode,,iam sure it will work,,:laugh::laugh:
ArjunrambZ said:
have you tried this methode,,iam sure it will work,,:laugh::laugh:
Click to expand...
Click to collapse
I started porting roms about year ago so... yes I did, I tried many "methods". This works mostly for similar devices.
Now I'm trying to use source code
lozohcum said:
I started porting roms about year ago so... yes I did, I tried many "methods". This works mostly for similar devices.
Now I'm trying to use source code
Click to expand...
Click to collapse
yah trying with source code is the best way ,but this tut is for users who really cant get it using source :good:
Arjunramb456651 said:
Code:
/*
* ~ DO READ THIS BEFORE ATTEMPTING~
* Iam not here to guarantee any successful PORTING. nor i am responsible
for bricked devices, dead SD cards, or a broken device. 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. But I will try
my best to explain all the necessities, so you won't mess up your Device.
*
~END
*/
Hello XDA'S Today i'm back with a useful guide/tutorial for ANDROID ROM PORTING
may have tried porting roms to their phones and has been succefull but most of the case is that we being end up in bootloops or cwm errors
So i'm dedicating this post for all users how are having a craze of rom porting or for atleast those wgo wanted to try rom porting
SO LETS START
And lastly Before you a port a ROM, make sure you asked permission from the Developer!
HERE THE BASIC ROM PORTING IS OVER BUT FOR SOME SPECIFIC COSTUME ROMS WE NEED LITTLE MORE STUFFS TO WORK ON ,THEY ARE SHOWN BELOW
ONLY FOR MIUI ROMS :
FOR ParanoidAndroid And PAC:
Specially For PAC Rom:
FOR SPECIFIC MANUFACTURE DEVICE
IF YOUR BASE ROM HAS ISSUES LIKE CAMERA ISSUE THAN YOUR PORTED ROM TOO WILL HAVE ISSUES.
NOW ZIP YOUR ROM AND POST IT BUT DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
TROUBLESHOOTING AFTER SUCCEFULL PORT
After a succefull port also there can be many bugs present which has to soved logically
here are somethings which can help in DEBUGGING
1) IF GALLERY FC :
open the system/framework and find framework-res.apk file[can use any extracting app]
in both the roms and go to res folder then to xml subfolder and copy and replace the storage_list.xml file from source to port rom
( framework-res.apk\res\xml\storage_list.xml)
Credits & Thanks to
# rishabh.raj37
# Peteragent5
Happy porting!
:laugh:
Click to expand...
Click to collapse
Can you port an AOSP/CM based rom using a Manufacturer/maufacturer based ROM as the base (i.e. touchwiz rom)?
Click to expand...
Click to collapse
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed?
Sent from my SGH-I337 using XDA Premium 4 mobile app
---------- Post added 16th November 2013 at 12:02 AM ---------- Previous post was 15th November 2013 at 11:59 PM ----------
Neozx25 said:
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed? I would be using a rom that runs on another tab 2 10.1 but not for AT&T. Or even if i wanted an AOSP rom, would be that difficult?
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my SGH-I337 using XDA Premium 4 mobile app
HitBobLer said:
Arjunramb456651 said:
Code:
/*
* ~ DO READ THIS BEFORE ATTEMPTING~
* Iam not here to guarantee any successful PORTING. nor i am responsible
for bricked devices, dead SD cards, or a broken device. 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. But I will try
my best to explain all the necessities, so you won't mess up your Device.
*
~END
*/
Hello XDA'S Today i'm back with a useful guide/tutorial for ANDROID ROM PORTING
may have tried porting roms to their phones and has been succefull but most of the case is that we being end up in bootloops or cwm errors
So i'm dedicating this post for all users how are having a craze of rom porting or for atleast those wgo wanted to try rom porting
SO LETS START
And lastly Before you a port a ROM, make sure you asked permission from the Developer!
HERE THE BASIC ROM PORTING IS OVER BUT FOR SOME SPECIFIC COSTUME ROMS WE NEED LITTLE MORE STUFFS TO WORK ON ,THEY ARE SHOWN BELOW
ONLY FOR MIUI ROMS :
FOR ParanoidAndroid And PAC:
Specially For PAC Rom:
FOR SPECIFIC MANUFACTURE DEVICE
IF YOUR BASE ROM HAS ISSUES LIKE CAMERA ISSUE THAN YOUR PORTED ROM TOO WILL HAVE ISSUES.
NOW ZIP YOUR ROM AND POST IT BUT DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
TROUBLESHOOTING AFTER SUCCEFULL PORT
Can you port an AOSP/CM based rom using a Manufacturer/maufacturer based ROM as the base (i.e. touchwiz rom)?
Click to expand...
Click to collapse
no i dont think so,because cm /pa have modified source code ,which differ from manufacture rom hence ,,not possible ,u will possibly end in boot loop
Click to expand...
Click to collapse
Neozx25 said:
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed?
Sent from my SGH-I337 using XDA Premium 4 mobile app
---------- Post added 16th November 2013 at 12:02 AM ---------- Previous post was 15th November 2013 at 11:59 PM ----------
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Neozx25 said:
So i own a Galaxy Tab 2 10.1 from AT&T... If i wanted to port a 4.2.2 Touchwiz rom to my tablet, would the steps vary much from those you've listed?
Sent from my SGH-I337 using XDA Premium 4 mobile app
---------- Post added 16th November 2013 at 12:02 AM ---------- Previous post was 15th November 2013 at 11:59 PM ----------
Sent from my SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes of course ,this methode is for aosp or for cm roms and not for manufacture roms,,there are other guids for porting manufacture roms ,go search the forum
only boot loop no progress!!!
i had tried this method more then 4 times but it didnt worked....
rom is not booting up and its stucked on boot animation and shows no progress although i left it for an hour but still stucked....
any idea??
and for details...
i am porting chameleon OS built for htc one s just see this....-
android v is 4.2.2
so i used aokp 4.2.2(stable) first as base rom but i failed more then 2-4 times then i tried cm10.1 as base rom but still i am at bootanimation.
i had also used the three libs from the port rom and base rom as mentioned in the guide but still nothing is going good......:crying:
can you tell me that am i missing something or i should try other guides?
if your answer is that i should try other guides so please lead me to a guide.....
thanks.
regardslayboydroid
playboydroid said:
i had tried this method more then 4 times but it didnt worked....
rom is not booting up and its stucked on boot animation and shows no progress although i left it for an hour but still stucked....
any idea??
and for details...
i am porting chameleon OS built for htc one s just see this....-
android v is 4.2.2
so i used aokp 4.2.2(stable) first as base rom but i failed more then 2-4 times then i tried cm10.1 as base rom but still i am at bootanimation.
i had also used the three libs from the port rom and base rom as mentioned in the guide but still nothing is going good......:crying:
can you tell me that am i missing something or i should try other guides?
if your answer is that i should try other guides so please lead me to a guide.....
thanks.
regardslayboydroid
Click to expand...
Click to collapse
bro firstof all,, porting is not that easy as to read,,, here logcat is your only friends,,, get me the logcat
hmm
ArjunrambZ said:
bro firstof all,, porting is not that easy as to read,,, here logcat is your only friends,,, get me the logcat
Click to expand...
Click to collapse
okay just wait for a day...
and thanks for your quick reply..
playboydroid said:
okay just wait for a day...
and thanks for your quick reply..
Click to expand...
Click to collapse
okay
Good evening to all, first of all thanks for the guide.
The rom part, it works most of the things, porting is a rom for nexus 5 to take on g2.
I have problems with wifi, vpn and security in the setting menu.
Practically the vpn and security go on crash, while the wifi is active but can not find anything.
Do you have suggestions?
thanks
Sorry for my bad english
jokerpoker1 said:
Good evening to all, first of all thanks for the guide.
The rom part, it works most of the things, porting is a rom for nexus 5 to take on g2.
I have problems with wifi, vpn and security in the setting menu.
Practically the vpn and security go on crash, while the wifi is active but can not find anything.
Do you have suggestions?
thanks
Sorry for my bad english
Click to expand...
Click to collapse
it would only b possible if you could get a logcat about the problem,, and if the problem persist in the base rom,then its sure to be in ur port too,
ArjunrambZ said:
it would only b possible if you could get a logcat about the problem,, and if the problem persist in the base rom,then its sure to be in ur port too,
Click to expand...
Click to collapse
thanks for the reply, it is the first time I use logcat, this is what I said when I port ROM.un my friend was telling me That might be the update script.
Thanks
Inviato dal mio LG-D802 utilizzando Tapatalk
jokerpoker1 said:
thanks for the reply, it is the first time I use logcat, this is what I said when I port ROM.un my friend was telling me That might be the update script.
Thanks
Inviato dal mio LG-D802 utilizzando Tapatalk
Click to expand...
Click to collapse
yes when it coms to porting logcat is ur only friend,, well updater script doesn't have any relations with the rom actually its like a process to installing the rom as said, and fixing permision,,,
and please tell me when was this logcat obtained and this time get me a full logcat
Here is the kernel source for:
General Mobile Discovery Elite
Gionee Elife E7
These two devices using the same kernel source. You should use the defconfig from your own device to compile and use it with shared source.
Source link: http://www.burakgon.com/kernel-sources-for-general-mobile-discovery-elite-and-gionee-elife-e7-is-here/
Have fun while modifying!
XDA:DevDB Information
Gionee Elife E7 - General Mobile Discovery Elite Kernel Sources, a Kernel for the GiONEE Elife E7
Contributors
burakgon
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2014-04-01
Created 2014-04-01
Last Updated 2014-04-05
Thanks a lot burakgon. I knew you were the real deal! Can you please post your ROM as well which is used in discovery mobile? And your flash tools which you promised to release as well?
[OFF TOPIC]
@burakgon Sir i Need General Mobile Discovery Kernel Source... You Made ATOM ROM Having ATOM Kernel For General Mobile Discovery Which Means You Have its Kernel Sources... i Tried Kernel Sources Released By FLY For its Fly-IQ4410 But Those Sources Are Not Complete Lots Of Drivers Are Missing And There is No Hope From Other Rebranded Devices... its An Humble Request Sir
Sorry To Disturb You Here...
Thank You very very much
let my exams complete
i will port cm
if you can provide device tree it will be awesome
yasirmujtaba said:
if you can provide device tree it will be awesome
Click to expand...
Click to collapse
I will try
Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.
icoolguy1995 said:
Hi guys.
I am looking forward to support this awesome device. I got the source later i do the recovery and all stuff. Can anyone provide me stock boot.img and recovery.img.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2706689
burakgon said:
I will try
Click to expand...
Click to collapse
hey burakgon did you got correct sources from gionee
i heard you were talking to gionee support for problems with kernel sources
pls reply
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..
GTARaja said:
Ive tried upacking boot.img from my device replaced the zImage which i compiled from sources and again repacked it with the same ramdisk and flashed..The black screen appears. heard that sometimes the smaller size of ramdisk can be the culprit..
Click to expand...
Click to collapse
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.
Ravikirancg said:
not exactly the size of ramdisk but the offset. we need a custom mkbootimg binary. need to edit mkbootimg.c and then re run make recoverytools. try unmkbootimg.
Click to expand...
Click to collapse
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time
Ravikirancg said:
the sources that have been posted here might be correct but they (gionee) use a different (non standard) mkbootimg to pack it. that leads to issues. simply put, take their boot image or recovery, unpack it, without making any changes, repack it. the new file will be smaller in size. and device wont boot up if you flash them.
Click to expand...
Click to collapse
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.
GTARaja said:
ive tried with different offsets from xperia z1 n nexus 5 didnt work.....not tried editing mkbootimg.c...ill try it later...btw can u compile it once for us if u have some spare time
Click to expand...
Click to collapse
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
dhirajranger said:
afaik if gionee uses a custom mkbootimg wouldn't they have provided the custom tool to general mobile. if so burakgon could have provided us with same. I at least request him to provide us with general mobile firmware so as to test the theory that they might have made small hardware changes
in general elite.
Click to expand...
Click to collapse
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..
Ravikirancg said:
surely.. here you go https://www.dropbox.com/s/e62wf141ahcqy7j/mkbootimg
when you repack, keep base address as 0x0.
well, I dont know much about Gionee to assume that it would have given the binary. afaik, it didnt even release the kernel sources.. let alone explain these. then again, I hope Gionee is dev friendly and helps us out. but I can assure you of one thing. Gionee does not use the standard methods. It surely has a messed up software on the device. it took me a week to get adb working properly on the terminal. Hell, I still cant get it to boot into fastboot mode..
P.S., It seems they use some signature for signing the recovery. I just unpacked the recovery and repacked it using mkbootimg. Its initial size was about 11mb. the newer one barely had a size of 8.7mb.
P.P.S., If some one is in touch with Gionee or get in touch with them, please pm..
Click to expand...
Click to collapse
Missing dt.img??
Sent from my ST25i using Tapatalk
AnoopKumar said:
Missing dt.img??
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..
They use some dtb.img.......
Have a look at dtb.img method
Sent from my Discovery Elite using XDA Premium 4 mobile app
This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
Ravikirancg said:
ah! googled that up.. interesting.. the mkbootimg xperia ZU guys use syncs up with the one I built.. I will test that out..
Click to expand...
Click to collapse
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk
AnoopKumar said:
This source is not good may be missing display driver.. Only giving black screen after booting.
Sent from my ST25i using Tapatalk
---------- Post added at 12:40 PM ---------- Previous post was at 12:38 PM ----------
You need to generate dt.img for for your complied zImage
Sent from my ST25i using Tapatalk
Click to expand...
Click to collapse
yes I did that.. and as you mentioned, I get a white screen.. actually, my kernel itself didnt compile.. but I had some dts files and built a dt.img out of it.. if you built a stock kernel, mind sharinng your dt.img?
deleted
Uchiha_Dev said:
Hello guys, I have a holly 3c lite and it's the original version and not a clone. The twist is I can port MT6592 ROMs to it and boot it up fairly easy but MT6582 ROMs after porting don't work at all. There is a black screen of death after optimizing apps has been completed
Click to expand...
Click to collapse
Hey I don't know whether u manage to solve this problem but u have to change some init.rc file also fstab. I also have same issue long ago while porting but now fixed don't know exactly what I have changed.
I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?
What have you done? Device tree something else?
Nope. Just changing libs here and there, according to this guide. I'm still noob in porting roms so I can't do much.
amirarsyad97 said:
I came across CM12.1 rom for Lenovo K3 Note on needrom. Considering that K3 have the same chipset as ours, I've been thinking that it can be ported to our device.
I've tried to port it past few days but failed. Any developer would come up and try to port it?
Click to expand...
Click to collapse
Did you edit the updater script?
Gibz97 said:
Did you edit the updater script?
Click to expand...
Click to collapse
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
If you have an idea for kernel, I'll help you
amirarsyad97 said:
Yes. I'm actually having problem in repacking system.new.dat files. The same as the guy face here. Finding the solution require me to learn Linux. I'm still new at Linux, so I need some time to learn.
Other than that is okay (perhaps). I followed some other guides like http://forum.xda-developers.com/android/development/guide-how-to-port-lollipop-based-roms-t3223938 and http://forum.xda-developers.com/showthread.php?t=2707438.
Oh and one more thing, the rom is ported by @Cheshkin. I've tried to seek his permission to port the rom through pm, but still no answer. So I cannot post the rom here (if I done porting it) without his permission.
Click to expand...
Click to collapse
Let's wait for the response then
Would be graet to see CM to release this device's potential. Especially since HTC is taking it's sweet time with 6.0 update and 5.1 was officially skipped.
Anyway if you would need some testers I would gladly help.
Good news! The permission has been granted. I will try my best to port this rom.
And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app
Dragonfail said:
And what with 820n?
Sent from my HTC Desire 820 using XDA Free mobile app
Click to expand...
Click to collapse
We don't have 64-bit kernel sources for 820n MSM chipset
Hi @amirarsyad97, so did you manage to extract system files?
Gibz97 said:
Hi @amirarsyad97, so did you manage to extract system files?
Click to expand...
Click to collapse
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.
amirarsyad97 said:
I already did, but I can't repack it. So instead I tried looking for other roms while staying away from dat files - cm12.1 ulefone be touch 2 and blisspop k3 note.
Now I'm having problems with the kernel. The rom won't boot at all, the worse I can't get the dmesg.
I don't have much free time to explore kernels in detail. If anybody can help me with porting the kernel, it would be a pleasure.
Click to expand...
Click to collapse
I will try porting the kernel using the kitkat kernel as base when I find time
Unfortunately, I did not succeed, I could not even get into the bootanimation. Hope someone can help us.
I am now trying to squeeze the Lollipop system partition so that we can liberate some more free space for the internal storage, hope it works
That would be the coolest thing???
Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it
Gibz97 said:
Hello guys hope you have been doing great, Was too busy with school, exams and stuff.
Good news!! I have finally managed to boot into CM 12.1 after I successfully ported it today.
It's lightning fast but has some bugs: USB, bluetooth and Sim don't work currently and it needs some resizing of the framework images.
I will try to work on it until Sunday and hopefully someone else can take over with modifying it
Click to expand...
Click to collapse
I was wondering how you can make the kernel work. Anyway good work!
amirarsyad97 said:
I was wondering how you can make the kernel work. Anyway good work!
Click to expand...
Click to collapse
Use this kernel and build.prop and use the original system (don't replace with stock files) https://mega.nz/#!c4USzSTL!rXmsjMYaxR9ECwNeiMjissLPuFRLBWBUSLIuwiBFwQk
Almost everything works right now except Bluetooth, camera and Sim
Great work keep it up
Sent from my HTC Desire 820 dual sim using XDA-Developers mobile app