Develop Bugs

[Q] 2.2 OTA update issues

Hi guys,
I have a Desire I bought unlocked on eBay. Though initially thinking it was factory unlocked, and having bought it under that pretense, I now think it's been unlocked by some other means. It doesn't appear to be rooted, having no superuser app but I'm not sure how else it could have been unlocked? If any one can shed some light here, that would be great.
I received the OTA update tonight, and after downloading and resetting it simply wouldn't get past 90% on the install before resetting itself. After about 15 minutes I switched it off and switched it on again, and it booted into my homescreen, with a "loading" alert and a rotating circle, no percentage.
Eventually that stopped, and it looked like everything was ok. I checked the version and it said I was running 2.2. Awesome, so I go about my business and realise I have no 3G or wireless connections. I check the settings and under WiFi it says "error", and I can't enable it. My APN is gone too. I can get that online, but it seems like there's an issue with the radio so I haven't bothered. It doesn't connect to the network anyway. It also resets occasionally, it seems when it has to load SenseUI but I can't confirm this.
What could it be? I'm not sure where the phone came from. It's a Black a8181 model with the Orange case branding, but the OS is unbranded. The locale is English (Singapore/Taiwan/a few others), though I thought the Black model was only in the UK. I'm in Australia, on vodafoneAU.
Is there anything I can do?
Cheers guys, I really hope I haven't (basically) bricked it.

Firstly, removing the SIM lock from the phone has nothing to do with rooting. Usually, you just stick in an "incorrect" SIM, and it will ask for an unlock code which you can buy online.
Given that the OTA update was a patch, it sounds to me like you have a partially patched ROM and this is causing your problems.
However, since it basically boots up and works to a fashion, it isn't bricked and chances are it is fairly easily recovered.
IMHO, you have two options.
1. Install a 2.1 RUU to downgrade your phone.
2. Root the phone using UnreEVOked and load a custom 2.2 ROM.
Both of these should be quite easily so long as your previous attempt to upgrade hasn't already updated HBOOT.
Turn you phone off and then power on again whilst holding down the volume down button - your phone should boot into HBOOT.
Look for the HBOOT version on the second line and post back what it says here.
Regards,
Dave

You've received a branded phone that has been debranded (you should have been told this) - you can't upgrade these without a goldcard. What's happened is part of the upgrade has worked, but other parts failed.
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.

teppic74 said:
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.
Click to expand...
Click to collapse
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave

foxmeister said:
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave
Click to expand...
Click to collapse
That's true, though it does mean going down the custom ROM route, which might not be wanted.

Thanks guys, that's really good info.
I'm not too concerned about running custom ROMs, I've been thinking about doing it for a while, just don't know enough about how to root and flash. There are some good guides here, I'm just a bit nervous about doing it. I also don't know what the best ROM would be. I'm really just after a factory standard Desire with Sense ROM, the most out of the box it could be.
I assume an RUU is like a rollback? In which case, what would I be rolling back to. I have no idea how it was debranded, so I don't know what ROM I'd need to roll back to.
As for the goldcard, what would that do? Is that rolling back, or fixing what I have now? It doesn't crash too often, I can probably baby it through.
Sorry for the questions guys, just want to know my options. I didn't think it was too badly bricked, but you never know. I bricked my XDA Mini II trying to flash a new ROM, so you can see my hesitation :/

An RUU is an official way to flash the phone with HTC's own software. That is how the phone was debranded in the first place, and you can do the same to get it back to normal. It does require a goldcard though, which is a minor software patch on the sdcard.
If you root and install a custom ROM (and update the radio) you'll have a working phone again, and you can make a goldcard in your own time.

If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
foxmeister said:
Look for the HBOOT version on the second line and post back what it says here.
Click to expand...
Click to collapse
Hboot - 0.80.0000

papalazarou said:
If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
Hboot - 0.80.0000
Click to expand...
Click to collapse
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.

teppic74 said:
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.
Click to expand...
Click to collapse
Cool, will the process in the link in your sig do the trick? And the goldcard, will I need to keep it in permanently, or only when updating? Trying to decide if I should use a dedicated card for it, or include it on the card I keep in there.
Thanks for the help, I'll run the RUU tomorrow morning.

I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.

papalazarou said:
I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.
Click to expand...
Click to collapse
Yeah, that's my fault for leaving a testing point in the Mac/Linux version of the utility. It was mentioned in the bugs section, but probably not made clear enough. It's fixed now.

[Q] A few questions before rooting

