Related
can anyone tell me how to add this to any rom ? i have seen these options in quite a few roms, but don't know what i need to be able to achieve this.
thanx
I'm interested as well. I saw the thread with the mod the other day before cooking my ROM and lost it. Haven't found it yet.
You can find a flashable version of it here :
forum.xda-developers.com/showthread.php?t=776679
in second post.
I use it in almost all ROM's I test.
android.policy.jar
ah thanx guys.
btw does anyone know which and what *.smali file you need to edit to achieve the above result ? i would rather do it myself to my own classes.dex than using the virusrom one. (unless i absolutely have too)
teshxx said:
ah thanx guys.
btw does anyone know which and what *.smali file you need to edit to achieve the above result ? i would rather do it myself to my own classes.dex than using the virusrom one. (unless i absolutely have too)
Click to expand...
Click to collapse
+1 Bump. I would like to know this also.
Hey guys!
i am very new at this but i have ported a build from fascinate over to our continuum and am looking for some devs to jump in and start helping me fix stuff.
this is very early but you can grab my first port here.
it is very much not ready for every day use.
Please flash if you are going to help me fix this for everyone
Code:
[B]
Rap sheet of things to fix will be here:
Screen placement overlaps the ticket screen, i was thinking we could
somehow code this thing so it will ignore the ticker
screen and only use the top.
Also we need to enable the soft keys.
Keyboard is non existent.
phone is not functional yet.[/B]
Well since this phone is virtually Unbrickable.... why not try our best.
Sent from my SCH-I400 using xda premium
Porting what build? Please tell me it's MIUI!
Sent from my SCH-I400 using XDA App
I've tried this before, and didn't get anywhere xP so, good luck
Sent from my SCH-I400 using xda premium
thanks for the well wishes... anyone know where to go in the rom to edit the screen dimentions yknow so it uses the top screen only? i think this is kernal
yea the problem with ports on the continuum is u cant flash mtd files in recovery a friend and i tried to port the fascinate miui 2.3.2 rom to the continuum we got everything resised and made it flashable but it just said installation aborted. the fascinate can flash mtd files straight from recovery and the continuum can not.
i still have all the files for miui if someone wants them pm me the problem is converting it to a .tar file so we can install via odin.
Bierce22 said:
yea the problem with ports on the continuum is u cant flash mtd files in recovery a friend and i tried to port the fascinate miui 2.3.2 rom to the continuum we got everything resised and made it flashable but it just said installation aborted. the fascinate can flash mtd files straight from recovery and the continuum can not.
i still have all the files for miui if someone wants them pm me the problem is converting it to a .tar file so we can install via odin.
Click to expand...
Click to collapse
mtd files? what's those for? the above build was ported from a fascinate rom. very asop
most roms use mtd sum to install everything im not going to go into detail about everything because i would just sound like an idiot lol.
Bierce22 said:
most roms use mtd sum to install everything im not going to go into detail about everything because i would just sound like an idiot lol.
Click to expand...
Click to collapse
lol i hear you, nah the above build ported fine.... no errors installing, i had to adjust scripting and also include imnut's kernal but it works. just need to fix stuff inside the rom
can u shed some more light on the rom such as is it froyo and aosp more information would be nice.
Bierce22 said:
can u shed some more light on the rom such as is it froyo and aosp more information would be nice.
Click to expand...
Click to collapse
sure, gimme a few and i'll update post 1, last night late i posted it with minimal info then went to bed...
alright here goes nothin im going to see what happens lol
The demensions seem to be within the framework, or at least the call to the kernel for the screen size..
So porting it is pointless, because you'll have to modify the framework back to the continuum's which would defeat the point...
As far as I think/know
That is actually why I stopped
But, feel free to prove/show me up
Sent from my SCH-I400 using xda premium
it does boot but i couldnt even get to settings and about phone to tell what it was and he still hasnt updated the op yet.
Yeah, i know it boots, haha.. I did this like two months ago
But the screen isn't divided properly for the ticker/softkeys... And won't be unless you can find the right part to edit
What language are we talking about? If it's Java I'm happy to help.
Sent from my SCH-I400 using XDA App
trailblazer101 said:
Yeah, i know it boots, haha.. I did this like two months ago
But the screen isn't divided properly for the ticker/softkeys... And won't be unless you can find the right part to edit
Click to expand...
Click to collapse
From what I have seen, in other posts about other phones, the screen size is written into the kernel. So, to do this, we need the source code for the kernel.
joshkoss: Great effort, but to do any serious mods, we must have the kernel source code. Without that, there is no way to compile the fixes/changes into the kernel. I have been able to use modprobe to do a few things, but, generally, the modules must be compiled against the source code of the kernel to work properly.
If someone can get us the kernel source code, we will be golden... Up until then, porting anything is not going to be fun.
If one was REALLY interested in doing this, one would take the generic Gingerbread kernel and ROM and work a build from the ground up that way. Especially since I don't think Samsung, nor Verizon will be handing out the kernel source code.
There is an off chance that Samsung might give the Continuum kernel source code to a developer AFTER Verizon sunsets this phone... (It's a very remote chance...)
Verizon gave me this number for the Samsung Mobile Helpline: (888) 987-4357. I haven't called them yet, but if enough of us call, someone MIGHT be able to knock something loose... Who knows. Let me know if I can help... This phone is my only phone, so I can't go flashing it every night to try things, but, over the weekend, I can try things.
Ciao!
I agree...collectively we should be capable of anything...even gettn sammy source...sumhow
sent from my XDA phone - its more than a continuum
I for one think y'all can do anything. Y'all have already done so much and I really think y'all are on to something huge!
Put a thread on cyanogen.com asking for assistance with this topic. What do you guys think of doing a donation pool to get a build working on our device?
Contents:
Android 4.0.4/IMM76D deodexed ROM in flashable ZIP format. Will not produce errors when decompiling APK/JAR files.
Includes Superuser and boot.img root-level access. Does not include radio or recovery.
Changelog:
[R1/02APR2012]: ROM base changed from 4.0.4/IMM26 to 4.0.4/IMM76D. Files updated from stock IMM76D listed below.
Updated File List:
system/app/GoogleEarth.apk (v.6.2.1.6363 :: Earth)
system/app/googlevoice.apk (v.0.4.2.54 :: Voice)
system/app/Maps.apk (v.6.5.0 :: Maps)
system/app/Phonesky.apk (v.3.5.15 :: Play Store)
system/app/Wallet.apk (v.1.1-R57v4 :: Wallet)
system/lib/libearthmobile.so
Notes:
The need to wipe data beforehand is dependent on which ROM you're already using, but is advisable when possible for the sake of simplicity.
[R1] http://www.mediafire.com/file/48w84r8v3qbb8bw/NS4G-4.0.4-IMM76D-DEODEX-R1.zip
So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.
ssconceptz said:
So does this mean the SystemUI in this version is able to decompile without errors? If so how exactly did you do this?
Thanks.
Click to expand...
Click to collapse
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.
So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium
Killasmoke said:
So how is this Rom & all I have to do is download & flash it or is there another step to do?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
The procedures are the same as for other ZIP-based ROMs: download, transfer to phone, and flash through recovery. You may or may not need to erase your data (depending on which ROM you're coming from), but backing up your data beforehand is advisable and never hurts.
I haven't received any feedback regarding this specific ROM yet (I don't know if that's a good or bad sign). The main difference is that it's deodexed and will decompile without errors. I'm sure there are other threads with more in-depth information on IMM26 changes/improvements/issues.
SuperUser
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.
mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.
I went to nexusshacks.com and downloaded the nexussrootICS.zip file (I think that's what its called). There's a SuperUser.zip file within that zip file. I moved the file to my phone and flashed it in recovery (wipe cache and dalvik cache of course). And its working well.
Sent from my Nexus S 4G using XDA App
mvilla8 said:
I was impressed with this rom for the first few minutes I used it. But then I found out that my SuperUser app wasn't working. I tried updating the binaries through the app itself but it couldn't gain root access. I downloaded the file again and flashed it again but SuperUser still didn't work. It was the same problem with not gaining root access. So I flash the SuperUser zip file from zedomax's tutorial on rooting the Nexus S 4G and I was able to gain root access. Just thought I'd tell you.
Click to expand...
Click to collapse
Thanks for bringing that to my attention. Uploaded an updated version in the OP that addresses the Superuser issue. Sorry for the inconvenience.
satuday said:
mvilla, how did you fix the superuser root access problem? i am having the same problem when i try to update binary, and im getting permission error when i try to flash recovery in rom manager, i think is because of superuser not working.
Click to expand...
Click to collapse
This update is from ChainsDD's site and has the latest Superuser app and binary. Should accomplish the same thing.
XK72 said:
I used smali and allowed each APK to reference all of the .odex files in the framework, added the classes.dex files to their respective APKs, and zipaligned. I don't know if it matters, but I did those steps through the command line, although I'm sure the process would be a lot faster with a script. If you would like the exact line-by-line process that I used, let me know.
Click to expand...
Click to collapse
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?
I guess the Google Apps are included?
Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.
Been using this since the 9th and I have to say it's very smooth. Very stock too, which obviously is what it's supposed to be. Just saying that for anyone who comes in looking for something customized. This is basically pure vanilla ICS.
Sorry for the delayed replies. I've been hammered by other obligations lately.
sniperkill said:
Hey buddy, I'd LOVE to have the step-by-step, or line-by-line on the process you used to decompile. If you could PM me, or post it up here for everyone to use, that would be great!! I'm kinda new to the decompiling and compiling scene so any help would be great! Also, you said that most devs that use ICS probably use a kitchen to decompile and compile their .jar and .apk files, where is this kitchen? Or are you talking about Android SDK?
Click to expand...
Click to collapse
mabry said:
Did you ever get that step-by-step process for deodexing ICS from the OP? If so, can you send it to me?
Click to expand...
Click to collapse
I'll try my best to post the steps later today or tomorrow. Sorry to keep you waiting.
akabadnews said:
I guess the Google Apps are included?
Click to expand...
Click to collapse
The stock Google apps are included. There are now two choices: One has the apps that were included in the IMM26 release (R3) and I have also included the latest app updates and related binary files as (R4).
The Batman said:
Will there be any further updates to this in the near future, or has this reached the end of the line so-to-speak? Just curious because I like having the natural AOSP of this.
Click to expand...
Click to collapse
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.
I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium
xamadeix said:
I'm getting a error for the media fire links. New link please?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Sorry about that. I don't know what happened there. Link fixed.
XK72 said:
Sorry about that. I don't know what happened there. Link fixed.
Click to expand...
Click to collapse
Thank you
Sent from my Nexus S 4G using xda premium
Does anyone have problems turning Bluetooth on?
Sent from my Nexus S 4G using Tapatalk
XK72 said:
I have replaced the Google apps that have been updated since the IMM26 release. There are rumblings that the official ICS ROM should be released sometime soon. I'm not holding my breath, but I'll offer the same thing to that release once it comes out.
If you're asking about adding functionality or features, I don't think I'd have anything unique to offer since there are so many other ROMs and customizable updates out already. I have considered including FaceLock functionality, but it adds quite a bit of size to the ROM and honestly, it hasn't worked very well for me. If there is enough interest, I'll include it as a separate revision in the future.
Click to expand...
Click to collapse
I would rather have the straight vanilla experience. Thanks for responding.
Edit: Also, touch to focus would be nice for the camera if at all possible. Thanks.
dsixda's Android Kitchen - Now for Samsung Galaxy SIII SGH-I747
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy SIII SGH-I747(M) (AT&T, Rogers, Bell, Telus) custom ROMs with the kitchen. This is NOT a guide to help you become Cyanogen or do fancy things with AOSP, but it may be your springboard to bigger things in the future.
Some of you already know about the Android Kitchen. It is a project I started on back in February 2010 to help newbies create their own custom ROMs and learn more about Android. As of the latest versions, you can now create your own Galaxy S3 I747 ROMs with the kitchen.
I have already posted an equivalent thread for the T-Mobile SGH-T999 Galaxy SIII, so no need for redundancy. The same steps will work for your device:
CLICK HERE FOR KITCHEN INSTRUCTIONS FOR YOUR GALAXY SIII.http://forum.xda-developers.com/showthread.php?t=1939420
Since the above link is for SGH-T999 discussion only, please post all SGH-I747 talk in the thread right here. Enjoy!
Nice, will check this out
Sent from my SGH-I747 using Tapatalk 2
I've been waiting for something like this for our phones. Thanks for your hard work, the time and effort in creating something like this is very much appreciated. :good:
Yea this android kitchen is awesome!!! I wasted no time trying it out, and its really straight forward too. Thanks again dsixda!
Oh yea!? Thems fightin words....
Thanks dsixda. Will be looking into your kitchen!
White Hot! GS3.
Nice! I have been using older versions of the kitchen on my GS3 to deodex with minimal issues. Going to update right away. Thanks Dsixda!
Thanks dsixda I have been using kitchen since the note even though it wasn't supported with 0 problems glad to see you are supporting the s3 even though I never had problems with it
Sent from my SAMSUNG-SGH-I747 using xda premium
dsixda: Thank you for such a great tool. I've written my share of scripts so I can definitely appreciate how much work something of this size has in it. I've used your kitchen for de-odexing pretty much every ROM I've built.
About that, does API 16 work with the kitchen now? Just curious.
Jirv311 said:
dsixda: Thank you for such a great tool. I've written my share of scripts so I can definitely appreciate how much work something of this size has in it. I've used your kitchen for de-odexing pretty much every ROM I've built.
About that, does API 16 work with the kitchen now? Just curious.
Click to expand...
Click to collapse
Hmm not sure, since the latest smali tools were released in September
your the Man Dsixda!!
Sorry of being off topic
Hi Dsixda
I'm a big fan of your work and I'm using your kitchen in my own custom roms
I don't whether you heard about this or not Qube 2 and me managed to port HTC one X rom to international S III. we still struggling with some stability issues along with ril issues as well.
Now I've got At&t variant of S III which has exact similar hardware of At&t HTC one XL. intially I thought porting would be easier as both has the same hardware but the rom won't boot and I frankly don't know why !!
I'm wondering if such a thing gets you interested to help me ?!
Now I'm really sorry to post this here and to use this thread for off topic subject.
Thanks and really glad to have you here.
This is awesome!! Thanks so much for all you do.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Oweida said:
Hi Dsixda
Now I've got At&t variant of S III which has exact similar hardware of At&t HTC one XL. intially I thought porting would be easier as both has the same hardware but the rom won't boot and I frankly don't know why !!
I'm wondering if such a thing gets you interested to help me ?!
Click to expand...
Click to collapse
Thanks for the comments. Na, I don't know anything about porting, and I'd rather not spend more time sitting at a computer, especially considering my health.
BIG thanks. Now to remember how to use the kitchen again…
Hi !
Great works !! Thanks !
I try it with a Stock ROM (Last Bell), and when I make the option 9 (Checkup), I have this error in the list:
>> ERROR: wiperiface_v02.so not found in working folder
Can I skip this error or how to fix it ?
Thanks !!
??
Also, someone have a good place to start to add MOD, THEMES, SOUND, etc.. to our custom ROM we make with this kitchen ?
Thanks !
Ok, it’s been a while since I used the kitchen. For my project, I’m using a stock rooted rom (UCALG1). I was hoping to use a nandroid backup from CWM. I use to do this quite often for the Nexus One. On the SG3, the nandroid backup files for the system are –
system.ext4.tar
system.ext4.tar.a
system.ext4.tar.b
The “a” & “b” have file size (different sizes) and the system.ext4.tar is empty.
There is only one boot.img file.
Looks like I can rename system.ext4.tar.a file and drop “a” and that will be the valid file to use. I’ve gone thru most of the steps, just wondering if anyone done this on a nandroid backup?
mustard007 said:
Hi !
Great works !! Thanks !
I try it with a Stock ROM (Last Bell), and when I make the option 9 (Checkup), I have this error in the list:
>> ERROR: wiperiface_v02.so not found in working folder
Can I skip this error or how to fix it ?
Thanks !!
??
Also, someone have a good place to start to add MOD, THEMES, SOUND, etc.. to our custom ROM we make with this kitchen ?
Thanks !
Click to expand...
Click to collapse
Did you add the Wipe Data option?
Sent from my phone
Jirv311 said:
Did you add the Wipe Data option?
Sent from my phone
Click to expand...
Click to collapse
I will check that !
Thanks !
Status 0 error flashing.
So when I use the G1 ODIN rom base with the only changes being deodexing and rooting, I get a status 0 error on the flash.
I'm using the updater-script that the kitchen is making, to no avail.
Has anyone else come across this? If so - how did you fix it?
I am convinced that the updater script is the issue, there is some symatical issue in there - mounting something wrong I am not sure, though I could be wrong - often am.
I will try this weekend with a captivate stock rom and my cappy, but the target is the AT&T GS3.
dsixda - great work I love it.
Hi dsixda,
I’m using att’s new JB rom from mrRobinson in your kitchen. I mainly added some items in the /data/app section. When I flash the rom, I receive the following error message -
Status 0 – Installation aborted. Can’t partition non-vfat: datamedia. Can’t partition unsafe device: /dev/blockmmcblkpl. Can’t format unknown volume: /emmc
This has actually has been happening on all the stock ICS roms I have attempted to create in the kitchen. Must be something simple I’m doing wrong in the SG3. Never had an issue creating roms for the SG2.
Does anyone know how to compile kernal.sin from kernal sources instead of having boot.img
Sent from my Sony Tablet S using xda app-developers app
psxpetey said:
Does anyone know how to compile kernal.sin from kernal sources instead of having boot.img
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Im presuming you mean to flash the kernel.ftf that loopz came up with for locked BL if so... U need zImage and ramdisk no need to build from source.
I use linux so have my own way. But pretty sure if your on windows. Championswimmer has a kitchen which you could use (As far as i remeber).
You should be left with kernel.ftf and inside it should be loader.sin, kernel.sin and META-INF
wedgess said:
Im presuming you mean to flash the kernel.ftf that loopz came up with for locked BL if so... U need zImage and ramdisk no need to build from source.
I use linux so have my own way. But pretty sure if your on windows. Championswimmer has a kitchen which you could use (As far as i remeber).
You should be left with kernel.ftf and inside it should be loader.sin, kernel.sin and META-INF
Click to expand...
Click to collapse
You sir are the MAN and yes it's exactly what I mean ive been asking tons of people and I can never get a straight answer. Yes I'm on windows so I will have to use the kitchen. Thankyou so much for the answer!! Just read a bit about it and it looks like it will work I'm going to try it out.
Sent from my LT28i using xda app-developers app
psxpetey said:
You sir are the MAN and yes it's exactly what I mean ive been asking tons of people and I can never get a straight answer. Yes I'm on windows so I will have to use the kitchen. Will the kitchen also take the extract the ramdisk and zimage or will I need. Separate tool? Thankyou so much for the answer!!
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
TBH I dont know I never used his kitchen. But u should be able to split the *.img. You should then see a ramdisk folder and zImage (or it could be called boot.img-kernel) if its named boot.img-kernel thats your zImage so rename it to zImage.
And of course ill anwser questions if posted in correct Forums
Good Luck psxpetey, hope to hear good news
wedgess said:
TBH I dont know I never used his kitchen. But u should be able to split the *.img. You should then see a ramdisk folder and zImage (or it could be called boot.img-kernel) if its named boot.img-kernel thats your zImage so rename it to zImage.
And of course ill anwser questions if posted in correct Forums
Click to expand...
Click to collapse
Thanks and I used it, it will split the image no problem but it wont build the kernel.sin on the site it says 2010 devices only also funny side not it says I dont have java installed lol. I have java jdk and jre lol. By the way wedges by correct forum do you mean under the title of the original thread about the kitchen?
phuzzeeoyster said:
Good Luck psxpetey, hope to hear good news
Click to expand...
Click to collapse
Thanks nothin good yet tho
Sent from my LT28i using xda app-developers app
Seriously??!! Are you planing make kernel.FTFs from kernel boot.imgs???
That's revolutionary!! I wish you the best in this project! :good:
Only 2010 devices but I you can unpack any device
Sent from my LT28i using xda app-developers app
Figure it out yet?
I'll get a guide up soon. Well...rough one now.
wedgess said:
TBH I dont know I never used his kitchen. But u should be able to split the *.img. You should then see a ramdisk folder and zImage (or it could be called boot.img-kernel) if its named boot.img-kernel thats your zImage so rename it to zImage.
And of course ill anwser questions if posted in correct Forums
Click to expand...
Click to collapse
wedgess's kernels = uploading atm...
When I was at the same point you currently are at, I wasted a few hours with the kitchen trying to split the *.img, just didn't output the the ramdisk.gz; since it tried to extract it. "...cpio: command not found" Maybe you will have luck?
Here's a quick guide what I'm currently doing to extract & make.
Follow this to set up Cygwin and get bootimg-tools.zip
When you get to "Select Packages", during Cygwin install, just type in perl, expand the perl section and select the radio button corresponding to B
Extract contents of bootimg-tools.zip to C:\ximg\
Replace split_bootimg.pl with the one I attached to post.(Will change output of the split img: kernel as image and ramdisk.gz as ramdisk, needed for the convert to FTF)
Copy the kernel to C:\ximg\ and rename to boot.img (or just boot, if you don't see the .img extention)
Open Cygwin terminal and enter cd /cygdrive/c/ximg/
if you wanna see contents of the location, type in ls, and you should see all the extract bootimg files + boot.img,
Extract boot.img by entering ./extractboot boot.img (in the ximg folder you should now see image and ramdisk
Grab the SINTools from the attachments and extract folder, it was originally part of the-laser's post here(just edited the build cmd to generate r800 kernel.sin's)
Copy the image and ramdisk from the ximg folder over into the SinTools folder, run the r800_build.cmd, you should now have kernel.sin made.
In the SINTools folder I threw an empty kernel.FTF w/ r800 loader, open it with winrar or w/ extractor tool you use and drag and drop the kernel.sin into the opened FTF, you can also edit the manifest if you want.
Flashtool time
DONE!
Good luck
Guess I will copypasta to thread after I format it a bit. Yay kernels done uploading too.
Was going to do this later but u got it done before I could most my kernels use lzma compression for ramdisk so would of taken him a bit to figure it out...
Did u test the kernels if they worked (the ones you just uploaded), if so ill post them on my thread linking to your guide on what to do. Good find by the way.
Ya I actually found lasers tools late last night (not very easy to find or popular) which I am going to use today thanks loopy I thought you were dead or something lol. Ive had cygwin for ages ive got the full install takes about an hour lol
Sent from my LT28i using xda app-developers app
wedgess said:
Was going to do this later but u got it done before I could most my kernels use lzma compression for ramdisk so would of taken him a bit to figure it out...
Did u test the kernels if they worked (the ones you just uploaded), if so ill post them on my thread linking to your guide on what to do. Good find by the way.
Click to expand...
Click to collapse
Tested a few, and got sexy Lupus bootlogo , so I'm assuming they work, didn't try appropriate roms to make sure they "fully" work, but I don't see why they won't. lzma compression would explain the CPIO error when it tries to decompress the ramdisk, thanks for pointing that out.
psxpetey said:
Ya I actually found lasers tools late last night (not very easy to find or popular) which I am going to use today thanks loopy I thought you were dead or something lol. Ive had cygwin for ages ive got the full install takes about an hour lol
Click to expand...
Click to collapse
Yep, the only reason I figured this method out was due to me messing around with an X10 2 weeks earlier, which led me to the_laser's tools and the idea of an FTF kernel. It's messy, but gets the job done.
LoOpy! said:
Tested a few, and got sexy Lupus bootlogo , so I'm assuming they work, didn't try appropriate roms to make sure they "fully" work, but I don't see why they won't. lzma compression would explain the CPIO error when it tries to decompress the ramdisk, thanks for pointing that out.
Yep, the only reason I figured this method out was due to me messing around with an X10 2 weeks earlier, which led me to the_laser's tools and the idea of an FTF kernel. It's messy, but gets the job done.
Click to expand...
Click to collapse
Oh ya they work ive been on doomkernel since I got home haha super glad you got this done.
Sent from my LT28i using xda app-developers app
psxpetey said:
Oh ya they work ive been on doomkernel since I got home haha super glad you got this done.
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
Is there a mirror for bootimg-tools.zip?
Please could anyone please edit the r800 file loopy edit from the x10 to r800 for sk17i insteaD pretty please I sure this work with loads of devices maybe all hdpi and mdpi
Sent from my SK17i using Tapatalk 2
This is the file I need to get with sk17i aka mango info
https://db.tt/C4ReBruX
Sent from my SK17i using Tapatalk 2
http://forum.xda-developers.com/showthread.php?p=46008894
Please help I think this is the need info just can some help explain how to convert the numbers , I dont get which one to use
Sent from my SK17i using Tapatalk 2
Or is it the info flashtool sin tool shows, please someone
Sent from my SK17i using Tapatalk HD
@LoOpy!
Hi, how can I edit the build.cmd to repack Arc S kernels?