Develop Bugs

Rooting with Visonary 14 killed me phone

I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!

People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.

You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App

@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.

ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery

ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery

Anyone? Bueller?

cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.

This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.

How do I get S-Off

I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.

Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
Are you following the guide in the wiki?
Sent from my T-Mobile G2 using XDA App

Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
First, yes you need S-Off to do a nandriod back up.
Second, you do not have permroot if you do not have S-Off. To get S-off there are several ways but I recommend using Rage+gfree found Here: in sub section "Rooting the Vision (G2/DZ) and DHD" This by far is the safest way to root.
But to let you make an informed decision there is also Visionary, now people in properly using this method, has produced a lot of soft bricks, I my self rooted this way, but again I still recommend using Rage+Gfree. But if you wish to still give Visionary a shot, Heres a link on how to properly use Visionary, make sure you follow everything to the "T". Read everything I have written in the post, do everything I have written in the post, then follow the videos exactly. But just to be clear, I am still recommending using the Rage+Gfree method. Happy Rooting.

ok joemm I tried the rage directions that you told me and I am not sure if it worked is there a way of knowing if it worked or not
Edit: nvm I can now get into CWM area which I could not get into before thanxs for the help and info.

What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).

KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
Click to expand...
Click to collapse
LOL..........how does he flash a custom CWM recovery with out having a rooted phone? Remember he is using ClockWorkMod to do a back up?

KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
Click to expand...
Click to collapse
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z

steviewevie said:
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
True you can't flash a custom recovery and have it stick after a reboot but you can package it into an update.zip and flash it when you get into recovery. Aside from that you're phone performs the same. That's how we did everything on the MT slide before some one found a method to gain s-off. Of course there were no custom MTD partitions and we couldn't change the splash but that falls into the 1% of things the average 'rooter' will not attempt. The only reason we needed the ENG hboot was so that adb would catch our phone in recovery every time without running a loop.bat and praying to god. As far as NAND write protection, normally when a dev manages to break s-on they also break the write protection. At least that's what I've seen in phones with s-off. Are there any not like that?
Hopefully I didn't come off as an ass earlier, didn't mean it. I got 3 hours of sleep and I'm pulling a 13 hour day with a foot of fresh snow outside

I think you might be drawing too much comparison with earlier phones. The DZ and DHD have much stronger security than earlier phones. People familiar with experience of older HTC Android phones have often made incorrect assumptions about how things work on the DZ, some things are quite different (and typically much more complicated to unlock)
Sent from my HTC Desire Z

steviewevie said:
People familiar with experience of older HTC Android phones have often made incorrect assumptions...
Click to expand...
Click to collapse
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...

schaggo said:
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
Click to expand...
Click to collapse
Its become more difficult because device manufacturers have made it more difficult. The "official" means to root the Vision is posted on the Vision wiki page here at XDA.
Sent from my T-Mobile G2 using XDA App

Thanks for the answer. I got the thing cracked in the meantime. The device feels so much smoother without Sense... and Gingerbread is good for one's soul

Cyanogen Mod Verizon HTC M7

So after absolutely no help from Cyanogen mod and their forum I thought I'd come here.
I have an HTC One M7 from Verizon with 4.4.2 and I'm just getting really "bored" of the Sense 5 feel. I used to like it at first with my DNA, and thought I'd like the M7 more, but I don't...it's just "dull" and I feel like it's meant for the average user.
Enough about that, here's what I'm trying to do..I want to put a new "skin" on my phone, but have never rooted or done anything like this to a phone before. After doing some research into the M7 for Verizon, it seems that Verizon puts a lot of blocks on their phones to prevent this.
Does anyone have a detailed guide on how to do this safely? Like I said, I'm new to this, and need a thorough explanation since a lot of the terminology I don't understand 100%.
I've been looped around at Cyanogen mod about S-Off and Bootloader, been told different things about what each one does and people just made it very confusing.

