Hi all,
My phone keeps crashing and rebooting. Every time it comes back, it needs to resign on to wifi (retype in WPA), downloads a file calle "how-to" (which I can't find), and have to resign into Google. By the time it accomplishes all this, it crashes and restarts the whole shabang again. Tried recovery mode and clearing, no difference.
It might be worth mentioning it boots into extreme power saving mode too.
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
redpoint73 said:
Is the phone modified (unlocked bootloader, root, custom ROM, etc.) or is it stock?
On the bootloader screen, what is the OS number?
Click to expand...
Click to collapse
It is stock. Tried to root it but it didn't take. Don't know which version as it is stuck in a loop currently. It seems to me this is a hardware problem though.
carljames0603 said:
It is stock. Tried to root it but it didn't take.
Click to expand...
Click to collapse
Need more details on that. How did you try to root, what exact steps did you perform, where did you get stuck and why, etc.
Always provide as many details as possible when asking for help and answering our questions.
carljames0603 said:
Don't know which version as it is stuck in a loop currently.
Click to expand...
Click to collapse
If its stuck in a loop (rebooting) then simply hold volume down, and don't let go. The next time it reboots, it will go to bootloader (then you can let go of vol down).
From there, tell us what OS number it says on the bootloader screen, near the top.
carljames0603 said:
It seems to me this is a hardware problem though.
Click to expand...
Click to collapse
What makes you think that? You haven't provided any details or evidence that would support the statement.
Its possible its a hardware issue. But based on what little you've said, its perfectly possible its a software issue. So be optimistic, unless you have specific evidence to think otherwise.
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process. Pain in the ass.
The OS is 3.28.605.4
carljames0603 said:
When it gets stuck in a loop, holding down VOL DOWN does nothing. The only way to get to the boot loader is to go to SETTINGS>POWER OPTIONS and disable fast boot. Then hopefully it shuts down fully and doesn't crash and reboot in the process.
Click to expand...
Click to collapse
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
redpoint73 said:
This is false. That setting only applies when the phone is powered off; since in that condition the phone was not truly powered off (just a deep sleep mode). A reboot is always a reboot.
I know this for fact, because back when I was on KitKat (and on past devices - the "fast boot" power setting was removed after KitKat) I never ever bothered to turn off the "fast boot" feature. I was able to get to bootloader whenever I wanted by rebooting (not power off) and then holding vol down. Worked every time.
Hold down the vol down button during the next reboot cycle, and it will go to bootloader. It may be that some set of conditions is just making you think what you posted is true. But try not to get the "timing" right. Just hold the vol down, and don't let go. It will go to bootloader, if its actually bootlooping.
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
Also, you never answered my previous question, how far you got with the rooting, and what steps you performed exactly. Is the bootloader LOCKED, UNLOCKED, or RELOCKED?
When you do go to bootloader, it stays there (doesn't reboot)?
Click to expand...
Click to collapse
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked, and it stays there until I push it to reboot.
carljames0603 said:
Either way, sorry I missed the question. Not very far, it crashes before to long. I tried downloading the SU app as prescribed in the site, but can't get it on the device itself.
The bootloader is locked.
Click to expand...
Click to collapse
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
carljames0603 said:
It's not false, because that's what is happening. I hold down the button the whole time and it will go through the whole process and never go to the bootloader.
Click to expand...
Click to collapse
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
redpoint73 said:
Nowhere will you find a guide for this device, that tells you to use an SU app. That isn't the proper way to root this phone. You need to flash SU/SuperSU, and you need custom recovery to do that. And for that, you need an unlocked bootloader, which for your device (Verizon version M8) requires s-off.
Or there is the kingroot method, which has some mixed results.
In any case, locked bootloader is good. Since my recommendation would be to RUU to full stock image, and see if that fixes your reboot problem. If not, then you are probably correct that its a hardware issue.
You can get the RUUs from here: https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
Not only will this get you on a full stock image (which if its a software problem, will fix it) but you can get to a more updated version (yours is really outdated).
You may need to find and flash the Marshmallow 6.21.605.3 firmware (not sure where to find that, offhand), before you can falsh the Marshmallow RUU. But otherwise, you can certainly flash the Lollipop RUU.
---------- Post added at 02:26 PM ---------- Previous post was at 02:22 PM ----------
Maybe its not actually rebooting, then; but doing something like just rebooting the Android shell? But that would be interesting, and not something I've seen before.
Click to expand...
Click to collapse
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app. I did try using something that came from the HTC website (RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
did you read the post you quoted ?
redpoint73 said clearly what you need and where to find
you used a different RUU and it will not accepted by your device ( in red above )
carljames0603 said:
Sorry, app as the wrong word. I tried several different methods but none was an actual app.
Click to expand...
Click to collapse
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
carljames0603 said:
(RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4), but the phone would crash every time. It said to use the program while it was on bootloader, but I don't think I did it write because it still couldn't find the phone via USB.
Click to expand...
Click to collapse
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
redpoint73 said:
Complete lack of correct terminology or any meaningful details, means you haven't provided any actual information on what "methods" you tried to root. You say you tried several different methods, but don't provide any information on what those were. You say an SU app, when you don't mean an SU app (SU zip? SuperSU zip? - which is not the same).
Further, you posted that you "downloading the SU app as prescribed in the site". What website? How are we supposed to have any idea what you are talking about? Please understand, that your posts are vague to the point, that they don't actually provide any real information.
If you want proper help on this website, in general, you need to be specific, provide proper details, and user the right terminology.
As the previous response indicated, this isn't the right RUU for your device. Why would you try to use this? Especially since the proper RUU for your Verizon version M8 was already provided in one of my previous responses? It seems you are just guessing around for solutions (which is a recipe for disaster). You have no reason to think the RUU you listed would work on your device. The version number is all wrong, and it says Brightstar US (which is the US Developer's Edition of the M8). It isn't intended for your device, won't work, and if you flashed it successfully, it would cause your phone's SIM to stop working (radio brick - possibly permanent).
Click to expand...
Click to collapse
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
carljames0603 said:
Alright, clearly I'm not knowledgeable in this type of repair. I apologize for using the wrong terminology, I'm scatter brained and names often elude me. Yes, I apparently used the wrong program to flash my ROM, either way it didn't work. In the end it doesn't matter, I'm throwing in the towel and getting a new phone. Go ahead and delete this thread as I won't be using this forum anymore. You're a ****.
Click to expand...
Click to collapse
That's unfortunate, as your issue is probably completely fixable. All you need to do is follow the instructions already provided. Myself and others have taken our time, at no benefit to ourselves, in order to try to help you and others.
Any critique given by me was not mean to insult or attack, and if you read my post there is nothing in there that constitutes a personal attack or flaming (I even said "please") - while you on the other hand can't claim such a statement to be true. A constructive criticism of your posts is not the same as attacking a person (which you did). The intent was for us to obtain the proper information so that we can better understand what you did, in order to help; and hopefully to improve the quality of your subsequent posts (but that didn't happen).
You can try to learn from your mistakes and expand your knowledge; or you can complain and continue to be ignorant. Your choice.
Related
Hello,
I've noticed that my volume buttons have pretty much stopped working. I don't think it's ROM related, I'm on tmcode's AOKP rc2 ROM and tried going back to CM10 stable and the problem was still there.
Sometimes they'll work randomly, but they're pretty much a write off it seems. My phone is under a year old purchased from Bell.
I've unlocked, rooted the phone, flashed CWM and have flashed numerous ROMS.
I'd like to try and see if they'll give me a replacement, or fix it or whatever before I get a new phone, which most certainly won't be an LG phone, too bad about the Nexus 4...
What's the easiest way to bring the phone back to a stock state? Do you think if I just flash Bell's ICS ROM it'll be enough?
Thanks
you haven't given us much info... my p930 works fine (edit spelling) on cm10 stable... if yours still aren't working i'm guessing one of two things.
1. maybe your rom flashing procedure is lacking... ? are you doing proper data wipes before flashing new roms?
2. did you jolt your phone? if you smashed your phone from the side the volume buttons are on its easily the contacts could have been damaged.
either way i think if your flash count is that high your warranty is probably useless, unless there is some way to hide all those custom roms you flashed but there isn't as far as i know.
you can only hope your problem can be fixed by doing a proper wipe... just another thought... have you tried restoring a backup from CWM from before you experienced the problem? this should confirm weather it is a hardware or software issue.
KronicSkillz said:
you haven't given us much info... my p930 works fine (edit spelling) on cm10 stable... if yours still aren't working i'm guessing one of two things.
1. maybe your rom flashing procedure is lacking... ? are you doing proper data wipes before flashing new roms?
2. did you jolt your phone? if you smashed your phone from the side the volume buttons are on its easily the contacts could have been damaged.
either way i think if your flash count is that high your warranty is probably useless, unless there is some way to hide all those custom roms you flashed but there isn't as far as i know.
you can only hope your problem can be fixed by doing a proper wipe... just another thought... have you tried restoring a backup from CWM from before you experienced the problem? this should confirm weather it is a hardware or software issue.
Click to expand...
Click to collapse
What do you mean "flash count is that high?" I mean, if they really care about that, just update through the LG updater tool and they would never know you've been flashing all sorts of custom ROMs.. Which, if you think it MIGHT be a software problem, that might not hurt anyway; but I doubt it's software related..
lordcheeto03 said:
What do you mean "flash count is that high?" I mean, if they really care about that, just update through the LG updater tool and they would never know you've been flashing all sorts of custom ROMs.. Which, if you think it MIGHT be a software problem, that might not hurt anyway; but I doubt it's software related..
Click to expand...
Click to collapse
someone told me there was something can counts rom installs or something, they called it a flash count i'm trying to find the thread i read it on... it might be completely wrong
KronicSkillz said:
someone told me there was something can counts rom installs or something, they called it a flash count i'm trying to find the thread i read it on... it might be completely wrong
Click to expand...
Click to collapse
I see what you're talking about now. From what I can tell, it's on Samsung devices; I can't find any other references to it on any other brand... not saying that it isn't on anything else, but Samsung appears to not like people having full control of their device.
I don't think it's a software issue, I'm pretty sure it's hardware.
I know to do a full wipe when flashing between different ROMs.
My phones been dropped a couple times, nothing drastic though, that could have done it maybe. I've got a TPU (sp?) case on the phone.
What is the easiest way to bring the phone back to a stock state? LG GB/ICS ROM, un-rooted?
Thanks again
Sent from my LG-P930 using xda app-developers app
RealyPssd said:
I don't think it's a software issue, I'm pretty sure it's hardware.
I know to do a full wipe when flashing between different ROMs.
My phones been dropped a couple times, nothing drastic though, that could have done it maybe. I've got a TPU (sp?) case on the phone.
What is the easiest way to bring the phone back to a stock state? LG GB/ICS ROM, un-rooted?
Thanks again
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
You can try running the official LG update tool; I'm not sure if that will work without doing anything else... I KNOW it works if you flash v18f and then update with the official software. Basically, run through steps 1-5 of this guide: http://forum.xda-developers.com/showthread.php?t=2044645 and instead of doing anything after all that, just start the official update software and update to Official ICS.
" just start the official update software and update to Official ICS."
I'm using the Bell phone unlocked on Rogers, will I still be able to update to the official ICS ROM?
RealyPssd said:
" just start the official update software and update to Official ICS."
From within the phone it self? Or is it an application I download and run from my PC?
I'm using the Bell phone unlocked on Rogers, will I still be able to update to the official ICS ROM?
Click to expand...
Click to collapse
http://www.lg.com/us/support-mobile/lg-P930#manuals
B2CAppsetup.exe is the app you'll need.
pretty sure by official lg update software he's talking about the tool you run on your pc that autoupdates your phone.
http://www.lg.com/ca_en/support/mobile-support
is where you would find the tool, i'm not 100% positive on this more like 99% if you want confirmation you should wait for him to verify, but i know this is the official lg update tool.
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
if you blocked the lg site from your hosts file like the (*edit* un) bricking guide tells you to, you'll have to remove that line from your hosts file (127.0.0.1 csmg.lgmobile.com) and flushdns in order to communicate with the lg servers again. just in case you run into this, i'll try to have your answer posted before you can ask the question
to flush dns open the run prompt, type cmd, hit enter, type ipconfig /flushdns
you should get a success message this has refreshed your dns and you should be able to communicate with csmg.lgmobile.com again.
---------- Post added at 06:42 PM ---------- Previous post was at 06:37 PM ----------
as per your 2nd question, i'm pretty sure you'll end up with A T&T but im not positive. however the at&t software will work if you enter your carriers APN settings, if you didn't write them down you can get them with a simple google search, go into mobile network settings on your phone select apn, then push the menu button and push new, then enter all your apn settings and your data should connect in a jiffy.
KronicSkillz said:
pretty sure by official lg update software he's talking about the tool you run on your pc that autoupdates your phone.
http://www.lg.com/ca_en/support/mobile-support
is where you would find the tool, i'm not 100% positive on this more like 99% if you want confirmation you should wait for him to verify, but i know this is the official lg update tool.
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
if you blocked the lg site from your hosts file like the (*edit* un) bricking guide tells you to, you'll have to remove that line from your hosts file (127.0.0.1 csmg.lgmobile.com) and flushdns in order to communicate with the lg servers again. just in case you run into this, i'll try to have your answer posted before you can ask the question
to flush dns open the run prompt, type cmd, hit enter, type ipconfig /flushdns
you should get a success message this has refreshed your dns and you should be able to communicate with csmg.lgmobile.com again.
---------- Post added at 06:42 PM ---------- Previous post was at 06:37 PM ----------
as per your 2nd question, i'm pretty sure you'll end up with A T&T but im not positive. however the at&t software will work if you enter your carriers APN settings, if you didn't write them down you can get them with a simple google search, go into mobile network settings on your phone select apn, then push the menu button and push new, then enter all your apn settings and your data should connect in a jiffy.
Click to expand...
Click to collapse
Yeah, the official update tool. That's the one I'm talking about; both links end up going to the same program - B2CAppSetup.exe
Good point on the hosts file, that's pretty important.
thank you just trying to him this guy get his phone going
Alright, once I find a cheapo phone to use while my Nitro HD / Optimus LTE is being repaired, I'll give this a go.
I just want to bring it back to stock state to remove root so they won't deny my warranty.
I remembered after I posted about the "B2CAppSetup.exe " program on LG's site.
My hosts file is untoched, I'm on a new install of Windows 8, I un-bricked a few months ago.
Thanks again for all the help.
I can't really, reliably, enter recovery any more...
I might try flashing the v20f Bell ROM via ROM manager and then try unrooting with super one click.
I do still have the first CWM backup I made of the stock GB ROM as well that I could restore maybe in ROM manager.
Sent from my LG-P930 using xda app-developers app
So I flashed the original GB CWM / Nandroid backup I had made, then I tried un-rooting with SuperOneClick, but for some reason it wouldn't work.
So I used the LG software and updated to the official ICS release, Bell version, and the now the phone is un-rooted.
Time to send it off to hopefully get fixed.. what are the chances that I'll get my actual handset back? I've unlocked it, I'm betting I don't get mine back, but a locked one...
Thanks again for all the help
first of all you dont want yours back, the volume button issue is probably hardware, unless you flashed the wrong rom or a corrupted wrong or something. secondly if you updated to stock ics, your phone is already has a relocked bootloader, you should be so lucky as to get a brand new phone that you can unbrick in an hour...
*edit* unless there is some new security they are putting on the new ones but i haven't heard of such, it has always seemed to me they only implement security to the point where it will stop an unknowledgeable person from breaking the phone. the amount of software "leaks" suggest to me they don't really care if people that know what they are doing mod the phones. having said that they still won't replace a phone they know has been modded, for valid reasons, they shouldn't be responsible for things they didn't do to the phone.
So I got my handset back and the volume buttons have been fixed.
To get root and CWM recovery back is it easiest to just follow an unbrick guide?
Hello there
I wanna root my HTC one m8, But i cant find fast boot in power setting...
Anybody can help me on this....
Why would you need that ?
Mr Hofs said:
Why would you need that ?
Click to expand...
Click to collapse
I want to root my m8, all tutorial ask untick fast boot....any help to root m8
This some tutorial I watch
https://m.youtube.com/watch?v=FOaRQoJWWDw
poje84 said:
I want to root my m8, all tutorial ask untick fast boot....any help to root m8
This some tutorial I watch
https://m.youtube.com/watch?v=FOaRQoJWWDw
Click to expand...
Click to collapse
don't watch video's, rather take a good guide here from XDA ! learn adb/fastboot commands and use them wise......if you don't know what you are doing stop it and read up first and full understand what you want to do.
hint :
ADB reboot bootloader
Mr Hofs said:
don't watch video's, rather take a good guide here from XDA ! learn adb/fastboot commands and use them wise......if you don't know what you are doing stop it and read up first and full understand what you want to do.
hint :
ADB reboot bootloader
Click to expand...
Click to collapse
Thanks for ur advice bro,anything I need I will post in this post
Fast boot has been removed in Lollipop so if you're running that it won't be there
EddyOS said:
Fast boot has been removed in Lollipop so if you're running that it won't be there
Click to expand...
Click to collapse
Yes mine is lollipop,so is it still can be root with the same method or I need to wait???
poje84 said:
Yes mine is lollipop,so is it still can be root with the same method or I need to wait???
Click to expand...
Click to collapse
1. Flash TWRP
2. Flash SuperSU ZIP
3. Done
Unticking the "Fast boot" option was a bit unnecessary even before.
Unticking it just prevented folks from getting confused why they couldn't get into bootloader from a "Power off" condition (which with "Fast boot" is really not a true power off, but a deep sleep mode).
If you used any other method, like selecting "Restart" after holding the power button (which is a true reboot) or holding down the Power + Vol up to reboot; those always worked to enter bootloader (by pressing vol down while rebooting).
For all the guides that said to untick "Fast boot" I always just left it on, since I preferred it that way.
---------- Post added at 01:45 PM ---------- Previous post was at 01:45 PM ----------
EddyOS said:
Fast boot has been removed in Lollipop so if you're running that it won't be there
Click to expand...
Click to collapse
Just noticed myself today, that the option was removed. LP boots pretty speedy anyway!
Need help guys... How to root my m8 phone.. Its lolipop version. Help me fast
Ce_dric said:
Need help guys... How to root my m8 phone.. Its lolipop version. Help me fast
Click to expand...
Click to collapse
Search for the superuser.zip from chain fire and flash it in the custom recovery.....
Please do it fast !!!
This is the most easy thing to find out for yourself on how to do it ...... seriously
Mr Hofs said:
Search for the superuser.zip from chain fire and flash it in the custom recovery.....
Please do it fast !!!
This is the most easy thing to find out for yourself on how to do it ...... seriously
Click to expand...
Click to collapse
Bro can we be friend in Facebook.. I am going root first time so I'm confused.. Give me ur fb id
Ce_dric said:
Bro can we be friend in Facebook.. I am going root first time so I'm confused.. Give me ur fb id
Click to expand...
Click to collapse
Uh no way mate. FB is for my friends not for people i do not know. Sorry.
1: unlock the bootloader
2: flash or boot TWRP custom recovery
3: CREATE A FULL NANDROID BACKUP
4: flash superuser.zip to gain root access
Done
Have a read here. Many people don't want to invest in reading carefully but want to be spoon fed ...... got to do some homework buddy.
Restore!
poje84 said:
Hello there
I wanna root my HTC one m8, But i cant find fast boot in power setting...
Anybody can help me on this....
Click to expand...
Click to collapse
In the last update (lollipop) the fast boot option is disabled. So all you can do is backup your stuff and factory reset your phone so it will go back to the previous update where fast boot option is available.
eam55028 said:
In the last update (lollipop) the fast boot option is disabled. So all you can do is backup your stuff and factory reset your phone so it will go back to the previous update where fast boot option is available.
Click to expand...
Click to collapse
You do realize the post you responded to is a year and a half old, correct?
xunholyx said:
You do realize the post you responded to is a year and a half old, correct?
Click to expand...
Click to collapse
Absolutely, but i just came across a spare phone to root which turns out to be an m8 with 6.0.
eam55028 said:
In the last update (lollipop) the fast boot option is disabled. So all you can do is backup your stuff and factory reset your phone so it will go back to the previous update where fast boot option is available.
Click to expand...
Click to collapse
This information is false, for more reason that one (see below). If you bothered to read a thread, I already explained it above in Post #9.
1) The only thing the "fast boot" power option (in Settings) prevented, was going to bootloader from a "power off" condition, as in this case, the phone isn't truly powered off (just a deep sleep state). But you can still get to booloader with a REBOOT, which is always a true reboot; even with "fast boot" power setting enabled.
2) With the "fast boot" power option gone, Item 1 above is irrelevant. The absence of this option in fact makes it easier to get to bootloader, not harder. This is not related to the Android fastboot/adb interface, if that is part of the confusion (as the name is practically the same).
3) Your advice about doing a factory reset is false, as a factory reset does not return you to a former OS version (despite somewhat popular misconception). All factory reset does, is delete user data. Plus, what you advise is completely unnecessary due to Item 2 above. Users on LP or MM are free to get into bootloader, unlock bootloader via HTCDev.com and root; without returning to any older OS version (which is actually impossible without root and/or s-off).
redpoint73 said:
This information is false, for more reason that one (see below). If you bothered to read a thread, I already explained it above in Post #9.
1) The only thing the "fast boot" power option (in Settings) prevented, was going to bootloader from a "power off" condition, as in this case, the phone isn't truly powered off (just a deep sleep state). But you can still get to booloader with a REBOOT, which is always a true reboot; even with "fast boot" power setting enabled.
2) With the "fast boot" power option gone, Item 1 above is irrelevant. The absence of this option in fact makes it easier to get to bootloader, not harder. This is not related to the Android fastboot/adb interface, if that is part of the confusion (as the name is practically the same).
3) Your advice about doing a factory reset is false, as a factory reset does not return you to a former OS version (despite somewhat popular misconception). All factory reset does, is delete user data. Plus, what you advise is completely unnecessary due to Item 2 above. Users on LP or MM are free to get into bootloader, unlock bootloader via HTCDev.com and root; without returning to any older OS version (which is actually impossible without root and/or s-off).
Click to expand...
Click to collapse
LOL! I never even read the post. I just saw how dead the thread was
xunholyx said:
LOL! I never even read the post. I just saw how dead the thread was
Click to expand...
Click to collapse
Fully agree. But Post #14 was so completely incorrect, that I felt the need to respond and prevent possible spread of misinformation.
Ce_dric said:
Need help guys... How to root my m8 phone.. Its lolipop version. Help me fast
Click to expand...
Click to collapse
http://theroot.ninja/
Okay, I'm giving up, I need someone to help me.
I was given my neighbours HTC One M9. It was working just fine. After he gave it to me, first thing I did was a factory reset because he didn't delete anything.
After that, the problems began. When I boot up the phone, even directly after resetting and even before the setup, I get an error "Google App stopped working". And after that, all couple of seconds another "com.google.process.gapps stopped working".
I tried several of the fixes out there on the web, but it didn't go away. I did another factory reset, and again even when I setup the phone I get those errors.
There is still Android 6.0 on the phone, so I wanted to update to 7.1
During install, I got the red triangle screen, on both attemps. Well, f*ck.
So, I went on to install a new OS. Never did this before, so I though this is a good chance to learn some more about Android.
It just got even more strange. When I'm in the bootloader, I saw
***Software status: Modified***
S-ON
LOCKED
***Security Warning***
Especially the modified software was very strange, since my neighbour has neither a clue nor any interested of fiddling with phones.
When I tried to go into Download Mode, it said "failed to boot into download mode".
Recovery mode worked just fine.
Therefore, I couldn't do anything to install a new OS.
Next I bought the Sunshine App and S-OFFd my phone, which worked just fine.
Now I'm S-OFF, unlocked and the Security Warning has gone. The software is apparently still modified.
But when I go into download mode, I get the black screen with the silver logo and red text for a while, then the phone proceeds to boot normally.
What the f*uck? I'm just out of idead what to do now. Please don't let it be a dead nand... it's such a nice phone, and apart from the google app errors, it works perfectly. I used it for some surfing around today and it works really well. I can't imagine it being broken.
Thanks for your help!
What variant do you have? Firmware version?
side_flip15 said:
What variant do you have? Firmware version?
Click to expand...
Click to collapse
Firmware is 3.35.166.12
I don't know exactly about the variant, this is what the IMEI checker says:
SKU , VF , German , CHE , HTC , CH , Swisscom , Bootloader Lock , Dark Gunmetal/Dark Gunmetal , w/o SIM Lock , HIMA#UHL-D1
I have a bug report of the gapps-Error. Would that be helpful?
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Flippy498 said:
I have some bad news for you:
According to everything that you describe in the opening post it's the dead nand issue. There's nothing you can do. And if you send the phone to HTC they will change the motherboard which means that you have to buy sunshine, again, after they send the phone back to you.
Click to expand...
Click to collapse
Flippy498 said:
It's the combination of several things that make me think it's a dead nand:
The security warning indicates that there is no OS installed. If that happened without manually deleting the OS via a custom recovery like TWRP then chances are high that the nand died.
The software status is modified although the phone is locked and S-ON. The only other explanation for this combination would be that the owner failed while using one of the 100% stock guides that convert S-OFF back to S-ON, Unlocked back to Locked and modified back to original. However, the dead nand issue is quite common during the recent months and the guides are hidden somewhere in the Genereal section (in other words: not located on the first page). Therefore, I think that chances are higher that it's the dead nand issue.
Last but not least: The black download mode error screen in combination with the other two symptoms.
Did you report about your tries to revive your phone somewhere here on xda? Do you have a link? What kind of symptoms did you face aside from the black error screen? Has your phone been S-ON or S-OFF?
I didn't have to revive it, except that Google-error it works beautifully. That' broken download mode the only symptom I have. The phone is (meanwhile after Sunshine) S-OFF
If you really faced a dead nand issue and could repair your phone by your own that would be a game-changing and I could finally overhaul the FAQ of the ReadMe thread. However, discussions like the one that starts with this post make me think that you might have faced a different problem with your download mode since it really looks like the dead nand isn't fixable without changing the hardware.
Click to expand...
Click to collapse
Well, there are two things that leave me hoping it's not a dead nand.
• Apart from that com.google.process.gapps-error, it works like a charm. No crashes, no sudden reboots. I really can't imagine a broken part of a motherboard making no trouble, wouldn't that render the part
useless? And is that Google-App Error really relatable?
• After letting the Sunshine App do its job, I don't get an error message in the download mode (well, it just boots normally after a while), the security warning has gone as well. Only the modified software is
suspicious.
side_flip15 said:
@Flippy498 Is the "failed to boot into download mode"? error a sign of dead nand? This happened to me before. I flashed hosd.img via bootloader to fix this. Still using my M9.
Click to expand...
Click to collapse
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue.
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Instructions are linked in the FAQ of the ReadMe thread. They're the solution for the blue download mode issue. Great, thanks!
The thing is that the download mode can't just break without either you actively manipulating it or the hardware of the phone dying. The same applies to that security warning. Either you manually delete the OS or the hardware fails and the phone isn't able to read the installed OS correctly, anymore. Therefore, I wouldn't put my hopes too high if I were you. Of course I could be wrong but I've read a lot of reports of dead nand phones since last year's summer and my feeling tells me that this is another one.
Click to expand...
Click to collapse
Yes, I know. Maybe I just don't want to accept that fact to keep my motivation to try to save the phone...
So what my optimism suspects is that somewhere deep in the firmware there is something corrupted. That leaves the System modified and the Google app confused.
After all, recovery mode works just fine. If you check what other people experience with a dead nand, it's got to do with sudden reboots, bootloops, failed download AND recovery modes et cetera.
As a sidenote: You're the first user that tried to S-OFF/successfully S-OFFed his phone after such errors occurred since sunshine can't unlock the bootloader on firmware 4.x and hasn't been able to do so on older firmware versions when the issue appeared the first time. Therefore, I don't know which influence sunshine has on the whole situation.
Click to expand...
Click to collapse
A little more hope rised in me...
sechsgangschakter said:
I've heard of that as well. I didn't really find any tutorial on that and I'm a bit afraid to experiment with that. Do you mind sharing how you achieved that?
Click to expand...
Click to collapse
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
SAME HERE PROBLEM PLEASE HELP
I HAVE HTC ONE M9 OPJA100 JUST GO ON LOCKED SCREEN WHEN REBOOT TO BOOTLOADER ITS RESTART AGAIN EVEN NOT GO DOWNLOAD MODE OR RECOVERY MODE.
I WAS JUST MAKE ROOT THEN ITS STUCK ON LOGO
NOT GO FASTBOOT MODE TO CHECK CID OR FIRMWARE
WHAT I DO ?????
ITS LOCKED
S-ON ALSO
side_flip15 said:
You can try this...
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Code:
fastboot flash hosd hosd.img
then try to reboot to download mode. If it does not work, try other firmware.zip but should be in the same build number at least X.XX.
Click to expand...
Click to collapse
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
sechsgangschakter said:
THANK YOU!!!!
It finally works!
Edit: I installed resurrection Remix. Working perfectly, I really don't think there is anything dead in that phone. It's great, thank you for your help!
Click to expand...
Click to collapse
Glad I helped you:highfive:
side_flip15 said:
Get the firmware.zip matching your current firmware @Flippy498 's thread here. Links are in the spreadsheet in post #2. Extract the hosd.img from the zip and flash in bootloader mode .
Click to expand...
Click to collapse
Just for the record, that's not my thread. It's owned by Sneakyghost.
@sechsgangchakter: I'm glad to hear that your phone is working, again.
Flippy498 said:
Just for the record, that's not my thread. It's owned by Sneakyghost.
Click to expand...
Click to collapse
Oh god! Sorry
Credits to @Sneakyghost :highfive:
Hello, I am having a very similar issue. I am looking for the hosd.img file for Verizon. I dont see it at https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml. Please help. Thanks
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Flippy498 said:
You won't find any CDMA files in that spreadsheet because the xda thread that sheet belongs to only supports GSM devices and clearly states that it'll never support CDMA.
Click to expand...
Click to collapse
So no one knows of one available for Verizon m9? What would happen if I used a GSM one?
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Flippy498 said:
You would probably damage your phone unrecoverably. GSM and CDMA are not compatible with each other due to the different partition layouts.
However, why don't you extract the needed file from a RUU that matches your current firmware version? That's how those firmware packs in the linked thread got made, as well. There's a thread with a RUU extraction tool linked in the RUU section of the ReadMe thread.
Sent from my HTC One S using XDA Labs
Click to expand...
Click to collapse
Good idea, ill give that a try. Thanks
This was posted in the all Note 8 forum claiming it is an engineering combo. Has anyone tried it to verify it is actually an engineer boot?
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=12507
The link above requires a paid membership but a file with the same name is available from androidfilehost, can't verify the md5 though.
https://www.androidfilehost.com/?w=files&flid=213338
From what i gather from the firmware this is the us firmware for sprint, which in theory should work for verizon, however not worth bricking to find out.
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
have you checked the sprint note 8 links??
I just ordered my vzw n8 today for tomorrow delivery. However im not smart enough nor brave enough attempt anything on it with a random rouge firmware, but you can bet I will follow this thread. Here's to wishful thinking. : )
~SG
Also being discussed here
https://forum.xda-developers.com/ga...ssion-snapdragon-note-8-models-t3670091/page4
Is it possible to use the mentioned firmware for some carrier switching flashing on note 8, just like what they did to S8 in this thread: https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
I can confirm this Combination firmware is legit, or at least the one from the AFH link. You must do a factory reset after flash or the phone will not boot, likely due to encryption.
This kernel is permissive, and it does have ADB enabled by default.
bangbusdriver said:
I can confirm this Combination firmware is legit, or at least the one from the AFH link. You must do a factory reset after flash or the phone will not boot, likely due to encryption.
This kernel is permissive, and it does have ADB enabled by default.
Click to expand...
Click to collapse
When you say likely due to encryption, do you mean encryption already present on the phone or does flashing this encrypt it? I don't believe my phone is encrypted as I haven't enabled any secure unlock system. Or do you mean bootloader encryption. Unless I'm mistaken the phone isn't encrypted until after a secure unlock option is enabled.
I really don't want to go through my phone setup again when root isn't available yet. This just seems like a first step to enable flashing of a rooted firmware.
jellyhead said:
When you say likely due to encryption, do you mean encryption already present on the phone or does flashing this encrypt it? I don't believe my phone is encrypted as I haven't enabled any secure unlock system. Or do you mean bootloader encryption. Unless I'm mistaken the phone isn't encrypted until after a secure unlock option is enabled.
I really don't want to go through my phone setup again when root isn't available yet. This just seems like a first step to enable flashing of a rooted firmware.
Click to expand...
Click to collapse
Since android 6.0, encryption of /userdata is supposed to have been standard. My understanding is that the partition is encrypted at first boot. It's probably encrypted with your personal key after you set a secure lock setting.
Regardless, won't boot without factory reset. You will lose your data if you want to use this firmware, but simply flashing it doesn't format /userdata. I can't say whether or not flashing back to stock triggers automatic factory reset, but sometimes it does.
I did confirm earlier today thought that you can't only flash the kernel. Phone won't boot, regardless of factory reset. Nor will it work with abl.mbn(I assume android boot loader), and xbl ( download mode?) But, the kernel is not fully permissive anyway. /system cannot be remounted rw, and I can't manipulate the files in /dev/block either.
---------- Post added at 10:57 PM ---------- Previous post was at 10:54 PM ----------
lilila said:
Is it possible to use the mentioned firmware for some carrier switching flashing on note 8, just like what they did to S8 in this thread: https://forum.xda-developers.com/galaxy-s8/how-to/snap-guide-flashing-standard-fw-carrier-t3625817
Click to expand...
Click to collapse
I'd like to try that, but insofar I noticed in Download mode it says the carrier is ATT. I think this might be set in the /efs but I could be wrong. If so, root can help. For the record, Verizon is the same model N950U as ATT.
Greetings all,
Been a couple years since I've visited these boards, I just picked up the note a couple days back. Am I reading this correctly that we can actually flash the verizon model with the engineering firmware to a more permissive setup without brick, or am I just exceptionally out of date and reading this wrong?
The.Jericho.Initiative said:
Greetings all,
Been a couple years since I've visited these boards, I just picked up the note a couple days back. Am I reading this correctly that we can actually flash the verizon model with the engineering firmware to a more permissive setup without brick, or am I just exceptionally out of date and reading this wrong?
Click to expand...
Click to collapse
Correct, its safe to flash the engineering firmware
hmm. interesting. now I just need to understand (or make sure I understand correctly) that/what is gained by using this firmware? Is root or bootloader unlocked gained by flashing this firmware? I would think this would be a hot topic and more people to chime in. Is there another thread somewhere where people are dissecting this firmware in more detail (based on what IS known)? Sorry, im just trying to simplify the subject. : )
~SG
I have successfully used this for carrier switching...Carrier Switching Guide coming soon....
SomeGuy2008 said:
hmm. interesting. now I just need to understand (or make sure I understand correctly) that/what is gained by using this firmware? Is root or bootloader unlocked gained by flashing this firmware? I would think this would be a hot topic and more people to chime in. Is there another thread somewhere where people are dissecting this firmware in more detail (based on what IS known)? Sorry, im just trying to simplify the subject. : )
~SG
Click to expand...
Click to collapse
THIS!! ^^
If this is true then I am trading in my Note 4 asap!
Though I have that sinking feeling in my gut that it may be too good to be true. As you've said, I too really feel like this info would have spread like wildfire if this was the case. I hope I am wrong!
Edit: I read a little more into it and it's pretty much just a carrier unlock. Not bootloader... :/
SomeGuy2008 said:
hmm. interesting. now I just need to understand (or make sure I understand correctly) that/what is gained by using this firmware? Is root or bootloader unlocked gained by flashing this firmware? I would think this would be a hot topic and more people to chime in. Is there another thread somewhere where people are dissecting this firmware in more detail (based on what IS known)? Sorry, im just trying to simplify the subject. : )
~SG
Click to expand...
Click to collapse
Root is now live
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
jellyhead said:
Root is now live
https://forum.xda-developers.com/galaxy-note-8/development/root-samfail-galaxy-note8-t3685340
Click to expand...
Click to collapse
Thanks for the info. Damit, I have everything working just right in a non rooted fashion. And to be honest I kinda like it that way. But then again I do miss the typical root advantages.
~SG
I'll be waiting to see if the 80% battery issue gets solved.
I read that part. Yuk. That sucks. Ima hold out for a bit while it bakes in the oven a little longer.
I'm stoked that it does not trip knox...
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
So i checked on a friends stock m9 and indeed it has the 4.47 update.
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
SO LONG FOR GOOD ADVICE FROM XDA.
BOOOO.
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
myphonesbetter said:
So i was trying to install the latest nougat roms and realized i need to be on 4.xx for them.
I am on 3.xx
Click to expand...
Click to collapse
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
myphonesbetter said:
So i tried to update via the latest ruu from htc.
http://www.htc.com/us/support/rom-downloads.html
Did not work.
Then i realized that the rom was for a developers edition phone which mine is not.
So i downloaded the latest 3.xx rom. for the non developer phone.
After i downloaded it, I realized it was the same 4.xx ruu that i downloaded before. So i thought my mistake.
Go back and download AGAIN and yup, the link they provide in the "details and instuctions" section for the 3.xx rom is definitely for the 4.xx ruu.
When i click the download link without going into details. the link does not work.
Click to expand...
Click to collapse
HTC is a bit lazy in regard to updating their webpage. You're always only able to download the latest RUU. However, you don't mention which variant you own. There is more than just one non-dev edition variant. Nevermind, you mentioned it in one if your following posts.
myphonesbetter said:
Weird thing. on this page http://www.htc.com/us/support/updates.aspx
They do not specify developer edition.
So now the question is. IS 4.xx the latest update for all t-mo m9 phones and i am just having a problem installing.
Or do i need to find the 3.xx rom from a different source.
Click to expand...
Click to collapse
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
myphonesbetter said:
So i checked on a friends stock m9 and indeed it has the 4.47 update.
Click to expand...
Click to collapse
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant.
myphonesbetter said:
So i guess i am just doing something wrong. I am rooted but i never chose the option in twrp to modify files.
Click to expand...
Click to collapse
It's possible to break the OTA-update function by modifying the system via a root file explorer, as well.
myphonesbetter said:
I can connect to the ruu in download mode. I tells me the correct rom that i have on the phone and offers to update. Once i choose update it seems to work fine. Reboots my phone then gives me error 123.
Click to expand...
Click to collapse
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
myphonesbetter said:
I cant seem to find a zip for it. Or a copy of the older ruu.
If anybody can point me in the direction of a database somewhere that would be super helpful. I know the mods used to keep them stickied at the top.
Click to expand...
Click to collapse
The "database" is still stickied (in not only one but two subforums of the M9 section - the general and the q&a section). Therefore, I'm a bit surprised that you weren't able to find what you're looking for. In addition the thread I'm talking about is not only a database, it even contains all information you would have needed for solving your issues, already.
myphonesbetter said:
I do have a ruu and zip on my computer from a couple years ago that i will try too.
Click to expand...
Click to collapse
If the RUU is older than your current firmware then you won't be able to use it.
myphonesbetter said:
Tried to flash the last ruu i flashed before. got error 155 and now am stuck in flashing mode. With a half flashed phone. no way to reset it. 10 second power button does not work. cant pull the battery as the ruu advises me to do.
Guess im waiting for the phone to die from 100%
Click to expand...
Click to collapse
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down up and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
myphonesbetter said:
I think the problem is simple and something i totally forgot in the last couple years.
I NEED TO RE LOCK MY BOOTLOADER. but who knows. apparently its just me on here.
Click to expand...
Click to collapse
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Flippy498 said:
Please don't forget that this is a forum and not a support-hotline/-chat where people get payed for replying immediately. Most of us are doing this as their hobby and aren't able to be online 24/7. It might take some time till you get a reply. Especially if you post in a section that shows almost no activity aside from some new questions being asked. Most (former) users have already moved on to other devices due to the age of the M9 and many devs left the development scene due to the end users on xda that became more and more toxic and demanding during the last couple of years.
Click to expand...
Click to collapse
Yah. I get it. Was kind of just shouting to get some attention.
Ive noticed that not just this forum but many other forums that i used to use have lossed a lot of popularity.
I think because facbook groups and things like reddit that cover all subjects.
The problem with those places is that they are so unorganized.
Maybe thats also part of why its become so unorganized here. just what people are used to.
I honestly wasnt expecting actual info. Thank you.
Flippy498 said:
You actually don't need firmware 4.x. Firmware 3.x is compatible with the latest custom roms, as well. They only run "better" on firmware 4.x.
Click to expand...
Click to collapse
Well i was afraid to brick it so i figured out (accidentally) how to update.
Flippy498 said:
Firmware 4.x is the latest version for all SKUs/variants and there won't be any further updates since the M9 reached the EOL stage almost a year ago.
Is that a typo? I only know about firmware 4.27.531.6 for the T-Mobile US variant It's possible to break the OTA-update function by modifying the system via a root file explorer, as well..
Click to expand...
Click to collapse
Yes that was. it is 4.27.
I could not find any older ruu's on their site. Or anywhere for that matter. none with active links at least.
Flippy498 said:
Is that another typo? I'd have expected error 132 since firmware 3.x and 4.x are using different encryption keys. You can't update using a RUU. You need to use the software update function of the system settings.
Click to expand...
Click to collapse
Yes 132. I did not realize that. Do you mean i would need to update via ota? by searching for updates.
Flippy498 said:
If the RUU is older than your current firmware then you won't be able to use it.
Error 155 means that you either try to flash a RUU that is too old or made for a different variant than the one you own. The key combination you're looking for is the power button plus volume down and you need to keep them pressed for about 30 seconds. HTC changed that on one of the devices that came out before the M9. Letting the battery die is a bad idea, though. You'll damage it this way.
Click to expand...
Click to collapse
So i was originally trying to flash the latest frimware 4.27.xxx but i kept getting error 132.
And on the htc website it has 2 sections for ruu's m9 ans m9 developer. So i just figured it was the wrong one.
So i figured i would try the last ruu that i flashed before installing the rom that i ran for almost 2 years (lee droid)
when i flashed that, it got halfway through and gave me error 155. but left my phone in the middle of an update. Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
Well i could not reboot the phone so i just started the recover process. This rebooted my phone a few times then just started flashing the rom. To my surprise it worked.
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Took about 4 hours and 7 updates or so. probably 5 gigs on the data plan but finally it finshed with a 1.1 gig update to 4.27.
Im not sure why the first flash failed or why it worked, but eventually it did work.
Flippy498 said:
No you don't. I can't discourage people enough from relocking this phone's bootloader if the phone is S-ON and not 100% stock and you don't have a RUU at hand that you already used successfully on your phone. HTC's security checks will prevent the device from booting if anything is modified (e.g. TWRP being installed) while the bootloader is locked or relocked. They don't differentiate between "broken" and "custom" files and think that the modified software is broken. Therefore, the checks are trying to prevent the hardware from getting damaged by preventing the device from booting. In addition, if OEM Unlock isn't activated in the developer settings of the currently installed rom then there is no way to re-unlock the phone. That's an FRP (factory reset protection) Google introduced with android 5.1 (which equals firmware 2.x of the M9).
Click to expand...
Click to collapse
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
I was using the last ruu that i had used. but i also flashed a rom and it was a long time in between.
Also i installed the old version of lee droid on 4.27.xxx and it seemed to work fine. I did this on accident though. Flashed the wrong zip. Re-flashed the latest 4.0 and it seems to be working great. Noticing a couple little lags. Might go to the stock rom just rooted and debloated. It seemed to run a little smoother than leedroid for the time i was using it. but i felt like they were trying to extract my stem cells via confusing TOS agreements.
myphonesbetter said:
Apparently the power button is disabled during this process.
it tell you to pull the battery or hold the power button for 10 seconds then try to recover from the boot using the ruu.
[...]
It also re-locked my phone.
After that, now that im stock, i tried to flash the 4.27 ruu. still 132.
So i tried to run the ota's and they worked.
Ive always relocked my htcs before running an ruu. If not then they never seem to work. I dont mind it because it takes about 10 seconds. and i already hae the token. I actually remembered the majority of the commands.
Maybe its causing another problem that i dont know about.
I did see the oem unlock in developer options if that is what you are talking about.
Click to expand...
Click to collapse
The power button isn't disabled. As said in my last post, you need to press the power button and the volume down button for 30 seconds. It's always been like that on the M9 since HTC already changed that on the M7 or M8 (can't tell you which one exactly it was).
Relocking was only needed on HTC phones that are older than the M9. HTC changed that with the M9. And as said in my last post, re-locking the M9 if you don't have a RUU at hand that you already used successfully is more than dangerous due to Google's FRP. You might end with a non-booting non-unlockable phone.
In addition, a relocked dootloader doesn't change the fact, that your phone is missing the needed encryption keys. That's why the 4.x RUU still failed.
However, it's nice to hear that you could solve your problems now. ?
Sent from my HTC One M9 using XDA Labs
Ah, I made a mistake while writing my posts. It's power and volume up. Not power and volume down. :silly: