Develop Bugs

getting stuck

hey guys im doing the cyanogenmod htc desire z root. i'm good up till the phone checks the firmware and tells me model id incorrect i have tried both froyo and gingerbread downgrade. i have sdk installed. I tried using a goldcard and that still didnt work. any ideas whats going on.? im runing 2.3.3 and carrier is bell. please help. i have been working and reading for three days. and please no Noobie video. really guys. we have all been in this spot( asking for help that is) . thank you.

Without more details, it's not much specifics I can say.
If I had to make an educated guess I would say that either :
1) Your gfree attempt to change the CID didn't work.
or
2) Your phone is one of the ones that requires the creation of a gold card in order to change the CID version to make the downgrade possible.

I'm a noob at this too, so I don't have much to offer, but I do have the same phone as you (duh) and I'm with Bell too.
I rooted a couple of weeks ago and I also had difficulty getting started - some guides didn't work for me, such as strawmetal's for instance, as well as some others. That's not to say that strawmetal doesn't do awesome work (because he does! - flashaholics) I think it may have had something to with files that he compiled for his guide or maybe even my PC.
In my case this guide worked for downgrading: [thread]http://forum.xda-developers.com/showthread.php?t=1178912[/thread] what was different for me there, compared to other guides, was the thoroughness of how to install the sdk and making all the files were in the right place - this was more work than other guides, but obviously worth it in the end.
This was the guide I used for rooting: http://wiki.cyanogenmod.com/wiki/HTC_Desire_Z:_Rooting
And of course, this is the guide I used for flashing CyanogenMod: http://wiki.cyanogenmod.com/wiki/HTC_Vision:_CyanogenMod
If you're still stuck, you can talk to the guys at #G2Root http://webchat.freenode.net/?channels=g2root obviously that's the web version of the chat portal.
Bell also released an OTA update last month, and I don't know if that would interfere with downgrading (again, I'm a noob too). I didn't download the update at the time because I knew I was going to be rooting my phone soon.
Good luck! You'll be super pumped when you see that first CyanogenMod boot animation!

(HELP) TMO HTC One- keep wiping and still end up in bootloop

I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!

westonnate said:
I got a new HTC One m8 from Tmobile a few weeks ago and instantly went to root and find out about S on and how I can get rid of it. I followed a rooting tutorial on unlockr diligently and unlocked bootloader and installed TWRP and SuperSU. I moved on to S-off the device and got to the last step of the tutorial where it starts to "chug" bottles(Firewater). After the first bottle, it tells me I'm out of luck and that my phone is patched. This confused me. Does this mean that my phone is forever stuck S-on? or does it mean that the developers of firewater haven't developed an S-off method for the newest version of HTC's software and that I simply have to wait.
This is just my first problem, even though I can't flash custom ROMs I was fine because I was willing to give the stock ROM a chance and just tweak it with root privileges, but no, the next time I had to restart for some various reason it starts bootlooping every few minutes. I swear I didn't do anything wrong when rooting. Is it just too new and the newest HTC software makes the rooting process obsolete making it impossible to root?
So I end up wiping the phone not being able to save all the pictures I took on my trip in the mountains. My phone is still rooted but the phone is wiped. I go about thinking the solution is fixed and when I decide to nandroid backup, I go into recovery, do a simple backup and when I restart it goes straight back to the infuriating bootloop. A simple nandroid backup shouldn't make it go into a bootloop.
So I decide to relock the bootloader, install the stock recovery and software again and start over. Maybe I really did mess up rooting. I go through the process again and low and behold my phone goes into a bootloop again.
I'm so sick and tired of this phone and I'm not sure why it always seems to happen to me. I follow the tutorials closely and it always ends up ****ting on me.
It recently went into a bootloop after a good 3 day run where I managed to keep the phone on the entire time. Had to restart because the wifi antenna wasn't working and another bootloop ensued. I decided to make this thread to see if any other new users are experiencing similar difficulties and seeing if anyone knows a cause or maybe a solution. Right now in the process of unrooting and going back to stock.
It would be a shame if there really is no way for me to unlock the full potential of my new phone. Almost wishing I had bought a nexus.
Thank you for anyone who was willing to read that and to anyone who takes the time to write a response. Thanks!
Click to expand...
Click to collapse
If you wanna fix it quick then just do an RUU (t-mobile one) and after you've done that use Sunshine to root, unlock and S-OFF your phone. All though Sunshine costs $25 it is a sure fire to work.
You can find a tutorial for the RUU in the t-mobile forum I believe, not sure as im replying to this before I go to bed but it should have one. If by some chance "TMO" doesn't mean T-Mobile then my bad. Anyways if you get confused take your time and do your research or wait for someone else or me to assist you further.
Also if you used Xposed then that could be the problem, I've had it randomly bootloop me after days of use, just google the Xposed deactivate script zip or Uninstaller script and flash it to remove it. If you don't have it then don't do this part.
Lastly I doubt you'll regret buying an M8 after you get it setup properly, it's a great phone but of course that's just mine and a lot of people's opinion. Anyways good luck and hope one of my solutions fix it! If not then don't be afraid to ask more questions or request further assistance whether from me or someone else.