Root can be found in the original development section. The thread is called weaksauce. Root is essentially a binary file that allows you access to the "root" files of your phone and its system.
S-off is a boot loader or hboot (similar to the bios on a pc) that has its security unlocked...allowing you to truly customize your phone. In order to s-off after gaining root. See the link in the weaksauce thread for fire water.
Once done you will flash a new recovery (controls the makings of your system). Then you will finally flash a new Rom CM11 if that's what you want.
I suggest doing a bit of reading in this forum before proceeding. Good luck.
Sent from my Lunar Ecliptic One.

A point where my HTC is perfect

I have an HTC One M8 from T-Mobile
S-ON and UNLOCKED
I was just wondering how to get to a point where my phone wont brick on me, soft brick or hard brick.
I have the Insertcoin mod, 3.0.6 and it keeps prompting for an update on 3.0.7. When I click download and install it, it says "installation aborted" and then it exits me out.
I tried Googling the issue, but someone said that they did it manually and it actually soft bricked their phone and they got stuck in a bootloop.
I don't want that to happen to me because I've been dealing with my friend's HTC One M7 for the last few weeks where he was doing a normal HTC Update to 4.4 and his phone got soft bricked, stuck in bootloop. Tried factory reset, flashing RUU, wiping dalvic cache, and normal cache. Put it in fastboot and tried flashing it, nothing worked.
I'm thinking the reason is because it's S-ON and LOCKED. It got to a point where I just don't know what to do with it, so I kind of gave up.
But what's a good way of getting out of soft brick if you do get stuck in it?
I figured it should be easier than this, but this is really difficult.
-Thanks

Those 2 cases are completely different from each other (OTA install on a stock M7 versus updating a custom ROM on a M8); so I would not lump the 2 together.
IMO, best way to get out of a brick is to practice some good sense preparation:
1) Achieve S-off before you try to flash the new ROM. This will give you a lot more recovery options if things go south.
2) Make sure adb and fastboot is working properly with your device
3) Make sure TWRP is up to date, and check if the latest version has any known issues of bugs
4) Make a nandroid, and keep it on the internal memory. Copy it to your computer to be safe. This is really important; and one of the easiest and most reliable way to get back up and running if you run into trouble (or simply don't like the new ROM and want to revert). Yet, a lot of folks flash ROM without making a nandroid backup. I have no idea why.
5) Have a known good ROM handy (such as InsertCoin 3.0.7 which you say has been working "perfect" for you) on your PC or possibly even on the phone's internal memory
"How to get out of a bootloop" depends on what is causing it, what errors your are getting, etc.. There isn't a silver bullet solution. I would normally say RUU is that silver bullet; but you have found that is not the case. In general, you were on the right track with your friends M7 (which I won't comment on, since I never owned that phone). But a few guidelines are given below. Its listed sequentially for the most part, meaning if a particular solution fails, proceed to the next one.
1) A "dirty flash" (wipe only Dalvik and cache, keep user data) is often possible when updating within a particular custom ROM. But check the InsertCoin thread to see what the dev recommends, or how this went for other user on 3.0.8. If a bootloop occurs, or any other random bugs, do a factory reset in TWRP (wipe user data, Dalvik and cache) and flash again.
2) Try to download the ROM again, if you're bootlooping maybe the download was corrupt. Check the MD5, if available
3) Boot into TWRP and restore your nandroid
4) Try to flash a known good ROM, or another ROM.
5) Use fastboot to wipe cache and flash recovery again. Try again to flash a known good ROM or nandroid
6) All else fails, run the RUU (requires you to relock bootloader if S-on)
7) Whatever you do, do not do a factory reset in bootloader (only within the OS Settings itself, or TWRP). There is a known bug where factory reset in bootloader on a modded phone will corrupt the phone's internal memory (including loss of nandroid and ROM zips on the memory).

Thanks!
I'll take a look at all of it.
And a nandroid backup is when you use your custom recovery to make a backup right? If so I already did that for my M8
I have S-ON for my M8, how do I get it off? And is it worth getting it off? I haven't had any problems with access or ROMS yet with it being on.
Thanks
Sent from my HTC One_M8 using XDA Free mobile app

