I understand there is a lot of posts that address this issue, but there is so much conflicting information, I get that you need to flash the kernel otherwise it goes into a boot loop, so where do you get the kernel to match the rom, If i see a rom i like on the board and I download it how do i know what kernel it needs, is it separate than the rom, I understand how to flash the kernel just not where to get it, or how.
I fought with that issue too, but in the end the scary "wire trick" was well worth the 35min to S-off. Though I do think there should be a better guide with pictures, and graphs, maybe in crayon, for users like me who keep messing it up. >
Sent from my cell phone using xda app-developers app
The kernel is included in the zip if the Rom. Open the zip file and look for boot.img. That is the kernel.
Sent from my ICS 3VO with Tapatalk 2
Just downgrade, its not that hard to do so.
Sent from my PG86100 using xda premium
dunndfrnt said:
I understand there is a lot of posts that address this issue, but there is so much conflicting information, I get that you need to flash the kernel otherwise it goes into a boot loop, so where do you get the kernel to match the rom, If i see a rom i like on the board and I download it how do i know what kernel it needs, is it separate than the rom, I understand how to flash the kernel just not where to get it, or how.
Click to expand...
Click to collapse
I'm hboot 1.5 (too lazy to downgrade). You have to flash the boot.IMG in the Rom that you want to flash. The boot.IMG is the kernel. You can also manually boot the recovery IMG through fastboot, which allows you to flash kernels.
so, if I download a kernel, flash through recovery then flash the boot.img from the rom, it unflashes my kernel? Im so confused about all this.
If I get a bootloop, can i flash rom, than kernel, than if no boot flash boot.img?
xblackvalorx said:
so, if I download a kernel, flash through recovery then flash the boot.img from the rom, it unflashes my kernel? Im so confused about all this.
If I get a bootloop, can i flash rom, than kernel, than if no boot flash boot.img?
Click to expand...
Click to collapse
I believe so and I believe so. A Rom will flash it's boot.img if you are s-off, but if you are s-on you have to flash it separately. You can use fastboot, flash image gui, or use 4ext Smart Flash.
Sent from my ICS 3VO with Tapatalk 2
Roosafur said:
I fought with that issue too, but in the end the scary "wire trick" was well worth the 35min to S-off. Though I do think there should be a better guide with pictures, and graphs, maybe in crayon, for users like me who keep messing it up. >
Sent from my cell phone using xda app-developers app
Click to expand...
Click to collapse
Max Lee has a good guide here.... http://htcevohacks.com/htc-evo-3d-h...c-evo-3d-using-wire-trick-juopunutbear-s-off/
He explains everything step by step with pics...In crayon, no need to worry with that guide.
Along the same lines, say I'm Juopunutbear s-off, how would I go about getting my original hboot (1.5) and s-on again? All I can find is how to relock through fastboot.
Sent from my PG86100 using xda premium
Related
So we all know there's going to be people who won't go for s-off due to the nature of the exploit
So I was thinking, since developers are going to eventually migrate to flashing kernels in recovery that wouldn't it be possible for someone to make a script that tells if your s-off or s-on by a txt file placed on the root of your sdcard by the user and then either flashes the kernel in recovery if your s-off or pushes the hboot file to the root of your sdcard?
Sent from my ADR6425LVW using Tapatalk 2
That's a good question man.
My thinking is that since S-On people cannot flash a boot.img in recovery, why can't devs just package the rom/kernel together for everyone to flash? The S-Off people will be able to flash one package for the full rom and since the boot won;t be flashed for S-On users, just provide the boot.img or PH98IMG.zip to flash in bootloader.
The only thing is I don't much of the intricate details on if this would work properly and if S-On users would get an error/have issues if a rom attempted to flash the boot.img.
Marcismo55 said:
That's a good question man.
My thinking is that since S-On people cannot flash a boot.img in recovery, why can't devs just package the rom/kernel together for everyone to flash? The S-Off people will be able to flash one package for the full rom and since the boot won;t be flashed for S-On users, just provide the boot.img or PH98IMG.zip to flash in bootloader.
The only thing is I don't much of the intricate details on if this would work properly and if S-On users would get an error/have issues if a room attempted to flash the boot.img.
Click to expand...
Click to collapse
I don't know the syntax of the updater script but it shouldn't be to hard, maybe a file that says .soff
Then again a separate kernel would fix that as well
Sent from my ADR6425LVW using Tapatalk 2
Flashing the "old" way with s-off shouldn't make a difference though right? So really why change it.
loki993 said:
Flashing the "old" way with s-off shouldn't make a difference though right? So really why change it.
Click to expand...
Click to collapse
My thought was not to kick the s-on people to the curb and tell them either s-off or learn how to flash via a computer
I agree they should posses that knowledge but making it simpler for everyone benefits us in the fact that if it isn't simplified we are going to have a whole bunch of "I flashed this ics Rom and it won't boot" threads
Sent from my ADR6425LVW using Tapatalk 2
Right I understand. I just flashed my first ROM though. It flashed, loaded the PH98IMG on its own rebooted into fastboot and I just had to vol up to flash it. That will work if your s-off or s-on. So I say just write them all like that
Unless Im missing something.
loki993 said:
Right I understand. I just flashed my first ROM though. It flashed, loaded the PH98IMG on its own rebooted into fastboot and I just had to vol up to flash it. That will work if your s-off or s-on. So I say just write them all like that
Unless Im missing something.
Click to expand...
Click to collapse
Very many people including me don't want to bother with hboot zips for a kernel when it can be a one shot flash in recovery if your s-off
If someone has the knowledge could they shoot me a pm on if this is possible? I have an idea but I can't apply it
Sent from my ADR6425LVW using Tapatalk 2
loki993 said:
Right I understand. I just flashed my first ROM though. It flashed, loaded the PH98IMG on its own rebooted into fastboot and I just had to vol up to flash it. That will work if your s-off or s-on. So I say just write them all like that
Unless Im missing something.
Click to expand...
Click to collapse
What superchillpill is saying that if repackaged for s off, it wouldn't goto bootloader at all. Takes out that step altogether. If your point happened to go over my head, my apologies lol
Sent from my ADR6425LVW using Tapatalk 2
What I wil l try and do is provide PH98IMG flashable zips that can flash via HBoot. Let the ROM flash the kernel, its the way its been on other phones and I don't see any reason to change it. Consistency is key no need to learn something new. The kernel guys could just change their scripts and hopefully package boot.img's which are easy to replace in the ROM .zip (along with the WiFi module). It would be great to see init.d supported so we could add some speed tweaks using scripts.
Just have to provide a PH98IMG of the kernel for the ROM is all. Take an extra download for S-On. You can boot into the bootloader by using the recovery option reboot into bootloader in the developer menu.
It's also more convient when you don't have to remove the ph98img off the root of your sd everytime you flash a Rom!
HTC REZOUND
I'm S-ON with hboot 1.19 and twrp. Tried installing viper4g but WiFi wouldnt work because kernal did not install. I know xhaus has a method for kernal installer for S-ON but reading thru that thread and the viper4g thread I could not figure out how to do it. Could someone explain this process?
Sent from my EVO using xda app-developers app
downsideup16 said:
I'm S-ON with hboot 1.19 and twrp. Tried installing viper4g but WiFi wouldnt work because kernal did not install. I know xhaus has a method for kernal installer for S-ON but reading thru that thread and the viper4g thread I could not figure out how to do it. Could someone explain this process?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
easiest way is to use flash image gui from google play. Not sure though as I think that rom runs off the old base and you seem to be running the new one
Not entirely sure but I think viper uses the work around for the kernel. Try flashing normally and if you can't start android, go back and fastboot flash the kernel
om4 said:
Not entirely sure but I think viper uses the work around for the kernel. Try flashing normally and if you can't start android, go back and fastboot flash the kernel
Click to expand...
Click to collapse
fastboot flash boot boot.img
extract the boot.img from the zip and put it in a location easy to get to, like the same place fastboot is at
hi
I'm trying to flash a custom kernel in specific the one created by SebastianFM on my stock, s-on, rooted htc rezound, but I'm getting an error
read_file() loading "/tmp/boot/zimage" failed: No such file or directorE:Unknown commane [y]
E:error in /sdcard/Overclocked_kernel_v1.4.0_by_SebastianFM.zip
(status 7)
while reading this thread someone mentioned the error is caused because the boot is secured. I don't really want to go s-off at this moment mainly because I cannot afford another expensive paperweight in the case I break something, so I wonder is there is an easy way to unsecure the boot so I can flash the new kernel while still being S-ON on stock rom.
I have flashed recovery-ra 3.14, stock 4.03.605.2 (global hboot 2.27)
thank you
amanuense_ said:
hi
I'm trying to flash a custom kernel in specific the one created by SebastianFM on my stock, s-on, rooted htc rezound, but I'm getting an error
read_file() loading "/tmp/boot/zimage" failed: No such file or directorE:Unknown commane [y]
E:error in /sdcard/Overclocked_kernel_v1.4.0_by_SebastianFM.zip
(status 7)
while reading this thread someone mentioned the error is caused because the boot is secured. I don't really want to go s-off at this moment mainly because I cannot afford another expensive paperweight in the case I break something, so I wonder is there is an easy way to unsecure the boot so I can flash the new kernel while still being S-ON on stock rom.
I have flashed recovery-ra 3.14, stock 4.03.605.2 (global hboot 2.27)
thank you
Click to expand...
Click to collapse
You shouldn't need to unsecure anything. Fastboot is sufficient to flash to the boot partition. From where did you receive this error? (i.e. Command Line on a PC, Recovery, etc.)
VitaminCBold said:
You shouldn't need to unsecure anything. Fastboot is sufficient to flash to the boot partition. From where did you receive this error? (i.e. Command Line on a PC, Recovery, etc.)
Click to expand...
Click to collapse
I got the error from recovery-ra, from the error I think the problem is recovery ra cannot read the information it needs (ramdisk)
amanuense_ said:
I got the error from recovery-ra, from the error I think the problem is recovery ra cannot read the information it needs (ramdisk)
Click to expand...
Click to collapse
I believe that since you're s-on you need to flash the kernel in fastboot, using your pc.
fastboot flash boot boot.img
I don't know if you have to pull the boot.img out of the zip you have or if you can even do that with this kernel. You should check in the kernel's thread and see if there's specific instructions for flashing it on an s-on device.
It does in fact require an unsecure boot.IMG don't confuse such as being a requirement to being s off. They are totally different. Most of our roms include an unsecured boot.IMG already. I know my rom has one. So its all dependent on which rom you're using.
Sent from my ADR6425LVW using Xparent Green Tapatalk 2
thanks for replying,
that is what I though, but in any case is there any way to create/get a boot.img for stock rezound rom? if not possible then I'll need to start taking a look to custom roms, the only thing is I really don't want to make big changes specially to the radio.
Snuzzo said:
It does in fact require an unsecure boot.IMG don't confuse such as being a requirement to being s off. They are totally different. Most of our roms include an unsecured boot.IMG already. I know my rom has one. So its all dependent on which rom you're using.
Sent from my ADR6425LVW using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
amanuense_ said:
thanks for replying,
that is what I though, but in any case is there any way to create/get a boot.img for stock rezound rom? if not possible then I'll need to start taking a look to custom roms, the only thing is I really don't want to make big changes specially to the radio.
Click to expand...
Click to collapse
I have the Global firmware boot.img at http://goo.im/devs/Flyhalf205/Rezound/Recovery/stock_boot_signed.img
If you need the OTA boot.img. try downloading the RUU and pulling it from there.
amanuense_ said:
thanks for replying,
that is what I though, but in any case is there any way to create/get a boot.img for stock rezound rom? if not possible then I'll need to start taking a look to custom roms, the only thing is I really don't want to make big changes specially to the radio.
Click to expand...
Click to collapse
flashing a custom rom wont affect your radios. dont worry and if you mess up, you dont have to worry then either because you're s-on.
cslingerland said:
flashing a custom rom wont affect your radios. dont worry and if you mess up, you dont have to worry then either because you're s-on.
Click to expand...
Click to collapse
This. It's basically impossible to hard-brick S-ON. That's why Chad runs S-ON for his AOSP development.
thank all you for the answers, I'll try with the boot.img flyhalf205 shared. in the worst of the cases I'll check the S-on custom builds as suggested
I just have one question is
fastboot flash boot boot.img
enough or do I need to do a full wipe before? basically I'm asking if there is anything I need to do.
if that doesn't work I'll try a custom S-ON rom as suggested
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
bjb_nyj101 said:
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
Click to expand...
Click to collapse
Try either viper rom or mean bean rom, both have instructions and a s-on kernel installer, just read the first 4 posts and follow the instructions to the dot... Good luck!
Sent from my EVO using xda app-developers app
jocarog said:
Try either viper rom or mean bean rom, both have instructions and a s-on kernel installer, just read the first 4 posts and follow the instructions to the dot... Good luck!
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Thank you for the quick reply.
So is being S-ON the reason for this problem? Why is that?
Also, is it worth the trouble of me getting S-OFF? I don't want to brick my phone, and apparently that's possible with Rancun?
bjb_nyj101 said:
So I've been trying to flash custom ROMs the past few days, and almost all of them end in bootloops. Even the two Stock-Rooted ROMs I found resulted in boot loops, regardless of how wipes & re-flashes I performed. The only ROM that I got to stick was Stock w/ Goodies... What's going on? I'm thouroghly confused. Would being S-OFF fix this?
Thanks in advance
Click to expand...
Click to collapse
tl:dr version - No, but do it.
You don't NEED to be S-Off, but I STRONGLY suggest you do go S-Off. I was dev unlocked for a long time and it was a pain in my pants to do almost anything.
First things first, are you making sure to wipe everything before you flash? You need to make sure to wipe system, restore, and wipe caches before you flash. Every time, S-On or S-Off. No. Matter. What.
If you don't want to go s-off and that doesn't work, use an app called Flash Image GUI. It's a dollar and works wonders. I have no affiliations with the app or the dev, but it made my life a lot easier when I would flash. What you would do is browse for a kernel image (your rom), check Kernel Image, make sure the two boxes are checked at the bottom and flash the image. When that was done, you have to boot into your recovery and install your kernel again after wiping.
That worked for me every time.
mstrblueskys said:
tl:dr version - No, but do it.
You don't NEED to be S-Off, but I STRONGLY suggest you do go S-Off. I was dev unlocked for a long time and it was a pain in my pants to do almost anything.
First things first, are you making sure to wipe everything before you flash? You need to make sure to wipe system, restore, and wipe caches before you flash. Every time, S-On or S-Off. No. Matter. What.
If you don't want to go s-off and that doesn't work, use an app called Flash Image GUI. It's a dollar and works wonders. I have no affiliations with the app or the dev, but it made my life a lot easier when I would flash. What you would do is browse for a kernel image (your rom), check Kernel Image, make sure the two boxes are checked at the bottom and flash the image. When that was done, you have to boot into your recovery and install your kernel again after wiping.
That worked for me every time.
Click to expand...
Click to collapse
Yup, I'm definitely wiping every time.
So with Flash Image GUI, I flash my ROM with the app, reboot to recovery, then flash the ROM again?
You should get S-OFF to make your life easier, it's free and the easiest way is facepalm... Everything is in the original development thread, is real easy, and yeah your headache/bootloops are due to the need of flash the kernel separately, with S-OFF the process is easier and in one step... Venom team also has a kernel installer for s-on and it's free... Mean bean includes it for free but you have to follow the special instructions for s-on in the OP, good luck!
Sent from my EVO using xda app-developers app
I'm going to make this a lot easier than everyone else has been. No offence people.
DO YOU WANT TO BE HAPPY!? ARE YOU HAVING PROBLEMS IN THE BEDROOM!? IS WORK GETTING YOU DOWN!? FEAR NO LONGER!!!! WITH THE BEST DEVELOPERS ON THIS PLANET HERE TO PROVIDE YOU WITH ALL THE TOOLS YOU NEED TP SATISFY YOUR EVERY NEED! I PRESENT TO YOU: just S-OFF dude.
Enjoy.
Delakit said:
I'm going to make this a lot easier than everyone else has been. No offence people.
DO YOU WANT TO BE HAPPY!? ARE YOU HAVING PROBLEMS IN THE BEDROOM!? IS WORK GETTING YOU DOWN!? FEAR NO LONGER!!!! WITH THE BEST DEVELOPERS ON THIS PLANET HERE TO PROVIDE YOU WITH ALL THE TOOLS YOU NEED TP SATISFY YOUR EVERY NEED! I PRESENT TO YOU: just S-OFF dude.
Enjoy.
Click to expand...
Click to collapse
LOL you made me laugh... Get S-OFF or keep s-on and read a lot to get it to work... Is just an extra step on every single flash...
Sent from my EVO using xda app-developers app
bjb_nyj101 said:
Yup, I'm definitely wiping every time.
So with Flash Image GUI, I flash my ROM with the app, reboot to recovery, then flash the ROM again?
Click to expand...
Click to collapse
Yep - and in recovery just flash it like you would normal app wiping everything if I remember correctly.
Mnstrblueskies responses and verbage are confusing the situation. I'm fairly literate about this and his posts are making my head spin.
If you are S-on, the kernel doesn't get flashed. You need to use flash image GUI app or fastboot to flash the kernel (i.e.boot.IMG) before or after flashing ROM. Preferably before, I suppose. Or use the HTC dumlock feature in TWRP (I'm not real familiar, but instructions are in their op/thread) (I'm S-off).
The easiest way to update firmware/radios will require S-off. If you're already on the latest OTA (3.16), you'll have the latest touch panel drivers and will only be able to use sense 3.16 based ROMs, no AOSP or older sense. This can be remedied by getting S-off and downgrading your TP drivers.
Good luck
Sent from my EVO using xda premium
So I already had an HTC Rezound for a year and was too afraid to root-so I bought an already rooted rezound from eBay that came with a 16 gig recovery sd card. I don't know what to do or how to flash a Rom or what I should do as a root noob... Can I please get some guidance from an experienced person?
Sent from my ADR6425LVW using xda app-developers app
undeadking said:
So I already had an HTC Rezound for a year and was too afraid to root-so I bought an already rooted rezound from eBay that came with a 16 gig recovery sd card. I don't know what to do or how to flash a Rom or what I should do as a root noob... Can I please get some guidance from an experienced person?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Any idea what's on it now? Check the rom info in Settings, About Phone.
Also power it off, pull the battery, put it back in and turn the phone back on while holding Volume down, that'll get you the bootloader. See what version you have and if it's s-on or s-off.
From there you can select Recovery on the menu and boot into it, see what recovery you have.
Let us know and we can go from there.
Sent from my ADR6425LVW using xda app-developers app
undeadking said:
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Looks like just the stock rom. What version hboot, are you s-on/off and what recovery do you have?
Just did what you said and took some pictures that i will post to show you what I'm working with.
Sent from my DROID RAZR HD using xda app-developers app
Is this the right information that you needed to know?
Sent from my ADR6425LVW using xda app-developers app
undeadking said:
Is this the right information that you needed to know?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You are already unlocked and have Amon Ra recovery installed, the "hard" stuff is done (actually it's not hard), and FYI you are S-ON... You are pretty good to go for any ICS based ROM. If you want to move into JellyBean or KitKat based ROMs you should switch to TWRP or CWM Recovery. Other than that, your good to go.
Ok, thanks a bunch! Ive done tons of reading about flashing roms and am still a little weary about the actual process. Ive read that a computer is needed in some cases but in others people are switching roms right from their phone- whats the safest or correct way to do it?
Sent from my DROID RAZR MAXX HD using xda app-developers app
undeadking said:
Ok, thanks a bunch! Ive done tons of reading about flashing roms and am still a little weary about the actual process. Ive read that a computer is needed in some cases but in others people are switching roms right from their phone- whats the safest or correct way to do it?
Sent from my DROID RAZR MAXX HD using xda app-developers app
Click to expand...
Click to collapse
Although there are ways around it (that I don't recommend, mind you) the rule of thumb is based on whether you are S-ON or S-OFF...
When S-ON, a computer has to be involved so that the boot.img can be loaded... you must either: A) flash the boot.img manually with fastboot after flashing the ROM in recovery, or B) boot the recovery image file with fastboot and flash the ROM file
When S-OFF, no computer is required, all partitions of the phone are writable by recovery directly.
acejavelin said:
Although there are ways around it (that I don't recommend, mind you) the rule of thumb is based on whether you are S-ON or S-OFF...
When S-ON, a computer has to be involved so that the boot.img can be loaded... you must either: A) flash the boot.img manually with fastboot after flashing the ROM in recovery, or B) boot the recovery image file with fastboot and flash the ROM file
When S-OFF, no computer is required, all partitions of the phone are writable by recovery directly.
Click to expand...
Click to collapse
Don't forget you can use the phone (or a computer) to pack the boot.img into a PH98IMG.zip. As long as it boots, that is.
Hi All,
I am also new at rooting the Rezound and I'm having trouble. I did quite a bit of reading and followed the instructions here: theunlockr.com/2012/08/24/how-to-root-the-htc-rezound-video/
Apparently this was for an older version because I can't install ClockworkMod Recovery ("an error occurred ..."). I read that getting a backup of ClockworkMod Recovery was the best thing to do before installing any ROMs. Is that really necessary? It seems like I could always find an RUU on this site and flash back to ICS if I wanted to right?
Can some one point me in the right direction for what I should do next? Basically all I want to do is flash a ROM on my Rezound that will enable me to use it as a wall controller for my home automation system. So, ideally I'd like to remove the swipe to unlock feature (just be able to press the power button to get to the home screen) and to be able to force a nightly reboot with Tasker and remove as much bloatware as possible. This device is connected to my home network through wifi only. Any ideas what the best ROM would be for that?
By the way my recovery screen looks like undeadking's. I have S-On.
Thanks!
next
Easiest way to get where you want is to HTC unlock if not already done,
S-0ff with RumRunner, then follow this thread with all its great stuff:
http://forum.xda-developers.com/showthread.php?t=2509770
You will end up with newest radios that are best for newer stock and custom roms.
There are several daily-user type custom roms mentioned in Development.
After you read a little about each, you'll know what you want to try first.
I like the custom Sense roms for best battery life.
michaelbsheldon said:
Easiest way to get where you want is to HTC unlock if not already done,
S-0ff with RumRunner, then follow this thread with all its great stuff:
http://forum.xda-developers.com/showthread.php?t=2509770
You will end up with newest radios that are best for newer stock and custom roms.
There are several daily-user type custom roms mentioned in Development.
After you read a little about each, you'll know what you want to try first.
I like the custom Sense roms for best battery life.
Click to expand...
Click to collapse
Thanks, I was able to get my ROM working. The problem I was having was I was still S-ON. I was a little leery about turning it off so I found instructions for flashing with it still on here: androidforums.com/rezound-all-things-root/499172-how-manually-flash-roms.html
I installed the LiquidSmooth ROM and I was able to disable the lock screen. Thanks again.
acejavelin said:
Although there are ways around it (that I don't recommend, mind you) the rule of thumb is based on whether you are S-ON or S-OFF...
When S-ON, a computer has to be involved so that the boot.img can be loaded... you must either: A) flash the boot.img manually with fastboot after flashing the ROM in recovery, or B) boot the recovery image file with fastboot and flash the ROM file
When S-OFF, no computer is required, all partitions of the phone are writable by recovery directly.
Click to expand...
Click to collapse
There are ways using terminal emulator with an s-on device alongside using a proper busybox installation to flash without using a pc and no fastboot/hboot access is needed. flashing a boot.img while in rom, rebooting to recovery and finish installing the matching rom by flashing its zip.
petewill8 said:
Thanks, I was able to get my ROM working. The problem I was having was I was still S-ON. I was a little leery about turning it off so I found instructions for flashing with it still on here: androidforums.com/rezound-all-things-root/499172-how-manually-flash-roms.html
I installed the LiquidSmooth ROM and I was able to disable the lock screen. Thanks again.
Click to expand...
Click to collapse
the one big issue you need to worry about while being s-on is if you soft brick while s-on there is absolutely almost no fix...with s-off you con ruu.exe to safely restore your phone which you cannot do while s-on....if you plan on flashing custom roms alot than i HIGHLY suggest going s-off or you'll regret not doing so when that time comes
REV3NT3CH said:
the one big issue you need to worry about while being s-on is if you soft brick while s-on there is absolutely almost no fix...with s-off you con ruu.exe to safely restore your phone which you cannot do while s-on....if you plan on flashing custom roms alot than i HIGHLY suggest going s-off or you'll regret not doing so when that time comes
Click to expand...
Click to collapse
I second this... S-Off is highly recommended, it might not seem necessary now, but when something goes wrong, you will be glad you did it.
Thank you both. I had not read that before. I guess I will be performing the S-Off after all.
Don't freak out if your ROM doesn't boot after running rum runner happened to me xD just go into recovery and flash your stuff again. Clean flash it. Make sure you're s-off though Lol hopefully doesn't happen to you
Sent from my Rezound. CyanogenMod 11. S-off
pball52998 said:
Don't freak out if your ROM doesn't boot after running rum runner happened to me xD just go into recovery and flash your stuff again. Clean flash it. Make sure you're s-off though Lol hopefully doesn't happen to you
Sent from my Rezound. CyanogenMod 11. S-off
Click to expand...
Click to collapse
Just do a quick backup of your ROM in recovery then when done restore it.
Sent from my Rezound using xda app-developers app
Just a thing. All my recoveries failed all 4, they would do the same thing and boot loop itself. *sigh* o well.
Sent from my Resound using tapatalk. CyanogenMod 11. S-off.