Hey guys, first time poster here and a bit of a newb to rooting, Android and smart-phones in general.
I've been hanging on these forums the past 3 months researching the rooting process for a Desire and all the relevant stuff that goes along with it. So please go easy on me. I've also read all the 'similar threads' suggested to me at post-time.
I'm almost ready to begin the process but there's a few bits of information that's got me pretty scared before I go ahead. I wasn't able to find much of a concrete answer/s to these questions, from Googling around.
Well without further ado.
What is the difference between GSM & CDMA and do I need to know which my phone is before proceeding?
If I DO need to know, how do I find this out?
My phone is branded (Orange splash-screen at boot) and locked to Orange network (Newly recieved contract phone).
I've heard that I may need a goldcard to proceed with the Unrevoked process due to the branding. Is this correct?
Another guide on the net (can provide link if necessary), mentions upgrading the radio on Orange phones can permanently break the wifi OR permanently simlock your phone.
Will I need to worry about this during the Unrevoked rooting process? And will this be avoidable after installing a custom rom. (If I get that far )
I read somewhere on these forums (I forgot where exactly), something about the newest Orange OTA update causing problems with the rooting process. Is this still the case or has Unrevoked been updated to avoid that now? Also, how can I check if I have that update?
I can provide all the information about my Hboot, radio and kernel versions etc, if you need it (I guess you will), but for some reason, I keep getting a spam warning as this is my first post. I can only assume the version numbers are being interpreted as IPs...
Well sorry for the wall of text, but I greatly appreciate any help I can get regarding these issues. I'm so scared of bricking my Desire and not being able to return it, if bricking does occur.
Yours a worried root newb!

1. We use GSM phones in the UK as we use SIM cards. CDMA phones don't use SIM cards and are locked/released to one network
2. You don't need a gold card to root, no. As there isn't an Orange RUU available to go back to stock for warranty you will need one to flash a non-Orange RUU. Best to make one before starting
3. This was the case a while back but I'd wait for confirmation before changing it
4. No as the radio isn't flashed during a ROM (unless stated in the ROM thread that it does)
5. Shouldn't be an issue, just get the latest version of unrEVOked from their website before starting

Great, that's most of my questions/concerns answered. Although the below answer has brought a new question to the front
EddyOS said:
2. You don't need a gold card to root, no. As there isn't an Orange RUU available to go back to stock for warranty you will need one to flash a non-Orange RUU. Best to make one before starting
Click to expand...
Click to collapse
Unfortunately my knowledge of RUU is almost non-existant, other than that it stands for Rom Upgrade Utility and is used to upgrade the software on my phone? Right?
And forgive me if I'm being dumb here but, if
EddyOS said:
there isn't an Orange RUU available to go back to stock for warranty
Click to expand...
Click to collapse
and yet I
EddyOS said:
will need one to flash a non-Orange RUU
Click to expand...
Click to collapse
then how can I do this? Or am I totally misunderstanding you?
Do I somehow use an application without root permission to perform a procedure similar to hdd ghosting?

Basically, if you wanted to return to stock for any reason you wouldn't be able to go back to the Orange ROM as the RUU doesn't exist so you'd have to go to a generic ROM. To flash any ROM other than the originally on the phone you need a gold card
It's the same for me, if (for some strange reason) I'd want to flash a branded ROM on my Desire I'd need a gold card. Thankfully, I have an unbranded handset so I can get the stock RUU and use it without a gold card

EddyOS said:
Basically, if you wanted to return to stock for any reason you wouldn't be able to go back to the Orange ROM as the RUU doesn't exist so you'd have to go to a generic ROM.
Click to expand...
Click to collapse
So basically if I were to screw it up, which I hopefully won't, I'm buggered as far as getting my phone fixed cos they'll see the Orange rom is no longer installed? Not too fussed about that, as I'm super-careful with my phone.
I guess my next issue would be, after rooting using Unrevoked, I'd need to gain S-OFF right? Which I understand is done via AlphaRev. Only issue there would be related to this
"Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files." If I'm reverting to a stock rom, while gaining S-OFF presumably there's a high chance that'd upgrade my radio - a potentially very bad thing.
THEN I go about choosing a rom to flash. Then Nandroid backup. Then flash the rom, hopefully love it and voila?
Also, what would you suggest as a good rom for someone like me just starting out with a fully rooted phone? I was thinking one of the official builds to lose all the crap, but then the above issue of the radio creeps up again...

