Well like the title says I was wondering if we might be able to use kexec to boot cm on our devices. If I'm not mistaken that's what is used for the droid 3 to boot cm
Sent from my SAMSUNG-SM-N900A using Tapatalk
This has been discussed many times here and in multiple other device forums. At this point, it has not been implemented into SafeStrap. I am not sure if it is possible or not, nor do I know if hash is working on putting it in. He is aware of it though.
Sent from my SM-N900A using XDA Premium 4 mobile app
kexec uses a hijacked kernel module to direct to a different kernel placed on the SDcard. Sort of like how SS works, but a bit differently. All SS does is direct the kernel to a different image. Kexec needs a hijacked module to load an insecure kernel. While this sounds easy to implement, trust me it will most likely never happen with the note 3. The problem is that the note 3 doesn't have any modules. And don't ask about inserting them, because the kernel will not run them. They are completely disabled in this kernel. That property is set when the kernel is compiled, so with it being disabled, we cannot enable it, and we cannot hijack the modules, because they are completely disabled.
Thanks for your informative reply. Just thought id ask
Sent from my XT862 using Tapatalk
Related
Going to try this on the D3, its big in the fascinate world. May be worth a dev porting to the D3 specifically. I'm going to take the plunge though since we can do nandbackups.
http://forum.xda-developers.com/showthread.php?t=1236779
From the thread post:
Whats inside:
changed partition mounts--- for less data corruption
patched sqlite's----IMPROVES I/O
honecomb 3.1 fugu mod-IMPROVES SCROLLING/RESPONSIVENESS
All new init.d files---PARTITION MOUNTS,CACHE,SYSCTL,KERNEL
Sysctl.conf----TWEAKS KERNEL AND I/O SCHEDULER
tweaked scaling governor----faster cpu performance
It has been reported to work on the Motorola Atrix, so that gives me hope for some additional improvements on the D3.
Sweet! Let us know how it works!
sent from my MONSTERDroid3 from the XDA app
Izeltokatl said:
Going to try this on the D3, its big in the fascinate world. May be worth a dev porting to the D3 specifically. I'm going to take the plunge though since we can do nandbackups.
http://forum.xda-developers.com/showthread.php?t=1236779
From the thread post:
Whats inside:
changed partition mounts--- for less data corruption
patched sqlite's----IMPROVES I/O
honecomb 3.1 fugu mod-IMPROVES SCROLLING/RESPONSIVENESS
All new init.d files---PARTITION MOUNTS,CACHE,SYSCTL,KERNEL
Sysctl.conf----TWEAKS KERNEL AND I/O SCHEDULER
tweaked scaling governor----faster cpu performance
It has been reported to work on the Motorola Atrix, so that gives me hope for some additional improvements on the D3.
Click to expand...
Click to collapse
So...howd it go?
evulhotdog said:
So...howd it go?
Click to expand...
Click to collapse
Perhaps not so well?
Sent from my DROID3 using xda premium
I have this mod applied on my mytouch 4g, made a big difference. Hope it works out for this device as well..
Wolfhere said:
Perhaps not so well?
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I'm gonna test this myself in a few hours. Ill report back
Sent from my DROID3 using XDA App
Maybe his phone ripped a hole in space-time; He was sucked into another dimension.
Bobbar said:
Maybe his phone ripped a hole in space-time; He was sucked into another dimension.
Click to expand...
Click to collapse
Worst that happens is a bootloop and then you just boot into recovery and restore /system and you're back in business
Sent from my DROID3 using XDA App
erismaster said:
Worst that happens is a bootloop and then you just boot into recovery and restore /system and you're back in business
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I looked throught the zip. It contains some files that the D3 doesnt have (or are in a different location). So some of the changes will probably do nothing.
Check out the newest from Hashcode. You can now restore from BP Tools. No need to flash and restore
Sent from my DROID3 using xda premium
Wolfhere said:
Check out the newest from Hashcode. You can now restore from BP Tools. No need to flash and restore
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
The .zips fail to install so this won't work on our phones. Not without tweaking.
And that's been out for over a week. I updated my recovey thread with it last week.
Sent from my DROID3 using XDA App
erismaster said:
The .zips fail to install so this won't work on our phones. Not without tweaking.
And that's been out for over a week. I updated my recovey thread with it last week.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I install the files inside the ZIP manually, it works out perfect and seems much smoother and with a better memory management now.
jchenny said:
I install the files inside the ZIP manually, it works out perfect and seems much smoother and with a better memory management now.
Click to expand...
Click to collapse
Did you do anything with the sysctl.conf and init.d?
Sorry for the delays... yes, as stated above, the zip files will not flash to the D3 (even though they do flash to the Moto Atrix??).
But you can definitely rip out files push them with Root Explorer or ADB commands. I haven't had time to mess with that but I may jump on it later today. Glad someone else tried and showed positive signs. That is encouraging.
I applied manually.
Don't notice any difference, really. But it may respond better to my finger. I'll have to run it for a few days.
Bobbar said:
I applied manually.
Don't notice any difference, really. But it may respond better to my finger. I'll have to run it for a few days.
Click to expand...
Click to collapse
Do we have init.d support? If not the init scripts probably wont do too much.
Willis111 said:
Do we have init.d support? If not the init scripts probably wont do too much.
Click to expand...
Click to collapse
I snatched the files from the latest SteelDroid to enable init.d. However I also used the scripts from that rom as well as they include alot the same tweaks.
I discovered that the sysctl.conf tweaks have no affect. We dont seem to have access to those adjustments. Perhaps because of our stock kernel?
for you, if you have a stock kernel to enable init.d .....
http://forum.xda-developers.com/showthread.php?t=1017291
Will it be a great help for bring the ICS to us?
Check it's out
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
mp9_sit said:
Will it be a great help for bring the ICS to us?
Check it's out
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
No not at all. For 1 our device isn't supported and for 2 we have already figured out a workaround to the locked bootloader
Sent from my XT860 using xda premium
It may not be supported yet but if they do add our phone to it, yes it will help. We may have a Kexec kernel but an unlocked bootloader will make things far easier.
Sent from my XT862 using xda premium
Will for one it says page not found so im saying they are not unlocking the bootloader but it it does not matter because of the fact that we have a workaround.
Sent from my Galaxy Nexus using xda app-developers app
leerpsp said:
Will for one it says page not found so im saying they are not unlocking the bootloader but it it does not matter because of the fact that we have a workaround.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Apparently it got posted and pulled and I think reposted. Android police or droid had the supported device list
Sent from my XT860 using xda premium
If you look here (https://motorola-global-portal.cust...sion/L3RpbWUvMTM0NTI1NDk1NC9zaWQvU3VDYlRZM2w=) only the Photon, Xoom, and RAZR dev can be unlocked. And the RAZR dev should be unlocked anyways... it IS the dev edition. This means nothing, and with working Kexec, I don't see why we'd even change since everything now is being written for Kexec and development for this phone ins't exactly active, we essentially have 2 people developing new things for it. There are more GNex kernels than there are D3 devs.
jesusishere said:
It may not be supported yet but if they do add our phone to it, yes it will help. We may have a Kexec kernel but an unlocked bootloader will make things far easier.
Sent from my XT862 using xda premium
Click to expand...
Click to collapse
At this point what difference can it make. Either way we can load a kernel, just need the kernel to be built
Sent from my XT860 using xda premium
Kexec makes this pointless. The reason development stopped initially was because making a ducati binary work with the Gingerbread stock kernel for ICS was impossible. Also doing a kernel module custom was too. Now even though we have ducati and it won't work for the camera we can do other things like Chrome. Also, Hash was going to modify his custom kernel for a camera driver for us as his next approach. This gives us options we didn't have before. The fact that we use Kexec is better because it is flashed on top of the kernel existing at first and it is just a ROM. If it is a bad flash all you have to do is just reflash from Safestrap. We couldn't do that before.
Sent from my xt862 using xda app-developers app
Hi new Sony user here and I'm just curious as to why we can't use initd scripts to work around this locked boot loader? I owned a Droid 2 global and Motorola has locked boot loaders on them and the devs just used initd scripts to work around this. That is how the Droid 2 guys got cm7. Figured I'd ask and throw the idea out there. I mean it'd give us cm9 or cm10 for now til the locked boot loader issue is figured out.
Afaik initd needs kernel support and the stock kernel doesn't support initd. Therefore, you need a different kernel, and different kernel needs unlocked bootloader.
Sent from my LT30p using xda app-developers app
You could always try to use the pimp my Rom app from the play store to enable init-d. Don't know if it will work though.
You WILL need root for this.
Sent from my LT30p (Xperia T) using XDA Premium.
Did I help? please press thanks button
Yes it does
crazymister said:
You could always try to use the pimp my Rom app from the play store to enable init-d. Don't know if it will work though.
You WILL need root for this.
Sent from my LT30p (Xperia T) using XDA Premium.
Did I help? please press thanks button
Click to expand...
Click to collapse
When you add init.d it also has a verify button to make sure it has worked and also you can check the build.prop
Init.d works on locked bootloader
Envoyé depuis mon LT30p avec Tapatalk
There are limitations to how far you can go with Second Init. If any changes to the kernel are needed you're hosed - and Jellybean requires kernel changes for vsync at a minimum. It also means any kernel issues can't be fixed. Also, as time progresses, bootloader lockdown usually becomes stronger - and Sony's locking solution is quite strong.
It's a ****-ton of work and horrible hacks (I don't think any device using a Second Init approach has EVER received official builds since CM7) which are unnecessary on the majority of T units. Some of us (including myself) refuse to work with devices which have non-unlockable bootloaders on principle.
Sucks for the AT&T TL users, but that's why I'm leaving AT&T. I'm tired of them mangling devices.
morning folks, just looking for a bit of help, just got a nexus 7 week or two ago and am looking to work on my owmn personal mods to kernel etc (probably wont release any as yet) but every boot image i try to flash wont boot at all - even fastboot boot refuses to do anything, any ideas what my issue is
Does not boot...any sign of life after the flash, or does the flash itself fail? I believe you have unlocked the bootloader but it's still worth a check.
bootloader is unlocked yes, if i do fastboot boot boot.img it just sits at bootng downloaded image, if i flash the img it sits at google logo permanently
This is the dev section, threads not related to development does not belong here, questions goes to the Q&A section..
And it seems that you device is done for..
Beamed from my Maguro.
Not really as it is dev related as its related to my own development on the device, its not device as I'm using it now after reflashin 4.3
Sent from my Nexus 7 using Tapatalk HD
Okay the only kernels that will work on 4.3 properly are faux's kernel, vorcer's kernel and Tasssadar's kexec kernel. Others won't work.
Problem is no kernel will boot including on 4.2 it seems like I may not be building boot right or something
Sent from my Nexus 7 using Tapatalk HD
Try the zImage separately. If it works and you still need help creating a boot.img, lemme know.
DJ_Steve said:
Problem is no kernel will boot including on 4.2 it seems like I may not be building boot right or something
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I'm no expert, so I can't help, but it seems like you are being very vague. You do not have any clue as to steps you took that are possibly incorrect? It just seems like you won't get much help if you don't share some details. I could be wrong.
Sent from my Nexus 7 using xda premium
I can share details as needed, not being intentionally vague and have been building kernels for android for some time hence I am pretty experianced but suspect n7 has some slightly different ways of building a working boot IMG than I'm used to
Sent from my Nexus 7 using Tapatalk HD
DJ_Steve said:
I can share details as needed, not being intentionally vague and have been building kernels for android for some time hence I am pretty experianced but suspect n7 has some slightly different ways of building a working boot IMG than I'm used to
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Ahh, sorry then, guess I was just being nosy.
Sent from my Nexus 7 using xda premium
Try what I said. If the zImage works for you then you are aren't packing the boot.img correctly.
Hello DJ_Steve,
Familiar with you from your work on the Dell Streak 7. If you don't find a solution, try the developer only discussion thread here: http://forum.xda-developers.com/forumdisplay.php?f=2071
Looking forward to any work that you may do for the N7.
Mike T
Try erasing boot then flash the stock boot image again?
Sent from my Nexus 7 using xda premium
sgt. meow said:
Try what I said. If the zImage works for you then you are aren't packing the boot.img correctly.
Click to expand...
Click to collapse
I agree.
Flash a stock boot.img for the ROM version you are on then use koush's any kernel method to flash the zImage.
I have an International version of GNote and it does not have an Insane chip i.e. it does not have Brick Bug according to 2 apps (screenshot attached).
So my question is that can I use TRIM to cope up with storage fragmentation or not, as my device has started hanging alot lately and whenever I am over using it, lockscreen gets crashed and I have to reboot the device. It mostly happens playing Real Racing 3 or Dead Trigger 2.
If not, is there any alternative, for defragmentation or to correct this issue.
I am using CM11 KitKat stock Kernel no mod.
Sent from my GT-N7000 using XDA Premium 4 mobile app
You should be able to get past it if you change your build.prop so that you have say... a nexus 4
http://forum.xda-developers.com/showthread.php?t=1948558
EDIT: Also our kernel has this thing disabled by default so you will have to compile your own kernel and change a flag.
EDIT2: Here's the flag you have to disable/enable: MMC_CAP_ERASE
Note: I DO NOT TAKE RESPONSIBILITY FOR ANY DAMAGE THAT MAY HAPPEN.
XxPixX said:
You should be able to get past it if you change your build.prop so that you have say... a nexus 4
http://forum.xda-developers.com/showthread.php?t=1948558
EDIT: Also our kernel has this thing disabled by default so you will have to compile your own kernel and change a flag.
EDIT2: Here's the flag you have to disable/enable: MMC_CAP_ERASE
Note: I DO NOT TAKE RESPONSIBILITY FOR ANY DAMAGE THAT MAY HAPPEN.
Click to expand...
Click to collapse
Yah thanks, but I am more concerned about the issues related to LagFix with incompatible devices, as I have read somewhere that if the wrong formatting/fragmentation/whatever it is, is used then it can make the memory permanently unreadable/corrupt.
There's no issue in running the app on my device, I just wanna know that is my device compatible with TRIM or not, and also the potential issues related to it.
Sent from my GT-N7000 using XDA Premium 4 mobile app
yes, you can trim the n7000...
http://forum.xda-developers.com/gal...kernel-trim-speed-cyanogenmod-galaxy-t2875730