Related
So the crackflashers have done it again - Gingerbread is now on the Desire / Bravo
Based on CM 7 Source
Thanks to Cyanogen, #teamdouche and @gridlock32404 (Thatguy32404) - These are unoffical builds based on their code as such..
Code:
These builds have nothing extra added, they are just like the usual
"nightly" builds. There is no support provided, this is just a hobby and
I thought I would share. If you don't know how to flash a unofficial build,
don't want possible bugs or don't like living on the edge, go away!
Do a nandroid backup first!
OK so here is how to get it up and running:
Step 1 - Download the latest build from http://www.crackflashers.com look in the builds folder for the latest file - The build will increment by 1 each time there is a new build so if there is one there greater than b#29 download it << In case I don't get the thread updated at the same time
Step 2 - Download the Gingerbread apps from NEEDS UPDATED TO POINT TO DESIRE / BRAVO. crackflashers.com/ace/[/URL] look in the google-apps folder for the file gingerbread-gapps-12302010.zip
Step 3 - Place all these files onto your sd card reboot into recovery
Step 4 - Flash the files using the install zip from sdcard option (do the rom first then the gapps)
Step 5 - Reboot phone and enjoy the Gingerbread goodness
Current Issues
Current Issues
#17 - APN list may be empty and you will need to manually enter this - a complete list can be found at http://code.google.com/p/cyanogenmo...orum.xda-developers.com/show...&postcount=271 for resolution
does it can be use with n1 table hboot?so, you will update nightly?
anyway, nice work!
nice work, will surely give it a try
any benchmarks?
najar360 said:
does it can be use with n1 table hboot?so, you will update nightly?
anyway, nice work!
Click to expand...
Click to collapse
Check out the N1 thread http://forum.xda-developers.com/showthread.php?t=883605
I only tested it and maintain the thread - the guys above deserve the kudos
gilmorenator said:
Check out the N1 thread http://forum.xda-developers.com/showthread.php?t=883605
I only tested it and maintain the thread - the guys above deserve the kudos
Click to expand...
Click to collapse
how bout a2sd+?does it work with dark tremor or firerat?
edit : confirm can't use with firerat.
najar360 said:
how bout a2sd+?does it work with dark tremor or firerat?
Click to expand...
Click to collapse
This is the first build that I actually made for the desire so to say we don't exactly know what other additions made outside the source/gingerbread will or won't work. The only way to try is to make a nandroid backup after you flash this in and try it
Ps. The new recovery image is not supported in rom manager so everything will need to be done in the recovery manually even thought the code of the recovery is made by koush it is not an official release by him at all, just built from it. it is the only recovery currently that can handle ext 4 /system partion that cm7 source is based on.
You will not be able to restore a pre-cm7 source build on this recovery or flash a pre cm7 rom on it either (hence the backup recovery.img if you decide to go back) you can backup and restore any cm7 source rom on this recovery
Yes the new recovery is needed to flash gapps and newer updates as they become availible.
This is on the list of many devices I am compiling for. Currently g2, mt4g, evo4g, droid, desire hd, desire and sometimes the n1. If you can't seem to find an answer to something there is a good chance you will find it in one of those sections. Just look for posts from me
Sent from my HTC Vision using XDA App
Thatguy32404 said:
This is the first build that I actually made for the desire so to say we don't exactly know what other additions made outside the source/gingerbread will or won't work. The only way to try is to make a nandroid backup after you flash this in and try it
Ps. The new recovery image is not supported in rom manager so everything will need to be done in the recovery manually even thought the code of the recovery is made by koush it is not an official release by him at all, just built from it. it is the only recovery currently that can handle ext 4 /system partion that cm7 source is based on.
You will not be able to restore a pre-cm7 source build on this recovery or flash a pre cm7 rom on it either (hence the backup recovery.img if you decide to go back) you can backup and restore any cm7 source rom on this recovery
Yes the new recovery is needed to flash gapps and newer updates as they become availible.
This is on the list of many devices I am compiling for. Currently g2, mt4g, evo4g, droid, desire hd, desire and sometimes the n1. If you can't seem to find an answer to something there is a good chance you will find it in one of those sections. Just look for posts from me
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
thanks for explanation. anyway i try firerat and it failed. not yet try with dark tremor.
question, if i use current recovery such amon ra or previous clockworld, is it give diff outcome?
najar360 said:
question, if i use current recovery such amon ra or previous clockworld, is it give diff outcome?
Click to expand...
Click to collapse
You may flash the ROM with your current recovery but you won't be able to flash GAPPS - making it a bare rom
Sent from my HTC Desire using XDA App
Sorry to get your hopes up guys, the code for the cm parts is there in the source and was all good to be added in but what the main code (not just the app but the framework parts of it) were removed till implemented. Still a build 13 coming shorty. It is compiling but will be missing the cm parts
Sent from my HTC Vision using XDA App
Build 13 is up, has gps fixes and other things. Too tired to list all changes check @cmsrc on twitter or github for what's been added
Sent from my HTC Vision using XDA App
deleted.....
woa.. just another cyanogen copy
For those having problems with Gapps on newer htc phones like g2, mt4g and desire hd try the new gapps I have posted up at http://gridlock.euroskank.com and grab the EMMC ones
Everyone else can grab the MTD gapps
This should remove having to mount /system in recovery but run fix permissions in the advanced section of the recovery just in case
Sent from my HTC Vision using XDA App
Midian666 said:
woa.. just another cyanogen copy
Click to expand...
Click to collapse
It isn't one bit at all a copy, just doing the service of basicly compiling the cm7 source just like a nightly untill buildbot is back building them (should be after a official rc1 release) and sharing
Sent from my HTC Vision using XDA App
Build #14 will be up on http://gridlock.euroskank.com within minutes. This should have a fix for data, if so thanks to phunkycow for the fix
Sent from my HTC Vision using XDA App
nice... auto-nightly builds of cm7... how i missed that
whats cwm3 originate from? is there also a changing codebase, or is this a static build, which wont change at all?
mad-murdock said:
nice... auto-nightly builds of cm7... how i missed that
whats cwm3 originate from? is there also a changing codebase, or is this a static build, which wont change at all?
Click to expand...
Click to collapse
There isn't any nightlies that I know of! Cwm3 is the recovery that is in the cm7 source code and it builds a recovery for the device that you compile for. Only when someone changes something in the recovery does it change
Sent from my HTC Vision using XDA App
Why are we unable to flash G-Apps with older recoveries?
Thanks for the effort, it's great to see some progress on this front!
bemymonkey said:
Why are we unable to flash G-Apps with older recoveries?
Thanks for the effort, it's great to see some progress on this front!
Click to expand...
Click to collapse
Once you flash a cm7 source based rom the system becomes ext4, other roms/cm6 are only ext 4 so in order for the /system to mount in recovery for making nandroid backups or to flash anything it needs to have a recovery that can support ext4, which currently is the recovery posted with these builds which is based on clockworkmod recovery because koush hasn't released a official recovery yet (also since it is unofficial rom manager does not support it, so everything has to be done manually in the recovery)
Sent from my HTC Vision using XDA App
Hello everyone?
I posted a while back here if there was a possibility of seeing an AOKP port for this awesome device. but I got no answer from anyone
So I figured maybe its time to learn how to do it myself and contribute to the community here.
My question is where can I learn to start porting? It can't be rocket science. I've been observing the cm9 port for some time before the official ics was out. And it went from a non useable rom to a full daily driver in a few days after the release of the official ics. So I was thinking maybe we could get the same results with AOKP? I'm hoping someone can point me at the right direction that's all.
Thanks.
MacZzang said:
Hello everyone?
I posted a while back here if there was a possibility of seeing an AOKP port for this awesome device. but I got no answer from anyone
So I figured maybe its time to learn how to do it myself and contribute to the community here.
My question is where can I learn to start porting? It can't be rocket science. I've been observing the cm9 port for some time before the official ics was out. And it went from a non useable rom to a full daily driver in a few days after the release of the official ics. So I was thinking maybe we could get the same results with AOKP? I'm hoping someone can point me at the right direction that's all.
Thanks.
Click to expand...
Click to collapse
There are a lot of useful porting guides on the Chef Central sub forum on XDA. There's bound to be an AOKP guide there somewhere. Shouldn't be too hard considering we have CM9 mostly working thanks to locerra and aorth.
Sent from my SPH-L710 using xda premium
Thank you so much! I found a guide it should be what I'm looking for if u come across any other thread I would greatly appreciate it man. I'm gonna start this porting project soon. I just have a question if u have any experiance in this. What's the possible least damage that could come from this? I mean I've seen a few devs in the s2 section that hard bricked their phones testing out ports or something like that. Do u think that's possible? I'm definitely doing this, I just wanna know what might come my way. And thanks again
MacZzang said:
Thank you so much! I found a guide it should be what I'm looking for if u come across any other thread I would greatly appreciate it man. I'm gonna start this porting project soon. I just have a question if u have any experiance in this. What's the possible least damage that could come from this? I mean I've seen a few devs in the s2 section that hard bricked their phones testing out ports or something like that. Do u think that's possible? I'm definitely doing this, I just wanna know what might come my way. And thanks again
Click to expand...
Click to collapse
I have some experience with porting. And from what I've experienced, I've never had an actual "hard brick". I've done builds in which the device doesn't boot or boot loops but a clean Odin flash or backup usually fixes those soft bricks. I think the big thing to really worry about is the partition mounting bug that's been affecting galaxy devices with ICS. Those have been known to hard brick devices with seamlessly simple tasks, such as, using Odin, or even as flashing a ROM.
Sent from my SPH-L710 using xda premium
Ceelos09 said:
I have some experience with porting. And from what I've experienced, I've never had an actual "hard brick". I've done builds in which the device doesn't boot or boot loops but a clean Odin flash or backup usually fixes those soft bricks. I think the big thing to really worry about is the partition mounting bug that's been affecting galaxy devices with ICS. Those have been known to hard brick devices with seamlessly simple tasks, such as, using Odin, or even as flashing a ROM.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Hmmm it dose sound kinda scary... but what the hell I'm determined to get this done I've flashed maybe hundreds of roms to so many different devices, and I'm glad I never had any problems. I'm just a bit worried beacuse this is a rom I messed with and I'm not quite sure I'm any good at this yet seeing that htis is my first time ever messing around like this... Hay if it's alright with you, I would like to ask you a favor seeing that you have some experience in porting. I started the whole porting thing, and I followed a few guides here and there. I put together the rom but it hangs at the boot animation after about two mins...? give or take. I made a logcat and I was wondering if you could take a look at it if you don't mind I would greatly appreciate any input
thanks again!
Oh here's the link to the logcat
http://pastebin.com/10X2MWNw
MacZzang said:
Hmmm it dose sound kinda scary... but what the hell I'm determined to get this done I've flashed maybe hundreds of roms to so many different devices, and I'm glad I never had any problems. I'm just a bit worried beacuse this is a rom I messed with and I'm not quite sure I'm any good at this yet seeing that htis is my first time ever messing around like this... Hay if it's alright with you, I would like to ask you a favor seeing that you have some experience in porting. I started the whole porting thing, and I followed a few guides here and there. I put together the rom but it hangs at the boot animation after about two mins...? give or take. I made a logcat and I was wondering if you could take a look at it if you don't mind I would greatly appreciate any input
thanks again!
Oh here's the link to the logcat
http://pastebin.com/10X2MWNw
Click to expand...
Click to collapse
hmmmm...I *might* know whats causing the problem. Any way you can upload and link to the build you made?
Edit: I'm gonna get my environment set up and try building it. Its been a while.
Ceelos09 said:
hmmmm...I *might* know whats causing the problem. Any way you can upload and link to the build you made?
Edit: I'm gonna get my environment set up and try building it. Its been a while.
Click to expand...
Click to collapse
hmm where can I upload the file? should i like split the file into parts and email them? it would be around five parts.. or should i use one of these file hosting sites? so from what you see is it something big or is it a simple problem?
and again thank you so much
Edit: someone just looked at my logcat from the thread with the guide and said that it was a framework issue, here
E/JNIHelp ( 3712): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 3712): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
could the problem be from the PowerManagerServise? ill try swapping that file and using the one from the base rom and see what happens
MacZzang said:
hmm where can I upload the file? should i like split the file into parts and email them? it would be around five parts.. or should i use one of these file hosting sites? so from what you see is it something big or is it a simple problem?
and again thank you so much
Edit: someone just looked at my logcat from the thread with the guide and said that it was a framework issue, here
E/JNIHelp ( 3712): RegisterNatives failed for 'com/android/server/PowerManagerService', aborting
F/libc ( 3712): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
could the problem be from the PowerManagerServise? ill try swapping that file and using the one from the base rom and see what happens
Click to expand...
Click to collapse
Hold off on uploading it, I'll try n compile a build myself within the next couple days. As for the error which libandroid_runtime.so were u using? If u were using the base one, try replacing it with the CM one. I'll have to take a closer look at the log later
Edit: Should have all my build environment and sources synced sometime around mid-week, at the latest. Had to juggle some partitions around and reinstall Linux. Any progress on your end lately?
Sent from my SPH-L710 using xda premium
Ceelos09 said:
Hold off on uploading it, I'll try n compile a build myself within the next couple days. As for the error which libandroid_runtime.so were u using? If u were using the base one, try replacing it with the CM one. I'll have to take a closer look at the log later
Edit: Should have all my build environment and sources synced sometime around mid-week, at the latest. Had to juggle some partitions around and reinstall Linux. Any progress on your end lately?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
well I'm not any good at linux or and kinda programming sadly but I've been trying different galaxy s2 roms ive tried swapping around hundreds of different files but to no prevail .. I cant get passed the boot screen. I've done numerous logcats and they all seem to have the same error... but the number after the F/libc keeps changing... is there anything i should learn so that I can be of real help? besides just swapping files
MacZzang said:
well I'm not any good at linux or and kinda programming sadly but I've been trying different galaxy s2 roms ive tried swapping around hundreds of different files but to no prevail .. I cant get passed the boot screen. I've done numerous logcats and they all seem to have the same error... but the number after the F/libc keeps changing... is there anything i should learn so that I can be of real help? besides just swapping files
Click to expand...
Click to collapse
I've tried compiling it from source but get an error when trying to compile the kernel. I'm looking into it right now. Just seems to be missing some base files.
Also, by Galaxy S2 ROMs you mean AOKP based ROMs, right? As far as I know, in order to understand and fix most issues you'll need to learn some C programming, along with some python. Porting with wizip requires just a basic understanding of the Android files. (framework, libs, etc.) a user named xboxfanj has ported alot of ROMs, you can ask him for some insight. Marcusant is another user whose ported a lot as well, but they easily have more insight in this than I do.
Edit: asked xboxfanj for some insight, here's what I got:
"What did you do to port this? The method I recommend is first delete everything in the aokp zip besides the system folder and then copy everything besides system from cm to aokp. Then copy the tab's system/build.prop and etc and vendor and firmware (if there is a folder for that) folders. Also copy the lib/hw and lib/egl folders from cm to aokp. I'm not sure if you're talking about the galaxy tab 2 7" or the original galaxy tab, but either way, go to github.com/themuppets/proprietary_vendor_samsung
If you have the original gtab, go to the p1 and p1 common folders. If you have the new one, go to p31xx in the common folder. You can download it as a zip by clicking zip on the webpage. Then you can just drag and drop the files. After that, copy bin/rild bin/pppd (if its there) lib/libril lib/libsec-ril and lib/libsecril-client. I recommend porting from the kindle fire if you have the tab 2 7" since that device has the same resolution.
Not much is given away by your original logcat. Maybe try a different libandroidruntime (if you were using your cm one, use the aokp one, if you were using the aokp one, use the cm one).
Another method you could use is copy app, framework, and media from the aokp zip to the cm zip (delete those folders from cm first)."
Sent from my SPH-L710 using xda premium
Ceelos09 said:
I've tried compiling it from source but get an error when trying to compile the kernel. I'm looking into it right now. Just seems to be missing some base files.
Also, by Galaxy S2 ROMs you mean AOKP based ROMs, right? As far as I know, in order to understand and fix most issues you'll need to learn some C programming, along with some python. Porting with wizip requires just a basic understanding of the Android files. (framework, libs, etc.) a user named xboxfanj has ported alot of ROMs, you can ask him for some insight. Marcusant is another user whose ported a lot as well, but they easily have more insight in this than I do.
Edit: asked xboxfanj for some insight, here's what u got:
"What did you do to port this? The method I recommend is first delete everything in the aokp zip besides the system folder and then copy everything besides system from cm to aokp. Then copy the tab's system/build.prop and etc and vendor and firmware (if there is a folder for that) folders. Also copy the lib/hw and lib/egl folders from cm to aokp. I'm not sure if you're talking about the galaxy tab 2 7" or the original galaxy tab, but either way, go to github.com/themuppets/proprietary_vendor_samsung
If you have the original gtab, go to the p1 and p1 common folders. If you have the new one, go to p31xx in the common folder. You can download it as a zip by clicking zip on the webpage. Then you can just drag and drop the files. After that, copy bin/rild bin/pppd (if its there) lib/libril lib/libsec-ril and lib/libsecril-client. I recommend porting from the kindle fire if you have the tab 2 7" since that device has the same resolution.
Not much is given away by your original logcat. Maybe try a different libandroidruntime (if you were using your cm one, use the aokp one, if you were using the aokp one, use the cm one).
Another method you could use is copy app, framework, and media from the aokp zip to the cm zip (delete those folders from cm first)."
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Ok I've downloaded a bunch of different roms for a number of devices (nexus S, galaxy s2, galaxy s, galaxy tab p1,s2 at&t, tab 2 7.0) but this time they are all pure AOKP builds not that they weren't before but they were all custom. I'm gonna try out the two methods you just mentioned and see what happens. ill try to reach Marcusant sense you already reached xboxfanj. I'll try to start learning some C and python and hopefully i can learn enough in time to actually be able to do something here. so what do you do for a living man are you a programmer?
MacZzang said:
Ok I've downloaded a bunch of different roms for a number of devices (nexus S, galaxy s2, galaxy s, galaxy tab p1,s2 at&t, tab 2 7.0) but this time they are all pure AOKP builds not that they weren't before but they were all custom. I'm gonna try out the two methods you just mentioned and see what happens. ill try to reach Marcusant sense you already reached xboxfanj. I'll try to start learning some C and python and hopefully i can learn enough in time to actually be able to do something here. so what do you do for a living man are you a programmer?
Click to expand...
Click to collapse
You might wanna port mainly from the Galaxy S2, seeing as how we have more in common with them hardware wise.
And no. I'm about to start my college classes next month at DeVry. Gonna do their Computer Engineering course. I don't know much but as soon as class kicks in, I'm hoping it'll kick start my development here on XDA. For the time being, I usually lurk around n help. Maybe learn a thing or two by reading a random thread or guide.
Sent from my SPH-L710 using xda premium
Well things don't look so good from my end... I've put together about 16 different roms and they all won't go past the boot screen. And the galaxy s2 roms kept giving me the same fatal error... I'm hitting a wall here I don't know what to do.. I'm guessing we just have to get our hands dirty with this one.. I'm doing some reading on python and c hopefully I can figure this out...
So ur a student? That's cool I wanted to learn program and computer engineering before I got into university
Sweet God Almighty, if we got AOKP on this thing I... I... well... I think I might just cry for joy. :crying:
Hahahaha yeah same here I love AOKP based roms, they have more options! And aokp has a unicorn! But sadly we have been trying here for a few days and well I'm not really a Dec I'm just following porting guides and tutorials around xda trying out different things here and there hoping we can get passed the boot screen. Would definitely appreciate your help
Been having some trouble setting my build environment up, so I'm currently seeking some help from others who have experience building AOKP from source. Hopefully they can guide me through it and I find what I did wrong
Sent from my SPH-L710 using xda premium
AOKP == CM
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
I figured you wouldn't be interested aorth I don't blame you. I have little experience in this and figured I'd hop in and see if I could do get it going but the Yamaha audio issue seems to come up in every logcat I take as well.
Sent from my SPH-L710 using xda premium
aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
Aorth u broke my heart man I actually had lots of hope that this can be pulled off... so you're saying this is impossible to do? I like aokp because if the rom control menu I feel it has more options and customization. But cm9 is great too. Thank you so much for all the hard work u have put into bringing cm9 to our awesome tabs
Ceelos09 said:
I figured you wouldn't be interested aorth I don't blame you. I have little experience in this and figured I'd hop in and see if I could do get it going but the Yamaha audio issue seems to come up in every logcat I take as well.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Yeah I saw the Yamaha audio thingie too...? What's the problem? Is that a driver thing or something else? From the way you both mentioned it I'm guessing its something serious.. ?
Sent from my GT-P6200 using xda premium
aorth said:
Android Open Kang Project is basically CyanogenMod. Minus some features. I have no interest in seeing AOKP on this device. Sorry. Any optimizations AOKP could bring would already be in CM.
For what it's worth, I did get a device tree configured which can build AOKP, but it didn't boot (stuck at boot animation, logs complaining about yamaha audio). That was in July, and I never went back to it.
Click to expand...
Click to collapse
Curious, what can CM do feature wise that AOKP can't?
I can think of quite a few that AOKP can do that CM can't.
Posted from my Galaxy S III.
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
androiddecoded said:
This might be a noob question, but I want to know that since our bootloader is locked, how we are able to port Cynaogenmod and other ROMs like Paranoid Android to Atrix 2? Recently official AOSP ROM was released for Moto RAZR which also has a locked bootloader. So why we can't have an official CM for Atrix 2?
What difference is there between a CM port and an official CM for unlocked bootloader device ?
Just some noob questions which came in my mind. Please clarify. Sorry for a silly question.
Click to expand...
Click to collapse
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
alteredlikeness said:
Actually, it looks like Hashcode and dhacker recently got the RAZR included in the "official" CM nightlies... http://wiki.cyanogenmod.org/w/Spyder_Info
So, if something stable enough is worked out for the A2 (i.e. kexec), then we could possibly see an "official" edison of some sort at some point... in theory.
For now, I'll be happy with stable "unofficial" builds..
Click to expand...
Click to collapse
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
jimbridgman said:
That is still not considered "official" cyanogen builds.....
If it is not listed here, then it is not 100% official:
http://get.cm
It is lets say.... an unofficial, "official" build, though. LOL
Click to expand...
Click to collapse
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
alteredlikeness said:
Um, Jim.. spyder and umts_spyder are both listed there
Still, I think Hashcode and dhacker have the status/connections to get it dubbed "official"..
Click to expand...
Click to collapse
so do I.... Don't forget who is on the cm coding team....
I did some looking internally at CM and found that these are semi-official, right now, with a big but, the kexec I am told is what is keeping it with the semi status...
They are looking into changing that for kexec based compiles, so.... Hopefully, that happens.
jimbridgman said:
It all surrounds around the kernel. Unlocked bootloader devices can run "custom" compiled kernels, and CM and the other "custom" non-stock based roms all have their own kernels too.
The reason that we can run "unofficial" versions is because your devs (me included), have to compile the ROM around the "stock" kernel, so that it can be installed right along side the stock kernel, and run without issue. All of the AOSPA, and PA, and such are the same exact way.
Anything that can be done on the Razr can pretty much be done on this phone. The thing is that your dev team is much smaller on the A2 as it was not a very popular device, so it takes longer if ever to get something since the devs make the choice to work on a specific ROM or not.
Also the "official" CM compiles are done by the cyanogen mod team themselves and they do all the coding and have an auto compile server to get the versions out to the public, so again it is up to the developers there to decide which phones they want to support. Again though if you look all the "official" build devices ALL have unlocked bootloaders in some form or fashion, so that the "custom" compiled kernel will install with out issue.
Click to expand...
Click to collapse
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
androiddecoded said:
Thanks for the reply. I wish I could also develop something for Atrix 2. But I am not familiar with the development. How is it done? and where do you test it and all other things? Is there some starting tutorial there for it? Or maybe some place from where you all guys started learning the developement?
Click to expand...
Click to collapse
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
I don't want to be the antagonist here , but I did everything in Windows until I started my attempts at building from source.
Dsixda's kitchen works fine in Windows with Cygwin. I started off building pseudo-ROMs (or rebuilding the stock ROMs) with the kitchen, and then I eventually just used 7-zip and other tools and did it manually.
I currently use Ubuntu 12.04 64-bit in Virtual Box in Windows on my laptop to compile from source. But I did just install 12.10 fully on my old PC... 32-bit unfortunately.. I need to upgrade that comp, or find a work-around to build in 32-bit.. Anyhow, it runs much nicer than windows xp did.
Sent from my paranoid phone's mind
jimbridgman said:
I would start with my thread for all the tools you need.
http://forum.xda-developers.com/showthread.php?t=1404442
Then you can start with taking a shot at a stock based ROM, since they really are the easiest place to start. You will need some form of linux ubuntu is really the most supported distro for android dev work, so that is a good start. This can be a VM to start out with, you can use a free VM tool like virtual box, if you want to just to give it a try, but I will tell you a dual boot works much better, and I will be honest I have a machine that just uses ubuntu and does not run windows at all. I have a wine install for things like netflix and such, but other than that.... no windows. That is just me though.
The key is the android kitchen... and that ONLY runs on linux, that where you build your ROM at. There are guys like rdavisct, who do it on windows, but even he would tell you how much of a PIA it was for him, and he did eventually go to ubuntu with my help.
After that you can start to look at compiling roms like CM, aospa, and the like.
Click to expand...
Click to collapse
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
androiddecoded said:
Thats awesome. I have both Red Hat and Ubuntu installed. What about the testing? After compiling do you test it directly on your Atrix 2? I have only one mobile and am afraid to test it directly on it. :crying:
Click to expand...
Click to collapse
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
Thanks sir. Got that
Will try to contribute something if I can. Kudos to our dev team. You guys are doing a great job. Happy to be a part of a great community
jimbridgman said:
Yes, that is the only way. That is why you have the fxz and rsd lite handy and ready, just in case. 20 min. and you are back up and running. If you are concerned go buy a 10-40 buck "burner" at Walmart and put your sim in it, for while you test. I am lucky that I still have my HTC hero lying around for just that purpose... Every time I bricked my a2 (doing bootloader work), that was my go to backup.
I never needed it while doing ROM work, because the worst that will happen is boot loops/soft brick, it is nearly impossible to hard brick the a2 testing a ROM that does not have a kernel in it.
Click to expand...
Click to collapse
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
androiddecoded said:
I took the Paranoid Android ROM from this page for practice. http://forum.xda-developers.com/showthread.php?t=2050705
I extracted it using Android Kitchen, but it says boot.img not found. Do we need to add boot.img from our phone or its not needed since we have a locked bootlader. Or should I take stock Atrix 2 ROM?
Click to expand...
Click to collapse
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
I will do it tomorrow. Really thank you for assisting me.
jimbridgman said:
Ok, so you need to let the kitchen create or import a "fake" one, as the kitchen was originally made for like samsung and htc phones and they require one, so the kitchen needs one, it will remove it when it builds the ROM and creates the zip file.
Also make sure you have the edison file, that was listed and where to put it was also listed in my thread on ROM building for the A2. That will help you create a proper updater-script when it builds the ROM, as well as give the proper mapping for our partitions on the A2.
Click to expand...
Click to collapse
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
androiddecoded said:
One more doubt. I am building ROM from already built ROM i.e. the zip is already compiled, so how can I fix bugs like camera bugs and other things because they are already compiled i.e. in the form of apk.So should I use APK tool which is used to decompile the apk? Is there any difference while creating a ROM from source and creating it from already compiled zips.?? Silly question but I want to clear all these doubts
I downloaded the leaked 4.1 for Atrix 2. But I can't see the same folder format in that like system, META-INF? Why is that difference
Click to expand...
Click to collapse
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
jimbridgman said:
The issues for the camera are NOT in the apk itself, they are in the vendor libraries, the issue is that when vendor libraries are introduced for certai n things the ROM does not boot.
The best bet until you get better at C code and compiling ROMS, I would not mess with that. You can however build a working CM10.1 with a working camera by using a camera apk from the market, like 360 camera, and there are a few others, you can just drop that into /system/app and build the ROM and it should work for you.
Once you complie CM there is not much you can fix like that, rdavisct and I were doing just that until Wang released his source for the required A2 files (we did find a lot of issues and fix them, but they were actual missing libs and similar back then., It really is a lost cause to use the zip to "fix" "real compiled in bugs, because anything you do like that will not have the needed pieces compiled around it, some libraries will not work right since others that are from CM were not compiled around the ones from the phone, and think that they are part of the CM code, and are not "includes" in the compile.
You can however do a lot of customizing to the ROM to fit YOUR needs, but do not expect to fix any issues this way. Like I mentioned the camera is an easy one, you then just go to settings tell it your "default" camera app is the 360 camera, not the stock CM one.
Click to expand...
Click to collapse
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
4.1 leak is not a flashable zip.
The meta-inf folder items are for zips that are flashed in recovery.
And, not to dissuade you from jumping in to modding/dev'ing, but you may want to take things a bit slower... Start small.. And read/research a lot.
Sent from my paranoid phone's mind
androiddecoded said:
Oh, ok. So can I try removing Moto Homescreen app and setting Nova Launcher as default?
And why is the difference between files between Moto 4.1 leak and Paranoid Android ROM. The regular mapping of folder is not there like META-inf , /system etc..
EDIT: I think I got it. Leaked Moto 4.1 is fastboot file and PA is flashable zip. I think I am right. Can I get the zip for Moto 4.1 leak?
Click to expand...
Click to collapse
No, there is not a flashable "zip" for the Moto 4.1 leak, you will have to build that on your own with the Rom kitchen, since it is an FXZ, it will not have those flashable parts. The kitchen is very easy to use, it is menu driven and only takes about 30 min to an hour to do what it seems you want to do.
You can replace the launcher from within a flashable zip, but you might have issues, because the MOTO blur junk that is in their ROMS DEPENDS on it, if you do NOT leave it (moto blur launcher) in /system, then a number of things will not work that depend on the moto launcher (they are embedded in the xml files in the apks, and need to be edited to NOT look for the moto laucher), I think it is more trouble than it is worth, personally.
I would throw Apex in there if that is what you want, and then on first boot select it as your default launcher and be done with it, less issues and mess, other than the old moto launcher taking space in /system. BY the way ANYTHING that you put in /system is not really 100% upgrade-able by the market app, so like lets say you put apex in /system, then the market can not update the version in /system, since it is read only, and it will either fail the update, or try to put the newer updated files /data, so you will have things in two places for your 3rd party launcher. It is MUCH better to put any APKS that would come from the market into /data so they can get updates with out any odd issues, just a heads up...
--EDIT--
As alteredlikeness said about the same time I was posting, start a little smaller, and do a bunch of learning, because from what I see you asking about and posting in here, you have a good bit of learning to do, about how the directory structure and things are and work in android, as well as some ROM building basics.
Hi. As you propably know, there is no TWRP 2.7 for saga. This is why:
Saga would need a number of updates in order to make it work with 4.4 Kit Kat ROMs. 4.4 ROM support really doesn't depend on the recovery itself. The kernel and other parts of the ramdisk have to support SELinux contexts in order for the set_metadata functions to work. I don't have a saga myself and at this point I have no plans to continue to support the device. I've been building saga in a CM7 / gingerbread tree which doesn't support the things needed for SELinux. The device would need to be compiled with an updated kernel in at least a 4.1 and preferably a 4.3 or 4.4 tree to support installing Kit Kat ROMs.
I plan to drop official support for any device that I've been building in ICS or Gingerbread trees which includes saga. If people want to see continued support for those devices, then hopefully developers for those devices will step up and build TWRP themselves and maybe offer their updated device files to us so that we can extend official support.
Click to expand...
Click to collapse
So basically we need developers who would like to help with that. I'm not that techy to understand what the problem is but I would like you to tell me and help.
BTW! Why our device is not available in DevDB! How do we change that?
Hm. I might take a shot at this. Though I personally prefer 4ext
devil-kin said:
Hm. I might take a shot at this. Though I personally prefer 4ext
Click to expand...
Click to collapse
It would be really splendid thing to do sir
Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.
devil-kin said:
Got it to build, just not to boot. I guess a black screen is no use to anyone
Will fiddle some more with it.
Click to expand...
Click to collapse
That's great! It would be even better if you could somehow share some of your work here so maybe someone else could take a look (i don't know if it's possible. But you use github right?) I would love to add this project to DevDB but it seems that our phone is not there and i don't know how to add it.
My github repos are at https://github.com/jdeluyck - I haven't uploaded anything yet save for the changes to the repo file to pull in TWRP.
Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know
PERFECT!
devil-kin said:
Here ya go, first build of TWRP 2.7.0.0 for Desire S, which seems to work
Please test and let me know
Click to expand...
Click to collapse
I flashed it, I backed up my rom, I wiped, I flashed my rom clean, it booted, I went to recovery and I restored my rom. Everything went perfect, no problems whatsoever! Now there are 2 questions left to ask.
1. May I update TWRP for saga developement thread and attach this build?
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Anyway great work devil-kin :highfive: Personally I see TWRP as the best recovery and I'm on it from 2.2. Seeing it still working in its latest iteration on my beloved DS makes little tears appear in the corners of my eyes. I absolutely love this phone for it's size, specs, build quality and weird survability (many screen to sidewalk encounters and no broken glass Only praiseworthy scars). LONG LIVE DS! <3
VnnAmed said:
1. May I update TWRP for saga developement thread and attach this build?
Click to expand...
Click to collapse
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
VnnAmed said:
2. Would you be willing to offer updated device files to TWRP team? From my observation most people download TWRP drom official website and it would be great if 2.7 would make an appearance there.
Click to expand...
Click to collapse
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?
devil-kin said:
Sure. I'm even willing to offer up new updates as long as I got a working CM tree to base it off.
Sure - the device files can be found at https://github.com/jdeluyck/android_device_htc_saga
Do I have to send them to anyone specific?
Click to expand...
Click to collapse
Thank you very much If you could, i would like you to PM Dees_Troy and tell him that you have succesfully compiled 2.7 for saga, so if he has some more technical questions you can answer them I'm updating TWRP for saga thread right away
Could multirom be ported to OPO users?
Would be so awesome for 64gb version !
Cheers
You must ask Tassadar, multirom creator, who will confirm (or not) if hardware is compatible
IF it is, we will have to wait for a compatible kernel
Also interested in seeing a Multirom port.
Would be interested as well. So @Tasssadar, can you help here?
EDIT: Just did a quick read on the wiki... Looks like we should be able to port it ourselves. Maybe I'll look into it when I find some time. But everyone is invited to do so as well!
EDIT2: See here: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROM
As in FAQ:
Will you port MultiROM to device X?
No, probably. I won't port MultiROM to any device I don't own, because it is very difficult to provide the level of support I want to provide if I can't test things myself, as proven by the Nexus 4 port. I'll probably keep buying Nexus devices and keep porting MultiROM to those myself, but I can't buy every single device - I'm still a student, all my existing devices were bought using some kind of money grant or donations from users.
But, you can port it yourself, the wiki should give you at least some idea how to do that: https://github.com/Tasssadar/multirom/wiki/Porting-MultiROMtl;dr: get me the device or port and maintain it yourself.
I won't know how "hard" (what does that even mean?) it is to port MultiROM to X until I have the device in my hands, but it should be possible. I see you've already found the wiki, there's a bit of info about porting there. Kexec-hardboot patch will be the "hardest", since you need to know a bit about how linux boots on ARM devices. Or just blind guessing, that seems to work for some people too.
Tasssadar said:
As in FAQ:
tl;dr: get me the device or port and maintain it yourself.
I won't know how "hard" (what does that even mean?) it is to port MultiROM to X until I have the device in my hands, but it should be possible. I see you've already found the wiki, there's a bit of info about porting there. Kexec-hardboot patch will be the "hardest", since you need to know a bit about how linux boots on ARM devices. Or just blind guessing, that seems to work for some people too.
Click to expand...
Click to collapse
Thanks, luckily I know some things about this already. So shouldn't be that hard for me. Hardest thing will be to find time to actually do it. As this device don't have an sdcard, that part is already covered. I do however have to take a look at the ramdisk for that patch...
Tasssadar said:
tl;dr: get me the device or port and maintain it yourself.
I won't know how "hard" (what does that even mean?) it is to port MultiROM to X until I have the device in my hands, but it should be possible. I see you've already found the wiki, there's a bit of info about porting there. Kexec-hardboot patch will be the "hardest", since you need to know a bit about how linux boots on ARM devices. Or just blind guessing, that seems to work for some people too.
Click to expand...
Click to collapse
Well if I win one I'll give it to you. Its the least I could do for all the great work you do for the community!
Thanks Tasssadar!
lol, I was just about to post about this. From what I remember the Devs for each of the other kernels just have to add in the multirom code in to their kernel for multirom support. Pretty easy from what I heard. Otherwise I reached out to the dev for multirom today to see if this will be coming to OPO.
synergeticink said:
lol, I was just about to post about this. From what I remember the Devs for each of the other kernels just have to add in the multirom code in to their kernel for multirom support. Pretty easy from what I heard. Otherwise I reached out to the dev for multirom today to see if this will be coming to OPO.
Click to expand...
Click to collapse
I already did this in the posts above... He won't support it himself, but we can port it ourselves. Looks not that hard.
Sent from my One using XDA Premium 4 mobile app
I'd love to see MultiRom on the OnePlus One as well. If someone could port it, that would be amazing!
Well it would be simply great
I've almost finished MultiROM port to the OPO. Just a few framebuffer things to fix
KINGbabasula said:
I've almost finished MultiROM port to the OPO. Just a few framebuffer things to fix
Click to expand...
Click to collapse
Awesome! Can't wait to see instructions to do this.
KINGbabasula said:
I've almost finished MultiROM port to the OPO. Just a few framebuffer things to fix
Click to expand...
Click to collapse
Impressive !
If you got a working version, that "donate to me" button of yours will be pressed
KINGbabasula said:
I've almost finished MultiROM port to the OPO. Just a few framebuffer things to fix
Click to expand...
Click to collapse
Great! Thanks for your awesome help.
Ok, so MultiROM works, TWRP works, kexec works BUT the boot menu is not visible (it's working but it shows completely black) still framebuffer problems. I can set the main ROM from TWRP and it gets booted correctly. So the last thing to fix is just the boot menu. It's completely usuable anyway from the recovery
sorry for the noob questions, i am not "inside" the multirom project...
will the installed roms share the same data partition...so you can switch between roms keeping everything else is installed on device?
No, this is not possible atm (if it's the same as for N5)
But the main advantage of multirom is for me: testing ROMs without loosing your daily driver. If you like the new rom, install your stuff and swap it to primary
beren said:
sorry for the noob questions, i am not "inside" the multirom project...
will the installed roms share the same data partition...so you can switch between roms keeping everything else is installed on device?
Click to expand...
Click to collapse
I confirm the data partition cannot be shared
@KINGbabasula :
You should already tell the kernel dev to include the k-exec boot patch, so we won't have to wait ages to have a compatible Kernel
@ak is very responsive for features requests
bud77 said:
I confirm the data partition cannot be shared
@KINGbabasula :
You should already tell the kernel dev to include the k-exec boot patch, so we won't have to wait ages to have a compatible Kernel
@ak is very responsive for features requests
Click to expand...
Click to collapse
Sure. I tested mahdi and slim rom and they work perfectly sharing my kexec'd kernel. PA sadly still doesn't because they use cm11s kernel so I can't set shared kernel (in short it's impossible to use it until they merge kexec patch). Anyone who wants to merge it in their kernel it's here: https://github.com/KINGbabasula/and...mmit/3e93ccd23a37cc5fa3140fc935a43362a678de37 and to enable it add this in defconfig:
CONFIG_KEXEC=y
CONFIG_KEXEC_HARDBOOT=y
CONFIG_PROC_DEVICETREE=y