Related
I'm as happy as anyone else with this new method of unlocking the bootloader. I'm rooted the ODIN way and then have bean's stock rom with imosey's custom rom installed (via the k-exec). I've read that people are doing this with all different kinds of rom and recovery.
My question: what happens to the k-exec? All gets re-written? we don't need to go to stock to get this to work? It seems to me that it would be safer if we re stock, no?
I know there is a one click now but I prefer manual stuff.
I was wondering the same thing. I want to flash an kexec kernel but idk what might happen now that I'm unlocked
Sent from my SCH-I535 using xda app-developers app
vx2ko said:
I was wondering the same thing. I want to flash an kexec kernel but idk what might happen now that I'm unlocked
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
PJnc284 said:
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
Click to expand...
Click to collapse
So running this new unlock method can be accomplished with K-exec on the phone? I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
loveubuntu said:
So running this new unlock method can be accomplished with K-exec on the phone? I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
Click to expand...
Click to collapse
I'm on Synergy 1.7 (non-nightly) and it's running fine. Still using the stock kernel and not Imo's lean kernel but it apparently still worked for others.
PJnc284 said:
You should be fine assuming you still have a kexec compatible recovery. Eventually all roms will move to full unlocked so kexec will pretty much be a thing of the past.
Click to expand...
Click to collapse
We need a list of non kexec and kexec recoveries and kernels. I've been in the Rom flashing and troubleshooting game for a while but never had to use a locked otloader so this kexec stuff is new. If someone could clarify what's kexec and what's not that would be great
Sent from my SCH-I535 using xda app-developers app
loveubuntu said:
I've always thought that k-exec was a bott=strap kind of a method. Wouldn't this get messed up with this new method?
Click to expand...
Click to collapse
To the best of my knowledge, when the bootchain gets to the boot partition, it loads the kernel on boot.img. It then proceeds to start up the system partition. If you're using kexec, the ROM you're using checks whether the kernel is the expected one or stock. If it isn't the right one, it reboots to recovery, passing instructions to CWR on what to do when it gets there (please feel free to correct me on that part, my knowledge there is vague). That's the first reboot. Once in recovery, those instructions tell recovery to load the right kernel into memory and uses kecex to perform a hardware restart and boot from the kernel it just put in memory. That's the second reboot you see. Once that kernel is loaded up, it starts up the system partition and finishes booting into your ROM.
Before, if the image on boot did not match what the bootloader would permit, it would throw an error and refuse to boot. Unlocking the bootloader allows us to put whatever we want on boot. What got overwritten when you unlocked your bootloader was aboot, the part of the boot sequence that's loaded before the boot partition. If you install a rom that includes a boot.image, now it will just boot from that with whatever kernel. It boots normally, the rom no longer needs to reboot into recovery to load the correct kernel, and all of that kexec infrastructure, which is still there goes unused.
So as long as you don't switch to a recovery without kexec support, you can flash whatever you want, kexec, stock, or using the unlocked bootloader. You can't get yourself into any trouble restoring a backup can't fix.
Of course, if you were to switch to TWRP or another recovery not supporting kexec and then try to boot a kexec rom, you're asking for a bootloop. So stick with the recovery you're using now until every rom or kernel you'd possibly try no longer uses kexec.
lazarus2405 said:
To the best of my knowledge, when the bootchain gets to the boot partition, it loads the kernel on boot.img. It then proceeds to start up the system partition. If you're using kexec, the ROM you're using checks whether the kernel is the expected one or stock. If it isn't the right one, it reboots to recovery, passing instructions to CWR on what to do when it gets there (please feel free to correct me on that part, my knowledge there is vague). That's the first reboot. Once in recovery, those instructions tell recovery to load the right kernel into memory and uses kecex to perform a hardware restart and boot from the kernel it just put in memory. That's the second reboot you see. Once that kernel is loaded up, it starts up the system partition and finishes booting into your ROM.
Before, if the image on boot did not match what the bootloader would permit, it would throw an error and refuse to boot. Unlocking the bootloader allows us to put whatever we want on boot. What got overwritten when you unlocked your bootloader was aboot, the part of the boot sequence that's loaded before the boot partition. If you install a rom that includes a boot.image, now it will just boot from that with whatever kernel. It boots normally, the rom no longer needs to reboot into recovery to load the correct kernel, and all of that kexec infrastructure, which is still there goes unused.
So as long as you don't switch to a recovery without kexec support, you can flash whatever you want, kexec, stock, or using the unlocked bootloader. You can't get yourself into any trouble restoring a backup can't fix.
Of course, if you were to switch to TWRP or another recovery not supporting kexec and then try to boot a kexec rom, you're asking for a bootloop. So stick with the recovery you're using now until every rom or kernel you'd possibly try no longer uses kexec.
Click to expand...
Click to collapse
Thank you, great explanation. To clarify: If you have k-exec and rot before the bootloader unlock leak and now unlock your bootloader with the new leak, you have the best of both worlds. If you use a ROM that uses K-exec, the k-exec part kicks in and if you use the new CM10 alpha without k-exec, the k-exec is unused and the new unlock bootloader is utilized.
Is that right?
Folks...listen up! You can unlock your device on any rom. That being said now that your unlocked, kexec or non kexec kernels will work on a unlocked device. Just make sure your unlocked and using cwm 6.0.1 and everything thats currently available to flash on our device will work. Kexec is not some majical program where we need to worry about bricking our device. Its simply a script that hijacks the boot process after the stock kernel passes verification and then it side loads the custom kexec kernel off of the recovery partition. Unlocking the bootloader has no effect on any of this. Im still using imoseyons 12-2 kexec kernel with beans 8 and the only difference is the device boots up alot quicker. Reason being the bootloader is no longer checking for signed software. Its really no big deal folks..everything still works the same.
droidstyle said:
Folks...listen up! You can unlock your device on any rom. That being said now that your unlocked, kexec or non kexec kernels will work on a unlocked device. Just make sure your unlocked and using cwm 6.0.1 and everything thats currently available to flash on our device will work. Kexec is not some majical program where we need to worry about bricking our device. Its simply a script that hijacks the boot process after the stock kernel passes verification and then it side loads the custom kexec kernel off of the recovery partition. Unlocking the bootloader has no effect on any of this. Im still using imoseyons 12-2 kexec kernel with beans 8 and the only difference is the device boots up alot quicker. Reason being the bootloader is no longer checking for signed software. Its really no big deal folks..everything still works the same.
Click to expand...
Click to collapse
Quick noob question. I rooted and flashed synergy v1.7 using ROM Manager from the app store. When I open the app is says rom manage v5.0.1.5 at the top. Everything is running perfect and do not want to flash a new rom until synergy does a jellybean rom. Should I use the unlock app to unlock my phone now or is there no need? Also is rom manager ok to continue using or should I use something else? Thanks for the help
I got lazy and unlocked using the market app. Running Bean building 8 that is using kexec. I'm still getting three reboots. Is this right?
Sent from my SCH-I535 using xda premium
Hey peeps, I'm running slapnuts v1.4 rom on a d2vzw gs3 vrucml1 baseband. The rom is supposed to be running with Lean Kernel v4.0 but for some reason I am stuck with the stock kernel. I have also tried flashing Lean Kernel by itself but with no success, actually whenever I flash it I just end up losing wifi and having to flash the ml1 modules back. I could use some help here, thanks!
Another thing that I could use some clarification on, Safestrap directs users to install the kernel modules after flashing a rom (otherwise we would be without working wifi). The problem I'm seeing here though is whenever a kernel is flashed, wifi is no longer working, in other words, the module is gone and has to be re-flashed which I am assuming (only because I've been unable to get a kernel up and running) would remove the kernel all over again and visa versa.
Am I just doing something wrong or does it seem that something is broken here?
Yeorgaki said:
Hey peeps, I'm running slapnuts v1.4 rom on a d2vzw gs3 vrucml1 baseband. The rom is supposed to be running with Lean Kernel v4.0 but for some reason I am stuck with the stock kernel. I have also tried flashing Lean Kernel by itself but with no success, actually whenever I flash it I just end up losing wifi and having to flash the ml1 modules back. I could use some help here, thanks!
Another thing that I could use some clarification on, Safestrap directs users to install the kernel modules after flashing a rom (otherwise we would be without working wifi). The problem I'm seeing here though is whenever a kernel is flashed, wifi is no longer working, in other words, the module is gone and has to be re-flashed which I am assuming (only because I've been unable to get a kernel up and running) would remove the kernel all over again and visa versa.
Am I just doing something wrong or does it seem that something is broken here?
Click to expand...
Click to collapse
You cannot flash a custom kernel on TouchWiz 4.3+. You must use the stock kernel. That's the way that Safestrap works on the S3 given the limitations created by Samsung.
Sent from my SCH-I535 using Tapatalk
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Preston2291 said:
I recently had to get a replacement phone sent to me from verizon. I'm on 4.4.4 I bought and used sunshine for unlock and s-off. I have flashed twrp and super su for root. I have not touched the kernel so I am still on stock kernel which has write protection. There are kernels out that have this disabled. What I'm trying to find information on is how do I flash one of these. I can't seem to find info on this. I got the original m8 on launch day and have done this months ago and I remember having to put certain things on the SD card and renaming them to something along the lines of (0BP6.img).
Is this correct. I also remember having to adb certain things to the phone. I'm just trying to avoid a brick. Any help is appreciated
Click to expand...
Click to collapse
Most kernels r flashed in recovery.
Tigerstown said:
Most kernels r flashed in recovery.
Click to expand...
Click to collapse
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Preston2291 said:
So I should just be able to download a sense 4.4.4 kernel and flash in recovery then I can nandroid backup and then start flashing custom roms? I just didn't know if I was able to flash one in recovery coming from stock which is write protected without problems.
Click to expand...
Click to collapse
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Tigerstown said:
have you tried to flash a ROM already? Cause I have been with HTC sense way way back. An I never have had this issue...I just pick a stock ROM an flash it... But you could fast boot a stock insecure boot using fast boot I guess if that's what you want to do.
Click to expand...
Click to collapse
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick because I can't write to the system with a new rom
Preston2291 said:
I haven't tried to flash a stock rom no because I wasn't sure. And I don't want to wipe system and data with a write protected kernel because I'll be screwed. Or do you mean dirty flash a stock rom with the insecure kernel? I just don't want to not have write protection removed and then wipe and soft brick
Click to expand...
Click to collapse
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Tigerstown said:
If you r s-off unlocked an flashed twrp then flashed SuperSU zip. Myself I just back a backup now verify backup is there an flash a ROM...or you could flash a stock insecure kernel 1st if you want to be extra safe.
Click to expand...
Click to collapse
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Preston2291 said:
Just flashed a stock insecure kernel. How is a way to test if I have write access?
Click to expand...
Click to collapse
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Tigerstown said:
Don't know. Never check has I have never had a issue ever once an have own 7+ different HTC devices.
Click to expand...
Click to collapse
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Preston2291 said:
Thing is I bricked my last m8 because I flashed a stock recovery and rom to get the 4.4.4 update. And I wiped system and data to re install a rom and couldn't write to system and the phone wouldn't do anything but sit at the HTC screen because it was bricked. That's why I'm concerned with the kernel.
Click to expand...
Click to collapse
You should be able to just flash pretty much any sense based rom and have what you want. Write protection is removed in all of them, or, at least in all the ones I've tried.
That said, if you've already flashed a kernel that has write protection removed, you should be able to check it by just copying any file to the system folder. A text file, picture, anything. Then reboot the phone and check to see if the file you copied to the system folder is still there. If so, you're good to go. If not, write protection is still being enforced.
Anyone know where I can locate the stock kernel? Im running Elemental X kernel and want to go back.
If you want the stock kernel, then fastboot flash the stock boot.img to both slots...you will lose twrp but that can always be installed again
BakedTator said:
If you want the stock kernel, then fastboot flash the stock boot.img to both slots...you will lose twrp but that can always be installed again
Click to expand...
Click to collapse
Thanks! I may do just that as the new update with Double Tap to wake isn't working and I'm assuming its due to Elemental X kernel that has that feature which I didn't enable during flash. I'll likely hold tight for a bit and see if someone posts a flashable via TWRP stock kernel so i dont need to go through the hassle of reinstalling TWRP (even though its not that time consuming).
Good evening,
I waited 168 hours, installed twrp, and RMM State, all with a Stock ROM, then for a bug I had in the Cerberus app I had to reinstall the Stock and blocked the RMM again.
Is it always going to be like this? You still do not have a way to avoid this using ROM Stock, I'm not much of a MOD fan!
costafabiof said:
Good evening,
I waited 168 hours, installed twrp, and RMM State, all with a Stock ROM, then for a bug I had in the Cerberus app I had to reinstall the Stock and blocked the RMM again.
Is it always going to be like this? You still do not have a way to avoid this using ROM Stock, I'm not much of a MOD fan!
Click to expand...
Click to collapse
I suspect that anytime you have to flash the stock rom again, you will need to start all over. That seems a PITA!
well u should have installed a custom kernel before it can boot for the 1st time
since custom kernels has patched rmm state right...
but for now you should wait 7 days again and dont forget to install custom kernel after the 7 days...
if you plan to install a new rom again in twrp install custom kernel right after without rebooting and u should be fine then
good luck
JeffDC said:
I suspect that anytime you have to flash the stock rom again, you will need to start all over. That seems a PITA!
Click to expand...
Click to collapse
It's very difficult this way, we still have no way out about it? right?
SOGKush420 said:
well u should have installed a custom kernel before it can boot for the 1st time
since custom kernels has patched rmm state right...
but for now you should wait 7 days again and dont forget to install custom kernel after the 7 days...
if you plan to install a new rom again in twrp install custom kernel right after without rebooting and u should be fine then
good luck
Click to expand...
Click to collapse
Sorry, but I did not understand.
How should I have installed the kernel?
The steps I followed were:
1. I expected to release the OEM
2. I installed TWRP
3. Restart (I was in Download mode).
4. In TWRP I installed the RMM State
Then I had an error in the ROM caused by an app, and I had to reinstall. When I did that the RMM was there again.
costafabiof said:
Sorry, but I did not understand.
How should I have installed the kernel?
The steps I followed were:
1. I expected to release the OEM
2. I installed TWRP
3. Restart (I was in Download mode).
4. In TWRP I installed the RMM State
Then I had an error in the ROM caused by an app, and I had to reinstall. When I did that the RMM was there again.
Click to expand...
Click to collapse
I think what he is saying is that after you install your custom stuff, via TWRP, and before you reboot to system, flash the custom kernel.
JeffDC said:
I think what he is saying is that after you install your custom stuff, via TWRP, and before you reboot to system, flash the custom kernel.
Click to expand...
Click to collapse
so I will need a custom kernel?
Because my understanding is medio, I use only stock rom, and the default kernel.
In this case, if it is mandatory, is there a custom kernel indicated?
Just to quote, in the topic that has the link to the RMM State does not say about kernel!