technocrat7 said:
And a nandroid backup is when you use your custom recovery to make a backup right? If so I already did that for my M8
Click to expand...
Click to collapse
Yes, nandroid is just a generic term for TWRP or CWM backup. You'd be amazed at home many folks flash mods to their phones without making one. You're already a cut above those folks!
technocrat7 said:
I have S-ON for my M8, how do I get it off? And is it worth getting it off? I haven't had any problems with access or ROMS yet with it being on.
Click to expand...
Click to collapse
Firewater S-off: http://forum.xda-developers.com/showthread.php?t=2708464
I already told you why S-off is important in my previous response; so I don't know why you are asking "is it worth getting?"
S-off can be important for recovery as it lets you run previous ("downgrade") RUUs (perhaps not as relevant this early, as most M8 versions only have one RUU version, or none at all) and RUUs for other carrier versions (may need to change CID also).
S-off also eliminates the requirement to relock the bootloader to run RUUs. So this saves you the extra steps of relocking to run the RUU, then unlocking again. Plus, you save yourself from the position of being relocked and in a bootloop (if RUU fails), which is a bit complicated and scary situation.
Further (aside from recovery options), S-off also permits you to flash different radios, mod hboot, update firmware packages, and other things not normally permitted with S-on.
The only downside to S-off, is that it bypasses all security and safety checks. For the most part while modding, this is a good thing. But you just have to be extra careful you only flash mods meant for the M8. Since device check is bypassed with S-off, its possible to flash a mod meant for another device and damage your M8 (such as different partitioning, damage partition table, etc.). But as long as you only flash things in the M8 forum, you will be safe.
So S-off has lots of upsides, very few downsides. Of course, its up to you whether to do it or not. But to me, the choice is pretty clear.

Thanks! I'll work on getting S-OFF on my device.
Also if you do screw it up and damage your M8, can you run the nandroid backup and get to where you were or no?
Sent from my HTC One_M8 using XDA Free mobile app

technocrat7 said:
Thanks! I'll work on getting S-OFF on my device.
Also if you do screw it up and damage your M8, can you run the nandroid backup and get to where you were or no?
Click to expand...
Click to collapse
Are you talking specifically about the firewater s-off process? If so, then no, a nandroid will not reverse this. But there isn't much to "screw up". Its a very easy process, and I wouldn't worry too much about it.

Alright thanks! I'll do that and then report back later!
Sent from my HTC One_M8

I ran firewater, it says:
Whelp, this sucks, firewater cannot work on your device. No amount of refreshing, retrying, or ruuing will fix this...
Sorry it didn't work out

Okay so I found out the real issue, and for those who saw my other post, the reason it said it could not be completed is because after I launch "adb shell"
I type "su"
And nothing happens. It's supposed to prompt me for my SuperSU permission but it doesn't.
SuperSU is not listed as a device manager under my security too. And in the shell it shows a # and I've granted other applications permission before so I know I'm rooted. Any help?
I'm running InsertCoin if it matters.

Have u tried the new other s-off methods? They do cost around 20 bucks I thinm
Sent from my HTC One_M8

technocrat7 said:
Okay so I found out the real issue, and for those who saw my other post, the reason it said it could not be completed is because after I launch "adb shell"
I type "su"
And nothing happens. It's supposed to prompt me for my SuperSU permission but it doesn't.
SuperSU is not listed as a device manager under my security too. And in the shell it shows a # and I've granted other applications permission before so I know I'm rooted. Any help?
I'm running InsertCoin if it matters.
Click to expand...
Click to collapse
If it doesn't prompt you for su access and doesn't seem to do anything when running firewater it's probably because the rom is not "stock" enough. Running Maximus or other near stock roms is more likely to succeed. But anyway if you previously got the whelp message in firewater I suppose you're like many of us out of luck using that since it seems HTC has closed the exploit that firewater used on some phones.
So as MotoTurbo said, you'll probably need to use Sunshine (http://theroot.ninja) rather than Firewater. It's made by the same devs, but works on all M8's (even the ones that got whelped in Firewater). It does cost $25 but it was really simple to use and worked perfect on my phone. The newest version even seem to root your phone if it's not rooted already and then s-off's your phone after it has made sure it will work on your phone and paying using Paypal or creditcard from within the app...
The close to stock requirement also seem valid for Sunshine, but you can always try from your current rom since it won't allow you to pay until it's sure it can s-off your phone.

