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
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 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
Why does search turn up nothing for this?
I thought with S-Off and Root and 4ext, all my problems would be solved; sadly no! I can't flash kernels because the write_raw_image assert fails.
Why is this, and what can I do to get around it permanently, besides buying Flash Image Gui? Perhaps extract something from a kernel and flash that to fastboot boot boot.img?
For others that run into this problem, I have Virgin Mobile Evo V 4G.
Is this with every ROM you try to flash or just certain ones?
coal686 said:
Is this with every ROM you try to flash or just certain ones?
Click to expand...
Click to collapse
Hadn't gotten to ROMs yet was just trying to get a non-stock kernel.
Every kernel I tried, didn't work.
This was confusing.
https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui&hl=en
I bought Flash Image GUI, $1.* Only have to use it once, from then on you can flash kernels to your hearts content. Something was preventing 4ext recovery from writing to /boot. Thought S-Off removed all that. Whatever. Flash Image GUI opened up my current boot.img, ripped the wifi, Wimax modules from it and inserted them into MAC Sense-Kernel 3.1 that I had been trying to install, then used my SuperUser/Root in Android to flash the kernel + modules as a boot.img to my /boot.
Now that /boot is "unsecured", there is nothing (what was doing it in the first place?) blocking me from flashing in recovery going forward.
Phew. These phones getting more confusing and complicated by the day.
*I think you can just use TWRP2 or this: http://teamw.in/project/htcdumlock
rancur3p1c said:
Now that /boot is "unsecured", there is nothing (what was doing it in the first place?) blocking me from flashing in recovery going forward.
Phew. These phones getting more confusing and complicated by the day.
*I think you can just use TWRP2 or this: http://teamw.in/project/htcdumlock
Click to expand...
Click to collapse
You shouldn't need Flash Image GUI, 4EXT SmartFlash or TWRP dumlock if you are S-OFF. Those are all tools designed to help S-ON users that can't update the boot partition in recovery without starting it from fastboot.
Were you able to flash the RUU.exe and the OTA update successfully?
ramjet73
This is my case when flashing a MIUI ROM with a signed boot.img.
Check out this link: HTC EVO 3d Kernel flash issue
Greetings.
copecu said:
This is my case when flashing a MIUI ROM with a signed boot.img.
Check out this link: HTC EVO 3d Kernel flash issue
Greetings.
Click to expand...
Click to collapse
Yes, that's a specific configuration that causes a problem but the OP of this thread is having problems with kernels that everyone else is flashing with no problems. I'm sure the cause in this case is some sort of misunderstanding.
ramjet73
ramjet73 said:
You shouldn't need Flash Image GUI, 4EXT SmartFlash or TWRP dumlock if you are S-OFF. Those are all tools designed to help S-ON users that can't update the boot partition in recovery without starting it from fastboot.
Were you able to flash the RUU.exe and the OTA update successfully?
ramjet73
Click to expand...
Click to collapse
Yes tried a second time like you mentioned completed just fine. Oh well, works now.
ramjet73 said:
Yes, that's a specific configuration that causes a problem but the OP of this thread is having problems with kernels that everyone else is flashing with no problems. I'm sure the cause in this case is some sort of misunderstanding.
ramjet73
Click to expand...
Click to collapse
Beats me. I tried every configuration every kernel couldn't get anything to flash smart mode on or off.
If I am S-On, is there a way to set it up so that i don't have to manually flash the boot.img every time? Btw, I am using TWRP
TRWP includes HTC Dumlock which makes it easier, but you'll always have to do some level of extra work when you're s-on. That's just the facts of life with HTC.
gleggie said:
If I am S-On, is there a way to set it up so that i don't have to manually flash the boot.img every time? Btw, I am using TWRP
Click to expand...
Click to collapse
S-off your phone, it's the only way to allow boot.img to be installed automatically along with a rom/kernel installer/etc..
Check out the second section of the TWRP OP: http://forum.xda-developers.com/showthread.php?t=1902381
It basically replaces your bootloader with a copy of recovery that is allowed to flash boot.img files directly, after which you have to replace the default boot again before you can boot. It lets you flash a kernel completely PC free, but it doesn't necessarily make it easier or simpler. There are still extra steps involved if you are s-on.
mjones73 said:
S-off your phone, it's the only way to allow boot.img to be installed automatically along with a rom/kernel installer/etc..
Click to expand...
Click to collapse
If you don't flash often I don't recommend going s-off. It makes it easier to brick the phone.
feralicious said:
If you don't flash often I don't recommend going s-off. It makes it easier to brick the phone.
Click to expand...
Click to collapse
I was just pointing out the only way to avoid manually flashing boot.img is to s-off.
Personally I've been s-off since the day the process was released and I've flashed numerous roms without issue.
I installed CM using CWM onto my HTC Deluxe. I tried 4 different nightlies and the 10.2 stable and after installing any of them, I get this... it reboots into the white htc screen with a quick vibrate. Then it goes black for a second and reboots again. No CM screen or anything!
I've tried flashing it multiple times, doing factory resets, clearing cache and dalvaic cache. I am at a loss as to what to do next.
Oh and with the 10.2, instead of rebooting it just gets stuck at the HTC white screen!
If you unlocked the bootloader with htcdev.com and are still S-On, you need to flash the boot.img via fastboot. Common cause of your type of problems.
es0tericcha0s said:
If you unlocked the bootloader with htcdev.com and are still S-On, you need to flash the boot.img via fastboot. Common cause of your type of problems.
Click to expand...
Click to collapse
Well I looked and sure enough it is s-on. So I know the process of flashing an img with flashboot, but where can I aquire the correct boot.img? I am sure it needs to be a trusty source because I would imagine the boot image could really cause damage.
alexander7567 said:
Well I looked and sure enough it is s-on. So I know the process of flashing an img with flashboot, but where can I aquire the correct boot.img? I am sure it needs to be a trusty source because I would imagine the boot image could really cause damage.
Click to expand...
Click to collapse
You just need to extract it from whichever version of CMrom.zip you are trying to use.
es0tericcha0s said:
You just need to extract it from whichever version of CMrom.zip you are trying to use.
Click to expand...
Click to collapse
Okay cool! Easy enough. Question before I do this though... If I flash boot.img with fastboot, will this acheive soff? Neither rumrunner or Firewater works! And if I do this what will have have to do to go back to my stock Rom for any reason using CWM?
alexander7567 said:
Okay cool! Easy enough. Question before I do this though... If I flash boot.img with fastboot, will this acheive soff? Neither rumrunner or Firewater works! And if I do this what will have have to do to go back to my stock Rom for any reason using CWM?
Click to expand...
Click to collapse
No, this will not affect S-On/Off status. This is because the bootloader unlock provided by HTC is really only a partial one. It allows you to install custom roms, themes, mods, etc, but not to allow installation of a custom kernel through recovery. That's why you have to pull it from the rom and flash it separate. Once you do that, then it will behave like normal. You can also use an app like Flashify to install the boot.img, then boot to recovery and flash the rom, if you don't have access to a PC. Just make sure to do a nandroid BEFORE that, otherwise it will back up the new kernel you flashed on top of the older OS, so might not be compatible, especially when switching between stock and CM based things.