So, okay, I'd like to start off by saying I messed up. I couldn't read what the thing said, so I clicked the wrong thing, and I'm pretty sure I somehow bricked my htc m8.
So, I was using Hasoon2000's Htc one all in one tool kit, and I was trying to root an m8 I just got. I wnt through all the steps to unlock the bootloader and whatnot, and everything somewhat worked, I couldn't flash TWRP on the phone for whatever reason. So, I put it on an sd card, and was gonna flash it myself. I clicked on "Relock bootloader" Meaning to click on "Boot into Bootloader"(Bad eyesight), and now I have no clue what the hell is going on with the phone.
I restarted the phone, and when it loaded into the os, I couldn't access settings, I couldn't uninstall apps(App not installed even though it was), so, I tried to install the factory os via the all in one tool kit, but now all my phone says is
*** Software status: Modified ***
*** RELOCKED***
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.25.21331147a1.06g
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-
eMMC-boot 2048MB
Jan 12 2015,21:43:09.9093
RUU
And thats it... I have no clue what the hell even happened, and whats going on.
Edit:
I was able to restart the phone and get into some more of the back end stuff, but not much...
It now has
Fastboot, recovery,factory reset,simlock,check smartsd,image crc,show barcode, however, clicking the first 3 takes me to ther fastboot menu(or fastboot usb with it plugged into my win pc), and if I try and factory reset it, it says *** Security Warning ***
Sigh... No clue how to fix it
The good news, is that your can't really brick this device while s-on (which it is), especially with the stuff you've done. It's simply stuck in a state that is not usable to you, that is very likely recoverable.
First off, I highly recommend you ditch the toolkit. This is for a couple reasons: one reason being, the toolkit only acts as a middle man for something you can (and should) know how to do yourself: simple one-line fastboot commands. And as you've seen, the toolkit makes it a little too easy to do something on accident, such as lock the bootloader. Which not only will typically render the phone unable to boot to OS (I'm surprised yours still did at first) as well as wipes all personal data on the phone. This would never happen, if you were doing the fastboot commands by yourself.
Another big reason to avoid the toolkit, it stopped being supported a long time ago, in 2014. Well before HTC stopped supporting this device (2016?). Since the toolkit is so old, it contains outdated versions of TWRP and SuperSU, which will cause a lot of problems for most folks. This includes you, and most likely the reason TWRP (outdated version) did no work for you.
My recommendation:
1) Your firmware is outdated (Lollipop). Since the bootloader is presently locked (relocked, basically the same thing) it is a good time to flash official firmware/RUU and bring your firmware up to Marshmallow. In order to figure out what firmware or RUU is right for your M8 version, we need more info. Do fastboot getvar all, and post the results (delete IMEI and serial number). If you don't know how to use fastboot, it's time to learn. Use xda seach function, and/or Google (although being a bit careful when following random websites outside xda) and learn the basics of fastboot. If you have specific questions, come back and ask. I'll be happy to help with those. But don't intend to give you a step-by-step instructions, for info that is posted in countless places already.
2) Once firmware is updated, unlock the bootloader again. You should be able to use the same unlock bin code as you originally did, to unlock the bootloader. Otherwise, just go through the process at HTCDev.com and get another unlock bin code. Flash the code with fastboot.
3) Once the bootloader is unlocked, flash latest TWRP 3.2.3-1 using fastboot. You can get TWRP from here: https://dl.twrp.me/m8/
4) Make a backup in TWRP of your stock ROM. This way, if you run into any problems rooting (or otherwise, want to reverse the process), you can still revert to stock. To backup the stock ROM, select BACKUP in TWRP, and select system and boot.img to backup. This is a very important step, that many folks (and guides) skip. But to me, it is not only best practice, but just common sense to make a backup and give yourself an "escape plan". I simply never root or make other mods to these devices, without having a backup of the stock ROM.
5) In TWRP, flash current version SuperSU 2.82 from here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
But to be honest, I would suggest Magisk at this point. It is a newer root method than SuperSU. And SuperSU appears to be dead, anyways. Not only is Magisk still being updated and supported, but it seems to work a little more reliably. Plus, Magisk has a ton of cool and useful features, that SuperSU does not. Suggested Magisk version is 18.0: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6) After flashing your root file of choice (SuperSU vs. Magisk), reboot and you should have a usable (and rooted) operating sy system.
redpoint73 said:
The good news, is that your can't really brick this device while s-on (which it is), especially with the stuff you've done. It's simply stuck in a state that is not usable to you, that is very likely recoverable.
First off, I highly recommend you ditch the toolkit. This is for a couple reasons: one reason being, the toolkit only acts as a middle man for something you can (and should) know how to do yourself: simple one-line fastboot commands. And as you've seen, the toolkit makes it a little too easy to do something on accident, such as lock the bootloader. Which not only will typically render the phone unable to boot to OS (I'm surprised yours still did at first) as well as wipes all personal data on the phone. This would never happen, if you were doing the fastboot commands by yourself.
Another big reason to avoid the toolkit, it stopped being supported a long time ago, in 2014. Well before HTC stopped supporting this device (2016?). Since the toolkit is so old, it contains outdated versions of TWRP and SuperSU, which will cause a lot of problems for most folks. This includes you, and most likely the reason TWRP (outdated version) did no work for you.
My recommendation:
1) Your firmware is outdated (Lollipop). Since the bootloader is presently locked (relocked, basically the same thing) it is a good time to flash official firmware/RUU and bring your firmware up to Marshmallow. In order to figure out what firmware or RUU is right for your M8 version, we need more info. Do fastboot getvar all, and post the results (delete IMEI and serial number). If you don't know how to use fastboot, it's time to learn. Use xda seach function, and/or Google (although being a bit careful when following random websites outside xda) and learn the basics of fastboot. If you have specific questions, come back and ask. I'll be happy to help with those. But don't intend to give you a step-by-step instructions, for info that is posted in countless places already.
2) Once firmware is updated, unlock the bootloader again. You should be able to use the same unlock bin code as you originally did, to unlock the bootloader. Otherwise, just go through the process at HTCDev.com and get another unlock bin code. Flash the code with fastboot.
3) Once the bootloader is unlocked, flash latest TWRP 3.2.3-1 using fastboot. You can get TWRP from here: https://dl.twrp.me/m8/
4) Make a backup in TWRP of your stock ROM. This way, if you run into any problems rooting (or otherwise, want to reverse the process), you can still revert to stock. To backup the stock ROM, select BACKUP in TWRP, and select system and boot.img to backup. This is a very important step, that many folks (and guides) skip. But to me, it is not only best practice, but just common sense to make a backup and give yourself an "escape plan". I simply never root or make other mods to these devices, without having a backup of the stock ROM.
5) In TWRP, flash current version SuperSU 2.82 from here: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
But to be honest, I would suggest Magisk at this point. It is a newer root method than SuperSU. And SuperSU appears to be dead, anyways. Not only is Magisk still being updated and supported, but it seems to work a little more reliably. Plus, Magisk has a ton of cool and useful features, that SuperSU does not. Suggested Magisk version is 18.0: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6) After flashing your root file of choice (SuperSU vs. Magisk), reboot and you should have a usable (and rooted) operating sy system.
Click to expand...
Click to collapse
First of all, I'd love to just say thanks for not calling me an idiot or anything, and taking the time to do this! I've rooted htcs before, but nothing this complex. This community seems to be better than most others, and less toxic, or so it seems.
Anyways:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.21331147A1.06G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B16000
cidnum: SASKT001
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dcdaa6e0
hbootpreupdate: 11
gencheckpt: 0
Still working on flashing a rom, I have no clue where to find them, or what a secure, proper download of one looks like, however, I did find one on the forums from here:
https://forum.xda-developers.com/showthread.php?t=2696282
I also got this in cmd as I tried to flash
target reported max download size of 1826418688 bytes
sending 'zip' (1559644 KB)...
OKAY [ 51.325s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
Neku DHack said:
Still working on flashing a rom, I have no clue where to find them, or what a secure, proper download of one looks like
Click to expand...
Click to collapse
Yeah, my intent was to get the fastboot getvar info about your device version (which you have now given), so we can further direct you from there. Figuring it out yourself is not that easy, for a number of reasons. You probably got signature verify fail, since the firmware must be the specific to your device version's CID (carrier ID) or else it will fail by design.
My suggestion would be:
a) Flash firmware fw_6.13.666.7 from here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Using instruction near the bottom of the post.
b) Restore stock TWRP backup (stock ROM) from here: https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Using the instruction in Post #1 of that same thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to Steps 1-9 of that guide (and skip step 3 of that guide).
c) Then you can do steps 4-6 of what I posted in my earlier reply above: https://forum.xda-developers.com/showpost.php?p=78750946&postcount=2
Keep in mind that the TWRP backup (stock ROM) in step "b" above, is not the same as the "firmware" in step "a" above. The firmware in this case, is not a full ROM, but a small file which contains radio, hboot, and some other small partitions, needed to make the ROM work, but does not contain the ROM itself. This is a little confusing I know, but moral of the story, is that you should update both the firmware and the ROM to get the phone working again, than backup and root.
---------- Post added at 09:57 AM ---------- Previous post was at 09:47 AM ----------
Neku DHack said:
First of all, I'd love to just say thanks for not calling me an idiot or anything,
This community seems to be better than most others, and less toxic, or so it seems.
Click to expand...
Click to collapse
Yeah, name calling and belittling folks is not my style. And also against xda's rules of conduct. There are a lot of toxic forums on the internet, and I agree xda is a cut above that; at least most of the time.
We all had to start somewhere with this stuff. And for a device this old, there is a lot of outdated and contradictory info out there. The only reason I understand all this the way I do, is that I've been here on the M8 forum section, since practically the start. And I've learned a lot from other folks in the community; and have benefitted from great resources like ckpv5's thread I linked above.
redpoint73 said:
Yeah, my intent was to get the fastboot getvar info about your device version (which you have now given), so we can further direct you from there. Figuring it out yourself is not that easy, for a number of reasons. You probably got signature verify fail, since the firmware must be the specific to your device version's CID (carrier ID) or else it will fail by design.
My suggestion would be:
a) Flash firmware fw_6.13.666.7 from here: https://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Using instruction near the bottom of the post.
b) Restore stock TWRP backup (stock ROM) from here: https://forum.xda-developers.com/showpost.php?p=60211240&postcount=3
Using the instruction in Post #1 of that same thread: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Only need to Steps 1-9 of that guide (and skip step 3 of that guide).
c) Then you can do steps 4-6 of what I posted in my earlier reply above: https://forum.xda-developers.com/showpost.php?p=78750946&postcount=2
Keep in mind that the TWRP backup (stock ROM) in step "b" above, is not the same as the "firmware" in step "a" above. The firmware in this case, is not a full ROM, but a small file which contains radio, hboot, and some other small partitions, needed to make the ROM work, but does not contain the ROM itself. This is a little confusing I know, but moral of the story, is that you should update both the firmware and the ROM to get the phone working again, than backup and root.
---------- Post added at 09:57 AM ---------- Previous post was at 09:47 AM ----------
Yeah, name calling and belittling folks is not my style. And also against xda's rules of conduct. There are a lot of toxic forums on the internet, and I agree xda is a cut above that; at least most of the time.
We all had to start somewhere with this stuff. And for a device this old, there is a lot of outdated and contradictory info out there. The only reason I understand all this the way I do, is that I've been here on the M8 forum section, since practically the start. And I've learned a lot from other folks in the community; and have benefitted from great resources like ckpv5's thread I linked above.
Click to expand...
Click to collapse
So, I did the first step, and flashed the OS twice because it gave me an error, now its stuck on the white boot screen with the htc o1ne logo in the middle, and its been like that for hours now. gonna wait for the battery to die, and see what happends. Can't hold the power to shut it down.
Edit:So, It died, and now it won't charge, and red/orange light at the top is blinking... the battery logo pops up and says its charging, but it isnt.
Edit 2:Fixed the charging issue
Neku DHack said:
So, I did the first step, and flashed the OS twice because it gave me an error, now its stuck on the white boot screen with the htc o1ne logo in the middle, and its been like that for hours now. gonna wait for the battery to die, and see what happends. Can't hold the power to shut it down.
Edit:So, It died, and now it won't charge, and red/orange light at the top is blinking... the battery logo pops up and says its charging, but it isnt.
Edit 2:Fixed the charging issue
Click to expand...
Click to collapse
Power + vol up will force a reboot, in cases where holding power alone doesn't do it. Or you possibly didn't hold power long enough. In some "stuck" situations, you may have to hold the button(s) for about a minute, before it reboots.
The button combos are hardwired into the device, so they will always work unless the phone is truly bricked.
Also, flashing the firmware twice is normal, as is the error message. So you did the right thing in flashing it again.
redpoint73 said:
Power + vol up will force a reboot, in cases where holding power alone doesn't do it. Or you possibly didn't hold power long enough. In some "stuck" situations, you may have to hold the button(s) for about a minute, before it reboots.
The button combos are hardwired into the device, so they will always work unless the phone is truly bricked.
Also, flashing the firmware twice is normal, as is the error message. So you did the right thing in flashing it again.
Click to expand...
Click to collapse
So, after leaving it for a few days, and trying to reboot it, it got stuck in the boot screen again, so I did the power+vol up, and now its black screened and wont charge... Is it bricked?
Edit:Not bricked, if I hold down every button it flashes the htc boot screen, then it goes to black again
Neku DHack said:
So, after leaving it for a few days, and trying to reboot it, it got stuck in the boot screen again, so I did the power+vol up, and now its black screened and wont charge... Is it bricked?
Edit:Not bricked, if I hold down every button it flashes the htc boot screen, then it goes to black again
Click to expand...
Click to collapse
Try power+vol down.
The phone isn't bricked. I already said, you can't brick this phone doing what you did (trying to flash recovery, root file). Those partitions are separate from the bootloader, which is also protected by s-on (you couldn't overwrite it, even if you wanted to).The fact that the HTC logo screen comes on, also means bootloader is still working properly (no bootloader = dead screen) and that you just need to execute the proper button combo to get to the bootloader screen. As long as bootloader works, the phone is recoverable.
Also, have you been charging the device? Since you let the battery die, you should charge it fully again (overnight on wall charger, not connected to PC).
redpoint73 said:
Try power+vol down.
The phone isn't bricked. I already said, you can't brick this phone doing what you did (trying to flash recovery, root file). Those partitions are separate from the bootloader, which is also protected by s-on (you couldn't overwrite it, even if you wanted to).The fact that the HTC logo screen comes on, also means bootloader is still working properly (no bootloader = dead screen) and that you just need to execute the proper button combo to get to the bootloader screen. As long as bootloader works, the phone is recoverable.
Also, have you been charging the device? Since you let the battery die, you should charge it fully again (overnight on wall charger, not connected to PC).
Click to expand...
Click to collapse
in my case bootloader is working even i cn can access recovery( but to access recovery it takes 20 minutes) /data is not mounting
tried every solution to flash even ran RUU , but no luck
I did nothing to device as such , device rebooted and i think EMMC blown itself!
Related
Hi,
I have bought a used HTC M9 on Kijiji (I'm in Québec, Canada)
It must be faulty because it kept randomly restarting (sometimes once, sometimes for periods of 20 minutes, which made it hardly usable)
After clearing the cache partition and factory resetting it a couple times, I decided to flash it.
What I did:
- enabled the developer mode and USB debugging
- unlocked the bootloader
- flashed TWRP
- flashed SuperSU v2.74-2
Now, Android won't boot. When I start the phone, I see the green HTC logo on a white background with a red text saying it's a development build, then after about 10 seconds it restarts to the same screen. Over and over again.
In download mode, I am able to see the device with fastboot, but adb does not show anything.
In recovery mode, it's the opposite.
The phone is still S-ON so I have tried S-OFF methods (moonshine and firewater), but the fact of not having fastboot AND adb working at the same time made them fail.
Here's my phone info:
(bootloader) kernel: lk
(bootloader) product: htc_himaulatt
(bootloader) version: 1.0
(bootloader) imei: ************
(bootloader) version-main: 3.38.666.2
(bootloader) boot-mode: download
(bootloader) version-baseband: 01.01_U11440801_96.01.51207G_F
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA11000
(bootloader) cid: BM___001
Any help would be greatly appreciated...
Thanks in advance!
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Roobwz said:
youre flashing the wrong superuser. Try 2.64. And btw, moonshine and firewater wont work. The only way to s off is sunshine
Click to expand...
Click to collapse
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
zzzer51 said:
Thanks for your reply.
I used Squabbi's HTC one M9 Toolkit to flash
It does not offer 2.64, but 2.52 and 2.66 are the closest ones. Both in BETA as well.
Should I try one of them?
Click to expand...
Click to collapse
You shouldnt use toolkits imo, no offence squabbi. You should just download the 2.64 file from chainfires thread and flash it in twrp. It isnt harder than that. Btw 2.64 was the only superSu that worked for me
Ok, I have been able to find a zip for 2.64 and will install it with TWRP when my phone's battery is drained out (it tried to boot on the OS and is currently stuck on the HTC logo...)
I have also tried installing files directly from the microSD
downloaded from:
https://docs.google.com/spreadsheets/d/1ZaiJ3F_f76sVa4daU5H62OYi5Bj23LEBBv4xDTQ8y-M/pubhtml
http://androidruu.com/index.php?developer=M9
using fastboot flash zip zipfile.zip
but I get errors like
9 RU_SECURITY_FAIL
android-version information is missing
I'm not sure I'm trying to flash the right file anymore...
EDIT:
I have tried to flash both 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.30 and 0PJAIMG_HIMA_UL_L50_SENSE70_ATT_BM_1.32.666.6 files by going to TWRP -> Install but I get the error message 'zip file is corrupt!' every time...
And when I try to flash with fastboot, I get "Invalid sparse file format at header magi"
EDIT2:
Ok, I have made some progress!
What I did:
1/ Downloaded the image from this page http://forum.xda-developers.com/one-m9/general/guide-return-to-stock-canadian-htc-one-t3108236
2/ Formated my 8GB microSD card to exFAT (because the system image file is over 4GB)
3/ Extracted the system.emmc.win and boot.emmc.win files to the microSD card in path: E:\TWRP\BACKUPS\<myPhoneIDThatFastbootCanGiveYouIfYouTypeFastbootDevices>\Stock Bell
4/ Started the phone in recovery mode (TWRP)
5/ Tapped on Restore
6/ Selected the two files and hit Restore
7/ Performed a Factory reset (through TWRP, by tapping Wipe)
8/ Rebooted the phone in System mode
And Android started!
I'm not 100% sure it fully works as I haven't been able to finish the configuration yet (I don't have access to a wifi network where I am) so I will do that when I get home tonight.
But it looks a lot better than these past few days.
In the meantime, a quick question:
My bootloader is still unlocked. Can I leave it like that or should I re-lock it?
Thanks
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
shivadow said:
No need to relock it unless you plan on updating. There is conflicting information on whether a locked bootloader is absolutely necessary.. Maybe someone could chime in?.
Otherwise it's safe to leave it and probably best to.
Beamed in by telepathy.
Click to expand...
Click to collapse
You can OTA with an unlocked bootloader but you need to be 100 % stock. It's always best to not relock bootloaders as if you get into problems, you'll not be able to flash stuff. The only time a locked bootloader is needed is when running RUU.exe while S-On. The SD card method works with an unlocked bootloader. I'd recommend to leave it unlocked
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
zzzer51 said:
Thanks for the advice!
Ok so I have been able to boot the phone and set it up with my GMail account using wifi.
However, now:
1/ I have a red text mentioning that the build the phone is running is meant for development purposes only. It does not really matter to me, I just thought I'd mention it.
2/ There is no network service. I have tried my girlfriend's SIM card as well, but nothing happens. It doesn't say it can't register the SIM card nor say that the SIM card is not detected. Just nothing.
I tried changing the radio mode to GSM auto using *#*#4636#*#*, but when the phone reboots, it's back to WCDMA
3/ No IMEI (*#06# shows an empty window)
4/ It still randomly reboots as before. I was able to save a 'system crash' error report that popped up after a reboot. Please find it here: https://docs.google.com/document/d/13QBaeA1_Vo-b9mndffvbulG8epMq42Pnguawa2GcQTA/edit?usp=sharing
5/ When I press the physical button to lock the screen, it makes it go black then reboot, 50% of the time
Click to expand...
Click to collapse
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Roobwz said:
did you restore the correct backup for your firmware?? ex 3.35,401.12 needs 3.35.401.12 and not 3.35.701.12. Everything needs to match. This might also solve your issues.
Click to expand...
Click to collapse
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
zzzer51 said:
I don't think I did...
The main-version that shows in download mode is 3.38.666.2 ... whereas the version of the backup I restored is 1.32.666.30.
I have been searching for a while, but have no idea where to find the right rom... Should I send an email to Bell?
Click to expand...
Click to collapse
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Skickat från min HTC One M9 via Tapatalk
Roobwz said:
That's why you are getting these issues. You can try out the RUU service. Keep in mind that it costs around 20$, but at least you'll get a phone that's 100 % stock again. Either that or getting s off and downgrade firmware with a RUU
Click to expand...
Click to collapse
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
zzzer51 said:
Thanks for the suggestion, I did not know that service.
I always prefer doing things on my own, but I might have to use them because I have already spent around 20 hours trying to fix my phone...
That is, if we are sure there is absolutely no other way to find the RUU for free?
Click to expand...
Click to collapse
The service is remotely done over the computer, so you'll see everything that happens.
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free. Either that or s off (25$ as well), and you'll be able to convert your phone into a world wide edition model or dev edition. S off opens up a whole new world for you. Ex - you can flash exactly what you want (no need for Canadian firmware) and you're able to downgrade etc. The rest is up to you.
Roobwz said:
Well, if you find a RUU that matches everything (cid, mid and firmware), you'll be able to do it for free.
Click to expand...
Click to collapse
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
zzzer51 said:
I found the version I was looking for from this link: http://www.htcdev.com/devcenter/downloads/P100
However, it's only 206MB, so I'm guessing it's not a firmware... what do I need to do with it?
EDIT: It's .tar.gz files. apparently source code
Click to expand...
Click to collapse
That's kernel source I believe. Your only luck would be flippys thread in the general section
Skickat från min HTC One M9 via Tapatalk
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
zzzer51 said:
The latest news:
I went S-OFF yesterday with Sunshine.
I was able to install Cyanogenmod, which looked cool, but I still did not have any network service.
So, I flashed an Bell stock firmware, version 1.xxx
Still did not have network.
I let Android download and install the update for version 2.xxx
When it finished, I got my network back!
Now, I would like, but am afraid to, update firmware to version 3.xxx or try Cyanogenmod again.
But, obviously, I'm afraid that I won't have any service anymore...
Anyways, thanks a lot guys for your help!
Click to expand...
Click to collapse
I would recommend upgrading to 3.xx for several reasons like doze, custom ROMs that are up to date etc. If you did the OTA from 1.x to 2.x, you shouldn't have any problems with the OTA to 3.x. in the worst case, just re flash the RUU or just convert the device to an European version.
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
zzzer51 said:
Heyyy, it's me again
So, Android downloaded the update, but when I try to install it, it reboots to download mode.
Also, I cannot access the Recovery Mode.
I tried flashing TWRP 3.0.2.0 with fastboot a couple times, but when I try to access the Recovery Mode from the bootloader, I get :
Code:
Failed to boot to recovery mode
Press volume up or down to back to menu
Anyone knows why?
I am S-OFF and my bootloader is UNLOCKED
Thanks
Click to expand...
Click to collapse
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Roobwz said:
what was flashed prior to the OTA? OTAs fail if you arent 100% stock.
Click to expand...
Click to collapse
A looooot of stuff!
But even after flashing the original HTC recovery again, I get the same message.
And I can't access the recovery menu either.
Thanks
So roughly two years ago I decided to root my phone. I flashed TWRP, got S-OFF, and root. Well somebody hacked my phone and I freaked out. They were remotely downloading and inventorying all my devices' files, serial numbers, hardware info, accessing my camera, I mean everything, it was truly frightening the level of which whomever was doing this was able to to do it. I freaked out, went into TWRP, and started deleting everything that looked suspicious. I deleted my OS and probably a bunch of other things I shouldn't have on accident through TWRP. My device still has TWRP recovery functioning. I tried using ADB on my Windows 10 PC but I have no idea what I'm doing. I kept getting errors to the effect of "wrong version" etc. Being unable to use ADB I resorted to copying Viper OS to a flash card and I used TWRP to install it from flash. Once installed it "ran" but my Wifi radio did not work at all. When I tried to enable it in settings it stayed grey. Figuring I screwed up royally again, I decided to copy and paste a folder I created in 2014 with a TWRP recovery. It had the OS, cache, etc backed up. After using TWRP recovery it said I had no OS again. I'm freaking out, my phone is trashed, and I don't want to do anything else without a babysitter. I just want my original phone back, no custom roms, nothing. I don't want to turn S-ON because I know there is a possibility of bricking and quite frankly, I'm an idiot. Somebody just please walk me through what I need to do to get a fully functioning OS back on my phone. SD card methods preferred, as I can't get ADB to work or I'm too stupid to use it. I saw something mentioned that the firmware may need updating and that may have been the cause for the WiFi issue, since all I did was install Viper through a .zip through TWRP.
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
lgally80 said:
I just have no clue what I'm doing, the forums were no use. I don't understand any of it. To be honest, I don't know how I managed to root my device in the first place without bricking it. I need someone to baby me through the reinstallation of an OS. I mean every moot detail.
My "POWER ON + VOL DWN" Menu:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT: 3.16.0.0000
RADIO: 1.16.21331931.LA11G
OpenDSP v38.2.2-005420M8974.0311
OS: N/A
eMMC-boot: 2048MB
Apr 18 2014,16:06:33.0
TWRP version is 2.7.0.2
Click to expand...
Click to collapse
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
xunholyx said:
First things first.
Yes, you need to update your firmware, but you also really need to update your recovery as well.
Download this version of ViperOneM8 and flash it from your extSD. That will get you an OS that works.
Next, update your recovery. I would suggest 2.8.7.0 or newer. You can find the downloads for that here and instructions on how to flash the recovery here. ( I usually use the fastboot method myself )
After that you can update your firmware. You can find downloads for your firmware and instructions on how to flash it in this thread.
After you have the new recovery and new firmware, you will be able to flash a ROM built for the newer Android versions with working wifi.
You could also update via RUU from HTC's official US website, but you didn't give enough information for that. An RUU will return your phone to stock.
If you want to RUU your phone, plug into your PC and get into fastboot, enter fastboot getvar all and post the results here minus your IMEI and serial#. Either me or someone else here will be able to direct you to the proper RUU.
I'm guessing from your profile that you are on AT&T? If so, you can find the RUU for your device and instructions to update manually here.
Good luck!
Click to expand...
Click to collapse
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Update 1:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Update 2:
Opened the original OS Viper I flashed, it was a .zip with boot also, so going to leave this new one alone and go ahead and flash as a whole...
Update 3:
Flashed as whole, last screen on install said successful, rebooted. On HTC screen, waiting to see what happens... 3 minutes into waiting...
Update 4:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed. You deserve just as many blowjobs as you do internets. Don't know what was wrong with that last Viper ROM but this did it. Many thanks. Not even going to bother with the new TWRP and everything else, my phone works as is and that's that. +1 for you mate.
lgally80 said:
So, I first flashed the latest TWRP, and it did not work. Upon boot, I got the HTC on white background, with red "development purposes" warning, and it stayed there. I reflashed openrecovery-twrp-2.7.0.2-m8.img over the twrp-3.0.2-0-m8.img and got my recovery back using "flash recovery *.img" through ADB. thank god. Was this due to S-ON?
Next step, going to try flashing the OS/Rom you suggested. Will update in a sec...
Click to expand...
Click to collapse
I did say to flash the ROM first to get back your OS, so.....
Anyway, that recovery version won't work until you update your firmware. Try 2.8.7.0 first, update your firmware, then you can use the 3.x.x.x recovery
I should have been clearer in my instructions
lgally80 said:
Crap, that .zip has a bunch of stuff in it... Do I need to "build" an image to flash manually? Going to use the OS *.img by itself instead of leaving it as a whole .zip and trying to flash the whole .zip. There is a boot.img file and I don't want to mess with boot, so I will extract the zip and use only the OS in TWRP and see how that goes...
Click to expand...
Click to collapse
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
lgally80 said:
Holy mother of gaben, booted into setup, and my WiFi radio is detecting my networks, that's all I needed.
Don't know what was wrong with that last Viper ROM but this did it.
Click to expand...
Click to collapse
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
redpoint73 said:
You don't need to mess with or open a custom ROM zip to flash it. You just flash the whole zip. Yes, there is a lot in there, the OS (particularly a Sense one) is big, about 1.5 GB.
Mess with taking things out of the zip, and it probably won't flash. Or even if it does, it won't boot.
There is nothing wrong with the current Viper ROM.
The problem is your firmware is ancient (release KitKat firmware). Firmware meaning a number of modules needed for the OS to work, but are not contained in a ROM, which include hboot, radio, and a number of other modules including . . . WiFi.
Using your outdated KitKat firmware with almost any later ROMs (Lollipop or Marshmallow) will result in the same issue of WiFi broken, and also possibly extreme long boot time or no boot.
If you want to flash any remotely updated ROMs, you will need to update firmware as xunholyx already directed.
Click to expand...
Click to collapse
Yes I probably "should" update TWRP and my firmware, buuuut....
If it ain't broke, don't fix it.
Also in reply to your comments:
1. Flashing ViperOneM8_6.1.0.zip caused WiFi loss. Maybe Bluetooth also, don't remember. Flashing ViperOneM8_2.5.0.zip and now my phone is 100% functioning.
2. That "Old" firmware works fine now that it matches the ROM requirements, all radios functioning stable for several days now. I don't mind staying on older releases.
3. Nah I'm good, I use this M8 as a tool or entertainment device at home, and nothing else. It has no service, no AT&T signal here. Hasn't had service since 3 years after public release.
Anyway, thank you everyone who contributed. Anyone who's just showing up:
The Lesson of the Day - If your Hardware Radios do not function, the solution is your ROM probably requires a different Firmware revision than the one installed.
Cheers.
Hi guys,
Got a phone a need to revive. I received unusable. Mother gave it to my sisters friend and she said it doesnt work. I now see why cause he was trying to mod it.
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
So currently "fastboot getvars" reports back all the info. It's showing version-main 6.13.206.5 and I just want official O2 stock so can use the phone. Ideally sim unlocked but could hassle O2 for that later since it was my mother's contract.
Basically just want to get a working recovery image on and then flash stock. CID is 02__001
Any suggestion to revive this welcomed, please.
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
ckpv5 said:
So it still have twrp on it ? If yes, boot to twrp recovery then restore the stock backup.
You can find all you need in my thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Post #1 - how-to
Post #3 - you'll find the O2 stock backup
Post #5 - you'll find O2 firmware, install firmware after you restore the backup
Click to expand...
Click to collapse
No, I cannot get into it. When I select HBOOT, then select recovery it just shows white screen, ANDROID and then back to the menu. TWRP no longer works. That's what I'm trying to fix or put on a stock recovery image and then stock OS/firmware.
Just wondering if I need to UNLOCK it again and also do I need USB debug on. I cannot boot into OS so unable to set USB debug.
To UNLOCK bootloader can that be done if you can only get into bootloader menu? S-ON is enabled but not 100% that will stop recovering it? That's just for signed rom/firmware and I just need something stock.
You don't need usb debugging on to unlock the bootloader as it is done on fastboot mode (bootloader).
First I suggest you install the O2 firmware only then see whether you can boot to OS (assuming the OS is still stock base)
Second, re unlock bootloader with unlock_code.bin that you can get from htcdev.com, install twrp 3.x and restore the stock backup and relock bootloader and reflash firmware. This will get your device to fully stock.
So far, I don't see any RUU for your device version that you can get for free, only paid site has it.
Tainted said:
I managed to once get into TWRP but cant anymore. It was UNLOCKED but now RELOCKED which I possibly made it a little harder for me.
Click to expand...
Click to collapse
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
redpoint73 said:
Relocking the bootloader renders the phone unable to boot into OS by definition, as it expects RUU to be run (but as mentioned, RUU is not available for your CID unless you pay - but it's not needed).
Also, you can't flash TWRP with a locked bootloader, again by definition. The primary limitation of an unlocked bootloader, is that it prohibits flashing unsigned recovery images.
So as suggested, simply unlock the bootloader again (with existing unlock bin code, or get a new one using the HTCDev.com process again). Then flash TWRP and a stock TWRP backup using ckpv5's backup collection (linked in his signature).
Click to expand...
Click to collapse
ok, well made some progress.
unlocked the bootloader the official way. Very quick which I was surprised.
This then repoened up the recovery menu working.
then used fastboot to install latest twrp
then installed S.Team-JW-7.5.0.zip !!!
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Wondering if end of the line. Any suggestions? I assume need to get into TWRP and flash stock update from ckpv5.
Must say thanks for replies guys. ckpv5 you done some good work on here.
Tainted said:
The install and everything looked good, no errors and now just not turning on. I think now it's a brick? Does not seem to be coming back to the bootloader menu and certainly does not try to boot.
Click to expand...
Click to collapse
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
redpoint73 said:
It's really hard to brick this phone (especially with s-on) just flashing TWRP and flashing ROMs. Probably not a brick.
At what point exactly did it shut down/not reboot? ROM installed with no errors, and when you tried to reboot, it went dark? You aren't specific on this point.
How much charge was on the battery when you were flashing the ROM? Did you leave it a long time flashing the ROM, or rebooting, that simply may have drained the battery to shutdown?
Try leaving the phone on charger for several hours, then hold power+vol up for a minute or so, and see if any change (even if just stuck on HTC logo screen).
Click to expand...
Click to collapse
Hi there,
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
The ROM install finished, battery was at about 80% and everything looked good and I let it reboot the phone. And then it went dead. Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes. My S7 edge shows up. It flash an orage dot twice, so appears to be a in loop.
I charged the phoned and no luck with any of the power+ vol +/- keys. No response from any of those? I let the phone sit till flat and no orange light and then charged it today and still nothing. Not sure if it's a bad battery but it was up at 83% showing in the TWRP menu and working plugged or unplugged.
It's become a challenge now to make it work, I havent had to mod phones since my HTC One which got heavily modded and then back to stock. I stopped doing that after modding every phone I had since HTC Desire Android 2.3. So been about 4 years since doing all this again. Never had one that was totally bricked.
Tainted said:
Well I expect the bootloader to be separate from the rest so we can get into TWRP and normally get out of this situation?
Click to expand...
Click to collapse
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
Tainted said:
Right now the PC keeps beeping as a device has just connected and then again as though it's disconnected. I'm watching the device manager and dont see it listed during the connect but device manager tree refreshes.
Click to expand...
Click to collapse
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
redpoint73 said:
You are correct that bootloader (AKA hboot) is a separate partition, isn't touched by TWRP, and in fact is "protected", and can't be modified with s-on. Only an official signed zip (RUU, OTA, zip) can write to hboot when s-on, which is one of the reasons why I say this phone is hard to brick with s-on, just by flashing TWRP and flashing ROMs.
You won't connect to the phone by PC in any way, unless you can get the phone to power on, at least to bootloader.
A few additional suggestions/comments I made to another user (in another thread) who by strange coincidence has a very similar condition (apparent brick after flashing a ROM): https://forum.xda-developers.com/showpost.php?p=73062871&postcount=10
But to be honest, it's not looking too good, since the condition hasn't changed after charging and trying the button combos.
Click to expand...
Click to collapse
Cheers for that. Not getting much except for the 2 brief flashes of orange light.
Any chance the battery is totally messed and this is the problem?
Tainted said:
Any chance the battery is totally messed and this is the problem?
Click to expand...
Click to collapse
It's possible. Or it might be something else like motherboard or emmc. It's impossible to say for sure.
Ok, friend gave me his old HTC One (M8)
Its locked to EE network, Whenever its on HTC Sense Input constantly stops working, I have attempted the fix many forums and youtubes say to just clear the Cache... but this has not helped. I came to conclusion that the OS itself has been corrupted and Factory Reset does not help. I have attempted many Ruu's trying to find the correct one running it from the PC but all say wrong signature. I see things like Fastboot and cmd commands but the bootup screen has no way to type so I must be missing something. I have read guides and such but many seem to have files missing from their uploaded guide lines. So I come to this... please help.
Here's how the Power + Up Arrow screen looks.
*** Software Status: Modified ***
*** Locked ***
*** Security Warning ***
M8-UL PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.29.214500021.12G
OpenDSP-v51.2.2-00593-M8974_FO.1015
OS-6.12.61.4
eMMC-boot 2048
After that it's just date/time stamp and the boot options
Edit...
So the closest I've gotten is using the guild here (androidforums.com/threads/htc-one-m8-unusable.995871/#post-7212766)
I have fastboot now installed, stuck on the twrp part as getting anything actually installed on the phone itself is impossible due to the Sense Input not working. At least though what I know what to do. Letting the phone boot normally just ends up with the HTC Sense Input looping and crashing.
From Fastboot getvar all
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
Renaan said:
HTC One (M8) please Help me fix this stupid phone....
Click to expand...
Click to collapse
I strongly suggest you reword the title of the thread. Just because you don't know what to do, doesn't make the phone "stupid". Coming onto this forum, and name calling (the device) is not a good idea. Most folks who you are asking help from, must hold this device in fairly high regard, to be spending their free time to help others with it.
While well-intentioned, it's apparent your knowledge of this device, as well as some common Android tools, is pretty limited. Therefore, you're making some mistakes and incorrect assumptions. That isn't an insult. You only know what you know, and we all hard to start somewhere.
Renaan said:
I have attempted many Ruu's trying to find the correct one running it from the PC but all say wrong signature.
Click to expand...
Click to collapse
You can only run the RUU which is intended for the device's specific CID. There are many (dozens?) of RUUs for the different M8 versions. So you aren't going to find the right one by guessing. In fact, I don't think the your M8 version has an RUU (at least, not for free).
Recovering a device without RUU is possible, but it's somewhat involved. It's going to require an investment of time and effort (and some knowledge gained - not altogether a bad thing).
Renaan said:
I see things like Fastboot and cmd commands but the bootup screen has no way to type so I must be missing something.
Click to expand...
Click to collapse
Fastboot works by connecting the phone to a computer, which needs to have a fastboot environment setup on it. Again, I can go into it. But I want to make sure you are willing to put forth the time and effort, to go through with the whole process. Otherwise, advising you on how to use fastboot in itself is not going to get the phone up and running, and not worthwhile.
Renaan said:
I have read guides and such but many seem to have files missing from their uploaded guide lines.
Click to expand...
Click to collapse
Can't help or advise on this, unless you are specific about what those guides are, or what specific actions/methods you are attempting. I know you don't have enough post to put up links. But you can at least describe what guides, if you want specific advice on them.
---------- Post added at 01:36 PM ---------- Previous post was at 01:03 PM ----------
Renaan said:
I have fastboot now installed, stuck on the twrp part as getting anything actually installed on the phone itself is impossible due to the Sense Input not working. At least though what I know what to do. Letting the phone boot normally just ends up with the HTC Sense Input looping and crashing.
Click to expand...
Click to collapse
Installing TWRP is not related to the OS getting "stuck". TWRP (custom recovery) boots independently of the Android OS, and in fact installing TWRP doesn't even require the OS to be working at all. It just requires being able to access bootloader-fastboot mode (which you can).
But installing TWRP is going to fail, unless you first unlock the bootloader.
You can use the following guide to unlock the bootloader (see Section 1): https://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
But keep in mind that some files (like TWRP version) in the guide are outdated. I recommend current TWRP version 3.1.1-0, which you can get from here: https://dl.twrp.me/m8/
Only perform the part of the guide relevant to unlocking the bootloader and installing TWRP. No need to root (and the SuperSU file linked is outdated), or any of the rest of the guide.
---------- Post added at 01:42 PM ---------- Previous post was at 01:36 PM ----------
Renaan said:
So the closest I've gotten is using the guild here (androidforums.com/threads/htc-one-m8-unusable.995871/#post-7212766)
Click to expand...
Click to collapse
You are on the right track: restore stock TWRP backup, since no RUU available for 6.12.61.4
But I'd suggest just using the original XDA thread, which is referenced in the Android forums thread you linked: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Just follow up through Step 9, and reboot. The rest isn't needed (no more updates for this phone).
I suppose the Android Forums post has a bit more explanation. But ckpv5 deserves full credit for doing all the work posting the files and maintaining the thread.
redpoint73 said:
I strongly suggest you reword the title of the thread. Just because you don't know what to do, doesn't make the phone "stupid". Coming onto this forum, and name calling (the device) is not a good idea. Most folks who you are asking help from, must hold this device in fairly high regard, to be spending their free time to help others with it.
I suppose the Android Forums post has a bit more explanation. But ckpv5 deserves full credit for doing all the work posting the files and maintaining the thread.
Click to expand...
Click to collapse
So I'm already stuck on getting twrp onto the phone, the HTCDev site which I need to unlock the Bootloader just seems to loop on itself when attempting to register.
How can I get twrp installed ?
Renaan said:
So I'm already stuck on getting twrp onto the phone, the HTCDev site which I need to unlock the Bootloader just seems to loop on itself when attempting to register.
How can I get twrp installed ?
Click to expand...
Click to collapse
The HTCDev.com website can be buggy. Maybe wait a while, and try later. I also remember having to use a couple different email addresses to register, before it worked (as it wouldn't take the same email address I already used).
There is no way around it. You need to unlock the bootloader in order to install a custom recovery, by definition.
Also, please refrain from including my whole post (when it's a long one, like the last one) in your response; as it clutters up the forum. I know it's the default (to quote the post you are replying to) when you reply. But just delete it (you can edit your previous post).
Progress....
So,
I have kinda made progress... kinda
It tells me to make a backup so I can find out where the backup goes on internal storage.... but nowhere can I find it... I have simply tried searching for backup and nothing, mounting as usb to search also comes up nothing and I'm not sure what I'm even doing wrong.
I went and made sure to download the correct zipe for my carrier as towards the end it asks me to flash an img... but nowhere does it seem to provide one. I've downloaded the correct ckpv5.zip for my phone but there's no recovery.img file in it, again, not sure what I'm messing up .
Renaan said:
It tells me to make a backup so I can find out where the backup goes on internal storage.... but nowhere can I find it... I have simply tried searching for backup and nothing, mounting as usb to search also comes up nothing and I'm not sure what I'm even doing wrong.
Click to expand...
Click to collapse
In TWRP, in the Backup option, make sure Internal Storage is selected as the storage location (button near the top of the "Backup" screen. It's also possible to select the SD card as the save location, if you have an SD inserted in the phone.
Once internal storage is selected as the save location for the backup, check "boot" and back it up. It's a little irrelavent what you backup. The idea is to just backup "something" so that TWRP creates the proper folder structure, and "boot" is the smallest thing to backup (something like 50 MB, as opposed to backing up System, which is like 1.5 GB).
Make sure TWRP says the backup was successful. After that, you should easily find the folder TWRP in the main directory of internal storage. Inside the TWRP folder, you will find the Backup folder, and inside that, a folder with your phone's serial number (don't post that number - it's personal info). That is where you want to copy the stock TWRP files you extracted from ckpv5's collection.
Renaan said:
I went and made sure to download the correct zipe for my carrier as towards the end it asks me to flash an img... but nowhere does it seem to provide one. I've downloaded the correct ckpv5.zip for my phone but there's no recovery.img file in it, again, not sure what I'm messing up .
Click to expand...
Click to collapse
The stock recovery is not included in the same folder as the stock system and boot. Stock recoveries are in Post #4 of the collection. But you don't need to do it. I already stated above, you only need to perform through Step 9 of the guide. Than just reboot, and setup the phone.
No need to flash stock recovery. It's a waste of time, as your phone will not get anymore updates from HTC, and that is really the only reason to install stock recovery for the device. Plus, if anything goes wrong, and you need to use TWRP again, it won't be there (it will have been over-written by stock recovery) and you will waste more time flashing TWRP back on the phone, if you nee to use it.
Fixed!
ok, Everything seems fixed now, no img was needed just putting things in correct place I guess..
Thankyou for the helps
Renaan said:
ok, Everything seems fixed now, no img was needed just putting things in correct place I guess..
Thankyou for the helps
Click to expand...
Click to collapse
Glad it worked out for you. The process to restore by stock TWRP backup (since no RUU) is not trivial. So nice job, and I'm sure you learned some things in the process!
Hello everyone,
- i'm sry if i posted abt the same issue but i managed to gather more information abt the situation
- 1st of all everytime i reboot i find the same apps installed , pics and missed calls no matter how many times i erase all that and if i installed new apps every reboot it's not there, I wanted to get it back to stock as new but i couldn't and here what i have tried :-
1-couldn't flash stock or custom recovery [failed (Remote : Not allowed)] cuz bootloader is locked, And i couldn't unlock bootloader .
-(after getting unlock code from HTCdev.com and installing it and after selecting yes on the phone to unlock bootloader, phone just reboots)
2-tried to flash RUU (3.30.651.2 & 4.25.651.14) Wizard while phone was on fastboot mode
https://onedrive.live.com/?cid=AC7B...23EA2B!345&parId=AC7BFAC4E523EA2B!341&o=OneUp
-Phone couldn't boot into bootloader while on fastboot mode so it reboots regularly.
3-tried to flash RUU (3.30.651.2 & 4.25.651.14) wizard while phone was on
https://onedrive.live.com/?cid=AC7B...23EA2B!344&parId=AC7BFAC4E523EA2B!341&o=OneUp
-did the first steps ok but again when wizard is waiting for bootloader while phone was in fastboot mode, it just reboot regularly.
4-tried renaming another (4.25.651.14) RUU to 0P6BIMG.zip and put it on sd-card and went to Hboot.
https://onedrive.live.com/?cid=AC7B...23EA2B!342&parId=AC7BFAC4E523EA2B!341&o=OneUp
-after clicking yes to confirm the update, Phone rebooted in the middle of the steps .
5-tried flashing same 0P6BIMG.zip from recovery mode.
https://onedrive.live.com/?cid=AC7B...23EA2B!347&parId=AC7BFAC4E523EA2B!341&o=OneUp
-after 3 mins of hope crushed by verifying update package.... - Installation aborted....
6-tried flashing RUU.zip via fastboot
https://onedrive.live.com/?cid=AC7B...23EA2B!346&parId=AC7BFAC4E523EA2B!341&o=OneUp
-phone just reboots regularly when trying to reboot RUU .
7-I contacted HTC support and after givin 'em alot of images and getvar they told me that my phone was modified in two ways (s-off) &
(Recovery tool) , They are telling me that (i must install the android recovery tool once again before proceeding) !! and i need to search on this site (Xda) for the stock recovery, but i think i have the stock recovery tool, and i can't flash any recovery because bootloader is locked, So is there any other way to flash recovery.
-here is some photos and getvar
https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B!339&parId=root&o=OneUp
https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B!350&parId=root&o=OneUp
version: 0.5
version-bootloader: 3.18.0.0000
version-baseband: 1.08.20.0612_4
version-cpld: None
version-microp: None
version-main: 3.30.651.2
version-misc: PVT SHIP S-OFF
imei2: Not Support
meid: **************
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B70000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: d4c3cae5
hbootpreupdate: 11
gencheckpt: 0
Devil_55 said:
1-couldn't flash stock or custom recovery [failed (Remote : Not allowed)] cuz bootloader is locked, And i couldn't unlock bootloader .
-(after getting unlock code from HTCdev.com and installing it and after selecting yes on the phone to unlock bootloader, phone just reboots)
Click to expand...
Click to collapse
Since you are s-off, try this method to unlock bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
Although I don't see the point in flashing stock recovery. It won't help your present situation (return to full stock).
What recovery is currently on the phone, stock or TWRP? What happens when you try to select Recovery from the bootloader menu?
Devil_55 said:
2-tried to flash RUU (3.30.651.2 & 4.25.651.14) Wizard while phone was on fastboot mode
https://onedrive.live.com/?cid=AC7B...23EA2B!345&parId=AC7BFAC4E523EA2B!341&o=OneUp
Click to expand...
Click to collapse
Can't see what you are trying to flash. It says "This item may not exist or is no longer available".
All Sprint RUUs are available here: https://forum.xda-developers.com/showthread.php?t=2729173
Thanks for the fast reply
redpoint73 said:
Since you are s-off, try this method to unlock bootloader: https://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
-I already Tried that several times but not working still locked
redpoint73 said:
Although I don't see the point in flashing stock recovery. It won't help your present situation (return to full stock).
Click to expand...
Click to collapse
-Yea but How to return to full stock
redpoint73 said:
What recovery is currently on the phone, stock or TWRP? What happens when you try to select Recovery from the bootloader menu?
Click to expand...
Click to collapse
-Stock Recovery, I attached a photo of the recovery,
-If i select recovery from the bootloader menu it gives me black screen with red triangle, Then i hold Vol up and click power once
redpoint73 said:
Can't see what you are trying to flash. It says "This item may not exist or is no longer available".
Click to expand...
Click to collapse
-I was flashing 3.30.651.2 RUU.exe while phone was on bootloader mode, The thing is if the phone is on bootloader mode and wizard is showing that it's (Waiting for bootloader...) ,then phone reboots regularly and nothing changed
-And if phone was just on with activated usb debugging and i opened RUU.exe, the first step is to get to bootloader mode and then will send all the data of the RUU, Then it will show it's (Waiting for bootloader....) again, But because the phone is already in bootloader mode, The phone will just reboot as i showed in step 3, so when wizard is trying to go bootloader mode while phone is on bootloader mode that's what make it doesn't work.
-This is another link of Step 2 (Flashing 3.30.651.2 RUU.exe) while on fastboot mode
https://onedrive.live.com/?cid=AC7BFAC4E523EA2B&id=AC7BFAC4E523EA2B!351&parId=root&o=OneUp
-I read abt Nandroid backup and how it takes an exact image of everything on the phone, could it be that someone did that backup and every time phone reboots it restores that backup, and if so how to know if something like that is activated.
Does the phone work normally in OS (but just won't wipe properly)? If you are trying to return to "stock", than what condition is it in now? Is it stock ROM, or otherwise?
Devil_55 said:
-Stock Recovery, I attached a photo of the recovery,
-If i select recovery from the bootloader menu it gives me black screen with red triangle, Then i hold Vol up and click power once
Click to expand...
Click to collapse
So I'm confused if you have stock recovery installed already; why you are trying to install stock recovery, or what that will do for you.
Devil_55 said:
-I read abt Nandroid backup and how it takes an exact image of everything on the phone, could it be that someone did that backup and every time phone reboots it restores that backup, and if so how to know if something like that is activated.
Click to expand...
Click to collapse
No, that isn't how a nandroid works. You need a custom recovery like TWRP to make a nandroid. And it will only restore if you manually boot into TWRP, and restore it. None of it happens "automatically" like you are describing.
---------- Post added at 03:38 PM ---------- Previous post was at 03:38 PM ----------
Devil_55 said:
-I already Tried that several times but not working still locked
Click to expand...
Click to collapse
Any type of error messages when you try to run the command to unlock the bootloader using the command prompt method?
redpoint73 said:
Does the phone work normally in OS (but just won't wipe properly)? If you are trying to return to "stock", than what condition is it in now? Is it stock ROM, or otherwise?
Click to expand...
Click to collapse
-yes it works fine in OS but won't wipe at all, I can install\uninstall apps , delete or add pictures but as soon the phone is rebooted everything gets back the way it was,
-I don't know if it has stock Rom installed on it, I just want to delete everything and start over with unmodified OS
redpoint73 said:
So I'm confused if you have stock recovery installed already; why you are trying to install stock recovery, or what that will do for you.
Click to expand...
Click to collapse
-sry for the confusion, I just thought if i could flash stock one by myself i could get around this situation somehow and at the same time the HTC support told me i don't have Stock recovery and i should flash stock one as the first step.
redpoint73 said:
No, that isn't how a nandroid works. You need a custom recovery like TWRP to make a nandroid. And it will only restore if you manually boot into TWRP, and restore it. None of it happens "automatically" like you are describing.
Click to expand...
Click to collapse
-Thanks for the clarification
redpoint73 said:
Any type of error messages when you try to run the command to unlock the bootloader using the command prompt method?
Click to expand...
Click to collapse
-Nope, I followed the guide then after adb reboot bootloader, Still locked
Devil_55 said:
at the same time the HTC support told me i don't have Stock recovery and i should flash stock one as the first step.
Click to expand...
Click to collapse
HTC support is wrong on that (or they are misunderstanding). Black screen with red triangle is the stock recovery. Re-installing the stock recovery isn't going to change or help anything.
Based on the widespread (largely storage-related) issues you've described (wiped user data reappearing, bootloader won't unlock despite multiple methods, RUUs won't flash) I tend to think this is an emmc failure, which you can't do much about. And based on the wide variety of options/workarounds you've tried so far (and failed) I don't personally see much (if any) options moving forward, unfortunately. If I think of anything else to try, I'll certainly let you know.
Thanks for your time and effort
Devil_55 said:
-yes it works fine in OS but won't wipe at all, I can install\uninstall apps , delete or add pictures but as soon the phone is rebooted everything gets back the way it was,
Click to expand...
Click to collapse
I've got the same issue, it's eMMC failure and you have to replace with the new one.
My topic: https://forum.xda-developers.com/htc-one-m8/help/help-wifi-off-t3762549
NoIP said:
I've got the same issue, it's eMMC failure and you have to replace with the new one.
Click to expand...
Click to collapse
How can i replace the emmc! Do u have a link for the guide?
Also is there any information i should take note of before deciding what emmc i should go with?
redpoint73 said:
HTC support is wrong on that (or they are misunderstanding). Black screen with red triangle is the stock recovery. Re-installing the stock recovery isn't going to change or help anything.
Based on the widespread (largely storage-related) issues you've described (wiped user data reappearing, bootloader won't unlock despite multiple methods, RUUs won't flash) I tend to think this is an emmc failure, which you can't do much about. And based on the wide variety of options/workarounds you've tried so far (and failed) I don't personally see much (if any) options moving forward, unfortunately. If I think of anything else to try, I'll certainly let you know.
Click to expand...
Click to collapse
I just found out that on the back of the phone .. Model : 0P6B100 !!!
Devil_55 said:
I just found out that on the back of the phone .. Model : 0P6B100 !!!
Click to expand...
Click to collapse
You can't trust what is on the back cover. We've often seen these swapped to remove US carrier logos. All indications on your getvar point to the "internals" of the phone (which is the important factor - and what you need to go by) being the Sprint version M8. It's very common to see the Sprint version to have its back cover replaced in order to remove the Sprint logo and sell it as an "unbranded" version (which it really is not).
---------- Post added at 09:03 AM ---------- Previous post was at 08:54 AM ----------
Devil_55 said:
How can i replace the emmc! Do u have a link for the guide?
Also is there any information i should take note of before deciding what emmc i should go with?
Click to expand...
Click to collapse
I'm not really a "hardware" guy. I can never seem to perform any hardware-related repairs on small electronics; despite being an engineer (very technically-minded) and all-around very careful about doing things (too obsessive about the minutia, in fact). But I have to say, changing emmc seems really delicate, and will not turn out well unless you are already experienced with this type of thing, and good at it. As far as I can tell, it involves heating up the chip, then installing the new one and "reflowing" the solder points. All of which looks really tricky, with a bunch of things that can go wrong along the way.
Might be better to have a repair shop do it, or change the whole motherboard, if you really want to go through the effort of hardware repairs to get this phone working again.
If you do change the emmc (or have a shop do it) I would only recommend using one intended for the Sprint M8. If you look at the thread NoIP linked, you will see I'm trying to help him with a weird emmc-motherboard combo, which I am not sure is fixable.
Thanks mate for explaining that