** ATTN DEVS **
Not sure if alot of people know about this but i wanted to share and help get the word out there, because i will affect our D4 as well. And the more people that know about it, the better.
kholk has got a custom kernal booting on his RAZR. As we all know the RAZR has a locked bootloader. check out the links to the original threads.
AS OF NOW THIS IS ON THE ETERNITY THREAD
What do we have today?
Kexec. After working with a really good developer, [mbm], finally this has become real.
Linux boots Linux. No signature checks.
Yeah, this is the beginning of custom kernels
Oh, remember that this is still a WORK IN PROGRESS!
Known issues (to be solved):
- CPU1 doesn't come up.
ToDo:
- Fix CPU1
Disclaimer:
The EternityProject isn't responsible of anything you do on your device: if it explodes and kills you, or if it comes to life and becomes something like Terminator, it's YOUR OWN RESPONSIBILITY.
LINK TO TOPIC IN
XDA
THREAD AT
ETERNITY PROJECT
BIG THANKS TO KHOLK, [MBM], ZEIDOF, AND ALL THE MEMBERS OF THE ETERNITY PROJECT TEAM WHO HELPED WITH THIS.
Sounds promising!
Sent from my DROID4 using XDA
this looks great, i hope this can be ported over to the Droid 4 no problem, in your face Motorola! you make great phones, but your bootloader policy sucks
About damn time! I had lost hope in any further development for our phones
Sent from my ICS flavored DROID4
I had decided I would try it on my phone as-is. When I run the script I get what appears to be syntax errors or something.
Code:
bypassme.sh[12]: /system/bypassme/physicalmem: No such file or directory
bypassme.sh[16]: ./kexec: No such file or directory
Hopefully we will get a version compatible with our phones and CM9 soon. I'd like to see something like the 2nd-init exploit that can do it early in the boot process.
From what's been said I think it only works with stock rom. Any custom rom would have to be ported to it. And for the d4 as well
Edit: did you run as su
*** Sent from OCd ICS D4 ***
I modified the bypassme.sh script to
Code:
insmod /system/bypassme/atags.ko
cat /system/bypassme/atags3 > /proc/atags
cat /system/bypassme/physicalmem 0x4A314048 w 0x4444AAAA
cat /system/bypassme/physicalmem 0x4A314048 w 0x44445555
insmod /system/bypassme/functions.ko
insmod /system/bypassme/userspace.ko
cd /system/bypassme/
sh kexec -l zImage --devtree=devtree3 --ramdisk=ramdisk.gz
sleep 10
sh kexec -e
and it runs and displays some funky text but doesn't seem to actually do anything. But is it the same error the CDMA Razr gets or something else?
so does it mean also droid 4 can be used with gsm ?
fatihx said:
so does it mean also droid 4 can be used with gsm ?
Click to expand...
Click to collapse
Yes, but that's old news and the tool that's supposed to allow it is just another thing Motorola has promised to release at some point in the future.
I'm going to show my total stupidity here and ask a very basic question.
If we already have root, custom ROMs and recovery, what does the custom kernel allow you to do?
Sorry for bringing it down to the lowest level and thanks for your patience.
it lets you flash custom kernels (to overclock, underclock, change voltage levels), it also let's you flash custom radios for better reception
Even a safestrap rom remains running off of the Motorola kernel. If we can run our own kernel, we can hack deeper into the device, compile our own drivers, and actually update the kernel itself to the latest one from AOSP. For example, right now we are running Android 4 using a kernel from Android 2.3, kexec would allow us to update that.
Sent from my DROID4 using XDA
as fare as i understand this should let us unlock GSM on the phone for use in Europe
or am i mistaken?
if i am not then how long do you think until we see GSM working?
edit
sorry it was late when i posted that and thought this was something to do with the baseband not bootloader
niai_mack said:
as fare as i understand this should let us unlock GSM on the phone for use in Europe
or am i mistaken?
if i am not then how long do you think until we see GSM working?
Click to expand...
Click to collapse
Someone in the general section under the Droid 4 for Hong Konger claims to have one for GSM enabled.
Sent from my DROID4 using Carrier Pigeons
Kernel?
Sent from my XT910 using xda premium
Possible dumb question. If there is only one sim card slot in this phone that Moto uses for authentification, where would the GSM sim card go?
Apologize if this is a stupid question.
LTE operates on a GSM band erm... gsm standard. (The LTE sim card, I believe is just that... a sim card)
Sent from my DROID4 using XDA
So if a custom kernel can unlock the phone, how would that work with Verizon?
I believe you just flash a radio that corresponds to verizon's specific spectrum vs some other carrier's spectrum like, say, at&t.
Sent from my DROID4 using XDA
This doesn't unlock the phone. It boots stock kernal, then boots a custom kernal on top of it
*** Sent from OCd ICS D4 ***
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 just made some boot.img files for International Android 2.3.4 users. It is tested for d00, but I don't see any reason it won't work fro 1100 users. It uses the same exact kernel image I had before for AT&T users. Everything seems to work without having to replace modules.
It includes SetCPU support. It is only a 1.1ghz overclock. It is still 1ghz by default, you have to use SetCPU to trigger the overclocking.
You phone needs to be in fastboot mode to flash the boot.img. To do this follow the steps below.
Steps:
1. Power off phone
2. Hold volume down
3. Plug USB cable into computer
4. Plug USB cable into phone
5. Wait for it to say Fastboot at the top of the phone's screen
6. Press Volume Up to select Fastboot
7.
d00:
On computer run, moto-fastboot flash boot boot-d00.img
1100:
On computer run, moto-fastboot flash boot boot-1100.img
Downloads:
d00:
boot-d00.img
1100:
boot-1100.img
This is still based on faux123's and kholk's work.
Thanks faux123!
Thanks kholk!
Thanks Mossys!
Great work, man!
I'll flash this and let everyone know how it goes. Homies with d00 tegra parts weren't having muck luck with faux123's recent releases.
Any other tweaks or optimizations? If not, I'm still feeling blessed to have OC soon!
I was having CPU temperatures above 150 f on faux123. Edgan's kernel seems much more
"cool". Looking forward to undervolting.
Testing atm. Everything seems alright, and i still the ram fix (i've lost it when i flashed faux's kernel :/)
Hi,
Tested with Bell GB firmware.
2100 quadrant at 1100Mhz first run, then 2900 second run. Whatever that is worth.
Cheers!
working on orange uk atrix, with kens 4.5 rom, overclocked to 11000, everything working.
Working on Bell Atrix with Orange FR 2.3.4 ROM
You compiled the wrong kernel bud. We have no wifi.
Sent from my Atrix 4g @ 2.3.4 Orange FR
nexxusty said:
You compiled the wrong kernel bud. We have no wifi.
Sent from my Atrix 4g @ 2.3.4 Orange FR
Click to expand...
Click to collapse
could that be because your applying a kernel based off of gingerbread to a froyo build?
Nope. Orange 2.3.4.
What I meant by he compiled the wrong kernel is, no 1 uses the AT&T GB build on international devices. Orange FR is far superior. Wifi doesn't work on international devices when using an AT&T kernel tho. Why he would base his international kernel on an American one is beyond me....
There was a kernel out on Friday that functioned the same. No idea why this was released.
Sent from my Atrix 4g @ 2.3.4 Orange FR
nexxusty said:
Nope. Orange 2.3.4.
What I meant by he compiled the wrong kernel is, no 1 uses the AT&T GB build on international devices. Orange FR is far superior. Wifi doesn't work on international devices when using an AT&T kernel tho. Why he would base his international kernel on an American one is beyond me....
Sent from my Atrix 4g @ 2.3.4 Orange FR
Click to expand...
Click to collapse
I am curious about your statement regarding ORANGE GB >>>> ATT GB? In what ways is the Orange version superior... Just want to know since I haven't loaded the Orange version myself.
Thanks.
faux123 said:
I am curious about your statement regarding ORANGE GB >>>> ATT GB? In what ways is the Orange version superior... Just want to know since I haven't loaded the Orange version myself.
Thanks.
Click to expand...
Click to collapse
I think he just means that the Orange Build works better with the slight HW changes that have come apparent in the International Versions, not that the code is any better on that build.
Fixes battery issues with faux kernel and everything works flawlessly and smooth. Thanks!
Running nice and smoothly for me. Going to calibrate my battery and test it out.
Cheers!
It is much faster. Especially the UI. Leaps and bounds.
Sent from my Atrix 4g @ 2.3.4 Orange FR
I dont see that much difference if any. I using kens rom with this kernel on my uk ATRIX. At least with AT&T versions you can theme it. There isn't any yet for orange.
Sent from my MB860 using XDA Premium App
Bah, had to flash my device RIGHT before work so I've lost this.
Is there any way it can be made into a CWM flashable .zip?
I dont quite get it... does it work with international Atrix causing wifi problems or not?
Viamonte said:
I dont quite get it... does it work with international Atrix causing wifi problems or not?
Click to expand...
Click to collapse
No problems.
Can this be flashed from terminal?
Su
Fastboot flash boot boot.img?
Thanks
Swyped from 'mount' Olympus
Edit: No you can't, fastboot not recognised.
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..
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.
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