[ROM][InDev] Help Wanted Custom ROM Option for SGH-I857 - Miscellaneous Android Development

I am currently attempting to port Cyanogenmod as well as Clockworkmod to a device known as the Samsung DoubleTime SGH-I857. It is a very unique end of life handset that I think needs a little hacking attention. So far I have found most of the partitions names and sizes on the device, and I have pulled the boot.img and recovery.img out of a firmware file for it that I found online. I am confident in my skills but I am often running into trouble when it comes to building with Cyanogenmod source. I am currently using the Froyo branch as I believe it might be easier to build with the same version that is currently on the phone. I eventually plan to some how build gingerbread for it but i am trying to build what I can as of right now.
I am making this thread to report progress and hopefully get advice from those who are more experienced than me. Any help or advice is deeply appreciated.

Update*
I finally got my build enviornment figured out, I chose Gingerbread because Froyo didn't like me for some reason...
I used the mkvendor.sh method as recommended on the Cyanogenmod Wikipage for porting. I looked through all of the files and everthing seems to be correct except the recovery.fstab which is saying that the system, cache, data, etc. partitions are in all sorts of diffrent file systems; and are mounted in places called the same name as them. The sdcard partition seems to be correct and I'm assuming that I need to manually put in the data. You can look at the files below and tell me if I'm on the right track. I cannot locate any recovery boot or misc partitions using shell commands. There were however there were loop and bml partitions, but they did not appear in the mount or df command.

Update*
I got sick of getting errors regarding my device not existing and random stuff about an HTC ACE. So I plugged the recovery.img from the firmware package into builder.clockworkmod.com and gave it a go. It built sucessfully but I am afraid of the recovery.fstab not being correct.
Upon inspection of sibiling phones most followed a similar pattern or stl## partitions for cache, data and system. Though they all have boot defined as boot and recovery as recovery; both of which with a BML file system. I also noticed the sibilings said their cache, data and systems were ext4 with a 2nd file system of rfs. This is just confusing to me...
I am unsure if I should flash it. I'm confident that the recovery.fstab's recovery and boot partitions are correct but what will happen if I get one of the partitions wrong.
The CWM recovery builder output is here: http://jenkins.cyanogenmod.com/job/recovery/56329/
A sibiling phone example would be: https://github.com/CyanogenMod/android_device_samsung_fascinate/blob/gingerbread/recovery.fstab
Anything other files I am happy to give out.
How I feel about my progress:
{
"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"
}

Due to my lack of experience, and fear of hardbricking my new DoubleTime, I will be postponing my developement of the Gingerbread port to the Doubletime. My priority now will be learning as much as possible about the device.
To Do List (In Order)
1. Find correct Odin version for flashing.
2. Create Froyo ROM that will maximize freespace.
3. Create working recovery.
4. Build Gingerbread kernel.
5. Port over Gingerbread.

I've recently been looking comparitivly at custom ROMs and so far I think the best option might be stock AOSP. I have also been looking into ways to flash onto the phone but ODIN 1.85 doesn't seem to work. It can't be my antivirus as far as I know because I've added firewall exceptions to Odin.
To Do List (in order)
1. Find way to flash things to Doubletime
2. Make Froyo based AOSP
3. Build Gingerbread kernel.
4. Port Gingerbread
(Porting CWM should probably be in there somewhere)

Progress?
legojr said:
i've recently been looking comparitivly at custom roms and so far i think the best option might be stock aosp. I have also been looking into ways to flash onto the phone but odin 1.85 doesn't seem to work. It can't be my antivirus as far as i know because i've added firewall exceptions to odin.
To do list (in order)
1. Find way to flash things to doubletime
2. Make froyo based aosp
3. Build gingerbread kernel.
4. Port gingerbread
(porting cwm should probably be in there somewhere)
Click to expand...
Click to collapse
did you give up on this?

Teknodad1974 said:
did you give up on this?
Click to expand...
Click to collapse
No I haven't but my schedule has not allowed for a lot of time to be dedicated to this. I also am very new to this and I'm taking a lot of baby steps.
The number one problem right now is there doesn't seem to be any way of flashing CWM to the phone as all of the Odin versions/cables/computers I've tried have failed.

Well no better way to learn than hands on and on your own... Good luck! I have one of these worthless phones laying around to give to my youngest girl 6. It's just sucks it's stick on Froyo 2.2
Sent from my SGH-I777 using XDA Premium 4 mobile app

I believe I may have a correct recovery.fstab now I'll run this through Clockworkmod Builder now and hopefully get Odin 1.87 to flash it. If at anytime anyone thinks I'm doing something wrong PLEASE TELL ME. I'd rather not have another hardbricked Doubletime.

Honest to goodness I need some help here I'm trying really hard but I can't seem to get anything right... Odin doesn't seem to work, CWM Builder doesn't even identify the name of the phone, and all of the code available for the Doubletime from Samsung makes almost no sense to me. I do enjoy doing this but I've made almost no progress at all.
As of right now the primary effort needs to be on finding a way to flash CWM onto the Doubletime. The issue being if CWM builder is giving out KitKat level recoveries I doubt the Doubletime could handle it. The only way I can see a reliable CWM img getting built is if we use Cyanogenmod 6, which will require proprietary blobs, and those will be a pain to get since extract-files.sh doesn't seem to be available for the Doubletime as far as I know.
I've started manually finding the blobs by finding files that are similar to those found in the device-vendor-blob.mk of some other Samsung Froyo devices. The link to it is here
If I'm going in the right direction someone please tell me...:crying:

