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 know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
As it stands, the OTA will look for GB 219 when upgrading so those early adopters won't be able to get future upgrades. Unless devs find a way to downgrade or trick the update that is.
Everything I've said could be wrong however this is how I have come to understand it.
Sent from my DROID4 using XDA
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
azrael293 said:
Given that we have the fastboot files can't we just wipe and flash that to downgrade?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
No, this results in a brick. Fastboot refuses to flash older partitions over new ones.
Sent from my XT894 using xda premium
flamefangahs said:
The kernel is based on GB because of the locked bootloader. At least that's how I am to understand it. In other words I think that the custom ROMs can be improved using the leaked ROMs but they'll still have to remain based on the GB kernel. Unless you update your stock system to ICS that is. I think the biggest thing devs should focus on right now is a way to safely upgrade to ICS where downgrading is possible in order to stay on Verizons official upgrade path.
Click to expand...
Click to collapse
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
highlandsun said:
This is why you need kexec - you can load the ICS kernel dynamically, without corrupting your GB install.
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
Actually, upgrading to ICS leak is probably the way to go. We can now upgrade from leak 200 to 206, giving us the ability to stay on the upgrade path. Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Here are the instructions for upgrading from leak 200 to 206:
http://www.droidforums.net/forum/droid-4-roms/209619-get-unstuck-ics-leak-200-aka-upgrading-200-206-instructions.html
Also, I believe Hashcode is working on bringing Safestrap 2.0 to the new ICS leak based on the new kernel, and will be working on getting our ROMs on the new kernel as well.
rumgool said:
Since the XDA forums are dead for the Droid 4, I suggest everyone keep up at droidforums.
Click to expand...
Click to collapse
droidforums is about as dead for the Droid 4 as is XDA. I am really surprised how little interest people have in this phone. I guess I am one of the few that still loves physical keyboards. Only drawback on this phone is the non-removable battery. Otherwise it is rock solid. Had the original Tilt, then TP and TP2. Had the G2 on T-mobile, but reception on that phone was not good and T-mobile Network in the US sucks.
GermanGuy said:
droidforums is about as dead for the Droid 4 as is XDA.
Click to expand...
Click to collapse
This is true, I was just mentioning since most of the recent information regarding the ICS leak has been on droidforums so checking it out would fill everyone in on whats going on. Because basically development for the GB kernel is probably going to come to a halt and future development will be based on the new ICS kernel, including the existing AOSP ROMs.
wait, the 206 version keeps you on the upgrade path?
dewhashish said:
wait, the 206 version keeps you on the upgrade path?
Click to expand...
Click to collapse
No, but 206 was supposed to require 219 as 200 did and the official one will and people have found ways around it.
Sent from my XT894 using xda premium
I have Hashcode's stuff running on my kindle fire. We will all be in for a treat once he starts focusing on D4. He's done really really good work on the kindle.
dewhashish said:
I know there were 2 leaks of ICS for the phone, but has anyone been able to update the ICS ROMs in the threads to use the new kernel and radios? There's still some data issues and we're using a GB kernel
EDIT: i meant leaks, stupid typo
Click to expand...
Click to collapse
They won't be able to do so. What they will be able to do is make their builds work off/with the new kernel/radios flashed by the leak.
So Hashcode will have two builds.
1) - works on phones running the current stock GB kernel.
2) - works on phones running the leaked ICS kernel.
There is still a locked bootloader so you can't flash unsigned kernels/boot.img. For the leaked "system" files to help you need the ICS kernel. The only way to get the ICS kernel is to flash the leak.
So the leaks are great news for people wanting an AOKP or CM9 build running fully functional....on their leak installed phones. Not much help for those who do not want to flash the leak.
I'll definitely flash the leak once root has been released for 4.0.4 (in case OTA rootkeeper doesn't work) and hashcode releases safestrap 2.0 for the leak.
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
So far it's working great, face unlock and the camera is working perfectly and GSM/WDCMA performance is awesome, I don't seem to have the problem of under-reported GSM signal like in the stock MotoBlur leak.
(Note that I'm in Canada and using Bell Mobility, not in the US on Verizon so I can't say if LTE is functioning properly).
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
Won't be long before Hashcode puts up an official release, but I definitely recommend trying it out if you're up for it. If Hashcode doesn't mind, I could share a .zip of the build I made if anyone out there is interested.
Sent from my XT894 using xda premium
Rick#2 said:
I'm presently running Hashcode and the rest of the STS Dev Team's CM9 release with modifications for the ICS kernel leak on my D4 that has been flashed to the .206 leak; I just pulled their work from GitHub and compiled it myself with a few little tweaks.
Click to expand...
Click to collapse
Do you think you create a guide or go into more detail how you did this? I'm not quite sure what their git is.
Sent from my XT894 using xda premium
Rick#2 said:
...
I just flashed it with Safestrap v1.09 for the D4; a little tricky since the bootmenu doesn't accept the Menu/Search softkey input to allow you to enter Safestrap, so I had to boot in BP Tools mode to force loading up the Safestrap Recovery. I made some additional tweaks to the build.prop file as well but am really impressed.
...
Click to expand...
Click to collapse
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Hashcode said:
This is what I'm trying to fix right now. Seems like the menu/home/search/back buttons are handled as part of the touchscreen. So the new Safestrap has to handle looking for virtual buttons.
Sent from my Amazon Kindle Fire using Tapatalk 2
Click to expand...
Click to collapse
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
podspi said:
If you are making good headway, then disregard this. But you could use a scheme similar to FireFireFire for the er, Kindle Fire
Either use a physical button (a return to the old hold the X from the D1, perhaps?) or a few taps to the screen?
Click to expand...
Click to collapse
Right now, I'm treating the front buttons like they are a special portion of the touch screen (basically any touch past 960 pixels down is considered the "button row", and then I divided the width up into 4 spots for button presses: menu, home, back and search respectively. (This is in the recovery itself as well as the splashscreen which triggers off of menu)
If that fails, Ill just use hard keys for D4's Safestrap temporarily.
Sent from my DROID4 using Tapatalk 2
..or maybe the volume buttons (I bet it requires less modification than implementing support for the digitizer)
I just put up an updated Droid4 2.00 Safestrap for use w/ the new MotoICS leaks:
http://forum.xda-developers.com/showthread.php?t=1688610
BE SURE TO MAKE AN INITIAL BACKUP OF NON-SAFE SYSTEM BEFORE YOU DO ANYTHING.
You will use the "System" backup to restore back to stock .206 to update later.
I have the D4 CM9 / AOKP builds for the MotoICS leaks almost ready and I'll post those soon.
Hey Everyone, I have been pushing the ICS update away, kind of scared of all the bugs. But I'm wondering if theirs any decent Jelly Bean ROMS? With working Data (4G?) and Camera / Video?
I'm not expecting anything perfect, darn bootloader..
I don't think the bootloader is a concern at this point. A bunch of smart and dedicated developers have managed to get past that on the D3/D4/Bionic/RAZR. Now the difficulty is getting a kernel that works well. Anyway, to answer your question, no. It is a WIP ATM.
Yeah I don't really blame the bootloder, making a joke.
How can I download, learn more, keep track of the w.i.p.s? I know hashcode says stuff over twitter, which is probably keeping track of part. Though I don't understand twitter tweets replys.
And do I need to be on the new ICS update to flash them (with Safestrap 2?)
And whats a kexic build over a rom, or are they the same? differences? I know the kexic stuff is going pretty well.
TechTinker said:
Yeah I don't really blame the bootloder, making a joke.
How can I download, learn more, keep track of the w.i.p.s? I know hashcode says stuff over twitter, which is probably keeping track of part. Though I don't understand twitter tweets replys.
And do I need to be on the new ICS update to flash them (with Safestrap 2?)
And whats a kexic build over a rom, or are they the same? differences? I know the kexic stuff is going pretty well.
Click to expand...
Click to collapse
Hashcode's twitter feed is probably the best/only way to keep tabs on kexec right now.
You do need to be on stock ICS in order to use safestrap 2.11 which is needed to flash the newer ICS builds as well as the kexec builds.
Kexec refers to the kernel as opposed to the ROM. So you have ROMs right now that run off the stock phone kernel and you have kexec ROMs which run off the custom kexec kernel.
Droid 4 - AOKP Skyline
Hi All
I am not really a developer at all but I have had loads of experience messing around with ROMs to improve them (such as changing rils manually, using my own updater scripts, creating my own nvflash layouts and images, etc).
Recently I have been trying out CM10.1 again (mivvs ROM) on the new bootloader and also paranoid android. But both are too buggy for me and the battery life is really bad. So I am thinking to revert back to CM7 again.
I am planning to *TRY* and build my own CM7 rom from source using these fixes by Pengus (http://forum.xda-developers.com/showpost.php?p=35661482&postcount=100) to try and make it boot and run on the new bootloader. I know the advantages are very little but its just a "to see if I can" thing. It will also mean others wanting to go back to CM7 won't have to flash the old bootloader again.
I am planning just a one-time build as CM7 has pretty much reached completion.
I am posting this up to:
Make sure no-one else has already done it
Make sure one of the devs doesn't know of a reason this 100% will fail
To see if anyone else would be interested in such a ROM
To know if its possible to build from Windows (if I need Linux then so be it)
Let me know what you think
hy
I have mivvs rom and the battery life in not bad.
however, your idea is interesting .. good job!
Well, I think this is quite interesting. However, I am a big fan of PA10 and Pengus work... for me they beat GB in all aspects at the moment. However, one of the greatest pro's of having a CM7 on the new bootloader is the ability to have dual boot with CM7 + CM10.1 (or something else), since dual boot only works for roms with the same bootloader.
So far I have:
Set up Ubuntu x64 VirtualPC
Installed Android SDK and all Dependancies
Sync'd the CyanogenMod 7 Source
Sorted out the P990 Proprietary libs
Made MOST of the changes Pengus lists (although some bits are in different files)
It turns out the kernel source isn't downloaded automatically with CM7 so I need to find out how to build the kernel from source (in order to make the rest of the changes on the list Pengus made) but I think its looking good..
CM7 also doesn't have fstab.p990 but these lines can be found in init.p990.rc. Until I have the kernel source I am stuck on point 6
And I didn't mean to knock Pengus/TonyP/Mivv's work. They have helped this phone come a really long way especially now acree seems to have dropped support for it.
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
rlees85 said:
Just FYI
I tried this, making all the changes above, compiled the build.... but it doesn't boot.
Just gets stuck on the red lg logo.
I think the old CM kernel will not run on the new boot loader at all.
Was worth a try!
Click to expand...
Click to collapse
Maybe your last resort, try the excellent CM7 ETaNa kernel (link is in my signature).
But, I guess it won't work; kernels are bootloader specific.
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