Hey all,
So I downloaded hexagon OS for mt6580 and LineaseOS13 for mt6580.. of course installing them gives me a bootlop since they are not ported for the K-touch i10... so I followed a guide to replace the files in those custom roms with the required ones from the stock rom to get them to work. zipped them up, put the zip on the phone, and twrp gives me the "invalid zip file" error when trying to flash them...
help?
@SaucemanBangorang
Isn't the error message "Invalid Zip File Format"?
0
Seppppx said:
1. You used the wrong compression method (most likely.)
You need to set the compression method to "store"
2. Don't port ROMs. Build them from source as they were intended to be. It is much easier to build them than port.
Click to expand...
Click to collapse
Thanks for replying.
I did something dumber, when it zipped, it put the files into a folder, hence the error, re-zipped so it wouldn't do that, and it installed, but the roms of course don't work despite porting them.
2. Building the rom from source sounds way beyond me. Porting meant coping files from the stock rom to the custom rom.. is building a rom easier than that? I actually hate this iteration of the i10 I was given, since it is actually weaker and less functional than my i9.. so I just wanted to see if a better rom would at least make it a usable phone.. I already spent hours flashing and rooting just to get past the stupid trojans/spyware that were installed on the phone.. irritates me that I would have to spend even more time building a rom for it.. especially when it's not a popular phone and said no rom would be of no use to anyone.
Related
I hope this IS the thread for asking questions..haha...
Firstly I'm a noob at Android developing, but I'm willing to learn..So I just got myself a Samsung Galaxy S Advance, and I'm going to try to root it myself.. But I'm quite buffled with the firmwares that I downloaded at samfirmware for this phone, cos the file inside are quite different from what we always see, listed like this:
cache.img.md5
system.img.md5
hidden.img.md5
kernel.bin.md5
modem.bin.md5
And there is also this file (SS_DL.dll) which I don't know how to use.. for rooting, I'm supposed to find the boot.img and modify some files in it, but I have no idea where to look for it... I suspected it would be in the kernel.bin, or compiled from that file, but that would be out of my knowledge... Is there anyone who can point me to the right direction?
So far i have been trying to decompile the system.img to get their NAND imgs using unyaffs and unyaffs2, but both are not working (segmentation fault and file is not multiple of 2048 + 64 or something)... Is there any other way for me to extract boot.img from the files above?
I have decompiled system.img with dsixda kitchen, to get system files, but I don't know how to get boot.img (kernel). I think it is in the kernel.bin file, but the kitchen can't decompile it. I've been asking around how to get boot.img from this phone but nobody gives me any answer. If we somehow manage to get boot.img and decomple it, we can than make insercure kernel, which could be used for rooting the phone.
Here is the guide for rooting Samsung Galaxy S I9070 Advance.
http://software2tech.com/2012/05/01/root-galaxy-s-advance-i9070/#more-18866
There is one problem though, the most important files, that we need, haven't been uploaded yet. I've already searched this group on facebook, and nwrite them to publish those files (kernels), but there was no answer. So I doubt that they even have those rooted kernels. Maybe you could write them too, and lets hope that they will publish kernels soon!
I think they don't really have the rooted kernel.. Cos Samsung haven't even release the opensource k kernel yet.. But yeah, right now I'm stuck.. I have been trying almost every possible way to create the boot.img, including unyaffs and unyaffs2, but keep getting errors... If we can just ask the guys at rootzwiki to port CWM recovery for us, but maybe they need rooted source too..
This would be great if they could build us CWM recovery. I don't think they need kernel source they just need stock recovery, but to get stock recover.img from our phone we need to know here is located. I have pull partitons layout from the phone, but unfortunatly it doesnt tell anything useful. You can see it in the attachment.
whoa...that is great...maybe that could help...i will try to check with other phones, cos it might be that one of this partitions would contain boot.img as well as recovery.img... how exactly you extract this information, using kitchen, perhaps? haha...
No my phone used to be rooted, until I have upgrade it to new firmware (stupid me I know, but I had test firmware before, and had quite few bugs). And I've pulled this from system partition (in /proc folder). But you can also get it with this:
adb shell
cd proc
cat partitions
I can provide some other files, that might be useful. We just need some help from experienced developers, but so far no help was offered. I've been starting threads all over the place, but nothing .
In the attachment are all the files that might help some developer to get us recovery working!
well, after searching throughout the web, I'm starting to think that without the opensource kernel from samsung, it might be quite impossible for us to root this phone... every other imaginable ways to make these system or boot images seemed to require root access... so far samsung had done a very well job in patching those root exploits...
kilsmap said:
well, after searching throughout the web, I'm starting to think that without the opensource kernel from samsung, it might be quite impossible for us to root this phone... every other imaginable ways to make these system or boot images seemed to require root access... so far samsung had done a very well job in patching those root exploits...
Click to expand...
Click to collapse
Yeah I think you are right, but I wish you wer not . Well no we have to wait for samsung to release source code of the kernel.
Ok source code for kernel is now available!!! You can download it from opensource.samsung.com. I will make a thread later, with mirror links! Now lets compile that sh*** !
hahahahaha...at last...i was checking that site every few hours...this would make it!!
I've just made a thread on XDA:
http://forum.xda-developers.com/showthread.php?p=25782811#post25782811
If you managed to compile it before me please PM . I'm just installing linux, but I won't be able to continue until tommorow, cause I do this on work computer .
Hi I'm trying to get CM11 running on LG Optimus S/V. I got the source to compile but the zip is too big to flash. What do I need to do to make it small enough so I can flash and test it? Also how do I make a writeable img file from a folder like /system or /boot? If I can't find a recovery that will flash a kitkat rom on my device I might have to try writing the images with dd.
I'm not sure I understand what the problem is. Do you mean the .zip that results at the end off your build? That zip file should be fine to flash.
romuloxiii said:
I'm not sure I understand what the problem is. Do you mean the .zip that results at the end off your build? That zip file should be fine to flash.
Click to expand...
Click to collapse
I'm actually trying to port CM11 to the Optimus S, I had to modify the device config to make a system.img that's bigger than the the system partition on the phone because the build was erroring out. Now I want to squeeze kitkat onto the phone taking out whatever isn't absolutely essential, just to see if it'll boot and run on our phone.
This is most likely a really newbie question..
But does anyone know how I can extract the .zip ROM file from an Android phone. The best I could find were people that were doing a backup of there phone (I don't know if they are .zip or not). But I want to somehow extract the .zip from the phone and be able to flash like a custom ROM.
Thanks in advance!
Sparrow40k said:
This is most likely a really newbie question..
But does anyone know how I can extract the .zip ROM file from an Android phone. The best I could find were people that were doing a backup of there phone (I don't know if they are .zip or not). But I want to somehow extract the .zip from the phone and be able to flash like a custom ROM.
Thanks in advance!
Click to expand...
Click to collapse
I understand what you are looking for, but there is not a way to do that. The backup and restore method would be as close as you could get, but the method to backup leaves the various partitions in .img file formats which the custom recovery (has to be a custom recovery like ClockWorkMod, TWRP, etc) would be able to read, copy, and restore. Does the same thing that you are looking for, just in a different way.
es0tericcha0s said:
I understand what you are looking for, but there is not a way to do that. The backup and restore method would be as close as you could get, but the method to backup leaves the various partitions in .img file formats which the custom recovery (has to be a custom recovery like ClockWorkMod, TWRP, etc) would be able to read, copy, and restore. Does the same thing that you are looking for, just in a different way.
Click to expand...
Click to collapse
If I am unable to extract a .zip of the ROM, how do I work on the ROM and do things like port it?
All the websites I look at say to download the .zip, but my phone (JiaYu G4s) doesn't have a ROM available. The closest would be the JiaYu G4; which to my (very small) knowledge is no good to me because the internals are all different.
That's one of the major downsides to having a phone that isn't supported by the manufacturer or the dev community. Technically, the manufacturer is supposed to release the source code per GPL, but most of the ones that use MediaTek chips never do.
http://www.xda-developers.com/android/have-you-paid-your-linux-kernel-source-license-fee/
I'm not sure how devs that work on those devices do it...
Edit: Found it
http://phonegist.blogspot.com/2014/02/how-to-make-stock-rom-of-mediatek.html
es0tericcha0s said:
That's one of the major downsides to having a phone that isn't supported by the manufacturer or the dev community. Technically, the manufacturer is supposed to release the source code per GPL, but most of the ones that use MediaTek chips never do.
http://www.xda-developers.com/android/have-you-paid-your-linux-kernel-source-license-fee/
I'm not sure how devs that work on those devices do it...
Edit: Found it
http://phonegist.blogspot.com/2014/02/how-to-make-stock-rom-of-mediatek.html
Click to expand...
Click to collapse
So, by following the steps on the link provided. I actually am able to create a .zip from the ROM installed on the phone?
That's the idea. I dunno if that one is compatible with your chipset, but you will have to find the version that does and should be able to get started.
hi guys!
First of all : I'm new to the custom rom scene development. I do know how to flash and so..
So i've installed cygwin and the android kitchen. I took the stock rom provided to me by the manufacturer, i was able to set up the working folder. Then I did : "Build ROM from working folder", without making any changes to apk's or something like that.
When i got the update.zip file i tried flashing it with a recovery and using the update.zip in /sdcard method. The first method just stopped after verifying, the second method said it was an invalid package.
I believe there is something wrong with the signing of the rom. Could you guys help me out?
Thx!
tcornelis said:
hi guys!
First of all : I'm new to the custom rom scene development. I do know how to flash and so..
So i've installed cygwin and the android kitchen. I took the stock rom provided to me by the manufacturer, i was able to set up the working folder. Then I did : "Build ROM from working folder", without making any changes to apk's or something like that.
When i got the update.zip file i tried flashing it with a recovery and using the update.zip in /sdcard method. The first method just stopped after verifying, the second method said it was an invalid package.
I believe there is something wrong with the signing of the rom. Could you guys help me out?
Thx!
Click to expand...
Click to collapse
do you installed java jdk?
how do you make rom using kitchen,via cwm backup or else.
for which phone you are making rom?
His story is history,My story is mystery.
roshan77ss said:
do you installed java jdk?
how do you make rom using kitchen,via cwm backup or else.
for which phone you are making rom?
His story is history,My story is mystery.
Click to expand...
Click to collapse
yes i have the latest java JDK
i've got the update.zip (see 1.png)
in Android Kitchen folder i put the update.zip in the original_update
So I was trying to package a rom and let the kitchen create the meta-inf folder along with the updater-script but the problem is that it's not using the specified mount points.
My phone isn't supported in the kitchen so I had to make a file in the edify_defs folder for my phone. I did all the right steps, I renamed the file to that of the ro.produc.device, used the template and made the necessary edits using notepad ++, and checked the file for any incorrect syntax yet after all that, the kitchen isn't using the mount points I put but instead uses the default value "mount("MTD", "system", "/system")".
Any help?
bump
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
iZLeeP said:
Don't rely on kitchen's mount. Instead, use the update binary of a working zip for your device and edit the updater-script manually to make it work.
Click to expand...
Click to collapse
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
black_fire21 said:
Yah, the thing is there are no roms for my device not even a stock rom. This is the reason why I'm trying to learn how to build a rom.
Anyways, I got the kitchen to detect the mount points. Turns out i had put the kitchen in the wrong directory. Made the zip flash correctly but now i encountered a new problem. After flashing the zip, the interface on my phone becomes really small. It's like my display went into tablet mode. Any idea on this?
Click to expand...
Click to collapse
What's your device and android version? Much better if you could post on your device's specific thread.
It's a local phone called starmobile quest, running jellybean. Sadly, there is absolutely no support for the device not even from the manufacturers. There are no developers either. The only thing we have is root and cwm.