S1L3nTShaDoWz said:
If by some chance "TMO" doesn't mean T-Mobile then my bad.
Click to expand...
Click to collapse
It does, although T-Mobile is a huge carrier in Europe, and AFAIK only the US T-Mob variant has an RUU (and not immediately clear what version the OP has).

You can flash custom roms without s-off, and have you tried wiping cache and fixing permissions? Idk if that'd solve it or not but worth a try.

HTC Desire 816 without Update Option (SOLVED)

Ok guys i roamed a lot on the internet trying to get a way to fix a not so common problem(but yes a major problem) on the htc desire 816. Finally resolved mine and hope that it will solve yours too (note that having a super CID phone is a plus point, i have that, proceed at your own risk) which means my phone is not region locked
Please note this may lead you to bricking your phone if not done properly.
UPDATEDFollow the steps below:-
Download your version of stock ROM.zip or RUU.exe From HERE
If your one is in .exe format then simply connect your phone and run RUU.exe and don't follow the steps given below
Rename the file to 0P9CIMG only(dont change extension .zip)
Place the file in your Ext. SD Card
Turn off your phone
Enter into bootloader by pressing VOLUME DOWN + POWER
Your phone will automatically recognize the zip file and start flashing it
Be Patient
Delete the zip after your phone has succesfully returned to stock.
HIT THANKS IF I HELPED :good::fingers-crossed::good:

First off, thanks for the post I've been searching this everywhere. Unfortunately though while updating, I got this error message in recovery: "Package expects build fingerprint of htc/htc_asia_wwe/htc_a5dwg:4.4.2/KOT49H/37"a number"983.1:user/release-keys or htc/htc_asia/wwe/htc_a5dwg:5.0.2/LRX22G/510432.1:user/release-keys; this device has htc/htc_europe/htc_a5dug:5.0.2?LRX22G/510432.1:user/release-keys". I'm assuming 'a5dwg' means my phone is a asia wwe model and thus not compatible with the european recovery.img I downloaded from your given link? If so, where can I find a stock recovery.img for asia wwe model? (My phone is a Desire 816 dual sim with 4.4.2 kitkat, sense 6, software number 1.58.707.1, kernel 3.4.0-g4ff7e8c and baseband version 1.31.50.0624_2) Does anybody else know?

I'll post that soon if I find it
Sent from my HTC Desire 816 dual sim using XDA Free mobile app

First Thank you for your effort.i did what you said BUT
1. When i connect my phone in fast boot and type command adb devices it does not show my Device ID . However it flashed the CWM recovery in phone.
2. i backed up my ROM and then restore your Provided ROM it did not ask me to fix root.
3. Everything works great Wi-Fi vibration etc. No Problem at all.Phone was rooted.i tried to unroot but after reboot it reroot device again.
4. Then again i connect my phone in fast boot and type "adb devices" again it doest not show my ID.Again i flashed stock recovery by ignoring this.
5. i reboot my phone and downloaded the SW update which was 151 MB. When download was finished it checked my phone for Verify.
6. i got error there that "your are using modifying system please revert back to your stock ROM" so it did not update.
7. Please give me solution for this Problem.i did everything you said.Now tell me what should i do to overcome this Problem?
8. My device HTC Desire 816w [Unicom] S-ON.

replacing cwm with twrp
Dear
is it ok to replace the cwm with twrp to do the steps?

