• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root CM12.1 UNOFFICIAL RC5

Well...first ima try to port some different ROMs. Liquid will be first And then try the baseless port method. I haven't done much work with ROMs since the lg motion days so I'm kinda rusty again :p
 
I'm on the old build (rc3) "everything" is working fine, my question is do I need the new build? Since the one I'm know on is working very well.
 
Sure! I just got to set up Linux on my PC. Lol problem is my PC is a potato and I heard that you need at least 64bit to be able to build jellybean and up. But other than that I can help you with other stuff just pm me
 
Okay, so how would I go about creating my own switcher.zip/restore.zip files for this version?

I recall reading way back on this thread that the file manager seems to be able to edit the /system file regardless? I also recall reasons being listed as to why this would be necessary at all. Here are mine:

•Changing the Emoji style
•Removing some unnecessary shenanigans
•Altering some text files

That's about it. It's not urgent, so if anything, I'll try to figure it out in my own time.
 
Ethanbanker2428 said:
Hey so I was working on porting a ROM and I downloaded a carbon 5.1 ROM from the moto g. I open it up and in the system folder theres just a build prop. It happens on multiple ones too. And idea why?
Click to expand...
All the other system files are compressed with lollipop ROMs. System.new.dat is where all the system files are located(except for build.prop)
 
Google "sdat2img xda" and you will find a tutorial on how to convert system.new.dat to a system.img
If you have a windows PC you can then use a program called ext4 unpacker to extract all the system files from the system.IMG

Im not sure how you convert the system files back to a system.new.dat file though.
 
hroark13 said:
cause I make it not be like that with my release tools folder
https://github.com/hroark13/android...lob/cm12.1/releasetools/ota_from_target_files
line 135
OPTIONS.block_based = False


i could make it be like that, but dont like it that way

i like to be able to unzip the rom, make a few changes, zip it back up and flash it
Click to expand...


that is also how I get my custom install script into the zip
https://github.com/hroark13/android...lob/cm12.1/releasetools/ota_from_target_files
line 128
OPTIONS.extra_script = 'device/zte/draconis/hroarks-install-script'



I have a tendency to do things a little different from others
 
Ethanbanker2428 said:
Hey I know your probably busy but I had 3 quick questions if you don't mind
1. Do you use the tool to convert DAT to img ? I'm having issues with it
2. Do I need to do something with the boot.img if its a rom for another phone being ported over?
3. Is it true to build for lollipop you need 64 bit Linux with a 500 GB hard drive?
Click to expand...


1. there is a python script sda2img you can use that to convert it to a system.img.ext4, then you can use Android Kitchen to extract the files
2. you have to use the boot.img from our phone, either a 444 or 5.1 version, and you will also need to take any files in /system/lib/modules from the rom you took the boot.img from, the modules and the boot.img need to be the same version, if they are not wifi and other things dont work
3. I dont know for sure, but I think so, but I you dont have 64 bit, that means you have max 4 GB of ram, does not sound like a fast enough build system

I use a 8 Core AMD with 24 GB of RAM, and 3 TB hdd, I probably dont need that much, but I also run Virtual Box on it with a Windows 7 VB
 
Last edited:
Ethanbanker2428 said:
Hey I know your probably busy but I had 3 quick questions if you don't mind
1. Do you use the tool to convert DAT to img ? I'm having issues with it
2. Do I need to do something with the boot.img if its a rom for another phone being ported over?
3. Is it true to build for lollipop you need 64 bit Linux with a 500 GB hard drive?
Click to expand...


sounds like you want to port a rom from another device, I think you will get as far as getting it booted, and having most Hardware working, but I very much doubt you will get camera to work the camera HAL /system/lib/hw/camera.msm8226.so will not load unless there are certain symbols in the /system/lib/camera_client.so

I am able to build those symbols into camera_client.so when I build a rom becuase camera_client.so is one of the files that gets made


usuall taking a camera_client.so from one rom to the other does not work, but it may if you are lucky
 
I believe that a 64bit PC is required for compiling anything later than gingerbread. I don't think you would absolutely need a 500GB hard drive although a smaller hard drive would probably fill up quickly. They also recommend 16GB of ram minimum but I know a dev who builds ROMs on a laptop with 6GB ram. It does take hours for each build though.
 
First off, I want to thank everyone who had worked so hard to get this running. I have had only one problem however the ROM itself functions almost flawlessly and all major functionalities work fine. I am now using this as my daily personal ROM. It's refreshing to see Lollipop on this phone.

Now, back to my one problem and I am not sure if this has been addressed or not. I have the T-Mobile Zmax. Like I said, the ROM works fine. My only issue is when I drag down the status menu, where it should say "T-Mobile" says "Emergency calls only". However, on my lock screen it says " T-Mobile".

I've tried changing the networks, etc and restarting but no luck getting the "Emergency calls only" to go away. I've sent and received phone calls and texts with no problems.
 
Furik said:
First off, I want to thank everyone who had worked so hard to get this running. I have had only one problem however the ROM itself functions almost flawlessly and all major functionalities work fine. I am now using this as my daily personal ROM. It's refreshing to see Lollipop on this phone.

Now, back to my one problem and I am not sure if this has been addressed or not. I have the T-Mobile Zmax. Like I said, the ROM works fine. My only issue is when I drag down the status menu, where it should say "T-Mobile" says "Emergency calls only". However, on my lock screen it says " T-Mobile".

I've tried changing the networks, etc and restarting but no luck getting the "Emergency calls only" to go away. I've sent and received phone calls and texts with no problems.
Click to expand...

do you have mobile data, and did you select an APN
 
hroark13 said:
do you have mobile data, and did you select an APN
Click to expand...
Yes. When I turn off Wifi, my data connects. I keep it ticked on regardless though. I also tried the two different T-Mobile APNs that are available when I search networks - the default and the IPv6 one.
 
You must log in or register to reply here.
Back
Top Bottom