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.
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..
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
I just bought this phone off a friend. still in very good condition and im happy with it.
It appears to be stock sony rom, with masses of bloat and clutter, and the battery usage is just average at best so im thinking i probably need a custom rom.
android 4.4.4
kernel 3.4.0
build .14.4.a.0.157
im not sure if bootloader is locked or unlocked.
I would like to get a better rom on this phone with less bloat and hopefully an improvement on battery life, can anyone advise whats best to do.
Thanks.
CyanogenMod is the most popular ROM
matalic said:
CyanogenMod is the most popular ROM
Click to expand...
Click to collapse
as I dont like tinkering with firmwares yet, after a few hours of research ive just rooted and flashed DstrikerZ1 Kai ROM 3.2 [BETA RELEASE][3-Dec-2014], fingers crossed it works ok. hopefully can flash lollipop at some stage
Hi,
I got the 1+3 since 3 days, and I must say that from the ROM point of view I quite happy with it ;
It is ...
1. Stable
2. Quick
3. Battery friendly
4. Enough customisation
5. Not Bloatware
Of course there is room for improvement in each points, I know, but ....
Usually I root for point 4. & 5. and I put Custom ROM for point 1. 2. & 3.
But this time, I´m not so hurry
Same here. I have rooted to solve memory management issue but dont really fancy putting a CM rom on it. Will wait until there is a stable oxygen rom I think
I will wait also. Hopefully more CM13 mods will come and improve performance in general.
I got it since 2 days and was very surprised on easy unlocking bootloader and rooting. ROM seems stable and quick enough. I assume that I will wait for an Android N port before I change to a custom ROM. Has someone an idea if there are already devs on the way to cook N-ROMs for different devices?
Same here, only rooted it for the memory fix, OOS have everything I want
I will for sure flash RR and Bliss Flashing Roms is why i bought this device.
andywright1982 said:
Same here. I have rooted to solve memory management issue but dont really fancy putting a CM rom on it. Will wait until there is a stable oxygen rom I think
Click to expand...
Click to collapse
I haven't even rooted - but I am quite happy with Oxygen 3, feel no great urge to customise or get CM etc installed. I really like it.
Does Android Pay still work on your device??
Thought I was the only one.
No intention of rooting at the moment.
Have a few apps for work that need a stock phone, plus banking apps etc.
But yep OOS3 seems to have everything with nova launcher.
Sent from my ONEPLUS A3003 using Tapatalk
Same here, OxygenOS is awesome so far, but I rooted for Xposed.
Those that have been flashing roms for 3+ years pretty much get tired of doing it and want all stock. New people get excited about flashing new roms and do it for 3+ years until they end up getting tired too
Valid points for staying on OOS, it's a good rom that has most all customizations I need and the rest I can get with xposed...
Thing is do you EVER plan on flashing a rom? My answer is of course so I decided to go ahead and decrypt (format data) now as opposed to later after I have all my music, etc loaded on.
Running Grarak's CM13 swimmingly.
brickedvice said:
Those that have been flashing roms for 3+ years pretty much get tired of doing it and want all stock. New people get excited about flashing new roms and do it for 3+ years until they end up getting tired too
Click to expand...
Click to collapse
Well in my case, I've been flashing rom's for 8 years. This is the first device I've not felt the need out of the box.
brickedvice said:
Those that have been flashing roms for 3+ years pretty much get tired of doing it and want all stock. New people get excited about flashing new roms and do it for 3+ years until they end up getting tired too
Click to expand...
Click to collapse
+1 here. I've been rooting phones for 5+ years as soon as I got them. But now, I'm wondering if I even need to bother.
Yeah, this is hard one. Thanks devs for quickly coming up with root, unlock, custom, and tweaks. Not sure if rooting is needed. I think we can all agree, if you want more out of the devices, you quickly root. For some reason, that's not necessary for one+3. I'm pretty sure we will get bored and devs will come out with super awesome Roms in the near future with many added tweaks. But this phone is solid. Might need a month's of stock rom usage and more arising issues before I will jump to rooting. Great device no complaints..
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Yes also for me. Great Rom and the first time that I don't want to change the rom!
Gesendet von meinem SGP511 mit Tapatalk
I agree, I actually like this stock, I got pretty much everything I need, iI will just miss flashing nightlies but I won't miss all the down time and missed text messages
Been flashing ROMs for 6 years now, always running cm, and I have been seriously considering given oos a few days before flashing, but also I'm to used to cm
I'm waiting for Multiboot/Dualboot patch...keeping Stock-Rom on first "partition" and Custom-ROM on second...