I have been flashing ROM's since I got my phone rooted last year and I have never bothered to S-OFF. It's not a requirement.
I have tried a number of ROM's (it becomes a bit addictive!) there is not normally a need to flash a new radio, just leave it be. If you are worried about it and the ROM requires a new radio don't flash it. There are plenty to choose from.
As for recommendations, everyone has their own tastes and likes. That's the beauty of modding. Just flash a few ROM's and see which you like. I have tried most of them, stuck with MIUI for ages, but am now on Cyanogenmod 7 Nightly's.

There is nothing to really worry about. There is a remote chance of bricking your phone for a start, like 0.0000000001% chance. Only way of doing it is disconnecting during say an S-Off.
As for the Orange issue. I had a locked, Orange Desire with 2.2 on it (the first update) and when I rooted and S-Off'd I had no problems. I also have updated my radio to 5.14.05.17 and have no issues at all. To be honest, I found issues to do with signals and Wi-Fi are to do with the ROM you install and the kernel as well which can be frustrating but fun as well.
As for choosing a ROM, choose one, flash it then see what it's like. It's purely down to what you like most about each ROM. I've been through so many ROMs in the past few months but now I am sort of staying with 1 ROM. I will say that when I installed a custom ROM, I had to pay to unlock my sim because it was being gay and Orange wanted £20 of my hard earned cash to unlock it and send it off. So be prepared.

thetasigma3 said:
So basically if I were to screw it up, which I hopefully won't, I'm buggered as far as getting my phone fixed cos they'll see the Orange rom is no longer installed? Not too fussed about that, as I'm super-careful with my phone.
I guess my next issue would be, after rooting using Unrevoked, I'd need to gain S-OFF right? Which I understand is done via AlphaRev. Only issue there would be related to this
"Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files." If I'm reverting to a stock rom, while gaining S-OFF presumably there's a high chance that'd upgrade my radio - a potentially very bad thing.
THEN I go about choosing a rom to flash. Then Nandroid backup. Then flash the rom, hopefully love it and voila?
Also, what would you suggest as a good rom for someone like me just starting out with a fully rooted phone? I was thinking one of the official builds to lose all the crap, but then the above issue of the radio creeps up again...
Click to expand...
Click to collapse
Don't bother about S-OFF at the moment, you don't need it. Just get rooted and then look into custom ROMs for now

Ok I've taken a tiny step further forward. I'm at the point of making a goldcard but one thing concerns me... http://forum.xda-developers.com/showpost.php?p=6710085&postcount=3 According to that it won't work with the 2.2 OTA update from HTC.
I know, I have 2.2 installed but this was already on the phone when I received it, so I've no idea if this was an OTA or not... So I guess I need a different method to make a goldcard now?

Use this:
http://android.modaco.com/content/software/308798/pc-application-goldcardtool/
Probably need to register to get the file, though

Hmmm tried using that tool and no joy... Get my img file downloaded, but then the tool refuses to recognise my phone, despite doing the appropriate change over to 'disk drive'. I tried re-plugging the un-mounting and re-plugging the usb cable. Still no joy.
I'm beginning to lose hope here... That tool won't work and the tutorial here says it's incompatible with 2.2...
**edit**
Been Googling around a fair bit and I can't find any information at all on downgrading a branded 2.2. Only information on people with branded handsets wanting to update to 2.2.
After a bit more searching, I found someone else with the exact same issue as me. http://forum.xda-developers.com/showpost.php?p=10370443&postcount=977
Only one difference though. He doesn't mention if he managed to flash a custom rom after his root. I'm guessing he probably wouldn't have been able to going by your post:
EddyOS said:
To flash any ROM other than the originally on the phone you need a gold card
Click to expand...
Click to collapse

A gold card is only needed to flash a STOCK ROM different from your original - it's not needed to flash a custom ROM. The gold card isn't even needed to root. It's just handy to have in your case as you'd need it to go back to stock due to the lack of an Orange RUU
I'm out of ideas I'm afraid, never had to deal with a gold card as I'm unbranded

Use this:
http://android.modaco.com/content/so...-goldcardtool/
Probably need to register to get the file, though
Click to expand...
Click to collapse
Does that work a lot better then?
I used the method posted by thetasigma3 and I can't get OTA 2.29.405.5 but I can get 2.29.405.2. To get round the problem I installed the 2.29.405.5 RUU and rooted

Anyone who's debranded will need to use the RUU as the OTA won't go through