ade.l said:
Dear
is it ok to replace the cwm with twrp to do the steps?
Click to expand...
Click to collapse
NO dont do this as twrp doesnt work with cwm backups
you might end up failing in restoring the backup

After flashing CM-12, Both SIM are not working. Flashed stock L firmware but still problem is there... any solution?

mr.jxtian
pls help me out,
i did this cwm backup for my htc a5_dug..j_15 with baseband 1.13.3230.27.0303_13.19.3230.00D_F
build number 1.29.708.1 CL342310 release key...kernel version [email protected]#. htc sense6.0, software number 1.29.708.1
when i restore this backup my sims are not working...pls help

HTC Desire 816 dula Sim
Dear, I have HTC desire 816 Dual Sim
Software Information
Android Version 4.4.2
HTC Sense
6.0
Software number
1.56.401.1
HTC SDK API level
6.20
Baseband 1.13.3230.16.05.13.17.3230.00D_F
Build number
1.56.401.1 CL372006 RELEASE-KEYS
I am not able to update to lollipop. Should possible to officially update by this method ...plz reply
---------- Post added at 09:37 AM ---------- Previous post was at 08:50 AM ----------
jxtian said:
pls help me out,
i did this cwm backup for my htc a5_dug..j_15 with baseband 1.13.3230.27.0303_13.19.3230.00D_F
build number 1.29.708.1 CL342310 release key...kernel version [email protected]#. htc sense6.0, software number 1.29.708.1
when i restore this backup my sims are not working...pls help
Click to expand...
Click to collapse
DO hard Reset
I have same problem with Lenovo A6000 solved after reinstall customer recovery and hard reset after that.

Harris777 said:
First Thank you for your effort.i did what you said BUT
1. When i connect my phone in fast boot and type command adb devices it does not show my Device ID . However it flashed the CWM recovery in phone.
2. i backed up my ROM and then restore your Provided ROM it did not ask me to fix root.
3. Everything works great Wi-Fi vibration etc. No Problem at all.Phone was rooted.i tried to unroot but after reboot it reroot device again.
4. Then again i connect my phone in fast boot and type "adb devices" again it doest not show my ID.Again i flashed stock recovery by ignoring this.
5. i reboot my phone and downloaded the SW update which was 151 MB. When download was finished it checked my phone for Verify.
6. i got error there that "your are using modifying system please revert back to your stock ROM" so it did not update.
7. Please give me solution for this Problem.i did everything you said.Now tell me what should i do to overcome this Problem?
8. My device HTC Desire 816w [Unicom] S-ON.
Click to expand...
Click to collapse
IF your phone is not region locked and second that it is s-off then that's what will give you best results in these kind of things.

azhargalaxy said:
Dear, I have HTC desire 816 Dual Sim
Software Information
Android Version 4.4.2
HTC Sense
6.0
Software number
1.56.401.1
HTC SDK API level
6.20
Baseband 1.13.3230.16.05.13.17.3230.00D_F
Build number
1.56.401.1 CL372006 RELEASE-KEYS
I am not able to update to lollipop. Should possible to officially update by this method ...plz reply
---------- Post added at 09:37 AM ---------- Previous post was at 08:50 AM ----------
DO hard Reset
I have same problem with Lenovo A6000 solved after reinstall customer recovery and hard reset after that.
Click to expand...
Click to collapse
what are the problems you are facing?? please state them.
You'll be able to get OTA updates after this method and upgrade to lollipop ver 5.0.2

jakhar13 said:
You'll have to make sure your phone is not region locked and second that it is s-off. That's what will give you best results in these kind of things.
Click to expand...
Click to collapse
To tell someone, that doesn't even know the correct way to flash a device, to get S-OFF (which completely removes ALL security, so the flashing won't stop, even if it is a bad flash) is the most ridiculous thing I've ever heard! I know experienced users that bricked their phone gaining S-OFF and attempting to flash a file, they THOUGHT were for their device. So imagine an unexperienced user trying the same.
Also, maybe you should tell the user that S-OFF costs real money. You need to buy the sunshine app or for MTK variants a dongle to make it work.
It's really nice of you posting this tutorial, but please consider that most of the users in this section of the forums are inexperienced and seek help.

