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..
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.
The only determining factor on whether I stick with OEM ROM or flash monster/steeldroid ROM is this: do these custom ROMs have a single bug?
So, users of monster and steeldroid ROMs: are there any bugs?
There are absolutely bugs in both ROMs but there are bugs in OEM too. Both SD and Monster run so much faster than stock. You can still do everything youre used to on the roms. CM7 had the phone broke at one point but even thats fixed now.
Thanks.
I've got one more question if anyone can answer it. Do either of these ROMs I mentioned work on the Verizon Wireless Droid 3 or the GSM Droid 3?
I own the Verizon Wireless one (gotta make sure I don't flash an incompatible ROM by accident).
What, DarkDroid not good enough for you? :'(
Anyways, all roms out right now have been made for the Verizon XT862.
dpwhitty11 said:
What, DarkDroid not good enough for you? :'(
Anyways, all roms out right now have been made for the Verizon XT862.
Click to expand...
Click to collapse
Being someone who doesn't enjoy flashing ROMs, I find it hard to tell which ROM does what but I thought I heard that Steel Droid and Monster were the oldest ones which made me assume they are more consistently stable.
poetryrocksalot said:
Being someone who doesn't enjoy flashing ROMs, I find it hard to tell which ROM does what but I thought I heard that Steel Droid and Monster were the oldest ones which made me assume they are more consistently stable.
Click to expand...
Click to collapse
Right now they're all equally consistent and reliable. Mine just hasn't been out as long, so less people are running it, but hopefully that'll change soon.
Sent from my DROID3 using XDA App
Lol I meant no disrespect. Although I know they have a decent user base, I have not tried dark droid, narcotics, or the other chinese rom (or whatever it is
Sent from my DROID3 using XDA App
Anyone else have problems with contacts forceclosing?
Sent from my DROID3 using XDA App
Ever since I flashed SteelDroid 3.0, the market app won't let me make purchases. I tried flashing Market 3.2, 3.0.26, and 3.1.something, and I tried the Root Explorer replace Vending and uninstall update method and nothing seems to work.
Not sure if its the ROM or something else, but very frustrating.
I'm having the same market problem with Monster, I brought it up in the Roms thread, hopefully it will be fixed in the next update
sent from my MONSTERDroid3 from the XDA app
i think you just need to wipe data/cache to get your market to work.
Yes wiping data and cache will fix the market purchases
Sent from my DROID3 using Tapatalk
Flashing with bootstrap Droid 3
I went in to the recovery mode of bootstrap and then went to safe mode to install zip from sd card and i got it to install. Although when I reboot in safe mode nothing starts and when i boot in regular mode it seems exactly the same? I was trying to get the monster rom on 1.2 need help am i missing a step>? I followed the instruction and i did not notice that i had done anything different.........
No issues with darkdroid or steeldroid 3 from what i've found with my own slight notification mods for both, not had any market buying issues with either, flush the cash of the app or reinstall the market, failing that reinstall your roms from scratch.
-smc
I am new to LG Revolution (trying to install custom ROM on sister's phone). I am coming from 2 different Samsung devices.
I have VZ6, 2.2.2, rooted. Windows 7 64
Here are my questions:
1) Thread http://forum.xda-developers.com/showthread.php?t=1121952
CWM download link gave me a "recovery-cwm-pr1.tar.gz", so I extracted it with 7-zip and get a "recovery-cwm-pr1.tar". How do I get the .img file??
2) What exactly is ADB shell? Where do I find instruction on that?
I assumed installation of Revolt 1.5 is straight forward after I get CWM on the phone. I am just having a hard time to follow those instructions on CWM tho.
Heya,
I'm no professional at all of this, but I'd recommend downloading the revotoolkit. i;ve not used it on vz6, but that is how most of us went about getting cwm. believe there is a thread about it in development (http://forum.xda-developers.com/showthread.php?t=1144951).
hope that helps you
I would get the GB update. Then root with using the post in development by mtmichealson. Then flash Gingervolt.
is the Gingervolt mature?? this is my sister's phone, so I am not going to flash it every week when there is a patch or update... I highly doubt my sister (technologically challenged) will appreciate Gingerbread anyways.
Gingervolt was just released so there will be more releases soon.
If she wouldn't appreciate it just get stock gingerbread on and leave it at that
Edit: not to take anything away from any the developers here don't take it that way please.
Sent from my VS910 4G using Tapatalk
pendragon11 said:
Heya,
I'm no professional at all of this, but I'd recommend downloading the revotoolkit. i;ve not used it on vz6, but that is how most of us went about getting cwm. believe there is a thread about it in development (http://forum.xda-developers.com/showthread.php?t=1144951).
hope that helps you
Click to expand...
Click to collapse
Thanks for the tip. Installed without sweat.
Nice to see people are still working on new ROM on this phone. All devs on Droid Charge have moved to Bionic and left us in the cold.
droidfever said:
Nice to see people are still working on new ROM on this phone. All devs on Droid Charge have moved to Bionic and left us in the cold.
Click to expand...
Click to collapse
That's gay
Haro912 said:
That's gay
Click to expand...
Click to collapse
Thankfully we have dedicated people here, who get excited about the little breakthroughs on this phone. The phone is great, the hardware is fast and responsive, the programming (from what I hear) is a disaster. All the Roms I have tested have been stableish on this phone, a couple force closes here and there, but nothing too intrusive. Gingerbread is perfect, and the Gingervolt from Mtmichaelson is stellar, no hangups, no force closes yet. I would expect themes to roll out soon, and some more stable Roms. I would assume the dream of CM7 is on the horizon now.
In agreement with Haro's comment, you will find that we will not simply give up on this phone, we have been through too much.
No worries, glad I could help. Props to thecubed for that one of course
Sent from my VS910 4G (pimp it) using XDA App
Hey All,
Soooo this is my first Motorola Android device and I have to say I'm quite excited, but nervous. Just recently I was using Verizon's thunderbolt, and I've always used HTC. Well, after my 2nd thunderbolt, it crapped out on me again. So, I complained to Verizon and in return they sent me a Bionic. After reading reviews I hear nothing but great things.
Now my issue, I don't know what to do. Usually with my HTC devices, I root and flash roms, enough said. But with this Bionic I dont know where to begin. Some folks say install the ICS .232 build (which not sure how to do) and some folks say root and flash a ROM on. (Also, not sure what all this safestrap/bootstrap stuff is)
In all honesty, I really want a newer android OS. I think I was using gingerbread with my Tbolt, and I know ICS is out now, and Jellybean.
My main concern in what I want, and I hope someone can direct me to the correct place. I really want a fast, stable, build/ROM. I would like for everything to work as far as apps, gps, bluetooth, camera, etc.
I really appreciate all who respond, and I apologize greatly in advance if this is a repost. I tried researching before posting.
Again, huge thanks to all who respond.
Follow this guide to get on the an ICS leak. Personally I would strongly recommend not going beyond the .232 ICS leak for now.
Follow this thread to get rooted.
Here's a link to everything you need to know about the bionic. http://www.droidrzr.com/index.php/t...tstrapall-download-links-in-op-updated-daily/.
Sent from my XT875 using xda app-developers app
Hey...
Thanks the responses. I'm just confused. Everyone is saying to put on the.232 build, but can I put a Rom over top of that? If so, what Rom do you recommend and why?
Is .232 stable? Any known issues?
shockaholick said:
Hey...
Thanks the responses. I'm just confused. Everyone is saying to put on the.232 build, but can I put a Rom over top of that? If so, what Rom do you recommend and why?
Is .232 stable? Any known issues?
Click to expand...
Click to collapse
Yes you need to install the .232 leak in stock recovery. Then you need to root it and install safestrap, which is a recovery in which you can flash things. Once you have that installed, you need to boot into safestrap and make a backup of the nonsafe side. Safestrap works by partioning your system into a safe and nonsafe side. You are able to flash stuff on your safe side. So you need to toggle to your safe side and then you can flash a rom. I recommend http://forum.xda-developers.com/showthread.php?p=32349741#post32349741 but thats just me haha, theres a ton of other info in the different sections here http://www.droidrzr.com/index.php/forum/68-droid-bionic/
Hey All,
I have my Droid 3, and its been great to me. Its my first smartphone and first android phone, and it will always have that place in my heart That being said, not getting ics was a letdown from Motorola and sparked my interest in rooting for awhile now. I had always been cautious as I would not want to void my warranty and then brick my device, as that is simply my luck, lol. I was fortunate in that when my device broke due to an abnormal defect (Scoured the forums, never found anything and Motorola support had no idea, immediately shipped me a new device haha) it got replaced this past summer, but now my warranty expired in October and I'm noticing the lag more and more. SO.... I have been looking into the process specific to the droid 3, and I have found bits and pieces, such as using motofail now for the latest ota and what not. But is there a specific, comprehensive how-to guide towards doing so, that is current? I've found threads and get excited, only to see a comment saying "x" is outdated use this instead blah blah blah. I was fine with this, as its an outdated device and all, until noticing such exists for the kindle fire (Girlfriend was open to possibly rooting it as well, have been looking into that too. but that's another story ) I'd post the link, but alas, I'm a noob and do not have the ability to.
I know I am just being paranoid, or just terrible at searching the forum lol. But if a super guide like this exists, I would feel so much more comfortable in proceeding with rooting.
Nor sure about a guide but here's what I did
1) Root device using motofail http://forum.xda-developers.com/showthread.php?t=1497690
2) Install Safestrap http://blog.hash-of-codes.com/how-to-safestrap/
3) Create an additional ROM slot
4) Dowonload the ROM of your choice. This might be a good place to start http://androidforums.com/droid-3-all-things-root/494721-rom-current-droid-3-rom-list.html
5) Activate the blank rom slot and flash the rom
6) reboot and you're up
Good writeup. Also I would suggest you stick with something stock based. Minimoto is very nice and has excellent battery life. JB is still alpha and takes a bit of tweaking to get it stable.
some videos
How to Video's Root, safe strap, kexec, and much more
How to install and use safe strap 3.05 on the droid 3 for true multi booting on ROMs
http://youtu.be/q-qK7kL0W3o
roms to look at
Steel Droid GB 4.5
Steel Droid ICS 5.6
Thanks everyone for the links and videos, rooting the phone today!
I'm looking for verification from the op that he used these videos and links successfully to gain root and install a ROM?
I am very android oriented.... just never played with a D3. GF's stock D3 is running, well, sucky stock. And she asked me to fix it for her. I was going to request something similar as far as a flashing guide so I could get it all set in one night
Thanks to those for posting the links and resources
Sent from my Galaxy Nexus using xda premium
Sorry this is extremely late, I must have not subbed to the thread, stumbled upon it when cleaning my bookmarks haha. Yes, I used these and I've been on minimoto since. No obstacles or anything, was pretty easy just updating my rom today actually, and fell back on them as well. I figure you already went ahead, but figured I'd finally respond nonetheless
Confused Noob.
Hello I just recently ordered my DROID 3 from Ebay (can't wait to get it). Now I know that there are two roms which are the CM 9 and CM 10 and they work with ICS and JB respectively. Also there are variations with KEXEC and stuff like AOKP now this is getting confusing for me. I have never owned an Android my whole life I have been a Linux user. So are the alpha builds of CM9 and 10 working properly? As in can you make calls, use the play store and download apps on both? Which one should I use? I could not care less about cameras. I am not the picture taking type. Advice please. Make a room in your heart for this Noob. Thank YOU!
cm10 is very usable, imo, but that is really up to you
I'm using AOKP JB, which is like CM10
use safestrap 3 for d3, you can install 4 roms and switch between reboots
---------- Post added at 10:55 PM ---------- Previous post was at 10:52 PM ----------
fyi
AvRS said:
Best/most stable ROM threads aren't allowed as they're too subjective, you'll receive lots of differing opinions on the same thing. Only way is to try yourself and find the one that fits you best as that's what these forums are about.!
Click to expand...
Click to collapse
Hey Thanks.
sd_shadow said:
cm10 is very usable, imo, but that is really up to you
I'm using AOKP JB, which is like CM10
use safestrap 3 for d3, you can install 4 roms and switch between reboots
---------- Post added at 10:55 PM ---------- Previous post was at 10:52 PM ----------
fyi
Click to expand...
Click to collapse
Thanks for the reply, so what are the latest versions of AOKP JB and CM10? Safestrap seems very useful. I agree with you better to install both and check which one is more useful.
http://goo.im/devs/hashcode/solana/
Sent from my XT862 using xda premium
Super
sd_shadow said:
hXXp://goo.im/devs/hashcode/solana/[/URL]
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
You Rock!