GoogleJelly said:
I will say that when I installed a custom ROM, I had to pay to unlock my sim because it was being gay and Orange wanted £20 of my hard earned cash to unlock it and send it off. So be prepared.
Click to expand...
Click to collapse
Call me crazy, but why the heck would flashing a custom rom require you to unlock and send off? Presumably the sending off thing would've been for Orange to perform the unlock procedure?
Anyway, back to my main issue, I know I've probably tread the same ground a few times now, but I really don't wanna end up bricking, cos I overlooked a tiny element, or something.
Could someone confirm I have these points all correct please?
Goldcard NOT needed for rooting.
Goldcard NOT needed if/when I flash a custom rom.
Goldcard needed if I wanted to go back to a STOCK rom.
Only reason to flash a STOCK rom is if I need to send back to Orange for repairs etc.
Oh and thanks for the clarification on your earlier post EddyOS. About goldcards not being needed for custom roms as opposed to stock etc.
Think I'm ready to go ahead with the process now, but if I go ahead and something goes wrong, what's my safety net, so to speak? Presumably my battery would die on me long before I get a response here

What you have there is correct (point 2-5)
The unlocking issue was down to some radios causing Orange handsets to become SIM locked. If you're using an Orange SIM this isn't an issue but others who got an Orange handset but use a different SIM card found they wouldn't work.
This was earlier in the Desire's life and I don't think it's applicable now

Try using "GoldCard Helper" app from Android Market, in case you want to try and make a goldcard (as the other methods did not work for you).
As mentioned as EddyOS, all your points from 2 - 5 are correct.

Ok finally got the guts together to go ahead and run unRevoked. (Already had done the driver steps etc).
I've checked with an app from the Android Market, called 'Root Check' to verify root access. That's saying I do have it and it also asked for Root permissions on start-up, which it never did before root. So I assume that's a good sign. I also checked for the 'Superuser Permissions' app in my apps menu. Found it was present and clicked it. Started without any problems. So I guess that's another good sign.
So I guess my next set of questions are reasonable simple.
Does this seem like my phone is now 100% rooted? I think it is, but I could be wrong.
Do I need to install Busybox? Root Checker seems to like seeing it there.
Does it matter if I use Titanium Backup Pro or free? I'm guessing it won't but I'd like to be certain.
If I backup my current Orange rom with Titanium Backup will I be able to go back to that without a goldcard? My guess is no. I didn't make or use one for the root process.

1. Yes
2. For Titanium Backup, yes
3. No
4. You don't backup the ROM with TB, you boot into Recovery and do it there

kvphani said:
Try using "GoldCard Helper" app from Android Market, in case you want to try and make a goldcard (as the other methods did not work for you).
As mentioned as EddyOS, all your points from 2 - 5 are correct.
Click to expand...
Click to collapse
Hey man, I downloaded that app and found a fairly easy looking guide on the Unlockr http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/ . Just wanted to check, if I use that app plus this guide. I skip steps 1-6 right?
Ok gone ahead and done that now. Just having some trouble finding instructions on backing up my Orange rom.
Oh and now that the forum won't grumble at my phone info, here it is. Hopefully that'll shed some more light on my situation, if I need further help.
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.10.05.30
Aug 10 2010, 17:52:18
Android Version
2.2
Baseband Version
32.48.00.32U_5.10.05.30
Kernel Version
2.6.32.15-g29e526b
[email protected] #1
Build Number
2.17.61.3 CL274424 release-keys
Softare Number
2.17.61.3
Browser Version
WebKit 3.1
Model Number
A8181

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?

Weird problems with my m8 after rooting and s-off.

So about 2 days ago I got my new m8 and I was Lucky enough to get a older device (4.4.2) so all I had to do was run sunshine, and I was s-off and rooted in no time. But I've noticed some problems. First of all is that latest twrp does not work, I clean cache and everything, but no luck, it just gets stuck on the splash screen with the pink text at the top. Older versions work tho. And second problem is that if I install insercoin it takes for ever to reboot every time and splash screen is not present.
I was thinking that maybe my problems are related to my older boot loader? Or something of the sorts? Anyway, any help is greatly appreciated, thanks!

You'd have to check the insertcoin rom thread to be sure, but you may need a newer firmware. That's kinda what it sounds like, but I don't use the rom so can't say for certain. Since you're s-off you can always go back, so nothing much to lose. Check the firmware flashing without the panic attacks thread for the how-to.

gokun said:
You'd have to check the insertcoin rom thread to be sure, but you may need a newer firmware. That's kinda what it sounds like, but I don't use the rom so can't say for certain. Since you're s-off you can always go back, so nothing much to lose. Check the firmware flashing without the panic attacks thread for the how-to.
Click to expand...
Click to collapse
Sounds good. Hopefully updating the firmware fixes the twrp problem

For what it's worth I still use an older version or twrp without any issues, so it's not too much of a big deal to stick with the slightly older stable builds.

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