Related
Hi there,
I am trying to find MoDaCo's rom with the framework and apps de odexed (that is, not pre odexed for speedup). If someone has it, it will be nice if it can be uploaded on 4shared (please no megaupload or rapidshare). Latest MoDaCo rom is preferable, this is already done for the Nexus one and G1 roms which eases ROM hacking.
Thanks
The latest released version of MCR is available for free over at modaco.com. If you want access to the latest beta (unreleased) versions you'll need to sign up for an account (adfree or premium).
I am not looking for the ROM itself, instead, I am looking for specific files in MoDaCo's ROM. They are the app and framework files but de"odex"ed (that is not pre compiled).
Thanks for your help
Compilation and odexing are 2 separate things.
You have 2 options:
1: PM Paul and ask him nicely, if he can share the files
2: unodex them yourself. It's a matter of minutes, so don't be lazy.
Its not an issue of lazyness, its an issue of Heroless-ness
Anyways, I will try the ask Paul option
i'm in the same boat...dont have a hero but would like a de-dexed version of the stock hero rom
UAE said:
Its not an issue of lazyness, its an issue of Heroless-ness
Anyways, I will try the ask Paul option
Click to expand...
Click to collapse
just for my curiousity: what do you need an unodexed hero rom for if you don't have a hero?
kendong2 said:
just for my curiousity: what do you need an unodexed hero rom for if you don't have a hero?
Click to expand...
Click to collapse
To port the hero sense UI to another device
.odex files are platform specific. From the dexopt documentation:
The output of dexopt is byte-swapped and struct-aligned for the host, and contains indices and offsets that are highly VM-specific (both version-wise and platform-wise)
Click to expand...
Click to collapse
With the de-odexed versions, the apks contain the original classes.dex file which is used to generate platform specific odex files when first booting
bpedman said:
To port the hero sense UI to another device
.odex files are platform specific. From the dexopt documentation:
Click to expand...
Click to collapse
i see. i can help you here, if you give me some starting point. i am a linux sysadmin who has never deodexed anything, so i'll be good if you throw me a script or something...
dsixda's Android Kitchen - Now for Samsung Galaxy S
Compatible with Windows (Cygwin) / Linux / Mac OS X
The following is a guide to assist you with creating your own Samsung Galaxy S 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 version 0.178, you can now create your own Galaxy S ROMs with the kitchen.
I'd like to thank Perka for testing and providing feedback, and also for giving me some ideas through his tutorial in his Ultimate ROM Cooking Guide.
[MAIN PAGE] [RELEASE NOTES] [FAQ - page 1] [FAQ - page 2]
PROCEDURE
This guide may be a bit basic right now but I will update it later if required.
First, you need a rooted Samsung Galaxy S with a ClockworkMod custom recovery. The kitchen supports the GT-I9000, but should also support most of its variants, such as the Captivate, Fascinate, Vibrant and Epic.
Visit the Android Kitchen thread to download the kitchen. Then, follow the link to the FAQ which will show you how to install it on Windows, Linux or Mac OS X. Ensure you read the FAQ carefully.
IMPORTANT (DO NOT IGNORE THIS STEP): To verify your variant of the Galaxy S works in the kitchen, read this post.
Put your base ROM(s) under the original_update folder. For the Samsung Galaxy S, there is support for the following formats which can be placed in that folder (you can place multiple ROMs there):
Stock firmware:
factoryfs.rfs (and optionally: cache.rfs, zImage)
PDA.tar.md5 (and optionally: CSC.tar.md5, PHONE.tar.md5)
PDA.tar (and optionally: CSC.tar, PHONE.tar)
TAR/ZIP file containing factoryfs.rfs (optional: cache.rfs, zImage, modem.bin)
TAR/ZIP file containing PDA.tar and others
TAR/ZIP file containing PDA.tar.md5 and others
Custom ROM:
ZIP file originally created by the kitchen from the stock firmware (NOTE: The kitchen does NOT support custom ROMs created through other methods, due to potential file structure incompatibility issues)
Nandroid backup from ClockworkMod recovery
system.img and boot.img
Here are some basic steps to creating your first ROM after you have your base of files under original_update (more options are available in the kitchen):
Start the kitchen with: ./menu
Create a working folder (by choosing your base ROM)
If you used a factoryfs.rfs but then didn't include the cache.rfs, then you have the option to add a cache.rfs later using the Extract CSC script in the Advanced menu's 'Plugins' section.
Optional: Add a rooted kernel (zImage) to the base of your working folder
You can create a ROM without a zImage and thus keep the existing kernel on your device, although keep in mind that a newer ROM may not work with a kernel meant for older ROMs!
If you use the stock kernel (zImage), you can always replace it later with the CF-Root kernel or any other custom/rooted kernel. Just replace the stock zImage anytime before you build the ROM.
Optional: Add a modem.bin to the base of your working folder, or remove the existing modem.bin if you don't want it. You can flash the ROM with or without a modem.bin.
Root your ROM
Add Busybox
In the Advanced options menu: De-odex your ROM
Build ROM
The ROM is built into a ZIP file meant for flashing from the custom recovery menu. No Odin.
Some notes:
Just select the defaults whenever you are asked about something in the kitchen and are unsure whether to type 'y' or 'n'.
There are lots of questions answered in the FAQ in Posts 3 and 4 of the main Android Kitchen thread. So please go through that first if you have any issues.
For the benefit of other readers, and to prevent confusion, please only discuss Samsung Galaxy S in this thread!
Most of all, have patience, take your time and enjoy!!
thanks for info mate exactly wat im looking for
cheers
Thx for this. Working very well.
Very nice guide
Just what i was looking for great
Sent from my GT-I9000 using xda premium
Thanks works very well! *5 stalls *
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Gvdn said:
So i made my first selfmade rom for samsung s5660 Gio but i am getting errors trying to flash in cwm. First error i managed to solve as in the updater-script there were # missing at the mount and unmount options.
Now im having "assert failed: write_raw_image("/tmp/boot.img","boot")" error. Reading up on XDA i saw u mentioned that it has to do with wrong update-binary and someone solved it by adding "edify_def" but i have no clue what that might be.
Any help would be much apreciated.
Also u mention there are 3 update-binary. Any link to all 3 and can i just try with each one of them first?
Edit: adding the updater-script and update-binary
Click to expand...
Click to collapse
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
dsixda said:
The Gio is not a Galaxy S device. This is where your problem lies. I am not sure how a ROM is constructed for that device.
Click to expand...
Click to collapse
So no matter what i try it wont work with kitchen? Damn too bad i was starting to know my way around it now
Kitchen made the whole rom without a problem tho. Using the boot.img option and following Perka guide. Just seems its not generating the Meta file correct.
Do u have any idea to what i asked earlier? If there is only 3 different update-binaries , can i get all 3 and test em out and 1 will work for sure or it wont work no matter what?
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
dsixda said:
I don't know anything about your device, dude. Just copy one from an existing ROM that someone made for your device. Anyways you're asking about a non-Galaxy S phone so you'll probably find more help in the Chef section of the forum or in your device's subforum.
Click to expand...
Click to collapse
Ok thx alot. Sadly no subforum for Gio
CWM issue
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
krazykipa said:
I'm having a big problem using the kitchen with regards to entering recovery in any custom ROM I make using the kitchen.
Once I flash the ROM everything is fine and dandy in the OS itself, works 100% and all customizations work flawlessly, but once I try to reboot into CWM whether via 3Button or extended power menu/adb, CWM gives a ton of errors saying it cannot mount volumes and basically recovery is useless. The errors are numerous, I'll see if I can post a pic if needed. The important one I'm thinking is "E:/unknown volume for path /sdcard" repeated for /data, /system, /cache, everything.
I tried eliminating sources of error by basically just inserting a JVS rom and pasting in a kernel (Semaphore JVS) without any customizations, and the error still occurs.
Any help?
Click to expand...
Click to collapse
I'm having the same problem here with CF-Root-XX_OXA_JVS-v4.1-CWM3RFS, I tried to move to DarkCore_4.0_JVS and the device get into reboots (just after activating lagfix).
its 2 days now that im working on stock rom and trying only to root and deOdex... help?
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
bhundven said:
Will this work for galaxy s 4g? If not, is there any way I can help to add support for it?
Click to expand...
Click to collapse
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
dsixda said:
Sorry for the late reply. Check your build.prop's ro.product.device value. If the name doesn't exist under the kitchen's tools/samsung_files/sgs_variants folder then just create a file there with same name.
Unfortunately I don't have the Galaxy S so I cannot test on my own.
Click to expand...
Click to collapse
Looks like the SGH-T959V file exists. Thanks for helping me figure that out!
I am having an issue with wi-fi not be able to connect after i have flashed my build.. and thats about it. I'm not sure whats causing it any ideas?
EDIT:
Was the updater-script, i swapped it out with another and all is well.
There are problem with kernels. I can't change?
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
xtrem88 said:
is this supported by the sidekick since it has similiar specs to the samsung vibrant?
Click to expand...
Click to collapse
If it's basically the same device then it should support it. Just make sure you have an entry in the kitchen for the ro.product.device value. See the note in the 2nd step in Post #1.
Hey guys,
Alroger has included a patched framework into one of his builds, offering support for PDroid. Based on their work, the modified JAR files seem to do the work nicely. Therefore, you can find the patched and unpatched versions of the files in CWM flashable format attached to this post.
Please report back if it works for you, as it will be valuable feedback to the team porting PDroid to ICS.
For more info on PDroid, go here:http://forum.xda-developers.com/showthread.php?t=1357056
For more info on the port of PDroid to ICS, go here: http://forum.xda-developers.com/showthread.php?t=1554960
Notes & Observations
- Only compatible with official CM9 (Android 4.0.3 and 4.0.4).
- Only compatible with Recovery 3.0.x or later (should not be a problem with recent/modern ROMs/builds).
- This build is only compatible with SGT7 device variants and the CM9 builds released for these devices.
However, if you indeed get into trouble, try clearing cache, dalvik cache and flashing your original ROM on top of this package. No data wipe should be required!
Download & Install:
Download OP post attachment of your choice (based on CM9 0421 nightly)
Flash P1-PDroid-CM9-0421-CWM.ON.v2.zip to apply patch
Flash P1-PDroid-CM9-0421-CWM.OFF.v2.zip to remove patch
Save zips onto your Tab
Reboot in Recovery mode
Install zip from SD Card
Reboot tab & wait for Android to upgrade
Install PDroid app from market (market link)
Enjoy
Disclaimer
I will not offer support to anyone in case these ZIPs cause any harm or damage in any way. You are responsible of your own actions including flashing anything to your device!
Thanks and Credits
Thanks, in no particular order to these guys:
svyat for the initial work
pastime1971 for the ICS port
alroger for building the patched framework files compatible with CM9 and giving me his blessing to pack the patched framework files
Let me know of any issues or success stories in the thread.
Peace,
C.
I don't need to flash this patch as I already use alroger's build of CM9 ROM with PDroid (2012-04-24), but I just wanted to say thank you, as this is excellent news for next time when I don't use a ROM that already includes PDroid patches!
http://cafe-ti.blog.br/1524~sgt7-p1000-android-ics-cm9-mtd.html
Is this device specific?
It runs on all SGT7 variants running official CM9 build.
It won't work for other ROMs or other devices than SGT7.
PS: if it runs on something else, it is only by chance!
Peace,
C.
Ok...thanks anyway.
From the OP it read like it was good for any cm9.
Hope nobody flashes it on the wrong device.
Luckily I was smart enough to ask first.
I thought it is common sense since this is SGT7 forum?
Sent from my GT-P1000 using XDA
priyana said:
I thought it is common sense since this is SGT7 forum?
Sent from my GT-P1000 using XDA
Click to expand...
Click to collapse
Just followed a link that he posted from a different thread....
And the xda app doesn't say what device thread you're in if you follow a link.
will this work on a sph-p100 running update-cm-9-20120425-NIGHTLY-p1c-signed
LivnDream said:
will this work on a sph-p100 running update-cm-9-20120425-NIGHTLY-p1c-signed
Click to expand...
Click to collapse
Yes, @cheatman's post is exactly for the official cm9 nightly p1 and p1c (Galaxy Tab 7 GSM and CDMA).
And he offers the removal of the patch also, in case you have any problems.
thanks will give it a go
Hi Cheatman,
Will this work on AOKP ICS?
Or will it need a different one? Can you build one?
Thanks!!
First thing: updated OP post to avoid confusion.
Secondly @priyana: It will probably break AOKP builds as the framework is heavily modified compared to CM9. You could try to flash it and report back, but be ready to flash AOKP again on top of it if it bugs out.
If you have issues, you will not need to restock or wipe data. You can just flash AOKP again on top of it and it should return to normal after a reboot.
Peace,
C.
Thanks Cheatman.
Just to feed back here.
I just tried applying it on my aokp build #31 but can't boot into the OS.
Flashed the from again on top of it and I am back to aokp like you said.
Sent from my GT-P1000 using XDA
Same for me with AOKP. After installing the ON package it boots up to the part of updating, the next start it doesn't boot up anymore and is stuck on the bootlogo and makes a short vibration in repeated intervalls.
Installed the OFF package, updated on first boot, doesn't work anymore on next boot just like the ON package.
Too bad for me as I'm going to use the train now and could've used the tab.
Thanks anyway and I'm still interested in this and would hope to see a fix.
You can still use the tab by flashing aokp again.
All data intact in my case.
Sent from my GT-P1000 using XDA
I know that and did that already because OP wrote that in the first post:
"However, if you indeed get into trouble, try clearing cache, dalvik cache and flashing your original ROM on top of this package."
Works as usual but no pdroid.
OK.
Read you wrongly because you said too bad, you "could have used the tab"
I thought you meant now it is unusable/broken, hence the reminder.
Sent from my GT-P1000 using XDA
This is mostly for new devs that want a stock build to work with, or just want to use the latest files & firmware version with their unlocked & rooted device.
All of the stock files are in this rom. The only changes made are busybox, SuperSU (Faster responses than traditional SU in my humble opinion), & I tore a lot of the apks down to java & applied diffpatches from the OTA update to all applicable apk & jar files, De-Odexed 100% & zip aligned. This currently includes the stock rooted kernel & will also work with the kernel by NunHugger (which supports init.d & custom boot images). You can easily change kernels with WinRAR or WinZip by making certain that "no compression" is selected & then drag & drop new boot.img to the root of the zip.
Also in the rom are the newer camera binaries & the other fixes from the AT&T LG1 OTA.
I did change the GoogleQuickSearchBox.apk so that on-device searches are still possible.
Rom include latest SuperSU & a working busybox 1.20.2 build.
Other than that, this is a fully bloated & stock AT&T rom & contains the stock rooted kernel. If you would like init.d support or anything else added, just let me know. I don't believe in init.d, & personally believe in editing xml's or boot init files to accomplish init tasks, but I'll add if desired. I am working on modding the LG1 kernel to have UV/OC function, but other than that, not much else.
This will
I am working on applying the diff patch to the kernel source, so that the kernel will match the LG1 system. However, I am having trouble with occasional bootloops when battery is under 30%. Could be the source, but most likely it is the fact that I haven't played with 100% stock source much, let alone Samsung source.
At any rate, do what you will with this. It is there to do with as you like, or not...
MD5: 1474aaffe7c178f939498da3a87469e3
Link: https://docs.google.com/open?id=0Bxxb003sdLoJZS1kUDJYcnVaXzg
*I will add a second link with updated apk's so that no google play updating is needed.
UPDATE: New version with most of the frequently updated apps located in Data/App to avoid duplicates & allow users to uninstall.
MD5: af4381d027abaec2e96828aa2799037f
Link: https://docs.google.com/open?id=0Bxxb003sdLoJNkFhSFB4M0N5ZUk
***Devs - Anyone familiar with Sammy source & willing to provide any assistance in patching the ALEM Kernel source to ALG1, it would be appreciated!
_just in case....
Am I missin something or where is the link to download - I like having a back up of the latest Stock "just in case' -
Oh - I see this is a fairly recent post - is the "upload" still processing?
Waiting for this as well.
Sent from my SGH-I747M using xda premium
I should lock this is but ill give you the benefit of doubt.
Mr.Highway said:
I should lock this is but ill give you the benefit of doubt.
Click to expand...
Click to collapse
What, a 9 hour upload time is excessive?
RampageRR said:
What, a 9 hour upload time is excessive?
Click to expand...
Click to collapse
Yes
GSLEON3 said:
This is mostly for new devs that want a stock build to work with, or just want to use the latest files & firmware version with their unlocked & rooted device.
All of the stock files are in this rom. The only changes made are busybox, SuperSU (Faster responses than traditional SU in my humble opinion), & I tore a lot of the apks down to java & applied diffpatches from the OTA update to all applicable apk & jar files, De-Odexed 100% & zip aligned.
Also in the rom are the newer camera binaries & the other fixes from the AT&T LG1 OTA.
I did change the GoogleQuickSearchBox.apk so that on-device searches are still possible.
Other than that, this is a fully bloated & stock AT&T rom.
I am working on applying the diff patch to the kernel source, so that the kernel will match the LG1 system. However, I am having trouble with occasional bootloops when battery is under 30%. Could be the source, but most likely it is the fact that I haven't played with 100% stock source much, let alone Samsung source.
At any rate, do what you will with this. It is there to do with as you like, or not...
***Devs - Anyone familiar with Sammy source & willing to provide any assistance in patching the ALEM Kernel source to ALG1, it would be appreciated!
Click to expand...
Click to collapse
Were is the link ??
So
what happened? Waiting...
LOL...Damn T1 line went down, traffic was bad & forgot when I got home. :silly:
1st in after the link lol. Thank you for your contribution look forward to trying it out!
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
So can you flash a different kernel like ktoonez just using cwm?
Yessiree.
Any kernel in the AT&T section I have tried so far has worked fine.
And if anyone wants, I can remove the debugging crap from all of the jars & apks to trim the files down further.
So the modem didnt change? Mine is still the same just curious
Edit: my bad forgot its just ota and just patches on the side note why no just make flashable zip of the removed apk if ever you debloat the rom
Sent from my SAMSUNG-SGH-I747 using xda premium
remove the debugging crap!
GSLEON3 said:
And if anyone wants, I can remove the debugging crap from all of the jars & apks to trim the files down further.
Click to expand...
Click to collapse
Actually - yes, please do and share! We're all after efficiency and optimized stock experience.
Curious as to why you didn't debloat this?
tomween1 said:
Curious as to why you didn't debloat this?
Click to expand...
Click to collapse
It is really meant to be a base for other's that wish to begin learning to cook. That way there is a base rom that is 100% stock for them to add to or deduct from as they choose. However, if you wish, I can do a de-bloated version. I have a new version as well, that still has bloat, but most of the frequently updated apps are in data/app & named so they are properly handled by updates.
Is there any consensus as to what is "Debloated" besides removing the AT&T crude? I usually remove gmail, I don't need two email clients, Flipboard, is gone, awww heck, I'll just do whatever & if ya'all want something back I'm sure I'll hear it.
GSLEON3 said:
It is really meant to be a base for other's that wish to begin learning to cook. That way there is a base rom that is 100% stock for them to add to or deduct from as they choose.
Click to expand...
Click to collapse
Just like the one I released. Only this is based on patches from the newer OTA.
Sent from my SAMSUNG-SGH-I747 using xda premium
GSLEON3 said:
Is there any consensus as to what is "Debloated" besides removing the AT&T crude? I usually remove gmail, I don't need two email clients, Flipboard, is gone, awww heck, I'll just do whatever & if ya'all want something back I'm sure I'll hear it.
Click to expand...
Click to collapse
Well if you do a de-bloated version, anybody that wants the app's you've pulled can pull them from your first one and install what they want. Also thank you
I have been in love with all things Android for years but there is a certain level of proficiency that I don't think I'll ever reach. I'm reaching out to anyone who can provide me with some assistance in this issue. I have a Nexus (my wife's) that constantly crashes the Talk and Camera apps. I've tried dozens of solutions posted online but I think the only one that actually addresses my issue is provided in the link below. Unfortunately, when it comes to compiling Android source code I get in over my head.
Could someone please give me instructions on how to implement this fix? I would like to run AOKP JB Milestone 1. It appears I need to swap out the binaries before compiling and flashing this ROM but that's about as much as I can tell.
Please help!
Link describing the fix -------------> http://anders.com/cms/435
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
mwalt2 said:
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
See, this is where I'm confused. I'm not compiling the ROMs or any of the gapps myself. I'm flashing a copy of AOKP that I used on other nexus devices and had zero issues. For some reason this phone won't work quite right. I've wiped, clear data, fixed permissions, blah blah blah.
From hefty googling I have found a decent number of other threads with my exact problem but none of the threads actually have a solution.
mwalt2 said:
Is there a reason you don't just flash the aokp rom that is already compiled? You do need to get some of the closed source proprietary files if you are compiling yourself (though I would have thought that aokp would already have everything set up in a vendor folder for your device). Talk is not part of aosp and you should be able to get it working by flashing a gapps package. It sounds like you are missing the talk libs (.so file) that goes in /system/lib. Look for libgtalk_initial.so and libgalk_stabilize.so. For the camera, make sure you have the ducati-m3.bin in /system/vendor/firmware. You can get these files from the factory images provided by Google or download a stock rom.
If you are compiling source yourself, the easiest way to see if anything is missing is to extract the factory image or a stock rom and use a program like beyondcompare to see the differences between your rom and one from Google.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
ANY AOSP rom should have these binary files.
http://forum.xda-developers.com/showthread.php?t=1386615
So in other words, it doesn't sound like this will solve my problems then, huh?
cartisdm said:
So in other words, it doesn't sound like this will solve my problems then, huh?
Click to expand...
Click to collapse
Check logcat/dmesg right after you reproduce the issue. (ref: http://forum.xda-developers.com/showthread.php?t=1812959)
We need more insight/details as to why it is failing.
Your wife's phone currently runs:
carrier: ______
rom: _____
rom build number: _____
kernel: _____
bootloader: ______
radio: ______
Have you tried starting fresh, flashing nexus factory image through fastboot, as per (ref: http://forum.xda-developers.com/showthread.php?t=1626895) ?