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
Related
I am S-Off with AmonRa 3.15 Unlocked, Rooted and have the GB Stock Sense.
Things seemed a lot simpler with the DInc. Load the RUU on the SD, change the name zip and boot it from the boot loader.
From what I am reading, I have to flash the newest leaked ROM, then install AmonRa 3.15 again, then load the radios?
Doesn't sound or seem right and I know I will end up screwing something up.
Can someone give me a step by step instruction on this? Do I have to name each file PH98IMG.zip, install it then delete it and load another to install?
I am not understanding it.
Lmao wtf ?
Grab the ruu file, rename it to ph98img.zip and put on root of sdcard. Itll update firmware, rom, radios in one shot. Then you reinstall aromra and why are you s off and unlocked ? Point of soff is to be locked and still be rooted. I think you probably misread some threads wrong but good luck, hope i helped
Sent from my ADR6425LVW using Tapatalk 2
Btw if your unlocked, you cant run the ruu i believe. Better relock first .
Sent from my ADR6425LVW using Tapatalk 2
I know I did. I thought I had to unlock to root so I did. There are so many variations of the update threads going around. S-On, S-Off, S-On, Unlocked, Rooted. I can't keep this crap straight. That is why I am asking.
Thank you
i suggest reading this thread to get a better idea of everything involved.
but yes, phones change and evolve. they're not all the same, so you gotta roll with it.
If you're s-off I don't think you'll have to relock. But it's a total wipe of the phone, so you'll have to reinstall Amon Ra. You'll lose everything except your external SD card.
Back up your internal SD, and anything you care about.
Put the RUU on your external SD named as PH98IMG.zip. MD5 it *after* you put it on the SD card to ensure a perfect transfer.
Shut off phone, pull battery. Put battery in.
Start bootloader with volume and power keys. Everything's automatic from there. Volume up to say Yes when prompted. Process restarts automatically if the RUU has to flash your HBOOT.
On first boot, go straight to the SD card and rename that PH98IMG.zip file so you don't lock yourself out of recovery.
Now shut down and do the battery thing again.
Start bootloader and do the factory system reset/wipe. This is your last and only chance to fix any corruption in the radio partition, and you need to do this before flashing Amon Ra. You'll see the recovery screen and a progress bar that just twirls. When done the phone reboots automatically.
You may now shut down and install Amon Ra. In my experience, the phone will remain unlocked, and you can flash from fastboot if you prefer.
I haven't tried rooting the leak from Amon Ra because I usually just apply a rooted ROM from this point.
Be careful what ROMs you apply, because some ROMs may "upgrade" your kernel to an older version. In my limited experience, the one on the RUU is the best one.
Well, this changed me to Sense 3.5 software number 2.01.605.11 I downloaded Scott's Stock Rooted RUU 3.14.605.5 LOL!
Told you **** never works right when I do it.
Going to try relocking and running again
superchaos said:
Going to try relocking and running again
Click to expand...
Click to collapse
You don't need to relock, you just need the right file. Scott's rooted 3.14 is a ROM, not the RUU. You need the actual RUU. The name of his thread is a little confusing as it is based on the newest leaked RUU but is not bootloader flashable via the PH98IMG.zip method. Get the real RUU and follow the excellent instructions above.
The PH98IMG in that post is not the full RUU and is only for the special case that he outlines in the first post under "install instructions".
Sent from my ADR6425LVW using Tapatalk 2
Got it. Couldn't install under HBOOT. Had to do it under recovery and couldn't use the PH98IMG file name. Just left Scott's as named in the download.
Thanks again
superchaos said:
Got it. Couldn't install under HBOOT. Had to do it under recovery and couldn't use the PH98IMG file name. Just left Scott's as named in the download.
Thanks again
Click to expand...
Click to collapse
Should somebody tell him all he did was load a rom? If you did it via recovery neither your hboot or radios were updated.........
Sent from my ADR6425LVW using Tapatalk 2
Shiznit14 said:
Should somebody tell him all he did was load a rom? If you did it via recovery neither your hboot or radios were updated.........
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Tried to tell him that was a ROM and not the RUU... He'll figure it out soon enough.
JinxtPhoto said:
Tried to tell him that was a ROM and not the RUU... He'll figure it out soon enough.
Click to expand...
Click to collapse
Haha that's funny
Sent from my Dinc... I mean 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...
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
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 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.