Can a kernel dev contact QuBe2 on xda he wants to port sense 4 to the mes,showcase,and fascinate he just needs a kernel dev to make a small change to the kernel for him so contact him please
Jurellz said:
Can a kernel dev contact QuBe2 on xda he wants to port sense 4 to the mes,showcase,and fascinate he just needs a kernel dev to make a small change to the kernel for him so contact him please
Click to expand...
Click to collapse
hope someone contacted him
ztotherad said:
hope someone contacted him
Click to expand...
Click to collapse
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
notta said:
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
Click to expand...
Click to collapse
Did you tell QuBe2 that?
he told me " I cant build kernels i need a kernel dev to do a edit to a cm9 kernel" before i posted this thread
but i just told him about this edit. hopefully this is it
Jurellz said:
he told me " I cant build kernels i need a kernel dev to do a edit to a cm9 kernel" before i posted this thread
but i just told him about this edit. hopefully this is it
Click to expand...
Click to collapse
I have used that exact code to boot sense myself!
notta said:
I have used that exact code to boot sense myself!
Click to expand...
Click to collapse
On the Fascinate??
istealhome said:
On the Fascinate??
Click to expand...
Click to collapse
Yes it was but now the fassy has a 1gb sys partition!
notta said:
Yes it was but now the fassy has a 1gb sys partition!
Click to expand...
Click to collapse
Sorry, I'm a little confused haha. I stopped flashing after JT redid the partitioning in jb (I'm to lazy to restore all my apps unless its for a brand operation system version, or skin lol) is that what you are talking about?
istealhome said:
Sorry, I'm a little confused haha. I stopped flashing after JT redid the partitioning in jb (I'm to lazy to restore all my apps unless its for a brand operation system version, or skin lol) is that what you are talking about?
Click to expand...
Click to collapse
Yes I am speaking of Jt's new partition layout for the 1gb!
notta said:
Yes I am speaking of Jt's new partition layout for the 1gb!
Click to expand...
Click to collapse
So does that break Sense or something? Why not use the old layout? I'm sure people would forfeit the new layout for Sense
istealhome said:
So does that break Sense or something? Why not use the old layout? I'm sure people would forfeit the new layout for Sense
Click to expand...
Click to collapse
NO! Was implying it would run much better and be much easier on the new partition layout!
I myself was planning on attempting it again on the new layout but I sorta picked up extra work I wasn't planning on! Plus, somebody bricked my HTC dev phone.... :laugh:
notta said:
NO! Was implying it would run much better and be much easier on the new partition layout!
I myself was planning on attempting it again on the new layout but I sorta picked up extra work I wasn't planning on! Plus, somebody bricked my HTC dev phone.... :laugh:
Click to expand...
Click to collapse
Ahhhh I see! Hey! You should talk to xboxfanj; he's been trying to get Sense 2.1 to boot on the fassy for a while now but hasn't been successful, tell him about the new partition layout and it should help him get 4.0 working for our phones! I'd be glad to test out for a dev duo like that
notta said:
This was what I always used!
Please nobody don't do anything stupid!
Take the prebuilt's and the tools from any cm10/aosp source and place in ramdisk folder!
Linux
Code:
mkdir ramdisk
cd ramdisk
gzip -dc ../ramdisk.img | cpio -i
cd ..
mv ramdisk.img ramdisk.bak
./mkbootfs ramdisk | gzip > ramdisk.img
./mkshbootimg.py boot.img kernel ramdisk.img ramdisk-recovery.img
Click to expand...
Click to collapse
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
this wouldnt work on the showcase right?
Jurellz said:
this wouldnt work on the showcase right?
Click to expand...
Click to collapse
It would still boot most likely on the showcase if it does on the fascinate. I think kernels should be interchangable.
i flashed it and it rebooted and looped in recovery
Jurellz said:
i flashed it and it rebooted and looped in recovery
Click to expand...
Click to collapse
What do you mean by that
Sent from my SPH-D700 using Tapatalk 2
xboxfanj said:
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
Click to expand...
Click to collapse
xboxfanj said:
What do you mean by that
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
nevermind i flashed it and this is what i get .
http://pastebin.com/YMQVULvZ
xboxfanj said:
My preferred method is to just do everything within the cm build directory. The only thing that needs modification is init.rc, so copy the sense init.rc to system/core/rootdir of the cm directory. Then build and get the boot.img from the zip. It takes awhile, but it's the most reliable method for Galaxy S devices (on others, you can easily just use kitchens). In other news, if someone could please test and logcat this Sense 2.1 ROM, I would appreciate it http://darkierawr.com/Android/Users/xboxfanj/FascinateSensemediafix.zip
istealhome, its a newer build than the one before at rootzwiki.
Click to expand...
Click to collapse
Well you could do that if you have the repo as well...
You could also save yourself some time by running "make bootimage"!
Related
NEW:
Working .34-rc3 kernel available at http://forum.xda-developers.com/showpost.php?p=6290443&postcount=45
OLD:
Code:
This is an experimental .34-rc2 kernel for the Nexus One.
Provided in the zip file is a folder (2.6.34-rc2-termana-nexusone) and the kernel (zImage).
It is extremely experimental, so only follow this if you [B][I][U]really[/U][/I][/B] know what your doing and know how to reflash another kernel back to make it boot again if it doesn't boot. I'm not responsible if your device curls over and dies.
Use adb to push the folder into /system/lib/modules/ and then use fastboot to flash the kernel.
The kernel is a rebase of cyanogen's .33.1 kernel to the latest .34-rc2 kernel. So nothing particularly new about it, besides the satisfaction that not many people would be running this kernel version on devices.
Zip file: bit.ly/94Oo6m (To download it click the link next to the text "Save file to your PC:")
Edit: Being a new member of xda-developers forum, it wouldn't let me post the link properly, but just copy and paste it and you'll be fine.
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
I just flashed the zimage, and the phone went into a boot loop. Do I have to install anything else?
jblazea50 said:
what folder are you talking about that needs to be pushed into /system/lib/modules/
there's only one folder in 2.6.34-rc2-termana-nexusone folder and that's kernel
also, is this kernel undervolted/overclocked/audio boost? can you give more info on the kernel itself?
thanks
Click to expand...
Click to collapse
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Will give it a go nad logcat it
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
thanks, thought it was a mistake that you said push that folder, glad you clarified it for me
thanks again
jlevy73 said:
Here is the changelog. Grab a cigarette and a cup of coffee it's damn long:
http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.34-rc2
Click to expand...
Click to collapse
damn, that is long; won't bother reading that thing
Termana said:
You have to push the 2.6.34-rc2-termana-nexusone folder, the whole thing, THAT folder, so that you end up with the a folder in /system/lib/modules called 2.6.34-rc2-termana-nexusone. There are no changes regarding undervolting, overclocking or audio boosting (unless cyanogen's kernel has included one of these) - but for general kernel changes jlevy73 provided a link to the mainline changelog.
Click to expand...
Click to collapse
I used this:
adb push 2.6.34-rc2-termana-nexusone /system/lib/modules/2.6.34-rc2-termana-nexusone
Click to expand...
Click to collapse
...and it still went into a boot loop for me.
hotweiss said:
I used this:
...and it still went into a boot loop for me.
Click to expand...
Click to collapse
You sure that wouldn't create a folder within a folder?
Not really sure just saying...
So is this working for you Termana?
I tried both have the subfolder and just pushing all the files to /modules and both produced a bootloop
i pushed the folder to /system/lib/modules/ and flashed zimage, but just get bootloop
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
I seriously thought, you tested it on your Nex before posting it....was a missunderstanding.
Termana said:
I should of been more clear. I released the kernel as extremely experimental as I don't have a Nexus One yet to test it on. I will be obtaining one in April/May some time. However, if people are willing to help me test these kernels, I will keep building and changing things until we get something that works. If no wants to help at all, then I will just wait until I obtain one to do any of this kind of work.
So if anyone does want to test, I will be doing another compile in the next day or two to be tested.
Click to expand...
Click to collapse
Did you cross compile the source against the ARM source?
hotweiss said:
Did you cross compile the source against the ARM source?
Click to expand...
Click to collapse
You might need to rephrase your question as the way you've said it doesn't let me know exactly what you mean by "ARM source". Do you mean using the Android ARM toolchain or what?
To anyone that is willing to help me test:
New build available at - bit.ly/c1tFqg (just the zImage, don't worry about pushing the modules for now)
Info:
This is a .33.1 kernel not a .34-rc2 kernel HOWEVER, I wanted to get the source that I'm rebasing off tested to make sure it boots, because if the source I'm pulling from doesn't boot, then obviously my rebases aren't going to either. So, please test it and tell me if it boots, if it does, I'll have another .34-rc2 kernel build up shortly after. If it doesn't, I may have to try rebasing from the official .32 kernel rather than the current source I'm rebasing from at the moment (which is .33.1).
Booted for me.
Code:
2.6.33.1-cyanogenmod
[email protected] #1
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Justin241982 said:
Should I post this in the kerenls list or wait till we know what it does, I dont think its a good idea to post yet with the noobs that might be flashin it and complaining.
Click to expand...
Click to collapse
I wouldn't post it yet. The first one he posted doesn't boot and the second one he posted I don't believe has any optimizations.
I managed to root my device by rooting one of the system dumps. With this I was able to pull our stock kernel.
The file is attached below, zipped so that the forum will allow it to be posted.
This is NOT a valid CWM flashable zip, do not try to flash it from CWM because it will not work! If you want to flash this kernel to return your device's kernel to stock, the following method has been tested:
Unzip the file, run the following command - this assumes that you have the commandline version of Heimdall installed.
Code:
heimdall flash --kernel zImage
Next up - extracting the initramfs and posting that to github.
Here is the initramfs from your kernel link.
http://www.mediafire.com/?z6yxc6z5fdkz1l2
designgears said:
Here is the initramfs from your kernel link.
http://www.mediafire.com/?z6yxc6z5fdkz1l2
Click to expand...
Click to collapse
Thanks, although already uploaded to github at https://github.com/Entropy512/initramfs_sgh-i777
ah, nice, didn't see your other thread
Entropy did u leave the infuse?
Sent from my SAMSUNG-SGH-I997 using xda premium
JordanElliott said:
Entropy did u leave the infuse?
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Indeterminate yet. Depends on:
1) GPS performance
2) Google Wallet support
If the GPS isn't a major improvement and GW doesn't work with the NFC chip in this device, I can't justify the cost of upgrading. I've got 30 days.
Entropy512 said:
Indeterminate yet. Depends on:
1) GPS performance
2) Google Wallet support
If the GPS isn't a major improvement and GW doesn't work with the NFC chip in this device, I can't justify the cost of upgrading. I've got 30 days.
Click to expand...
Click to collapse
Ok. Well I hope ull wait for the nexus prime or note
Sent from my SAMSUNG-SGH-I997 using xda premium
Entropy512 said:
I managed to root my device by rooting one of the system dumps. With this I was able to pull our stock kernel.
The file is attached below, zipped so that the forum will allow it to be posted.
This is NOT a valid CWM flashable zip, do not try to flash it from CWM because it will not work! If you want to flash this kernel to return your device's kernel to stock, the following method has been tested:
Unzip the file, run the following command - this assumes that you have the commandline version of Heimdall installed.
Code:
heimdall flash --kernel zImage
Next up - extracting the initramfs and posting that to github.
Click to expand...
Click to collapse
Wow, nice job, I go make a repacked stock kernel
Sent from my GT-I9100
Our phone has NFC. But how do we enable it? would that be kernel modifications? or general ROM mods?
tiwey said:
Our phone has NFC. But how do we enable it? would that be kernel modifications? or general ROM mods?
Click to expand...
Click to collapse
it has NFC but I dont think its being used at the moment.
tiwey said:
Our phone has NFC. But how do we enable it? would that be kernel modifications? or general ROM mods?
Click to expand...
Click to collapse
As far as I can tell it's enabled in the stock kernel. So what's missing is in userland. It may be as simple as a market filtering issue.
Entropy512 said:
As far as I can tell it's enabled in the stock kernel. So what's missing is in userland. It may be as simple as a market filtering issue.
Click to expand...
Click to collapse
Yes, here is some code of init.rc
Code:
# permissions for NFC
setprop ro.nfc.port "I2C"
chmod 0600 /dev/pn544
chown nfc nfc /dev/pn544
netchip said:
Yes, here is some code of init.rc
Code:
# permissions for NFC
setprop ro.nfc.port "I2C"
chmod 0600 /dev/pn544
chown nfc nfc /dev/pn544
Click to expand...
Click to collapse
That's pretty much part of the kernel (I consider initramfs part of the kernel) and just handling device permissions.
Unknown whether or not required userland libraries are present.
Entropy512 said:
That's pretty much part of the kernel (I consider initramfs part of the kernel) and just handling device permissions.
Unknown whether or not required userland libraries are present.
Click to expand...
Click to collapse
Yes, there a is not a service who enable nfc.
Maybe cyanogenmod can enable it.
Edit: this code set up also the interface for nfc.
Sent from my GT-I9100
Could someone tar this up for odin. Thanks.
Look here man: http://forum.xda-developers.com/showthread.php?t=1286432
agh1701 said:
Could someone tar this up for odin. Thanks.
Click to expand...
Click to collapse
+1
Sent from my SAMSUNG-SGH-I777 using xda premium
Do you not read before you post? Look at my above post, he has a different thread which has what you need.
abacon15 said:
Do you not read before you post? Look at my above post, he has a different thread which has what you need.
Click to expand...
Click to collapse
I just need the kernel. But anyway I flash with heimdall
Sent from my SAMSUNG-SGH-I777 using xda premium
So if I install this stock kernel, I should loose cwm and yellow triangle right? If this is the case then it should be a great way to return to stock!
Sent from my SGH-I777 using xda premium
Hey guys, we have here a kernel built from the kernel source HTC released on 8/29/12 for Vigor. This kernel is a modified version of what came in the Official 3.14.605.12 ICS OTA except it is built from HTC's kernel source release. What else can I say?
Bugs:
-?
Current features:
Perflock Disabled
Fast charge enabled using any power source - Thanks to Chad, I used his commits as a reference
Download:
Link Removed
Download Global OTA Compatible Version (Thanks to MicroMod for making it happen
Link Removed
Install:
Place zip on sd
Reboot to recovery (I use amon)
Install from zip
Select the zip file
The file will flash and then the phone will reboot to hboot
Once there, simple press power to select bootloader
Accept the update
It will install
Reboot your phone
????
Enjoy
Don't forget to go delete the PH98IMG.zip from your SD Card after boot.
Disclaimers:
I won't be responsible for what you flash on your phone or any damge that could be caused. Always use caution when modifying any part of your device.
Credits:
Thank con247 for the auto kernel flasher.
Thanks Chad for all your awesome kernel knowledge.
My Github for this kernel:
Link Removed
/// Info for new devs \\\
How to disable perflock in an HTC kernel through source
Simple, open you source. Open the arch/arm/configs. Find the file vigor_defcofig. Find the following lines:
Code:
CONFIG_PERFLOCK=y
CONFIG_PERFLOCK_BOOT_LOCK=y
Change them to:
Code:
# CONFIG_PERFLOCK is not set
# CONFIG_PERFLOCK_BOOT_LOCK is not set
Perflock is now disabled. Build your source
Changing the kernel name
Open the scripts folder in the root of your source. Find and open the file makecompile_h. Find the lines:
Code:
echo \#define LINUX_COMPILE_BY \"`echo $LINUX_COMPILE_BY | $UTS_TRUNCATE`\"
echo \#define LINUX_COMPILE_HOST \"`echo $LINUX_COMPILE_HOST | $UTS_TRUNCATE`\"
Edit how you want:
Code:
echo \#define LINUX_COMPILE_BY \"`echo wildstang83`\"
echo \#define LINUX_COMPILE_HOST \"`echo vigor-ics`\"
Enjoy
Is this a sense kernel? I know...but noobs should have heads up.
Sent from my HTC Rezound using xda premium
I'm going to keep count of the flood of kernels that are sure to come.
This is #1
Anyway will download tomorrow, way too tired right now
Sent from my Nexus 7 using Tapatalk 2
What makes this different from the stock ones?
apophis9283 said:
What makes this different from the stock ones?
Click to expand...
Click to collapse
As far as I know, absolutely nothing. I could be wrong though. Some of you that remember the Incredible or Thunderbolt will remember how the kernel that was in the ota for those devices and the kernel source released after the ota were different. HTC had added in minor fixes to the kernel source release that was not in the ota. I don't know if that is the case here, just a thought though.
It's not different. Lmao read the title. Looking forward to see what come from this, stang
Sent from my ADR6425LVW using Tapatalk 2
antp121 said:
It's not different. Lmao read the title. Looking forward to see what come from this, stang
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Exactly, we can assume this kernel is no different from the one in the OTA. Unless of course someone else can prove otherwise.
wildstang83 said:
As far as I know, absolutely nothing. I could be wrong though. Some of you that remember the Incredible or Thunderbolt will remember how the kernel that was in the ota for those devices and the kernel source released after the ota were different. HTC had added in minor fixes to the kernel source release that was not in the ota. I don't know if that is the case here, just a thought though.
Click to expand...
Click to collapse
Is that Kernel still perflocked?
Not totally familiar with what could be different between stock and custom built stock from source.
Quantumrabbit said:
Is that Kernel still perflocked?
Not totally familiar with what could be different between stock and custom built stock from source.
Click to expand...
Click to collapse
If built as is from source, I'd say yes. Give the devs some times, you'll see them come out with perflock removed.
mjones73 said:
If built as is from source, I'd say yes. Give the devs some times, you'll see them come out with perflock removed.
Click to expand...
Click to collapse
Right, this kernel was not intended to be custom in anyway whatsoever. It is simply a kernel built from source. I know I like stock things, I'm sure others do as well.
i honestly love you wild stang. and neo and mbobino.
Nice work stang
Sent from my ADR6425LVW
I got a stock build with PERFLOCK disabled building right now. I'll upload that to the OP in just a minute.
I love you
Sent from my Nexus 7 using Tapatalk 2
Perflock disabled version added to OP.
Will this work with sense 4 roms?
i guess with perflock disabled, we could underclock? or at least change the governors and stuff using cpu controller apps?
apophis9283 said:
Will this work with sense 4 roms?
Click to expand...
Click to collapse
in theory, yes. would i attempt it? not quite yet.
antp121 said:
in theory, yes. would i attempt it? not quite yet.
Click to expand...
Click to collapse
Should be fairly simple to insure a Sense 4 version. Just grab a sense 4 boot.img like newtoroots or whatever, open it up in android kitchen and drop in the zimage from my kernel's zip. Repackage the boot.img and fastboot flash it. ant, you should try it
wildstang83 said:
Should be fairly simple to insure a Sense 4 version. Just grab a sense 4 boot.img like newtoroots or whatever, open it up in android kitchen and drop in the zimage from my kernel's zip. Repackage the boot.img and fastboot flash it. ant, you should try it
Click to expand...
Click to collapse
sounds a little bit difficult for an end user just like me with no idea about dev things
Sent from my ADR6425LVW using xda premium
I asked for help to build a rom ics on our xt615
I present the trick:
we recover a leak motorola ics for our phone (. sbf)
we extracted the boot.img system.img recovery. etc. .....
we have for the moment a Chinese cwm recovery but works in English or a problem with the nandroid
the problem is that when trying to build the rom for our phone and flash that we have a "status 0"
then here we ask a person who could help us build a rom ics
thank you
links:
extracted from sbf
https://docs.google.com/file/d/0B2k1N5APM4JQLWZ3ajVETG54UTQ/edit
testing the construction of the ROM
https://docs.google.com/file/d/0B2k1N5APM4JQaWF0N0Q0TV9pWTA/edit
and the subject of motoluxe xt615 not play pass all first pages on pages 65 to
http://forum.xda-developers.com/showthread.php?t=1660377&page=77
Up please
Thank
Sent from my XT615 using xda app-developers app
I don't know anything about your phone, but your zip file is incorrect.
You want to put all the files except META_INF into a folder called system. Look in META_INF/com/google/android/updater-script and you will see this is what the recovery is expecting.
Also, add a boot.img since it will try to flash that as well.
This is what the root directory of the zip file should look like:
Code:
[email protected]:/android/work/moto/zipper# ls
boot.img META-INF system
[email protected]:/android/work/moto/zipper# ls system/
app bin build_proj etc framework media usr
arcsoft build_id build.prop fonts lib tts xbin
gee one said:
I don't know anything about your phone, but your zip file is incorrect.
You want to put all the files except META_INF into a folder called system. Look in META_INF/com/google/android/updater-script and you will see this is what the recovery is expecting.
Also, add a boot.img since it will try to flash that as well.
Click to expand...
Click to collapse
Yes but try various solution and i have always error status 0
If you look the topic we have try
Page n° 70\80
Thank
Sent from my XT615 using xda app-developers app
gee one said:
This is what the root directory of the zip file should look like:
Code:
[email protected]:/android/work/moto/zipper# ls
boot.img META-INF system
[email protected]:/android/work/moto/zipper# ls system/
app bin build_proj etc framework media usr
arcsoft build_id build.prop fonts lib tts xbin
Click to expand...
Click to collapse
I don't understand
I took example on several
can you help me to do this update
A big thank
Sent from my XT615 using xda app-developers app
I read that thread a little- it looks like a lot of people trying different things. Also, use post numbers because it's page 17 on my computer
So, where did the updater-binary and script come from? The script has to match the rom, but I think the binary is a lot more forgiving. I think a binary from another ics or gb rom should work. Your phone uses yaffs, so maybe an older binary? I thought a lot of the ics devices were moving to ext3/4?
I think the stock recovery won't work. Usually, they will only accept zips that are signed by the manufacturer.
sent while running with scissors
gee one said:
I read that thread a little- it looks like a lot of people trying different things. Also, use post numbers because it's page 17 on my computer
So, where did the updater-binary and script come from? The script has to match the rom, but I think the binary is a lot more forgiving. I think a binary from another ics or gb rom should work. Your phone uses yaffs, so maybe an older binary? I thought a lot of the ics devices were moving to ext3/4?
I think the stock recovery won't work. Usually, they will only accept zips that are signed by the manufacturer.
sent while running with scissors
Click to expand...
Click to collapse
we have a custom recovery rom just leaked motorola
I built the rom update with kitchen
I get a flash of themes yet but they put me in error
and I saw no or that I can just
I can not make a updater-script
can you tell me the way to follow
Thank
Sent from my XT615 using xda app-developers app
dams161 said:
we have a custom recovery rom just leaked motorola
I built the rom update with kitchen
I get a flash of themes yet but they put me in error
and I saw no or that I can just
I can not make a updater-script
can you tell me the way to follow
Thank
Sent from my XT615 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=31086093
Sent from my XT615 using xda app-developers app
Flash at your own risk- I didn't read the thread and I wouldn't know you device from an iphone.
https://rapidshare.com/files/2281343112/xt615ics1.2_mod1.zip
I cleaned up the system and added the boot.img. if you can get the /etc/recovery.fstab from your recovery, it might help since the partitions might have different names.
sent while running with scissors
gee one said:
Flash at your own risk- I didn't read the thread and I wouldn't know you device from an iphone.
https://rapidshare.com/files/2281343112/xt615ics1.2_mod1.zip
I cleaned up the system and added the boot.img. if you can get the /etc/recovery.fstab from your recovery, it might help since the partitions might have different names.
sent while running with scissors
Click to expand...
Click to collapse
thank you
i try and i say if work
does not work I toujour error status 0
I think that is an error with the update binary. Maybe you can get one from a similar phone? It should be pretty generic, as long as it uses a similar file system/android version. So try to find a binary from an ics device that uses yaffs/MTD.
sent while running with scissors
i try and i say if work
yes works but the boot.img is bad thank you
I thought this was the stock firmware? Could you just put in a similar ics kernel and see if that works? A kernel from an ics moto phone might work, but you'll have to change the ramdisk.
sent while running with scissors
gee one said:
I thought this was the stock firmware? Could you just put in a similar ics kernel and see if that works? A kernel from an ics moto phone might work, but you'll have to change the ramdisk.
sent while running with scissors
Click to expand...
Click to collapse
the concern is that the bootloader is locked
and I think he does not want ics files
you have ideas on how to bypass the UNLOCK or
thank you again
Do you have a copy of a working boot.img or kernel? Even a dump from a running phone would work.
sent while running with scissors
gee one said:
Do you have a copy of a working boot.img or kernel? Even a dump from a running phone would work.
sent while running with scissors
Click to expand...
Click to collapse
my boot.img
So the zip that I uploaded flashes, but it doesn't boot?
I think your working boot image is GB or Froyo and the new one is ICS. So maybe if I take the kernel from the ICS boot.img and add the ramdisk from your working one, then maybe it might work.
Maybe...
This is the new kernel with the old ramdisk. Again, flash at your own risk.
https://rapidshare.com/files/908298923/xt615ics1.2_mod3.zip
Hello
I am thinking of porting a Galaxy S2 4.1.2 stock touchwiz jb rom to the galaxy player 5.0 probably using cm10 as a base.However, porting requires someone to modify the player 5.0 boot.img which I can't do and I can't compile a kernel as I don't know how to do so and I don't hav Linux.I can tell the volunteer what file in the ramdisk should be modified in order to possibly have a working s2 4.1.2 port.
So is there anyone with a player 5.0 willing to either unpack the player 5.0's boot.img or compile the kernel from source with the modification I will tell you?
This project may actually succeed with the help of the community so I hope that you can help.
Thanks
I98 said:
Hello
I am thinking of porting a Galaxy S2 4.1.2 stock touchwiz jb rom to the galaxy player 5.0 probably using cm10 as a base.However, porting requires someone to modify the player 5.0 boot.img which I can't do and I can't compile a kernel as I don't know how to do so and I don't hav Linux.I can tell the volunteer what file in the ramdisk should be modified in order to possibly have a working s2 4.1.2 port.
So is there anyone with a player 5.0 willing to either unpack the player 5.0's boot.img or compile the kernel from source with the modification I will tell you?
This project may actually succeed with the help of the community so I hope that you can help.
Thanks
Click to expand...
Click to collapse
I can modify, the kernel source to load a ramdisk.cpio from a static folder... I was planning on doing that any way...:good:
All you would have to do is create a ramdisk.cpio with the cpio command, I think...
Meticulus said:
I can modify, the kernel source to load a ramdisk.cpio from a static folder... I was planning on doing that any way...:good:
All you would have to do is create a ramdisk.cpio with the cpio command, I think...
Click to expand...
Click to collapse
Ok great, I might then start this project on the weekend
Thanks
I98 said:
Ok great, I might then start this project on the weekend
Thanks
Click to expand...
Click to collapse
I made the change for the kernel to load external ramdisks:
https://github.com/Meticulus/nutell...mmit/e5e17f478018d84c866f7ec829c17e0272bf0231
here is a build of the kernel with this change and the current carbon ramdisk. You can use the "cpio" tool to make/extract/repack cpio ramdisks..:good:
https://mega.co.nz/#!ZJVDWTxT!tep0VH1nmfCTxYqhDHmUfROxq-O1Joro2_RiJWqd6RI
Meticulus said:
I made the change for the kernel to load external ramdisks:
https://github.com/Meticulus/nutell...mmit/e5e17f478018d84c866f7ec829c17e0272bf0231
here is a build of the kernel with this change and the current carbon ramdisk. You can use the "cpio" tool to make/extract/repack cpio ramdisks..:good:
https://mega.co.nz/#!ZJVDWTxT!tep0VH1nmfCTxYqhDHmUfROxq-O1Joro2_RiJWqd6RI
Click to expand...
Click to collapse
Thanks
but when I'm using this command on Cygwin:
cpio -i -F ramdisk.cpio
I'm getting an error, bash: cpio command not found
Any suggestions?
Meticulus said:
I made the change for the kernel to load external ramdisks:
https://github.com/Meticulus/nutell...mmit/e5e17f478018d84c866f7ec829c17e0272bf0231
here is a build of the kernel with this change and the current carbon ramdisk. You can use the "cpio" tool to make/extract/repack cpio ramdisks..:good:
https://mega.co.nz/#!ZJVDWTxT!tep0VH1nmfCTxYqhDHmUfROxq-O1Joro2_RiJWqd6RI
Click to expand...
Click to collapse
Thank you very much
but when I'm using this command on cygwin:
cpio -i -F ramdisk.cpio
I'm getting an error, bash: cpio command not found
Any suggestions?
Thanks again
I98 said:
Thanks
but when I'm using this command on Cygwin:
cpio -i -F ramdisk.cpio
I'm getting an error, bash: cpio command not found
Any suggestions?
Click to expand...
Click to collapse
Looks like WinRAR has support for cpio?... never tried it but...
Meticulus said:
Looks like WinRAR has support for cpio?... never tried it but...
Click to expand...
Click to collapse
Yeah, I tried it with WinRAR but it still didn't work, I've tried another tool but it didn't work ..
btw, is it just possible to place the init.rc file in the folder as that is the only file that has to be modified?
I98 said:
Yeah, I tried it with WinRAR but it still didn't work, I've tried another tool but it didn't work ..
Click to expand...
Click to collapse
1. Linux on a virtual machine.
2. push the ramdisk to your player using adb. Then, use cpio in adb shell on device or terminal emulator.. :good: