Hey guys
I know there are similar posts out there but none who describe my exact problem^^
It's like this: Earlier today, I wanted to go back to stock, fully. Which means I downloaded the stock backup and put it on my phone with TWRP. Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
As far, as good, everything worked just fine. And to have it completely back to stock (except for the still unlocked bootloader) I came up with the glorious idea of restoring to factory settings using the options in the phone's settings... aaaand now I'm stuck in the bootloop.
I meanwhile figured out how to enter the bootloader (volume up + power til screen turns fully black, then volume down) and I'm also able to access stock recovery through that... I of course tried factory resetting it through the bootloader and the recovery, I also took the sim card out as somewhere was suggested... but ultimately, it always goes back to the bootloop.
When connecting to the PC I hear the connecting sound... but that's it. It doesn't show up and thus I also can't access it through fastboot/adb
I ran out of ideas myself, do you have any?^^
Thanks!
M4C00kie said:
Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
Click to expand...
Click to collapse
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
M4C00kie said:
I also can't access it through fastboot/adb
Click to expand...
Click to collapse
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
adb requires being in OS or recovery (and I'm not sure if stock recovery supports adb). And for the most part, fastboot is what you need to recover.
Need more info to help further. What CID version of the phone? If OS version number is shown on hboot screen, post it here. What are the version numbers or the stock nandroid, and the stock recovery you installed? If you can get fastboot work, do fastboot getvar all, and post the output.
redpoint73 said:
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
Click to expand...
Click to collapse
That's because I was using an older guide... good to know^^
redpoint73 said:
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
Click to expand...
Click to collapse
That's what's strange... on the phone, it's showing FASTBOOT USB and it even makes this sound when connecting... fastboot commands still don't work though: "error: device not found"
the CID number is HTC__102, he version number of the stock nandroid and recovery was 4.16.401.10
regarding the OS number: on the hboot screen there's just written OS- <- is this the place where it's supposed to be?
thanks a lot for helping!
OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
C:\Users\aaron_000\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.25.2145000
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
my version & radio number are matching the ones in this RUU
so...
what now?^^ before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
oh, and would doing this even help in my current situation?
Thanks for helping
M4C00kie said:
OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
Click to expand...
Click to collapse
Did you do anything different to get it working?
M4C00kie said:
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=f...4a4f68918d8199)
Click to expand...
Click to collapse
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
M4C00kie said:
before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
Click to expand...
Click to collapse
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
M4C00kie said:
oh, and would doing this even help in my current situation?
Click to expand...
Click to collapse
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!
redpoint73 said:
Did you do anything different to get it working?
Click to expand...
Click to collapse
I might have confused adb and fastboot... pretty sure it was working all along
redpoint73 said:
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
Click to expand...
Click to collapse
I initially posted this on another forum... realised too late that this one here was more appropriate and posted it here xD
redpoint73 said:
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
redpoint73 said:
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
Click to expand...
Click to collapse
done.
redpoint73 said:
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!
Click to expand...
Click to collapse
deleted it. thanks for all your help so far!
M4C00kie said:
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
Click to expand...
Click to collapse
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.
redpoint73 said:
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.
Click to expand...
Click to collapse
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ or should I rather download a zip version of it?
M4C00kie said:
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ ?
Click to expand...
Click to collapse
As long as "fastboot" is selected in bootloader it will work.
redpoint73 said:
As long as "fastboot" is selected in bootloader it will work.
Click to expand...
Click to collapse
it worked!!
never heard a sweeter sound before than the HTC boot sound^^
thank you so much for all your help!
Related
I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
unifex_ said:
I got fed up with the problems my phone has been having since the Lollipop update and I decided to "reinstall" the whole thing. I've looked through lots of threads here and I more or less have an idea of what to do, but what troubles me is that most people point out that the phone will still not be the same as when it came from the shop.
So, could anyone please explain to me, how do I bring the phone back to its original maiden state. At this point, I don't even care if it would be Lollipop or KitKat, seeing that many people claim to have no problems with Lollipop.
It might well be that the problems I'm having are due to my meddling with the phone - i.e. disabling apps and restricting permissions. But at the same time, when I started backing up files to my PC in preparation to what I want to do with the phone, I found out that there are gigabytes of leftover data from apps that I had installed on KitKat. These apps are no longer installed on Lollipop, but their data (maps, dictionaries, etc.) are still there, despite the update and subsequent factory reset. And it certainly does not help that HTC Sync Manager erases records from my Outlook database instead of actually "syncing" the contacts with the phone.
I imagine what I need to do it to completely wipe the internal storage and flash the original HTC software there. Could anyone please confirm that this is possible and which method would be the safest?
Click to expand...
Click to collapse
Do as EddyOS says, he will guide you on the best which version to downgrade to (if your looking to do that). Honestly I didnt have any issues with Lollipop, its all good.
my suggestion of the easiest way to totally wipe up your internal memory is to unlock bootloader (if you've already unlocked it, then relock and unlock again), doing that will totally wipe your internal memory, as for ext. sd card, you can just format that.
Flashing original stock rom is done by an RUU.
EddyOS said:
Post the output of fastboot getvar all (minus your IMEI and serial number) first and we'll go from there
Click to expand...
Click to collapse
Thanks Eddy, I appreciate the help.
I attach an image of the fastboot output.
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
This will give you a 100% stock device, as if you just got it out the box
Click to expand...
Click to collapse
Great, that sounds uncomplicated enough. My bootloader is locked, as far as I know, at least I never did anything to unlock it. So I should be good to go.
One question though. At the moment, the phone is unlocked as far as SIM is concerned. I mean that although the CID is from T-Mobile Germany, I'm using O2 as the service provider. Will that RUU keep it that way, or it will make the phone locked towards T-Mobile SIM cards?
Thanks a lot.
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
EddyOS said:
It shouldn't put the SIM lock back on, if that's what you mean, but I can't say for certain it won't
Click to expand...
Click to collapse
In case it would, what would I have to do to unlock it? I don't have any T-Mobile SIM cards around here after all.
Buy a code, like you did last time
EddyOS said:
Buy a code, like you did last time
Click to expand...
Click to collapse
I did not buy any code, I bought a phone. That's how it came from the shop - SIM-unlocked. I had no idea it had the T-Mobile anything in it until I started looking around this forum and someone asked me about my CID.
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
EddyOS said:
If it was factory SIM-unlocked then it'll still be SIM-unlocked after flashing the RUU
Click to expand...
Click to collapse
Great, thanks! I'll let you know how it went.
OK, finally got the time to do it, but unfortunately, the RUU that I downloaded
EddyOS said:
If you don't mind setting up the device from scratch, you just use the 4.19.111.2 RUU, available here:
https://drive.google.com/file/d/0B17smFr95pleNTFvYi1yNnJrcU0/view
You need a locked bootloader first, so use fastboot oem lock first otherwise it'll fail
1. Run the file as administrator
2. Connect the phone in fastboot mode to your PC
3. Follow the instructions
Click to expand...
Click to collapse
did not work, I attach the screenshot with the error. Any ideas? The error was the same regardless of whether the phone was connected to the PC.
Yeah, it appears that RUU is corrupt
EddyOS said:
Yeah, it appears that RUU is corrupt
Click to expand...
Click to collapse
That's a pity. Do you know where can one find a proper RUU? I looked at the htcdev.com download section, they list the software I need, 4.19.111.2, but the download link brings me simply to the htc.de, where nothing can be downloaded, it's just their regular advertising site.
I also found a zip file with the 4.16.111.2 firmware on a German forum (basically, from a link in the xda thread with RUU and OTA collection), but to be honest, I'm not sure what to do with the bunch of img files.
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
EddyOS said:
The files on HTCDev are the kernel source so can't be flashed. Easiest thing to do for now is flash a ROM based on Lollipop until the proper RUU is re-posted
Click to expand...
Click to collapse
How about the files from that site (German, though). I found that link on the xda thread for RUU collection.
http://www.handy-faq.de/forum/htc_o...ne_m8_firmwaresammlung_ruus_otas_backups.html
They have a list of various files, for 4.19.11.2 they have nandroid backups and signed firmware, but not a RUU.
Or could you suggest a well working ROM?
You could flash the backup, then the firmware to restore stock recovery and it should work
EddyOS said:
You could flash the backup, then the firmware to restore stock recovery and it should work
Click to expand...
Click to collapse
Could you help me with mine as well
from fastboot
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.631.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH445WM0----
(bootloader) imei: ----------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B16000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.177s
Hello,
i have a problem with my htc one m8 any help will be appreciate.
i wan't to install the new rom viperone m8 but when i try to flash twrp latest version the recovery don't load it's reboot the bootloader only and don't get access to twrp to install rom
i'm able to flash philz_touch_6.26.6-m8.img and install skydragon latest rom
i'm also able to flash twrp-2.7.0.2-m8.img
here is my getvar all
c:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: <----------- i have doubt on this why it's empty
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: eb00c9d0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.016s
there is any solution for my problem?
can i install viperone 4.6.0 with wrp-2.7.0.2-m8.img
bootloader is unlocked and phone is s-off
Thank you in advance for your help.
First, remove Serial & Imei no from your post.
Can you remember whether your stock ROM is 4.21.1020.1 or 3.31.1020.9 ? Because both have hboot 3.19.0000
Don't use TWRP 2.7.0.2, use at least 2.8.4.0 or newer or latest.
Run these command
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
now you should be able to enter recovery.
Advisable to reboot your device after doing fastboot erase cache and then boot to recovery
Hello,
thank you very much for your help.
i was on 4.21.1020.1
yes i have tried to use twrp-2.8.4.0-m8.img but not working
i also did what you said
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
it's boot to bootloader it don't show twrp recovery.
very strange
thank you for your assistance
ckpv5 said:
First, remove Serial & Imei no from your post.
Can you remember whether your stock ROM is 4.21.1020.1 or 3.31.1020.9 ? Because both have hboot 3.19.0000
Don't use TWRP 2.7.0.2, use at least 2.8.4.0 or newer or latest.
Run these command
fastboot flash recovery NameofRecovery.img
fastboot erase cache
fastboot reboot-bootloader
now you should be able to enter recovery.
Advisable to reboot your device after doing fastboot erase cache and then boot to recovery
Click to expand...
Click to collapse
Yeah .. that's strange because your device on latest hboot.
Since your device is S-Off .. may I know why did you S-Off it ?
Seeing your device has stock CID/MID .. I'm scare that you jump from a lower 3.16.0000 hboot straight to 3.19.0000
Some people face problem too when they jump hboot.
i had to S-Off because in skydragon installation guides requirements
s-off is more easy
there is any solution to back and redo everything.
Thank you
ckpv5 said:
Yeah .. that's strange because your device on latest hboot.
Since your device is S-Off .. may I know why did you S-Off it ?
Seeing your device has stock CID/MID .. I'm scare that you jump from a lower 3.16.0000 hboot straight to 3.19.0000
Some people face problem too when they jump hboot.
Click to expand...
Click to collapse
Hello
Anyone got this type of problems?
There is any solution ?
Thank you
novalayer said:
yes i have tried to use twrp-2.8.4.0-m8.img but not working
i also did what you said
fastboot flash recovery NameofRecovery.img
Click to expand...
Click to collapse
You understand "NameofRecovery.img" needs to be the actual file name (such as: twrp-2.8.4.0-m8.img)?
redpoint73 said:
You understand "NameofRecovery.img" needs to be the actual file name (such as: twrp-2.8.4.0-m8.img)?
Click to expand...
Click to collapse
@redpoint73, I think that is refering to an issue that occured with the new update from HTC. I have it too and another users the same. The recovery TWRP higher than twrp-2.8.1.0-m8.img does not boot and enter back to bootloader. We discused this in another thread and we don't have an resolution until now. Is not manifesting on all the phones and is not region and provider dependent. In this thread you can see more details. http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-stuck-boot-screen-t3186424
whiperhack said:
@redpoint73, I think that is refering to an issue that occured with the new update from HTC. I have it too and another users the same. The recovery TWRP higher than twrp-2.8.1.0-m8.img does not boot and enter back to bootloader. We discused this in another thread and we don't have an resolution until now. Is not manifesting on all the phones and is not region and provider dependent. In this thread you can see more details. http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-stuck-boot-screen-t3186424
Click to expand...
Click to collapse
Good info. Makes sense since he was able to flash TWRP 2.7.something.
But it would be useful for folks when they seek help to actually give the exact fastboot commands used, and not just cut and paste from somebody else's post (so we can't even be sure if he is using the right commands to install TWRP).
For some reason I only can use twrp-2.7.0.2. All the others get back to bootloader immediately. Is there a solution? It happens after going back to sense from GPE. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2733523
Edit: Maybe is has somrthing to do with hboot? I have 3 .19.0.000
Petert87 said:
For some reason I only can use twrp-2.7.0.2. All the others get back to bootloader immediately. Is there a solution? It happens after going back to sense from GPE. I followed this thread: http://forum.xda-developers.com/showthread.php?t=2733523
Edit: Maybe is has somrthing to do with hboot? I have 3 .19.0.000
Click to expand...
Click to collapse
Something isn't right here. If you actually followed the thread you linked, you would not be on hboot 3.19.
The thread is also incredibly obsolete, as in 3 software/firmware generations old (the current is 4.16.xxx).
You most likely can't use the current TWRP due to outdated firmware. But you haven't provided enough info to tell for sure. Do fastboot getvar all and post the output (be sure to delete IMEI and serial numbers before posting the getvar data, as these are personal info).
redpoint73 said:
Something isn't right here. If you actually followed the thread you linked, you would not be on hboot 3.19.
The thread is also incredibly obsolete, as in 3 software/firmware generations old (the current is 4.16.xxx).
You most likely can't use the current TWRP due to outdated firmware. But you haven't provided enough info to tell for sure. Do fastboot getvar all and post the output (be sure to delete IMEI and serial numbers before posting the getvar data, as these are personal info).
Click to expand...
Click to collapse
I'm at work so atm cant provide a getvar all. What I did:
write cid 11111111, flashed 1.54.401.5-W_Splash.zip, reboot stock recovery, factory reset, installed TWRP. Again factory reset in TWRP. Then installed MaximusHD. Then I installed the first Nandroid I had from my software x.xx.161.x. Then did all OTA's. I think my hboot never updated during OTA.s
Petert87 said:
Then did all OTA's. I think my hboot never updated during OTA.s
Click to expand...
Click to collapse
And why do you think that? If that were the case, you would not be on hboot 3.19. Flashing 1.54 firmware would put you on hboot 3.16.
redpoint73 said:
And why do you think that? If that were the case, you would not be on hboot 3.19. Flashing 1.54 firmware would put you on hboot 3.16.
Click to expand...
Click to collapse
I thought that OTA updates the firmware automatically
Petert87 said:
I thought that OTA updates the firmware automatically
Click to expand...
Click to collapse
Yes, it does.
But why do you think it failed to do so?
redpoint73 said:
Yes, it does.
But why do you think it failed to do so?
Click to expand...
Click to collapse
Because I'm on old hboot and latest lollipop.
Petert87 said:
Because I'm on old hboot and latest lollipop.
Click to expand...
Click to collapse
You stated your were on hboot 3.19; which is the latest hboot there is.
redpoint73 said:
You stated your were on hboot 3.19; which is the latest hboot there is.
Click to expand...
Click to collapse
Sorry, there was a misunderstanding. I thought you said the latest was 4.16.xxx but that was the software not hboot. Software is 4.19.161.3
Petert87 said:
Sorry, there was a misunderstanding. I thought you said the latest was 4.16.xxx but that was the software not hboot. Software is 4.19.161.3
Click to expand...
Click to collapse
I see.
Well, it would seem that your firmware is up to date. So I see no reason why TWRP 2.8 would cause any trouble.
What versions of TWRP did you try exactly? I would focus on the current/latest which is 2.8.7.
redpoint73 said:
I see.
Well, it would seem that your firmware is up to date. So I see no reason why TWRP 2.8 would cause any trouble.
What versions of TWRP did you try exactly? I would focus on the current/latest which is 2.8.7.
Click to expand...
Click to collapse
I tried every version until one works and stopped at that one.
Hi, I have a htc one m8 and I believe it is a sprint. I bought this of ebay and did not realise it was a sprint version as I wanted a GSM version. I noticed the phone is s-off and has a cidnum of 11111111.
It has problems. If you boot into fastboot, it will stay in fastboot for say 10 seconds then reboot back into the system automatically. OS is not working correctly.
I have downloaded the up to date sprint RUU and this is titled 'RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe'
I tried flashing this from windows 10 as an exe file but this does not work. (Error 155)
Here is the getvar all data minus imei and serial number:
C:\Users\uggitt\Desktop\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.08.20.0916
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.30.654.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 99000499237405
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d4c3cae5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
I need to get the phone working again and any help would be most appreciated. If anyone needs any further info please let me know.
Mark
Try this RUU: link
lucyr03 said:
Try this RUU: link
Click to expand...
Click to collapse
Thank you and I will give it a go later today
uggitt said:
Thank you and I will give it a go later today
Click to expand...
Click to collapse
Just tried the RUU from your link and I get the same error 155.
uggitt said:
Just tried the RUU from your link and I get the same error 155.
Click to expand...
Click to collapse
Hmm error 155 is related to bootloader status(needs to be locked/relocked) but your device is s-off so you don't need to relock for ruu.
Anyway try to relock your bootloader and come back with the results.
lucyr03 said:
Hmm error 155 is related to bootloader status(needs to be locked/relocked) but your device is s-off so you don't need to relock for ruu.
Anyway try to relock your bootloader and come back with the results.
Click to expand...
Click to collapse
I tried to relock the bootloader but it came back as already locked.
uggitt said:
I tried to relock the bootloader but it came back as already locked.
Click to expand...
Click to collapse
What says in hboot? locked/relocked/unlocked ?
lucyr03 said:
What says in hboot? locked/relocked/unlocked ?
Click to expand...
Click to collapse
locked in hboot
uggitt said:
locked in hboot
Click to expand...
Click to collapse
So.. you have s-off but never unlocked the bootloader? This is strange...
Try to unlock it and see if works.
I have tried to unlock the bootloader but as it keeps rebooting when in Fastboot on the phone after 10-15 seconds. I cannot seem to get the token.
I feel something is wrong with the phones fastboot/hboot but this is only a guess.
I bought the phone like this and I did not s-off etc.
uggitt said:
I have tried to unlock the bootloader but as it keeps rebooting when in Fastboot on the phone after 10-15 seconds. I cannot seem to get the token.
I feel something is wrong with the phones fastboot/hboot but this is only a guess.
I bought the phone like this and I did not s-off etc.
Click to expand...
Click to collapse
I think it's because the battery, I just saw in your getvar the battery reported charged capacity is 0...
lucyr03 said:
I think it's because the battery, I just saw in your getvar the battery reported charged capacity is 0...
Click to expand...
Click to collapse
Ok, phone is on and showing 100%.. Do you think the actual battery is faulty and is causing the problems?
uggitt said:
Ok, phone is on and showing 100%.. Do you think the actual battery is faulty and is causing the problems?
Click to expand...
Click to collapse
If the battery acts normally when phone is on it's not because a battery problem...
The phone stay in hboot without cable connected more than 10 secs?
Sent from my HTC One M9 using Tapatalk
lucyr03 said:
If the battery acts normally when phone is on it's not because a battery problem...
The phone stay in hboot without cable connected more than 10 secs?
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
No, reboots out of hboot with cable or without cable plugged in
uggitt said:
No, reboots out of hboot with cable or without cable plugged in
Click to expand...
Click to collapse
In RUU mode too?(fastboot oem rebootRUU)
Sent from my HTC One M9 using Tapatalk
lucyr03 said:
In RUU mode too?(fastboot oem rebootRUU)
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Hi Just tried and goes into ruu mode and then restarts after say 10 seconds
uggitt said:
Hi Just tried and goes into ruu mode and then restarts after say 10 seconds
Click to expand...
Click to collapse
That's strange behavior... Idk what to say..
Sent from my HTC One M9 using Tapatalk
lucyr03 said:
That's strange behavior... Idk what to say..
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thanks for trying and for your help. I think it is destined for the bin....
uggitt said:
I have downloaded the up to date sprint RUU and this is titled 'RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe'
I tried flashing this from windows 10 as an exe file but this does not work. (Error 155)
Click to expand...
Click to collapse
You need to flash firmware 6.20.651.3. before the RUU will install. It's a peculiar requirement on US Marshmallow RUUs, that updating by RUU from any lower version (Lollipop, Kitkat) you need to flash firmware first, before RUU, otherwise you will have Error 155.
Firmware and instructions for flashing if can be found here (as well as all Sprint RUUs):
https://forum.xda-developers.com/showthread.php?t=2729173
But if the phone will not stay in hboot (or RUU mode) it may be a problem flashing firmware and/or RUU. May possibly even brick the phone. If flashing firmware or RUU, the process is interrupted when updating hboot partitions, a brick is almost certain. But on the other hand, it looks like you are close to binning it anyway, so maybe the risk is not significant (and worth trying). It's up to your judgment.
redpoint73 said:
You need to flash firmware 6.20.651.3. before the RUU will install. It's a peculiar requirement on US Marshmallow RUUs, that updating by RUU from any lower version (Lollipop, Kitkat) you need to flash firmware first, before RUU, otherwise you will have Error 155.
Firmware and instructions for flashing if can be found here (as well as all Sprint RUUs):
https://forum.xda-developers.com/showthread.php?t=2729173
But if the phone will not stay in hboot (or RUU mode) it may be a problem flashing firmware and/or RUU. May possibly even brick the phone. If flashing firmware or RUU, the process is interrupted when updating hboot partitions, a brick is almost certain. But on the other hand, it looks like you are close to binning it anyway, so maybe the risk is not significant (and worth trying). It's up to your judgment.
Click to expand...
Click to collapse
Thank you for the reply and I may give it a go later when back from work
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Jabbah said:
Hi all.
Got a HTC one m8 in and it appears to be stuck on the HTC screen, I can get into bootloader fine, have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Thanks in advance.
Click to expand...
Click to collapse
What does it say next to "OS" in your bootloader menu?
Jabbah said:
have tried to reflash via SD card but i get a CID error.
Can anyone direct me to what ROM i need to be installing? Its a UK version.
Click to expand...
Click to collapse
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
redpoint73 said:
Tried to flash what? Can't troubleshoot what you did wrong, unless you tell is what you tried to flash. RUU, firmware.zip, or something else? What is the version number and file name?
That is in addition to the info requested in the previous reply.
Also, if you know how, do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the device.
Click to expand...
Click to collapse
Tried to flash a stock UK rom.
I have no idea how to use that command sorry.
os is 6.12.61.4
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Jabbah said:
Tried to flash a stock UK rom.
Click to expand...
Click to collapse
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
redpoint73 said:
RUU, firmware.zip, or something else?
What is the version number and file name?
Click to expand...
Click to collapse
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
redpoint73 said:
Still too vague for us to have any idea what you tried to flash.
I asked some specific questions for a reason; some of which you seem to have missed or ignored. I'm not just typing to exercise my fingers!
"Stock UK ROM" can mean a number of things. If you are talking about RUU, then calling it a "stock ROM" is not the right term (and confusing) since RUU is a complete image containing something like 41 partitions, with the ROM being only one of those partitions.
In fact, if you are referring to RUU, I don't think your version M8 (or most UK versions, for that matter) has a valid RUU. So you are likely in fact not even trying to flash a stock UK ROM. Which also explains the CID error.
On a positive note, good work figuring out how to do fastboot getvar all. If you can provide more info on what you tried to flash, we can make some progress!
Click to expand...
Click to collapse
Thanks for the replies, ive actually gotten somewhere today, Ive installed twrp, and installed the latest Lineage ROM which booted fine .
But.... Not detecting sim card
Always something haha
Another option (especially now that you have unlocked the bootloader, and installed TWRP), is restore stock TWRP backup 6.12.61.4 from here:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
No need to do Step 3, nor Steps 10 or after (only relevant to get OTA updates - which no longer applies to this device). Just reboot.
Jabbah said:
Thanks for the replies
Click to expand...
Click to collapse
There is a button for that.
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
David.
Jabbah said:
Quick update, Restored stock TWRP as you suggested, performed simunlock and am now a happy chappy with a working M8
Now, Whats the best ROM to use for it ? Is it worth installing Lineage ROM?
Click to expand...
Click to collapse
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
redpoint73 said:
Glad the TWRP restore worked out for you.
No such thing as a "best ROM". Each individual user has different preferences and tastes. That's the reason there are different ROM choices. If there was a "best ROM", nobody would ever need anything else, right?
I am not personally a Lineage user (so good example right there how one person's opinion may not apply to you). But if you flash it again, I assume you can (or will) have the same problem with SIM not detected. I think I've seen other folks with the problem on Lineage (again, I don't really keep up with that ROM), so you should check the thread to see if there is a fix for that issue.
Click to expand...
Click to collapse
Got around the sim not detected issue, the phone was simlocked to orange, it just didnt pop up with the enter unlock code dialogue.
Ill try a few see what they are like
Thanks again for your help.
Jabbah said:
Got around the sim not detected issue, the phone was simlocked to orange.
Click to expand...
Click to collapse
Understood. I would not have expected the "SIM not detected" error in that case. So thanks for clarifying.
Jabbah said:
it just didnt pop up with the enter unlock code dialogue.
Click to expand...
Click to collapse
Stock (Sense) ROM is needed to unlock SIM. Which you either figured out, or stumbled upon the solution by luck! :good:
hi all
the mother in law gave me her broken htc one m8 phone too look at as it was stuck on the htc boot screen.
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
the problem i am now having is that the phone wont let me choose a network mode as its blanked off and not able to choose, which also means when i enter a sim it just doesnt work.
i have done a fastboot getvar all and details follow
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
any help would be greatfully appreciated
First of all, you posted in the General M8s section. The M8s is a variant with different hardware. You have the M8 (no "s") which has it's own General forum section, but you should post questions like this in the M8 Q&A section, anyway. Don't make another post, I'll ask the mods to move this one to the right place.
s84taylo41984 said:
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
Click to expand...
Click to collapse
Those are not RUU (as your thread title states). An RUU is an official HTC tool, which is run from bootloader. What you linked are stock TWRP backups, which are flashed using TWRP.
Which TWRP backup version number did you flash? What version TWRP did you use?
---------- Post added at 01:02 PM ---------- Previous post was at 12:59 PM ----------
s84taylo41984 said:
(bootloader) imei:
Click to expand...
Click to collapse
Is there an IMEI number listed? I know it's the right thing to leave this out, when posting online. But just want to make sure that is the case (and it is not actually missing from the getvar output as you see it). I don't want or need to know the IMEI number, just whether you can actually see it or not.
I realised i posted in the wrong section about 1 hour ago when i was looking through some other posts on here and noticed there was a differnce in the m8 and m8s.
yes IMEI is there. i just blanked it off when posting
Quote:
Originally Posted by s84taylo41984
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
https://forum.xda-developers.com/htc...-twrp-t3086860.
Those are not RUU (as your thread title states). An RUU is an official HTC tool, which is run from bootloader. What you linked are stock TWRP backups, which are flashed using TWRP.
Click to expand...
Click to collapse
Oh i thought that they all worked the same, didnt realise they was so different!
Which TWRP backup version number did you flash? What version TWRP did you use?
Click to expand...
Click to collapse
I used TWRP 3.3.1-0 amd followed the whole of that guide, i thought it was RUU not stock.
s84taylo41984 said:
after abit of searching around i got the phone into bootloader and managed to get the phone back up and running after following the below page to get it working again well mostly.
Click to expand...
Click to collapse
What does that mean "mostly" working?
Seems you are going about this a bit haphazardly. You didn't answer all my questions, but instead decided to search around for you own solutions (we may have gotten you there faster).
redpoint73 said:
What does that mean "mostly" working?
Seems you are going about this a bit haphazardly. You didn't answer all my questions, but instead decided to search around for you own solutions (we may have gotten you there faster).
Click to expand...
Click to collapse
Mostly working as in i wasnt able to get the wifi to enable on the phone until i flashed the TWRP Backup collection in 3, and then flashed the stock recovery image's from post 4 and the signed firmware in post 5 all with the 6.12.401.4 and CID HTC__001
MID 0P6B10000
s84taylo41984 said:
Mostly working as in i wasnt able to get the wifi to enable on the phone until i flashed the TWRP Backup collection in 3, and then flashed the stock recovery image's from post 4 and the signed firmware in post 5 all with the 6.12.401.4 and CID HTC__001
MID 0P6B10000
Click to expand...
Click to collapse
WiFi not turning on is due to restoring the wrong stock TWRP backup which does not correspond to the installed firmware. As I mentioned, this is something we could have identified much earlier, if you supplied the requested info (questions I asked days ago).
what questions did you want me to answer to answer days ago??
is there anything that can be done for me to get the phone working again???
s84taylo41984 said:
what questions did you want me to answer to answer days ago??
Click to expand...
Click to collapse
redpoint73 said:
Which TWRP backup version number did you flash?
Click to expand...
Click to collapse
s84taylo41984 said:
is there anything that can be done for me to get the phone working again???
Click to expand...
Click to collapse
Not clear to me what doesn't work now. You already said the WiFi was fixed once you flashed the signed firmware.
redpoint73 said:
Not clear to me what doesn't work now. You already said the WiFi was fixed once you flashed the signed firmware.
Click to expand...
Click to collapse
Yes the WIFI started working after flashing the signed firmware but as posted in my original post, i am unable to select network mode to choose a network even with a sim card inserted it just says no sim card, emergency calls only!
The TWRP backup version i flashed was 6.12.401.4
s84taylo41984 said:
Yes the WIFI started working after flashing the signed firmware but as posted in my original post, i am unable to select network mode to choose a network even with a sim card inserted it just says no sim card, emergency calls only!
Click to expand...
Click to collapse
Not sure I necessarily have an answer for you. But at least so if I understand the sequence of events correctly:
1) You received the phone in "no boot" condition.
2) (Unlocked bootloader?). Restored stock TWRP backup 6.12.401.4 using TWRP 3.3.1-0.
3) Able to boot the phone, but no SIM and no WiFi.
4) (Relocked bootloader presumably). Flashed firmware 6.12.401.4. Also flashed stock recovery.
5) WiFi is not working, still no SIM.
redpoint73 said:
Not sure I necessarily have an answer for you. But at least so if I understand the sequence of events correctly:
1) You received the phone in "no boot" condition.
2) (Unlocked bootloader?). Restored stock TWRP backup 6.12.401.4 using TWRP 3.3.1-0.
3) Able to boot the phone, but no SIM and no WiFi.
4) (Relocked bootloader presumably). Flashed firmware 6.12.401.4. Also flashed stock recovery.
5) WiFi is not working, still no SIM.
Click to expand...
Click to collapse
i never unlocked the bootloader just booted the phone into bootloader
the WiFi is working, just no SIM
s84taylo41984 said:
i never unlocked the bootloader just booted the phone into bootloader
Click to expand...
Click to collapse
Was the phone already bootloader unlocked when you received it? Does it say LOCKED, UNLOCKED, or RELOCKED near the top of the bootloader screen?
You can't install TWRP with a locked bootloader (while s-on).
It says RELOCKED now when i put the phone in to bootloader. I have no idea if the bootloader was unlocked when i recieved the phone i cant remember
s84taylo41984 said:
It says RELOCKED now when i put the phone in to bootloader. I have no idea if the bootloader was unlocked when i recieved the phone i cant remember
Click to expand...
Click to collapse
The only way it could have been bootloader unlocked when you got the device, and relocked after, is if you relocked it yourself, with fastboot command: fastboot oem lock
Did your mother-in-law or someone she know, mod the phone? Or did she obtain it used or from a 3rd party vendor? If it was RELOCKED when you received it, it was definitely modded by someone at some point.
The only way the bootloader can be locked (or relocked) and you can still flash TWRP, is if the device is s-off, but has the security flag spoofed to say it is s-on.
redpoint73 said:
The only way it could have been bootloader unlocked when you got the device, and relocked after, is if you relocked it yourself, with fastboot command: fastboot oem lock
Did your mother-in-law or someone she know, mod the phone? Or did she obtain it used or from a 3rd party vendor? If it was RELOCKED when you received it, it was definitely modded by someone at some point.
The only way the bootloader can be locked (or relocked) and you can still flash TWRP, is if the device is s-off, but has the security flag spoofed to say it is s-on.
Click to expand...
Click to collapse
I did relock it using the fastboot oem lock command.
She did have somebody look at it before me and it was the same thing.