nukaru said:
To tell someone, that doesn't even know the correct way to flash a device, to get S-OFF (which completely removes ALL security, so the flashing won't stop, even if it is a bad flash) is the most ridiculous thing I've ever heard! I know experienced users that bricked their phone gaining S-OFF and attempting to flash a file, they THOUGHT were for their device. So imagine an unexperienced user trying the same.
Also, maybe you should tell the user that S-OFF costs real money. You need to buy the sunshine app or for MTK variants a dongle to make it work.
It's really nice of you posting this tutorial, but please consider that most of the users in this section of the forums are inexperienced and seek help.
Click to expand...
Click to collapse
Yes I do know that but you must also know that there is no other simple method right now to gain S-OFF without the sunshine app which costs 25$ at the time.
I know that they can end up doing it wrong, but the files that i've stated are stock roms or ruu files and are not that much of a problem if they know which one to look out for.
I should have told them that. Sorry my bad.
BUT THANKS TO YOU FOR STATING IT :good:

jakhar13 said:
what are the problems you are facing?? please state them.
You'll be able to get OTA updates after this method and upgrade to lollipop ver 5.0.2
Click to expand...
Click to collapse
Dear My phone is showing
*****Locked ******
A5_Dug PVT SHIP S-Off
CID-1111111
and also it is unrooted phone . Can you plz Pm me Step by step for updating to lollipop and Actually I am new here.

Thanks a lot bro... I done it .. thanks for your kind support.

azhargalaxy said:
Thanks a lot bro... I done it .. thanks for your kind support.
Click to expand...
Click to collapse
On December 27th you posted here that your phone was pure stock and you couldn't update. Now a few months later your phone is now set to S off which by the way requires you to preroot your phone first and now your set to SuperCID which takes even more knowledge to do through ADB/fastboot properly but your still "new" here? Now your saying your phone isn't even rooted and after asking the OP for his "supposed" help(which none of which is documented anywhere here with interactions back and forth between the two of you) your thanking him for what exactly? Coming across the one other "new" guy with an S off and SuperCID set device? This is all sounding very fishy and "real" people are being hurt here who don't have S off and SuperCID and are soft bricking their phones left and right from what I'm reading here. Shame on both of you (OP) for giving such incomplete advice and having more unlocked phone's then the rest and not even sharing your back and forth discussions here in XDA to inform the rest. This forum is one big joke but the people being hurt by it aren't laughing so neither will I !

thoctor said:
On December 27th you posted here that your phone was pure stock and you couldn't update. Now a few months later your phone is now set to S off which by the way requires you to preroot your phone first and now your set to SuperCID which takes even more knowledge to do through ADB/fastboot properly but your still "new" here? Now your saying your phone isn't even rooted and after asking the OP for his "supposed" help(which none of which is documented anywhere here with interactions back and forth between the two of you) your thanking him for what exactly? Coming across the one other "new" guy with an S off and SuperCID set device? This is all sounding very fishy and "real" people are being hurt here who don't have S off and SuperCID and are soft bricking their phones left and right from what I'm reading here. Shame on both of you (OP) for giving such incomplete advice and having more unlocked phone's then the rest and not even sharing your back and forth discussions here in XDA to inform the rest. This forum is one big joke but the people being hurt by it aren't laughing so neither will I !
Click to expand...
Click to collapse
I think you should consider reading my post where I've clearly mentioned "this may lead you to bricking your phone if not done properly & proceed at your own risk"
Nukaru has also already stated in a post above what i should have told regarding s-off and the info i provided.
If you notice i have asked people to post their specific problem in detail and also i had sent them PM's asking them the details of the problem. I've helped them as far as i could. I'm not a developer or someone with great knowledge in these things but what i've written is from my experience of the problems that i faced and how to resolve them.
The original post was completely different from what it is now which is much easier to do. People who were following the steps in the earlier version of my original post faced those problems that you are talking about.
I appreciate your criticism for this post and i also say that what you are saying is not completely incorrect.I'll soon edit this thread to give proper info to people in need.
:good:

http://forum.xda-developers.com/desire-816/help/stuck-htc-logo-screen-t3339751
Can you check this topic and help me? I see you are experienced.. I don't care what Android version I get, I just need my phone working again..
Would flashing Stock ROM help with my situation or not? and what kind of recovery do I need to flash this ROM? I have stock recovery right now..

