So many people have been wondering about this, so I thought I would try to bring it to life. I would like to get a port of CyanogenMod 7 going for the Atrix 2. I know it normally comes with a custom kernel, but is there any reason it won't run with our stock one? obviously we can't change it until we get our bootloader unlocked. I am not a super talented developer like some of you, but I am capable of doing a lot. Still I would greatly appreciate any help from others who would like to take part in this. As far as I am concerned, we should be able to get something working by taking a port for some device close to ours and modifying it slightly to work. we will have to replace the radio with our own, which we can do by just flashing the fxz files we have and we will not be able to use a custom kernel. Does this sound about right to people or am I missing something big. Will CM7 run on a stock kernel, or does it need something special? thanks for any help in advance, if you are interested in helping with this, please reply here or send me a PM, preferably post here so others can see what is going on, but if it is something you don't want to share, PM me. Also, what device(s) should We look at to try and port from? I would guess the Droid Bionic as it is very similar, the RAZR as I think it also has a locked bootloader, and the Droid 3 because cm9 ports from it will boot on our phone. Any others?
lkrasner said:
So many people have been wondering about this, so I thought I would try to bring it to life. I would like to get a port of CyanogenMod 7 going for the Atrix 2. I know it normally comes with a custom kernel, but is there any reason it won't run with our stock one? obviously we can't change it until we get our bootloader unlocked. I am not a super talented developer like some of you, but I am capable of doing a lot. Still I would greatly appreciate any help from others who would like to take part in this. As far as I am concerned, we should be able to get something working by taking a port for some device close to ours and modifying it slightly to work. we will have to replace the radio with our own, which we can do by just flashing the fxz files we have and we will not be able to use a custom kernel. Does this sound about right to people or am I missing something big. Will CM7 run on a stock kernel, or does it need something special? thanks for any help in advance, if you are interested in helping with this, please reply here or send me a PM, preferably post here so others can see what is going on, but if it is something you don't want to share, PM me. Also, what device(s) should We look at to try and port from? I would guess the Droid Bionic as it is very similar, the RAZR as I think it also has a locked bootloader, and the Droid 3 because cm9 ports from it will boot on our phone. Any others?
Click to expand...
Click to collapse
Last i knew jimbridgman was working on a port. I have a rough cm7 only running on one core and only using about 427mb of ram that was passed down to me from lfaber.he said its set on 2.3.5 so u need to have 2.3.5 before u install it however still doesnt seem to boot ..stays on moto logo for me.theres two different ports i have so maybe i just tried the wrong one but i last remember trying both and to no evail..stuck at boot. If i get the time and get to a wifi spot ill upload them so u can have a go at it if youd like. Right now i am busy with scv6 which is making progress btw. So ill let u know thru pm when i get them up for u to d/l.
Sent from my MB865 using XDA
rdavisct said:
Last i knew jimbridgman was working on a port. I have a rough cm7 only running on one core and only using about 427mb of ram that was passed down to me from lfaber.he said its set on 2.3.5 so u need to have 2.3.5 before u install it however still doesnt seem to boot ..stays on moto logo for me.theres two different ports i have so maybe i just tried the wrong one but i last remember trying both and to no evail..stuck at boot. If i get the time and get to a wifi spot ill upload them so u can have a go at it if youd like. Right now i am busy with scv6 which is making progress btw. So ill let u know thru pm when i get them up for u to d/l.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Thanks, I'm glad there is some work on this going. I did not really know what all the hype was about CM until I really used it for a bit in the last few days on a family members phone, which got me excited. Keep going with scv6, I can't wait to try that out as I was quite pleased with v5 as it got me started with roms for our phone (no pressure). why do you think it is not booting well? is it just because we have to optimize it for our kernel or something?
lkrasner said:
Thanks, I'm glad there is some work on this going. I did not really know what all the hype was about CM until I really used it for a bit in the last few days on a family members phone, which got me excited. Keep going with scv6, I can't wait to try that out as I was quite pleased with v5 as it got me started with roms for our phone (no pressure). why do you think it is not booting well? is it just because we have to optimize it for our kernel or something?
Click to expand...
Click to collapse
No.he said it boots. It just isnt for me. Maybe i wasnt supposed to wipe data.dont know ill find out tho.
Sent from my MB865 using XDA
rdavisct said:
No.he said it boots. It just isnt for me. Maybe i wasnt supposed to wipe data.dont know ill find out tho.
Sent from my MB865 using XDA
Click to expand...
Click to collapse
No problem, I will PM him and see if I can get some info. I just tried to flash one of the droid 3 ports I found for the hell of it. Naturally it did not work. would not even get past the boot logo to the animation, so I guess simple modification is out of the question for now! anyways, restoring back to normal for now until I can get some more info.
Im talkin with him now.ill let u know
Sent from my MB865 using XDA
rdavisct said:
Im talkin with him now.ill let u know
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Alright, thanks.
I don't know a thing of developing roms but i do know this, my fist phone was a nexus one, and the first custom rom i installed was the CM6 and if i remember well it was under the stock kernel, so i guess it should work with us too. It's my humble opinion
Not for nothing but isn't a CM7 port a waste of time when CM9 is only a few tweaks away from working? Why not focus completely on CM9 so we can get ICS on our phone?
Sent from my MB865 using Tapatalk
jfrank1485 said:
I don't know a thing of developing roms but i do know this, my fist phone was a nexus one, and the first custom rom i installed was the CM6 and if i remember well it was under the stock kernel, so i guess it should work with us too. It's my humble opinion
Click to expand...
Click to collapse
It will work without a custom kernel. You will have to strip it though... as all builds of CM7 come with a custom kernel. It's really just a matter of having everything in place and tweaking it to work with the stock Motorola kernel.
StrizzMatik said:
Not for nothing but isn't a CM7 port a waste of time when CM9 is only a few tweaks away from working? Why not focus completely on CM9 so we can get ICS on our phone?
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
good point, but cm9 is more than a few tweaks from working. the radio may never work until the ota for ics comes out, or we can pull one with cheesecake. either way it will be a few months. plus many people like GB better anyways, i prefer ICS, but i know some do not. things we learn from developing this could of course help us with other roms as well.
Sorry guys, but I don't get as much of a chance to get on here as often anymore, and its been about 6 or so weeks since I have pulled up XDA, I just have a ton of things on my plate right now.
Yes I had a bootable CM7, but it really does not work, the big issue is that ALL of the CM7 apps are tied to the kernel, and there is no kernel that has been built that is close enough to our hardware to just stick in there.
The ONLY way I have had a successful build was to compile a custom kernel and bypass the bootloader with kexec. There was an update to kexec a few weeks ago and I have lost the ability to bypass the bootloader on our phone since then.
My plan all along has been once I can get kexec working to release this version of CM7, but the issue is that it is all based on 2.3.5, and can't go forward, since 2.3.6 does not work well with CM7, no matter what i have tried.
I have just sort of let the cm7 no-kernel port die, and I am focusing on just kexec at the moment.
I have to keep my efforts underground right now, because I have been given a cease and desist letter from Moto, about my bypassing the kernel with kexec. They (Moto) do read this board, so I do advise you to be very careful what you decide to post on this site.
P.S. I have PM'd lkranser with this information, and I will PM him the link to the last no-kernel CM7 build, but it is worthless without the kernel, which is why I started the work on kexec. I have been the one person on here really focusing on cracking the boot loader since day one that this phone was out, and I have done it 3 different ways, but it is only a temp situation, until kexec is fully working on our phone, and I am working to resolve that.
Jim
jimbridgman said:
Sorry guys, but I don't get as much of a chance to get on here as often anymore, and its been about 6 or so weeks since I have pulled up XDA, I just have a ton of things on my plate right now.
Yes I had a bootable CM7, but it really does not work, the big issue is that ALL of the CM7 apps are tied to the kernel, and there is no kernel that has been built that is close enough to our hardware to just stick in there.
The ONLY way I have had a successful build was to compile a custom kernel and bypass the bootloader with kexec. There was an update to kexec a few weeks ago and I have lost the ability to bypass the bootloader on our phone since then.
My plan all along has been once I can get kexec working to release this version of CM7, but the issue is that it is all based on 2.3.5, and can't go forward, since 2.3.6 does not work well with CM7, no matter what i have tried.
I have just sort of let the cm7 no-kernel port die, and I am focusing on just kexec at the moment.
I have to keep my efforts underground right now, because I have been given a cease and desist letter from Moto, about my bypassing the kernel with kexec. They (Moto) do read this board, so I do advise you to be very careful what you decide to post on this site.
P.S. I have PM'd lkranser with this information, and I will PM him the link to the last no-kernel CM7 build, but it is worthless without the kernel, which is why I started the work on kexec. I have been the one person on here really focusing on cracking the boot loader since day one that this phone was out, and I have done it 3 different ways, but it is only a temp situation, until kexec is fully working on our phone, and I am working to resolve that.
Jim
Click to expand...
Click to collapse
Thanks, I will take a look at all that and see if I can get anything done. I can't believe Moto actually did that! Keep up the good work though.... I mean you should stop right now of course....
jimbridgman said:
Sorry guys, but I don't get as much of a chance to get on here as often anymore, and its been about 6 or so weeks since I have pulled up XDA, I just have a ton of things on my plate right now.
Yes I had a bootable CM7, but it really does not work, the big issue is that ALL of the CM7 apps are tied to the kernel, and there is no kernel that has been built that is close enough to our hardware to just stick in there.
The ONLY way I have had a successful build was to compile a custom kernel and bypass the bootloader with kexec. There was an update to kexec a few weeks ago and I have lost the ability to bypass the bootloader on our phone since then.
My plan all along has been once I can get kexec working to release this version of CM7, but the issue is that it is all based on 2.3.5, and can't go forward, since 2.3.6 does not work well with CM7, no matter what i have tried.
I have just sort of let the cm7 no-kernel port die, and I am focusing on just kexec at the moment.
I have to keep my efforts underground right now, because I have been given a cease and desist letter from Moto, about my bypassing the kernel with kexec. They (Moto) do read this board, so I do advise you to be very careful what you decide to post on this site.
P.S. I have PM'd lkranser with this information, and I will PM him the link to the last no-kernel CM7 build, but it is worthless without the kernel, which is why I started the work on kexec. I have been the one person on here really focusing on cracking the boot loader since day one that this phone was out, and I have done it 3 different ways, but it is only a temp situation, until kexec is fully working on our phone, and I am working to resolve that.
Jim
Click to expand...
Click to collapse
How complex are the 3 different ways for temporary bypass?
Sent from my MB865 using XDA
jimbridgman said:
Sorry guys, but I don't get as much of a chance to get on here as often anymore, and its been about 6 or so weeks since I have pulled up XDA, I just have a ton of things on my plate right now.
Yes I had a bootable CM7, but it really does not work, the big issue is that ALL of the CM7 apps are tied to the kernel, and there is no kernel that has been built that is close enough to our hardware to just stick in there.
The ONLY way I have had a successful build was to compile a custom kernel and bypass the bootloader with kexec. There was an update to kexec a few weeks ago and I have lost the ability to bypass the bootloader on our phone since then.
My plan all along has been once I can get kexec working to release this version of CM7, but the issue is that it is all based on 2.3.5, and can't go forward, since 2.3.6 does not work well with CM7, no matter what i have tried.
I have just sort of let the cm7 no-kernel port die, and I am focusing on just kexec at the moment.
I have to keep my efforts underground right now, because I have been given a cease and desist letter from Moto, about my bypassing the kernel with kexec. They (Moto) do read this board, so I do advise you to be very careful what you decide to post on this site.
P.S. I have PM'd lkranser with this information, and I will PM him the link to the last no-kernel CM7 build, but it is worthless without the kernel, which is why I started the work on kexec. I have been the one person on here really focusing on cracking the boot loader since day one that this phone was out, and I have done it 3 different ways, but it is only a temp situation, until kexec is fully working on our phone, and I am working to resolve that.
Jim
Click to expand...
Click to collapse
This is THE man right here. Thanks for all the hard work Jim, we wouldn't have crap without this guy
Sent from my MB865 using Tapatalk
rdavisct said:
How complex are the 3 different ways for temporary bypass?
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Well the first two ended up bricking my phone after a reboot, but work until you reboot.... hence temporary.... They both involve compiling a HUGE kernel file that is over a GB in size, then while the bootloader tries to uncompress the tar.gz kernel file, you replace the kernel file with the one you want to boot, since the bootloader is busy. The second one is similar, but replaces the boot.img and the restore partition as well while the bootloader is busy. Again you get one successful boot and can run forever, unless you need to reboot, or drain the battery, then you are hard bricked.... that is how I bricked my first 3 A2s.
The third is kexec, that is how I had been running cm7 with a custom kernel for 2 months. Untill the last update that would allow ics kernel booting, but I have had trouble getting it working again with the newer version. It works like firmware in that you can't go to a lower version from a higher version, even after an fxz flash, so I am stuck, until I get it working. Oh and kexec has not caused a single brick yet, when I had it working.
Jim
Sent from my MB865 using xda premium
Oh by the way here is the link to kexec, for those who would like to give it a shot..... it is not hard.... it looks like kohlk has it for the razr, so that version "should" work for us too.
I will give this one a try hopefully tomorrow and report back. I was using my own compiled version before.
Kexec for the razr:
http://forum.xda-developers.com/showthread.php?t=1599648
Jim
Sent from my MB865 using xda premium
jimbridgman said:
Oh by the way here is the link to kexec, for those who would like to give it a shot..... it is not hard.... it looks like kohlk has it for the razr, so that version "should" work for us too.
I will give this one a try hopefully tomorrow and report back. I was using my own compiled version before.
Kexec for the razr:
http://forum.xda-developers.com/showthread.php?t=1599648
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Hm, I can't get it to work... Here's the output when I execute "unlockme.sh"
Code:
sh /system/bypassme/bypassme.sh
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444
Written 0x4444AAAA; readback 0x4444
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444AAAA
Written 0x44445555; readback 0x4444AAAA
I've recognized devtree argument! devtree3Adding OMAP Device Tree...
Adding initrd...
Then it hot reboots but the kernel stays the same:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
cogeary said:
Hm, I can't get it to work... Here's the output when I execute "unlockme.sh"
Code:
sh /system/bypassme/bypassme.sh
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444
Written 0x4444AAAA; readback 0x4444
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444AAAA
Written 0x44445555; readback 0x4444AAAA
I've recognized devtree argument! devtree3Adding OMAP Device Tree...
Adding initrd...
Then it hot reboots but the kernel stays the same:
Click to expand...
Click to collapse
You need a kernel to boot for that to change. The kernel must be compiled for this device though. That is great news though, that means that you can boot other kernels with it. Check what kholk has to say on how to in the link I posted, there is a place you need to put the kernel...
This is HUGE!!!!
Jim
Sent from my MB865 using xda premium
jimbridgman said:
You need a kernel to boot for that to change. The kernel must be compiled for this device though. That is great news though, that means that you can boot other kernels with it. Check what kholk has to say on how to in the link I posted, there is a place you need to put the kernel...
This is HUGE!!!!
Jim
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
cogeary said:
Hm, I can't get it to work... Here's the output when I execute "unlockme.sh"
Code:
sh /system/bypassme/bypassme.sh
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444
Written 0x4444AAAA; readback 0x4444
/dev/mem opened.
Memory mapped at address 0x4001b000.
Value at address 0x4A314048 (0x4001b048): 0x4444AAAA
Written 0x44445555; readback 0x4444AAAA
I've recognized devtree argument! devtree3Adding OMAP Device Tree...
Adding initrd...
Then it hot reboots but the kernel stays the same:
Click to expand...
Click to collapse
This should probably be moved/quoted in the Bootloader thread
Related
Hi guys
I would appreciate if someone [dev] can give me some answers on this ...
Now that we have full CWM , thanks to the devs [@gtg465x]
How about following instructions to flash lastest MIUI for Galaxy S I9000 , using the actual installation guide > http://j.mp/iZSjlh , and try this ROM on the Infuse
Is the Galaxy S I9000 the closest phone [specs] we can have to try this ?
Some step(s) in that guide to be replaced or skipped ?
Worth to try it?
Would it work ?
Would I brick the phone?
I if brick it , would I still be able to un-brick using ODIN [back to factory]
TIA
pvillasuso said:
Hi guys
I would appreciate if someone [dev] can give me some answers on this ...
Now that we have full CWM , thanks to the devs [@gtg465x]
How about following instructions to flash lastest MIUI for Galaxy S I9000 , using the actual installation guide > http://j.mp/iZSjlh , and try this ROM on the Infuse
Is the Galaxy S I9000 the closest phone [specs] we can have to try this ?
Some step(s) in that guide to be replaced or skipped ?
Worth to try it?
Would it work ?
Would I brick the phone?
I if brick it , would I still be able to un-brick using ODIN [back to factory]
TIA
Click to expand...
Click to collapse
Would be very interested in this as well, but not enough to try bricking my phone .
I wouldn't try it.
Just because the partition layout of the original Galaxy S is the same as our device, it does not mean the kernel is compatible.
The current roms are all based on the stock kernel and do not change any of the core of how the device works. We still have TouchWiz built in and won't be changing that until we have custom kernel built and working on this device.
On the other hand, we can flash back to stock with Odin, so you won't completely fubar your phone if you try.
knight4led said:
I wouldn't try it.
Just because the partition layout of the original Galaxy S is the same as our device, it does not mean the kernel is compatible.
The current roms are all based on the stock kernel and do not change any of the core of how the device works. We still have TouchWiz built in and won't be changing that until we have custom kernel built and working on this device.
On the other hand, we can flash back to stock with Odin, so you won't completely fubar your phone if you try.
Click to expand...
Click to collapse
Your right about kernel compatibility , so 1st step not using speedmod kernel [used @ guide]
But I would like to know if the native MIUI kernel used @ the galaxy S is like a "modded kernel" they used to port that rom .. or if its a kind of "universal kernel" ?? . I dont know if Im making myself clear
knight4led said:
I wouldn't try it.
Just because the partition layout of the original Galaxy S is the same as our device, it does not mean the kernel is compatible.
The current roms are all based on the stock kernel and do not change any of the core of how the device works. We still have TouchWiz built in and won't be changing that until we have custom kernel built and working on this device.
On the other hand, we can flash back to stock with Odin, so you won't completely fubar your phone if you try.
Click to expand...
Click to collapse
If the partition layout changes, cannot promise Odin will fix it. Pit, boot.bin and sbl.bin pulled from a phone to flash will most likely cause a hard brick. We need a leaked one-click, or some very crazy testers willing to brick phones left and right to test that. I don't recommend it.
Sent from my SAMSUNG-SGH-I997 using XDA App
h8rift said:
If the partition layout changes, cannot promise Odin will fix it. Pit, boot.bin and sbl.bin pulled from a phone to flash will most likely cause a hard brick. We need a leaked one-click, or some very crazy testers willing to brick phones left and right to test that. I don't recommend it.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Thanks for that information , exactly what I wanted to read ...
Time to close this thread [MODS please] , and wait for someone who can make this happen !
pvillasuso said:
Thanks for that information , exactly what I wanted to read ...
Time to close this thread [MODS please] , and wait for someone who can make this happen !
Click to expand...
Click to collapse
Not a problem. When a new phone comes out....here's what happens:
1. Root
2. SBF/ODIN
3. CWM recovery
4. Psuedo ROMs based on stock.
5. Source Code drops.
6. Custom kernels (w/CWM built in)
7. Ports for MIUI/CM7/Sense/etc.
In 3 weeks, the community as a whole has completely done steps 1-5. (Usually takes a couple of months).
Next big focus has to be custom kernels. I helped out with some of the initial stuff for CM7 on Captivate before I bought an Atrix, then the Infuse. I'm going to be doing alot of reading and trying to learn alot more about git. Then I will be able to look into kernels. Team Whiskey had some guys working on a kernel with CWM + VooDoo lagfix written up...but I havent heard anything in a few days. So....be patient, its coming! .
Sent from my SAMSUNG-SGH-I997 using XDA App
h8rift said:
Not a problem. When a new phone comes out....here's what happens:
1. Root
2. SBF/ODIN
3. CWM recovery
4. Psuedo ROMs based on stock.
5. Source Code drops.
6. Custom kernels (w/CWM built in)
7. Ports for MIUI/CM7/Sense/etc.
In 3 weeks, the community as a whole has completely done steps 1-5. (Usually takes a couple of months).
Next big focus has to be custom kernels. I helped out with some of the initial stuff for CM7 on Captivate before I bought an Atrix, then the Infuse. I'm going to be doing alot of reading and trying to learn alot more about git. Then I will be able to look into kernels. Team Whiskey had some guys working on a kernel with CWM + VooDoo lagfix written up...but I havent heard anything in a few days. So....be patient, its coming! .
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
You are indeed one of the MAN, I speak for my self thanks dude
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
h8rift said:
When a new phone comes out....here's what happens:
1. Root
2. SBF/ODIN
3. CWM recovery
4. Psuedo ROMs based on stock.
5. Source Code drops.
6. Custom kernels (w/CWM built in)
7. Ports for MIUI/CM7/Sense/etc.
Click to expand...
Click to collapse
Very interesting info , thanks for sharing , didn't know the order of these steps to follow ..
We are closer then ! cool , cant wait to run MIUI @ Infuse
Like others said, we will need a custom kernel for MIUI. However, the Infuse is very similar to the original Galaxy S. I bet it would be really easy to port 2.2.1 Galaxy S ROMs. They would probably boot right up and work fine if you just remove the kernel from them and swap out a few files (ril, camera libs, key layouts).
gtg465x said:
Like others said, we will need a custom kernel for MIUI. However, the Infuse is very similar to the original Galaxy S. I bet it would be really easy to port 2.2.1 Galaxy S ROMs. They would probably boot right up and work fine if you just remove the kernel from them and swap out a few files (ril, camera libs, key layouts).
Click to expand...
Click to collapse
Hey I have one theme in mind, can you give me the details of these files?
(Wait do themes even mess with these files?)
Key layouts I got...
Camera libs? where are those located?
ril? what is that and where?
Thanks much appreciated.
-Ken
slider2828 said:
Hey I have one theme in mind, can you give me the details of these files?
(Wait do themes even mess with these files?)
Key layouts I got...
Camera libs? where are those located?
ril? what is that and where?
Thanks much appreciated.
-Ken
Click to expand...
Click to collapse
I'm used to HTC devices so I can't tell you the exact names of the ril and camera libs on a Samsung device without looking, but they will be in /system/lib. You may also have to swap a few files in /system/etc. Just takes research and then trial and error. I suggest grabbing a GS 2.2.1 ROM, removing the kernal (and modem if that's included) (will have to remove corresponding parts of updater-script as well), and then flashing. Adb logcat will help you to debug and fix issues from there.
Hell id donate an InFuSe to a miui dev that would make it happen!
I run miui on my Desire HD and wont use anything else, ever...
Sent from my SAMSUNG InFuSe using XDA Premium App
Once we get kernel source and a working CM7 build for it, my team is able to port MIUI to it
Well... once we get a device that is
We have been looking for a new device to port MIUI to. If there is enough demand for the Infuse 4G we'll pick one up.
If you guys manage to get it ported we'll create a device forum for you and host your roms, etc. If you need porting help/advice, or just want to talk about MIUI, join our IRC channel #miui-us on Freenode (details in my signature) and look for someone with a + in front of their name (those are the developers).
Anyway, hope to see you guys running MIUI soon!
Now this is what im talking about. If you guys have stuff to test ill snag it up and try it. Cant write but I can install it and test for ya. Not really scared to brick it. Plus its insured. Anyway good luck cant wait for it!!!
Sent from my SAMSUNG-SGH-I997 using XDA App
Are there any good guides/articles to learning how to create custom roms and whatnot?
I'm a software developer and while I've never done anything related to kernals/operating systems normally I'm able to pick up stuff quick and I think learning about stuff like this for Android phones would be awesome. I just really have no idea where to start at.
Frooty said:
Are there any good guides/articles to learning how to create custom roms and whatnot?
I'm a software developer and while I've never done anything related to kernals/operating systems normally I'm able to pick up stuff quick and I think learning about stuff like this for Android phones would be awesome. I just really have no idea where to start at.
Click to expand...
Click to collapse
Unfortunately...that is why there aren't more devs around. No docs. Its all trial and error...especially kernels.
Sent from my SAMSUNG-SGH-I997 using XDA App
Just keep trying you can unbrick anyway with dev gtg465x ultimate unbrick procedure so it is safe, just don't drop the Indie on water,
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
h8rift said:
Unfortunately...that is why there aren't more devs around. No docs. Its all trial and error...especially kernels.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Would you or one of the other devs be willing to post an intro guide or something in order to help get more developers here?
I know you guys are probably busy working on your roms as well as work/school/doing other things, but it probably wouldn't take too long to make a short intro to help us get started. That way we could hopefully get some more devs around here.
I've been reading others guides and posts about it and I could probably do at least a little work from the start based on what they say is involved in making a rom, but the biggest problem for me is not knowing how to get going. It seems like you need an android kitchen to do a lot of the work but all of the kitchens look like they are phone specific so I don't want to try using one if those on the infuse. Maybe they aren't, but info like that to help us get our feet wet would be extremely helpful.
Sent from my SAMSUNG-SGH-I997 using XDA App
Frooty said:
Would you or one of the other devs be willing to post an intro guide or something in order to help get more developers here?
I know you guys are probably busy working on your roms as well as work/school/doing other things, but it probably wouldn't take too long to make a short intro to help us get started. That way we could hopefully get some more devs around here.
I've been reading others guides and posts about it and I could probably do at least a little work from the start based on what they say is involved in making a rom, but the biggest problem for me is not knowing how to get going. It seems like you need an android kitchen to do a lot of the work but all of the kitchens look like they are phone specific so I don't want to try using one if those on the infuse. Maybe they aren't, but info like that to help us get our feet wet would be extremely helpful.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
I'm with ya. I've got some free time and would be happy to help in anyway.
Sent from Samy Infuse
Just wondering if anybody saw this. Here's a link for everybody to check out.
http://community.developer.motorola...-2-development-resources-available/td-p/19569
Sent from my MB865 using Tapatalk
tylercarter said:
Just wondering if anybody saw this. Here's a link for everybody to check out.
http://community.developer.motorola...-2-development-resources-available/td-p/19569
Sent from my MB865 using Tapatalk
Click to expand...
Click to collapse
Yeah, unfortunately it is not the source code yet, just the parts for the emulator and pieces needed for Devs to write apps specifically for the Atrix2.
I wish there was more there for us to use to get this thing cracked open. Hopefully we can get a ROM developer to jump in here soon and help us collect what they need to get started on ROM development. Although we will need someone like Th3ory who is not afraid of making ROMs for devices with locked bootloaders, because I have a feeling it will be after ICS before we have an unlocked bootloader.
An emulator as in a full emulation of our phone? So if one were to try to develop a ROM for this thing could that be used to test rather than risking a brick?
jimbridgman said:
Yeah, unfortunately it is not the source code yet, just the parts for the emulator and pieces needed for Devs to write apps specifically for the Atrix2.
I wish there was more there for us to use to get this thing cracked open. Hopefully we can get a ROM developer to jump in here soon and help us collect what they need to get started on ROM development. Although we will need someone like Th3ory who is not afraid of making ROMs for devices with locked bootloaders, because I have a feeling it will be after ICS before we have an unlocked bootloader.
Click to expand...
Click to collapse
Jim I'm curious. What recovery are you using? Bionic bootstrapper? And is it safe yet? I've read on it a little. Is it one of those things where unless your a bit of a dev not to try it?
Sent from my MB865 using Tapatalk
@PeteSeiler2010:
Yes this could be used to test a Developed ROM, however until we get a hold of some kind of code for this thing, there can't be too much development of ROMs and such, unless someone knows something I don't. And "code" can be anything from an fxz to the released source code for the Atrix 2 build.
@tylercarter:
For a "Recovery" this is the one you want, link below. And yes it is not 100% yet, but it does what we need it to right now, the only issue is if you crash, you can't get back to it on boot, you have to use the bootstrap to boot into it, from your app drawer. This is again something that can be done after a bootloader unlock. This will allow back up and restores though.
http://forum.xda-developers.com/showthread.php?t=1346977
----EDIT----
I use the emulator for a lot of the work I have been doing to see what will happen, without risking a screwup on my phone directly. Then once I have tested it out there, on the phone it goes. You can even test apps from the market as well, just to see. It is really for app developers, to do their testing of the apps they build, but we can also do something similar for our "hacking".
Thanks for info Jim, I am going to download it and check it out and see if there is anything I do with it.
Also, Jim, have you done many restores on your phone? I have been hesitant to try one...its just so risky without the sbf.
PeteSeiler2010 said:
Thanks for info Jim, I am going to download it and check it out and see if there is anything I do with it.
Also, Jim, have you done many restores on your phone? I have been hesitant to try one...its just so risky without the sbf.
Click to expand...
Click to collapse
Not a FULL restore, but there are others who have tried one of the updates in the bootloader unlock forum, that have been able to restore back to before the update successfully.
I have restored files, and even directories, but not the whole thing yet.
Hi, I have noticed a ton of people curious about why AT&T people do not have ICS yet, so I thought I would answer that once and for all. I admit that I and others have gotten a little mad whenever people ask about this, but it seems they are not able to really find a clear answer, so here it is.
If you feel like this is well done, please sticky it at least until we get it all figured out.
I figure this would be best said i a Q and A type form.
Q: What is ICS, and why does everyone want it so bad?
ICS or "Ice Cream Sandwich" is android version 4.0.x. the next version, 4.1 Jellybean was just released as a slightly less important update, but ICS brought huge changes from Ginger Bread (2.3.x) the previous phone version (3.x HoneyComb was tablet only). ICS brings a slicker, darker, and better looking user interface, as well as many performance enhancements. Most of us want it more because it seems like we should than because it is actually that much better. That said it is still a great update, and most people will be happy to see it.
Click to expand...
Click to collapse
Q: Why is it so hard to get ICS for our phone, while others have it even though it is not officially out?
The main reason is our locked bootloader. That means it is not possible to flash or boot a custom kernel unless it is signed with Motorola's key. That is obviously impossible.
Click to expand...
Click to collapse
Q: What is a kernel?
the kernel is a major part of any operating system. you can think of it as a sort of layer between hardware and software. It is the part of an OS that communicates directly with a device's hardware. Android is based off the open source Linux kernel, meaning it is free for anybody to build and modify. However, Motorola has only released the source for the ME865, and partially for the MB865, meaning we can't really build a kernel anyways. Then of course, even if we could build one, we wouldn't be able to boot it with our locked bootloader.
ICS is not really complete without the newer kernel that goes with it
Click to expand...
Click to collapse
What is Kexec, and is there any way to unlock the bootloader
The fact that I grouped these together would probably lead you to correctly believe they are related. Lets start with the second half. Simply put, NO. I hate to say it, but there is very little hope of EVER unlocking our bootloader, unless Motorola decides to do something like HTC did and allow unlocking.
Kexec is a method of hot switching kernels while still booted. It is actually just a linux tool that you can use on a computer, but it has been built for android essentially allowing you to bypass the bootloader. Theoretically it would be an easy way to run custom kernels. Then why don't we? Well a few reasons. One, we can't really get one built to begin with, especially because, at least to my knowledge, jimbridgman is the only one who actually knows what he is doing with kernel building, and he is only half here now that he got his fany new SGS3. Two, it does not work great. I am not sure the latest version is working at all on our phone, and even if it did, only one processor comes up, meaning it is really slow.
Click to expand...
Click to collapse
Q: What's the deal with these Droid 3 builds that supposedly boot?
Some people managed to build ICS for the droid 3 based of a 2.3.6 kernel. that means you can boot it on a stock GB kernel, and therefore you do not need to unlock the bootloader. Unfortunately that means it is not totally ICS, but it is still pretty good. Of course they are for a cdma phone, so that means no data, no calls, and no gps, making it kind of useless.
I am not going to give a link to them, but if you are really interested go search around. any of the Droid 3 AOKP and CM9 builds will boot just fine. Find more info in the dev section, but please don't start a thread asking about it.
We have been trying to port these to work for us, but that is proving more difficult than expected, and with ICS just around the corner, I don't want to put time into it. I do think it is possible, and if you are a dev looking to give it a shot, PM me and I will tell you all I know, and try to help out as much as I can.
Click to expand...
Click to collapse
Great thread!
Thanks for putting this together!
Sent from my SAMSUNG-SGH-I747 using xda premium
jimbridgman said:
Great thread!
Thanks for putting this together!
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
thanks. I felt it was needed. let me know if I forgot to say something important.
Sent from my MB865 using xda premium
Perhaps this will hopefully curb some of the incessant "where's my ice cream sandwich" or "make me a rom based on ICS" threads here. Nice job, and as always, your work here is both highly appreciated and revered.
Sent from my MB865 using xda premium
Nice work kras, as always.
Sent from my MB865 using xda premium
Hell i thought this thread was going to give me info on why att hadn't released ics for us yet. Just kidding, good job. If this thread falls down the list ill bump it so maybe it will help some of the new people and we won't get any more new threads about ics.
Sent from my MB865 using xda premium
Apex_Strider said:
Perhaps this will hopefully curb some of the incessant "where's my ice cream sandwich" or "make me a rom based on ICS" threads here. Nice job, and as always, your work here is both highly appreciated and revered.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
No,Most likely once posts stop on this thread and it makes it to the second page we will see more questions im sure lol
Sent from my MB865 using xda premium
rdavisct said:
No,Most likely once posts stop on this thread and it makes it to the second page we will see more questions im sure lol
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
that's why I asked for sticky
Sent from my MB865 using xda premium
The good news is that the "3rd quarter" is tomorrow! Which knowing motorola and AT&T, could mean whatever.
Take that with a grain of salt. Lol.
Sent from my MB865 using xda premium
Fall of Enosis said:
The good news is that the "3rd quarter" is tomorrow! Which knowing motorola and AT&T, could mean whatever.
Take that with a grain of salt. Lol.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
so is September
Sent from my MB865 using xda premium
Why don't we have a vanilla rom? Is it due again to the locked bootloader?
Sent from my MB865
gvsukids said:
Why don't we have a vanilla rom? Is it due again to the locked bootloader?
Sent from my MB865
Click to expand...
Click to collapse
yep. same thing. we have a hard time compiling any also source as you need a custom kernel
Sent from my MB865 using xda premium
Nice post..
Just one thing to inform about your last question's ans.. DROID 3'S ROMS DONT WORK ON OUR PHONE. IT WILL BOOTLOOP. SO DO NOT TRY FLASHING THEIR AOKP OR CM.. without backups and sufficient knowledge and experience atleast.. some changes have to be made in the rom before flashing.. i am trying to find all the files we must replace to get them working on our phone.. and just a FYI for those of you that wanna try.. other than droid 3, bionic is our nearest relative.. so u can edit and try their roms as well.. i did kinda get cm9 of bionic after replacing some required files.. but it bootlooped.. and of course bionic is cdma.. so.. good luck..
Sent from my MB865 using Tapatalk 2
Ravikirancg said:
Nice post..
Just one thing to inform about your last question's ans.. DROID 3'S ROMS DONT WORK ON OUR PHONE. IT WILL BOOTLOOP. SO DO NOT TRY FLASHING THEIR AOKP OR CM.. without backups and sufficient knowledge and experience atleast.. some changes have to be made in the rom before flashing.. i am trying to find all the files we must replace to get them working on our phone.. and just a FYI for those of you that wanna try.. other than droid 3, bionic is our nearest relative.. so u can edit and try their roms as well.. i did kinda get cm9 of bionic after replacing some required files.. but it bootlooped.. and of course bionic is cdma.. so.. good luck..
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
You are not right. I can prove it. The latest droid 3 AOKP and Cm9 builds will boot just fine, with no radio
You should also add Why any other leak releases of atrix 2 ICS will not work on att atrix 2..... Sick of will this work on my att..... About to be like yea we all use it lol JK.....
Ravikirancg said:
DROID 3'S ROMS DONT WORK ON OUR PHONE. IT WILL BOOTLOOP. SO DO NOT TRY FLASHING THEIR AOKP OR CM9
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Couldn't be more wrong....they both boot just fine and are pretty functional, the problem lies in getting the radio to work.
Ravikirancg said:
Nice post..
Just one thing to inform about your last question's ans.. DROID 3'S ROMS DONT WORK ON OUR PHONE. IT WILL BOOTLOOP. SO DO NOT TRY FLASHING THEIR AOKP OR CM.. without backups and sufficient knowledge and experience atleast.. some changes have to be made in the rom before flashing.. i am trying to find all the files we must replace to get them working on our phone.. and just a FYI for those of you that wanna try.. other than droid 3, bionic is our nearest relative.. so u can edit and try their roms as well.. i did kinda get cm9 of bionic after replacing some required files.. but it bootlooped.. and of course bionic is cdma.. so.. good luck..
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Please I emplore you to do your proper research before making incorrect posts like this. I constantly see posts from those who think they know it all, and post idiotic things like this. Nothing makes me madder than someone who does not know how to use google and the search function.
It takes less than 2 min. to make sure you CYA before posting bad information.
Both CM9 and AOKP boot, but with no radio, as has already been said in several posts now. I have tested both.
P.S. most of us devs in here have been working on this very thing for sometime now, and I have not seen you jump in on any of threads discussing the files or how to port or anything.
Sent from my SAMSUNG-SGH-I747 using xda premium
jimbridgman said:
Please I emplore you to do your proper research before making incorrect posts like this. I constantly see posts from those who think they know it all, and post idiotic things like this. Nothing makes me madder than someone who does not know how to use google and the search function.
It takes less than 2 min. to make sure you CYA before posting bad information.
Both CM9 and AOKP boot, but with no radio, as has already been said in several posts now. I have tested both.
P.S. most of us devs in here have been working on this very thing for sometime now, and I have not seen you jump in on any of threads discussing the files or how to port or anything.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Agreed, They actually run extremely well, but obviously I can't stick with them with no radio.
P.S. this is my new best thought for porting, might take some extra build.prop work too. It did not boot for me, but I think we should be able to get it to. Then it is just a question of whether or not the radio will work. there is way more in build.prop on that than I would think.
http://forum.xda-developers.com/showthread.php?t=1598713
I think it may work because it really adds the cm9 stuff to our own files rather than add our files to it. maybe not the cleanest way, but it might just work.
hankbizzo5 said:
You should also add Why any other leak releases of atrix 2 ICS will not work on att atrix 2..... Sick of will this work on my att..... About to be like yea we all use it lol JK.....
Click to expand...
Click to collapse
WOW, did I really forget to add that? that was kind of one of the main points of this post I'll fix it tomorrow (actually today, I guess it is after midnight), but I need some sleep.
lkrasner said:
http://forum.xda-developers.com/showthread.php?t=1598713
I think it may work because it really adds the cm9 stuff to our own files rather than add our files to it. maybe not the cleanest way, but it might just work.
Click to expand...
Click to collapse
I have tried this method along with every idea that popped in my head of things to alter after following this guide. I have a highly modified build prop that AOKP boots with that I replaced with a lot of our build prop but there are still some things missing as no luck yet
Every other good phone has it...even the ones with locked BL like defy......
Come on guys..we have one of the best phones .....atrix 2 aint bull****...if not everything then maybe CM would atleast make most of us happy......be a team ..if not many then atleast one awsomely working CM ....i dont want samsung or htc....look at them ..brick bug or touch issues or battery backup........we have no issues except BL ......
And can someone tell me when kexec comes out.. usable for us.....
Im happy though with my A2
hemanbond said:
Every other good phone has it...even the ones with locked BL like defy......
Come on guys..we have one of the best phones .....atrix 2 aint bull****...if not everything then maybe CM would atleast make most of us happy......be a team ..if not many then atleast one awsomely working CM ....i dont want samsung or htc....look at them ..brick bug or touch issues or battery backup........we have no issues except BL ......
And can someone tell me when kexec comes out.. usable for us.....
Im happy though with my A2
Click to expand...
Click to collapse
seriously?? can a mod just lock this before it explodes
Sent from my MB865 using xda premium
I dont know anything...but its a harsh truth that moto wont unlock bootloader..
Locked boot loader means NO CM7/9.
PERIOD.
Whatever the defy boys have is probably some half-arsed hacked port.
Please, FOR THE LOVE OF GOD, search before you ask next time.
Here, I'll do it for you: http://lmgtfy.com/?q=will+cyanogenmod+work+on+a+locked+bootloader?+
Sent from my MB865 using xda premium
lkrasner said:
seriously?? can a mod just lock this before it explodes
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Agreed. I hope we don't start seeing a bunch of these, "Well this phone or that phone can have (whatever) so what's up with the ATRIX 2?"
Sent from my ME860 using xda premium
Hmmm
hemanbond said:
Every other good phone has it...even the ones with locked BL like defy......
Come on guys..we have one of the best phones .....atrix 2 aint bull****...if not everything then maybe CM would atleast make most of us happy......be a team ..if not many then atleast one awsomely working CM ....i dont want samsung or htc....look at them ..brick bug or touch issues or battery backup........we have no issues except BL ......
And can someone tell me when kexec comes out.. usable for us.....
Im happy though with my A2
Click to expand...
Click to collapse
i know u r right...since i had defy with cm7 though its bootloader is unlocked ....but u cannot complain about it .....u bought the phone ...nobody forced u ......be happy with what u got nd devs can offer ...if u cant help....dnt expect to get help /......fair enough ,....not to be harsh ,its just as simple as that
GaganPla said:
i know u r right...since i had defy with cm7 though its bootloader is unlocked ....but u cannot complain about it .....u bought the phone ...nobody forced u ......be happy with what u got nd devs can offer ...if u cant help....dnt expect to get help /......fair enough ,....not to be harsh ,its just as simple as that
Click to expand...
Click to collapse
Or the OP could learn how to dev and try and compile CM9 for himself and see where he gets. Most of our devs did not start out as devs.
jimbridgman said:
Or the OP could learn how to dev and try and compile CM9 for himself and see where he gets. Most of our devs did not start out as devs.
Click to expand...
Click to collapse
+1 to that A BIG ONE
This is getting to be a every day thing here and i personally am running out of patience because of people not taking five minutes to read up on their already answered questions. I propose that we start ignoring these type of posts from now on. That to me is the best solution.
Sent from my MB865 using xda premium
tmease1 said:
This is getting to be a every day thing here and i personally am running out of patience because of people not taking five minutes to read up on their already answered questions. I propose that we start ignoring these type of posts from now on. That to me is the best solution.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
+1
Agreed.
Sent from my MB865 using xda's premium carrier pigeon service
@OP yea good attitude now go do RnD for yourself, you cant search sh!t in first place and you dare to order other respected people ? Just cut your [email protected] and stop posting useless threads.
+1 tmease. I concur.
Sent from my MB865 using xda premium
BOOMSHAKALAKAAAAA!
(That's this thread exploding :-D )
Sent from my Motorola Atrix 2 with AT&T 4G
Not a bad idea. I came from defy.
They basically run cm7/9 with an existing signed moto kernel.
Myself, am interested in porting the 2nd init from defy. Really hope I can do it.
Sent from my MB865 using Tapatalk 2
lukensteinz said:
Not a bad idea. I came from defy.
They basically run cm7/9 with an existing signed moto kernel.
Myself, am interested in porting the 2nd init from defy. Really hope I can do it.
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Do a search... we already have done something similar, it is slow, and not worth it, since we don't have space on the internal storage to put the 2nd ROM, so it MUST go on the SDcard.
It was abandoned due to the fact that it was so slow it was unusable. Besides there are many of us that have been working to get CM7 and CM9 working from a port without success.... but you are more than welcome to jump in and lend a hand, we have a post in the dev section about it for aokp and CM9.
jimbridgman said:
Do a search... we already have done something similar, it is slow, and not worth it, since we don't have space on the internal storage to put the 2nd ROM, so it MUST go on the SDcard.
It was abandoned due to the fact that it was so slow it was unusable. Besides there are many of us that have been working to get CM7 and CM9 working from a port without success.... but you are more than welcome to jump in and lend a hand, we have a post in the dev section about it for aokp and CM9.
Click to expand...
Click to collapse
Do you mean as in a multi boot?
The Defy I had, I flashed a defy+ sbf too then plonked cm9 on, no 2nd rom/boot or such.
My understanding was that the purpose of 2nd init was to hijack the init process and allow to boot into boot manager.
I'm also guessing bootmanager would need to be built from source to suit the A2?
I've read a few of your posts mate, worked with Linus? Legend.
You will by far know more than I do these days, but I'll see what I can do to help.
First I'll deodex the ics leak I'm running and make a Cwm backup to upload. Not sure how useful it will be due to the kernel.
The U.S, Europe and Asia hardware is all different?
The one last thing I remember from defy was I had to use at&t baseband since telecom nz uses the same carrier frequency.
And ran the defy+ rom on old red lense ddfy without a single issue at defy+ stock clock freq
Sent from my MB865 using Tapatalk 2
lukensteinz said:
Do you mean as in a multi boot?
The Defy I had, I flashed a defy+ sbf too then plonked cm9 on, no 2nd rom/boot or such.
My understanding was that the purpose of 2nd init was to hijack the init process and allow to boot into boot manager.
I'm also guessing bootmanager would need to be built from source to suit the A2?
I've read a few of your posts mate, worked with Linus? Legend.
You will by far know more than I do these days, but I'll see what I can do to help.
First I'll deodex the ics leak I'm running and make a Cwm backup to upload. Not sure how useful it will be due to the kernel.
The U.S, Europe and Asia hardware is all different?
The one last thing I remember from defy was I had to use at&t baseband since telecom nz uses the same carrier frequency.
And ran the defy+ rom on old red lense ddfy without a single issue at defy+ stock clock freq
Sent from my MB865 using Tapatalk 2
Click to expand...
Click to collapse
Yeah we used a util called safestrap that another dev and I patched to make it work on this phone that was originally from hashcode.
It allowed us to boot another ROM on say our SDcard, but again it still has to use our kernel due to the bootloader issue...
The only way around the bootloader as of now is by using kexec, and that only works with 1 CPU and can only load a "stock based" unsigned kernel, so the CM stuff is out.
We are working to get CM9 and or AOKP booting from a port on our phone using the stock GB kernel. There is a post on it in the dev section.
Yeah Linus is a Friend, a great guy and I can't say enough good things about him. I have not seen him since the last Linux world / Opensource world now as it is called.
Yeah you should jump in and join the frey, we can always use more help in here.
Well it wasn't hard to work out how to get a 2nd init style boot. (As in, blue light, press vol down, gets bootmenu)
Except bootmenu is garbled screen. I need to test more, and probably mod some of the scripts.
Heres a system nandroid of ICS http://www.4shared.com/archive/bp3qzA9o/Atrix2-ICS-NANDROID__672112asi.html
Dunno how much use it will be since I didn't get the kernel.
Got it.... thanks
Can someone tell me is this cm10 fake?
http://crackteam.crackflasher.com/edison/cm10/
Sent from my ME865 using xda premium
I think ist real ill try it...wish me luck lol
From my locked down superchargedV6 1.425ghz A "What tha duce?"
daavvis said:
I think ist real ill try it...wish me luck lol
From my locked down superchargedV6 1.425ghz A "What tha duce?"
Click to expand...
Click to collapse
please let us know if it works.if you can flash that,can you tell me is there a custom recovery(cm) included in that rom?thanks.(someone flashed this rom on ME865 and bricked his phone,i just want to tell you)
sorry for my bad english
sunnytse1 said:
please let us know if it works.if you can flash that,can you tell me is there a custom recovery(cm) included in that rom?thanks.(someone flashed this rom on ME865 and bricked his phone,i just want to tell you)
sorry for my bad english
Click to expand...
Click to collapse
so far no good it flashed but i got stuck on the cyanogen circle..... it may have been my fault for more than one reason
i DID NOT wipe cache, cause i was on magicmod and tried to just upgrade, prob the culprit
recovery locked up on me directly after i opened justinbeanaroma to install inverted g apps, but i didnt reboot first, so could have been that
i installed through cm10 recovery, and there was no recovery after i installed this rom, so i think the data files left from no wipe may have either messed with this cm10 recovery, or this one doesnt have one
i had to rds back to 2.3.6 and just got back to leak 1
im gonna root real quick and install through bootstrap and ill let u guys know whats up
hashcodes name is on this tho, so i think i messed up, and i think this might still work....
edit..... gotta charge up a bit first in case i gotta rds back again lol
hope you will success! waiting for your reply.
ok guys im stupid.... see the "kexec log" at the top? this is for safestrap, explains y theres no recovery and y im stuk on the cyanogen screen again.....
im gonna re rds again and try this with safestrap, only cause theres like 80 roms on this site lol
ill keep u guys updated
daavvis said:
ok guys im stupid.... see the "kexec log" at the top? this is for safestrap, explains y theres no recovery and y im stuk on the cyanogen screen again.....
im gonna re rds again and try this with safestrap, only cause theres like 80 roms on this site lol
ill keep u guys updated
Click to expand...
Click to collapse
Downloading now..
This is a bit weird,
There are cm9, aosp and one CNA rom, also theyve given logs for kexec version for cm10..
Have we got a kexec for our A2 ??
any luck daavis ??
EDIT:
The crackflasher forums dont show a Atrix 2 subforum
Do you guys know who make this rom
and why there is no thread about it in xda?
(I found that link in a chinese website.)
Sent from my ME865 using xda premium
sunnytse1 said:
Do you guys know who make this rom
and why there is no thread about it in xda?
(I found that link in a chinese website.)
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
ok folks after a bunch of crap, feeling like a noob for a few hours, then cunsulting with the master of masters mr jimbridgman (next time i think of him or someone smarter than me first.... lol) heres the deal....
these roms are a test so to speak, and as far as i know none of them work, not cause they are faulty, but because kexec is not working properly on our phones, you can install it, you can wipe install and everything else really cool in a custom recovery, but the clincher is, when you try to boot the "safe system" the phone just hangs on a black screen.....
however.....
as a recovery tool only, safestrap isnt bad lol...
so the greatest question of all, can we port some of these to run without safestrap.... ill look into it.... must be possible...
daavvis said:
ok folks after a bunch of crap, feeling like a noob for a few hours, then cunsulting with the master of masters mr jimbridgman (next time i think of him or someone smarter than me first.... lol) heres the deal....
these roms are a test so to speak, and as far as i know none of them work, not cause they are faulty, but because kexec is not working properly on our phones, you can install it, you can wipe install and everything else really cool in a custom recovery, but the clincher is, when you try to boot the "safe system" the phone just hangs on a black screen.....
however.....
as a recovery tool only, safestrap isnt bad lol...
so the greatest question of all, can we port some of these to run without safestrap.... ill look into it.... must be possible...
Click to expand...
Click to collapse
It is possible, if you include kexec and the kernel files in the right location in the ROM that is built from this, then the phone will boot fully, and do a soft reset with the new kernel. I am not too sure that even that will work well. I have not had much luck with kexec in ICS yet. I had it working on GB and even was able to boot my early CM7 builds, but after an update in MAY that stopped working too. So.... good luck.
jimbridgman said:
It is possible, if you include kexec and the kernel files in the right location in the ROM that is built from this, then the phone will boot fully, and do a soft reset with the new kernel. I am not too sure that even that will work well. I have not had much luck with kexec in ICS yet. I had it working on GB and even was able to boot my early CM7 builds, but after an update in MAY that stopped working too. So.... good luck.
Click to expand...
Click to collapse
so.... um.... i kinda got it to boot..... forked the recovery from wangs cm10 and some other files and she lit up.... well it got as far as lighting up the soft keys lol...... im installing gapps now to see it that was the issue, may have forked some files that confused the ol girl, but hey, at least i have recovery lol
edit: ok so this time it made it through "android is upgrading, then it soft booted.... and got stuck at the cyanogenmod splash screen.... im close i can feel it lol
hey daavis, i had sent a mail asking whether this is in fact for the A2.. Got this reply..
Aniruddha:
My apologies for not having the appropriate threads set up ahead of time. CrackFlasher is still quite new, and the three users that moderate it, all have very busy schedules.
Please find the below threads that deal with your device. And yes, this is for the Atrix 2.
I believe you will need to use SafeStrap developed by Hashcode to flash these Roms, as for we just build them from source, but do not have a valid device to physically test on.
These Roms are development Roms, as in stock [branch] compile from source. Feel free to use these Roms as a base for Custom Rom Development. We would love to see your work, or other's, on CrackFlasher.com.
http://www.crackflasher.com/forumdisplay.php?47-Atrix-2-Development
Thanks again, and feel free to become a member and join the community. It's a slow building one, but we all do have one thing in common. We're all CrackFlashers.
Have a good day.
Click to expand...
Click to collapse
Theres an A2 development forum now.. and theyve posted nightlies for aosp, aokp, CNA and CM10.
have you tried the aosp or aokp builds yet ??
EDit: rather, is it possible to get them to work in any way ?
anikadam said:
hey daavis, i had sent a mail asking whether this is in fact for the A2.. Got this reply..
Theres an A2 development forum now.. and theyve posted nightlies for aosp, aokp, CNA and CM10.
have you tried the aosp or aokp builds yet ??
Click to expand...
Click to collapse
I ran out of time and had to stop but I was close, I'm going to get in touch with them and give it another go when I get my kitchen back up and running (upgraded fedora after I messed with the cm10 build.).
The latest cm10 was the only one I tried....
I'll keep u guys updated with progress reports...
Also anyone that wants to help pm me I have time issues cause I'm really just a nerdy Finish carpenter lol
Sent from my MB865 using xda app-developers app
daavvis said:
I ran out of time and had to stop but I was close, I'm going to get in touch with them and give it another go when I get my kitchen back up and running (upgraded fedora after I messed with the cm10 build.).
The latest cm10 was the only one I tried....
I'll keep u guys updated with progress reports...
Also anyone that wants to help pm me I have time issues cause I'm really just a nerdy Finish carpenter lol
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
haha.. a talented nerdy carpenter i must say
yeah u got it to boot.. thats quite a good amount of progress.. id help out if i knew more and had some more time..
Good to see some more potential ROMs for our beloved A2... looking forward to your progress daavvis.. :good:
This post from hashcode is talking about the crackflash ROMs for the a2, in our safestrap thread in the dev section:
http://forum.xda-developers.com/showthread.php?p=34555169
jimbridgman said:
This post from hashcode is talking about the crackflash ROMs for the a2, in our safestrap thread in the dev section:
http://forum.xda-developers.com/showthread.php?p=34555169
Click to expand...
Click to collapse
I read that too.... a very good warning for everyone to follow, they DEF don't work.... I'm still gonna try when I'm bored tho, cause I get bored lol
Sent from my MB865 using xda app-developers app
jimbridgman said:
This post from hashcode is talking about the crackflash ROMs for the a2, in our safestrap thread in the dev section:
http://forum.xda-developers.com/showthread.php?p=34555169
Click to expand...
Click to collapse
Yeah i read it too.. i thought this was some new development in kexec for our phone and therefore the aosp and aokp ROMs, since they showed a november build.. but then it wasnt
Can someone actually can use this rom?
Sent from my ME865 using xda premium
sunnytse1 said:
Can someone actually can use this rom?
Sent from my ME865 using xda premium
Click to expand...
Click to collapse
no, not yet, these build are not ready for users. Someone set these up for auto-builds, that works with hashcode. Hashcode said that they do not work as of yet. I would not use these or even try unless you have some dev experience.
jimbridgman said:
no, not yet, these build are not ready for users. Someone set these up for auto-builds, that works with hashcode. Hashcode said that they do not work as of yet. I would not use these or even try unless you have some dev experience.
Click to expand...
Click to collapse
im about to give her another whack, after finally ( fedora 17 doesnt speak well with my video card, ubuntu [eh' i know noob build, but lets face it it runs nice and has tons of documentation] decided it didnt like my wireless card [ ok so it decided to fail installing the firmware and after hours explained to me what was wrong] ) getting my m1330 back together, and running effin wicked fast again, i need to know what files i need to play with to get my little cm build booting....
jim what would you expect was the culprit if she soft boots after building any cache? the log wont show anything through cm recovery, is there a log i can pull through adb or something that will bring a beacon of light to my daavviscm10build dreariness?