Ah I see.
Thank you. It sucks I'm out of luck but I think it's worth the $20. I am pretty sure I plan on keeping the phone around long enough.
One more question. The newest update for InsertCoin, or even some xposed modules are falling to work. It says "installation aborted" after not being able to extract to some directory or find it or something.
But I was installing updates fine a week ago. It's just the newest one giving me trouble. Someone said I have to go to the website manually and just put it in my SD card and zip install it through recovery.
I don't want to screw things up because I heard someone got stuck in a bootloop by doing this.

technocrat7 said:
I ran firewater, it says:
Whelp, this sucks, firewater cannot work on your device. No amount of refreshing, retrying, or ruuing will fix this...
Sorry it didn't work out
Click to expand...
Click to collapse
Later hboots don't work with firewater. What hboot version is your device on?
---------- Post added at 09:37 AM ---------- Previous post was at 09:30 AM ----------
technocrat7 said:
But I was installing updates fine a week ago. It's just the newest one giving me trouble. Someone said I have to go to the website manually and just put it in my SD card and zip install it through recovery.
I don't want to screw things up because I heard someone got stuck in a bootloop by doing this.
Click to expand...
Click to collapse
There is no reason to believe the new InsertCoin has any higher change to cause a bootloop than any other update or mod. I just manually flashed InsertCoin 3.0.8 and things went just fine. Side note: its funny I haven't been keeping up with the InsertCoin versions, and this thread made me realized how out of date I was . . . I was still on 3.0.4!
I'd relax on the "fear of a bootloop" thing. Bootloops happen, its just a fact of flashing mods. But the solution to recover is often an easy one; its just a matter of knowing or figuring out the exact trick to recover (different based on various causes). S-off is nice to have, but honestly its not an absolute necessity, as long as you've followed the other suggestions I gave previously, you are well equipped to recover from a bootloop, even in the unlikely event that one happens. S-off isn't necessary to flash ROMs, many folks do so S-on. S-off just gives you more options if you run into problems.

Ah I see.
And well, downloading 3.0.7 is aborting the installation so I guess I'll just do it manually or something haha

Also I forgot to mention..
Why doesn't SuperSU show up as a device administrator under security?
How can I fix this? Or is it not supposed to?
When doing firewater, I do "su" and there is no authentication, nothing. It's like SU doesn't exist
-----
EDIT:
also, whenever I download something from the marketplace or something it says "installation aborted" is there a reason for this?

re-exploring rooting, flashing, and so on

Just wanted to make a post about re-exploring the whole rooting and custom ROM nature of Android.
I used to be fairly active when I was using my Desire HD back in the day (which remains one of my all time favorite devices). I was making splash screens, boot animations, discovering my own tweaks and stuff, which are probably around here in the Desire HD section somewhere, inclusing a bootloader, splash flash, radio flasher and all sorts.
And then it seemed to me that most of the reasons people were rooting for, were starting to becoming irrelevant, as more of those features were being built in etc. For my phones after the HD, I used a custom recovery at most, but never bothered to root, or install a different rom. Not to mention one of the more important banking apps I used refuses to work with root. Even now, I find my self exploring, tweaking, and then removing root. It seems to leave things as I set them whilst letting me run the phone normally.
I've been on the HTC10 for a few weeks now and a few issues with it have forced me to consider alternative ROMS as a way of fixing these or getting more out of the phone than is already possible. I unlocked the bootloader fine, but I dont think I will bother with S-OFF.
Last time I tried to install a custom rom to a phone with S-ON, you had to install the ROM first, and then go back into the bootloader and flash the roms boot.img seperatley. Apparently that step isnt necessary anymore, it takes care of it all during the installation process.
I'm glad I started to get into it all again, and I will be keeping an eye on new or interesting roms and seeing what becomes of them. Open to suggestions too

