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
Related
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
confusedman112 said:
I unlocked the bootloader. Roms like Synergy, Bean, etc no longer boot (stuck on samusg scrreeen)
Any idea?\
Click to expand...
Click to collapse
What methode did you use to unlock it? I'm running the stock no nonsense rom and I belive unlocked with no problems
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
lazarus2405 said:
Do other roms boot? Will the newest CM10 nightly boot? Will anything boot?
Did you flash a different recovery? If you were using kexec roms before (beans is one, so is synergy with imo's kernel) and then flashed a non-kexec-supporting recovery, that'd explain not being able to boot. If you're unlocked, you don't have to flash a new recovery.
If you did the unlock correctly, you should be able to boot whatever you were able to before. If you can't get anything at all to boot, it's possible you flashed a bad aboot image.
Click to expand...
Click to collapse
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x. Phone isn't recongized by PC, no idea why. Any idae how to get 6.x using the terminal app in CM10 and wifi?
Click to expand...
Click to collapse
Install EZ-Recovery from the play store and flash 6.0.1.0?
PJnc284 said:
Install EZ-Recovery from the play store and flash 6.0.1.0?
Click to expand...
Click to collapse
Thanks. Flashing Synergy now to test it...let's see what happens.
EDIT: Flashed just great, but still isn't working. But, it's cool, CM10 mods work and I got what I needed (exported Verizon contacts and improted them to Google Contacts using My Verizon's webstie)
confusedman112 said:
CM10 ROMs boot.
I think it's because I used CWM 5.x rather than 6.x.
Click to expand...
Click to collapse
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
lazarus2405 said:
Yep, that's exactly the problem. You installed a non-kexec recovery and your roms still use kexec.
You're sure you selected the right options in EZ recovery? Open it, scroll to the recovery pane, select the "recovery" radio button, change the drop down menu next to it to CWM 6.0.1.0, click the "Flash!" button. That should let you install whatever roms or kernels you like.
Click to expand...
Click to collapse
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
confusedman112 said:
Dang. How do I undo the bootloader unlock so I can redo it with the proper CWM?
Click to expand...
Click to collapse
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
droidstyle said:
why dont you take some time and read before flashing...this s*** is getting rediculous! Your questions are answered in multiple threads on this forum. Actually I just answered your question in a thread right below this!! Sorry not trying to be a ****...sigh.
Click to expand...
Click to collapse
Because I am at work and don't have time to find and locate? Could you reference it, please?
PJnc284 said:
Being unlocked shouldn't have any impact on being able to flash using ez-recovery. One thing you can try is use EZ-Recovery to flash stock recovery, odin back to the stock verizon image which should relock the bootloader and start all over.
Click to expand...
Click to collapse
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
newuser134 said:
Why do you need to flash stock recovery to use Odin to flash stock Verizon rom? Odin has nothing to do with what recovery you have installed. I flashed stock unrooted rom while rooted and having CWM recovery, it worked just fine. Once you flash stock rom, it restores the stock recovery too anyway. I'm fairly sure of this, but if I'm wrong, please correct me anybody.
Click to expand...
Click to collapse
Just to be safe. Wanted to get rid of the sprint related elements from the original root so I Odin'd back to stock with cwm installed using the VRALF2 tar found here. Tried to boot into recovery to factory reset prior to first boot and had 0 recovery (not stock nor cwm). Luckily the rom booted and I used the simple root method to root and install EZ-Recovery to install CWM.
If I flashed synergy v1.7 and used rom manager v5.x.x and then unlocked the boot loader how would I flash a new rom? Do I have to use ez recovery with clockwork mod v6.x.x since it is now unlocked or can I continue using rom manager with clockwork mod 5.x.x. I'm a noob and won't be looking to switch roms until synergy gets jellybean. Thanks for the help and hopefully I made sense with my question
synergy to beans to synergy bootloop
I think my issue might be related to the issues stated above.
So after after having unlocked my bootloader with EZ unlock & installing beans custom Rom via TWRP , I decided to go back to synergy. I made a nandroid of my synergy which was origianlly installed with CWM and figured I could just wipe and restore that with TWRP. Total bootloop.
OK, so I pulled the battery, tried it again...bootloop.
SO I pulled the battery, wiped and installed the synergy zip thinking I could try a fresh install. I got a message in TWRP that E:sd-ext was not found, but wipe seemed to happen so I continued the process.
installation said it was successful but now when I try to boot up, I either get stuck in the android is upgrading applications (looping over and over) or it gets through there and tells me all teh com.android.xxxx applications unexpectedly stop.
is this a soft brick? can I recover from this? are there incompatibilities between the kernels of bean's custom rom and synergy for verizon samsung galaxy s3?
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
j0hnnyn said:
I did a lot of reading before I got into hacking my s3. I'm pretty new to the android development of Samsung phones, so the terms Odin and kexec are a little unfamiliar to me. I've owned and rooted and flashed 4 different HTC phones within the past 2 years successfully. But Samsung is a new ball game for me. And to my limited knowledge, I'm stuck and I'm hoping you guys can help me out.
Here's the process of what I did to my phone that got me to where I am.
1. I was able to root my phone and flash the custom recovery using using Adam outler's program successfully
2. I downloaded ez unlock boot loader from the play store and then successfully unlocked my boot loader
3. I tried to make a nandroid but I didn't know how to with the recovery I had. So I installed Rom manager and flashed cwm.
4. I downloaded the custom bean build 8 ROM, fully wiped, and attempted to flash the Rom with the Rom file sitting on the root of my phone's "sdcard"
- The zip seemed to flash correctly but then after I reboot from recovery, the screen would be sent back into recovery for some odd reason.
- I even tried to repeat the flashing process but it still resulted in sending me back to recovery after I hit reboot
5. So I restored my nandroid. Moved the Rom file to the root of extsdcard and then tried to flash it with cwm. It seemed to flash correctly once again but after I hit reboot, the phone shows the black splash screen with "Samsung galaxy s iii" in white letters then the phone shuts off. That's all that happens when I try to turn my phone on now.
Now normally if this were a HTC phone, I'd boot the phone to bootloader then recovery then restore my back up. But it's a Samsung. I know the volume down/home/power button trick but when I do that with my s3, the caution box pops up.. I hit volume up to by pass it then it just shows a big "downloading" sign that stays there forever. (I've literally left the phone sitting at the "downloading" sign for over an hour and nothing happened.)
So now I'm stuck. I no longer have a solution to get out of this situation. (I suppose this is a soft brick? )
Can anyone offer me any advice?
Click to expand...
Click to collapse
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
psycopanther said:
aye. go here and look for the return to stock section. remember to read it all before you start at least once.
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
volume up/home/power button is recovery try that
and you used rom manger to flash rom?
j0hnnyn said:
I'll try this when I get home. Do you know where it is I messed up while flashing the Rom? Did I use the wrong recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
PJnc284 said:
Use EZ-Recovery to flash CWM 6.0.1.0 and just avoid rom manager next time. Does Beans still use kexec? Could be the issue since the cwm in rom manager doesn't support it.
Click to expand...
Click to collapse
Yep, kexec rom (kernel) using a recovery that doesn't support it.
not sure if this can help but read this post I made, it may help:
http://forum.xda-developers.com/showthread.php?t=1842716
Make sure you have the right CWR version which is 6.0.1 or 6.0.2. Don't mess around with flashing things in rom manager.
To get to your recovery you need to use vol up+home+power.
The vol down puts the phone into Download/ODIN mode. It's like the bootloader/hboot screen of HTC phones.
I always super wipe)cache,data,dalvil,system) before any install, nandroid or fresh rom. And then install downloaded apps with tit backup.
To use Bean's nandroids after bootloader unlock, flash a fresh copy of bean first to install kexec, then flash your nandroid.
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1768209]
From what I have read in his original post for his new build, it does require an unlock and is running a custom non-kexec kernel, so it I would draw the same conclusion that you are and it should in theory work with the 6.0.1.2 version of CWM.
j0hnnyn said:
If I understand correctly, Bean's Custom Build 9 is out and no longer needs kexec. Therefore I can now use CWM 6.0.1.2 as I did earlier and I should have no problems now that kexec is no longer necessary. Can anyone confirm that?
Click to expand...
Click to collapse
You should be able to use cwm6.0.1.2 to flash Imoseyons leankernel on any version of a custom touchwiz rom and enjoy no kexec
Im running beans 8 with imo's 2.2 kernel w/ no kexec...dont really like beans 9.
Hi xda. I just installed (flashed) cyanogenmod 9 on my nexus s, after getting bored with the stock kernel so I flashed trinity ics kernel. Now when I try and flash a new kernel nothing changes, cwm recovery said it flashed successfully. The procedure I did when I installed it was:
1) install zip from SD card
2) choose zip
3) yes
4) reboot system
Is there anything I did wrong? Do i need to clean the cache and dalvik cache?
Sent from my Nexus S using xda premium
How are confirming that it did not flash?
Clockwork recovery said it was successfully installed. Also the version of the kernels are right for my rom (ics)
Sent from my Nexus S using xda premium
You missed understood me.
How are you checking/confirming that the kernels you flashed after trinity are not actually flashing/ booting/being used or how ever you want to phrase it?
cm changed their ramdisk(again). so now custom kernels without cm ramdisk wont boot cm. as always, cm likes to "break" things. complain to cm. i recommend other non cm based roms, like rasbean jelly. it doesnt have as much junk included and is a faster/smoother experience than cm. many kernel developers arent willing to cater to cm anymore because of these changes they constantly make. enough is enough.
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
maybe so, bit i dont see a mention of a boot animation
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
ah, ok. i reread the op very slowly.
op, did you check the kernel version in your about phone? other kernels wont get rid of the boot animation unless they offer a boot animation or include a script to delete it.
Yeah. But he is saying he doesn't see a change. Implying the phone boots up as it did prior.
He is also on cm9 , not the new cm10 that botched things up again.
That is why I am trying to get him to confirm how he is checking if the kernel changed. Almost certain its the op just seeing the boot animation and thinking that it didn't change due to that.
Op. Go to settings /about phone and look at kernel version. Flash a different kernel again. Check again.
I am confirming that it did not flash by going to settings and then about phone. In kernel it still says Trinity kernel rather that matrix kernel or air kernel (2 roms I've tried flashing).
Sent from my Nexus S using xda premium
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
[/QUOTE]
albundy2010 said:
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
Click to expand...
Click to collapse
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.[/QUOTE]
albundy2010 said:
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
Click to expand...
Click to collapse
Ok ll try that
You can flash my cm compatible kernel.
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
p1gp3n said:
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I gave up and flash a new rom and kernel thanks for the help.
Im having a problem getting to the recovery screen of safestrap.
I just installed safestrap from this link here http://forum.xda-developers.com/showthread.php?t=2605648
and it said it was successful. When I clicked Boot into Recovery, the phone restarts and just hangs at the Samsung Galaxy SIII Screen.
pressing any of the keys, or trying to power it off does not work. I have to pull the battery.
Upon pulling the battery, I do get the safestrap overlay where it says safestrap is disabled. I click the menu button that says recovery and it just hangs on a black screen. And I need to pull the battery again. When i get back to the safestrap screen again, i can get my phone to boot as normal by clicking continue as oppopsed to recovery, but I still can not get safestrap to boot into the recovery screen to install a rom (I want to install a 4.3 Rom).
Does anyone have any advice? Im currently running on a rooted 4.1.2.
PS: Is there a rooted stock 4.3 rom? I dont have alot of experience with custom roms. I just want the latest stock rom, but have root access. If there is one, can someone please point me in the direction of it?
Safestrap is intended for people that took the 4.3 ota, so I'm not sure if it will work on 4.1.2. You should make sure your bootloader is unlocked and install a custom recovery. There are several threads that explain the process.
Sent from my SCH-I535
roaddog665 said:
Safestrap is intended for people that took the 4.3 ota, so I'm not sure if it will work on 4.1.2. You should make sure your bootloader is unlocked and install a custom recovery. There are several threads that explain the process.
Sent from my SCH-I535
Click to expand...
Click to collapse
Safestrap should work fine for any other versions of jellybean, (im assuming) he intends to install a custom rom while at the same time having a live back up of the stock one. Also safestrap is meant for people with locked bootloaders and even though you can unlock the bootloader (on 4.1.2) you really don't need to in order to install safestrap.
Mtsprite said:
Safestrap should work fine for any other versions of jellybean, (im assuming) he intends to install a custom rom while at the same time having a live back up of the stock one. Also safestrap is meant for people with locked bootloaders and even though you can unlock the bootloader (on 4.1.2) you really don't need to in order to install safestrap.
Click to expand...
Click to collapse
OK, I wasn't sure if it would or not. Thanks.
Sent from my SCH-I535
rslthara very
So wait... Do I even need safestrap then? or is there a way to install 4.3 without having my bootloader become locked. I thought that was the whole point of installing safestrap was to create a partion of the update before you actually update to it.
MattDusza said:
So wait... Do I even need safestrap then? or is there a way to install 4.3 without having my bootloader become locked. I thought that was the whole point of installing safestrap was to create a partion of the update before you actually update to it.
Click to expand...
Click to collapse
Safestrap is only for people who already updated to 4.3 rom with LOCKED bootloader. In your case, NO you don't need safestrap. You could install 4.3 for unlocked bootloader (in your case) here are a few:
http://forum.xda-developers.com/showthread.php?t=1904329
http://forum.xda-developers.com/showthread.php?t=2591895
http://forum.xda-developers.com/showthread.php?t=2608639
Gturvis mingled
Thank You. I guess I missed something when I was reading on how to avoid getting your bootloader locked in the process.
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.