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
Related
I have re-written the ICS camera HAL module to be a thin wrapper for the gingerbread libcamera.so and hence it will only work with the 2.6 kernel. The advantage is that getting to gingerbread level functionality should be quick Creating a new thread because there is a slight chance that this will work for all qualcomm devices with existing libcamera.so files (with slight mods ofcourse )
http://www.mediafire.com/download.php?wjf035mz2vzunw4
Here is a zip file which contains the new camera HAL module. README file accompanying it has instructions on the locations for the files. If you already have the previous version of camera HAL working, all you have to do is replace camera.qsd8k.so and libcamera.so with the ones in the zip file.
What works:
1) Preview works.
2) Taking a picture works pretty well.
3) Size of picture is no longer huge.
4) Software zoom works.
5) Most of the other knobs like focus, file size etc. seemed to work as well in my testing.
6) Pretty stable as far as I can see
Not working yet:
Video and other fancy stuff.
If people have requests for other qualcomm devices after having tried the HAL included in the zip file, kindly include the following information.
1) logcat from having used the HAL module.
2) build.prop
3) libcamera.so from gingerbread ROM for the device.
4) liboemcamera.so from gingerbread ROM.
Currently known to work on the following devices:
1) Nexus One.
2) HTC Desire
3) HTC HD2
Enjoy and thanks for all the feedback.
Updates:
02/09/2012
Working barcode scanner mode
Flashable zip file (should work with texasice's ROMs)
http://www.mediafire.com/?w4fu0u05qtxq3tu
01/30/2012
Working Panorama mode
Flashable zip file (should work with texasice's ROMs)
http://www.mediafire.com/?5r599m5jg5yfaqn
Known issues:
Sometimes screen has some garbage while in Panorama mode viewfinder. Quitting completely from the app and restart or invoking Gallery from inside the app and returning back to camera app should mostly fix it.
Video enabled version:
Fastboot compatible images compiled from evervolv base:
For Stock hboot :
http://www.mediafire.com/?wdlip7h6necetia
For HBoot(s) supporting larger /system partition
http://www.mediafire.com/?f6rz3sz2r97qln0
Source code is now available at
https://github.com/rapmv78/
Your upload doesn't include a HAL, and from your instructions I am not sure if you are implying to use the HAL and the GB libcamera and liboemcamera, or the ones included.
please show me what i have to type in adb to push these files? (sorry i'm noob)
is camera.qsd8k.so not included?
sorry for my english..
Sorry wrong link. Now updated. Please re-download. And yes the files need to pushed through adb.
One step closer!
Thank you!
twistedumbrella said:
Your upload doesn't include a HAL, and from your instructions I am not sure if you are implying to use the HAL and the GB libcamera and liboemcamera, or the ones included.
Click to expand...
Click to collapse
Link fixed. The files included in the zip are the ones to be used. The generic libs part is only for people with non nexus one devices and would want help enabling camera on them. Hope this clarifies better.
Is the code specific to qsd8 or just a generic wrapper function? On most "newer" devices you are looking at msm7x30, but generic qsd8 code, much like the gralloc, would still work with a rename.
Sent from my ADR6400L using Tapatalk
rapmv78 said:
Sorry wrong link. Now updated. Please re-download. And yes the files need to pushed through adb.
Click to expand...
Click to collapse
if i have installed the previous version, is it right what i have to type in adb?
Code:
adb remount
adb push libcamera.so /system/lib/libcamera.so
adb push camera.qsd8k.so /system/lib/hw/camera.qsd8k.so
adb reboot bootloader
fastboot flash boot boot-new.img
fastboot reboot
please help, i don't know what to do..
thanks..
mulerokeh said:
if i have installed the previous version, is it right what i have to type in adb?
Code:
adb remount
adb push libcamera.so /system/lib/libcamera.so
adb push camera.qsd8k.so /system/lib/hw/camera.qsd8k.so
adb reboot bootloader
fastboot flash boot boot-new.img
fastboot reboot
please help, i don't know what to do..
thanks..
Click to expand...
Click to collapse
If you have previously working camera, you can skip flashing the boot-new.img file. It is there for people who do not have existing ics camera hal. Rest looks fine to me.
twistedumbrella said:
Is the code specific to qsd8 or just a generic wrapper function? On most "newer" devices you are looking at msm7x30, but generic qsd8 code, much like the gralloc, would still work with a rename.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
It is just a wrapper, but is dynamically linked with the libcamera.so file. So, if kernel change does not change structs and constants, things will work fine with a rename as you suggest. Otherwise it will not.
Maybe you should ask @charnsingh_online help for video, as he already works on 720p for N1
rapmv78 said:
It is just a wrapper, but is dynamically linked with the libcamera.so file. So, if kernel change does not change structs and constants, things will work fine with a rename as you suggest. Otherwise it will not.
Click to expand...
Click to collapse
So what were the kernel changes?
twistedumbrella said:
So what were the kernel changes?
Click to expand...
Click to collapse
There are none in this hal, that is why it works. What I was intending to say was that if MSMx30 kernel uses different size structs/constants it will not work.
rapmv78 said:
There are none in this hal, that is why it works. What I was intending to say was that if MSMx30 kernel uses different size structs/constants it will not work.
Click to expand...
Click to collapse
That is why I asked if it was generic code or specialized to qsd8. If the kernel code was not edited, that will be irrelevant because the source is not built (at least not by anyone other than CAF) using an inline kernel.
twistedumbrella said:
That is why I asked if it was generic code or specialized to qsd8. If the kernel code was not edited, that will be irrelevant because the source is not built (at least not by anyone other than CAF) using an inline kernel.
Click to expand...
Click to collapse
The hal code itself is generic, but it depends on libcamera.so, which inturn depends on kernel structs and constants to match the running kernel for successful control ioctls/pmem etc.
Can confirm this works on HTC Desire exactly as mentioned in OP.
Sent from my HTC Desire using XDA App
I tried it with (Texas)Ice ICS ROM and network not work. Failed to load driver! Need flash another kernel?
sucon said:
I tried it with (Texas)Ice ICS ROM and network not work. Failed to load driver! Need flash another kernel?
Click to expand...
Click to collapse
it works for me, but sometimes not responding after take 2 or 3 photos..
but great work!!
Sent from my Nexus One using xda premium
sucon said:
I tried it with (Texas)Ice ICS ROM and network not work. Failed to load driver! Need flash another kernel?
Click to expand...
Click to collapse
Works both fine with texasice ICS!
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"!
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
Any devs working on a stock Read and Write kernel? so we can finally get rid of all the ATT bloat without it coming back? Or are we just waiting for kernel source?
Fidelio_o said:
Any devs working on a stock Read and Write kernel? so we can finally get rid of all the ATT bloat without it coming back? Or are we just waiting for kernel source?
Click to expand...
Click to collapse
It's available, somebody just needs to use a hex editor to make the module load with whatever kernel version AT&T uses.
http://forum.xda-developers.com/showthread.php?t=2230341
flar2 said:
It's available, somebody just needs to use a hex editor to make the module load with whatever kernel version AT&T uses.
http://forum.xda-developers.com/showthread.php?t=2230341
Click to expand...
Click to collapse
Was there only the one string for the kernel version towards the top? If so - here it is for kernel 3.4.10-g3de55a2
Note: not a flashable zip... the module is inside, just couldn't attach it as a .ko
homeslice976 said:
Was there only the one string for the kernel version towards the top? If so - here it is for kernel 3.4.10-g3de55a2
Note: not a flashable zip... the module is inside, just couldn't attach it as a .ko
Click to expand...
Click to collapse
Not sure what am supposed to do with the module
Sent from my HTC One using xda premium
I flashed Android Revolution 7.0 and none of the apps I delete or any of the bloat he deleted came back.
Sent from my HTC One using XDA Premium HD app