S-off isn't as much of a necessity as it used to be with some of the older HTC phones. It still has its usefulness, though. As far as ROM flashing goes, you can flash a ROM on the 10 without having to flash the boot.img separately, as you stated.
Sent from my HTC 10

The process is how I remember it on my old Desire HD, which I dug out recently. For whatever reason it cannot be changed to ENG-HBOOT or S-OFF (I think the bootloader is too recent or it was when HTC decided to start locking bootloaders, or something along those lines) it is bootloader unlocked, but S-ON RL (not sure what the RL means ... re-locked?) I updated the recovery to 4EXT since apparently no one seems to like CWM/Rom Manager these days, and I reflashed a more stable rom to it, which needed the boot.img flashed in fastboot.
S-OFF and ENG-HBOOT was fun for things like custom splash screens and so on, buts its nice that it isnt necessary for ROM flashing.

I was debating whether to bother with S-OFF, but in the end I'm glad I did if only to have the latest radio firmware. A bit terrifying to be a big step closer to bricking, though.
Everyone seems to be using TWRP recovery now, by the way.
Also, might want to give LeeDroid ROM a shot. Have been very impressed with how many kinks he's worked out.
The only finance app I know of that won't run on a rooted device is Android Pay. There's a workaround for this, though: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382 Can't imagine not having root!

pixelvisions said:
I was debating whether to bother with S-OFF, but in the end I'm glad I did if only to have the latest radio firmware. A bit terrifying to be a big step closer to bricking, though.
Everyone seems to be using TWRP recovery now, by the way.
Also, might want to give LeeDroid ROM a shot. Have been very impressed with how many kinks he's worked out.
The only finance app I know of that won't run on a rooted device is Android Pay. There's a workaround for this, though: http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382 Can't imagine not having root!
Click to expand...
Click to collapse
Yeah I know it's opens up a lot of avenues for things, the app is Barclays, I'm in the UK so it may differ from what you have if you're elsewhere. They did ALOT of work to make it pretty unusable if you're rooted, and it won't even load at all with xposed and root cloak installed. A few do work, such as Nationwide.
I am on Maximus HD (LlabTooFeRs ROM), which is easier because OTA updates etc. I used to use LeeDroid a lot back on my Desire HD. I'll try a variety of roms when I can find the time.
HTC10 is pretty stable for now though. My main problem (just for fun really) is figuring out how to radio s-off and eng s-off my old desire HD. The cid is ORANG001, but the phone itself accepts any sim as it's been unlocked. Beyond that, I cannot downgrade the bootloader, the phone is rooted, bootloader unlocked, the sd card for it is a gold card, although I may try another. It just seems to not want to do anything.

silegeek said:
Yeah I know it's opens up a lot of avenues for things, the app is Barclays, I'm in the UK so it may differ from what you have if you're elsewhere.
Click to expand...
Click to collapse
Ah, I see -- a lot of frustration with that app on these forums!

pixelvisions said:
Ah, I see -- a lot of frustration with that app on these forums!
Click to expand...
Click to collapse
Yeah I noticed that! :laugh:

silegeek said:
Yeah I noticed that! :laugh:
Click to expand...
Click to collapse
Hey there. Just something to try out, if you want a bunch of tweaks build into the ROM, would be Viper10. It's really amazing and comes with OTA updates as well.
S-OFF would be needed in case you'll leave your HTC 10 on a custom ROM instead of reverting to stock, to be able to flash the latest no wipe firmware zips if need occurs as a result of incompatibility with your Custom ROM's base.
Sent from my HTC 10 using XDA Labs