​Well it finally feels nice to know what your doing! While going file by file through the phones system directory might do it, I can't deny that I may have absolutely no idea what I'm doing. So with that lovely feeling in my heart I will be finding each of the parts inside of the DoubleTime and will looking at other phones that have those same parts and copy the blobs specific for them over to the github page I made. Anything that's on the DoubleTime but not in the blobs that I copied I'll put in a miscellaneous section in the vendor-blobs.mk file. So far here is what I know we'll need part wise, and what I know part wise.
List o' part we might need (totally could be wrong):
Bluetooth: ???
Wi-Fi: ???
Camera: ???
Sensors: ???
Audio: ???
Graphics: Qualcomm Aderno 205
GSM: ???
GPS: ???
Media: ???
DRM: ???
DSP: ???
USB: ???
​The chipset is a Qualcomm MSM7230, looking at apps that gather information about the device I've come to the conclusion that the phone is running on an extremely generic Android build and is not even really optimized for the devices hardware. The phone seems to think that it has an ARMv6 processor while in fact it has a v7.
​That adds to my other phone binary preference. Add anything you thing might be helpful! I'm a total noob at this and I need all the help I can get. :|

Legojr said:
​Well it finally feels nice to know what your doing! While going file by file through the phones system directory might do it, I can't deny that I may have absolutely no idea what I'm doing. So with that lovely feeling in my heart I will be finding each of the parts inside of the DoubleTime and will looking at other phones that have those same parts and copy the blobs specific for them over to the github page I made. Anything that's on the DoubleTime but not in the blobs that I copied I'll put in a miscellaneous section in the vendor-blobs.mk file. So far here is what I know we'll need part wise, and what I know part wise.
List o' part we might need (totally could be wrong):
Bluetooth: ???
Wi-Fi: ???
Camera: ???
Sensors: ???
Audio: ???
Graphics: Qualcomm Aderno 205
GSM: ???
GPS: ???
Media: ???
DRM: ???
DSP: ???
USB: ???
​The chipset is a Qualcomm MSM7230, looking at apps that gather information about the device I've come to the conclusion that the phone is running on an extremely generic Android build and is not even really optimized for the devices hardware. The phone seems to think that it has an ARMv6 processor while in fact it has a v7.
​That adds to my other phone binary preference. Add anything you thing might be helpful! I'm a total noob at this and I need all the help I can get. :|
Click to expand...
Click to collapse
I have this phone and would like a little of hacking on it. Have you gotten anything?

migui0401 said:
I have this phone and would like a little of hacking on it. Have you gotten anything?
Click to expand...
Click to collapse
So far all I got is a plan. Although I do have a recovery.img of CWM 6 from the Clockworkmod builder but the issue is it might not even work. Also as of right now I haven't found a way to flash anything to the DoubleTime. Although I have a theory that Odin on Windows XP might work. If you know anyways of flashing that are universal or something I'm all ears.

Legojr said:
So far all I got is a plan. Although I do have a recovery.img of CWM 6 from the Clockworkmod builder but the issue is it might not even work. Also as of right now I haven't found a way to flash anything to the DoubleTime. Although I have a theory that Odin on Windows XP might work. If you know anyways of flashing that are universal or something I'm all ears.
Click to expand...
Click to collapse
Can you create a flashable zip file for flashing via stock recovery, i mean a recovery which just opens flashing it everytime you need it, there some like this.

migui0401 said:
Can you create a flashable zip file for flashing via stock recovery, i mean a recovery which just opens flashing it everytime you need it, there some like this.
Click to expand...
Click to collapse
I've heard about that but I'm not sure if a stock recovery can flash a recovery on itself.
Besides a recovery.img that we know will work is needed for that and well... we don't really have one.
Being a noob I'm not sure how much is testable before flashing but I believe that those binary files are going to be needed. Do we just need the vendor-blobs.mk file to copy everything in system/lib, system/bin and system/etc directories?

Legojr said:
I've heard about that but I'm not sure if a stock recovery can flash a recovery on itself.
Besides a recovery.img that we know will work is needed for that and well... we don't really have one.
Being a noob I'm not sure how much is testable before flashing but I believe that those binary files are going to be needed. Do we just need the vendor-blobs.mk file to copy everything in system/lib, system/bin and system/etc directories?
Click to expand...
Click to collapse
Search for guide for creating the flashable zip, this is the better way to get a fast recovery working in any device, about the vendor-blobs.mk, i have not tried to create a recovery, so i can't help.

migui0401 said:
Search for guide for creating the flashable zip, this is the better way to get a fast recovery working in any device, about the vendor-blobs.mk, i have not tried to create a recovery, so i can't help.
Click to expand...
Click to collapse
How much experience at Android hacking do you have?

Legojr said:
How much experience at Android hacking do you have?
Click to expand...
Click to collapse
I'm not a great here just like the contributors or reconigzed, but I can do something, do you need help?

migui0401 said:
I'm not a great here just like the contributors or reconigzed, but I can do something, do you need help?
Click to expand...
Click to collapse
Well I'm no expert but we're eventually going to need to find a way to build Gingerbread for the DoubleTime. If you know the basics of a Cyanogenmod build enviornment that would be cool! If you could maybe look for any source code for the DoubleTime that would also be the best! Those are the only things I can think of. I don't really know much...

Legojr said:
Well I'm no expert but we're eventually going to need to find a way to build Gingerbread for the DoubleTime. If you know the basics of a Cyanogenmod build enviornment that would be cool! If you could maybe look for any source code for the DoubleTime that would also be the best! Those are the only things I can think of. I don't really know much...
Click to expand...
Click to collapse
I have the stock firmware extracted, the boot.img and recovery.img.

Related

How to Port a ROM to Milestone2

