Evo3d had same s-on, place your recovery image in your same folder as fastboot and adb and do: fastboot boot recovery.img(assuming you renamed your amon ra to recovery) and flash anything. I think even radios but dont know that one for sure.
Link:http://forum.xda-developers.com/showthread.php?t=1239821
1) I don't think belongs in development. 2) You cannot flash radios with S-ON. 3) http://forum.xda-developers.com/showthread.php?t=1419587 4) Not really any new or useful information.
I understand there are other way to do this but you can just flash a single zip in the phones recovery this way. then a dev can do roms including a costum kernel and flash as one. Like normal. Not to mention devs make one package. Just seems so much easier to me.
lawnguy said:
I understand there are other way to do this but you can just flash a single zip in the phones recovery this way. then a dev can do roms including a costum kernel and flash as one. Like normal. Not to mention devs make one package. Just seems so much easier to me.
Click to expand...
Click to collapse
If the devs could do this on the Rezound where you can install everything using one zip they would be doing so.
I suspect the largest reason this hasn't happened is the lack of s-off devices in developers hands to build with.
Sent from my ADR6425LVW using Tapatalk
The drawback is it requires fastboot. that is hard for some people. I use this type of stuff myself, but I make easy tools for people anyway.
Deathbyfugu said:
If the devs could do this on the Rezound where you can install everything using one zip they would be doing so.
Click to expand...
Click to collapse
There IS a way of installing kernels with a single zip on the Rezound... DSB did that with his kernel for the Rezound on rootzwiki. It basically still is two steps, but simplified into one zip and a script that automatically reboots to the bootloader and installs the boot.img from there.
a.mcdear said:
There IS a way of installing kernels with a single zip on the Rezound... DSB did that with his kernel for the Rezound on rootzwiki. It basically still is two steps, but simplified into one zip and a script that automatically reboots to the bootloader and installs the boot.img from there.
Click to expand...
Click to collapse
That is not the way to do it. It uses a hardcoded boot image which is BAD.
Con, I've seen the automated script you made and that's cool. I just wanted to add what we had done with the 3d. But certainly appreciate your work.
lawnguy said:
Con, I've seen the automated script you made and that's cool. I just wanted to add what we had done with the 3d. But certainly appreciate your work.
Click to expand...
Click to collapse
I understand that. I prefer using fastboot and the methods you have described. But a hardcoded boot.img is not good for people with custom roms... if a rom needs a customized boot image and you flash dsb's kernel, you might have a bootloop on your hands.
Thread reported, this is ridiculous. How can you not understand not to post in development?
Related
So I made a toolkit for 3 HTC phones. You can see them in my signature. Would you guys / girls be interested in using a toolkit for an All-In-One use. If so, please let me know and I can work on it and probably have it up by tonight. Thanks!
hasoon2000 said:
So I made a toolkit for 3 HTC phones. You can see them in my signature. Would you guys / girls be interested in using a toolkit for an All-In-One use. If so, please let me know and I can work on it and probably have it up by tonight. Thanks!
Click to expand...
Click to collapse
Actually looks pretty cool and convenient. I think it would be welcomed for the Rez.
WasabiWa83 said:
Actually looks pretty cool and convenient. I think it would be welcomed for the Rez.
Click to expand...
Click to collapse
Thanks. If I can get another person or 2 to confirm, I will work in it. Just want to make sure my tool and I will be welcomed!
hasoon2000 said:
Thanks. If I can get another person or 2 to confirm, I will work in it. Just want to make sure my tool and I will be welcomed!
Click to expand...
Click to collapse
Yeah, I wouldn't trust WasabiWa's opinion either.
It looks like it would come in handy for a lot of folks, especially those that don't like using the cmd prompt on their pc.
feralicious said:
Yeah, I wouldn't trust WasabiWa's opinion either.
It looks like it would come in handy for a lot of folks, especially those that don't like using the cmd prompt on their pc.
Click to expand...
Click to collapse
Haha. I bet he's a nice guy. I guess ill work on it for you guys!
Sent From My HTC Amaze 4G via Someone's Room
feralicious said:
Yeah, I wouldn't trust WasabiWa's opinion either.
It looks like it would come in handy for a lot of folks, especially those that don't like using the cmd prompt on their pc.
Click to expand...
Click to collapse
Except that I know everything. Therefore, my opinion should be trusted.
EDIT: I'm a very nice guy. And you appear to be, as well. So, yes, make this for us!
WasabiWa83 said:
Except that I know everything. Therefore, my opinion should be trusted.
EDIT: I'm a very nice guy. And you appear to be, as well. So, yes, make this for us!
Click to expand...
Click to collapse
haha. I think you should make me a custom sig
I just have to browse through the dev section and collect all the files first.
hasoon2000 said:
haha. I think you should make me a custom sig
I just have to browse through the dev section and collect all the files first.
Click to expand...
Click to collapse
I'd love to make you a custom sig! Just pm me if you want to and we'll figure it out.
WasabiWa83 said:
I'd love to make you a custom sig! Just pm me if you want to and we'll figure it out.
Click to expand...
Click to collapse
Will do!
Just a question though. With flashing kernels, you have to flash it via recovery and then bootloader? For the Amaze / Sensation / Vivd, we can flash it just through the computer. I am trying to get a better idea so I can make the tollkit correct.
hasoon2000 said:
Will do!
Just a question though. With flashing kernels, you have to flash it via recovery and then bootloader? For the Amaze / Sensation / Vivd, we can flash it just through the computer. I am trying to get a better idea so I can make the tollkit correct.
Click to expand...
Click to collapse
Pretty sure it's only bootloader for the kernel or fastboot for just the boot.img. Can't flash them through recovery, I don't think.
I am trying to find the boot.img for the kernels. If I can't find them, then I am done with the toolkit. If I can find them, then I can add it to the toolkit. I only found the flashable zip.
hasoon2000 said:
I am trying to find the boot.img for the kernels. If I can't find them, then I am done with the toolkit. If I can find them, then I can add it to the toolkit. I only found the flashable zip.
Click to expand...
Click to collapse
They're all in the PH98IMG.zip files.
WasabiWa83 said:
Pretty sure it's only bootloader for the kernel or fastboot for just the boot.img. Can't flash them through recovery, I don't think.
Click to expand...
Click to collapse
Correct. Modules for the kernel can be flashed in recovery, but the actual boot.img must be flashed in hboot.
Sent from my ADR6425LVW using XDA App
WasabiWa83 said:
They're all in the PH98IMG.zip files.
Click to expand...
Click to collapse
I am reading the instructions and they say "Flash in recovery, it will copy the modules and then reboot to hboot. Select bootloader and select yes to flashing PH98IMG.zip."
hasoon2000 said:
I am reading the instructions and they say "Flash in recovery, it will copy the modules and then reboot to hboot. Select bootloader and select yes to flashing PH98IMG.zip."
Click to expand...
Click to collapse
Yeah, what nosympathy said. The kernel itself isn't flashed in recovery.
hasoon2000 said:
I am reading the instructions and they say "Flash in recovery, it will copy the modules and then reboot to hboot. Select bootloader and select yes to flashing PH98IMG.zip."
Click to expand...
Click to collapse
Yes, and then in that PHzip file is the boot.img which can also be flashed on its own in fastboot if pulled out of the PHzip file.
Sometimes that is the preferred method since the phones and kernels are not always on the same mainver and if the text file included in the PHzip file has a different mainver than the phone it is being flashed to there will be an error. The error can be fixed by editing the mainver in the text file before flashing it, but flashing in fastboot avoids the error.
Some ICS ROM's brought people's mainver up to 3.x. Original stock was at 1.x and with the OTA stock is now 2.x. I believe most ROMs are on 2.x but there is a good number of people whose phones got updated to the 3.x version.
I can have the modules flash when the phone is on. That is how we flash the modules and can I just flash the boot.img via fastboot instead of the PH98IMG.zip?
Remember, I don't have the phone so I can't test it, so please bare with me lol.
Toolkit would be awesome.
Sent from my HTC Rezound using xda premium
hasoon2000 said:
I can have the modules flash when the phone is on. That is how we flash the modules and can I just flash the boot.img via fastboot instead of the PH98IMG.zip?
Remember, I don't have the phone so I can't test it, so please bare with me lol.
Click to expand...
Click to collapse
Yes. Flash the boot.IMG via fastboot.
Sent from my HTC Rezound using xda premium
hasoon2000 said:
I can have the modules flash when the phone is on. That is how we flash the modules and can I just flash the boot.img via fastboot instead of the PH98IMG.zip?
Remember, I don't have the phone so I can't test it, so please bare with me lol.
Click to expand...
Click to collapse
I think so, but some people seem to be uncomfortable using fastboot. But using this tool it seems it won't be as daunting since they won't have to use the cmd prompt on the pc, right? How would it work?
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 ported an unofficial build of CM7 over to the Rezound from the Sensation. I’m not sure why, but the ROM will not boot past the splash screen, so I am going to turn this into a community WIP.
ROM Progress Synopsis :
- Rom was ported over from the HTC Sensation
- A custom kernel was compiled from CM7 source
Working:
Unknown
Not Working
Unknown
Here is what I have done so far.
Since our device isn’t officially supported by CM7, this ROM was ported from a CM7.a3 rom from the Evo3D. Porting from the Evo shouldn’t be a problem since the devices are very similar, both having the msm8660 chipset.
The base ROM that was used was a stock vigor OTA.
Files that were injected in to the base ROM from the CM7 ROM:
- /system/app folder minus phone and Bluetooth
- /system/framework
- /system/fonts and /system/media
- necessary /system/lib files including libandroid_runtime.so
- init.d
- necessary permissions
- altered build.prop
- custom update script
How to install:
NOTE: THIS ROM CURRENTLY DOESN'T BOOT. This is currently a WORK IN PROGRESS and no promises are made that a fully functional ROM will be produced from these efforts. The purpose of this thread is to collaborate all of our CM7 efforts into one thread. DON'T GET YOUR HOPES UP.
As of now, this ROM is GB only. Here is an excellent thread explaining GB/ICS firmware combos: clicky Thanks superchilpil
Disclaimer: I am not responsible for any harm that comes to you or your device by flashing my stuff. Do this at your own risk.
Download link: quada_CM7_20120716
This is a COMMUNITY PROJECT. I want help working on this so we can get this stable as fast as possible. If you are able to help with this project, don’t be afraid to contact me on this thread, PM me, or tweet me Quada03.
Changelog
20120716 - Rebased of off HTC Pyramid (Sensation) which is slightly closer to our device (no 3D screen)
20120715– initial port from Evo 3D
To do list
Replace libaudio.so in system files
Try to find someone who still has the CM7 tree/repo from GB Pyramid. This way we can build straight from source.
ROM Progress:
As of right now, the ROM will not boot past the splash screen. I did a logcat and there are no fatal errors but an audio driver seems to be in a constant loop. I’ll see if I can post a pastebin later today.
Nice work bro. Can't wait to see where this heads
Sent from my Rezound
This would be awesome but again, there is no working RIL for any aosp variation. That will be your biggest hurdle.....
+ 10000000
...
siulmagic said:
...
Click to expand...
Click to collapse
??
he just saving place for future
Erm, why does this require a different HBOOT?
Exciting. Can't wait to see this get worked on more.
Chyrux said:
Erm, why does this require a different HBOOT?
Click to expand...
Click to collapse
You can't flash boot.img files with the stock hboot. If you want to work on the ROM and don't want to switch hboots, a PH98IMG zip could be made in 10 seconds, but I am constantly switching kernels to see if that is part of the problem. I hate always having a PH98IMG on the SD card. It makes it a pain to go back into recovery.
Quada said:
You can't flash boot.img files with the stock hboot. If you want to work on the ROM and don't want to switch hboots, a PH98IMG zip could be made in 10 seconds, but I am constantly switching kernels to see if that is part of the problem. I hate always having a PH98IMG on the SD card. It makes it a pain to go back into recovery.
Click to expand...
Click to collapse
Most people here understand this, they are more than likely s-off and if they are s-off then they already have a custome hboot
The ones who choose to stay s-on have to deal with the consequences
Sent from my ADR6425LVW using Tapatalk 2
Quada said:
You can't flash boot.img files with the stock hboot. If you want to work on the ROM and don't want to switch hboots, a PH98IMG zip could be made in 10 seconds, but I am constantly switching kernels to see if that is part of the problem. I hate always having a PH98IMG on the SD card. It makes it a pain to go back into recovery.
Click to expand...
Click to collapse
Yeah, you can. I'm s–on and I don't bother with ph98 zips. I just flash the boot.img and have never had a problem lol
Sent from my ADR6425LVW using Tapatalk 2
Chyrux said:
Yeah, you can. I'm s–on and I don't bother with ph98 zips. I just flash the boot.img and have never had a problem lol
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
You are S-ON with the stock HBOOT and you can flash boot.img? I'm not saying you are for sure wrong, but my stock hboot would not let me flash another boot.img.
Maybe he's referring to flashing from hboot and not recovery
Sent from my ADR6425LVW using Tapatalk
Quada said:
You can't flash boot.img files with the stock hboot. If you want to work on the ROM and don't want to switch hboots, a PH98IMG zip could be made in 10 seconds, but I am constantly switching kernels to see if that is part of the problem. I hate always having a PH98IMG on the SD card. It makes it a pain to go back into recovery.
Click to expand...
Click to collapse
You're talking about the difference of being S-On vs S-Off, not stock hboot vs modified hboot. The main thing a stock hboot won't allow is using fastboot commands. If you install a recovery via PH98IMG.zip, then most people won't miss fastboot commands. I've always been on stock hboot since being S-Off.
Yes I've been waiting for this
Sent from my iPad using Tapatalk HD
nolimit78 said:
Maybe he's referring to flashing from hboot and not recovery
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
This.
destro158 said:
You're talking about the difference of being S-On vs S-Off, not stock hboot vs modified hboot. The main thing a stock hboot won't allow is using fastboot commands. If you install a recovery via PH98IMG.zip, then most people won't miss fastboot commands. I've always been on stock hboot since being S-Off.
Click to expand...
Click to collapse
I use JBs hboot to modify the kernel with fastboot commands in HBOOT. A stock hboot will not allow for this, I believe the only way would be to use a PH98IMG or flash a kernel in recovery using a script. I just feel that flashing in fastboot is much easier.
fastboot flash boot boot.img
or
fastboot boot zimage zImage
Quada said:
I use JBs hboot to modify the kernel with fastboot commands in HBOOT. A stock hboot will not allow for this, I believe the only way would be to use a PH98IMG or flash a kernel in recovery using a script. I just feel that flashing in fastboot is much easier.
fastboot flash boot boot.img
or
fastboot boot zimage zImage
Click to expand...
Click to collapse
I do that in stock hboot even when I was s-off...
Hey guys,
I'm a long time android user,I've dealt with HTC mytouch 4g and evo then moved on to Motorola droid razr and then the gs3,I came back to HTC because their phones feel more better in the hand and have better specs in my opinion. I've rooted plenty of phones and I have one question,I'm seeing a lot of instructions of how to unlock,s-off but one thing that doesn't make sense is loading a boot.img for every rom? If I'm correct,I have to flash any given Rom and then flash a boot.img and then do a different method for a custom kernel? I thought I could load a custom Rom and a custom kernal in a custom recovery? Please forgive me for asking a lot of questions but it seems the whole custom Rom methods has changed for specifically HTC phones? Is all this due to locked bootloaders?
Sent from my HTC6435LVW using xda premium
ali87va said:
Hey guys,
I'm a long time android user,I've dealt with HTC mytouch 4g and evo then moved on to Motorola droid razr and then the gs3,I came back to HTC because their phones feel more better in the hand and have better specs in my opinion. I've rooted plenty of phones and I have one question,I'm seeing a lot of instructions of how to unlock,s-off but one thing that doesn't make sense is loading a boot.img for every rom? If I'm correct,I have to flash any given Rom and then flash a boot.img and then do a different method for a custom kernel? I thought I could load a custom Rom and a custom kernal in a custom recovery? Please forgive me for asking a lot of questions but it seems the whole custom Rom methods has changed for specifically HTC phones? Is all this due to locked bootloaders?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
yeah the whole s-on and off creates some confusion but you can have s-on and still flash custom recoveries and kernels,
I havent really found a need to achieve s-off yet (probably when the unofficial cm10 release is complete i will), but i would leave s-off.
Having to flash roms is easy and pretty straightforward. I also had trouble with flashing kernels in which case you flash the boot image and then flash the zip. It also depends how they are packaged, because the boot.img is sometimes packaged in the zip in which case you have to unzip it to get the img and the zip and then flash the new zip after the img.
I've also been an android user a decent amount of time but it seems like htc devices are slightly more complicated.
almo40192 said:
yeah the whole s-on and off creates some confusion but you can have s-on and still flash custom recoveries and kernels,
I havent really found a need to achieve s-off yet (probably when the unofficial cm10 release is complete i will), but i would leave s-off.
Having to flash roms is easy and pretty straightforward. I also had trouble with flashing kernels in which case you flash the boot image and then flash the zip. It also depends how they are packaged, because the boot.img is sometimes packaged in the zip in which case you have to unzip it to get the img and the zip and then flash the new zip after the img.
I've also been an android user a decent amount of time but it seems like htc devices are slightly more complicated.
Click to expand...
Click to collapse
I think a lot of people (like me) got into rooting phones where the phone we owned already had s-off and as such all the roms we were flashing were made while that was true. The DNA has only recently had s-off so most of the roms were made with s-on being the only option.They needed the boot image flashed seperately to work. My understanding now is even with s-off, if the rom was made prior to s-off, you still have to flash an image file. Probably soon enough most will not need that extra step.
In a simple nutshell, the s stands for security flag, and prevents access of the boot partition from recovery, as well as low level stuff like firmware.
Turning security off, known as s off, allows a user to write to the boot partition (like a boot.img) and write firmware such as the radios (telephony and modem firmware) from recovery.
So s off has pros and cons. It's there as a protective measure, and being s on slows the HTC Dev bootloader tool to be a reality and still have a safety measure in place for the general public that doesn't know squat and doesn't follow the forums or keep up with their device's software.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
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