I'm taking requests for what ROMs you'd like to see in Safestrap friendly form?
FOR ROM DEVS: The process is really easy. To make a ROM .zip Safestrap friendly (meaning able to run as 2nd-system) you make sure of 3 things:
1. Make sure in your update-script commands (mount / format) you don't reference the system partition as /dev/block/mmcblk1p21. Use /dev/block/system instead.
2. Create a folder in your zips: /system/etc/rootfs and add these files (keep them separated -- not in a .zip)
3. Remove all references to hijacks. Keep the stock logwrapper file intact. Can be downloaded here.
FOR THE REST: Let me know what you ROMs you want converted and I'll see what I can do.
Apex. Darkslide.
Sent from my DROID3 using Tapatalk
I know this is CM based, but I want MIUI.
Sent from my DROID3 using xda premium
HAH. Ok, they have to be EXISTING ROMs for D3.
>.>
I know you've been working with ChevyCam, so I assume Steel Droid will be supported eventually?
Liberty would be nice lol
/droid3
yea...i kinda skimmed the topic.. my bad .
Seems the process to be safe strap friendly is pretty striaght forward. Perhaps this thread can be rewritten as a dev sticky so anyone looking to make a custom rom will already have safe strap in mind when coding. It would be nice to have an actively supported recovery for our phones. I divert from the topic slightly, but I feel that by setting a standard you won't have to worry about porting every update to every custom ROM. I'm sure AOSP keeps you up at night enough already.
sic4672 said:
Seems the process to be safe strap friendly is pretty striaght forward. Perhaps this thread can be rewritten as a dev sticky so anyone looking to make a custom rom will already have safe strap in mind when coding. It would be nice to have an actively supported recovery for our phones. I divert from the topic slightly, but I feel that by setting a standard you won't have to worry about porting every update to every custom ROM. I'm sure AOSP keeps you up at night enough already.
Click to expand...
Click to collapse
I would have to agree, although maybe just another thread like "[Devs] Safestrap your rom!" to put the onus on individual rom developers might be more appropriate and let you continue with your awesomeness!!
maybeh some monster love? =D
Yonnor said:
I know you've been working with ChevyCam, so I assume Steel Droid will be supported eventually?
Click to expand...
Click to collapse
Yes, it will be supported. I just need to upload a fixed version (thanks Hashcode), and I will post a link in the OP, both here and on DroidForums.net
Deodexed stock gets my vote.
narcotICS rom? wanting to get the best of ice cream sandwich for my d3
joeGhard26 said:
narcotICS rom? wanting to get the best of ice cream sandwich for my d3
Click to expand...
Click to collapse
There is a system wide ICS theme for Liberty, it's for Bionic but it works just fine.
Related
This was the tweet fromCvpcs!!! (We haz a booting "true" AOSP system with 0 blur! http://www.youtube.com/watch?v=PPqfIRZP7Mc Still very buggy but I'm working on it)
Sent from my DROIDX using XDA App
booyah! let get er done!
Sound like good news!
Still, could anybody explain what AOSP boot means? Will this enable us to boot a custom kernel on the x?
I have no idea what this means except 100% no blur sounds awesome!
AOSP essentially means it was built completely from source. Not built based on Moto's own build with their custom framework (blur) crap. It is a true complete Vanilla rom.
Android Open Source Project
http://source.android.com/
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
If they got an aosp to run they should be able to modify the kernel no? Thought that was the while point of the exploit nenolod is working on.
Sent from my DROIDX using Tapatalk
this is too awesome.
Joe92T said:
So they got an AOSP rom to run using the stock moto kernal? Because obv we can't change kernals at this point yet
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
vonfeldt7 said:
No, from my limited understanding, this isn't using the Stock Kernel. They've figured out a way to get NVRAM into Engineering Mode..
Someone correct me if I'm wrong.
Click to expand...
Click to collapse
This AOSP has actually been running for a while now. Its being developed by cvpcs, the same guy who's been developing the Sapphire roms for Droid. I don't know if he's using the recent exploit that has made the rumor-mill lately. He claims its a true AOSP boot, which implies a custom kernel compiled from source. However, for all we know he could still be using the Moto 2.2 kernel, but replaced everything else in user space with fresh, compiled code.
Either way, its interesting. Despite Motorola's best attempts, it looks like the Droid X (and Droid 2 by implication) will soon be free of its eFuse prison, allowing us users the choice of what to run on this device.
We won't be getting rid of eFuse, as it's hard coded into the silicon itself in NVRAM, as I understand it. Its just that folks are working on getting the keys to the prison .
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
sniffle said:
hi guys,
i am sniffle, a member of the CCRoms Team that produces Sapphire(Droid 1), Ruby(HTC Incredible), Obsidian(Droid X), Emerald(HTC Evo)
to clarify a few things.
this does NOT utilize the bootloader hack, it is a custom boot setup that initializes the boot process a second time to load the custom rom after the bootloader has ran all of its checks. It technically could be considered a second boot setup as it does initialize the boot process a second time.
it does NOT use a custom kernel, it uses the stock kernel, since the bootloader is not locked. the process to actually be able to use this rom is quite involved. When we are ready to release, there will be detailed instructions for flashing. If you aren't comfortable with ADB, terminal executions this rom will not be for you.
i will try to explain more as the questions come up, but for the most part that's all there is to say... other than to say that more is broken at this point than fixed. as more news comes available i will let you guys know.
Click to expand...
Click to collapse
Thank you guys for your hard work, I am sure that most of the community is as excited as I am to see your work make it to the X. I love the boot ani from the video, and even though this is my first android phone the things Ive read about your teams previous releases has me EXCITED for this to hit.
appreciate your update and clarification, sniffle!
OMG, aosp 2.2 for my droidx would be awesome. Nice to set someone working on it, props and kudoes.
Sent from my PC36100 using XDA App
i hear this is almost 100% working!
LT1UltraZ said:
i hear this is almost 100% working!
Click to expand...
Click to collapse
Heard the same this morning. Very excited!
dogswind said:
Heard the same this morning. Very excited!
Click to expand...
Click to collapse
Would love a source on this info.
Almost 100% is a bit too strong of a descriptor, there are still some major bugs like rebooting on sleep(hitting the power button to turn the screen off) and a few others on top of that. With our next sapphire and Ruby release we will be making the latest build publicly available for other development to help figure out a fix for these problems.
I want to develope my own kernels and roms but I don't know the road to take to get there. I'm working in some new things (editing and creating system files to boost performance, etc) but What and where should I start learning to be able to make my own roms and kernels for the hero community?
Also which is better liquids 2.1sense rom or nfinites stock 2.2 rom? Pros and cons thank you
Sent from my DROIDX using XDA App
Well thats gonna be a matter of opinion.Liquids are optimized and most of the bloat and google stuff removed. Nfinite's not optimized,has senseand sprint apps.Both have odex and deodex versions. I prefer both odex versions of the .2 roms not big on theming ,also the odex ver. boot faster.Deca's kernels are compatable with all.If anyone can add anything that I missed,jump in get your feet wet and add to my observations based
kifno said:
I want to develope my own kernels and roms but I don't know the road to take to get there. I'm working in some new things (editing and creating system files to boost performance, etc) but What and where should I start learning to be able to make my own roms and kernels for the hero community?
Also which is better liquids 2.1sense tom or nfinites stock 2.2 rom? Pros and cons thank you
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Sent FromMy Pedal-to-the Metal Hero
I think what a lot of guys do is take a rom that's already made, strip it down, and then reassemble it according to how they want
That's essentially what liquid did. So I would suggest to learn the layout and how stuff is put together you do that for your first time.
I'm no dev tho, and really have no idea how to do that kind of detailed stuff. Its just what I've seen others here do and be successful and its what I would do if I could. Good luck.
Sent from my 2.2 Hero
MrDowntown12 said:
I think what a lot of guys do is take a rom that's already made, strip it down, and then reassemble it according to how they want
That's essentially what liquid did. So I would suggest to learn the layout and how stuff is put together you do that for your first time.
I'm no dev tho, and really have no idea how to do that kind of detailed stuff. Its just what I've seen others here do and be successful and its what I would do if I could. Good luck.
Sent from my 2.2 Hero
Click to expand...
Click to collapse
I really needed a starting point thanks a lot. Now I get to doing my research and hopefully and soon release my own rom
Check this post out by Decad3nce -> [RESOURCE] ROM Cooking
That's where I started for reading on development, editing, etc.
Currently MIA for a few weeks - Sent from my HERO200 using XDA App
kyouko said:
Check this post out by Decad3nce -> [RESOURCE] ROM Cooking
That's where I started for reading on development, editing, etc.
Currently MIA for a few weeks - Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Wondering why the bionic has a few roms out already and we dont? Do they have a fully working cwm? Am i missing something? Just curious. Thanks.
So far I've seen a deodexed stock rom and an early pre-alpha of CyanogenMod. What else has been posted for the Bionic?
The deodexed ROM is no different than stock for users and offers zero benefits.
The CM7 ROM was created by the lead CM team member of the Motorola Droid and Motorola Droid X (lots of experience with Motorola phones) and because he was donated a Droid Bionic. It's a completely useless ROM at this point as most of the hardware sensors do not work. It boots. Not much else.
Buy cpvcs a Droid 3, ship it to him and he will have a CM7 ROM booting on it within days of receiving it. It'll be just as useless as the Bionic's version....but it'll be there.
Give it time....it is going to be a while before a good solid/stable ROM is released.
First rule of XDA, don't ask for ETA's. If you want a custom ROM, nothing stopping you from trying to cook one your own.
Edit, hit the thanks instead of quote, they really should move that button
lordgodgeneral said:
First rule of XDA, don't ask for ETA's. If you want a custom ROM, nothing stopping you from trying to cook one your own.
Edit, hit the thanks instead of quote, they really should move that button
Click to expand...
Click to collapse
Where in my post does it ask for an eta???? I was asking why. Its a simple question.
heres the thing...waiting for CM7 will be worth the wait.. mmhmm.
..
They can flash, they're using the same flashing method that the D2, DX are using with 2nd init and hijacking. Hashcode hasn't enabled flashing on the D3 recovery yet because he's trying to do something a little different and a little safer from what I understand. From his explanation over in the clockwork recovery thread in development he's working more on a dualboot flashing system where we would basically leave the stock system intact and run the custom rom off a different partition/folder. This would allow us to boot to the stock rom if something happens during the flash process on the custom rom. Since using the 2nd init and hijack and not having an unlocked bootloader, CWR gets loaded into the preinstall partition along with the hijack files, so there's a chance these can get overwrote while flashing if something goes wrong and potentially soft brick the phone.
Don't worry the D3 is the flag ship phone that won't go to much longer with out some kick ass roms. But it is some BS that the bionic is getting roms right off the bat, while we wait. But I would be happy to send a d3 to those guys... if it would help or will bionic development and hacks work for the d3 as well????
Sent from my DROID3 using XDA App
Since when?
lordgodgeneral said:
First rule of XDA, don't ask for ETA's. If you want a custom ROM, nothing stopping you from trying to cook one your own.
Edit, hit the thanks instead of quote, they really should move that button
Click to expand...
Click to collapse
Since when has their been rules on topics asking ETA's on this forum, or any other forum in general? I know it's taboo to ask questions that have already been answered in several posts, but there are several forums specifically about speculating the ETA of not only just devices or OTA leaks, but about the cooking of roms on freshly rooted phones as well. The question of this post is legit, especially for users without the experience that more knowledgable users like tcrew and you (lordgodgeneral) have contributed to answering a question ALOT of people in the droid 3 community are wanting to know. Glad this topic existed, helped me out..
mmsomekid said:
Because the bootloader is still locked. The Bionic will probably get unlocked slightly faster than the D3 because they have more developers working on it, but theyre so similar that i would expect the D3 to get an unlock the same day as the Bionic. Unless Motorola finally unlocks the bootloaders but who knows when that day will come...
Edit: there is an UNL3ASH3D rom now available for the bionic, i didnt think they could flash yet in CWM?
Sent from my rooted Droid 3
Click to expand...
Click to collapse
It doesn't matter if the Bootloader is locked. It will probably never be unlocked.
Its been a rule since the devs on this particular forum specifically asked us not to ask for eta's. We have people cooking roms, were just waiting for our awesome version of CWM to be stable and safe to use. I'm as anxious as any of you, but don't hassle the devs that are working so hard to make our phones the best out there. Give them time.
sent from my ROOTED DROID3 from the XDA app
ROM Manager Premium Clockwork Recovery
Until now I have been more or less bemused by the complaints that the Droid 3 was being somewhat neglected in the development community in favor of the Bionic, assuming that there was more than a little exaggeration of the progress on the Bionic vs D3. Now, however, I am beginning to wonder if the complaints may not have been somewhat justified. I know no one owes the D3 owners anything on the dev side, but to see the Bionic now able to use ROM Manager while I sit with a previously paid app that does nothing on my phone is admittedly frustrating. I keep reading posts saying that any Bionic developments will be followed rapidly by similar progress on D3, so I hope I can use ROM Manager on my phone in a few days.
pgzerwer said:
Until now I have been more or less bemused by the complaints that the Droid 3 was being somewhat neglected in the development community in favor of the Bionic, assuming that there was more than a little exaggeration of the progress on the Bionic vs D3. Now, however, I am beginning to wonder if the complaints may not have been somewhat justified. I know no one owes the D3 owners anything on the dev side, but to see the Bionic now able to use ROM Manager while I sit with a previously paid app that does nothing on my phone is admittedly frustrating. I keep reading posts saying that any Bionic developments will be followed rapidly by similar progress on D3, so I hope I can use ROM Manager on my phone in a few days.
Click to expand...
Click to collapse
Droid 3 Bootstrap on Market: https://market.android.com/details?id=com.koushikdutta.droid3.bootstrap and direct download: http://download.clockworkmod.com//test/Droid3Bootstrap.apk (ROM Manager support as well)
bam
If you have already purchased Rom Manager, just install it and have it install the custom recovery for you...
Edit: Maybe not.. it shows it installed CWR but I can't boot into it..
A large PayPal donation to the first flashable Rom!
Sent from my DROID3 using Tapatalk
Rocinante said:
If you have already purchased Rom Manager, just install it and have it install the custom recovery for you...
Edit: Maybe not.. it shows it installed CWR but I can't boot into it..
Click to expand...
Click to collapse
You have to use koush's bootstrap...
Sent from my DROID3 using xda premium
Just curious, outside of no custom kernels nothing else has to be used from the stock system, correct? So custom roms with our 512 of ram will be more than enough.
Sent from my DROID3 using Tapatalk
ROM Manager Premium Clockwork Recovery
OK, I am a believer now. No more pathetic whining by me, at least for the next 5 minutes or so.
Androidsims said:
You have to use koush's bootstrap...
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Yeah, I'm guessing there is a special way it boots into recovery with the custom app because I can't get Rom Manager to boot into recovery..
Please delete thread mod
SynysterSilence said:
Hello welcome to the first ever Synyster rom. This is going to be complete 100% dinc stock that i will create from a nandroid back up (im getting a refurbished one today) It will be posted tonight so if anyone wants to be alpha testers PM me or simply comment. Also, if you want to be a tester, i would rather you have a good understanding of rom development. This is so that if you run across a problem you could fix it for me since i know little about this. If you are able to fix something and do it succssfully i will update the post and give you credit for what you did.
Click to expand...
Click to collapse
nice name.
While I love your enthusiasm, Stock+ is a good stock ROM. There's also several other releases of the OTA on here. If you were to develop another stock ROM for this community, it really wouldn't be a very big contribution.
A community built ROM is kind of a cool idea though.
Sent from my ADR6300 using xda premium
yea but theres times when im looking for a pure stock rom for it and i can never find it. I love stock plus its great but i have 2 primary reasons for this: giving people a pure stock rom, and giving people a pure stock rom to use as a base. also i plan to do this for several other devices thatll be the point of the synyster stock rom series is to give different phones absolute stock if needed.
synisterwolf said:
nice name.
Click to expand...
Click to collapse
why thank you sir xD
Why build from a nandroid when the ruu and otas are available? That makes no sense to me personally.
Sent from my ADR6300 using XDA Premium App
SynysterSilence said:
yea but theres times when im looking for a pure stock rom for it and i can never find it. I love stock plus its great but i have 2 primary reasons for this: giving people a pure stock rom, and giving people a pure stock rom to use as a base. also i plan to do this for several other devices thatll be the point of the synyster stock rom series is to give different phones absolute stock if needed.
Click to expand...
Click to collapse
Might I suggest using the latest OTA? A nandroid backup isn't necessarily the best base for a rom.
If you do end up going the way of a nandroid backup, only use the system and boot images. The data and cache partitions will be created on first boot.
I would also suggest making a /data/app folder in your rom zip for bloat/market apps, so the user can uninstall them easier.
wdfowty said:
Might I suggest using the latest OTA? A nandroid backup isn't necessarily the best base for a rom.
If you do end up going the way of a nandroid backup, only use the system and boot images. The data and cache partitions will be created on first boot.
I would also suggest making a /data/app folder in your rom zip for bloat/market apps, so the user can uninstall them easier.
Click to expand...
Click to collapse
will do ill see what i can do if i have any troubles would you be able to help me out with it? ill give you full credit if you do.
blastthenoise said:
Why build from a nandroid when the ruu and otas are available? That makes no sense to me personally.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
cause im originally making this for normal use like any other rom im just allowing people to use it as a base if they so choose. also alot of people that are new to making roms dont know how to use otas or the ruu so using this would be a great way for them to start out
If you want a stock ROM just use the OTA.
Let me google that for you.
SynysterSilence said:
cause im originally making this for normal use like any other rom im just allowing people to use it as a base if they so choose. also alot of people that are new to making roms dont know how to use otas or the ruu so using this would be a great way for them to start out
Click to expand...
Click to collapse
If you are using the kitchen to build your ROMs you are better off using the rom.zip file found in the RUU or one of the other bases already posted on here. There are like 5 or them already. I personally would never use any ROM built off a nandroid even my own. That said I have made my own stock ROMs before using the kitchen and found its best to just use wildstangs gingerbread base which has been cleaned up removing all the Sprint stuff out of it. Saves the time of going in and editing the build.prop file yourself.
To extract the rom.zip file start the RUU and once at the first main screen click Start>Run and type %temp% now, find the newest folder and in there will be a ZIP file called Rom.
Wildstangs base:
http://forum.xda-developers.com/showthread.php?t=1247253
I just purchased a Motorola Droid 3 XT862. It came loaded with a whole lot of Verizon stuff, and assumes I'm living in the USA. I'm living in Australia and would really prefer to have a choice of locale, and just get all of the pre-installed stuff off there because I'm not gonna use most it. From what I can tell, my only option is to flash the phone with a different firmware.
While I'm aware of the additional features of a couple of the mods such as Cyanogen, because this is my very first Android phone and I'd just like to play around with the stock OS before making any decisions regarding mods, I'd prefer to just stick with vanilla Gingerbread.
So my question is, for someone who has no idea what they're doing, how do I go about putting the stock Android OS on my phone?
Honestly CM is as close for Gingerbread you will get. There are some good stripped down ROMs based off of stock.
Sent from my XT862 using XDA
You should try Ice Cream Sandwich.
Sent from my XT862 using XDA
I'm not quite ready to try Ice Cream Sandwich just yet.
Do you think it simply isn't possible to get a stock version of Android for my phone?
I use Mavrom myself http://www.droidforums.net/forum/maverick-rom-d3/200510-maverick-rom-v3-5-droid-3-a.html
use it with a different launcher to get rid of the blur launcher, and the rom is pretty close to stock android. You can choose google mucisc and stock messaging too.
No verizon-crap either.
If you don't want mavrom i heard liberty is close to stock too, but never tried it myself and not sure if's being updated still
I'm not sure what the launcher is, sorry. I literally have no idea what I'm doing.
djmattyg007 said:
I'm not sure what the launcher is, sorry. I literally have no idea what I'm doing.
Click to expand...
Click to collapse
Well, motorola uses blur launcher.. which is basically the way your homescreen looks (=desktop) and your app drawer. So if you don't want blur use something like go launcher, or stick with blur if you don't care.
You can use morelocale2 (app) to choose your locale.
You could also just root and use the de-bloat script (stickied) to remove all the bloat-ware
You should root your phone and install CyanogenMod 7. It's not ICS and it's quite stable. It's an AOSP (Android Open Source Project) ROM so all those useless apps (bloatware) will be removed.
The link to the thread is here http://forum.xda-developers.com/showthread.php?t=1308924
I'm not sure if Australia is GSM, but here's the link for the patch if it is. http://forum.xda-developers.com/showthread.php?t=1357350
I have not tested the patch as I live in the US
djmattyg007 said:
I'm not sure what the launcher is, sorry. I literally have no idea what I'm doing.
Click to expand...
Click to collapse
I'll give a counter point to all those saying "root your phone" or flash this ROM or that ROM. Since you say, " I literally have no idea what I'm doing" and elsewhere you say this is your first Android my recommendation would be to just stick with stock for a while and learn how things work before diving into rooting, custom ROM's etc.
In the meantime, one pretty harmless thing you can do is to try different launchers. These give you a somewhat different look and feel to the "desktop" but since they are really an app, you can easily get back to stock by just uninstalling it. That would be much more of a pain free way to go while you try things out and learn. I would ignore those telling you to root at this point.
The only reason I would root is because the battery life is better when you make some tweaks that are only available on root. Even if you just tweak the stock ROM with a couple things it can be worth it.
Sent from my DROID3 using XDA
ratman6161 said:
I'll give a counter point to all those saying "root your phone" or flash this ROM or that ROM. Since you say, " I literally have no idea what I'm doing" and elsewhere you say this is your first Android my recommendation would be to just stick with stock for a while and learn how things work before diving into rooting, custom ROM's etc.
In the meantime, one pretty harmless thing you can do is to try different launchers. These give you a somewhat different look and feel to the "desktop" but since they are really an app, you can easily get back to stock by just uninstalling it. That would be much more of a pain free way to go while you try things out and learn. I would ignore those telling you to root at this point.
Click to expand...
Click to collapse
This was my first android phone and the first thing I did was root it. With pete's tool it couldn't be easier
so is there still no way to flash back to stock if you do the stage upgrade to 906?