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..
Now available for Alpha testing! http://goo.im/devs/Hashcode/jflteatt-active
This is Still Alpha! Be very careful! Have both a complete Nandroid backup as well as a full backup of the internal SD Card!
Read the threads below for more information.
Threads:
Normal ATT S4
Normal VZW S4
Active ATT S4
User @my-blue-snog-box Provided kernel modules:
MF1
MF2
MF3 is in the above thread links.
-- History --
SafeStrap is a method of booting custom ROMs on the Droid Razr line of phones (which have a locked bootloader) by hijacking one of the system processes during the boot process. SafeStrap Official Thread
Testing a few things out, the binaries seem to work upon initial inspection, but since the Graphics driver is wrong (and I'm going to assume the touchscreen input itself as well), I'm not willing to attempt it yet as I don't have any kind of way to recover from a soft brick.
See my ventures Here and Here
Now, I don't really know much how this works other than that which I have already described. I feel that once a custom Rom compatible with the International version is ready, we may just be able to get this ported over and working on our jailed phones...
Thoughts?
http://forum.xda-developers.com/showthread.php?t=2428226.
I am hoping that @Hashcode will be willing to help with making it work for the Active.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
thnx
thank you my brother
my-blue-snog-box said:
http://forum.xda-developers.com/showthread.php?t=2428226.
I am hoping that @Hashcode will be willing to help with making it work for the Active.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Click to expand...
Click to collapse
I have PM hashcode and told him that if he needs a loaner device that I would send mine.
Sent from my SAMSUNG-SGH-I537
my-blue-snog-box said:
http://forum.xda-developers.com/showthread.php?t=2428226.
I am hoping that @Hashcode will be willing to help with making it work for the Active.
Click to expand...
Click to collapse
How did I miss this? :silly:
Theoretically, if it works for the normal S4, we should be able to just drop the new display drivers and run. Of course, if not having a display during recovery is fine, it sounds like we might be able to test it now?
Tsaukpaetra said:
How did I miss this? :silly:
Theoretically, if it works for the normal S4, we should be able to just drop the new display drivers and run. Of course, if not having a display during recovery is fine, it sounds like we might be able to test it now?
Click to expand...
Click to collapse
Actually I can confirm that SS B08 boots into recovery just fine (he is going to make a modified version for us with proper build.prop config).
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
my-blue-snog-box said:
Actually I can confirm that SS B08 boots into recovery just fine (he is going to make a modified version for us with proper build.prop config).
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Click to expand...
Click to collapse
Sweet! (runs off to test)
Even if there are NO Roms yet, it's still nifty!
Yeah, but for whatever reason "/" isn't mounting. @thatbigmoose notified Hashcode.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
my-blue-snog-box said:
Yeah, but for whatever reason "/" isn't mounting.
Click to expand...
Click to collapse
Interesting, for me it's /ss and /datamedia that aren't mounting, something about not having mmcblk0pt29-orig
On the chat now for a little while #safestrap on freenode.
Ok, so Hashcode just posted a Safestrap for the GS4A I537 (the AT&T variant many of us have) and I'm very interested in doing some testing and experimentation but, for all the ROM swaps and stuff I've done over the past decade, this strapping thing has me somewhat baffled to some degrees.
I get that I can install it, that I can use "virtual" slots for ROMs using the internal storage (iirc, or ext SD, gotta learn this stuff) and be able to run 1, 2, or even 3 ROMs on the same device (not at the same time, obviously, but chosen during the boot process).
So here's the bazillion dollar question: does this Safestrap method mean that we as GS4A I537 owners now can potentially load up the ROMs being developed for the I9295 which is the International version of the GS4A ?
Just that one question and an answer would be greatly appreciated at this point, and then I'll go from there. Apparently there's only the one ROM being developed right now (the CM10.2 one) which is fine by me, would love to check that out on the GS4A and see how it works out, but since I'm pretty much scared stiff of damaging or bricking this GS4A of mine at this point I'm just going to be (a bit more) patient instead of jumping in with both feet, figuratively speaking.
Thanks for any input...
Testing!!!!!!!
OMG!!!
I am so HAPPPY!!!!!!!
I also go today note 3 dump and also safestrap!
Edit: installed recovery!
Edit: WORKS! Booted!
Well I took the leap of faith and installed Safestrap, went as expected, so now I'm itching to put this new "feature" to some good use. No issues with the install or accessing it, so good so far.
I need a .zip of the stock GS4A I537 kernel modules for the MF3 build please.
After flashing almost any ROM you will need to flash the kernel module .zip to keep the kernel modules inline with the stock kernel. This should help keep the lkmauth error's at bay (any module which does not meet the signature requirements will be rejected).
If you can explain how to get those files, I'd be happy to provide them since I'm gonna be up all night experimenting now.
Best way is to use adb
adb pull /system/lib/modules
(While booted up on the stock slot)
Hashcode said:
I need a .zip of the stock GS4A I537 kernel modules for the MF3 build please.
After flashing almost any ROM you will need to flash the kernel module .zip to keep the kernel modules inline with the stock kernel. This should help keep the lkmauth error's at bay (any module which does not meet the signature requirements will be rejected).
Click to expand...
Click to collapse
I'm on MF1; would that help at all? I successfully loaded and booted this: http://forum.xda-developers.com/showthread.php?t=240617 and I'd love to get wifi working.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Problem
I have trouble booting back into system.
Guys, I'm stoked about this, but I'm going to bed. @Hashcode if you can't get anyone to do that adb pull and MF1 will do, tag me and I can do it tomorrow.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
I've got the "[AOSP][Port]★I9295★ Official 4.2.2 - S4 Google Edition - Feel the Experience of Nexus" ROM installed in slot 1 and it's working up to a point; the Wi-Fi won't stay enabled (not sure why but as stated I'm new to this Safestrap thing and of course it's a port, and we're doing this haphazardly, bleh bleh bleh). Funny thing is that it's connecting with HSPA:15 whereas the stock ROM only gets me HSPA:11 so, it's definitely faster on the data connection (luckily I have 4GB left I suppose).
I'm going to assume - shame on me - that the Wi-Fi module is one that would be affected by the kernel modules issue you mentioned, Hashcode, so I'm working on getting them now (installing Android Studio now).
<insert minutes here learning how to use adb pull and directing the output to a folder>
Ok, here ya go... kernel modules from a stock I537 running 4.2.2:
this is so pretty damn awesome
The whole time i can't decide if i get the S4A or the Xperia Z - now i know which im gonna take and hope, that SafeStrap will find its way to the normal S4A
Regards
Seelbreaker
Hi All,
My Moto X (1st Gen) is about 4 months old. I'm contemplating on rooting the phone. Is it worth the effort or should I patiently wait for the Lollipop update to come in (whenever that is!). I used a lot of custom roms in my old Nexus 4, so missing the excitement of a new rom. just a bit indecisive at the moment. Would love your opinions on this.
arjun2058 said:
Hi All,
My Moto X (1st Gen) is about 4 months old. I'm contemplating on rooting the phone. Is it worth the effort or should I patiently wait for the Lollipop update to come in (whenever that is!). I used a lot of custom roms in my old Nexus 4, so missing the excitement of a new rom. just a bit indecisive at the moment. Would love your opinions on this.
Click to expand...
Click to collapse
I am using the Moto X for nealry 9 months now. Never thought of rooting it as I didnt find any bloat here like the Touchwiz
I am honestly very tempted by the ROMs out there. And I don't know why but I'm definitely noticing some performance lag. Tried everything but not seeing a lot of improvement.
Sent from my Moto X using XDA Free mobile app
Before you go contemplating this question, figure out if you'll be able to root your phone in the first place.
Then instead of asking this question, ask whether or not you should unlock the bootloader. It's the only way to maintain root since 4.4.4 patched the vulnerabilities used to attain root.
There are reasons why I would root like Tasker(full functionality),a custom kernel or UI changes
I rooted my X so I can play with gravity box and other stuff. Unrooting and relocking the bootloader isn't hard to do and that's what I'll do once Lollipop comes out for my phone. (Already factory reset my phone once from custom Rom).
TheBoiledDogs said:
I rooted my X so I can play with gravity box and other stuff. Unrooting and relocking the bootloader isn't hard to do and that's what I'll do once Lollipop comes out for my phone. (Already factory reset my phone once from custom Rom).
Click to expand...
Click to collapse
You are going to re lock your bootloader to take Lollipop?
Travisdroidx2 said:
You are going to re lock your bootloader to take Lollipop?
Click to expand...
Click to collapse
I meant to say return to stock recovery. I read somewhere that you can't get OTA with a custom recovery, Rom and rooted.
TheBoiledDogs said:
I meant to say return to stock recovery. I read somewhere that you can't get OTA with a custom recovery, Rom and rooted.
Click to expand...
Click to collapse
Gotcha, that is true. Stock recovery and stock system and you are good to go.
I personally root all my devices for better control. However, I personally don't use Roms because I want a stock experience and that includes boot animation and themes. The only Roms I have ever kept on my phones were ARHD and Paranoid Android. If neither are available, I go with Xposed.
I have a non dev Moto X from Verizon (XT1060, first gen). It is currently running 4.4.4. What is the most I can do with it? Reading several threads, I am unable to find a conclusive answer regarding this. Looks like sunshine doesn't work nor do most one click tools. My goal is to flash a debloated ROM at the very least if possible.
You won't be able to flash any custom rom without an unlocked bootloader and that's that really. At most you could root(when possible) and manually uninstall bloatwares from the stock rom. I'm glad I had troubles upgrading my phone initially and was able to read about sunshine app on time.
Sent from my XT1060
to the moon and back at least, of course try krypton, or maybe even the modded 5.1 for the 1060, I prefer krypton but the modded 5.1 came a long way quickly I just wasn't feeling the change from simplicity (less options but works perfect for me) of Moto Assist, to the more complex options in LP :/ Check out the respect threads for each rom!
Safestrap only works for 4.4.2 no?