Related
Hi guys,
so, this is indeed my first post here. But the forums helped me a lot with playing with my Desire.
But now I have a problem for which I cannot find help anywhere, neither here via the search nor Google. I really hope you would be so kind to help me find an answer.
This morning I dropped my Desire Nothing really happened case, but the display won't work anymore. When I start it I feel the vibration that indicates the system start, and I also see the buttons under the display lighting up. But the damn display itself stays black. My best guess now is that the connector between display and motherboard might be disconnected/broken.
Since I hope to get it repaired over warranty, I think the first thing to do is to recover standard sense rom and unroot it. Otherwise HTC wouldn't repair it, right?!
So now the tricky part: how can I do that with an unconnected display? Is there any chance?
Or would you just risk it and send it in rooted and with a custom rom?
What's left to say: It cannot be discovered by my computer since I'm not able to turn it on.
I would really really appreciate any help or inputs on how to resolve this.
Cheers,
Pascal
PS: Since my Macbook Air got stolen 3 days ago, I can only answer from my office PC.
Just boot in to fast boot the run ur ruu then send it off
Sent from my HTC Desire using XDA App
So, how would I do that exactly without being able to use the display or the pc?
http://www.youtube.com/watch?v=6VVQyQizxhM
or
http://www.youtube.com/watch?v=XOm2DCzuE8g
Both methods require your minimum interaction.
Thanks!
Since I have no Win PC, this would be the equivalent for Mac/Linux, right?
And, how do I find out Baseband Version/Software Number?
I don't know much about OpenRUU, wait for someone else.
Second youtube video doesn't depend on your OS so I would suggest you that solution. However, it requires some interaction with your phone so...
If you're able to find a friend with Windows, that would be win-win solution. Basically you have zero interaction with your phone, just instal HTC Sync (drivers) and plug in the phone.
Since your phone is rooted do not bother about SW/BB version and use RUU ROM provided for your carrier which will restore SW and BB version to the stock. If your carrier sells unbranded Desire then go for the last official Froyo WWE:
http://shipped-roms.com/index.php?category=android&model=Bravo (2.29.405.5)
If your Desire is branded, find adequate ROM and possibly you'll need a goldcard too.
Thanks for your help guys.
Fortunately, I'm able to use a WinPC for a couple of days now. So, yay me
Unfortunately, it's not working the way I tried and wanted it to work. Here's what I did:
Downloaded, installed and started HTC Sync, plugged in my phone and powered it on. HTC Sync doesn't recognize the phone
Secondly I downloaded and executed the RUU exe, but it also doesn't recogize the phone.
Am I doing something wrong? Or is it just not working cos I'm not able to unlock the SIM?
Let me make something clear to you! If they do take and repair a dropped phone, they'll not even care to look at the software... Seriously. Warranty is for factory/shipping errors, which were caused by the manufacturer. Good luck convincing them how a factory fault suddenly destroyed your display.
But the easy way of going to stock is to get a sd-card reader and put a PB99IMG.zip in the root of the sd-card and start it up in bootloader mode. It'll flash it automatically.(no need to use a windows pc)
Well, it's worth a try, isn't it?! And to be on the safe side, I'd like to get everything back to normal before sending it in. At least to know, that the SW really isn't the reason why they don't wanna repair it.
And for this PB99IMG.zip, does it have to have exactly this name?
Thx
Hey,
Made a few posts relating to my issues with the galaxy nexus and it not charging etc....
Now I have contacted Samsung and they said send it for repair, not this leaves me in a bit of a pickle seeing as the phone has been rooted since day one.
The issue comes as the phone does not respond to being plugged into the computer despite all drivers being installed.
Has any bright person got any idea's to removing the root on the handset and re-flashing stock .img without the need of adb and fastboot seeing as the phone just comes up as not recognised, probably due to the issues with the USB port on the handset (see initial problem...)
Don't really want to send it back to Samsung rooted as they will just send it back saying its my fault even though its not and its a hardware issue.... not software.
Any advice would be great,
J
P.s. Had a check around the internet on several Google groups about this issue and the only conclusion is send back to Samsung or get a new USB port for the phone from Ebay.
Just flash a stock ROM in recovery then use this app to lock bootloader http://forum.xda-developers.com/showthread.php?p=27878074 and then unroot (SuperSU has this option).
You are my friend is why i love XDA , thanks for the advice.
J
See this post for a much better explanation
http://rootzwiki.com/topic/19864-vz...ockrootflash-romsfaq/page__st__40#entry759280
Essentially that tells you to lock bootloader and then use mobile odin to flash a stock ROM.
mbh87 said:
See this post for a much better explanation
http://rootzwiki.com/topic/19864-vz...ockrootflash-romsfaq/page__st__40#entry759280
Essentially that tells you to lock bootloader and then use mobile odin to flash a stock ROM.
Click to expand...
Click to collapse
Same guide is posted here on XDA, sir.
Thanks for the reference, though =]
Jubakuba said:
Same guide is posted here on XDA, sir.
Thanks for the reference, though =]
Click to expand...
Click to collapse
Yeah I know but I was browsing rootz too and you already posted on the page I was on so was easier to find the guide there
Hi there,
Long story short. Im on holidays using a MAC which I am not used to (Windows User). Ran a hex editor to change up some text for the boot loader screen (UNLOCKED to LOCKED) but I think I Hex'd it wrong. I then zipped the hboot.img into the firmware.zip and I flashed it on my phone using:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Phone now won't turn on. Im fairly sure I hard bricked it.
Any advice on what I can do to fix it/if I can fix it?
The screen has a pressure crack in the digitizer which I'll be getting fixed through warranty with Optus Australia although I'm fairly sure technicians will see what I've done straight away concerning the software side of things.
Cheers
--EDIT--
Sent phone in for Warranty with Optus. Stated phone didnt turn on and did not charge. Got a new phone replacement.
Hiyoal said:
Hi there,
Long story short. Im on holidays using a MAC which I am not used to (Windows User). Ran a hex editor to change up some text for the boot loader screen (UNLOCKED to LOCKED) but I think I Hex'd it wrong. I then zipped the hboot.img into the firmware.zip and I flashed it on my phone using:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Phone now won't turn on. Im fairly sure I hard bricked it.
Any advice on what I can do to fix it/if I can fix it?
The screen has a pressure crack in the digitizer which I'll be getting fixed through warranty with Optus Australia although I'm fairly sure technicians will see what I've done straight away concerning the software side of things.
Cheers
Click to expand...
Click to collapse
Messing with the hboot is a sure fire way to brick it permanently ...nice job
I know this.
Advice on what normally happens with phone companies regarding this would be appreciated.
How do phone companies repair this sort of problem? Im no super genius when it comes to tech stuff but don't they use something along the lines of JTAG?
If this is far too complex from an intermediate user please let me know. Im up for trying anything at the expense of around $100. Gives me something to learn also.
Hiyoal said:
I know this.
Advice on what normally happens with phone companies regarding this would be appreciated.
How do phone companies repair this sort of problem? Im no super genius when it comes to tech stuff but don't they use something along the lines of JTAG?
If this is far too complex from an intermediate user please let me know. Im up for trying anything at the expense of around $100. Gives me something to learn also.
Click to expand...
Click to collapse
just send it to HTC, they will tell you if they will fix it or not and how much they charge. You basically need a new motherboard
As I recall the hardware required to do JTAG cost thousands
Hiyoal said:
Hi there,
Long story short. Im on holidays using a MAC which I am not used to (Windows User). Ran a hex editor to change up some text for the boot loader screen (UNLOCKED to LOCKED) but I think I Hex'd it wrong. I then zipped the hboot.img into the firmware.zip and I flashed it on my phone using:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
Phone now won't turn on. Im fairly sure I hard bricked it.
Any advice on what I can do to fix it/if I can fix it?
The screen has a pressure crack in the digitizer which I'll be getting fixed through warranty with Optus Australia although I'm fairly sure technicians will see what I've done straight away concerning the software side of things.
Cheers
Click to expand...
Click to collapse
First mistake was using that awful mac.
Second mistake was going with optus, they will not help.
The only logical thing to do is to send it to htc.
Hope this helps
1. Im definitely an idiot for using the mac. I'll never use one again.
2. Im on a 2yr plan with optus (with 2yr warranty) and i cracked the digitizer behind the glass yesterday while go karting. Ill see how i go with telling them that and will just tell em it didnt turn on this morning.
Last time i handed in my old htc one xl to telstra (unlocked, s-off with no spoof hboot screen) cos the lcd module died and it was replaced and wiped free of charge through warranty... Even with the software tampering voiding warranty.
3. Last resort I reckon.
Sent from my Nexus 7 using XDA Free mobile app
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.
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