Related
I'm on HBOOT 1.5 and have unlocked my phone the HTC unlock method and from what I've read and understand the only drawback is that I have to use fastboot in order to write to the boot area and properly flash a ROM (which I have done many times and am very familiar with the process), or I can just use the Flash Image GUI app (which I have also used many times). Are there other restrictions I'm not aware of?
petermg said:
I'm on HBOOT 1.5 and have unlocked my phone the HTC unlock method and from what I've read and understand the only drawback is that I have to use fastboot in order to write to the boot area and properly flash a ROM (which I have done many times and am very familiar with the process), or I can just use the Flash Image GUI app (which I have also used many times). Are there other restrictions I'm not aware of?
Click to expand...
Click to collapse
Nope, not that bad at all as far as I can tell. I'm running CM9 and love it
like it was my wife. I couldn't care less about more time in the command
prompt because if you don't use it you loose it. My 3D with HB 1.5 has ICS
port and my wife's fully rooted 4G doesn't so I'm feeling pretty good about
my HB 1.5 3D right now!
I don't have hboot 1.5 but I think you can use boot manager also which let's you install multiple roms on your ad card and let's you boot into them.
I blame 1.5hboot HTC method for random reboots and soft freezes
No issues with hboot 1.5 No reboots no nothing just some minor steps when it comes to flashing.
Sent from my PG86100 using xda premium
Don't you guys have to be connected to a computer in order to flash a rom?
oohaylima said:
Don't you guys have to be connected to a computer in order to flash a rom?
Click to expand...
Click to collapse
not with flash gui
Sent from my PG86100 using XDA
oohaylima said:
Don't you guys have to be connected to a computer in order to flash a rom?
Click to expand...
Click to collapse
nope just flash in recovery. if the rom has a custom kernel i just use flash img gui and it extracts the kernel and flashes it for you the just reboot in to recovery and flash the rom.
the only thing with 1.5 is we can't flash radios or splash screens.
Excellent. I thought you guys had to go through an elaborate process to install a Rom.
No, not really. Also, intentional brick method ftw.
there are many customization optiom option just like changing splash screen, cpu overclock, and many more for advance user.
Sent from my SCH-I500 using Tapatalk
jdeoxys said:
No, not really. Also, intentional brick method ftw.
Click to expand...
Click to collapse
I seen that method not a total brick tho if you do brick your phone it will behave like one no power. Dead
Sent from my PG86100 using xda premium
stevestone said:
there are many customization optiom option just like changing splash screen, cpu overclock, and many more for advance user.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
I could already do an overclocked CPU with HBOOT 1.5, so I'm sure I could do the other things you mentioned also. Where can I find splash screens for the EVO 3D? I just did the HBOOT downgrade here because I like a challenge, not because I think I needed to. My wife is still on HBOOT 1.5. I'm just not sure having HBOOT 1.5 is really that bad a thing. I don't think there is anything you can't do with HBOOT 1.5 execpt that you need to use the computer or flash image gui.
EDIT: Oh and I never had any reboot issues or whatnot as someone else associated with HBOOT 1.5. Not that I ever noticed.
hboot 1.5 is not all that bad for your average user.
For "power users" it is a nightmare because it makes it a pain to flash kernels. Okay, maybe not a pain, but still. We like more control over our devices to be able to flash things where ever we'd like. Also, HTC's unlock makes the bootloader unable to accept PG86IMG.zips, which means flashing them via bootloader doesn't work. What does that mean? No "all-in-one" firmware update packages when new software versions are released. Lastly, no splash screen flashing. While this isn't a big deal, it still allows one to further customize their device.
I for one am very happy to be back on eng hboot 1.04 and thanks to the efforts of Unknownforce and everyone involved, this got made possible and for power users, it will make phone exchanges less of a risk.
I dont know... I dont really see the differences
For me personally, yes, its a terrible curse on my phone. For one, I couldn't change that super bright HTC splash screen, also I couldn't make or restore a nandroid backup unless I was fastbooted into recovery, which means I had to be at my computer. Fastbooting into recovery was just a command away, and id unplug from the computer right after booting to recovery so that I wasn't stuck at the computer, but still, I had to have a comp. Lastly, I use boot manager so if I switch roms and it wouldn't boot, I have to flash to the boot partition, which means I had to be at a comp. That happened at work and I was without a phone all day. I was spoiled with s-off on my EVO 4g so its really hard to get used to the HTC unlock. Thankfully, I downgraded and I'm now s-off, and loving it.
xcpefrmreality said:
For me personally, yes, its a terrible curse on my phone. For one, I couldn't change that super bright HTC splash screen, also I couldn't make or restore a nandroid backup unless I was fastbooted into recovery, which means I had to be at my computer. Fastbooting into recovery was just a command away, and id unplug from the computer right after booting to recovery so that I wasn't stuck at the computer, but still, I had to have a comp. Lastly, I use boot manager so if I switch roms and it wouldn't boot, I have to flash to the boot partition, which means I had to be at a comp. That happened at work and I was without a phone all day. I was spoiled with s-off on my EVO 4g so its really hard to get used to the HTC unlock. Thankfully, I downgraded and I'm now s-off, and loving it.
Click to expand...
Click to collapse
Does the cwm recovery not allow you to make and restore backups normally then?
Sent from my GT-I9100
Atomix86 said:
Does the cwm recovery not allow you to make and restore backups normally then?
Sent from my GT-I9100
Click to expand...
Click to collapse
A nandroid backs up your boot partition, and when u restore, it writes to boot partition. With htcdev unlock u can't do that unless you fastboot (from comp) to recovery.
And this is kinda weird, but good, with htcdev unlock, cwm wouldn't let my phone charge with power off. Now that I'm 1.4 s-off. It will. Charged all night with power off.
Easy adb and a computer Your all set . Root is easy. Swapping kernels is fine too. Stock kernel isn't bad .
Sent from my PG86100 using xda premium
xcpefrmreality said:
A nandroid backs up your boot partition, and when u restore, it writes to boot partition. With htcdev unlock u can't do that unless you fastboot (from comp) to recovery.
Click to expand...
Click to collapse
I don't see what the problem is. Can you not keep the boot partition the same when backing up and restoring? It never stopped me doing anything when I had an S-On Wildfire S
Greetings
You see the question, does the current root method also give you S-Off or is there a seperate zip file for that?
Thanks
Not at the moment. Also root and s-off are two different things, think of root as the admin account on your PC, it lets you change almost anything within the OS itself. Think of S-OFF (or unlocked bootloader) as having the ability to OVERWRITE your OS with something different.
The only current way we have of overwriting our OS (flashing other ROMs) is through the HTC Dev unlock method but that will void your warranty.
EDIT: Here's the link if you want it, scroll down to "All other supported models"
http://htcdev.com/bootloader
OK so
so I am pretty limited as to what i can do at this time...right? And I don't want to do anything that wouldd cause me to have to pull a battery that wont pull lol.
Should I wait for S-Off before rooting?
Thanks
No, you're not pretty limited. Unlocked bootloader allows for custom recovery which allows for flashing ROMs and SU, etc.
With S-on, radios cannot be flashed, and you can run update IMGs thru bootloader, like a PC6IMG (or whatever the P code is for this phone).
sent from my Evo LTE, usually.
musicman625 said:
so I am pretty limited as to what i can do at this time...right? And I don't want to do anything that wouldd cause me to have to pull a battery that wont pull lol.
Should I wait for S-Off before rooting?
Thanks
Click to expand...
Click to collapse
I think only thing you can't do is flash kernels and aosp roms as they have different kernels
That and flash radios
Sent from my EVO using Tapatalk 2
Ep3n3wp said:
I think only thing you can't do is flash kernels and aosp roms as they have different kernels
That and flash radios
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I believe you can flash kernels through fastboot, at least that was the case with the Evo 3D.
Hello everyone
I am new to this forum, well I have been downloading roms for about 6 months but I registered today, anyhow I took my evo 3d to the sprint repair center the other day because my lcd went out, that's what the sprint employee had told me anyway and so two days later I received a replacement evo 3d, it was hboot 1.5 obviously and I took it home and installed the 2.17.651.5 RUU because sprint puts a version of the 2.17.651.5 ruu on their evo 3d's that does not communicate well during the unlock process of HTCdev.com, so here is my problem, after flashing the ruu I unlocked my bootloader via the htcdev unlock method, and began to flash my first custom rom, and I have run into the same problem over and over, I would boot into clockwordmod recovery via fastboot and then flash the rom after performing a super-wipe and every single time I would get a boot loop, no matter which rom I used, it would boot up and get to the setup screen and boot loop constant boot loop, every single rom I tried, I have not experienced this before when flashing roms, I then looked at a few threads of the roms I tried to flash and one recommended that I extract the boot.img from the zip and flash it via fastboot, some people say that you are required to do that with hboot 1.5 but in the past when I used my old evo 3d I never had to do that and it was hboot 1.5 s-on, please if someone has an answer I would gladly appreciate it, thanks in advance
UndefinedUser said:
Hello everyone
I am new to this forum, well I have been downloading roms for about 6 months but I registered today, anyhow I took my evo 3d to the sprint repair center the other day because my lcd went out, that's what the sprint employee had told me anyway and so two days later I received a replacement evo 3d, it was hboot 1.5 obviously and I took it home and installed the 2.17.651.5 RUU because sprint puts a version of the 2.17.651.5 ruu on their evo 3d's that does not communicate well during the unlock process of HTCdev.com, so here is my problem, after flashing the ruu I unlocked my bootloader via the htcdev unlock method, and began to flash my first custom rom, and I have run into the same problem over and over, I would boot into clockwordmod recovery via fastboot and then flash the rom after performing a super-wipe and every single time I would get a boot loop, no matter which rom I used, it would boot up and get to the setup screen and boot loop constant boot loop, every single rom I tried, I have not experienced this before when flashing roms, I then looked at a few threads of the roms I tried to flash and one recommended that I extract the boot.img from the zip and flash it via fastboot, some people say that you are required to do that with hboot 1.5 but in the past when I used my old evo 3d I never had to do that and it was hboot 1.5 s-on, please if someone has an answer I would gladly appreciate it, thanks in advance
Click to expand...
Click to collapse
the problem is just that.....youre s-on..you either must do the wire trick...or unknownforces downgrade method to obtain s-off and then flashing will be easier bc of permissions needed to write to the boot partition...
wloftus said:
the problem is just that.....youre s-on..you either must do the wire trick...or unknownforces downgrade method to obtain s-off and then flashing will be easier bc of permissions needed to write to the boot partition...
Click to expand...
Click to collapse
That may be true but there are a lot of users on this forum who are s-on and still flash plenty of roms, most roms do not require you to be s-off and it's not a normal boot loop, the phone starts up and then gets to the setup screen and that's when it reboots, most boot loops occur at the boot animation, so why is this happening now when my old when which was hboot 1.5 s-on worked fine when flashing roms, someone please help
UndefinedUser said:
That may be true but there are a lot of users on this forum who are s-on and still flash plenty of roms, most roms do not require you to be s-off and it's not a normal boot loop, the phone starts up and then gets to the setup screen and that's when it reboots, most boot loops occur at the boot animation, so why is this happening now when my old when which was hboot 1.5 s-on worked fine when flashing roms, someone please help
Click to expand...
Click to collapse
youre right they do flash...they use an app called flash gui...unless you want to manually go and flash the boot image through fastboot
wloftus said:
youre right they do flash...they use an app called flash gui...unless you want to manually go and flash the boot image through fastboot
Click to expand...
Click to collapse
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
UndefinedUser said:
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
Click to expand...
Click to collapse
well then...maybe you should also try scanning the posts better... if youre upset that you have 2.17 and think thats the issue...do a downgrade...oh wait..you already knew that now if you had 2.17 before and had no problems maybe its not the phone...oh btw...my phone is a replacement from asurion as well...i had no issues doing what i needed.. now maybe...JUST maybe someone might know a bit more than you and you should try not to argue with them
UndefinedUser said:
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
Click to expand...
Click to collapse
I didn't really believe that all evo 3d's act differently until I got my replacement. Now I know that their not all the same, even when they have the same hardware version. I'm sure you can see that too. You just have to figure out what works for that phone. I think a sure fire way to get a good install when you have s-on is to use fastboot to boot to recovery. Have you tried that yet? It doesn't sound like you've got a normal bootloop and I haven't encountered your issue before but fastbooting to recovery is worth a try. I'm sure you've heard this a lot but I'm gonna suggest it anyway, get s-off, you won't regret it.
Also, does the phone reboot like that after you run an ruu?
wloftus said:
well then...maybe you should also try scanning the posts better... if youre upset that you have 2.17 and think thats the issue...do a downgrade...oh wait..you already knew that now if you had 2.17 before and had no problems maybe its not the phone...oh btw...my phone is a replacement from asurion as well...i had no issues doing what i needed.. now maybe...JUST maybe someone might know a bit more than you and you should try not to argue with them
Click to expand...
Click to collapse
I was not trying to argue, I was trying to get my point across, I know all about flashing on hboot 1.5 with s-on, like I said I owned a device that was not downgraded, all I am asking is for a simple answer to original problem, what is different about this device? if anyone could help I would appreciate it
UndefinedUser said:
I was not trying to argue, I was trying to get my point across, I know all about flashing on hboot 1.5 with s-on, like I said I owned a device that was not downgraded, all I am asking is for a simple answer to original problem, what is different about this device? if anyone could help I would appreciate it
Click to expand...
Click to collapse
What wikdNoob said. Some phones do fine flashing ICS ROMs with S-on, but from my reading of the forums, many phones bootloop when flashing ICS ROMs with S-on. Since you are 1.5 S-on, you should do the wire trick to get S-off.
I've read so many times how people use the same procedures to flash the same ROM with the same radios, hboot, etc where one gets bootloops and the other does not. Each phone is different.
coal686 said:
What wikdNoob said. Some phones do fine flashing ICS ROMs with S-on, but from my reading of the forums, many phones bootloop when flashing ICS ROMs with S-on. Since you are 1.5 S-on, you should do the wire trick to get S-off.
I've read so many times how people use the same procedures to flash the same ROM with the same radios, hboot, etc where one gets bootloops and the other does not. Each phone is different.
Click to expand...
Click to collapse
I just decided to do the wire trick and now i'm s-off, I love being s-off, I feel so free now
UndefinedUser said:
I just decided to do the wire trick and now i'm s-off, I love being s-off, I feel so free now
Click to expand...
Click to collapse
see how much easier that was now...?
wloftus said:
see how much easier that was now...?
Click to expand...
Click to collapse
yes I should not have argued with your logic, thanks for the help
UndefinedUser said:
I know all of that, you are clearly not understanding me, I owned an evo 3d that was rooted and was hboot 1.5 s-on, I flashed roms for 4-5 months, I am not a noob, my replacement evo 3d that I got through sprint and unlocked the boot loader, I am flashing roms exactly the same way and I am getting boot loops at the setup screen for every rom, maybe next time you will read my entire post and not just skim through it
Click to expand...
Click to collapse
Its A Problem With Certain Phones Because I Have A Replacement Right Now And I Can Flash ICS Roms With Ease But On My Purchased Phone I Would Get Bootloops.
NexusS4gFreak said:
Its A Problem With Certain Phones Because I Have A Replacement Right Now And I Can Flash ICS Roms With Ease But On My Purchased Phone I Would Get Bootloops.
Click to expand...
Click to collapse
I am now s-off, I feel so free, no more boot loops ever, I am so happy that I can flash roms with ease and in my own custom recovery, I don't ever have to touch fastboot again!
UndefinedUser said:
I am now s-off, I feel so free, no more boot loops ever, I am so happy that I can flash roms with ease and in my own custom recovery, I don't ever have to touch fastboot again!
Click to expand...
Click to collapse
Lol Congrats, I Was Thinking About S-OFF But With My Replacement I Dont Need To!
UndefinedUser said:
I am now s-off, I feel so free, no more boot loops ever, I am so happy that I can flash roms with ease and in my own custom recovery, I don't ever have to touch fastboot again!
Click to expand...
Click to collapse
Now that you're s-off you can change your boot splash screen, a lot of choices in the the themes and apps section. You can check mine out from the link in my Sig.
NexusS4gFreak said:
Lol Congrats, I Was Thinking About S-OFF But With My Replacement I Dont Need To!
Click to expand...
Click to collapse
you really should go s-off, I thought the wire trick method would be difficult it was literally the easiest thing I have ever done, I don't know if you are familiar with JTAG xboxes, I used to jtag a **** load xbox's back in the day, in high school, so all this **** is easy, no soldering involved with this ****
Just curious if anyone is currently working on this. Haven't really seen any one mention it. I know these things ate kept hush-hush but a simple yes/no would be good for me.
Sent from my HTC6435LVW using xda app-developers app
no I dont think so. Pretty sure everyone moved on to other devices already.
someone claimed they had it figured out, but of course they wouldn't prove it, and said they were going to do something with another device, before releasing the exploit. I for one thought the entire thing was made up, but all these people got all their hopes up and its probably best to not talk about it, as you might hurt someone's feelings after they were all duped.
rajuabju said:
no I dont think so. Pretty sure everyone moved on to other devices already.
Click to expand...
Click to collapse
I was close to trading for a Note 2 earlier today. But decided to hold out another week. I like this phone too much to just give up.
Not really a huge deal is it?
We have kernel to write to system while booted. The radio is unlocked for other carriers AFAIK. Need a computer to flash kernels but besides that...
rajuabju said:
no I dont think so. Pretty sure everyone moved on to other devices already.
Click to expand...
Click to collapse
I bet it is still in the works. And... moved on to WHAT other devices? DNA is the newest.
The nexus and note crowds are different folks with different desires.
There are people working on it, however no HTC phones without an external sdcard currently have s off...as existing methods require it
I'm not holding my breath waiting for it, since I don't need it for anything personally...but would be nice to have it
nitsuj17 said:
There are people working on it, however no HTC phones without an external sdcard currently have s off...as existing methods require it
I'm not holding my breath waiting for it, since I don't need it for anything personally...but would be nice to have it
Click to expand...
Click to collapse
Evo 4g LTE has archived SOFF, I don't know if it has SD card?? I can be wrong
Sent from my Galaxy Nexus using xda premium
---------- Post added at 09:27 AM ---------- Previous post was at 09:24 AM ----------
Never mind evo 4g LTE does have an SD card slot
Sent from my Galaxy Nexus using xda premium
---------- Post added at 09:27 AM ---------- Previous post was at 09:27 AM ----------
Never mind evo 4g LTE does have an SD card slot
Sent from my Galaxy Nexus using xda premium
sorry, was being sarcastic and forgot the /sarcasm lol
NOsquid said:
Not really a huge deal is it?
We have kernel to write to system while booted. The radio is unlocked for other carriers AFAIK. Need a computer to flash kernels but besides that...
Click to expand...
Click to collapse
Some of us actually like running AOSP ROMs.
TheBiles said:
Some of us actually like running AOSP ROMs.
Click to expand...
Click to collapse
I'm confused. I thought we didn't need s-off for aosp?
fchowd0696 said:
I'm confused. I thought we didn't need s-off for aosp?
Click to expand...
Click to collapse
you dont
nitsuj17 said:
you dont
Click to expand...
Click to collapse
Can you explain why? Please???
bossei said:
Can you explain why? Please???
Click to expand...
Click to collapse
Because you don't need s-off to flash kernels. It just makes it easier.
Sent from my HTC6435LVW using Tapatalk 2
DbZ Gokuu said:
Because you don't need s-off to flash kernels. It just makes it easier.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
But can't we flash Kernels with our phone without being on AOSP? That's the part I'm missing. Or because we have Sense we are restricted somehow unless we take the whole verizon/sense thing out of the equation?
DbZ Gokuu said:
Because you don't need s-off to flash kernels. It just makes it easier.
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
What?.......does this have to do with aosp? These are sort of unrelated issues.
Sent from my HTC6435LVW using xda premium
---------- Post added at 01:34 PM ---------- Previous post was at 01:33 PM ----------
bossei said:
But can't we flash Kernels with our phone without being on AOSP?
Click to expand...
Click to collapse
Yes, we can.
Sent from my HTC6435LVW using xda premium
We can flash kernels and roms because of the unlocked bootloader.
We can make changes to the system while booted in android because of the writeable kernel by dsb.
As far as s-off, I'm not sure what we can't do right now since we have the bootloader unlocked and a kernel that allows writing to the system while booted.
You don't need AOSP, AOKP, CM to flash a kernel. As far as making these roms work on our phones, there's something with the RIL that I beleive has to be worked on to get them going but don't quote me on that.
I know this is a bit off topic, but was kind of brought up..
For those wondering why it's hard to get aosp on the DNA, HTC Sense phone, take a look through the thread posted below. It's from the Rezound forums, and has been in the works since July or so. They have made great progress, but it can't happen over night.
Sorry for going off topic a bit.
http://forum.xda-developers.com/showthread.php?t=1804289
Sent from my HTC6435LVW using xda premium
I did a litle searching and found the answer (I think)
*what exactly IS s-off?
the simple answer is "security-off" on the normal checks that the phone does before it allows you to change different partitions,or revert to an older software/firmware combination.
more specifically,what the s-off procedure gives the device is a "radio s-off" by changing a setting in the radio NVRAM called the "secure flag" to "off". this method of s-off is ideal,as it is below the radio level of the phone,and will remain no matter what other changes are made. radios,hboots,etc. can all be changed and the radio secure flag will remain off.
ruus can be run,OTAs accepted,etc. and the s-off will stay,until it is purposely changed.
other devices use a "patched" hboot,wich is basically an hboot,that does not listen to the radio secure flag. the radio secure flag is still s-on,the patched hboot simply ignores it. these hboots can be further patched to prevent themselves from being overwritten,so the s-off is not lost during an ruu or OTA. with older phones,this works fine until a new hboot is required for an OS upgrade.
with the new devices,this type of s-off is not possible(or we would have had it a long time ago) due to the complex checks that the phone makes when it boots. if the s-on radio checks hboot and finds it to be unsigned,the phone is put into a "do not boot" mode that is only reversible by htc,becoming effectively a hard brick.
"why not patch the radio just like we patched the hboot??" partially because its easier said than done,partially because other checks are going on,and if the radio is found to be unsigned,again, "no boot mode". basically there are just too many checks going on to patch them all. since it all starts with the radio secure flag,its the only practical way to gain complete access to the phone.
*isnt my unlocked via htcdev bootloader the same as s-off? i thot thats what unlocked means?
sorry,no. its not the same. the key difference is that htcdev unlock only allows access to boot/system/recovery. the phone is still s-on,and still doing plently of checks that prevent you from:
-changing firmware
-changing your splash screen
-going backwards in software/firmware build version numbers.
it also does not allow you to write the boot image from the recovery partition,as we all know that have flashed roms on s-on phones. since the kernel lives in the boot image,the kernel can only be changed by:
1)flashing it seperately via hboot or fastboot
or
2)launching your recovery from fastboot.
a permanently installed recovery cannot install kernels with htcdev unlock
*so what does s-off do for me??
-first and foremost,it makes rom flashing and nandroid restoring ALOT easier by allowing the permanently installed recovery to write the boot image,making the PC no longer a required part of the flash/restore equAtion you can now download a rom right to your phone,move it to the root of your sd with a file manager,and boot to a recovery and flash it,without a PC anywhere in sight.(note that i do not download roms to my phone,i prefer to download to pc,then transfer. a personal preference)
-second,it alows changing of firmware,so you can run a "patched" or engnieering hboot,the advantages of will be discussed later
-it lets you upgrade your radio and related firmware wihtout running a huge,signed,full RUU
-it lets you go backwards in build numbers. this is handy becasue you can,without fear,flash the latest leak,and if its bad,revert back to older software/firmware without issue.
-you can change your splash screen,wich is not important functionally,but fun. anything from carman electra, to your cat,to your grandkids can replace the htc splash screen.
-last and not least,the ability to add a patched or engineering hboot,combined with the ability to run any RUU that exists,gives a much greater opportunity to revive a "soft bricked" phone.
-one last big plus is that the procedure will change your unlocked or relocked status back to locked wich,visiually,is good for warranty purpose.
Click to expand...
Click to collapse
http://androidforums.com/cdma-evo-3...fo-faq-root-s-off-cdma-evo-3d-all-hboots.html
So basically, with our phone unlocked we can flash custom recovery, get root and flash a kernel or rom. With a writeable kernel we can make changes to the system partition whole booted in android. With s-on there are certain things we can't do like flash radios or revert firmware.
Hello! I used to be very engrossed in the modding community for the Rezound a few months ago. But because of a forced phone switch I haven't been in the loop for a while.
Well now I'm back on a Rezound and I was wanting to know a few things.
Fair warning. When I left we had just achieved S-off and were delving into the new things we could do from then on, so if my questions seem dated; I'm sorry.
Also, my phone atm is on stock ICS, I wanted to get a feel for everything again before I went and rooted it.
*Which are the most prominent ROMs right now? (Preferrably sense with beats)
*Do any of those ROMs have a working DSP Manager with Virtual room or ability to get it working on it?
*What is this whole GSM thing I'm seeing on some ROMs lists? Are we able to use the rezound easily overseas or on different networks now or something?
I have looked through some of the forums but haven't been able to find any concrete information, so I figured I would just post my own thread.
Thank you for your time and any replies!
The most prominent roms are any of the ones on the first two pages of the development sections. I know that neo includes a Beats mod in his AOSP roms which works as well as any stock beats you'll find in a sense rom. The DSP manager included with cyanogenmod is 100% functional as far as I can tell. And yes, we can use the rezound on AT&T (siul does MIUI and uses his rezound on AT&T) but I'm not sure as to what frequencies we have access to and if its HSPA or not.
Since you've been gone we received a global ruu that gives the rezound service over seas. The most prominent roms sense based are viperrez, newts one xxx, ecliptic rez and so on.. Those are just the ones I've tried. I'm running newts hybrid rom now and it's doing well though it's not as optimized as his one xxx rom
Sent from my ADR6425LVW using xda app-developers app
Alright, thanks for the info! And what are the best recoveries to use, now?
Volkaru said:
Alright, thanks for the info! And what are the best recoveries to use, now?
Click to expand...
Click to collapse
all the recoverys are about the same now. its up to you on what you want it to do. TWRP and CWMT are both great touch based recoveries. if you want more of the menu scroll classic way. go with AmonRA 3.15
Volkaru said:
Alright, thanks for the info! And what are the best recoveries to use, now?
Click to expand...
Click to collapse
TWRP, unbeatable! Not sure if it's available for your phone though..
Vangelis13 said:
TWRP, unbeatable! Not sure if it's available for your phone though..
Click to expand...
Click to collapse
It is. Installed it.
I think I'm all set now except for one thing. Is it normal now after you unlock and install a recovery for it to say TAMPERED? Last I saw that was when people were installing the leaked ICS RUUs.
The order of which I rooted my phone in case I did anything wrong was. Unlock bootloader with HTCDev, Phone restarted, let it load up then went into the menu and enabled Debugging again, shut it off. Reloaded fastboot. Then installed TWRP 2.3.3.0 using the All-in-one tool. After that my bootloader said TAMPERED.
Thanks again for all the help.
Volkaru said:
It is. Installed it.
I think I'm all set now except for one thing. Is it normal now after you unlock and install a recovery for it to say TAMPERED? Last I saw that was when people were installing the leaked ICS RUUs.
The order of which I rooted my phone in case I did anything wrong was. Unlock bootloader with HTCDev, Phone restarted, let it load up then went into the menu and enabled Debugging again, shut it off. Reloaded fastboot. Then installed TWRP 2.3.3.0 using the All-in-one tool. After that my bootloader said TAMPERED.
Thanks again for all the help.
Click to expand...
Click to collapse
Tampered is ok. It just means there's a custom recovery installed. Every now and then TWRP has some issues flashing certain files just so you know, most likely you'll never see it, but just in case it keeps you from chasing your tail I mentioned it.
We're s off now, that's the big change for when you want to do some wild modification. But thanks to snuzzo there's no harm done in being s on it's easier now than it used to be.
Anything else, send me a PM if you'd like and we can catch up on gtalk.
So is your hboot 2.25 and your radio basebands end in .421r and .424r?
CharliesTheMan said:
Tampered is ok. It just means there's a custom recovery installed. Every now and then TWRP has some issues flashing certain files just so you know, most likely you'll never see it, but just in case it keeps you from chasing your tail I mentioned it.
We're s off now, that's the big change for when you want to do some wild modification. But thanks to snuzzo there's no harm done in being s on it's easier now than it used to be.
Anything else, send me a PM if you'd like and we can catch up on gtalk.
So is your hboot 2.25 and your radio basebands end in .421r and .424r?
Click to expand...
Click to collapse
Alright, thanks for all the info. Will PM you later.
Everything was fully updated as far as stock goes.