So, I'm trying something that's probably doomed to failure but I thought was worth a go:
Take the excellent kernel / binaries that Cyanogen has produced and add some hero goodness.
It's currently flashing onto my phone.....
edit: install from sdcard complete... lets see if it boots.
edit2: epic fail. I removed the odex files from the rom when I built it since cyanogen's rom didn't have any... however, on boot I got a complaint about 'no odex file found'...so, I've now added them back in to see if I can boot.
boot attempt 2....
hmm, I'm getting this error on boot... anyone got any ideas?
Code:
bionic/linker/linker.c:1580| ERROR: 75 could not load 'libstdc++.so'
bionic/linker/linker.c:1640| ERROR: failed to link /system/bin/sh
bionic/linker/linker.c:1752| ERROR: CANNOT LINK EXECUTABLE '/system/bin/sh'
did a full wipe, format, reinstall... same error. Hmm. maybe if I describe my methodology someone can see where I'm going wrong:
I took cyanogen's latest rom, extracted everything. took drizzy's latest rom, extracted that somewhere else. then deleted the apps folder from the cyanogen rom and copied in all the apps from Drizzy's rom. Used the update script from cyanogen. Also copied in the /system/framework from Drizzy's (since it's all jars and apks).
Basically anything java based is from Drizzy's rom, everything else is from Cyanogen's.
My thinking is that if everything that's a compiled binary comes from Cyanogen, and the boot.img is from cyanogen then I should be able to use the hero APKs from somehere else without a problem. Apparently not though :/
I assume you have done it, but are you sure libstdc++.so is there? And did you try with another version with the library?
it is in there... maybe I just got unlucky and got a corrupt download or archive somewhere along the way.
I'll try again tonight
Okay, just a tried a rebuild using a different Hero rom (Qteks) and got a slightly different error on boot:
Code:
bionic/linker/linker.c:1580| ERROR: 62 could not load 'libc.so'
bionic/linker/linker.c:1640| ERROR: failed to link /system/bin/sh
bionic/linker/linker.c:1752| ERROR: CANNOT LINK EXECUTABLE '/system/bin/sh'
I don't even know where to start troubleshooting this really...
i have also tried this. When i managed to get it all to boot (removing all odex files and other unwanted crud) it went through all the setups etc then when it restarted the HERO Startupo gif and sound were extremely slow and played twice witjh about 500ms difference so it was like when your a kid singing fre ra jaqua (or whatever)
Giod knows y tbh.I also tried to put the modified launcher in the rom but no joy?
If you try installing apps from a hero ROM update it says "this app cannot be installed on this model"
|Maybe try figuring why hero apps wont run first, Then it may solve it?
FIRST OFF I TAKE NO CREDIT WHAT SO EVER FOR ANY OF THIS I AM CLEARLY LETTING YOU GUYS kNOw ABOUT PETES NEW ROM.
Hey guys I was looking around and couldnt find anything about Pete's new Rom for the Og droid. I have flashed it myself and personally love it so I thought I would share it with you guys that havent visited petes page. Here is the link to his website>>>> http://www.peteralfonso.com/
If you like it I would consider donating to him, he does great work.
Thanks you guys for everything!!
Here is what Pete has to say straight from his page, (Agian I take no credit this is strictly me copying and pasting from Peter's Page.)
I would like to present to you a clean stock Gingerbread (Android 2.3.2) ROM. Although this build is stock, I spent many hours modifying it to my liking. First off let me start by saying compiling Gingerbread for the Droid is a pain, goodluck to those who are attempting this process. On that note, I would like to say thank you to actngrezy for answering my questions about Gingerbread specific compiling. Secondly, but no less important, I would like to say thank you to the CyanogenMod community, specifically the maintainers for the Droid, cvpcs, mtwebster, and koush. Without the efforts of this community we (Droid users) would not have a stable, fully functional Gingerbread build.
So how is this build different from other Gingerbread ROMs?
For starters, this build was made using the master branch of the AOSP only two days ago, meaning it not only brings you to version 2.3.2 but it also has the latest bug fixes included. Once you flash this ROM you will immediately see how much time I spent making this build exactly how Motorola would have provided it to you (if they still supported our "old" device). This ROM has the stock signature Droid boot animation, ringtones, wallpaper set, 2D Launcher, and Neural Network live wallpaper. Additionally, I have implemented many of my own bug fixes and others provided by the development community. I also went ahead and enabled the Sound Recorder and Camcorder shortcuts because I find them useful.
Since Motorola will never "officially" provide the Droid with a Gingerbread build, we will never have accurate build numbers (e.g. FRG83) to go by. Because of this I have decided to create my own build numbers and always maintain an updated stock build for the Droid here on my website in the Downloads section. Upon installing this ROM, you will notice a build number of GPA10. The first letter stands for Gingerbread, second letter Peter, third letter Alfonso, and a number that will increase as I release future updated builds.
This ROM is to be treated as if it were an update straight from Motorola. For those learning to develop or those who base their ROMs off of stock builds you may use this ROM, modify it, and distribute it as your own. I do ask that you provide a link to my website wherever you distribute it. Also, please do not reupload this ROM elsewhere if you have not modified it in any way. I would like to keep track of the download count.
If you have not read about the amazing features that Gingerbread brings, I encourage you to visit Android.com to learn more. Also, don't forget that the new market.android.com is now live and works well with this ROM. While you're there you may notice that Android 2.3.3 is on its way, when it comes I will bring it to you. Be sure to give Google a "thank you" by setting you and you're friends home page to Google.com!
I did not include ANY market apps in this ROM other than Car Home (because I included an updated version not available in the Market yet) and Quick Search Box (if you do not include this app, the search key will not work properly). Having said that, after the installation I recommend downloading YouTube, Gmail, Street View, Voice Search, Maps, and Flash Player. For those of you wanting a boost of performance without the need of a CPU scaling application, download and install AutoOverClock.zip which will bring this ROM to 800mhz. If you decide to flash an alternate kernel, it will automatically overclock itself to the highest available slot.
Ok, I am done rambling...follow me on Twitter and enjoy!
Do you use setcpu to scale your kernel using this rom?
Peter Alfonso Gingerbread
PA said the kernel needs to be a minimum of 800mhz, does this mean you cant scale it? or can you still? Just wondering
Issue with Install Abort
I've followed his instructions, but after clearing all on my rooted DROID 1, cache, and all data, i still get a 'installation aborted' message and am forced to reboot without completing.
I searched the comments within Peter's article and can't find this same alert message and it seems pretty easy and people have been doing it....so i'm assuming this is a noob thing.
I've rooted using super one click. Only other root experience i have is the auto nooter method with my nook color. I know i have the root working, since my DROID was doing fine with wireless tethering to my NC. If it depends on the exact text that appears right before my install abort message then let me know and i'll do it again to post exactly what its doing trying to boot from Peter's rom on the sd card.
EDIT: Screen text
--Install from sdcard...
Finding update package...
Opening update package..
Verifying update package...
Installing update...
assert failed: filegetprop("/system/build.prop",
"ro.build.fingerprint") == "verizon/voles/sholes/sholes:2.1-update1/ESE81/29593:user/release-keys"
||
file_getprop("/systembuild.prop",
"ro.build.fingerprint") == "verison/voles/sholes/sholes:2.2/FRO1B/45394:user/release-keys"
E:Error in /sdcardupdate.zip
(Status 7)
Installation aborted
Anyone have this issue?
Have success now with GPA14. I saw the difference, in the boot menu there was no option to select the .zip file from the sd card, only to install from sd card (that was what i saw attempting Peter's GPA13 file).
GPA14 had the other option, and obviously, when you are able to choose the file, it starts and completes in a minute.
Droid 1 now has a nice Android 2.3.3. on it. sweetness.
I am trying to compile a custom kernel,
I succeed to build one but I can't boot him, when I load the kernel I go in to boot loop
I haven't made any real changes to this kernel I really just downloaded the source and compile it
The version match its a GB kernel 2.6.35.7 I disabled the lag fix, still it goes to boot loop.
any ideas?
What source code did you try to use to build this kernel? Links would be awesome.
Well I tried this two
Code:
github.com/Krylon360/SGS4G_Kernel_GB
opensource.samsung.com/index.jsp (SGH-T959V-TMB_GB_Opensource.zip)
I did
make clean && make mrproper
make vibrantplus_rev00_defconfig
make -j8
and then I loaded the kernel via heimdall
Building the stock kernel
I have run in to a similar problem. One issue I had to get past is the stock rom source does not have have the initramfs included. It is needed so the kernel can boot into a file system before it can start loading loadable modules and mount the rom filesystem.
I have been able to get an initramfs by extracting it from the original rom, The issue I have is it is loading all modules, but the rom devices will not mount as the /dev directory is empty and the mount needs them to mount the file systems.
This may be off topic for this forum. If you want to PM me, I'm willing to let you know what I have found out.
Tom
You should keep discussing it here since it does pertain to the phone and it'll be useful for future reference
Sent from my SGH-T959V using XDA App
Agree with FB.
I have ran into the same problem. I was unable to find a way to get it beyond boot loop so I scratched the project. I am definitely curious on how to get this working.
FBis251 said:
You should keep discussing it here since it does pertain to the phone and it'll be useful for future reference
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
DISCLAIMER
I am NOT a kernel developer, just a programmer that has done linux programming before, and is trying to understand and build the kernel.
I will share what I have found out through my attempts to build the stock rom as delivered from Samsung.
I have searched XDA and Googled the web in search of the answers I need with some success as well as dead ends. I am not looking to have the answers handed to me on a silver plate, but a few hints or links to point me in the right direction is helpful.
To start:
Recommended Hardware needed:
Search the XDA for AdamOutler threads on building the serial interface via the USB. Highly recommended reading as it helps to see what the kernel is doing when it is in the bootloop. All the important parts was purchased from his recommended supplier(s). Thanks AdamOutler for the information!
What I know about the samsung kernel source as delivered:
1) if you follow the readme in the kernel, it will build cleanly. However, it will NOT run, it will bootloop!!
2) If you intend to only build the stock kernel, I recommend making sure you are starting with a stock build installed on the phone. I suggest the same release version you are trying to build.
3) After you build the kernel and load it ( the zImage file is loaded via Heimdall ) the first problem I ran into was the initramfs. It is not included in the source and must be created from scratch or obtained from another kernel.
4) Once the initramfs is being built and included in the kernel, the next problem is the driver modules that are included, have to have the same version as the kernel. You will need to figure out the version by the kernel debug messages on the serial/usb interface mentioned above. Once the versions match, the kernel will load them.
This is where I am stopped... once the drivers are loaded, the init scripts mount the file systems. This does not happen with my kernel. I am still investigating this. I think it has to do with the /dev files for the mount points not being created/missing. I have not found the piece of info yet points me to the solution. Most of the links I have found pertain to linux on an x86/64 platform. I have found little on embedded linux and how it works.
That is all I have in a nutshell. Feel free to comment and ask questions. Remember to search! Use different forms of your search terms, use different working. I like to use the 'yippy.com' search engine as it places the results in categories.
Good luck!
Tom
logan123 said:
Well I tried this two
Code:
github.com/Krylon360/SGS4G_Kernel_GB
opensource.samsung.com/index.jsp (SGH-T959V-TMB_GB_Opensource.zip)
I did
make clean && make mrproper
make vibrantplus_rev00_defconfig
make -j8
and then I loaded the kernel via heimdall
Click to expand...
Click to collapse
Krylon's tree is stock, no changes.
It has all the problems I fixed in my tree.
I have a lot of uncommitted changes, but you can find my work at: https://github.com/bhundven/
Regardless of me being on xda or not, I am still working on sgs4g.
bhundven said:
Krylon's tree is stock, no changes.
It has all the problems I fixed in my tree.
I have a lot of uncommitted changes, but you can find my work at: https://github.com/bhundven/
Regardless of me being on xda or not, I am still working on sgs4g.
Click to expand...
Click to collapse
Aww hell bhundven! Refreshing to see you stop by!
Thank you everyone
mccabet, You actually saved me some time because those were my next two step
I was looking for the initramfs and I didn't find it...
Could you please share your?
I do not have my initramfs file available to me at work. So here is the info I used to get my copy. You will need an original rom release ( I used the heimdall one-click from bhundven ) to extract the zImage file from.
Here is the link to info on how extract your own initramfs from a kernel image (zImage):
http://forum.xda-developers.com/wiki/index.php?title=Extract_initramfs_from_zImage
I used the improved script mentioned at the bottom of the page from:
https://github.com/mistadman/Extract-Kernel-Initramfs
After getting your initramfs, you will need to modify your vibrantplus_rev00_defconfig file and change the following parameter to point to your initramfs you extracted:
CONFIG_INITRAMFS_SOURCE="/path/to/initramfs"
Hope that helps.
Tom
Ok it seems like I was able to boot the kernel, no more boot loops thank to the initramfs but
The system isn't loading, it get stuck on the "Galaxy S 4G" page.
and when I load recovery it gives me lots of error so as
E:Can't mount /cache/recovery/log
E:failed to mount /cache (No such file or directory)
it goes on and on but its all the same...
logan123 said:
Ok it seems like I was able to boot the kernel, no more boot loops thank to the initramfs but
The system isn't loading, it get stuck on the "Galaxy S 4G" page.
and when I load recovery it gives me lots of error so as
E:Can't mount /cache/recovery/log
E:failed to mount /cache (No such file or directory)
it goes on and on but its all the same...
Click to expand...
Click to collapse
I may be off-base, but do you know if /cache and the other file systems were the Samsung rfs filesystem or the ext4 filesystem? Standard recovery can't mount ext4 & if your kernel doesn't support it, then it won't be able to mount them, either.
I thought so too so I removed the lag-fix and return to rfs
but this is neither because apparently there are no stl devices :\
I pulled out the recovery log
Code:
http://pastebin.com/hDCNbdne
Code:
failed to mount '/dev/block/stl11' '/cache'(rfs) -> No such device
Now I feel like an idiot because I can't seem to find what is it in the kernel config
moreover I tired to pull a config from a working kernel and I basically got the same errors
Any ideas?
Well the solution is simple, apparently version magic didn't load the kernel modules
for rfs_fat and fsr_stl...(you get the point)
now I can't to find way to compile them it seems as if someone removed them from the kernel tree and I can't load them either
I tired several modules from different kernel well all result in failure.
so any ideas?
logan123 said:
Well the solution is simple, apparently version magic didn't load the kernel modules
for rfs_fat and fsr_stl...(you get the point)
now I can't to find way to compile them it seems as if someone removed them from the kernel tree and I can't load them either
I tired several modules from different kernel well all result in failure.
so any ideas?
Click to expand...
Click to collapse
I wish had some, man. I've never compiled a kernel for Android. At least, not yet. However the moduel code should be somewhere in the kernel tree. I believe Android is a layer on top of the Linux kernel so the source may be there.
I'm still reading about and learning the platform side of Android. Hopefully one of the devs around can provide some solid guidance.
Ok no offence but this kernel is worthless
even if I load the modules into the kernel I get a errors because of the unknown symbols
bahh any ideas anyone?
stephen_w said:
I wish had some, man. I've never compiled a kernel for Android. At least, not yet. However the moduel code should be somewhere in the kernel tree. I believe Android is a layer on top of the Linux kernel so the source may be there.
I'm still reading about and learning the platform side of Android. Hopefully one of the devs around can provide some solid guidance.
Click to expand...
Click to collapse
That is as far as I have gotten. The drivers for the RFS ( drivers/tfsr ) are not loading and therefore the /dev mount points do not exist. The default build config flags ( CONFIG_RFS_FSR=m and CONFIG_RFS_FSR_STL=m ) are to build the module as a loadable module. I have tried to build the module with no success. Still investigating when I have the time. I was even thinking of looking at the Epic 4G MTD build and trying that. The problem there is if I can not solve this problem, I probably solve it by trying the MTD conversion. ( Except to brick it.)
if one of you kernel devs gets a bootable MTD kernel hit me up... I got a rom that needs some mtd loving
RaverX3X said:
if one of you kernel devs gets a bootable MTD kernel hit me up... I got a rom that needs some mtd loving
Click to expand...
Click to collapse
I do not claim to be a kernel developer. I am trying to understand and build the base kernel. If you can help me get past this, that would be great! I need to take baby steps before I can start walking. Once I get the build to work and boot completely, I'm game to go further, but have to get to a working base before we can continue. I understand the more experienced developers don't want to be bothered. I understand they have other jobs, and families. So do I. They became as great as they are, through hard work, experience and asking the right people the right questions. Asking the right question also applies to Google. The query only returns the matches to your query. Change a few words, get different results.
I'm not looking for someone to hold my hand, I want to learn by doing, not having it done for me. Just point be to the bread crumb trail, and I will follow.
Right now, I am at a stand still until I figure out why it is not loading the tfsr module. If that is even the problem.
If I make any progress, I'll post it here for all. If I am wrong, please correct me so we all don't go down the wrong path.
Thank you for listening.
Tom
hi guys, I bought two Galaxy Ace 3 GT-S7272 for my parents, and since they can't easily use it and not so familiar with smart phones
I decided to cook the rom so that to be able to add our local language into the phone,
I used android kitchen and while Flashing I face STATUS 0 Installation Aborted.
this has two causes, one is using Amend ( which I don't use, because I use Edify which is updater script ), another cause is as mentioned by Daniel '' Your updater-script is using the "MTD" partition type when mounting a partition rather than another type such as EMMC (and thus, you need the device defined under the kitchen's /tools/edify_defs folder) ''
I really really appreciate anyone helping me with this problem as I searched the entire forum and I didn't find any single clue for the soultion.
I tried using update binary from another rom, but that didn't work too,
below the update binary and the updater script,
I will be so thankful to anyone who can help me. thank you so much