Related
ROOTSide ROM
Base Flipside ROM with root/busybox/unknown sources enabled. Only thing different in this rom than rooting it yourself is you get to check/uncheck unknown sources. Yes, that means you can turn unknown sources ON and OFF! I have a clockworkmod recovery folder zipped up for distribution, but I want to post a full-fledged ROM zip file for the masses. PM me, and I will send you the ZIP file that I have right now.
What you get:
base install for the flipside (AT&T) with motoblur ready to set up. It is the exact same thing as doing a factory reset, but you get all the benefits of superuser with busybox and the addead feature of having unknown sources checkbox in the settings.
I will work towards a deoxed version this weekend as well.
No custom bootscreen (yet). No custom anything, really.
Almost There
I am currently in the middle of Deodexing the image. I have added in wifi tethering, and ensured it will have superuser and busybox pre-packaged. Next step is pushing this to my wife's phone and not having her get a pretty brick in return. If all goes well, I will be posting the image by morning light (CST).
Fingers Crossed!
Well
Things didn't go too well with my first build attempt. Appears to be a permission issue with the /system folder. I will sleep on it, and give it a second go in the morning. Sorry for the apparent "tease". If you want a faster build, I could use some other devs working with me.
Hey man, sounds like you're doing great! Keep it up...I already found a way to get the root with unknown sources checked, so i'm just gonna wait for the deoxed version! Hope it goes well as you try again.
Current Issues
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Me too...good luck!!
jonsjava said:
unable to deodex the following:
/system/app/AABSync.odex
/system/app/blur-services.odex
Will try to load to phone without dodexing those two files. Hopefully all will go well.
Click to expand...
Click to collapse
Both of those files are att/moto bloat... just be rid of them
Sent from my MB508 using XDA App
Glad to see some work on this device, I love the form factor but it's obviously not very popular with devs...
Very interested to see this come around. I would like to streamline the wife's phone. Her battery life is a 1/3 of my rooted and flashed X10. Sadly though I am NOT a Dev nor even a cook.
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
so I was curious, I was able to get to unlock mode with an sqlite thing and it worked just fine for me, but have you been able to knock out the bloat and stuff? cause it sounds like the makings of a custom rom lol
you know what the turtle said.. slowly but surely I will win this race
jonsjava said:
I would have had something sooner, but I ran into issues not related to the ROM. Still working on it. Anybody have an idea for upgrading the CWM from the one we can currently use?
Click to expand...
Click to collapse
Several ppl have said they have run into this problem...don't know what the deal is...
Is it possible to get CM7, or it's a problem with a locked kernel?
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
jonsjava said:
Ok, I just got a new phone for the Mrs., so I can break the flipside and unbreak it as much as I like.
Time for some real fearless development lol.
Click to expand...
Click to collapse
sounds good man, keep us posted on progress!!
So check this out...I messaged the guy at modmymobile and asked how things were going becuase I heard people were having problems getting an updated CMW and this is his response:
"been sittin on the updated cwm recovery binaries and been draggin my feet/takin a break the past week or 2. i'll throw something out soon, but cant commit to a timeframe, sorry."
Looks like things are on the up and up...stay patient everyone
GOOD JOB!!!,
We are waiting for the rom
Dukenukemx said:
Is it possible to get CM7, or it's a problem with a locked kernel?
Click to expand...
Click to collapse
I can't install CM7, it reboots and locks up, then I have to reinstall froyo. It never worked when I had eclair either.
Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Update: I'm now running 2 AOSP roms Kushdeck's 1.3b2(main rom) and SalvageMod 1.4 and a Sense rom SynergyRls1 and haven't noticed any major issues. Gps works on each rom as well as 4g. Synergy does have some lag and for this reason took some patience and a little longer to initially set up but it works decently for running off of an sdcard. On a side note I've heard claims that Synergy does have some lag issues running normally.
I plan on ordering a better sdcard with a faster class rating such as class 4 or 6 so hopefully this will decrease lag but overall I'm very impressed with Boot Manager. If nothing else this gives you a chance to test drive roms without having to go through the whole process of replacing your daily driver.
PLEASE READ: I've reached out to one of the developers of this app who's from XDA and asked for his help in answering the problems some of you are having. I wish I could help more especially since this a paid app and you guys deserve to have an app that work. Below are the links to email support through the app website as well as the one of the developers Conap who's from XDA. Maybe if they receive enough emails they will shoot over to this thread to help.
Sorry I can't help more. All I can do is verify that it's working on my Evo but don't have enough advanced skills to do a lot more.
App Support Address: [email protected]
Conap Contact (One of the Devs from XDA): http://forum.xda-developers.com/member.php?u=2468293 (I just pm'd him)
aerajan said:
Disclaimer: I didn't create Boot Manager and am not affiliated with the developers in anyway.
I didn't see anyone posting this yet so I figured some of you might be interested.
There's an app on the market now called Boot Manager that's 2.99 and allows you to dual boot up to 5 roms. You still have your main rom which is stored directly in your phone's memory and then up to four more that are stored and run from your sdcard. Because you're running secondary roms from your sdard those may not run as fast as your main phone rom but my preliminary testing has been pretty good.
Boot manager is simple to set up and use and requires no special skills. You don't even need to partition your sdcard.
All you have to do is put whatever roms you wish to run on your sdcard and then install them through Boot Manager. Initially setting up the roms takes maybe 15 minutes but once your done you can boot back and forth very quickly, much faster than doing nandroids.
Enjoy
Click to expand...
Click to collapse
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.
mattykinsx said:
Fantastic alternative to being able to update prl/data profile on aosp considering that functionality hasn't been adapted to aosp yet.
Click to expand...
Click to collapse
Yea that's a good point. I'm running Kushdeck's 1.3b2 gb aosp as my main rom and didn't even think of that.
https://market.android.com/details?id=com.drx2.bootmanager
Alright, this looks really great. Love the idea. Just wondering for those who have it, since there are different kernels associated with each ROM (going from CM to Synergy) would you have to go back in and wipe battery stats? Also, would vipermod carry from ROM to ROM or would you need to set it up for every ROM?
How much room on the SD card would you need to boot 5 ROMS?
edit: quite a bit of room, have over a gig on sd card and can't load synergy. Have to do some cleaning later. Wish it could import nands, that would rock.
edit 2: cleared room, installed synergy on slot 1, rebooted, hanging on evo 4g screen..... bah
Im trying this now. I have Mikg as my phone rom and installing miui as a test. Will report back when I do some testing on kernals and battery life.
I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App
i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.
yeah crazy... stuck in splash screen sooooo yay no bueno thus far...
locoboi187 said:
I'm getting error on editing boot.img when trying to install salvage.
Edit: even though this is an app, someone move it to the dev section. Needs more attention.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
alaman68 said:
i need some more instructions. What are we supposed to wipe in the Rom Installer section? Also, how do you flash Gapps?
hasn't worked yet, boo... 2 battery yanks and nand restores
Edit: Got into salvagemod from synergy through the app. Didn't flash the Gapps, so it wouldn't recognize the app, so when I tried to go back to the "phone ROM", I get a "boot.img failed to flash, not rebooting" error.
Click to expand...
Click to collapse
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
jbrawley1 said:
yeah crazy... stuck in splash screen sooooo yay no bueno thus far...
Click to expand...
Click to collapse
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.
It takes a while. Since it's booting from your sdcard it's not quite as fast the first time as when you normally flash a rom. Mine stayed on splash screen for a little while to the first time I rebooted. Also try another rom just to see if that works for you.
aerajan said:
Try doing it again. I've had that happen. Also the developer does state that not all roms will work. I've had 1 so far not work but I know Salvage works because I'm running it as a secondary right now.
Good question. That confused me first also. You only need to do wipes if you're installing a new rom over an original one in a slot. If the slot is empty you don't need to do any wipes.
I can't address the other problem since I'm not technically proficient enough with the app yet to give you suggestions. Sorry
To flash gapps just install the rom but don't reboot install gapps over the rom in the same slot.
Try doing it again or try another rom. My first tries didn't work either. Also as I mentioned above the developer says this doesn't work with all roms yet.
Click to expand...
Click to collapse
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App
Omfg will download and test this out ASAP and report back results!!
Sent from my PC36100
locoboi187 said:
Ext2 or ext4?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Ext 2 because it's compatible with more roms.
aerajan said:
Ext 2 because it's compatible with more roms.
Click to expand...
Click to collapse
still no go, error building the boot
Sent from my PC36100 using XDA Premium App
Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Also if you go back to OP I've posted links to email support or one of the devs who's from XDA. I pm'd him personally asking if he's willing to shoot over here and try to help. If you get the time send him a PM. Maybe if enough people from here contact him he will help.
aerajan said:
Ok, well I've contacted one of the developers of this app who's also from XDA to see if he will come over here to answer some questions since I'm not able to help as much as I wish and you guys paid for this.
Click to expand...
Click to collapse
Thanks
Sent from my PC36100 using XDA Premium App
It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).
pottyvick said:
It does not work on my evo. tried everything but it errors out while finishing building the rom.
Their description does say which phones it supports and EVo is not on there. They probably wont respond to any evo users (at least according to their description, since its a non supported phone).
Click to expand...
Click to collapse
I wonder what steps the other guy took to get it working on his evo
Sent from my PC36100 using XDA Premium App
well... ive gotten this to work with Miui as main rom, and Synergy Kingdom port 7/23 but confirmed i dont believe that synergy rls 1+God Mode ive tried tons this wont work...
pretty cool you can switch between aosp and sense pretty easily i like this lots hope in the future it becomes more stable and compatible!
This is meant to be a dev thread, not an end-user thread. Please keep this on-topic. End-user support and VM670 development are off-topic.
For the more user and Optimus V (VM670) oriented thread please check in here:
http://forum.xda-developers.com/showthread.php?t=1176888
If you are working on porting the phone to the VS660, LW690, US670, or MS690 with the eventual goal of inclusion in the IHO repository please check in here.
I'm trying port this for the ms690. I'll admit it's a bit over my head but I have a rooted and flashed M and a rooted but stock M at my disposal and a working android development environment.
My rom is compiling now after fixing the typo in the mms_config.xml. I would like to help get the proper changes in the IHO repo if I get this working, but I have absolutely no idea how all that works.
I'll update here if I get my rom compiled and let ya know how it runs. Anyone know how long it should take to completely compile a rom error free? I'm running 2 dual core xeons at 2ghz... This is a long compile for a >100MB file, heh.
Has anyone successfully ported using Ubuntu 11.xx on a 32 bit, vmware setup? I got it to work with wubi, but that messed up my windows. Can you run Ubuntu off of a thumb drive but use your hard drive for storage?
Sent from my LG-VM670 using XDA App
1. I thought you couldn't successfully compile on 32 bit since 2.2
2. Setting up a development environment in vm? or on a flash drive? Do you really deserve that kind of punishment?
I guess you could build on a persistent usb but but it sounds scary to me. I don't know if you could properly mount a drive in live usb, seems like you would need your build folder on a hdd or a 32gig flash.
Backup your stuff and throw on an ext partition. Your building will be easier in a native environment and a clean windows install never hurts.
My compile is stopped. I've been poking around and I don't think I'm gonna figure this out like all the other BS I've figured out.
GRRR this is ****ing stupid, tried to post my error but the forum thinks that xxx.xml is a web address and wont let me post cuz I don't have enough posts. If anyone can help me shoot me a PM I'm not gonna spam the forums to get my posts to post a ****ing error log. If I ever met a spammer I would kick him in the nuts for all the bull**** I have to deal with because of the crap...
pbailey212 said:
Has anyone successfully ported using Ubuntu 11.xx on a 32 bit, vmware setup? I got it to work with wubi, but that messed up my windows. Can you run Ubuntu off of a thumb drive but use your hard drive for storage?
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
I use a 32-bit version of whatever the LTS version is with VirtualBox. 10.04?
Sent from my LG-VM670 using XDA App
blarfiejandro said:
I use a 32-bit version of whatever the LTS version is with VirtualBox. 10.04?
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
I was thinking about downgrading Ubuntu and trying it, I'm on Ubuntu 11.xx now. I would like to keep the vmware setup, I like just minimizing vmware to go back and forth to windows. Plus everything's transferable between the 2 os'
Sent from my LG-VM670 using XDA App
Update: Its creating the zip file now, I just needed to up the ram available to vmware, I wish I would have tried that a week ago, thanks for hearing me ***** and moan about this
pbailey212 said:
I was thinking about downgrading Ubuntu and trying it, I'm on Ubuntu 11.xx now. I would like to keep the vmware setup, I like just minimizing vmware to go back and forth to windows. Plus everything's transferable between the 2 os'
Sent from my LG-VM670 using XDA App
Update: Its creating the zip file now, I just needed to up the ram available to vmware, I wish I would have tried that a week ago, thanks for hearing me ***** and moan about this
Click to expand...
Click to collapse
I had problems setting up a good build environment with 11.04, but 10.10 64 bit with VMware works great for me on Windows 7 64 bit.
EDIT: I forgot to mention that if anyone want to try my Optiums Cricket version they can grab it here: http://www.mediafire.com/?vcfc5jtwncsxkzg
I don't own a OC, I built it for a friend. He tells me that GPS, BT, and MMS are not working.
So I got my very own zip file, backed, wiped flashed, my phone told me It was "bad" so I went and restored my backup it said bad md5, I thaught no big deal, I keep a couple backups handy, all 3 of them said bad md5. I restored them before just fine, I don't know what's going on, I should just give up, but I'm stupid and enjoy a challenge. I guess I will start completely fresh again. "Goin back to compile"
Sent from my LG-VM670 using XDA App
somedood81 said:
I'm trying port this for the ms690. I'll admit it's a bit over my head but I have a rooted and flashed M and a rooted but stock M at my disposal and a working android development environment.
My rom is compiling now after fixing the typo in the mms_config.xml. I would like to help get the proper changes in the IHO repo if I get this working, but I have absolutely no idea how all that works.
I'll update here if I get my rom compiled and let ya know how it runs. Anyone know how long it should take to completely compile a rom error free? I'm running 2 dual core xeons at 2ghz... This is a long compile for a >100MB file, heh.
Click to expand...
Click to collapse
It'll probably take a couple of hours to compile. The easiest way to get everything included is to file a pull request on Github. Keep in mind I'm not going to accept any applications (so that rules out the real popular MMS patches floating around for the C and M). Most of the stuff for the M is already in the tree, I believe...
Some of the other stuff like cnd probably won't get fixed /just/ yet, but I'll rename the keymap file. What else did you have to change?
pbailey212 said:
So I got my very own zip file, backed, wiped flashed, my phone told me It was "bad" so I went and restored my backup it said bad md5, I thaught no big deal, I keep a couple backups handy, all 3 of them said bad md5. I restored them before just fine, I don't know what's going on, I should just give up, but I'm stupid and enjoy a challenge. I guess I will start completely fresh again. "Goin back to compile"
Sent from my LG-VM670 using XDA App
Click to expand...
Click to collapse
Someone mentioned that IHO wasn't computing checksums properly in the general dev thread. Try using another recovery and/or making sure your build box isn't on its way out?
Anyhow I'm using a 32-bit Ubuntu 10.04.3 VM to build everything and it works just fine for me (definitely need to throw some more RAM at the machine tho).
blarfiejandro said:
It'll probably take a couple of hours to compile. The easiest way to get everything included is to file a pull request on Github. Keep in mind I'm not going to accept any applications (so that rules out the real popular MMS patches floating around for the C and M). Most of the stuff for the M is already in the tree, I believe...
Some of the other stuff like cnd probably won't get fixed /just/ yet, but I'll rename the keymap file. What else did you have to change?
Click to expand...
Click to collapse
I had to fix a typo on a tag in the mms_config.xml, I think using the cnd from the V was a no no, so i commented out the cnd in the build. There was an extra space in a string in an xml file I can't remember that needed removed. Other than that I just put in the ko files and the gps libs and it was building fine.
I fixed the last error I had which was about 2.5 hours into the build and started the compile over... Then my workstation shut down. It refuses to even post. Tried a new video card to no avail. Dual xeon running rambus ram, LOL. Don't have any parts laying around for it other than drives and video cards.
My port is kind of stalled at the moment, heh.
Just thinking out loud:
Has anyone done a build for the MS690(Metro version)?
Is the "LG Optimus One, P500, > Optimus V Android Development" thread for all Optimus phones? Or just the V?
I was working on the ms690 b4 my linux box died. There are a couple of us working on it.
somedood81 said:
I was working on the ms690 b4 my linux box died. There are a couple of us working on it.
Click to expand...
Click to collapse
Do you have a CWM recovery?
What wasn't working on your ROM?
My first attempt gave me this: make: *** [out/target/common/obj/APPS/Mms_intermediates/src/R.stamp] Error 1
BobZhome said:
Do you have a CWM recovery?
What wasn't working on your ROM?
My first attempt gave me this: make: *** [out/target/common/obj/APPS/Mms_intermediates/src/R.stamp] Error 1
Click to expand...
Click to collapse
That was the last error I was working with actually. Don't know if I had it fixed.
The op m can't use CWM recovery. We have 2 custom ones, joneidys recovery and getitnowmarketing recovery.
somedood81 said:
That was the last error I was working with actually. Don't know if I had it fixed.
The op m can't use CWM recovery. We have 2 custom ones, joneidys recovery and getitnowmarketing recovery.
Click to expand...
Click to collapse
Can't use CWM? All other Optimus phone do!
Sent from my VM670 using Tapatalk
I don't know the details of why, here is a thread on it:
http://androidforums.com/optimus-m-all-things-root/352401-do-not-use-clockwork-mod-rom-manager.html
It would be cool if someone could figure out the problem and fix it...
BobZhome said:
Do you have a CWM recovery?
What wasn't working on your ROM?
My first attempt gave me this: make: *** [out/target/common/obj/APPS/Mms_intermediates/src/R.stamp] Error 1
Click to expand...
Click to collapse
Sounds like you need to have the proper MMS overlays in the device folder. Maybe.
blarfiejandro said:
Sounds like you need to have the proper MMS overlays in the device folder. Maybe.
Click to expand...
Click to collapse
The overlay/MS690/packages/apps/Mms/res/xml/mms_config.xml has a bad string.
Profile<string/> needs to be changed to Profile</string>
I posted a comment on your git.
I compile my 0.1 kernel and trying an other MS690 build.
Blarf, can you look at these two pastebin to see if you see anything wrong.
There are problems with my LW690 builds, wifi produces an error and camera is broken.
wifi - http://pastebin.com/hMmhH9Bk
camera - http://pastebin.com/ukSGQaWz
Bluetooth wasn't working and when I used the MS BT file it worked, do you think by using the MS BT in the LW is giving me the wifi problem?
Thanks for the help,
Bob
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
masterpker2 said:
I am relatively new to android, but I recently purchaced an Acer a100. I probably should have done more research... but unfortunately the bootloader is locked down pretty tight so I'm on a mission now to help find a way past this evil bootloader issue. I have scoured the Google plains only to find this tablet has missed out on alot of great dev possibilities due to the bootloader. But I did come across an interesting tidbit of dev info and am not sure if it would really aid us in our search for a fix. The Motorola atrix forums here on xda has some interesting dev on a file called kexec I believe. It seems as though someone figured out how to bypass the locked bootloader and was very close to finding a kernel that would load on top of the program, though the issue was then Motorola having some sort of security to shut down the radio on the device if a custom kernel was loaded... so.. that being said, would this project be worth continuing on the a100 since mine does not have a cellular radio and as far as I know no security to disable anything if a custom kernel is loaded? http://forum.xda-developers.com/showthread.php?t=1079097
Click to expand...
Click to collapse
AFAIK that was one the things thrown around for the Nook Tablet which also had a locked and signed bootloader. Maybe someone with the necessary skills should take a look and see if its viable? it looks like quite the undertaking though.
how can dumb people help
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
RobbandJenica said:
I was curious if anyone knew how a person with absolutely no development skills could help this locked bootloader situation and get some rooms on this amazing machine?
Click to expand...
Click to collapse
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
crossix said:
Talk to acer and express your concern and disappointment with thier device. Tell them what you think about the locked bootloader and make them understand how its imacting how you use the device and that the limitations they have placed on your device will effect future decisions on buying additional devices from them in the future.
I doubt it'll help, but it's better than sitting on your hands doing nothing.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
littleemp said:
I wanted to ask you or any of the other devs that were giving this a try, if you could perhaps spare a few minutes to fill us in on what has been tried and is currently being tried (if anything)? I think at the very least it would stop the posting of more threads on the same subject (perhaps even sticky such post so new owners and devs alike are informed on progress), and also maybe shine a little bit of hope to the community
Click to expand...
Click to collapse
I don't know if there is anyone that is actually working on a solution to unlock it or find a work around such as 2nd-init or kexec. I don't know if we have any experienced devs that have done that sort of thing in the past with other devices that actually own an a100 and are working on it. If we don't I'd suggest that someone contact someone that does have experience (ie. koush or possibly sc2k) and see if they would be willing to help.
I am not a bootloader / recovery guy and have never personally developed a working solution to a problem like this. I barely know how they work in conjunction with each other. I know that recovery runs it's own kernel and in order to get cwm to work you have to compile a kernel for your device and cwm uses it. I have tried several solutions that others have created but none of them have worked so far.
sc2k from the a500 forum created itsmajic for their device and I attempted to install it along with cwm but almost borked recovery on my tab in the process.
The recovery partition does some sort of checking (I dunno if its a checksum validation or what) but its obvious that the p7 partition in our device doesn't do the same thing as it does on the a500. So the bootloader hack for the a500 will not work for our device.
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
crossix said:
I have compiled kexec and got kexec-tools to run, but I don't know enough about the kernel or memory addresses to know how to launch an alternate kernel or what memory address to launch it in (if thats even the proper terminology??)
I have looked at 2nd-init, but don't understand where / how cwm would get launched from it.
I just don't have enough knowledge about the boot process / recovery to get a working solution for this thing. I don't consider myself a dev, but just a modder that has done some kernel tweaking and device tweaking here and there. I know how to use a c compiler, write sh scripts, check logcats for issues... enough to be dangerous but thats about it
Click to expand...
Click to collapse
2nd-Init might be possible, we just need to find a binary that starts within init/init.rc that can be hijacked. On Motorola phones it is logwrapper, at this line in init.rc is the first it executes.
Code:
exec /system/bin/logwrapper /system/bin/mount_ext3.sh userdata /data
For this to work logwrapper has to be renamed to something else (logwrapper.bin , .orig) and executed in a new executable script called, logwrapper. In the script just about anything can be done. To run cwm, / gets remounted rw new init files replace the old. busybox, other binaries and a hacked adbd are unzipped. 2nd-Init then goes to work killing process 1 (init) and starts cwm. I believe in this case cwm is 2nd-Init rather than a recovery partition.
The a100 init.rc doesn't use logwrapper. One idea, which may be too far fetched and too far into init, is hijacking the bootanimation binary, but it runs as user 'graphics' which doesn't have elevated privileges. So could an su binary, compiled without requesting SuperUser.apk, be used in the hijacked bootanimation??... If it's too far in the boot process maybe we could atleast get init.d tweaks.
Hashcode has come up with an inventive new approach to cwm bootstrap called safestrap. A different partition is used to hold the rom keeping stock intact making it almost impossible to brick. For anyone interested I recommend reading his blog to see how it works hash-of-codes.blogspot.com/p/how-to-safestrap.html?m=0/. Attached is the logwrapper script from my Droid3 to get an idea of how it starts cwm. The safestrap.apk can also be downloaded from hashcode's blog for a better understanding. DO NOT install it, it can be unzipped and analyzed.
At this point theres no reason we can't deodex then make a custom rom/theme with just replacing atleast the system apps and the framework. With the update.zips theres no reason not to.
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Icewyng said:
Some interesting stuff you have there...
So, you think that update-style ROM porting would be possible right now?
I will defenitely take a look at the logwrapper.
Sent from my A100 using xda premium
Click to expand...
Click to collapse
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful. So if the apks are decompiled and themed or even adjusting some code, they can be copied with a simple script from adb. If it bricks just use one of the update.zip's to recover. The first thing the updates do is format /system so no checksums or anything it should be safe.
I would think that aosp style roms can be compiled but most of acers framework would have to stay, along with all the libs. Kind of like some of Team Liberty roms.
Click to expand...
Click to collapse
True. I used edify script before to get my updates to work w/ CWR and I was formatting cache, userdata and system before reinstalling.
Perhaps working on an Acer update with the DSIDXA kitchen could help to get something workable?
Sent from my A100 using xda premium
eww245 said:
Using an update.zip? The only option we have now would be copying via adb or maybe dd but doubtful.
Click to expand...
Click to collapse
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
crossix said:
The update.zip method wont work through recovery. I tried to pre-root 2.007.04 and when you load any modified .zip file in recovery you get an android with an exclaimation...
I have successfully used dd to make/restore a backup of boot, recovery and system partitions. I haven't had a chance yet to deodex the system (too busy with other projects at the moment).
I mighe be able to do something with your post on that init method, just need to get some time to dig in to it.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Oh good, should be able to make backups of /data, it umounts clean and dd works so that's a step forward. I was worried about partition overlap. tar might be useful too cwm uses it and Titanium and AppExtractor both can restore the data.
Hopefully this weekend I can try that along with possible init.d
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Its nice to see a possibility of methods popping up. Hopefully we make some hedge-way here.
crossix said:
If I get a chance I'll mess around with the kernel that acer posted a while back on their site and see if I can't get it to compile. If it does, I'll see if we can try to get a working cwm. Don't go getting your hopes up though, if cwm requires any code changes to get it working then we still may be sunk. I've never attempted to roll my own cwm before, this'll be a first lol.
hmm... looks complicated...
http://www.acsyndicate.net/how-to-porting-cwm-to-other-devices-windows/
Click to expand...
Click to collapse
I'll look into it over the weekend as well. also, I will look into an update file and see if there are anything special in those as well.
Let us know how it goes with the kernel.
Did anyone ever experiment with NVFlash btw? or tried the Acer update decrypter?
Oh...and it seems the ICS ROM for the A200 has already leaked.
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
mvan4310 said:
Im gonna be ballsy and try and flash it later probably in 20 minutes. Probably wont work, but why not try(other than the fact I can brick my device, meh) Ill also mess around IN the file itself to see what parameters it checks for. Maybe we can do what they did for the A500, but slightly different, heh....
Click to expand...
Click to collapse
GL, you'll probably get an android with an exclamation point when you try and flash it due to different signing keys used between tablets.
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
mvan4310 said:
Lol, it got halfway, stopped for a few minutes and gave me the !. lol. It wiped my settings clean, seems as far as it got before it thought about the device, lol. Nice try though.
Click to expand...
Click to collapse
You should post the last_log file from /cache/recovery, that'll tell you why it died.
On another note, the acer supplied kernel didnt include the config file they used to build so I'm having to roll my own Tried compiling with a minimal amount of settings, but the compile died..
Hello,
I am considering updating my gingerbread based ROM on my old EVO 4g (I am currently running Cyanogen mod 7.1)...
Its been a very long time since I've flashed a ROM to my phone, but I have been wanting to upgrade to an ICS/JB ROM for a while because (amongst other things) I hear that these android 4.0 ROMs are better when it comes to battery life.. As you can probably tell, I am not one of these folks that re-flashes their rom every week so I may be a bit rusty with this and I am a little bit intimidated. While I would like to try something new I also am a bit worried that my lack of experience may cause me to make a mis-step and mess up my phone..
The ROM I am looking at right now is the new release of MotoBlur'd, found here: .. I understand that this ROM is based on CyanogenMod 10, and since it seems I cannot get a version of the raw CM10 directly to install on my phone, perhaps MotoBlur'd is the next best thing...
But before I open up this can of worms and go off and wipe my phone and flash this new rom, I had 3 questions which I hope someone with experience can answer
1) All other things being equal, would this actually help with the battery life, over the Gingerbread based CM 7.1?
2) Is it still the case that Netflix and other video viewing apps do not work with this (or any other ICS/JB) ROM?? They mention it in the android dev thread, but no one has confirmed that these things work or not work.
3) Do I have to peroform any extra steps or install anything else (other than what is shown in the instructions) to move the phone from CM 7.1 to the latest Motoblur'd ?? For example do I need to install an ICS based ROM first before JB? Or can I just flash directly to this ROM??
Hopefully I can do this without causing too much damage or requiring too much help from the users in this forum... Of course any advice or suggestions anyone can give me would help...
Thanks
TPK2013
For number 3 just make sure your using the smelkus 4.3 recovery and for sure wipe the sd-ext to make sure you get a clean flash..
Sent from my PC36100 using xda app-developers app
hondafreak513 said:
For number 3 just make sure your using the smelkus 4.3 recovery and for sure wipe the sd-ext to make sure you get a clean flash..
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
1. battery life will be worse. most likely
2. That is stil lthe case
3. Read the Guide in my signature (Evo Superguide). It'll help you a lot
HipKat said:
1. battery life will be worse. most likely
2. That is stil lthe case
3. Read the Guide in my signature (Evo Superguide). It'll help you a lot
Click to expand...
Click to collapse
Excellent guide, Hipcat... I think this will really be helpful to me... As someone who doesn't do this all the time, it can really help to have a guide like that to cover all the bases.. I know we are supposed to try to search for the stuff that we need to know, but sometimes its hard to know even what we need to know, and sometimes the multitudes of information we find is contradictory or out of date, so this really helps..
I found a broken link on it, so I posted that as a reply in your thread (I hope thats okay)...
I think I may just stick with my GB based rom, as much as I would like to monkey around with ICS or JB.. I guess I don't see the sense of switching if it won't help my battery life and if it will prohibit the use of video playing apps (which, I know, suck a lot of battery)..
The biggest problem for me is the battery life (I found several contradictory explainations on how to calibrate the battery, I will try the one found in your guide next), but mainly I believe my problem is that I have too much garbage loaded on the phone (not reloading after a year and a half can do that), and a lot of stuff loads in the background so that is probably affecting my battery life.. Also I don't think I am using the most up-to-date radio, which is probably causing the most battery drain of all... So I am going to try the following...
1) I am going to (actually I already have) upgrade my radio to 2.15.00.01.15
2) As per your, and honda's suggestion I will try to update my recovery to smelkus 4.3 (I think I am using clockwork recovery right now, although I am not sure if that is the same thing or not)..
3) I will try to re-format and re-partition my SD card and attempt to install A2SD so I can have more room for apps (can I use A2SD with CM 7?)
4) I will wipe everything, and reload to CyanogenMod 7.2 (perhaps this will work better than 7.1) and reload about half the apps I have on there now (only the stuff I am using now)..
If battery life is my main concern, is there a better ROM I should be using??? I picked CM in the first place because it was an AOSP (no frills, no extra garbage) ROM, however I haven't been able to update my PRL (havent ever updated it, probably)...
Thanks again for your response... You and your guide have been quite helpful...
TPK2013
TPK2013 said:
Excellent guide, Hipcat... I think this will really be helpful to me... As someone who doesn't do this all the time, it can really help to have a guide like that to cover all the bases.. I know we are supposed to try to search for the stuff that we need to know, but sometimes its hard to know even what we need to know, and sometimes the multitudes of information we find is contradictory or out of date, so this really helps..
I found a broken link on it, so I posted that as a reply in your thread (I hope thats okay)...
I think I may just stick with my GB based rom, as much as I would like to monkey around with ICS or JB.. I guess I don't see the sense of switching if it won't help my battery life and if it will prohibit the use of video playing apps (which, I know, suck a lot of battery)..
The biggest problem for me is the battery life (I found several contradictory explainations on how to calibrate the battery, I will try the one found in your guide next), but mainly I believe my problem is that I have too much garbage loaded on the phone (not reloading after a year and a half can do that), and a lot of stuff loads in the background so that is probably affecting my battery life.. Also I don't think I am using the most up-to-date radio, which is probably causing the most battery drain of all... So I am going to try the following...
1) I am going to (actually I already have) upgrade my radio to 2.15.00.01.15
2) As per your, and honda's suggestion I will try to update my recovery to smelkus 4.3 (I think I am using clockwork recovery right now, although I am not sure if that is the same thing or not)..
3) I will try to re-format and re-partition my SD card and attempt to install A2SD so I can have more room for apps (can I use A2SD with CM 7?)
4) I will wipe everything, and reload to CyanogenMod 7.2 (perhaps this will work better than 7.1) and reload about half the apps I have on there now (only the stuff I am using now)..
If battery life is my main concern, is there a better ROM I should be using??? I picked CM in the first place because it was an AOSP (no frills, no extra garbage) ROM, however I haven't been able to update my PRL (havent ever updated it, probably)...
Thanks again for your response... You and your guide have been quite helpful...
TPK2013
Click to expand...
Click to collapse
Yep, I fixed that link and what you said is why I wrote that guide; because searching can be a real pain in the @ss sometimes. It's like a teacher telling you to look up a word you can't spell. Well how do you search for an answer if you're not really sure of the question?? lol
You cant update your PRL on any non-stock rom. It has to be stock for you to be able to do that
Well if battery life is your main concern I always suggest a good sense 3.0 ROM. If you are worried about bloat that can be removed. If you want I can hook you up with a rom/kernel combo with everything you want.
When I am not testing or making a new rom I use sense 3.0 and can get 8 hrs of heavy use on stock battery. Thats netflix with 3-4 hrs use plus web surfing and calls during the rest. On my extended battery with light use I can get 4+ days.
If you would like to try my rom pm me before you partion your sdcard. There are certain things you need to do for it to work right.
Sent from my PC36100 using xda app-developers app
CNexus said:
You cant update your PRL on any non-stock rom. It has to be stock for you to be able to do that
Click to expand...
Click to collapse
Perhaps I will go to stock and try to update the PRL before I go ahead and update the ROM to custom... However, this Evo is on Boost Mobile (not Sprint) network, so I am not sure how to appropriately update the PRL... Should I just update it as if it were a regular Sprint Evo 4g or does it matter?
CNexus said:
You cant update your PRL on any non-stock rom. It has to be stock for you to be able to do that
Click to expand...
Click to collapse
Umm updating prl only requires the *228 call from the phone and it works on any rom. Now to put a custom or older prl it takes a bit more. Updating your profile now that I do believe you have to be on a Sprint rom but I don't have Sprint so I can't say for sure.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
Umm updating prl only requires the *228 call from the phone and it works on any rom. Now to put a custom or older prl it takes a bit more. Updating your profile now that I do believe you have to be on a Sprint rom but I don't have Sprint so I can't say for sure.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Never heard of that *228, so cant say anything about that
Updating profile and prl I've always seen and heard can only be done on stock, unless you use this ##codes apps I saw somewhere....
The ## codes only work on the sprint roms. To change prls on AOSP roms you need a windows pc with qpst setup and prl files on the pc. Then you have to enable diagnostic mode through adb or a terminal emulator. There is a thread here on our EVO forum to do it. I will bump it so you can check it out. It sure beats all the backing up and restoring to do it.
Edit: I bumped it. It is in the dev section.
jlmancuso said:
The ## codes only work on the sprint roms. To change prls on AOSP roms you need a windows pc with qpst setup and prl files on the pc. Then you have to enable diagnostic mode through adb or a terminal emulator. There is a thread here on our EVO forum to do it. I will bump it so you can check it out. It sure beats all the backing up and restoring to do it.
Edit: I bumped it. It is in the dev section.
Click to expand...
Click to collapse
Yeah. Theres an app that uses scripts to emulate the ##code functions.
Really? I can't believe I have not heard of that till now. Do you know what it is called? I would love to check it out.
Sent from my PC36100 using xda app-developers app
jlmancuso said:
The ## codes only work on the sprint roms. To change prls on AOSP roms you need a windows pc with qpst setup and prl files on the pc. Then you have to enable diagnostic mode through adb or a terminal emulator. There is a thread here on our EVO forum to do it. I will bump it so you can check it out. It sure beats all the backing up and restoring to do it.
Edit: I bumped it. It is in the dev section.
Click to expand...
Click to collapse
Found the thread, thanks!!
Now I just have to figure out which PRL file to use for my Evo on Boost, and where to find it (I think this is what stopped me from updating the PRL before, not knowing if I should use a sprint PRL or something else)...
Edit: I did find this thread regarding boost PRLs on EVO
And if there is indeed an app that emulates the ## commands, I would like to know what that is...
... TPK2013
Heck if your on boost you need a boost prl. You can Google boost prls and find dozens of them. I would suggest using the latest one. Just dial *228 and it will update your prl. After it finishes reboot your phone. It is really that simple. I do it on my cricket flashed EVO but it works for every service provider.
Sent from my PC36100 using xda app-developers app