As lately some people are asking me about ROM porting I decided to create this new thread where we can share knowledge about this hard task.
Please note this is a Dev talk thread, so DON'T ASK about fixing a particular ROM problem here. Also don't ask questions like "My phone is bricked! please help!". This IS NOT the appropriate place for it. There are plenty of other threads to help you out.
Also note that this is not a step by step guide (and not a guide at all), it's just a point where you can start from. Android is a very complex system and there are many things I don't know yet. So, research and hard work is what you need to learn it deeply. My first tip is Google really works. Don't be afraid to search
Ok, to the basics. Porting a ROM is no simple task. It requires advanced understanding of how android works and how it is organized. Previous Linux/Unix knowledge helps A LOT. As android is based on this O.S. there are many similarities between both. In fact many ppl consider android to be a kind of linux distro.
The very first task to port a ROM is finding a device which is compatible with your own. For example Defy/Milestone2. Then you are going to choose a ROM to port to your device.
As our devices (Milestone2) have a locked bootloader we now need to find a system image that have a compatible kernel with the ROM we are trying to port. This is mainly based on trial and test and takes a long time. You'll be ending flashing your phone several times with RSD Lite. You should learn how to use MotoAndroidDepacker and how to create a fixed SBF.
The basic procedure to try that:
1. Open original ROM update.zip and remove any files/commands that flashes boot/devtree/recovery/anything.
2. Install this new file on your phone via CW Recovery.
3. Boot into bootmenu and enable ADB so you can read logcat while phone boots.
4. Choose Boot/Normal. If your ROM uses 2nd-init you will need to place/edit/adapt bootscripts into bootmenu 2nd-init folder.
5. Check logcat for errors:
- If you're getting HAL errors you're going to need a new kernel;
- If you can start android without getting HAL errors but still getting errors and bootloop on android animation you should try to replace libs with appropriate original ones.
6. Once you are able to boot android you should test it's features to see what needs to be fixed.
This is what I have to say for now. The thread is now open for discussion.
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
jorgebaruchi said:
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
Click to expand...
Click to collapse
It may be possible, but you'll have a hard time fixing the baseband.
You may have to mod the init.rc scripts and find the right radio binaries (rild is one of them) and drivers.
Ask those ms1 people for help, if they are still with the same phone...
Sent from my Milestone 2 XDA App
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
i guess it is second-init. but not sure
thanks a lot for this !!!
WeeDv2 said:
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
Click to expand...
Click to collapse
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
sahilarora911 said:
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
Click to expand...
Click to collapse
Don't worry, this is the right place
As for your question: yes you can work in windows if you like, but using at least a Linux VM is more productive. I don't have a full list of applications to give you, as different mods may require different tools, but I advice you to have at least:
- Notepad++ (essential for editing text files and keeping linux end-line format);
- dsixda's Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
- 7zip (or some other compress tool you like)
- Moded putty for ADB as working with windows command prompt really suck (http://forum.xda-developers.com/showthread.php?t=803225)
- Oracle Virtual Box (if you are going to use linux VM).
r2beta0 said:
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
Click to expand...
Click to collapse
Thanks again r2beta
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
sahilarora911 said:
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
Click to expand...
Click to collapse
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
r2beta0 said:
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
Click to expand...
Click to collapse
I know a bit about virtual box but as I said I'm not allowed to have softwares not approved by the IT team to be present on the system. Though I can get away with small things like notepad++ and 7-zip, having virtual box on my system may raise some eye brows.
I'm trying to arrange an alternative system.
Me neither. I must do almost everything at home, and at this very moment I simply don't have any free time. I'm afraid you're not going to see me here very often anymore (maybe in a few months? a year? well, it might be a bit too late for milestone2...)
hi. Have a question, I want to remove baseband from a flashable zip (lets say, CM7 from Tezet) , is it posible? I dont know where to look for it (baseband). Thanks!!
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
---UFO--- said:
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
Click to expand...
Click to collapse
Ok thanks for the info.
Sent from my A953 using XDA
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Megalith27 said:
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Click to expand...
Click to collapse
I meant to get to it last night, but I was tired after work and fell asleep watch tv. Eventually, later tonight, I'll be uploading PA for MS2. Check my Defy PA thread in 12-14 hours cause I'm about to go to work and I'm not gonna feel like making a MS2 PA thread or updating my Bravo PA thread -- but the Defy Thread is always up to date when I put out new roms.
Also, I'm looking to get either a Defy or MS2 -- I've heard that there's 3G issues with AT&T users (which I am) with the MS2 -- Apparently the MS2 has different 3G frequencies than AT&T. Are there any AT&T MS2 users who are knowledgeable about that? While I can deal with no 3G, edge only, calls only -- I need to make sure I can at least do that before I commit to something.
I'd rather have the MS2 because I want a hw keyboard and I don't have the $300+ to try and get a Photon Q LTE from eBay (and I don't have to change up my repos if I get a MS2). If anyone here knows of a phone that's AT&T compatible, Defy code compatible, and has a keyboard, please let me know.
Thanks.
//Normally I'd post the latter half in the Q&A section, but ya'll don't have one so I'm just gonna piggyback
//My Bravo doesn't have a Q&A page either -- it needs one that's not my PM box...Don't PM me on how to root your phone and flash CM7 -- read one of the 5 guides on the first page of both General & Dev...:silly:
Ok devs need some help here.
I am trying to port a rom to our Milestone 2...but it bootloops on rom animation.
I tried to logcat it but I don't think it gets as far as adb server to detect the device.and just keeps saying "waiting for device"...so I end up with no logcat to diagnose the problem.
I can logcat my current working rom but only after the phone boots....am i missing something here? please, help
Any help is very much appretiated.
Thanks a lot in advance

[Q] Creating Custom ROM

Hello, I'm new to all this Android stuff (I don't even have a phone yet, but its on it way)
I have been reading up on custom ROM creation but there are some things I don't quite understand.
Let's say I have a phone in Android 2.3. I want to create an Android 4.0 ROM to put on the phone.
Now... to compile Android 4.0 I need the drivers for my phone (which I doubt I will ever have access too since its only a cheap Android with a MediaTek CPU)
So I have a 2.3 ROM that contains all the compiled drivers and the Android 4.0 source code.
Is it possible to compile 4.0 and replace the zImage (if I'm correct) with the 2.3 zImage. From what I have read, that's where all the drivers are stored.
I guess its not that simple since I also think the zImage contains the OS. If so, is it then possible to extract the zImage and replace the invalid driver files in 4.0 with the correct drivers from 2.3?
Also, I think my phone will arrive with an annoying UI, is it possible to just get any 2.3 ROM (that doesn't have an annoying UI and shares the same CPU as my phone) and replace the zImage in that with my phones 2.3 zImage?
Sorry, if my questions are stupid but this is all new to me. I've tryed to read up on this but nothing is straight to the point.
Thanks
Anyone there?
try out some roms first. see what you like and dont like. it'll probably give you a better idea for how you would make your own rom.
I don't think you could just port an entire zimage to ICs and say it will work (it might not even compile i think). It won't work. You could probably take some drivers' code (screen, speaker, etc), modify them a bit so it compiles, and test to so if it works. You more than likely have to modify the ICS code also so it works. And the zimage is just the kernel no? And the kernel really only has to do with low level system processes, drivers, etc. I think UI's and such are more fitted in frameworks and such.
Personally if it was so easy to port ICS by simply replacing the zimage or file with another, ICS would have been ported to many devices, fully working, by now.
Kailkti said:
I don't think you could just port an entire zimage to ICs and say it will work (it might not even compile i think). It won't work. You could probably take some drivers' code (screen, speaker, etc), modify them a bit so it compiles, and test to so if it works. You more than likely have to modify the ICS code also so it works. And the zimage is just the kernel no? And the kernel really only has to do with low level system processes, drivers, etc. I think UI's and such are more fitted in frameworks and such.
Personally if it was so easy to port ICS by simply replacing the zimage or file with another, ICS would have been ported to many devices, fully working, by now.
Click to expand...
Click to collapse
Yeh, but my problem is I don't have the drivers for the phone. I just have the stock ROM that come with it.
Is not that simple. I am 99% sure that you can't do that.
The phone I'm getting has a horrible theme on it. Its running Android 2.3
I have the ROM for a very similar phone (also using Android 2.3), uses the exact same CPU so it should be compiled using the correct platform.
Is it possible to use that phones ROM but replace it with my phones Kernel and .prop (so it has all my phones drivers and settings etc...)?
the hard work required in making a custom rom
I think you can take from the stock rom and compared with existing custom rom
but some sources are not shared freely as an example Tegra
CMIIW
I will mess about with the ROM when I get my phone. Hopefully I wont brick it...
I too am fairly new to android. I spent a couple weeks reading and watching TONS of youtube videos on how to ROOT and Unlock my bootloader. My best advice from one n00b to another would be to do the same. In particular...research how to do it on YOUR phone. Also, Roms are device specific. I recommend you finding the forum here on XDA for your phone and read up on whatever ROMS are available here. This might not be the ONLY place to find ROMS, but this place simply rocks! Once you get your device rooted and if necessary, your bootloader unlocked...you can easily try out any ROM without much fear. Just make a good backup...make sure you also have a factory recovery image too...just in case. For backups...if you install and use Clockwork Mod (CWM) you can use the nandroid backup it offers. I bought Titanium backup from the market and used it to do a full backup before I started...it backs up to dropbox even, which was a nice feature for me. Extra safety so incase I hosed my external SD card which had my backups...I could easily retrieve a backup ANY place that had internet access. Lastly...get ready to have some FUN! Flashing ROMs is VERY addictive!! :-D
Ok, Thanks. I will see what I can do then.

[TOOL] HTC MyTouch 4G Slide All-In-One Toolkit V2.0 [6-9-2012][Noob-Proof]

Post 1 - Information
Post 2 - Downloads and Release / Change Information
Post 3 - Bugs, Future Additions to the GUI, FAQ
I would like to add for those that like my toolkit, PLEASE DO NOT POST IT ELSEWHERE WITHOUT MY PERMISSION!
I have seen multiple sites who copy and paste my work to their site! If I do not approve of it, then do not do it! it will discourage me from adding updates since it is being used for their own benefits!
tl;dr.
If you post my work without permission, don't expect updates!​
I created an easy to use GUI program for the MT4GS. I spent a good over 10+ hours to learn how to script, watch videos on how to do it, working on it during school when I should have been listening lol and all that fun stuff. The GUI interface looks like crap right now GUI is improved starting from v2.0 but I just wanted to share it. I am going to fix it and up and add more updates to it. You CAN place requests and I will try to fulfill it!
If this helped you out, Please press the thanks button and if you want, you can always donate!​
FEATURES​
- Install HTC Drivers
- Enter Bootloader (after it enters into bootloader, press the power button to enter Fastboot) REMOVED. No longer necessary.
- Get Token ID. Register at HTCDev, login to the site and submit the Token ID here. Buttons have been replaced and include links.
- Unlock Bootloader (Must place Unlock_code.bin in the folder)
- Install Recoveries
CWM 5.5.0.4
User Provided Recoveries
-Flash Kernels provided
User Provided Kernels
- Link to this thread
- Link to the FAQ thread
- Link to the MT4GS Development thread.
- Boot Into Recovery
- Relock Bootloader (must be in fastboot)
- Donate to me (Hasoon2000) -> Donating to yours truly for putting time into this!
Here is a screenshot.
{
"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"
}
How To Use
Just run the "MT4GS V2.0" DO NOT RENAME THE FOLDER
Credits
- The guys at the AutoIT help forum that helped me learn how to make the script!
- Mods who helped this forum!
- Developers made ROMs for everyone to use!
- Devs who made the kernels!
- The community for being awesome!
- HTC for making us the phone so we can be a community!
- To everyone else I may have forgotten!
*DISCLAIMER*​
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
DONATIONS​​
-Dranzer23
Click to expand...
Click to collapse
Downloads
Mod edit: Download links removed
Changes
V1.0 Released! 3-5-2012
- Initial Release
V2.0 Released! 6-9-2012
- New UI. A lot better and cleaner!
- Removed all Recoveries
- Removed all the kernels (Users flash things they have no clue about and soft brick their phones)
- Updated CWM to 5.5.0.4
- Added ability to flash your own kernel/recovery
- Removed the debloaters
- Fixed Root. Now it works.
Bugs
- Directory has to have one word.
Ex:
Will Work. This will solve any issues if the buttons don't work when you press them.
C:\Users\John\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
C:\Users\John_Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
Will NOT work. Your directory will look something like this and buttons won't work when you press it.
C:\Users\John Smith\Dropbox\Phones\Amaze_All-In-One_Kit_V2.4
If you have 2 words, put the folder in Drive C:
Ex. This will solve any issues if the buttons don't work when you press them.
C:\Amaze_All-In-One_Kit_V2.4
Click to expand...
Click to collapse
Looking to add in the future
- Kernels
- More recoveries
- Makes Requests!!!
FAQs
Q - Why Did you make this?
A - To make life easier
Q - You are limited on features. Why?
A- You can always make a request!
Q - Will this work on other devices?
A - Only the fastboot commands, HTC Dev unlock (device specific) and the HTC drivers. Toolkit is made for the specific device.
Q - Will you support more devices in the future?
A - If people REALLY want, I can make it happen. I just don't want to make anything that nobody would use.
Q - Awesome! Can I make a donation?
A - Of course! Do not feel obligated though. If you would like to make a donation, you can click the button on my toolkit or under my username.
This received 28 downloads. Can I get some feedback?
hasoon2000 said:
This received 28 downloads. Can I get some feedback?
Click to expand...
Click to collapse
I see from your other threads that your tools seem to be well done. not sure why you haven't gotten any response here.
I installed it just to check it out, even though I don't need it at the moment. I suspect many others don't really have occasion to use it either. for example, I'm already running pyr-o-ice (ICS ROM), so I don't need the root tools or the kernals you provide.
it would be useful to noobs, except they need step by step guides and definitions otherwise they don;t know what's going on. so it's kind of like you've developed a tool that only experienced users would know how harness, but don't really need to.
also, I would say that your intro to your threads where you make it seemed like you just learned how to do this (even if true) is not the most comforting thing to read when one is considering actions that can potentially damage your phone.
the only thing I tried was Debloater tool, but it didn't work on my PC. could be an issue with my own pc command prompt though. I usually use a mac but I'm at work using a pc that I'm not that familiar with.
my advice would be to make stuff clear enough for noobish types to understand. for example you don't even say that this runs on a pc. you're going to even have to explain extracting the rar. and especially, what the point of the toolkit is and what it does.
I actually have no idea why I took the time to write this, but I'm not trying to be harsh. its good work. keep it up and keep improving.
As the previous poster said I am on ICS so i have not tried this as I don't have a need for it now but i do have some comments that may or may not be relevant.
I came to the MT4GS from the Touch pro 2 on AT&T running Windows Mobile. Windows Mobile had a tool called Sashimi which after a fresh flash you could run and it would install backed up programs, data, create folders, import files etc. It was an excellent seamless way to restore the phone after flash. I know there are ways to do all that with Android but nothing is all inclusive. A script which could create directories, move files, restore; apps, desktop, account info, default settings all from running one command would be awesome. I don't know how possible or impossible this is but just a thought.
Regards,
http://forum.ppcgeeks.com/general-windows-mobile-discussions/101422-guide-murduckys-guide-auto-user-customization-sashimi.html
j.books said:
I see from your other threads that your tools seem to be well done. not sure why you haven't gotten any response here.
I installed it just to check it out, even though I don't need it at the moment. I suspect many others don't really have occasion to use it either. for example, I'm already running pyr-o-ice (ICS ROM), so I don't need the root tools or the kernals you provide.
it would be useful to noobs, except they need step by step guides and definitions otherwise they don;t know what's going on. so it's kind of like you've developed a tool that only experienced users would know how harness, but don't really need to.
also, I would say that your intro to your threads where you make it seemed like you just learned how to do this (even if true) is not the most comforting thing to read when one is considering actions that can potentially damage your phone.
the only thing I tried was Debloater tool, but it didn't work on my PC. could be an issue with my own pc command prompt though. I usually use a mac but I'm at work using a pc that I'm not that familiar with.
my advice would be to make stuff clear enough for noobish types to understand. for example you don't even say that this runs on a pc. you're going to even have to explain extracting the rar. and especially, what the point of the toolkit is and what it does.
I actually have no idea why I took the time to write this, but I'm not trying to be harsh. its good work. keep it up and keep improving.
Click to expand...
Click to collapse
This is the perfect feedback I am looking for. Criticism helps me know what to do and how to make it better.
The coding part in my intro was to make the design of the program and to have the button do what it is supposed to do when pressed. All the files are 100% accurate.
I will add more detail. Thanks.
As the previous poster said I am on ICS so i have not tried this as I don't have a need for it now but i do have some comments that may or may not be relevant.
I came to the MT4GS from the Touch pro 2 on AT&T running Windows Mobile. Windows Mobile had a tool called Sashimi which after a fresh flash you could run and it would install backed up programs, data, create folders, import files etc. It was an excellent seamless way to restore the phone after flash. I know there are ways to do all that with Android but nothing is all inclusive. A script which could create directories, move files, restore; apps, desktop, account info, default settings all from running one command would be awesome. I don't know how possible or impossible this is but just a thought.
Regards,
http://forum.ppcgeeks.com/general-wi...n-sashimi.html
Click to expand...
Click to collapse
I'd have to look into that. I don't believe it's easy. I can take an adb command to do a batch install of .apk files. For everything else, I'd have to look more into it. Thanks!
going to try this out now
I am trying to unlock a mt4gs that was recently updated. I have signed up at HTC but when I run the program I don't get an unlock code. All I get is an error. I thought that I read that if I have an older mt4gs that I may have to update it first, but I can find what I need to update it to. Any help would be appreciated thanks
Sent from my SGH-T959V using XDA
NewKlNGjames said:
I am trying to unlock a mt4gs that was recently updated. I have signed up at HTC but when I run the program I don't get an unlock code. All I get is an error. I thought that I read that if I have an older mt4gs that I may have to update it first, but I can find what I need to update it to. Any help would be appreciated thanks
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
I saw that a non T-Mobile MT4GS needs an hboot update. If yours is a T-Mobile model, you may have copied the token ID incorrectly.
NewKlNGjames said:
I am trying to unlock a mt4gs that was recently updated. I have signed up at HTC but when I run the program I don't get an unlock code. All I get is an error. I thought that I read that if I have an older mt4gs that I may have to update it first, but I can find what I need to update it to. Any help would be appreciated thanks
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
If you have an older MT4GS check which version of hboot you are on. From powered off state and fastboot off hold volume down and the power button. If the Hboot hersion ends in 007 use the Revolutionary method and stay away from the HTC Dev method. You will be MUCH better off if you do. Don't update software until you check your hboot.
Hastily spouted for your befuddlement.
Hasoon,
First of all, thank you for adding to the community and especially for developing an inclusive tool for newbies. I would like to add a few comments that may or may not be helpful to you:
1. I'm concerned about the inclusion of the OC / UV kernals as a 'no big deal' option. I think users, especially those new to flashing ROMs need to be aware that:
- they are voiding their warranty by modifying their device (obviously this applies to flashing ROMs in general, not just kernals)
- that they can brick their device permanently (however unlikely)
- and that only certain kernals will work with specific ROMs and versions of ROMs
If including OC / UV kernals, I think a big "This is for advanced users, only flash a new kernal if you know what you're doing..." warning would be justified. This is especially true since we don't know what software version the user is coming to this program with (e.g. what if they bought the phone used and it has a custom ROM or new and it has received the OTA update)?
2. You should probably note that this is a Windows only app. May seem obvious, but this is a broad community. Has the software been tested in other versions of Windows beyond Win7? The three most popular versions of Windows are still Windows 7, Windows XP, and Vista - in that order. VMware might be helpful for your testing, though if I recall the virtualized OS also used virtual ports for connections, which might cause testing issues. Its probably easier just to ask for feedback from users of other versions of Windows in the thread.
3. You might want to mention that the download is a RAR file. Specifically, that an archive program will be required to extract the files, such as:
- Winrar
- WinZip
- 7zip
That said, these are relatively minor critiques, and I think you've put together something useful and valuable - so thank you for your time and for being open to suggestions.
That's where I get the error. The screen comes up and my phone goes into fast boot, but it never gives me a token. Just says error. I have tried it with USB debugging on and off
Sent from my SGH-T959V using XDA
I will check my hboot when I get home. Thanks.
Sent from my SGH-T959V using XDA
SpaceSpeed said:
Hasoon,
First of all, thank you for adding to the community and especially for developing an inclusive tool for newbies. I would like to add a few comments that may or may not be helpful to you:
1. I'm concerned about the inclusion of the OC / UV kernals as a 'no big deal' option. I think users, especially those new to flashing ROMs need to be aware that:
- they are voiding their warranty by modifying their device (obviously this applies to flashing ROMs in general, not just kernals)
- that they can brick their device permanently (however unlikely)
- and that only certain kernals will work with specific ROMs and versions of ROMs
If including OC / UV kernals, I think a big "This is for advanced users, only flash a new kernal if you know what you're doing..." warning would be justified. This is especially true since we don't know what software version the user is coming to this program with (e.g. what if they bought the phone used and it has a custom ROM or new and it has received the OTA update)?
2. You should probably note that this is a Windows only app. May seem obvious, but this is a broad community. Has the software been tested in other versions of Windows beyond Win7? The three most popular versions of Windows are still Windows 7, Windows XP, and Vista - in that order. VMware might be helpful for your testing, though if I recall the virtualized OS also used virtual ports for connections, which might cause testing issues. Its probably easier just to ask for feedback from users of other versions of Windows in the thread.
3. You might want to mention that the download is a RAR file. Specifically, that an archive program will be required to extract the files, such as:
- Winrar
- WinZip
- 7zip
That said, these are relatively minor critiques, and I think you've put together something useful and valuable - so thank you for your time and for being open to suggestions.
Click to expand...
Click to collapse
You know what? I really appreciate it. In my eyes I just flash the kernels and think of it as whatever. I sometimes forget that I am a long time expert on this and no the Do's and the Don'ts.
I kind of overlook it and shrug it off. I do put these into consideration and as you can tell, I do read all the comments and reply to them as soon as I can.
When I do a new update (whenever there are new features), I will add some of the things onto the tool and edit it my original posts to include the info.
Thank you.
NewKlNGjames said:
That's where I get the error. The screen comes up and my phone goes into fast boot, but it never gives me a token. Just says error. I have tried it with USB debugging on and off
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
I have this same problem. Trying to "fix" my wife's phone. If I could get her to use a Galaxy Nexus like mine, I doubt she'd be having half the problems she does.
Ps. 1.44 hboot and already S-Off.
Mi|enko said:
I have this same problem. Trying to "fix" my wife's phone. If I could get her to use a Galaxy Nexus like mine, I doubt she'd be having half the problems she does.
Click to expand...
Click to collapse
Have you enabled fastboot from the phone?
Sent From My HTC Amaze 4G via Someone's Room
hasoon2000 said:
Have you enabled fastboot from the phone?
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
The "Fastboot" setting was still enabled, but I'll be dumbfounded if that's the problem, as the phone was rebooting into fastboot just fine, so that setting shouldn't make a difference. It's when it's running the "get token" that I'm having the problem with the error.
Update: Crisis averted. Ran revolutionary (even though my phone was already S-Off and wouldn't let me flash recovery) and all is well. Got recovery and pretty damn sure I'll be able to flash. Thanks!
Mi|enko said:
The "Fastboot" setting was still enabled, but I'll be dumbfounded if that's the problem, as the phone was rebooting into fastboot just fine, so that setting shouldn't make a difference. It's when it's running the "get token" that I'm having the problem with the error.
Update: Crisis averted. Ran revolutionary (even though my phone was already S-Off and wouldn't let me flash recovery) and all is well. Got recovery and pretty damn sure I'll be able to flash. Thanks!
Click to expand...
Click to collapse
Great to hear! Have fun flashing!
Sent From My HTC Amaze 4G via Someone's Room
Worked like a charm OP
THANKS SO MUCH

【E1】Porting ROMs for Xperia E1 Tutorial

BEFORE DOING ANY OF THESE, KEEP IT IN MIND THAT IF YOU BRICK YOUR PHONE I'M NOT RESPONSIBLE FOR IT!!
Hi guys this is a tutorial on how to port roms for Xperia E1
Search for a phone that has the same motherboard, as the Xperia E1 MSM8210(MSM8610)
In this case, I downloaded an Andromax C2 CarbonROM
Phones with MSM8210/8610 chipset: Motorola Moto E, Andromax C2, ZTE Open C, ZTE Concord II
First you have to backup your current ROM using nandroid in the Recovery.
Without this step you won't be able to access the files which are needed to port
Not necessary to backup your ROM, but It is recommended, just in case If your E1 bootloops.
If you somehow bricked your phone, use XperiFirm to download the Stock rom and flash It.
1. Go to the PORT Rom and navigate to /system/framework/
2. Find and drop framework-res.apk to the Desktop
3. Rename the framework-res.apk to framework-res.rar (or framework-res.zip If you don't have WinRaR)
4. Open the framework-res and navigate to /res/xml/
5. Copy and paste the storage_list.xml you downloaded from here
6. Close the rar/zip and rename it to framework-res.apk and put it back to /system/framework/
7. Go tohttp://forum.xda-developers.com/xperia-j-e/general/philz-touch-recovery-xperia-e1-t2941831 and download the Recovery (If you already have it skip this step)
8. Put the boot.img in the root of the port's directory
{
"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"
}
9. Go to recovery and wipe cache, dalvik, media, data (everything)
10. Flash the zip
If you did it correctly, by now you should see the CM/AOSP logo
Enjoy! Hit Thanks If it was helpful!
Video tutorial: <work in progress>
Note: If the ROM won't boot, It is because the PNGs are too big for the phone, so you either need to resize them, or give up.
Or you messed something up. Re-check everything before flashing the .zip.
What's not working:
Bluetooth, GPS, Wi-Fi, VPN, everything releated to Internet; Sound
Xperia E1 Spec:
CPU: Cortex-A7 1,19GHz r0p3 (2 core)
GPU: Adreno 305 400MHz (300MHz by default)
Chipset: Qualcomm MSM8210/MSM8610
DPI: 240
Total RAM: 423mb (Physically 512mb)
You chose CM for porting ?
Where is the base ? MODIFIED RAMDISK FOR KERNEL, HAL(S), ETC !
Cm has to be build on a Linux system with source as a base.
:/
Simple Tutorial..
Sent from my D2105 using XDA Free mobile app
kaustubh.rockstar said:
You chose CM for porting ?
Where is the base ? MODIFIED RAMDISK FOR KERNEL, HAL(S), ETC !
Cm has to be build on a Linux system with source as a base.
:/
Click to expand...
Click to collapse
Yep, but If you found a phone that has similar motherboard to your device, it is easy to port stuff, but not 100% guraanted to work
Building from source is much better .. !
kaustubh.rockstar said:
Building from source is much better .. !
Click to expand...
Click to collapse
Without the source files it is impossible
Also, I'm a noob compared to you, I don't know how to begin
Oh please sir don't say like that.
wtf
Kizoky said:
Hit Thanks If it was helpful!
Click to expand...
Click to collapse
you mean : "helpful to brick the E1 phone ?"
mai77 said:
you mean : "helpful to brick the E1 phone ?"
Click to expand...
Click to collapse
Unexperienced user will brick E1 ofc
If there is any nandroid backup in the SD Card then there is no problems
@Kizoky
As far as I know, there is no nadroid available for the E1.
Also, I really think that we should make like a "dev team" and focus on working on CM11 (CM12?) for the E1.
It's not impossible, but WILL take a lot of time and work.
Hell, I'm in.
zeteny.nagy.20 said:
@Kizoky
As far as I know, there is no nadroid available for the E1.
Also, I really think that we should make like a "dev team" and focus on working on CM11 (CM12?) for the E1.
It's not impossible, but WILL take a lot of time and work.
Hell, I'm in.
Click to expand...
Click to collapse
There is Nandroid for the Xperia E1, it's the part of CWM. And it is working, it just needs more than 2 GB available space on SD card. Also, none of the developers have this phone and I don't think they will ever consider buying it just to develop CyanogenMod for it. If we could get a display driver for the E1 that works (Adreno 305 or whatever the E1 has) we could compile CM, according to Kizoky. Or maybe if we could get drivers working on the ROM that has been ported from the Andromax C2's CM. We tried, I managed to get sound working, but no WiFi or Service or anything. Otherwise, it was waaaay more smoother than stock... If we could get CyanogenMod 12 even if it's broken I'm sure I would get it even without WiFi or Service, I don't care. If I will get an 8GB SD card I will attempt to get things working on this CM11, as I found new files that may be able to get WiFi working. Also an interesting note, the stock kernel that comes with the stock firmware is working with this CyanogenMod, which also means that it's possible to get CM on Locked Bootloader and it may also be possible on other devices. It's really handy, especially because I cannot unlock my BL because it is from a career. Oh my that's a long message lol
xezrunner said:
There is Nandroid for the Xperia E1, it's the part of CWM. And it is working, it just needs more than 2 GB available space on SD card. Also, none of the developers have this phone and I don't think they will ever consider buying it just to develop CyanogenMod for it. If we could get a display driver for the E1 that works (Adreno 305 or whatever the E1 has) we could compile CM, according to Kizoky. Or maybe if we could get drivers working on the ROM that has been ported from the Andromax C2's CM. We tried, I managed to get sound working, but no WiFi or Service or anything. Otherwise, it was waaaay more smoother than stock... If we could get CyanogenMod 12 even if it's broken I'm sure I would get it even without WiFi or Service, I don't care. If I will get an 8GB SD card I will attempt to get things working on this CM11, as I found new files that may be able to get WiFi working. Also an interesting note, the stock kernel that comes with the stock firmware is working with this CyanogenMod, which also means that it's possible to get CM on Locked Bootloader and it may also be possible on other devices. It's really handy, especially because I cannot unlock my BL because it is from a career. Oh my that's a long message lol
Click to expand...
Click to collapse
That was a fast reply
So the thing is that the E1 uses the Adreno 302, exactly the same as the Moto E. Which means there are drivers floating around in the CM11 builds for the Moto E. It uses the same connection boards, too - DRIVERS EVERYWHERE.
Only if I had the knowledge to do all this alone, the thing is that I can't
EDIT: Could you give me a link for CWM? I only found Philz Touch and I don't really like that, I prefer CWM
zeteny.nagy.20 said:
@Kizoky
As far as I know, there is no nadroid available for the E1.
Also, I really think that we should make like a "dev team" and focus on working on CM11 (CM12?) for the E1.
It's not impossible, but WILL take a lot of time and work.
Hell, I'm in.
Click to expand...
Click to collapse
There is. There's already a recovery for E1, which has built-in Nandroid backup, available to use.
@Kizoky
I'm going to dig around in Moto E CM11 files, maybe I can extract some display drivers.
@Kizoky
I managed to get some Qualcomm-made .APK-s from various ROMs. Does that help at all?
zeteny.nagy.20 said:
@Kizoky
I managed to get some Qualcomm-made .APK-s from various ROMs. Does that help at all?
Click to expand...
Click to collapse
I don't think they would, but maybe they do. (maybe one of them manages WiFI connectivity) Try to install them onto CM and see what happens (reboot too)
xezrunner said:
I don't think they would, but maybe they do. (maybe one of them manages WiFI connectivity) Try to install them onto CM and see what happens (reboot too)
Click to expand...
Click to collapse
I managed to get GPS / Location services up and running. There are still tons of .APK-s that I haven't tried yet.
EDIT: I think I found the WiFi driver.
EDIT 2: @Kizoky Did you check the ROM made by @ramdanzs ? It probably contains the display drivers you needed.
EDIT 3: I managed to get telephony working but now it doesn't function.
zeteny.nagy.20 said:
I managed to get GPS / Location services up and running. There are still tons of .APK-s that I haven't tried yet.
EDIT: I think I found the WiFi driver.
EDIT 2: @Kizoky Did you check the ROM made by @ramdanzs ? It probably contains the display drivers you needed.
EDIT 3: I managed to get telephony working but now it doesn't function.
Click to expand...
Click to collapse
Wi-Fi and Bluetooth? Those 2 bastards that are always idling and don't do anything at all.
zeteny.nagy.20 said:
I managed to get GPS / Location services up and running. There are still tons of .APK-s that I haven't tried yet.
EDIT: I think I found the WiFi driver.
EDIT 2: @Kizoky Did you check the ROM made by @ramdanzs ? It probably contains the display drivers you needed.
EDIT 3: I managed to get telephony working but now it doesn't function.
Click to expand...
Click to collapse
If you get any drivers working, please let us know immidiately.
xezrunner said:
If you get any drivers working, please let us know immidiately.
Click to expand...
Click to collapse
Told ya, GPS is fine
---------- Post added at 05:50 PM ---------- Previous post was at 04:51 PM ----------
@Kizoky
I just found this tool called FTF Extractor can be used to decompress .FTF firmware files of Sony Xperia phones, just as listed in this article/tutorial on how to decompile .FTF files.
Is it possible to grab some drivers from the stock firmware and port it to CM11? Just askin'.
AFAIK .FTF files are just "renamed" flashable .zips so, their structure is the same.

porting custom rom,kernel from mt6753 to mt6753

i need some help devs,
im a newbie and i tried to port custom aosp rom using tutorials i found on the internet,and of course here. i replaced all files and pack port rom in zip but unable to flash it,it says error executing updater binary in zip .......
im using leagoo elite with stock rom rooted and tried to port aosp 7.0 for another device but same specs except kernel (newer) in rom
i didnt managed to find tutorial how to port kernel so i just replaced boot.img,
and one little thing, rom i tried to port was packed to new.dat files,and i managed to unpack but cant repack it again
i read that if u flash via recovery only boot.img has to be in img file or correct me if iam wrong
please help me with this or with tutorials or guide me throu this,
im just a guy who wants latest android for his phone but there is no devs that work on this phone
if there is anyone who is willing to do this for me i can pm him links for download of everything he needs and i can make a donation if it works, cheers
sry for bad english
You will need to find pre-built blobs for your device or extract them. If they do not work on newer Android versions you will need to hack them or find alternatives. Not everything is the same about the device, including the panel, camera etc... You will hopefully not need to edit the kernel for the blobs to work properly, but it's a lot more work than you think it is.
BRiANj64 said:
You will need to find pre-built blobs for your device or extract them. If they do not work on newer Android versions you will need to hack them or find alternatives. Not everything is the same about the device, including the panel, camera etc... You will hopefully not need to edit the kernel for the blobs to work properly, but it's a lot more work than you think it is.
Click to expand...
Click to collapse
I found the phone with exact same specs procesor ram storage camera mp not sure about lenses but i dont find tha as important, only thing that is different is kernel version. Blobs are? I know its not easy but im trying to learn something. I found 101 guide for this but after reading all of that it just messes up in my head. I would like to find someone who can walk me through that step by step and share his knowledge
skinheadXhc said:
I found the phone with exact same specs procesor ram storage camera mp not sure about lenses but i dont find tha as important, only thing that is different is kernel version. Blobs are? I know its not easy but im trying to learn something. I found 101 guide for this but after reading all of that it just messes up in my head. I would like to find someone who can walk me through that step by step and share his knowledge
Click to expand...
Click to collapse
Blobs are pre-built drivers that do not have a source and thus cannot be built by CM themselves. You could try to compare all the drivers in system/libs on stock ROM of your device and CM of the other. There are tutorials on how to port CM to any device, try to search for such topics, they are very helpful.

Categories

Resources