Related
Guys i came up with an idea
to change the kernel
by rewriting the kernel
i know this idea is crazy
but i just came up with this idea because im soo sick of using this stock roms stuck too much unlike the unlocked ones
im having 12W01 w8 mobile no wonder i bricked my phone twice
every one knows that we can modify the codes using rom manager so we just have to copy and paste whats in nAa kernel methods and implementations to stock tweaks
hope this will work
DEVELOPERS please consider
eh? explai better? you wanna unlock the bootloader with kernel for install kernel? ._.
its like this after 11W29+ they have blocked the kernel right
but still with using tools we can modify the running methods and implement new
so as i was trying to say it has to work if we replace the whole nAa Kernel methods and implementations to stock the whole bunch with out removing the kernel files
I dont think you can mod it whitout flashing it again...
Sent from my X8 using xda app-developers app
eh, nice idea bro!
but still, i don't think it could be possible without unlocked bootloader and trying it may brick your phone again as u need to probably reflash it, as said by Lukenda too...
good luck if you wanna try it. :good:
fingers crossed :fingers-crossed:
Do you mean something like this? I don't know if it works on X8 but with this thing we could be able to "install" custom kernels on devices with locked bootloader.
fifo171 said:
Do you mean something like this? I don't know if it works on X8 but with this thing we could be able to "install" custom kernels on devices with locked bootloader.
Click to expand...
Click to collapse
That could work. But i think the op is talking about modifying the kernel the phone is on as opposed to running a kernel on top of what's already there. At least that's how i understood the guide...
Sent from my rooted tomato using xda app
@OP : As long as the bootloader is locked, you can modify all the kernels you want, but it still won't be flashable to our phones.
untill your bootloader locked you cant flash any kernel mod into your device :'(
rohin he means to say to make changes in the stock kernel present in the phone some how and not flash new kernel...
it might work if some developer works on it....like alfsamsung and nobodyatall coming together and do it?
aZuZus method might be some help.. may be cwm flashable kernel? but that would require unlocked bootloader too.
CnC-ROCK said:
rohin he means to say to make changes in the stock kernel present in the phone some how and not flash new kernel...
it might work if some developer works on it....like alfsamsung and nobodyatall coming together and do it?
aZuZus method might be some help.. may be cwm flashable kernel? but that would require unlocked bootloader too.
Click to expand...
Click to collapse
To tamper with even the stock kernel, the bootloader needs to be unlocked. It's like trying to edit a stock rom (2.1 like Matej2010) without root. It's impossible.
Are you sure it won't work on locked BL? Then how is it possible that with kexec method X10 users can run custom kernels with locked BL? AFAIK they use the kexec to unload stock kernel and load custom kernel (for example like doixanhs DT module - it unloads the stock screen driver and loads the modified one. I think that kexec does the same with the whole kernel).
Provided you can load/unload the whole kernel w/o f*cking the system up
RohinZaraki said:
Provided you can load/unload the whole kernel w/o f*cking the system up
Click to expand...
Click to collapse
i suppose that if x10minipro can do it then so can x8
Yeah, maybe it's possible. Isn't here anyone to so that willingly?
Sent from my MANGO using Tapatalk2
Infact idea is working on the Samsung Galaxy S3 whereby Kexec is loading and selecting the boot from the recovery partition
But then we does need figure out a way to enable the system to boot from different partition.
hell of a work to rewrite script
Somebody should ask nAa and dx,they should know the answer
Sent from my X8 using xda app-developers app
@all azuzu's SBoot tool will make use of the kexec module. A kernel with a kexec module does not necessarily need an unlocked bootloader. It will (AFAIK) load up the new kernel for debugging over the existing stock kernel. We won't see such a kernel soon but that soon doesn't necessarily mean never.
Can we run 2 kernel om 2 different roms,like multibooting them? That way would be possible..
Sent from my X8 using Tapatalk 2
Lukenda said:
Can we run 2 kernel om 2 different roms,like multibooting them? That way would be possible..
Sent from my X8 using Tapatalk 2
Click to expand...
Click to collapse
Huh? Really explain what you mean and give an example if you can.
Hi All,
I had heard about many people having issues if switching from franco to any other kernel and knew about the solution [ flashing stock kernel / the entire ROM in case of CM before flashing other kernel]. But, unfortunately in my hurry forgot to do it this one time.
Now, forgive me , but the solution I had heard to fix the bootloop always involved using the flashboot to flash to the stock image and then proceeding from there.
Fearing the worst, I tried going to the bootloader mode and then to the recovery mode. Was quite surprised to find that recovery mode was working perfectly fine, so all I had to do was flash the franco kernel zip file.
The phone then rebooted fine without any issues. And I was then able to proceed without any data loss.
Maybe, it was because I hadn't read about this and it was posted earlier. But, thought this information could be useful for newbies. Cheers!! Mods, please delete the thread if the information is widely known . Tried searching but wasn't able to get any specific results other than what I had mentioned.
Hrithan2020 said:
Hi All,
I had heard about many people having issues if switching from franco to any other kernel and knew about the solution [ flashing stock kernel / the entire ROM in case of CM before flashing other kernel]. But, unfortunately in my hurry forgot to do it this one time.
Now, forgive me , but the solution I had heard always involved using the flashboot to flash to the stock image and then proceeding from there.
Fearing the worst, I tried going to the bootloader mode and then to the recovery mode. Was quite surprised to find that recovery mode was working perfectly fine, so all I had to do was flash the franco kernel zip file.
The phone then rebooted fine without any issues. And I was then able to proceed without any data loss.
Maybe, it was because I hadn't read about this and it was posted earlier. But, thought this information could be useful for newbies. Cheers!! Mods, please delete the thread if the information is widely known . Tried searching but wasn't able to get any specific results other than what I had mentioned.
Click to expand...
Click to collapse
Its well known that you need to flash a stock reset kernel after coming from a Franco kernel to another.
Sent from my Nexus 4 using xda premium
nbeebe24 said:
Its well known that you need to flash a stock reset kernel after coming from a Franco kernel to another.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Of course, I know that as is stated clearly in the OP. [ For CM, it would mean reflashing the ROM] But the solution to bootloop in case one forgets to do so, is just going to the bootloader mode-> recovery mode and flashing the franco kernel again.
As stated, only for newbies.
Hi,
Some of you may recognise my name from around the forums, especially if you have had an Xperia device before. I started my first android developments on the Xperia Play and then continued onto the Xperia U. I then lost mass interest in development due to joining college and being overloaded with work due to a computing course. I was no longer able to contribute to any developments.
Now, I am in the second year of college and have dropped a subject I am finding myself with more free time so I have decided to start developing again, only this time I have an Xperia SP.
There's only one catch, the device I have is network locked to O2 and therefore I cannot unlock my boot loader, so most if not all of my work will be for those with a locked bootloader. I am mostly interested in creating custom ROMs based on stock and also creating my own applications and embedding them into the stock ROM.
And the flashy bar at the bottom, yeah I have ideas for that.
Developments for Xperia SP:
illumination app
~Keiran
Sent from my C5303 using Tapatalk
Thank you!
Sent from my C5303 using XDA Premium 4 mobile app
Thank you!
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded
MrZender said:
Thank you guy!
You have locked bootloader and you don't use fastboot
You should sell branded phone and buy no-branded
Click to expand...
Click to collapse
I can't, it just means that I will only be able to developed for locked bootloader which is no problem really. All it means is that I cannot change the kernel image, using scripts I can mess about with the ramdisk though and may be able to boot CM on a locked boot loader if the stock kernel allows it.
Sent from my C5303 using Tapatalk
Glad to see you back in the game mate ! Too bad that you can't unlock your bootloader. Although I know that would not be a problem for you.
Sent from my C5303 using Tapatalk
Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
adfad666 said:
Hi @KeiranFTW welcome to Xperia SP development!
I hope we can work together on a project I want to try when we get the Android 4.3 update, I'm not sure if it will be successful and I'm not sure if anyone else tried this on other devices, but I want to try.
Basically I want to build Android 4.3 that works with the stock Sony 4.3 bootloader. I already have my fork of CodeAurora up and running here, I call it recaf, it will 'simply' be a matter of satisfying the extra dependencies and other Sony changes.
Come chat on freenode IRC, I'm in #freexperia, or on my own at #recaf. (If I don't reply immediately it mean's I'm afk, but my irc bouncer keeps me logged in.)
Click to expand...
Click to collapse
I'm sure it is very possible, as there is a way that could work really, I could probably set it up as a dual boot. You would need the AOSP ramdisk in tar format somewhere on your phone and at boot time if you wish to boot AOSP then it would delete everything at / and extract that ramdisk to / and then continue boot process with that ramdisk.. as long as stock kernel is compatible.
Sent from my C5303 using Tapatalk
Welcome in SP section
Happy to see more real dev here
Well, maybe you could port kexec to our locked SP's? The main part of the module and binary is done, there is only one thing left - implementing proper hardboot and finally porting to our phones. I think some Xperia SP devs might help you. There's a thread in Z1 forums where delewer tries to get last parts of the job done. If you decide to start working on it, I want to be a alpha or beta tester
http://forum.xda-developers.com/showthread.php?t=2495152
Welcome mate, glad you are here can't wait to see your work I also had an xperia play and I'm pretty sure I had a few of your roms and mods installed at some point.
Sent from my C5303 using XDA Premium HD app
I have a few projects in mind at the moment:
1. Getting the 4.3 leak to boot on locked bootloader
2. When 4.3 is released get AOSP 4.3 to run also on locked boot loader - I will be working with @adfad666 on this - most priority
3. Maybe a stock based custom ROM - least priority.
Sent from my C5303 using Tapatalk
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
MrSteve555 said:
Maybe after booting AOSP 4.3 on locked BL you could try booting 4.4? Because it was possible in Xperia X8 "age of glory"(some devs booted 2.2 on 2.1 kernel if I'm not mistaken).
Click to expand...
Click to collapse
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk
I think I'll try to boot 4.3 today, with the method described in this thread: http://forum.xda-developers.com/showthread.php?t=2593806
I'll post my results later.
KeiranFTW said:
We could try.
The way I'm going to do it is hijack pre_hw_config.sh and then launch a script from there to determine whether to extract recovery ramdisk or AOSP ramdisk, then this will be extracted to /, and then everything will be unmounted and init will be started again to restart the boot process.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
adfad666 said:
Unfortunately pre_hw_config.sh doesn't exist in the 4.3 leak, so assuming that doesn't change when we receive the official update, we won't be able to use that.
Click to expand...
Click to collapse
then /system/bin/charger
Sent from my C5303 using Tapatalk
Well, pre_hw_config.sh doesn't exist even in stock 4.1.2. I think we should try with chargemon, not charger(because it's executed earlier). I tried booting DooMLord's DoomKernel ramdisk on stock kernel. Absolutely no luck. I don't even know what's wrong - after loading ramdisk, kernel panic occurs. Maybe someone more clever will figure it out.:silly:
I think I'm nearly there at hijacking the boot process to inject new ramdisk, I just have a little test that I will have to do later as I need to go out now.
What I'm going to do is use the same ramdisk as that's in the kernel but inject it again after removing anything, this way I don't need to change my ROM and I know that I can inject a new ramdisk. I'll upload my work to github later too so people can contribute
~Keiran
Sent from my C5303 using Tapatalk
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now
KeiranFTW said:
Okay, so I've been successful in booting a custom RAMdisk, only problem I am experiencing is that the data partition is not being remounted when the new ramdisk is loaded, no idea why though.
Okay, done and fixed, sources are at https://github.com/keiranFTW/hijack-ramdisk-huashan
Get ready for exciting things coming now
Click to expand...
Click to collapse
I tried your method, but it has one bug - it doesn't symlink /data/media to /storage/sdcard0, so the data from internal memory isn't accesible through that path. Still amazing work, but I suggest you to change the format of ramdisk read by the script to .cpio, because it's easier to get from kernels. :good:
This thread is for the development for a Moto X(2013) port for Android Lollipop.
http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
2nd test build in the works
Everyone who wants to test builds needs to add [email protected] to hangouts
WARNING! tests builds,if they work, will be very unstable. Please remember to backup your system before flashing
In order to flash your phone must
-Have an Unlocked bootloader
- TWRP Recovery installed
If you meet those requirements then add him to hangouts and join the development process
Android 5.0 will come to the 2013 Moto X before the end of november , if not early december, so the amount of work that i believe is required, i dont really think its worth it.
^^^^^agreed. This has already been discussed in the GENERAL section. Mods should move this to general. No development here.
---------- Post added at 05:39 AM ---------- Previous post was at 05:37 AM ----------
And after putting android L on my N7 all locked devices will not have root anymore or safestrap. Currently only way to root is with a custom rooted kernel.
Does TWRP still work with 5.0? What about SuperSU?
lowvolt1 said:
Does TWRP still work with 5.0? What about SuperSU?
Click to expand...
Click to collapse
TWRP still works with L. However only way at this time to get root is with a custom rooted kernel by chainfire. Which means root and safestrap will be dead on L if you are on a locked bootloader.
Ha! I'm unlocked. So Flashing TWRP and installing SuperSU the traditional way no longer works? Am I understanding?
lowvolt1 said:
Ha! I'm unlocked. So Flashing TWRP and installing SuperSU the traditional way no longer works? Am I understanding?
Click to expand...
Click to collapse
Correct, now to root you will need to flash a rooted kernel.
Any word on xposed and L?
Xposed use davilk not art. So with Android Like you can't use xposed mod
Porting is difficult ..why dont u build aosp 5.0 from source using cm device tree ?
Travisdroidx2 said:
TWRP still works with L. However only way at this time to get root is with a custom rooted kernel by chainfire. Which means root and safestrap will be dead on L if you are on a locked bootloader.
Click to expand...
Click to collapse
That's not right.. with the SuperSU betas you can flash them with any kernel from my experience so far. I have flashed the betas on the stock kernel on my N7 and N5 and so far I haven't had any problems. But I just opened FKU and that was it, so I might have the app and no root..
Vekhez said:
That's not right.. with the SuperSU betas you can flash them with any kernel from my experience so far. I have flashed the betas on the stock kernel on my N7 and N5 and so far I haven't had any problems. But I just opened FKU and that was it, so I might have the app and no root..
Click to expand...
Click to collapse
So you did not have to fastboot the boot.img on your N7? That is what I had to do. Not sure if you can just flash root to your kernel. Even instructions from chainfire shows you have to be unlocked to get the rooted kernel. https://plus.google.com/113517319477420052449/posts/fw659MWRewE
But if flashing SuperSU beta works then that would be easy. However, my searches did not point me in that direction on N7 threads.
Also even if flashing SuperSU beta works it still modifies the kernel correct? In this case locked phones will not get root since they can not have mod kernels right? You mention your N7 and N5 which both probably have a unlocked bootloader. We shall see what happens when L is dropped for retail devices.
I just searched more and even on the N5 to flash the SuperSU beta you need a unlocked bootloader. Please link something that shows a locked phone will get root with L please. Since you did say I was wrong. And that was my point. Looks like only way to root L is with a modified kernel which locked bootloader can not use. Besides you mention flashing it in TWRP. Locked bootloaders can not even use TWRP.
In my understanding if Selinux is set to permissive when the ROM is compiled, you would then be able to have root access and flash superuser. Correct me if I'm wrong though.
perfoliate said:
In my understanding if Selinux is set to permissive when the ROM is compiled, you would then be able to have root access and flash superuser. Correct me if I'm wrong though.
Click to expand...
Click to collapse
I hope you are correct. Last night was my first time flashing and rooting L. I hope root is not lost for locked phones. But you still need to be unlocked to have a custom recovery to flash root. So time will tell I guess.
---------- Post added at 05:49 PM ---------- Previous post was at 05:42 PM ----------
Looks like I am still correct: straight from chain fire:
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Posted 1 hour ago. https://plus.google.com/113517319477420052449/posts/EC5MhqFFqMK
Another example of the 14' X just got root and it has to be unlocked boot loader.
http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154
Seriously!!! I do agree beggars cannot be choosers... But... The attitude of Moto X owners is Why do it when eventually we will get it!! But isn't it the same condition of other phones like Xperia Z, Nexus 4, Nexus 7, One Plus One? They know they will all eventually get it... But still people ported the ROMs without the binaries or the kernel!! I personally feel the whole point of XDA was to be independent! Not depending on an OEM for what u want! But lack of development makes me really sad, cuz the Moto X was Motorola's baby! It almost brought them back from the dead!!! Its got such brilliant hardware, just enough to be awesome n give a smooth experience! Anyways... All wanna enjoy their Motorola Goodies I guess... Let's just see what people think about development for this phone once its no longer supported By Motorola! Anyways at this point according to Motorola's time line its Droid Turbo next n then the Moto X.... Hoping to see lollipop soooon!
I am learning android programming right now... Just started playing around with codes.... I was messing with stock rom with few mods but no luck.... Let's see how it goes with AoSP source code.. ?
Sent from my XT1053 using XDA Premium 4 mobile app
Megatron007 said:
Porting is difficult ..why dont u build aosp 5.0 from source using cm device tree ?
Click to expand...
Click to collapse
Porting is actually really simple. Ive ported many roms. I am locked so i cant test anything but if anybody wants to test for me then ill give it a go. Pm me if interested
Travisdroidx2 said:
So you did not have to fastboot the boot.img on your N7? That is what I had to do. Not sure if you can just flash root to your kernel. Even instructions from chainfire shows you have to be unlocked to get the rooted kernel. https://plus.google.com/113517319477420052449/posts/fw659MWRewE
But if flashing SuperSU beta works then that would be easy. However, my searches did not point me in that direction on N7 threads.
Also even if flashing SuperSU beta works it still modifies the kernel correct? In this case locked phones will not get root since they can not have mod kernels right? You mention your N7 and N5 which both probably have a unlocked bootloader. We shall see what happens when L is dropped for retail devices.
I just searched more and even on the N5 to flash the SuperSU beta you need a unlocked bootloader. Please link something that shows a locked phone will get root with L please. Since you did say I was wrong. And that was my point. Looks like only way to root L is with a modified kernel which locked bootloader can not use. Besides you mention flashing it in TWRP. Locked bootloaders can not even use TWRP.
Click to expand...
Click to collapse
Yeah that's the thing you need to have an unlocked bootloader. That's the reason for L being such a pain to get root on. You need to either have an unlocked bootloader so that you can flash a custom recovery and flash the SuperSU Beta.zip, or you need an unlocked bootloader so you can flash an insecure boot.img which allows for root. But with a locked bootloader, I can see that getting root, is going to be somewhat of a difficult task, especially with some parts of Android becoming closed source.
atrix2man said:
Porting is actually really simple. Ive ported many roms. I am locked so i cant test anything but if anybody wants to test for me then ill give it a go. Pm me if interested
Click to expand...
Click to collapse
I am interested in testing
flipm00de said:
I am interested in testing
Click to expand...
Click to collapse
Ill pm u when its ready. Make sure u have a backup of your rom incase it doesnt boot lol
I have a question, there is progress of a custom user software on the device? (Z00D), I just came to XDA and see a lot of firmware range to more expensive models (ZE551ML and others), and on our ZE500CL's nothing ( I'm sorry for my bad English ) P.S Can someone is already working on the firmware?
Lord1201 said:
I have a question, there is progress of a custom user software on the device? (Z00D), I just came to XDA and see a lot of firmware range to more expensive models (ZE551ML and others), and on our ZE500CL's nothing ( I'm sorry for my bad Englis​h ) P.S Can someone is already working on the firmware?
Click to expand...
Click to collapse
There was one user that offered to port Cyanogenmod( @jrior001 ) , but Asus didn't provide a working kernel source file needed to accomplish that. They have updated it twice already, but I don't know if they fixed it yet.
So, we can only wait and see. We probably won't get a custom ROM, again, thanks to Asus, but who knows, there may be some hope for it.
djole94hns said:
There was one user that offered to port Cyanogenmod( @jrior001 ) , but Asus didn't provide a working kernel source file needed to accomplish that. They have updated it twice already, but I don't know if they fixed it yet.
So, we can only wait and see. We probably won't get a custom ROM, again, thanks to Asus, but who knows, there may be some hope for it.
Click to expand...
Click to collapse
The updated kernel source filled in the questions I couldn't solve. I already posted a working TWRP recovery build in my recovery thread. I started working on a CM port with some guidance from the Zenfone 5/6 devs as the ze500cl/Z00D models are closer to those devices than the other zenfone 2 models. When I have something that mostly functions I'll get a thread up.
Word to the wise, I tested my recovery by flashing a full stock build.
While everything checked out OK including flashing Intel's "unique" boot.image format, a full stock flash undid my unlocked bootloader. Something to look into for anybody tinkering with modified stock ROMS.
Sent from my N5206 using Tapatalk
jrior001 said:
The updated kernel source filled in the questions I couldn't solve. I already posted a working TWRP recovery build in my recovery thread. I started working on a CM port with some guidance from the Zenfone 5/6 devs as the ze500cl/Z00D models are closer to those devices than the other zenfone 2 models. When I have something that mostly functions I'll get a thread up.
Sent from my N5206 using Tapatalk
Click to expand...
Click to collapse
Huh, didn't know that. Thanks for the update, and your work
jrior001 said:
The updated kernel source filled in the questions I couldn't solve. I already posted a working TWRP recovery build in my recovery thread. I started working on a CM port with some guidance from the Zenfone 5/6 devs as the ze500cl/Z00D models are closer to those devices than the other zenfone 2 models. When I have something that mostly functions I'll get a thread up.
Word to the wise, I tested my recovery by flashing a full stock build.
While everything checked out OK including flashing Intel's "unique" boot.image format, a full stock flash undid my unlocked bootloader. Something to look into for anybody tinkering with modified stock ROMS.
Sent from my N5206 using Tapatalk
Click to expand...
Click to collapse
willing to test if necessary. can only do so on random times as its my daily driver. thank you for development
I will test this whenever, no fear of bricks!!!
Sent from my Z00D using XDA-Developers mobile app
thank you so much for building CM 12.1 for Z00D!!!
i hope you will support Z00D much longer with upper Custom Rom
this Cm 12.1 is so good though it hasnt been official
p/s : please reply my email on Gmail and private message
Aquaragon said:
i hope you will support Z00D much longer with upper Custom Rom
this Cm 12.1 is so good though it hasnt been official
p/s : please reply my email on Gmail and private message
Click to expand...
Click to collapse
Bro, I'm almost positive he's done developing for the z00d. He gave the ze500cl to his kid. I had to get a different phone, unlocked gsm, unlocked bootloader, about 25 roms to choose from, moto g3 2015... Best buy was $150. This zf2 is dead, unless someone else picks up development.
3GotoM ym morf tneS
AICP http://forum.xda-developers.com/showthread.php?p=68384432
3GotoM ym morf tneS