jakhar13 said:
I think you should consider reading my post where I've clearly mentioned "this may lead you to bricking your phone if not done properly & proceed at your own risk"
Nukaru has also already stated in a post above what i should have told regarding s-off and the info i provided.
If you notice i have asked people to post their specific problem in detail and also i had sent them PM's asking them the details of the problem. I've helped them as far as i could. I'm not a developer or someone with great knowledge in these things but what i've written is from my experience of the problems that i faced and how to resolve them.
The original post was completely different from what it is now which is much easier to do. People who were following the steps in the earlier version of my original post faced those problems that you are talking about.
I appreciate your criticism for this post and i also say that what you are saying is not completely incorrect.I'll soon edit this thread to give proper info to people in need.
:good:
Click to expand...
Click to collapse
I genuinely appreciate your response and your desire to help people I'm sure is genuine but I did read your whole post and every single persons response one after the other. I learned that from my first days here at XDA that sometimes the responses gave me more info than the original post. Plus I'm OCD when it comes to reading. I also am not an expert/dev and have just learned by reading obsessively and dealing with my own device's issues over the years so I'm not saying you don't have the right to help here( we need more people to help.)
What I am saying is maybe you should be "reading" more tutorials from more experienced people and devs to get your information gaps fixed better before "writing" more tutorials that are (and I've read all of them to be fair) incomplete with dead links and more emoji filled than correctly filled. PMing is great and it's commendable that you are taking that much effort into helping people but that doesn't help the next guy that comes across this forum after you've gone to sleep and wants to get the information you and the other person communicated. I guess if the mods are fine with it I have to be but my advice is to read some of the better written tutorials and support forums then compare them to yours and you'll pretty much see what I'm talking about and if you don't then none of what I'm saying matters anyway. Good luck to you and I mean that.

thoctor said:
I genuinely appreciate your response and your desire to help people I'm sure is genuine but I did read your whole post and every single persons response one after the other. I learned that from my first days here at XDA that sometimes the responses gave me more info than the original post. Plus I'm OCD when it comes to reading. I also am not an expert/dev and have just learned by reading obsessively and dealing with my own device's issues over the years so I'm not saying you don't have the right to help here( we need more people to help.)
What I am saying is maybe you should be "reading" more tutorials from more experienced people and devs to get your information gaps fixed better before "writing" more tutorials that are (and I've read all of them to be fair) incomplete with dead links and more emoji filled than correctly filled. PMing is great and it's commendable that you are taking that much effort into helping people but that doesn't help the next guy that comes across this forum after you've gone to sleep and wants to get the information you and the other person communicated. I guess if the mods are fine with it I have to be but my advice is to read some of the better written tutorials and support forums then compare them to yours and you'll pretty much see what I'm talking about and if you don't then none of what I'm saying matters anyway. Good luck to you and I mean that.
Click to expand...
Click to collapse
Thanks you understood me really well. Appreciate your advice, working on it.

"System update available"

Hi,
terribly sorry to bother you guys!
I recently bought an M9 (Belgium, no carrier) and rooted it with the help of this youtube video /watch?v=rOHN8byHAzk
works fine, it's rooted.
The thing is: i did updates before doing the root, as i unlocked bootloader everything was lost/deleted, at the time (4a.m), with my brain half asleep i didn't think about doing the updates again before performing the actual root. Now i keep getting the "system update available" message and can't get rid of it.
It'll keep popping up every few hours, obviously i can't install them because i arrive back at twrp recovery.
Android version 5.0.2
Kernel version 3.10.49-g5c16a62
I turned software updates off in the "about" section in settings, to no avail. I keep getting the message that updates are available. Downloading them and then proceeding to remove the downloaded files don't solve it.
I'm a total noob at this, but (hopefully) not a complete idiot. If there are any steps i can take to get rid of this constantly popping up, please advise me:fingers-crossed:

There's more than one possibility to proceed. Could you provide the output of the "htc_fastboot getvar all" command, when M9 is in download mode (without IMEI and Serial no.). I'd like to point you into the right direction.
Send by the swarm intelligence of my coffee machine ?.

Thanks for taking the time!
It's in download mode, i've got my command prompt open but it says "htc_fastboot is not recognized as an internal or external command, program or batchfile"

In all honesty just pay for s-off and you can flash an unsigned zip and be done with it.
Otherwise you need to get back to official status to flash the update. Pita to be honest.
Sent from my HTC One M9 using Tapatalk

shivadow said:
In all honesty just pay for s-off and you can flash an unsigned zip and be done with it.
Otherwise you need to get back to official status to flash the update. Pita to be honest.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
*sigh*
I'm going to take a few days off of work and try to educate myself on how all of this works exactly because i'm starting to feel like i just came out of the stone age. Honestly, i just rooted my last phone through good old towelroot without ever having to touch or change anything else. I should not have touched stuff i know nothing of to begin with.
I appreciate you guys taking the time to reply, i'm gonna find some sites to teach me more about this, if you have anything that could help me, feel free to share, because i literally know 0.

Fatimiyye said:
*sigh*
I'm going to take a few days off of work and try to educate myself on how all of this works exactly because i'm starting to feel like i just came out of the stone age. Honestly, i just rooted my last phone through good old towelroot without ever having to touch or change anything else. I should not have touched stuff i know nothing of to begin with.
I appreciate you guys taking the time to reply, i'm gonna find some sites to teach me more about this, if you have anything that could help me, feel free to share, because i literally know 0.
Click to expand...
Click to collapse
Basically, there is a safety feature in HTC otas now that prevents them from running unless your phone is 100% stock. So being rooted, it won't run. There are only two ways forward, find the RUU files for your carrier and install them, or get s-off and update manually. There are multiple threads on how to do all this in the General forum. Read there before doing anything else. HTC phones work differently from other handsets that have to be hacked to achieve root. There is an official path, but how you do it matters.

iElvis said:
Basically, there is a safety feature in HTC otas now that prevents them from running unless your phone is 100% stock. So being rooted, it won't run. There are only two ways forward, find the RUU files for your carrier and install them, or get s-off and update manually. There are multiple threads on how to do all this in the General forum. Read there before doing anything else. HTC phones work differently from other handsets that have to be hacked to achieve root. There is an official path, but how you do it matters.
Click to expand...
Click to collapse
Thank you very much man. I'm gonna learn up first, and then take your advice and head to the general forum.
For all other noobs who are desperate to catch up, this is helping me out quite a bit:
http://androidforums.com/threads/how-to-and-some-root-terminology.353591/ => Terminology
https://www.youtube.com/watch?v=rOHN8byHAzk => Unlock bootloader and root the phone
http://forum.xda-developers.com/showthread.php?t=2588979 => This helps to install ADB/fastboot/drivers
http://www.addictivetips.com/mobile...on-htc-android-phones-with-unrevoked-forever/ => some info about s-off
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3 => HTC One M9 FAQ
Edit: OH, AND THIS! https://www.youtube.com/watch?v=JmvCpR45LKA
FFS, WATCH THAT ONE!

Just in case anyone has the same issue (i like to end on a positive note =D ) :
The easiest working solution i found for the issue is to go to the Apps management (Settings, apps), go to "All", select "Updater" and then clear data.
No pop ups so far.
Credit for this goes to moderator Earlymon from androidforums

HTC one m8 stuck and desperate owner

Guys I am kind of screwed here, could you help me out?
Ok so I wanted to root my HTC one m8 and flash a custom rom on it (the sky dragon one, but that is irrelevant). So I looked up a video on youtube called; "how to root you htc one m8 **made easy** " and everything went well (it did take me about 3 hours... I am not a proud man right now...), until I had to install a custom rom. I wiped my phone, cache etc. (including phone storage) and here's where I start to notice my failure. I don't exactly know what steps I did and where exactly everything went wrong, but basically this is what I've got to work with: -a htc one m8 that gets stuck on the htc boot-up screen -roms complaining about missing md5 files and verification error or something -and last but not least; a very concerned owner who, after about 7hours of non-stop trying, is pretty desperate for help...
right now is there anyone who could help me with this, it would mean a lot to me (and my phone)
Edit: I remember where exactly my phone got stuck in the boot-up htc screen; it was right after I rooted my phone, but supersu said it was missing binary files or something. I installed, according to the guy from the video this woul fix it, supersu version 2.4 updater or something, and from that point the phone would't get past the boot-up screen. Again: any help is, at this point, very very veerryy appreciated

abramo2001 said:
I looked up a video on youtube called; "how to root you htc one m8 **made easy** " and everything went well (it did take me about 3 hours... I am not a proud man right now...)
Click to expand...
Click to collapse
Beware of such Youtube tutorial videos. I normally advise against using them. They often contain outdated information that can easily screw you up. And even more important, they are often used to shortcut the learning process, spoon-feeding you the steps in a way that pretty much means you won't learn anything; and leave you high and dry without the proper knowledge, when things inevitably do south.
Word to the wise: read, learn and understand before trying anything else. I know XDA can be a bit intimidating (like trying to drink out of a firehose, as one new member phrased it). But all the information is here, for those willing to take the time to read and learn.
abramo2001 said:
Ok so I wanted to root my HTC one m8 and flash a custom rom on it (the sky dragon one, but that is irrelevant).
Click to expand...
Click to collapse
Its completely relevant and important what ROM and version number you tried to install. Skydragon GPE or Sense? And what version number?
abramo2001 said:
Edit: I remember where exactly my phone got stuck in the boot-up htc screen; it was right after I rooted my phone, but supersu said it was missing binary files or something. I installed, according to the guy from the video this woul fix it, supersu version 2.4 updater or something, and from that point the phone would't get past the boot-up screen
Click to expand...
Click to collapse
Not clear from your description when you tried to root. But its probably at least part of the problem. You don't need to root if you are installing a custom ROM. You don't need to root in order to flash it (just an unlocked bootloader, and custom recovery), and you don't need to root after flashing, as all the custom ROMs are already pre-rooted.
For further help, we'll need more info on the phone. If you know how to use fastboot, do a fastboot getvar all, and post the results (delete your IMEI and serial number before posting). If you don't know how to use fastboot . . . well, time to start reading.
Also, need to know what TWRP version, and SuperSU version you tried.

redpoint73 said:
Beware of such Youtube tutorial videos. I normally advise against using them. They often contain outdated information that can easily screw you up. And even more important, they are often used to shortcut the learning process, spoon-feeding you the steps in a way that pretty much means you won't learn anything; and leave you high and dry without the proper knowledge, when things inevitably do south.
Word to the wise: read, learn and understand before trying anything else. I know XDA can be a bit intimidating (like trying to drink out of a firehose, as one new member phrased it). But all the information is here, for those willing to take the time to read and learn.
Its completely relevant and important what ROM and version number you tried to install. Skydragon GPE or Sense? And what version number?
Not clear from your description when you tried to root. But its probably at least part of the problem. You don't need to root if you are installing a custom ROM. You don't need to root in order to flash it (just an unlocked bootloader, and custom recovery), and you don't need to root after flashing, as all the custom ROMs are already pre-rooted.
For further help, we'll need more info on the phone. If you know how to use fastboot, do a fastboot getvar all, and post the results (delete your IMEI and serial number before posting). If you don't know how to use fastboot . . . well, time to start reading.
Also, need to know what TWRP version, and SuperSU version you tried.
Click to expand...
Click to collapse
Thank you very much for your help and in the future I will definetly do some more research before doing this ind of stuff, but I EXTREMELY glad to tell you: I FIXED IT . I googled and googled and all in all it probably took me around 15 hours, but I installed the marshmallow stock gpe rom for my phone via fastboot and after about 70 tries, learning and googling along the way, it worked. I don't know what went wrong the first time I tried (with the rooting), but everything is fully functional right now and my battery life, along with my free storage (bloat used to take up around 4 gigs), has improved significantly. I really really appreciate your response and I wil certainly be more careful in the future. Also, am I now allowed to call myself a "hacker"? I am right? . Have a great day; android is masterrace!

abramo2001 said:
I googled and googled and all in all it probably took me around 15 hours, but I installed the marshmallow stock gpe rom for my phone via fastboot and after about 70 tries, learning and googling along the way, it worked. I don't know what went wrong the first time I tried (with the rooting), but everything is fully functional right now
Click to expand...
Click to collapse
Probably could have cut down on the amount of time finding the problem, and the reason root failed; if you had provided the info requested in my last post. My last post was meant to be taken "post the required info, and we'll help you more". But glad you sorted it out, anyway; and you're welcome and glad to have helped in whatever way you found useful.
I'd also suggest sticking to XDA search function for these types of mods (or at least, reputable mod websites). Googling random websites will often lead to outdated info; and the info is often stolen from XDA, anyway.