Now that we have a working 2nd init its time to get an aosp rom booting. Logically the first choice is CM7. We have a repo setup but first I need a small favor. I need the ramdisk (boot.img) ripped from the photon and the xoom. The atrix's wont work at all for us due to the fact it is gsm only.
Ignore my post
motcher41 said:
http://www.multiupload.com/XOYSGFYVHQ
Poton System Dump if it helps....from http://forum.xda-developers.com/showthread.php?t=1197219&highlight=boot.img
Xoom System pull http://www.gamefront.com/files/20919234/systempull.7z
Let me know if this helps or not
Click to expand...
Click to collapse
Eh, not quite what im looking for. Im looking for what we had at the beginning of the 2nd init thread. the ramdisk has things like the mapphone files and the init.
Ignore this post
Essentially you need to decompile the boot.img from a CM7 rom for both devices.
Ignore this post
Ace: Not sure quite what you want. This is the boot.img pulled from Photon CM7 Sunfire Kang dated Nov 20th. http://www.multiupload.com/1U12Z8LV76
And here is the boot.img (stock I guess) for the wifi xoom: http://www.mediafire.com/?lrdnz93ldsn5oc9
I'll keep looking.
Your on the right path, just de compile that boot.img and you have what I need for the photon. Do the same with the xoom.
How do I decompile? I should know this, but sadly.. I've never actually decompiled these things before. I tried mounting them via CloneDrive and that didn't work.
Theres guides on how to do it, search for de compile boot.img or decomile android ramdisk youll find guide. I dont do it myself because of how locked down my work laptop is (until I get my thinkpad's motherboard replaced I only have this) BTW if anyone was curious im in a dispute with the seller of the mobo I bought atm.
Unfortunately I can't find any guides for Windows on decompiling Android boot.img files. All the ones I find are for Linux.
Send me the link of the.img and I'll try to do it on mine.
Went be till tonight tho
Tapin' the Talk on the xSquared
Peperm1nt said:
Send me the link of the.img and I'll try to do it on mine.
Went be till tonight tho
Click to expand...
Click to collapse
0vermind said:
This is the boot.img pulled from Photon CM7 Sunfire Kang dated Nov 20th. http://www.multiupload.com/1U12Z8LV76
And here is the boot.img for the wifi xoom: http://www.mediafire.com/?lrdnz93ldsn5oc9
Click to expand...
Click to collapse
He wants both the Photon and Xoom boot.img files decompiled.
Never decompiled boot.img before but I gave it a shot.
http://dl.dropbox.com/u/23458785/xoom-boot.img-ramdisk.gz
http://dl.dropbox.com/u/23458785/photon-boot.img-ramdisk.gz
Hope this helps.
For decompiling I used this perl script:
https://gist.github.com/1087743
Just feed it the filename for boot.img and that's it.
PS - Ace I'm not sure if you know or not, but there is NO CM7 for the Xoom.
mazz0310 said:
PS - Ace I'm not sure if you know or not, but there is NO CM7 for the Xoom.
Click to expand...
Click to collapse
I didnt know that actually. Any aosp roms for it then? We just need something that isnt blur.
aceoyame said:
I didnt know that actually. Any aosp roms for it then? We just need something that isnt blur.
Click to expand...
Click to collapse
nope theres an ics sandwich rom in the works thats aosp but the honeycomb source just dropped when the ICS came out
Well is it running AOSP honeycomb or was it with blur? AOSP honeycomb would be good enough even. All we need is the boot.img from it
aceoyame said:
Well is it running AOSP honeycomb or was it with blur? AOSP honeycomb would be good enough even. All we need is the boot.img from it
Click to expand...
Click to collapse
Xoom is a google experience device came with a stock build of honeycomb no blur
Edit: I can get you the boot.img for the latest stock version of honeycomb from the 3G/4G Xoom
Sandso9 said:
Xoom is a google experience device came with a stock build of honeycomb no blur
Click to expand...
Click to collapse
And the source for honeycomb was never released so therefore, no CM8.
Related
mySlide-1.0.2
YOU PROBABLY DON'T WANT THIS...DON'T WASTE YOUR TIME!!!!!
This is just what I want, not necessarily what you want http://www.mediafire.com/?tstgikwhfezj6ph
This Rom will mostly be unsupported and unmaintained.
Flash at your OWN RISK.
What it is:
Stock slide rom.
added busybox
added netcat (busybox nc isn't good enough for me)
added bash
added htop
removed link toolbox->df (prefer the one in busybox)
removed link toolbox->rm (prefer the one in busybox)
changed the default animated boot ADVERTISEMENT and jingle
pngcrushed and zipaligned apks (with the execption of one) to save some space
Kangs:
what isn't.
maybe a few more little changes I forgot.
changes:
from 1.0.0 to 1.0.1:
added a2sd (from eugene373's smr5r1. breaks boot animation)
added default themes back.
from 1.0.1 to 1.0.2
added e2fsck
mySlide-1.0.0-signed
mySlide-1.0.1-signed
mySlide-1.0.2-signed
Themes in this are broken (1.0.0 only). If you want the default themes back then flash this...
themes-signed.zip
hey dumfuq glad to see you over on the slide section now. can we expect some overclocked kernals from you like on the g1?
jriv said:
hey dumfuq glad to see you over on the slide section now. can we expect some overclocked kernals from you like on the g1?
Click to expand...
Click to collapse
I sure hope so, but only time will tell.
That would be sick wonder how high this processer can go?
Sent from my T-Mobile myTouch 3G Slide using XDA App
Is the IM app erased in this and the tmobile app pack? i hate those apps
Nevermind i used ur rom and erased the files and signed it again. Thanks for the rom
dumfuq said:
YOU PROBABLY DON'T WANT THIS...DON'T WASTE YOUR TIME!!!!!
Click to expand...
Click to collapse
Not sure why you say that (in those words), but this does look decent!
Also, noob question, but are the stock ROMs (apps included) not zipaligned by default?
Yup they were already zipaligned. At least the ones I just checked
Honesty I didn't even look first. The crush actually takes off about 10Mb though.
yo dumfuq quick question... what exactly is required in editing a kernel to allow for overclocking and undervolting?
kingofyo1 said:
yo dumfuq quick question... what exactly is required in editing a kernel to allow for overclocking and undervolting?
Click to expand...
Click to collapse
Not exactly sure if this is what your asking but basically...
You need the kernel source code to edit (the legend kernel source has the espresso board files),
A handy dandy text editor (like vim),
a cross-compiler (There is one under prebuilt/linux-x86/toolchain in an AOSP or cyanogenmod build environment),
and a linux environment (cygwin might work not really sure).
1. download source
2. unpack source
3. edit source
4. set environmental variables
4. compile source
5. make a boot.img or an update.zip
Obviously that's incredibly simplified, but hopefully you get the idea.
Ok quick question to the maker of this rom... How can i add the themes back to this rom? I want to put the themes back but i dont kno which folder to put them in. Also which folder is where i can change the boot animation you have installed to stock? Thanks
this actually seems like exactly what i want. My only question is does it support a2sd. if so.. i have a new rom
btate0121 said:
this actually seems like exactly what i want. My only question is does it support a2sd. if so.. i have a new rom
Click to expand...
Click to collapse
good question. a2sd is a plus
you don't put them in anywhere. you can download and install them. there's a thread already with a small pack of themes to download and install. You install like any other APK. Search this forum section for them.
NiN39Z said:
Ok quick question to the maker of this rom... How can i add the themes back to this rom? I want to put the themes back but i dont kno which folder to put them in. Also which folder is where i can change the boot animation you have installed to stock? Thanks
Click to expand...
Click to collapse
The PNG crush killed the stock themes. If you want them back you can either boot to recovery and push the original ones to /system/app/ or just flash this...themes-signed.zip. That is just an update.zip that will copy the original themes back to your phone.
btate0121 said:
this actually seems like exactly what i want. My only question is does it support a2sd. if so.. i have a new rom
Click to expand...
Click to collapse
Nope, no a2sd.
any plans to add a2sd? I mean seriously... this would be PERFECT for my needs if it only had a2sd. I'm happy with a stock rom... i just want a2sd.
btate0121 said:
any plans to add a2sd? I mean seriously... this would be PERFECT for my needs if it only had a2sd. I'm happy with a stock rom... i just want a2sd.
Click to expand...
Click to collapse
Nope. Currently I don't use a2sd, or this rom really. I made this just for an optimized stock rom to bounce back to when needed. Currently I'm running a customized version of eugene's cm6 as my daily driver.
in your experience.. how hard would it be for a novice to add a2dp to this? I did a quick google and found about 3 good pages of data.. but it seems pretty complicated (packing and repacking boot.img looks to be pretty intense on a windows machine without any experience from what i can tell). Do you think i should attempt this? LOL.
dumfuq said:
Nope. Currently I don't use a2sd, or this rom really. I made this just for an optimized stock rom to bounce back to when needed. Currently I'm running a customized version of eugene's cm6 as my daily driver.
Click to expand...
Click to collapse
what is the difference between your customized version and the regular?
btate0121 said:
in your experience.. how hard would it be for a novice to add a2dp to this? I did a quick google and found about 3 good pages of data.. but it seems pretty complicated (packing and repacking boot.img looks to be pretty intense on a windows machine without any experience from what i can tell). Do you think i should attempt this? LOL.
Click to expand...
Click to collapse
what were the links they seem like the ones i have been looking for lol! i can already unpack and repack a boot.img im just looking for the steps i need to add to get aps2sd to work! i had a link explaining it but i cant find it anymore or google it!
DO NOT flash this to US EVO 3D, for DEVS only !!!![/size]
This is a stock rooted EU Shooter 1.20.401.2 ROM (odexed) to use as a base for the DEVs so it can be ported. This was extracted directly from the RUU.
The only MODS made to this were that it has been ROOTED and ZIPALIGNED.
I would port it but I don't know how.
DOWNLOAD LINKS
http://www.multiupload.com/P6KDFDYD5K
t3project said:
UPLOADING NOW !!!
DO NOT flash this to US EVO 3D, for DEVS only !!!!
This is a stock rooted EU Shooter 1.20.401.2 ROM (odexed) to use as a base for the DEVs so it can be ported. This was extracted directly from the RUU.
The only MODS made to this were that it has been ROOTED and ZIPALIGNED.
I would port it but I don't know how.
DOWNLOAD LINKS
Uploading Now - 1:02 left
Click to expand...
Click to collapse
Thanks man just what i wanted based on official release right?
t3project said:
UPLOADING NOW !!!
DO NOT flash this to US EVO 3D, for DEVS only !!!!
This is a stock rooted EU Shooter 1.20.401.2 ROM (odexed) to use as a base for the DEVs so it can be ported. This was extracted directly from the RUU.
The only MODS made to this were that it has been ROOTED and ZIPALIGNED.
I would port it but I don't know how.
DOWNLOAD LINKS
Uploading Now - 1:02 left
Click to expand...
Click to collapse
I'll be trying to port this for sure
Sent from my PG86100 using Tapatalk
JoelZ9614 said:
Thanks man just what i wanted based on official release right?
Click to expand...
Click to collapse
yea, i pulled i straight out of the EU_Shooter_1.20.401.2 RUU, rooted, zipaligned and then repackaged it.
t3project said:
yea, i pulled i straight out of the EU_Shooter_1.20.401.2 RUU, rooted, zipaligned and then repackaged it.
Click to expand...
Click to collapse
alright thanks ill have it ported right away
links are up
downloading
I am hoping I don't come off like an ass when I say this... So I apologize in advance...
You post a ZIP file of a ROM from Euro device for "Devs" that want to port it? Any Dev would use the original (which is assuming where you got this) from here: http://forum.xda-developers.com/showthread.php?t=1176174. A real Dev would not need this for porting. They would use the original. Just saying...
Also, for anyone interested, I did a side by side comparison of this Euro ROM and the US ROM back on July 21st: http://forum.xda-developers.com/showpost.php?p=15847420&postcount=17. It details the specific /system changes besides the OS change.
I think your effort is commendable but maybe a duplication in work... Either way thanks for adding to the community!
scrosler said:
I am hoping I don't come off like an ass when I say this... So I apologize in advance...
You post a ZIP file of a ROM from Euro device for "Devs" that want to port it? Any Dev would use the original (which is assuming where you got this) from here: http://forum.xda-developers.com/showthread.php?t=1176174. A real Dev would not need this for porting. They would use the original. Just saying...
Also, for anyone interested, I did a side by side comparison of this Euro ROM and the US ROM back on July 21st: http://forum.xda-developers.com/showpost.php?p=15847420&postcount=17. It details the specific /system changes besides the OS change.
I think your effort is commendable but maybe a duplication in work... Either way thanks for adding to the community!
Click to expand...
Click to collapse
umm yea, you're sounding like an ass. sure they are perfectly capable of doing that and YAY for them if they do. just trying to save someone a few steps because i had nothing else to do. it's much more convenient to work with a zip then to have to pull it all from the RUU.
anyone more knowledgeable than I attempt to port this yet?
JoelZ and I have been working on it but the display will not work properly. Apparently it's not as straight forward as we thought.
I got it to boot with sound and everything the screen went out and I'm currently trying to fix a radio issue now. I really hope there isn't a RUU in my future. LMAO
same here. there are some lib issues somewhere
Below are links to a ICL23D Ice Cream Sandwich development build for the Galaxy Nexus!
Originally posted at:
http://android.modaco.com/topic/348194-04-nov-icl23d-galaxy-nexus-boot-recovery-system-dump/
Some points to note about the files...
All 3 files are completely stock and unedited
This build is a dev build, not a release build
This build is from a test Galaxy Nexus
This build is not odexed!
I know a lot of people are hacking up ports for other devices, so hopefully the non-odexed nature of this release together with the fact it includes the boot and recovery images will help make that happen.
All I ask is that you don't mirror the files elsewhere, that you link back to this topic rather than deeplinking the files and that if you use them you credit the source. So here they are...
Galaxy Nexus ICL23D boot image - http://www.filesonic.com/file/2985317613 - MD5: 8ad48c176eb12b33e436f38a8d9711f8
Galaxy Nexus ICL23D recovery image - http://www.filesonic.se/file/2985400373 - MD5: c02fe19e8b0d162e225597aab26704cb
Galaxy Nexus ICL23D system image (tar.gz) - http://www.filesonic.se/file/2985366173 - MD5: 7a47451ace5689b0fefbec64a7b911a0
(NOTE I WILL NOT CREATE ANY MULTIUPLOAD MIRROR OF THIS FILE!)
DUE TO I WANT YOU TO SUPPORT THIS GUY!
Enjoy!
Damn, was literally coming here to post this, DAMN...
but how hard would it be to port it over to our phone?
Jameslepable said:
Damn, was literally coming here to post this, DAMN...
but how hard would it be to port it over to our phone?
Click to expand...
Click to collapse
you can give it a try
It's same situation with SDK,armv7-built libs. Need to wait for sources
ciaox said:
It's same situation with SDK,armv7-built libs. Need to wait for sources
Click to expand...
Click to collapse
this was meant to have here as people are "collector's" and expect stuffs like this, look at zte blade they may have this also
SWEATTAIMI said:
you can give it a try
Click to expand...
Click to collapse
Tbh i wouldn't even know where to start.
Sent from my LG-P500 using Tapatalk
Jameslepable said:
Tbh i wouldn't even know where to start.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
to start is to make it to boot, using the changes in init.rc (however this is not nessesary as our boot.img already seems to have these, but needs to be edited a bit if i aint wrong,
then create boot.img
go for libs, try edit em to make it work for our armv6, boot and it should be starting
however editing libs takes good time,
i still wonder how Honeycomb were ported and not ics
SWEATTAIMI said:
to start is to make it to boot, using the changes in init.rc (however this is not nessesary as our boot.img already seems to have these, but needs to be edited a bit if i aint wrong,
then create boot.img
go for libs, try edit em to make it work for our armv6, boot and it should be starting
however editing libs takes good time,
i still wonder how Honeycomb were ported and not ics
Click to expand...
Click to collapse
Could ask they guy (forget his name) that got honeycomb running and see how its done? That would be a good start.
Sent from my LG-P500 using Tapatalk
I dont get the reason by posting a new thread?? Devs are not doing anything, so why bother to post? Even though, ciaox is planning it but he said "wait for the source"...
Sent from my Nexus One using Tapatalk
Jameslepable said:
Could ask they guy (forget his name) that got honeycomb running and see how its done? That would be a good start.
Sent from my LG-P500 using Tapatalk
Click to expand...
Click to collapse
ah you mean だ(da)っ(SS)ち(chi)ん (Dastin) but that's not exactly in hiragana
so litterarly i wrote dasschin (trust me i know i read japanese)
anyhow he maybe want this (Y)
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Silentbtdeadly said:
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Click to expand...
Click to collapse
They steal the code from CM source. Then they wrap it up in a closed source OS. So you won't find any source for it.
zelendel said:
They steal the code from CM source. Then they wrap it up in a closed source OS. So you won't find any source for it.
Click to expand...
Click to collapse
I figured it might be something like that, would explain why I haven't found anything really helpful.. but then the question becomes how do people port it to other devices? I'm personally a fan of the functionality it has over CM, and it would give the users of my device something to play with(and me something to learn/experiment with) while we wait for ICS to get built. Hell, if I can find some good resources, maybe I could contribute to the ICS build before it is done..
But while the resources I've been finding here are good, I learn best by tinkering, just figuring things out, so the resources between what is offered here and the finished product would do me the most good.
Silentbtdeadly said:
I haven't been able to find a good answer on miui.us nor have I gotten a reply from any of the devs who have successfully ported to an unsupported device. I have searched for answers as much as possible, and I haven't been able to find out where miui devs get started. Are they compiling from source(I haven't found any source)? I plan on asking the same question there, but I have always gotten the best answers from the XDA community..
I'm waiting for my amaze 4g to come in the mail, the device doesn't have many devs, and while the main dev is working on ICS I figured I'd try to get into development(that is why I finally bought a new device) to see if I can offer the community something while we wait for ICS to get done/stable. If anyone can point me in the direction of where these devs go to get started, I would greatly appreciate it!
Click to expand...
Click to collapse
So what we (miui porters) do is take the kernel from cm7 and some lib files from cm7 and add to an existing miui rom until it boots. It helps if you use a similar device as the base (I use the nexus s 4g as a base for my epic 4g ports b/c epic is pretty much a keyboarded version of the nexus s 4g).
Sent from my SPH-D700 using Tapatalk
xboxfanj said:
So what we (miui porters) do is take the kernel from cm7 and some lib files from cm7 and add to an existing miui rom until it boots. It helps if you use a similar device as the base (I use the nexus s 4g as a base for my epic 4g ports b/c epic is pretty much a keyboarded version of the nexus s 4g).
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Where do you guys get the weekly build of miui from, I know it is updated every friday, but I haven't seen where they are getting it from..
The phone I want to develop for is the Amaze 4g, the Sensation is pretty much the same with just a underclocked cpu. The amaze is new enough that everything I've found says they are working on a cm9 build and skipping cm7 all together, so the best I can think of is grabbing some files from the sensation cm7(like you do the nexus) and stock files from the official gingerbread releases for the amaze.
The question is what files can I use from the sensation, will the files from stock ginger work, and which files need to be ported at all. The best I've found is this http://www.madteam.co/forum/support-65/how-to-port-miui/ which I've read the feedback on, and results seem to vary quite a bit.
Silentbtdeadly said:
Where do you guys get the weekly build of miui from, I know it is updated every friday, but I haven't seen where they are getting it from..
The phone I want to develop for is the Amaze 4g, the Sensation is pretty much the same with just a underclocked cpu. The amaze is new enough that everything I've found says they are working on a cm9 build and skipping cm7 all together, so the best I can think of is grabbing some files from the sensation cm7(like you do the nexus) and stock files from the official gingerbread releases for the amaze.
The question is what files can I use from the sensation, will the files from stock ginger work, and which files need to be ported at all. The best I've found is this http://www.madteam.co/forum/support-65/how-to-port-miui/ which I've read the feedback on, and results seem to vary quite a bit.
Click to expand...
Click to collapse
Since your devices are so close, try just copying system/lib/egl and system/lib/hw from stock to Sensation MIUI and also IDK if Amaze and Sensation kernels are compatible, but I'll assume not because that could lead to a brick. So copy boot.img from stock to MIUI. Then Logcat and see what the errors are and replace whatever files error (If it says libcamera failed, replace it with one from stock). It may never boot from a stockbased kernel, it does on some devices and not on others. You may also be able to unpack the boot.img from stock and Sensation MIUI and copy the Sensations intramfs/ramdisk from Sensations folder to Amaze's. Then repack the Amaze folder, which has the Sensation's intramfs in it and then try.
xboxfanj said:
Since your devices are so close, try just copying system/lib/egl and system/lib/hw from stock to Sensation MIUI and also IDK if Amaze and Sensation kernels are compatible, but I'll assume not because that could lead to a brick. So copy boot.img from stock to MIUI. Then Logcat and see what the errors are and replace whatever files error (If it says libcamera failed, replace it with one from stock). It may never boot from a stockbased kernel, it does on some devices and not on others. You may also be able to unpack the boot.img from stock and Sensation MIUI and copy the Sensations intramfs/ramdisk from Sensations folder to Amaze's. Then repack the Amaze folder, which has the Sensation's intramfs in it and then try.
Click to expand...
Click to collapse
Awesome, a place to start. My buy for the Amaze got screwed up, so I'm going to likely get one from tmobile.. but I've already put together a rom to spec that you have described, and I have a few kernels to try too. I hope that checking the logcat and making some tweaks based on the output I get a working rom, the next questions would be what a script looks like(on a pc or mac) I could just apply to pull the files from the different sources to apply to weekly released-- I am pretty sure that is what successful ports do.. and what I could do to be more of a developer rather than just porting or kang'ing. I just figured this would be a good way to get some working experience in the meantime.. but I am guessing that once a good build of an OS is out there, people aren't compiling from source. Seems like many are just learning aspects of the OS and tweaking stock roms with things they have found..
Thanks again for the advice, as soon as I have the phone to test it with, I am gonna give this a try
Silentbtdeadly said:
Awesome, a place to start. My buy for the Amaze got screwed up, so I'm going to likely get one from tmobile.. but I've already put together a rom to spec that you have described, and I have a few kernels to try too. I hope that checking the logcat and making some tweaks based on the output I get a working rom, the next questions would be what a script looks like(on a pc or mac) I could just apply to pull the files from the different sources to apply to weekly released-- I am pretty sure that is what successful ports do.. and what I could do to be more of a developer rather than just porting or kang'ing. I just figured this would be a good way to get some working experience in the meantime.. but I am guessing that once a good build of an OS is out there, people aren't compiling from source. Seems like many are just learning aspects of the OS and tweaking stock roms with things they have found..
Thanks again for the advice, as soon as I have the phone to test it with, I am gonna give this a try
Click to expand...
Click to collapse
Actually, one more suggestion on the kernel. Using dsixdas kitchen, extract the boot.Img from amaze stock and sensation miui and go to boot.img-ramdisk folder and go to init.RC on both devices using notepad++ and find the line that says bootclasspath and copy it from miui to amaze stock. Then recompile using dsixdas kitchen and then test
Sent from my GT-P7510 using Tapatalk
hey guys this is a cwm recovery flashable zip of my bootleg buildprop for the Photon
i have one version for blur based/stock roms and a version for cm7 please make sure and use the correct file cause the blur version on cm7 causes havoc. If on cm7 use the cm7 version if on stock based use blur version.
cm9, electrify, and miui not supported yet
has:
overmind's speedyv7
rocko's rom tweaks
balltounge's mashup
motcher's flow control changes
nok0763, Notorious544d for the raindrop fix and moonzbabysh for showing us the way
seanzscreams multitouch mod
zep's v6 and 3g
and several adjustments made by yours truly
instructions:
before going into recovery make sure wifi is turned off and you have either a fresh nandroid or have renamed your buildprop to buildprop.bak
reboot into recovery
wipe cache and dalvivk cache
flash bootleg zip
reboot phone
let phone boot completely then reboot phone
let it reboot and everything should be super slick
first boot should take a relatively long time, but the second boot should be roughly half the time you are used to seeing
enjoy and as always with anything make a back up
using a file explorer navigate to system and put it into rw rename your build prop to be buildprop.bak just in case things arent the way you like it so you can restore back quicker
download linkS:
BLUR PHOTON VERSION
http://dev-host.org/xV6
CM7 PHOTON VERSION ( just seen cougar updated so will have a new update again for the cm7 version this is based off of 2/10/2012j )
http://dev-host.org/sir
* lots of problems in the cm7 version flash at your own risk when I get time will try fixing it up better sorry for any issues or problems this has caused you leaving link up so if anyone wants it can have it
let me know of any issues or maybe something you would like added.
i realize that alot of these mods are already out there you can download them one at a time or you can try this bootleg buildprop and save yourself some time
I'll be the "guinea pig"
Will be giving this a go too
Also, just wanted to let you know that I didn't create or mod the raindrop fix, I just tested it on my MoPho and was happy to report it. The actual creator is linked in the thread I made for it, don't want to have anyone think I'm taking someone else's credit.
MoPhoACTV Initiative
moonzbabysh said:
Will be giving this a go too
Also, just wanted to let you know that I didn't create or mod the raindrop fix, I just tested it on my MoPho and was happy to report it. The actual creator is linked in the thread I made for it, don't want to have anyone think I'm taking someone else's credit.
MoPhoACTV Initiative
Click to expand...
Click to collapse
thanks so much for bringing that to my attention i dont want anyone getting upset either ill reread thread and edit with appropriate creds.
All it did was kill my services
Sent from my MB855 using xda premium
pbedard said:
All it did was kill my services
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
? kill your services can you be more descriptive, what rom are you using are you locked unlocked cm7, cm9 miui?
Flashed with cm7.2 and wifi doesn't work anymore. Runs smooth though.
Sent from my Motorola Electrify
nate6138 said:
Flashed with cm7.2 and wifi doesn't work anymore. Runs smooth though.
Sent from my Motorola Electrify
Click to expand...
Click to collapse
is it not working at all? or just doing the whole works then cuts off then works then disconnected then uncheck and it works the disconnects? thats not an issue with the prop but now if it killed wifi entirely thats another thing idk why would kill wifi .
the prop is based off blur maybe has something to do with it i have another one im going to release for cm7 users several lines need to be changed sorry you are having these issues only method to remove is to restore your backed up prop file or rename bootleg's prop to buildprop.bak and it should create a new one after you reboot. Or can extract the buildprop from the ROM you flashed and replace it to revert
about to go to sleep any more q's ill have to catch in the am
for now if on a non blur rom its not fully working ill have a cm7 version by monday of course can always make a backup of builprop and try for yourself gl
It killed everything even with 3 reboots nothing
Sent from my MB855 using xda premium
pbedard said:
It killed everything even with 3 reboots nothing
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
What rom are you using how did you install are you Photon or electrify to revert you can restore your backed up prop or can extract from the ROM you flashed and use it to replace the one it installed or can rename it to .bak and restart should create a new one once you reboot
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
make one of these for CM9 also does this include the SD card fix? where we had to change a number from 2 to 3.. i dont remember the line but im sure you know what i mean.
It errors the wifi out.
Sent from my Motorola Electrify
nate6138 said:
It errors the wifi out.
Sent from my Motorola Electrify
Click to expand...
Click to collapse
what rom are you using plus I see your sig says electrify IDK the differences but I would think thats why. its made for Photon on a stock based rom. To revert extract build prop from ROM you flashed and replace it. Sorry didn't work for you. Will be trying to get this worked out/ up for cm7 & 9 miui and electrify since they are 2.3.5 will need an electrify buildprop though anyone willing to zip it and send to me
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
tsdeaton said:
make one of these for CM9 also does this include the SD card fix? where we had to change a number from 2 to 3.. i dont remember the line but im sure you know what i mean.
Click to expand...
Click to collapse
wont work on cm right now so far all that tried on cm has had issues as for the sd thing not sure what you mean if you referring to the cm9 fix then no it has no fixes for 9 the one I make for 9 ill try to incorporate what I can so it can be a one stop shop for what will work. for now if not on Photon blur based rom id stay away unless just wanting to test for yourself if thats the case make sure to back up your buildprop or have the ROM you are using zip handy to extract the prop from it really sorry guys that are having issues I'm going to edit the crap out op to make it more clear as to who this is working for after work
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
Using a photon with cm7?
Sent from my MB855 using xda premium
pbedard said:
Using a photon with cm7?
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
cm7, cm9, and miui not supported yet will be soon you can try it see if it will work but so far people reporting issues.... So unless on a blur based ROM on the Photon use knowing it might cause issues so make sure you can revert
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
So am home now going to be trying to get the cm7 version whipped up
So far has been Wifi and data issues
Question?
Anyone using this on blur roms having these issues from what the replies have been I'm seeing only electrify and cm roms having issues if anyone on a blur based ROM could confirm having issues or not so I know if I need to be working on the original also.
Anyone wanting this made for electrify can get me the buildprop for it id be happy to make one
Well I've went on enough see ya
Sent from a [email protected] in the night
http://forum.xda-developers.com/showthread.php?t=1506250
Ill send you a build.prop of the electrify. how do you want me to send it?
BHermes21 said:
Ill send you a build.prop of the electrify. how do you want me to send it?
Click to expand...
Click to collapse
however you are able to would rather through pm or email so it doesnt link in thread
hey
i just flashes the latest cm7 rom ,
should i flash this buildprop too ?
what does it do?
thanks