Hi, here is tool for making flashable zip in few commands! No need root! In few commands your rom is ready for sharing or flashing with CMW ! You can dump any rom! NOTE: all your rom changes which is in your phone will be included in rom.zip (for example busybox, su...etc)! Tool will be usefull for dumping next Sony stock rom, but allso all rom is supported! Enjoy!
For no rooted devices:
adb push romgen /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 755 romgen
Code:
./romgen C6903 honami /dev/block/platform/msm_sdcc.1/by-name/system /dev/block/platform/msm_sdcc.1/byname/userdata /dev/block/platform/msm_sdcc.1/by-name/cache [COLOR="Red"]/dev/null[/COLOR] /storage/removable/sdcard1/rom.zip
/dev/null must be used as a boot partition since no rooted devices have no access to these device!
For rooted devices:
adb push romgen /data/local/tmp/
adb shell
su
cd /data/local/tmp
chmod 755 romgen
Code:
./romgen C6903 honami /dev/block/platform/msm_sdcc.1/by-name/system /dev/block/platform/msm_sdcc.1/byname/userdata /dev/block/platform/msm_sdcc.1/by-name/cache [COLOR="Red"]/dev/block/platform/msm_sdcc.1/by-name/boot[/COLOR] /storage/removable/sdcard1/rom.zip
Download tool:
http://forum.xda-developers.com/showthread.php?t=2533585
munjeni said:
Hi, here is tool for making flashable zip
Click to expand...
Click to collapse
is it stable already?
I mean the Meta-INF generated completely?
thanks gonna try this if the tool complete
nelikp said:
is it stable already?
I mean the Meta-INF generated completely?
thanks gonna try this if the tool complete
Click to expand...
Click to collapse
Yesterday I noticed bug There is bug when folder is empty or when symlink is inside folder but there no other files! So when tool generate zip these folder is missing in zip but updater-script have line "set perm to folder" which not exist, so installation aborting because a missing folder Will try to solve them soon! Do not flash generated zip since you will get boot loop (you can only if you add missing folders to zip)! I will make new version soon, hope clean!
New version is out! Hope all bugs solved! Bug is solved by creating empty file .placeholder to all existing folders so zip for sure now have all mised folders, than placeholders is auto removed at finish of the installation
I am hope eerything is right now, but I will test and let you know if generated zip is installable with sucess!
New working version finaly, sorry! Now I tested tool and found another 2 bugs, first one was "zip fail to store file which contain special characters like *()...etc", and seccond one was wrong format of the permssions in updater-scrip. Now all things is solved, I have tested tool, tried to install generated zip, installed zip, and bum. Everything is ok now, enjoy!
Hi mate...nice to see you here
If I'm correct, you have some great work and kernels in your biography
Sent from my C6903 using Tapatalk
funky0308 said:
Hi mate...nice to see you here
If I'm correct, you have some great work and kernels in your biography
Sent from my C6903 using Tapatalk
Click to expand...
Click to collapse
No space left in my signature :laugh: One oftopic question, anyone have info when Sony will anounce 4.4.2 ?
munjeni said:
No space left in my signature :laugh: One oftopic question, anyone have info when Sony will anounce 4.4.2 ?
Click to expand...
Click to collapse
Yeah...I'm using Tapatalk so can't see...but, as I said, I know who you are and we will be very happy if you join Z1 development :thumbup:
It should be out (most likely) in a first few days on april (let just hope it won't be first April and we.won't be April's fools )
Some of Z2 apk files are already out and if that guy who already post few things managed to post Z2 system dump - we could have something even earlier
Sent from my C6903 using Tapatalk
I am allready in development on Z1 Compact but curently I have problem in semc_colorizable (going to start working in MIUI), so first of all I need to solve all things related to the recompiling framework-res and full removal of the semc_generic_uxp... by now have no luck Did you have luck on framework-res on Z1 using apktool ? I have managed to recompile/compile them by now, but boot loop on colorizable things since my modificaions on framework / framework-res is not complete .
munjeni said:
I am allready in development on Z1 Compact but curently I have problem in semc_colorizable (going to start working in MIUI), so first of all I need to solve all things related to the recompiling framework-res and full removal of the semc_generic_uxp... by now have no luck Did you have luck on framework-res on Z1 using apktool ? I have managed to recompile/compile them by now, but boot loop on colorizable things since my modificaions on framework / framework-res is not complete .
Click to expand...
Click to collapse
@munjeni bro, you can try out the Advanced APKtool by @BDFreak bro for the framework-res issues. It's compatible with z1 Compact.
http://forum.xda-developers.com/showthread.php?t=2639400
@munjeni, nice tool, but I need help. I get this error in CWM log every time I try to install my zip; "l:Can't partition non mmcblk device: /devices/msm_sdcc.2/mmc_host
What do I need to do to the updater script? I tried replacing the mount system bit with;
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("system", "/system");
but I had no luck.
Probably you pased bad command to the romgen since you say /devices/msm_sdcc.2/mmc_host !!! Double check first post before you going to generate zip! Or probably you using an bad cwm which have bad fstab! If no of these 2 simptoms is true than for sure you have modified updater-script by your own way which probably is not ok! Hope this help.
munjeni said:
Probably you pased bad command to the romgen since you say /devices/msm_sdcc.2/mmc_host !!! Double check first post before you going to generate zip! Or probably you using an bad cwm which have bad fstab! If no of these 2 simptoms is true than for sure you have modified updater-script by your own way which probably is not ok! Hope this help.
Click to expand...
Click to collapse
Okay so it's the bad fstab, thanks man
Can anyone make rom for my karbon a39 HD
Related
Here is (Desire Z) System Dump, help working on it.
Hi everyone! Here comes a Desire Z dump
http://www.multiupload.com/5RSGRQFATK
This is NOT a flashable zip file.
It is a file collections for ROM Dev.
This is Dump slimdizzy gave us,
so all
credits for porting it and make it work goes to slimdizzy, thanx man!
He made a dump of the device but would like some help to make sure no personal elements are left since the device was being used as a daily use phone. The dump is about 300MB big. All he did was put busybox into /data/local, chmod it to 755 and then tar'ed the /system directory.
mohamed_moscow said:
Here is (Desire Z) System Dump, help working on it.
Hi everyone! Here comes a Desire Z dump
http://www.multiupload.com/5RSGRQFATK
This is NOT a flashable zip file.
It is a file collections for ROM Dev.
This is Dump slimdizzy gave us,
so all
credits for porting it and make it work goes to slimdizzy, thanx man!
He made a dump of the device but would like some help to make sure no personal elements are left since the device was being used as a daily use phone. The dump is about 300MB big. All he did was put busybox into /data/local, chmod it to 755 and then tar'ed the /system directory.
Click to expand...
Click to collapse
I can't wait for a stable release!! XD
Sent from my Nexus One using XDA App
hey if so how could sonone make a rom from dumps or such??? if able could someone link me or guid me how to customize or links....please...thanks!!!
xghostyxjokerx said:
hey if so how could sonone make a rom from dumps or such??? if able could someone link me or guid me how to customize or links....please...thanks!!!
Click to expand...
Click to collapse
Uhh...well, you'd need to unpack the system directory, place it all in an update zip, write an update script (or updater-script w/ update binary), sign it, and flash it. It will not work on any devices though without some (or a TON) of modification.
Good luck.
cool beans, hope it doesnt run as slow as the hd port did on my droid1
sorry dumb question but is this for the htc evo too
sac23 said:
sorry dumb question but is this for the htc evo too
Click to expand...
Click to collapse
No this is a dump and therfore is just a bunch of files (at least to the average user). Some devs (IncredibleDoes) check out his twitter are working on porting this to the incredible and the evo.
is this watermarked??
Thanks, this is usefull for my upcomming project here in XDA-dev..
Hi guys, I've opened this thread so we can talk about the camera developement for CM9.
Here is the link including files and a how-to.
Here is the second link if you want even clearler instructions (Thanks to texten)
andy did u try it?( camera work)
Sent from my GT-I8150 using xda premium
Nothing, isn't working for me...
EDIT: I've an alpha 3, flashed the zip, and checked the permissions... Waiting for Arco...
I think we are missing with something..hopefully our Mentor. arco68 have the time to pass thru ere..
Can somebody poke alisd too...NVM I think I just did
http://forum.xda-developers.com/showthread.php?p=26384027
Sent from my GT-I8150 using Tapatalk 2
We can wait xD
iSadic said:
Nothing, isn't working for me...
Click to expand...
Click to collapse
+1
I tried very quickly 'cuz I don't have much time, but oisis' update zip+alpha2 didn't work.
this link is better:
http://forum.xda-developers.com/showpost.php?p=26511647&postcount=428
have fun!
texten said:
this link is better:
http://forum.xda-developers.com/showpost.php?p=26511647&postcount=428
have fun!
Click to expand...
Click to collapse
tried the instructions, but not working...
mike_kenji said:
tried the instructions, but not working...
Click to expand...
Click to collapse
maybe you will need to replace the "firmware"folder in that zip with firmware folder of gingerbread for you device
also the same procedure for the "media_profile.xml" in etc...
this could work:
just take that zip in my post, replace firmware folder and the media_profile.xml with the ones of your latest gingerbread...
and follow the installation instructions in my post
texten said:
this link is better:
http://forum.xda-developers.com/showpost.php?p=26511647&postcount=428
have fun!
Click to expand...
Click to collapse
texten said:
maybe you will need to replace the "firmware"folder in that zip with firmware folder of gingerbread for you device
Click to expand...
Click to collapse
where can i find those files? is the camera working for you?
mike_kenji said:
where can i find those files? is the camera working for you?
Click to expand...
Click to collapse
look here http://forum.xda-developers.com/showpost.php?p=26511647&postcount=428
you can see whats working and whats not working...
you can use the camera_experimental-0.1.zip
but you need to replace the firmware folder and the media_profile.xml in that zip with the ones of the latest gingerbread for your device
and do not forget to follow the installation instructions
for your further development on camera, you can also use these "instructions for camera testers"
(maybe you will add these to post#1 of this topic here)
--------------------------
here are instructions for camera testers:
Few important things:
1. make notes, because we will need it to restore steps.
2. make a logcat:
Code:
adb logcat -d > logcat.txt
if you want, edit logs like that (less logs - easier to read, logs only related with camera):
Linux shell:
Code:
cat ./logcat.txt | grep camera > logcat.new.txt
Windows cmd:
Code:
type logcat.txt | findstr camera > nwelogcat.txt
3. If you will find in log that HAL cannot connect with camera do not post logs, because they are useless
4. Do not zip or rar logs = easier to read on phone
----------------------------------
Additional Links:
You can try files from these phones.
Phones with MSM8255:
- CDMA XPeria Play
- LG Revolution
- HTC Desire S
- Sony xperia mini,mini pro, neo etc - camera works
- My touch 4g - camera works
- Xperia play - camera works
- Htc desire s - camera works
- Huawei honor - official ICS
- Htc one V - no front camera but official ICS
- http://forum.xda-developers.com/showthread.php?t=1639634
Thanks to: Spider550 for links, he cannot post here yet.
----------------------------------------------------------------------
if you make a logcat, do not forget to post which files you used.
folders for all files:
do not forget to set permissions for changed files/folders like all other files/folders there... and reboot after all changes you made!
*.so files to /system/lib
media_profile.xml to /system/etc
camera.apk to /system/app
firmware files to /system/firmware (maybe you have to create a folder)
---------
now you can start with testing.
for logcat = shutdown device - boot - start camtests - after that make a logcat directly.
texten said:
look here http://forum.xda-developers.com/showpost.php?p=26511647&postcount=428
you can see whats working and whats not working...
you can use the camera_experimental-0.1.zip
but you need to replace the firmware folder and the media_profile.xml in that zip with the ones of the latest gingerbread for your device
Click to expand...
Click to collapse
i'll try this in a while... thanks a lot... sorry for being a noob...
mike_kenji said:
i'll try this in a while... thanks a lot... sorry for being a noob...
Click to expand...
Click to collapse
no problem, maybe one other user of your device will give it a try
texten said:
no problem, maybe one other user of your device will give it a try
Click to expand...
Click to collapse
uhm... one last question, where do i put the firmware files? hehehe
*EDIT
nevermind, found it... thanks again!
mike_kenji said:
uhm... one last question, where do i put the firmware files? hehehe
Click to expand...
Click to collapse
open the zip file, delete the folder "firmware" and push your firmware folder from the latest gingerbread of your device on that place...
the same do with media_profile.xml
texten said:
open the zip file, delete the folder "firmware" and push your firmware folder from the latest gingerbread of your device on that place...
the same do with media_profile.xml
Click to expand...
Click to collapse
thanks.... wish me luck
mike_kenji said:
thanks.... wish me luck
Click to expand...
Click to collapse
good luck.
hahaha, i'm stuck on a bootloop.... try again...
Hi All,
I'm starting this thread so that we can compile in one location the methods we attempted to create a zip for the recent Jellybean update, and hopefully advance the creation of this rom. This should be mentioned before starting.
ONLY POST IF YOU HAVE RELEVENT INFORMATION REGARDING THIS JELLYBEAN ROM.
This Includes:
Procedures
Logcats
Test Builds
Helpful Suggestions (Be Specific)
To start, I've attempted the following alterations on the zip level:
Straight System dump with updated updater-script
System dump with default updater script
Modified updater script removing patch elements
Utilizing the Canadian Rom, which flashed and appplying new system.
Swapping out radio flashing and boot.img with shellnutt's boot.img
I also have the following plans:
System Dump on Canadian Rom, and default boot.img
Recursive Deleting of patched files
Example
Code:
assert(apply_patch_check("/system/3rd_party/videowiz/lib/libMvMMAS.so", "65cfe8efc36cf58669e5fb9f30274bc49c3f9703", "e1a051bb2562af8d9b106ef4b875f85a6109ee9e"));
set_progress(0.003080);
delete("/system/3rd_party/videowiz/lib/libMvMMAS.so");
Than initiate the normal package_extract_dir("system", "/system");
Any other information would be great. Some developers have gotten it to flash but not boot.
Also, here's a link to the test builds I released.
http://goo.im/devs/AdriVelazquez/Roms/Nightlies/TestSprint
Thanks to all the developers that have been working on it.
This is what I've tried:
Used the boot.img & system.img. from dump to compile a rom in dxsdia's kitchen. I was able to apply root to the boot.img and compiled a zip but it wont flash. I then added the updater script from the dump but it still wouldn' t flash. Ithink my problem is in the updater script. I didn't take thetime to configure the kitchen properly for the optimus G but will do so tonight. I have the 2 test zips at home and I'll post them tonight if anyone wants to take a look.
Suggestion:
Since houstonns Korean port boots, and all is well except radio, would it also help to look at that system dump along with the Canadian? Maybe something to utilize?
johnq54 said:
Suggestion:
Since houstonns Korean port boots, and all is well except radio, would it also help to look at that system dump along with the Canadian? Maybe something to utilize?
Click to expand...
Click to collapse
I already tried that. That was the test zip I did last night.
Sent from my LG-LS970 using xda premium
I also tried both mentioned here, none worked for me as well. I contacted couple of friends to help us out, Scott (Scrossler cleanrom series) already answer me back, he's looking into it, I will let u guys know if they get something working.
Edit: houston answer as well, he is gonna work on it as well.
LROD'S OPTIMUS G
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
dastin1015 said:
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
Click to expand...
Click to collapse
There is no /proc/emmc on my phone, but I've attached what I have in /proc/mounts in case that helps.
grktaurus83 said:
There is no /proc/emmc on my phone, but I've attached what I have in /proc/mounts in case that helps.
Click to expand...
Click to collapse
This is what I was looking for. Thanks!
dastin1015 said:
As I don't own the device I need your guys' help with creating a flashable zip for you guys. Lrod0175 requested my help. What I need is your system mount points. To get those open up Terminal Emulator and enter these commands:
Code:
$ su
# cat /proc/emmc
I need what is printed out.
Click to expand...
Click to collapse
Please, for safety, only use the by-name mount points. Below are the partitions for the American and Candian variants.
http://pastebin.com/Rej3FgQS
Shelnutt2 said:
Please, for safety, only use the by-name mount points. Below are the partitions for the American and Candian variants.
http://pastebin.com/Rej3FgQS
Click to expand...
Click to collapse
I'm using the by-name mount points. Wasn't sure if the Optimus G was proc/emmc or not.
Thanks dastin for answering and thanks guys for getting what he needs to help us.
LROD'S OPTIMUS G
do we have any logcats?
dastin1015 said:
I'm using the by-name mount points. Wasn't sure if the Optimus G was proc/emmc or not.
Click to expand...
Click to collapse
A bit late but might still be helpful to others. Here is a pastie of the by-name goodness as clear as a bell. This is the Sprint varaint
http://pastebin.com/teQmXDX9
If anyone needs anything from the stock JB ROM let me know. I am running it and can provide any files or anything.
_Epic said:
If anyone needs anything from the stock JB ROM let me know. I am running it and can provide any files or anything.
Click to expand...
Click to collapse
Same here
Sent from my LG-LS970 using xda premium
Veritass said:
Same here
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
can either of you post the build.prop? I won't be updating.
interloper said:
can either of you post the build.prop? I won't be updating.
Click to expand...
Click to collapse
How's this?
http://pastebin.com/yjNnR2sh
Sent from my LG-LS970 using xda premium
interloper said:
can either of you post the build.prop? I won't be updating.
Click to expand...
Click to collapse
Here's the build.prop
http://pastebin.com/UXSBvNMj
Provided by epic since I haven't done the update also.
Sent from my LG-LS970 using xda premium
I sent Adriel build.prop file but forgot I could copy text and post to pastebin. That's why we both posted. Lol.
Sent from my LG-LS970 using xda premium
Good morning to all, We have another dev, his name is negamann303 from the evo 3d forum, he's working hard on our project, already send me stuff to test, we will not post anything because these zips are highly flammable and all the testing is done in a spare phone I have, I will keep u guys updated.
LROD'S OPTIMUS G
Hello, i am trying to port cm 12 rom for moto g to our redmi 1s (cm 11 rom) ,but the thing is that the content in the port rom and the base rom is different,and i dont know what to do now ,you can see in the screen shot,any help will be appreciated
Update:
Some how i was able to extract that"system.new.dat" and it contains all the folders which are present in system folder in kitkat rom,i had done modifying the files, my rom is almost at the final stage,now i just want to know how to repack it back to system.new.dat.. This is the last step then we will have our lollpop rom
Dude Porting needs to be carried out between ROMs having Same android versions.
Your Moto G Rom CM12 is Android 5.x and CM11 is Android 4.4.4
Thanks...
chauhansonu104 said:
Hello, i am trying to port cm 12 rom for moto g to our redmi 1s (cm 11 rom) ,but the thing is that the content in the port rom and the base rom is different,and i dont know what to do now ,you can see in the screen shot,any help will be appreciated
Click to expand...
Click to collapse
sry if i am wrong bt u said that u r porting to our cm11 rom nd cuz of that the files are different r8? so cant u use cm12 by syhost or mokee 5.0.1? sorry for noob ques
arunal_123 said:
Dude Porting needs to be carried out between ROMs having Same android versions.
Your Moto G Rom CM12 is Android 5.x and CM11 is Android 4.4.4
Thanks...
Click to expand...
Click to collapse
But there are tutorials in which they port kitkat on jellybean roms,thats why i was trying to port lollipop on kitkat
Eziogamer said:
sry if i am wrong bt u said that u r porting to our cm11 rom nd cuz of that the files are different r8? so cant u use cm12 by syhost or mokee 5.0.1? sorry for noob ques
Click to expand...
Click to collapse
Dude i had tried the mokee lollipop rom by syhost but it was not stable and as smooth as the cm12 rom which is for moto g,i have a moto g too
chauhansonu104 said:
Dude i had tried the mokee lollipop rom by syhost but it was not stable and as smooth as the cm12 rom which is for moto g,i have a moto g too
Click to expand...
Click to collapse
u tried porting it?
---------- Post added at 06:04 AM ---------- Previous post was at 05:57 AM ----------
hey one doubt...i heard that by doing a modem fix u can make RIL work....is it true? if so can u try it? cuz i dont know how to do these thing and most of all i have a limited internet plan :crying: if a modem fix can solve it it would be so helpful for all the redmi 1s users who are waiting for functional lollipop build......
Unfortunately, you won't have any luck with porting different android versions. Porting KK from JB was possible because they were pretty similar.
I have ported the rom,but dont know why it is getting stucked at bootlogo,do anyone has solution of this?
chauhansonu104 said:
I have ported the rom,but dont know why it is getting stucked at bootlogo,do anyone has solution of this?
Click to expand...
Click to collapse
Kernel sources are available
Building from sources is easier than porting
Hit thanks if it helped
as9333 said:
Kernel sources are available
Building from sources is easier than porting
Hit thanks if it helped
Click to expand...
Click to collapse
but it will take more time
Hey its gud to know that someone is working on lollipop....
---------- Post added at 07:09 PM ---------- Previous post was at 06:50 PM ----------
http://en.miui.com/forum.php?mod=viewthread&tid=20482&extra= dont know if its helpful or not... Its about porting miui rom bt there is a section which includes information about fixing bootloop....
If the rom doesn't boot here are two things you can try:
In the folder /system/lib replace
libandroid_runtime.so
with the one from the port rom. If that still doesn't work then also replace
libmedia_jni.so
it SHOULD boot then, if not then there are other issues at hand.this
http://forum.xda-developers.com/showthread.php?t=1908008 this also contains info about fix
Hope its helpful...
Eziogamer said:
Hey its gud to know that someone is working on lollipop....
---------- Post added at 07:09 PM ---------- Previous post was at 06:50 PM ----------
http://en.miui.com/forum.php?mod=viewthread&tid=20482&extra= dont know if its helpful or not... Its about porting miui rom bt there is a section which includes information about fixing bootloop....
If the rom doesn't boot here are two things you can try:
In the folder /system/lib replace
libandroid_runtime.so
with the one from the port rom. If that still doesn't work then also replace
libmedia_jni.so
it SHOULD boot then, if not then there are other issues at hand.this
http://forum.xda-developers.com/showthread.php?t=1908008 this also contains info about fix
Hope its helpful...
Click to expand...
Click to collapse
Thanx Bro :good:
chauhansonu104 said:
Thanx Bro :good:
Click to expand...
Click to collapse
Was it useful? Should i gather more info?
---------- Post added at 04:59 PM ---------- Previous post was at 04:32 PM ----------
Hey its about repacking...
a python package script was provided to pack system.img into system.new.dat.
Usage:
$ python img2sdat.zip [system.img] [output_dir]
The argument system.img is default set as system.img, can be omitted.
The argument output_dir is default set as otazip, can be omitted.
Big thanks to luxi78.
Please get the script at:
https://www.dropbox.com/s/ljn1q9eprf...2sdat.zip?dl=0
or
http://download.csdn.net/download/howellzhu/8375811
If you know Chinese , you can visit the blog for details at:
http://blog.csdn.net/howellzhu/article/details/42841191
http://forum.xda-developers.com/and...o-conver-lollipop-dat-files-to-t2978952/page8
http://forum.xda-developers.com/and.../how-to-conver-lollipop-dat-files-to-t2978952
Hey i read on some post that the rom requires lollipop kernel for it to work... Nd if its bootloop then it shows that its not a kernel problem since it passed the logo.. . Both of this is a little confusing.... Bt hope it helps. ....
Eziogamer said:
Was it useful? Should i gather more info?
---------- Post added at 04:59 PM ---------- Previous post was at 04:32 PM ----------
Hey its about repacking...
a python package script was provided to pack system.img into system.new.dat.
Usage:
$ python img2sdat.zip [system.img] [output_dir]
The argument system.img is default set as system.img, can be omitted.
The argument output_dir is default set as otazip, can be omitted.
Big thanks to luxi78.
Please get the script at:
https://www.dropbox.com/s/ljn1q9eprf...2sdat.zip?dl=0
or
http://download.csdn.net/download/howellzhu/8375811
If you know Chinese , you can visit the blog for details at:
http://blog.csdn.net/howellzhu/article/details/42841191
http://forum.xda-developers.com/and...o-conver-lollipop-dat-files-to-t2978952/page8
http://forum.xda-developers.com/and.../how-to-conver-lollipop-dat-files-to-t2978952
Hey i read on some post that the rom requires lollipop kernel for it to work... Nd if its bootloop then it shows that its not a kernel problem since it passed the logo.. . Both of this is a little confusing.... Bt hope it helps. ....
Click to expand...
Click to collapse
Yeah i think,this may be a kernel issue, because i have tried many possibilites in building this rom, spent 2 weeks in it,everything seems to be right, but dont know what the problem is, i tried looking out in mokee 5.0 rom by syhost to get to know where i am going wrong, but he has protected his rom with some password thats why i am not able to get know about the inside contents,if i install his rom in my device,is there a way to extract boot.img(which is the kernel) using terminal on android , let me google it
And yes thanks for what you are doing, helping people in their work keep it up bro, thats how the forums run
chauhansonu104 said:
Yeah i think,this may be a kernel issue, because i have tried many possibilites in building this rom, spent 2 weeks in it,everything seems to be right, but dont know what the problem is, i tried looking out in mokee 5.0 rom by syhost to get to know where i am going wrong, but he has protected his rom with some password thats why i am not able to get know about the inside contents,if i install his rom in my device,is there a way to extract boot.img(which is the kernel) using terminal on android , let me google it
And yes thanks for what you are doing, helping people in their work keep it up bro, thats how the forums run
Click to expand...
Click to collapse
Hey did u try extracting it with 7zip?if not just give it a try....0
xda-developers
There is programm called unmkbootimg. type:
unmkbootimg boot.img
will create zImage and initramfs.cpio.gz files in current directory. scripts/extract-ikconfig will give you config from kernel.
mafamafa
If you have unpacked ROM and got yourromfolder/RFSFAT16_BOOT_00000000000 then all you need
>unmkbootimg yourromfolder/RFSFAT16_BOOT_00000000000
To get boot.img from tablet: install Term(terminal) (to tablet), run terminal, type:
>su
>busybox dd if=/dev/block/nandc of=/mnt/sdcard/boot.img
http://forum.xda-developers.com/showthread.php?t=1877807
http://technopyrate.blogspot.in/2013/04/how-to-edit-android-bootimg-in-windows.html?m=1
https://gist.github.com/jberkel/1087743
Hey i got this info on some site 1st make backup of mokee rom with CWM nd look into the backup folder for the boot. Img...
http://forum.xda-developers.com/showthread.php?
t=1929222
the simplest way is to log into adb shell and run
Quote:
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img
and then exit adb and run
Quote:
adb pull /sdcard/boot.img boot.img
this assumes that your boot is on mtd2 (run: cat /proc/mtd on the device to determine right partition)
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Open up your android terminal emulator.
-- Now go ahead and pull your boot.img from your device (or use another one if you wish). Here is an example:
Code (Text):
[email protected]:/ # dd if=/dev/block/mmcblk0p20 of=/data/local/tmp/boot.img
dd if=/dev/block/mmcblk0p20 of=/data/local/tmp/boot.img
Eziogamer said:
Hey did u try extracting it with 7zip?if not just give it a try....0
xda-developers
There is programm called unmkbootimg. type:
unmkbootimg boot.img
will create zImage and initramfs.cpio.gz files in current directory. scripts/extract-ikconfig will give you config from kernel.
mafamafa
If you have unpacked ROM and got yourromfolder/RFSFAT16_BOOT_00000000000 then all you need
>unmkbootimg yourromfolder/RFSFAT16_BOOT_00000000000
To get boot.img from tablet: install Term(terminal) (to tablet), run terminal, type:
>su
>busybox dd if=/dev/block/nandc of=/mnt/sdcard/boot.img
http://forum.xda-developers.com/showthread.php?t=1877807
http://technopyrate.blogspot.in/2013/04/how-to-edit-android-bootimg-in-windows.html?m=1
https://gist.github.com/jberkel/1087743
Hey i got this info on some site 1st make backup of mokee rom with CWM nd look into the backup folder for the boot. Img...
http://forum.xda-developers.com/showthread.php?
t=1929222
the simplest way is to log into adb shell and run
Quote:
dd if=/dev/mtd/mtd2 of=/sdcard/boot.img
and then exit adb and run
Quote:
adb pull /sdcard/boot.img boot.img
this assumes that your boot is on mtd2 (run: cat /proc/mtd on the device to determine right partition)
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Open up your android terminal emulator.
-- Now go ahead and pull your boot.img from your device (or use another one if you wish). Here is an example:
Code (Text):
[email protected]:/ # dd if=/dev/block/mmcblk0p20 of=/data/local/tmp/boot.img
dd if=/dev/block/mmcblk0p20 of=/data/local/tmp/boot.img
Click to expand...
Click to collapse
will try this
Progress?
that's the spirit bro
Eziogamer said:
Progress?
Click to expand...
Click to collapse
Maybe with your effort and op's work we can get stable lollipop, never give up just keep trying bro and thanks for putting efforts and thinking about me(users of redmi 1s)
chauhansonu104 said:
will try this
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g/development/rom-mokee-opensource-project-t2962496
Hey its the link for mokee lollipop nightly for moto g.... Maybe u could use this for porting to redmi 1s,as now both have same android version...
Hope its helpful...
I don't know much about this stuff, but i guess i could help you in getting the kernel and the system folder used in mokee 50.1 by syhost. Flash the rom, back it up using twrp. Then in the twrp folder you'll see two files like boot.emmc.win and system.emmc.win (names might not be same as i mentioned, but the extension is .win and also you'll know what's what if you just see the file size). Then rename boot.emmc.win to boot.img ~ you'll get the kernel. Rename system.emmc.win to system.tar, extract it ~ you'll get the system folder (although i'm not sure about the image file). Give it a try.
As well as my own MoDaCo Custom ROM for the 5X, I've created a custom ROM starter template for anyone who wants to have a go. It's a bit different.
Basically, this ROM template will let you create your own custom ROM VERY easily. Easier than ever before. All you have to do is...
download my ROM template zip
make the changes to the system of your phone just as you'd like them for your custom ROM
run some commands on your device via ADB
add the 2 resulting files to the template zip
That's it! No messaging around with install scripts, no rebuilding anything complex, just mod - and go!
Preparation
ONLY if you are completing the process for the first time, you need to set up a file on your microSD card - so launch and ADB shell and type the following commands...
Code:
touch /sdcard/exclude
echo app > /sdcard/exclude
echo priv-app >> /sdcard/exclude
echo delapp >> /sdcard/exclude
ROM build
Once you have your system up and running how you want it, and you're ready to distribute it (just the system and cust dirs mind, it won't pull the data dir, so your personal data is safe), reboot to recovery, launch an ADB shell and type the following commands:
Code:
mount /system
tar -X /sdcard/exclude -zcvpf /sdcard/system.therest.tar.gz /system/
tar -zcvpf /sdcard/system.apps.tar.gz /system/app /system/priv-app /system/delapp
mount /cust
tar -zcvpf /sdcard/cust.tar.gz /cust
You'll then end up with 3 new files on your SD card - system.apps.tar.gz (which is apps and priv-apps from system), system.therest.tar.gz (which, as the name suggests, is the rest of the system partition!) and cust.tar.gz with is the cust partition contents.
Update the template zip with these 3 files and that's it. It's ready to distribute for people to flash via TWRP! If you have updated the boot image, you'll need to replace that too, the easiest way is to do a TWRP backup then pull that file from the SD card and drop it into the template zip as boot.img. That's really it!
I hope this inspires a few people to start playing around with custom ROMs for the 5X... more cool things coming soon!
Oh and the all important template file...
DOWNLOAD - customromtemplate-5x-plk21-b330-r4.zip [ROMRAID] MD5: 524ef13ab773859245c2488ab8271bc0
P
Changelog
r4:
Updated to B330
r3:
Updated to format partitions rather than delete
r2:
Updated to include /cust partition support
r1:
Initial release
Thank you for this your work is much appreciated
Thnx a lot...
Sent from my KIW-L21 using Tapatalk
Thankyou, can I use this script for L-22? And will your MoDaCo rom will work with L-22?
I don't think this one will in its entirety, but you can make your own template by pulling the boot image from the TWRP backup and using the commands above to create the files to put in the zip.
P
Sent from my SM-G928F using Tapatalk
paulobrien said:
I don't think this one will in its entirety, but you can make your own template by pulling the boot image from the TWRP backup and using the commands above to create the files to put in the zip.
P
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
Oh, I see. I will try after my exams. And MoDaCo rom will support all versions or only L-21?
praxant said:
Oh, I see. I will try after my exams. And MoDaCo rom will support all versions or only L-21?
Click to expand...
Click to collapse
L21 is the only model I can test on currently.
P
Sent from my SM-G928F using Tapatalk
Looking forward to rooting and trying your ROM MoDaCo thanks for your efforts
Sent from my KIW-L21 using Tapatalk
paulobrien said:
L21 is the only model I can test on currently.
P
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
I tested it on my L24-B140 and it worked just fine. Thanks for sharing
I think it's going to be worth integrating /cust into this too, as they are a lot of things pulled from there (such as the build.prop changes). It'll be simple enough though.
re: non KIW-L21 devices, creating a template for other models shouldn't be any issue at all. I'm getting a US spec Honor 5X, so that'll be helpful.
P
paulobrien said:
I think it's going to be worth integrating /cust into this too, as they are a lot of things pulled from there (such as the build.prop changes). It'll be simple enough though.
re: non KIW-L21 devices, creating a template for other models shouldn't be any issue at all. I'm getting a US spec Honor 5X, so that'll be helpful.
P
Click to expand...
Click to collapse
Are you referring to the cust/hw/USA/prop/local.prop
the rest of the stuff in cust seems pretty standard like (media/bootanimation.zip)
Might as well make all of /cust changeable.
P
paulobrien said:
Might as well make all of /cust changeable.
P
Click to expand...
Click to collapse
so just add tar -zcvpf /sdcard/system.apps.tar.gz /system/app /system/priv-app /cust
or does it need it's own line and an updater-script edit to include it
That should probably work. updater-script will need to include mounting /cust too.
P
paulobrien said:
That should probably work. updater-script will need to include mounting /cust too.
P
Click to expand...
Click to collapse
yeah that worked as expected, only question is their any user info stored in /cust that we might not want to share ?
I didn't check every file in their
No, /cust is read only.
P
Sent from my SM-G928F using Tapatalk
paulobrien said:
No, /cust is read only.
P
Sent from my SM-G928F using Tapatalk
Click to expand...
Click to collapse
So just to be sure, if I want to remove facebook and twitter from /cust/preinstalled/public
I would need to add --> run_program("/sbin/busybox", "rm", "-rf", "/cust/*");
to erase the /cust folder first ? the same way /system is erased / formated
Exactly.
P
paulobrien said:
Exactly.
P
Click to expand...
Click to collapse
Alright, here's my updater-script with all the changes
Code:
ui_print("Flashing boot...");
package_extract_file("boot.img", "/tmp/boot.img");
write_raw_image("/tmp/boot.img", "/dev/block/bootdevice/by-name/boot");
delete("/tmp/boot.img");
ui_print("Mounting system...");
mount("ext4","EMMC","/dev/block/bootdevice/by-name/system", "/system");
mount("ext4","EMMC","/dev/block/bootdevice/by-name/cust", "/cust");
ui_print("Erasing system...");
run_program("/sbin/busybox", "rm", "-rf", "/system/*");
run_program("/sbin/busybox", "rm", "-rf", "/cust/*");
ui_print("Extract Apps...");
package_extract_file("system.apps.tar.gz", "/tmp/system.apps.tar.gz");
run_program("/sbin/busybox", "tar", "zxvf", "/tmp/system.apps.tar.gz", "-C", "/");
delete("/tmp/system.apps.tar.gz");
ui_print("Extract System Files...");
package_extract_file("system.therest.tar.gz", "/tmp/system.therest.tar.gz");
run_program("/sbin/busybox", "tar", "zxvf", "/tmp/system.therest.tar.gz", "-C", "/");
delete("/tmp/system.therest.tar.gz");
sync();
unmount("/system");
unmount("/cust");
ui_print("Done Enjoy !!");
set_progress(1.000000);
For completeness here's the boot.img for the KIW-L24 B140 for any USA users who want to join in
https://www.androidfilehost.com/?fid=24438995911973056