Google play issue - One (M8) Q&A, Help & Troubleshooting

I bought a used M8 At&t I don't have yet. But the seller says the following about the phone. Google Play crashes during setup, preventing setup from completing. The phone looks great. Is this an easy fix?

Sounds like a software problem, this can be easy to fix with a ruu.

Can you please recommend what I would need for att variant? Should I just get the latest nougat? This ruu correct 6.20.502.5is? Just htc rom update that's it? In fastboot?

cell2011 said:
Can you please recommend what I would need for att variant? Should I just get the latest nougat? This ruu correct 6.20.502.5is? Just htc rom update that's it? In fastboot?
Click to expand...
Click to collapse
First, we need some informations about your device, you have it now?

lucyr03 said:
First, we need some informations about your device, you have it now?
Click to expand...
Click to collapse
HTC-One-M8-0P6B120-32GB-

cell2011 said:
HTC-One-M8-0P6B120-32GB-
Click to expand...
Click to collapse
Boot in hboot and do "fastboot getvar all" then post the result here(remove imei,sn)

lucyr03 said:
Boot in hboot and do "fastboot getvar all" then post the result here(remove imei,sn)
Click to expand...
Click to collapse
I dont hve the phone for a couple of days. i think ill try the RUU file and see how that goes

cell2011 said:
Can you please recommend what I would need for att variant? Should I just get the latest nougat? This ruu correct 6.20.502.5is? Just htc rom update that's it? In fastboot?
Click to expand...
Click to collapse
There is no official (HTC) Nougat software/firmware for this device. They stopped at Marshmallow, which 6.20.502.5 is.
RUU is a full stock/factory image. It will wipe all data on the phone (probably not a bad thing in your case) as well as re-write all partitions to "stock" condition. If your problem is with software (and I'm thinking it probably is), the RUU will likely fix it.
I assume you have the .exe format RUU (which is the most likely case). In which case, connect the phone to PC. Run the RUU, and it's pretty self-explanatory from there. Having the hone booted to OS should be okay, but bootloader-fastboot mode is even better.
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
cell2011 said:
i think ill try the RUU file and see how that goes
Click to expand...
Click to collapse
The RUU may or may not work, depending on the phone's current condition. Which is why lucyr03 asked for the getvar data, so we can give you more specific advice.

redpoint73 said:
There is no official (HTC) Nougat software/firmware for this device. They stopped at Marshmallow, which 6.20.502.5 is.
RUU is a full stock/factory image. It will wipe all data on the phone (probably not a bad thing in your case) as well as re-write all partitions to "stock" condition. If your problem is with software (and I'm thinking it probably is), the RUU will likely fix it.
I assume you have the .exe format RUU (which is the most likely case). In which case, connect the phone to PC. Run the RUU, and it's pretty self-explanatory from there. Having the hone booted to OS should be okay, but bootloader-fastboot mode is even better.
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
The RUU may or may not work, depending on the phone's current condition. Which is why lucyr03 asked for the getvar data, so we can give you more specific advice.
Click to expand...
Click to collapse
Does this help MPN
6217A and UPC
0821793039523. I dont have the phone yet. This is a pic of the phone and condition i would imagine

cell2011 said:
Does this help MPN
6217A and UPC
0821793039523. I dont have the phone yet. This is a pic of the phone and condition i would imagine
Click to expand...
Click to collapse
No, none of that really helps. Once you have the phone, you can do fastboot getvar all, give us the results, and we can advise you further.

Got my phone but it's HTC Europe. Came with LeeDroid installed and rooted. I'm using At&t carrier. It works 4g and everything but what nougat or Oreo rom could I use?

cell2011 said:
Got my phone but it's HTC Europe. Came with LeeDroid installed and rooted. I'm using At&t carrier. It works 4g and everything but what nougat or Oreo rom could I use?
Click to expand...
Click to collapse
Use what rom you want, I think Oreo is just lineageos.

Related

Big problem about S-off

Hello
I have bootloader unlocked, rooted HTC one M8. I want to use android revolution hd and to do that I need to flash a new firmware. I need to do "s-off". However I tried I failed that with "runrummer". I get this fail : (I dont wanna pay 25$ for sunshine)
Pouring (1) ......................
Pouring (2)
WTF: what are you doing.
Press Enter to exit.
I want to do s-off so badly and I can give more info. about the phone.
Thanks a lot
Runrunner doesn't work with the M8. Sunshine is the only working method
EddyOS said:
Runrunner doesn't work with the M8. Sunshine is the only working method
Click to expand...
Click to collapse
So you say There is no other way execpt sunshine ?
tugratolunay said:
So you say There is no other way execpt sunshine ?
Click to expand...
Click to collapse
Yep man. I use s-on for its ok all good
leos0000 said:
Yep man. I use s-on for its ok all good
Click to expand...
Click to collapse
That's nice, but you need to be S-Off to do certain things, like manually flashing firmware without reverting to stock, or using firmware meant for carriers other than yours when they update before your carrier.
There are other advantages as well, but these are the ones that S-Off is most used for.
tugratolunay said:
So you say there is no other way except Sunshine ?
Click to expand...
Click to collapse
That's exactly what I'm saying
tugratolunay said:
WTF: what are you doing.
Click to expand...
Click to collapse
"WTF what are you doing" indeed. Rumrunner never worked for this phone. It was for the M7. Firewater (related, but different from rumrunner) was for earlier M8 versions. It was an online service, and will no longer work now that the dev has stopped supporting it (so don't even bother asking).
For many variants, s-off is not needed to update firmware (as long as Lollipop has been released for your variant). You can just return to stock ROM and stock recovery, and OTA to Lollipop in order to update your firmware.
redpoint73 said:
"WTF what are you doing" indeed. Rumrunner never worked for this phone. It was for the M7. Firewater (related, but different from rumrunner) was for earlier M8 versions. It was an online service, and will no longer work now that the dev has stopped supporting it (so don't even bother asking).
For many variants, s-off is not needed to update firmware (as long as Lollipop has been released for your variant). You can just return to stock ROM and stock recovery, and OTA to Lollipop in order to update your firmware.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2694994
I have used this rom (Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9) and I still cant use wifi or I cant restart the phone it stucks at HTC logo. Could you please help me about finding correct stock rom ? or is there only 1 stock rom I really dont know what to do so far or how do I return back..
tugratolunay said:
http://forum.xda-developers.com/showthread.php?t=2694994
I have used this rom (Stock ROM's (Android 4.4.4 + HTC Sense 6.0 | Latest: 3.28.401.9) and I still cant use wifi or I cant restart the phone it stucks at HTC logo. Could you please help me about finding correct stock rom ? or is there only 1 stock rom I really dont know what to do so far or how do I return back..
Click to expand...
Click to collapse
There are different stock ROMs for different CIDs. Plus, if you have no WiFi, and extreme long boot times, its due to your firmware not being supported by the ROM. You need to find the stock ROM for your current firmware and CID. Then you also need to flash the corresponding stock recovery. After that, you can OTA to the latest firmware.
What is your CID, hboot number, and radio number?
redpoint73 said:
There are different stock ROMs for different CIDs. Plus, if you have no WiFi, and extreme long boot times, its due to your firmware not being supported by the ROM. You need to find the stock ROM for your current firmware and CID. Then you also need to flash the corresponding stock recovery. After that, you can OTA to the latest firmware.
What is your CID, hboot number, and radio number?
Click to expand...
Click to collapse
HBoot 3.16.0.0000
Radio-1.16.21331931.LA11G
Cid : CWS_001
by the way I bought this phone when I was in USA and I bought it from AT&T I dont know if it makes difference. I have a custom rom (4.4.2) its the only rom that I can use the phone and this rom is sux :'(
tugratolunay said:
HBoot 3.16.0.0000
Radio-1.16.21331931.LA11G
Cid : CWS_001
by the way I bought this phone when I was in USA and I bought it from AT&T I dont know if it makes difference.
Click to expand...
Click to collapse
Not only is that make a difference, it makes it easy to update your firmware. Just relock the bootloader and run the new Lollipop RUU: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Backup any important personal data before RUU, as RUU will wipe the phone.
redpoint73 said:
Not only is that make a difference, it makes it easy to update your firmware. Just relock the bootloader and run the new Lollipop RUU: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
Backup any important personal data before RUU, as RUU will wipe the phone.
Click to expand...
Click to collapse
Would you mind I want you to explain the process how to do it or can you please give me link to follow the process?
tugratolunay said:
Would you mind I want you to explain the process how to do it or can you please give me link to follow the process?
Click to expand...
Click to collapse
1) To lock bootloader: Connect phone to PC (PC required for RUU). Boot phone into bootloader-fastboot mode. Open command prompt on computer, and type command: fastboot oem lock
2) Download RUU onto PC. With phone connected, run the RUU exectuble program on the PC and follow the instructions given.
3) Done, drink beer
A little more detail is given here under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
But seriously, the RUU is a self-explanatory program. It will tell you to confirm a couple dialogue boxes. But aside from that, the program will install a completely clean factory Lollipop software image.
Option Step) Unlock the bootloader again via HTCDev.com, then flash TWRP if you want to root or flash a custom ROM.
redpoint73 said:
1) To lock bootloader: Connect phone to PC (PC required for RUU). Boot phone into bootloader-fastboot mode. Open command prompt on computer, and type command: fastboot oem lock
2) Download RUU onto PC. With phone connected, run the RUU exectuble program on the PC and follow the instructions given.
3) Done, drink beer
A little more detail is given here under "Manual system update instructions": http://www.htc.com/us/support/htc-one-m8-att/news/
But seriously, the RUU is a self-explanatory program. It will tell you to confirm a couple dialogue boxes. But aside from that, the program will install a completely clean factory Lollipop software image.
Option Step) Unlock the bootloader again via HTCDev.com, then flash TWRP if you want to root or flash a custom ROM.
Click to expand...
Click to collapse
Cant I use the same unlock_code.bin ? and Will the at&t app be back? and will my SD card will be safe? Should I be in fastboot while doing RUU? or just homescreen?
Sorry for bothering you too much :/
***Tampered***
***relocked***
***security Warning**
M8_ul_ca
.
.
.
I cant open my phone, it always comes at this screen (bootloader). Is that normal?
tugratolunay said:
Cant I use the same unlock_code.bin ?
Click to expand...
Click to collapse
You can try it. It certainly doesn't hurts, as it only takes a single fastboot command, and would be faster than going through the whole HTCDev.com process (although that really doesn't take that much time, either).
I know using the same token has worked on past HTC devices. But I haven't seen much (if any) success on the M8. Most (or all?) folks have had to get a new token in order to unlock.
tugratolunay said:
Will the at&t app be back?
Click to expand...
Click to collapse
Yes, whatever AT&T apps are present on the stock Lollipop AT&T image will be on your phone. Simply root and delete/freeze, or install a custom ROM to be rid of the AT&T bloat.
tugratolunay said:
will my SD card will be safe?
Click to expand...
Click to collapse
You mean the removable SD? It should be safe. But you can always take it out before RUU to be sure it doesn't get touched by RUU.
Any other data on the phone (including the "virtual SD" AKA internal storage) should be backed up, if you want to keep it. Internal storage "might" be okay, but I'd back up anything you want to keep, just in case.
tugratolunay said:
Should I be in fastboot while doing RUU? or just homescreen?
Click to expand...
Click to collapse
Usually booted into OS works. But some folks have had to put the phone in fastboot mode.
---------- Post added at 04:39 PM ---------- Previous post was at 04:37 PM ----------
tugratolunay said:
Sorry for bothering you too much :/
Click to expand...
Click to collapse
Its no bother. I enjoy helping others.
I only ask in return you click the "Thanks" button for any posts you found helpful.
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
tugratolunay said:
***Tampered***
***relocked***
***security Warning**
M8_ul_ca
.
.
.
I cant open my phone, it always comes at this screen (bootloader). Is that normal?
Click to expand...
Click to collapse
Yes, that is normal. Its expected that RUU will be run once you relock, so it makes the phone this way.
I always forget this, since I s-off my devices (no relocking necessary to RUU with s-off)
redpoint73 said:
I always forget this, since I s-off my devices (no relocking necessary to RUU with s-off)
Click to expand...
Click to collapse
After installing this RUU I will have original At&t rom and unroot, relocked bootloader phone. and it will be 5.0.1 lollipop. Am I right? and so firmware will be upgraded tho? That means I can Unlock it, root it and install that android revolution HD rom without having problems.
tugratolunay said:
After installing this RUU I will have original At&t rom and unroot, relocked bootloader phone. and it will be 5.0.1 lollipop. Am I right? and so firmware will be upgraded tho? That means I can Unlock it, root it and install that android revolution HD rom without having problems.
Click to expand...
Click to collapse
Yes, yes, and yes.
The only thing above that isn't completely correct, if that after you unlock the bootloader again, just install custom recovery and flash ARHD. No need to root before flashing a custom ROM. Installing a ROM wipes whatever you did with root anyway, and custom ROMs are always pre-rooted. So rooting manually is an unnecessary step. You only need to root "manually" if you are keeping the stock ROM.

[SOLVED] T-Mobile M8 Stuck In Recovery With ReLocked Bootloader and No ROM!

The title basically says it all but I'll describe what I did so hopefully you guys can help.
Today I got tired of the ROM I was running and I figured I'd update my firmware before I flashed a new one just cause I hadn't done it in months. So I went and followed this guide: http://forum.xda-developers.com/showthread.php?t=2696282
I used this firmware: https://www.androidfilehost.com/?w=files&flid=32788
My CID is T-MOB010 just like the firmware's and I thought it would be a pretty simple thing, so I got to work.
First I rebooted to fastboot USB and did fastboot getvar all to make sure everything lined up, then I relocked the bootloader and did fastboot oem rebootRUU, all successfully.
Then I flashed the firmware and it all went great but I forgot to flash it a second time. I'm not sure if it's required, but anyway...
After it flashed successfully I did a fastboot reboot and my phone tried to reboot but it stalled on the white HTC splash screen, then went black, then the splash screen returned, then black, then it went into the stock recovery.
The stock recovery functions just fine and I attempted to just clear the cache and reboot but it did the exact same thing.
I don't currently have a stock Nandroid or RUU on my phone and I'm not even sure I have a way to get one on there besides using someone else's phone to put one on my SD.
Can anyone help me out? Is it even possible to get out of this? My bootloader is relocked and my phone can't get S-OFF (tried awhile ago multiple times). As of now I am all out of ideas/experience so I'm hoping you guys can help me. Thank you!!
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Update: Once I got into hboot all was well, I just flashed TWRP again and got it going. Thanks everyone for the help!
Did you get it going again?
_jakeryan said:
I don't currently have a stock Nandroid or RUU on my phone
Click to expand...
Click to collapse
Just use the official RUU.exe which runs from a PC (with phone connected), not from the phone.
http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will also update your firmware.
Also, the firmware you linked is not the latest. Its the Android 4.4.4 firmware. The 5.0 (Lollipop) firmware would be 4.20.531.4
hack14u said:
Did you get it going again?
Click to expand...
Click to collapse
I did! Thank you redpoint for the help anyway!
_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Maybe add 'solved' to the topic? If that's still a thing.
_jakeryan said:
I did! Thank you redpoint for the help anyway!
Click to expand...
Click to collapse
Its not what your top post says, so its not clear whether you were trying to put the RUU.exe on the phone (which is incorrect), unsuccessful in putting on the phone or running an RUU.zip, or did the latter in addition to trying to run the RUU.exe from the PC (which was not originally mentioned). If the last one didn't work, it would help to have more details on failure mode, error messages, etc.
---------- Post added at 09:25 AM ---------- Previous post was at 09:23 AM ----------
_jakeryan said:
UPDATE: I got myself into the HBOOT so I think I should be good now but I'll keep this around just in case.
Click to expand...
Click to collapse
So is your issue resolve or not? Able to get a ROM or nandroid on the phone and flash/restore it?
---------- Post added at 09:26 AM ---------- Previous post was at 09:25 AM ----------
voidzero said:
Maybe add 'solved' to the topic? If that's still a thing.
Click to expand...
Click to collapse
Not everyone does it, but its certainly good to do, and still done from time to time. Its helpful so folks don't click on a link, intending to help someone that doesn't need the help anymore.
Same kinda problem.
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??
morgansgrandad said:
I'm stuck in bootloader.
Any key I just brings me back to this again.
Even in HBOOT selecting Recovery or Factory reset does nothing other than bring up this screen.
Powering down and then on again has the same result.
I was trying to get back to stock. Typed in fastboot oem lock and after that... the problem started!!
Any ideas??
Click to expand...
Click to collapse
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.
redpoint73 said:
This is intentional. When you relock the bootloader, it renders the phone unbootable and expects the RUU to be run.
Click to expand...
Click to collapse
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!
morgansgrandad said:
Ok. I'd downloaded what I assume is the correct RUU.exe. Ran it from the computer and I get a 131 error. Not the correct RUU !!
Stuck for a solution now!!
Click to expand...
Click to collapse
You shouldn't be assuming what RUU to run. What is your CID and hboot number? What RUU did you try to run?
HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe
morgansgrandad said:
HBOOT is 3.19.0.0000 CID, can't find.
RUU is M8_4.16.401.10_Europe.exe
Click to expand...
Click to collapse
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.
redpoint73 said:
The OS number (3.32.206.9) shown on your hboot screen (pic in your top post) indicates that is not the right RUU. The number in the x.xx.206.x is carrier specific,and seems to indicate that your phone is the O2 UK version. Running an RUU with version x.xx.401.x won't work. The number in the "401" spot would need to "206" for it to be the right RUU.
Not sure, but I don't think your CID has RUUs. If that is the case, your best bet it to unlock the bootloader again, flash TWRP back to the phone, and restore a nandroid with your software number (3.32.206.9) if you can find it. Then flash stock recovery back to the phone. That is as close to "stock" as you will get, if there is no RUU for your CID version.
Click to expand...
Click to collapse
Thanks redpoint73. Looks like that's the only way to go!!
By looking at the radio, you need the Euro Version RUU. Looks like we gotta be detectives sometimes, lol.
Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??
morgansgrandad said:
Ok, I've unlocked the bootloader and am back to where it was.
It's running 5.0.1, Sense 6.0 and Android Revolution HD 34.6 by mike1986
I would like to clear that off and get back to stock with OTT updates.
Revolution HD 34.6 seems to use an awful lot of data. My other M8 has stock on-board, has identical apps etc and doesn't use nearly as much data as this one!!
Any further ideas??
Click to expand...
Click to collapse
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/
hack14u said:
Why not just set it up for Dev / Unlocked Edition?
http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
I'm downloading that now. BUT...........
Because of all my faffing on!! there's NO OS on the phone.
I'm really struggling now:crying:
This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.
And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne
morgansgrandad said:
This is my position now. Totally unusable phone!!
I would appreciate ANY help on getting back to as near as normal as possible.
Thank you.
I should add, the RUU messages are from trying post #16.
Click to expand...
Click to collapse
What hack14u neglected to mention, is that to run another version's RUU, you need s-off ($25 by sunshine), and then you need to change your MID and CID.
Relocking the bootloader (to run RUU) renders the phone with no OS, this is by design.
---------- Post added at 09:41 AM ---------- Previous post was at 09:34 AM ----------
morgansgrandad said:
And the saga continues!
I found a nandroid backup with the same s/w number as mine, downloaded it from MEGA (it seemed to d/l ok).
When I ran it through TWRP I got signature verification failed.
This phone could end up in the depths of the river Tyne
Click to expand...
Click to collapse
Hang in there, modding phones can often be an exercise in frustration. But the phone is quite recoverable, as long as you perform the correct steps.
A nandroid is not a flashable zip (such as a ROM). It needs to be restored in a very different way, its described in Post 3 of the stock nandroid thread (assuming that is where you go it from) under Question & Answers.
To summarize, you need to:
1) Unpack the zipk, which is a number of folders
2) Move the folders to the proper location on the phone's internal storage (removable SD is also possible, if you setup TWRP to back and restore to that location)
The exact location if very important (its described in Post 3 of the stock nandroid thread), since when restoring a nandroid, TWRP will not see the file to restore if you have it wrong. This is in direct contrast to installing a ROM zip, in which TWRP allows you to browse anywhere on the storage to find the file to flash.
3) Choose the menu option to RESTORE, not INSTALL

Flashing a firmware

Hello
My htc one m8 is the Asian version (HTC__044) , upon using getvar all, I noticed that my version-main was missing along with the os in hboot. If I were to flash a firmware, would I need to relock the bootloader? Would I lose my data on locking the bootloader? Also, im on base .401 , would I directly be able to flash a .707?
Thanks in advance.
wasdapple said:
If I were to flash a firmware, would I need to relock the bootloader?
Click to expand...
Click to collapse
If s-on, yes. Otherwise if s-off, no.
Also, be aware that with s-on you can only flash a firmware that is HTC signed/encrypted. Some are not, and require s-off.
wasdapple said:
Would I lose my data on locking the bootloader?
Click to expand...
Click to collapse
Yes.
wasdapple said:
Also, im on base .401 , would I directly be able to flash a .707?
Click to expand...
Click to collapse
How are you determining 401? From what I'm seeing, the stock software/firmware for your CID should be 707.
You should be able to flash 707 firmware (assume you want to update to Lollipop) on your version, provided the previously mentioned requirements are met.
redpoint73 said:
If s-on, yes. Otherwise if s-off, no.
Also, be aware that with s-on you can only flash a firmware that is HTC signed/encrypted. Some are not, and require s-off.
Yes.
How are you determining 401? From what I'm seeing, the stock software/firmware for your CID should be 707.
You should be able to flash 707 firmware (assume you want to update to Lollipop) on your version, provided the previously mentioned requirements are met.
Click to expand...
Click to collapse
Thanks for replying. I believe it may have been the rom ive installed that changed my firmware, along with the fact it writes .401 on my software information page. Yes the default firmware should be .707 which I believe is also the main cause of my inability to connect to 4g in my area.
So assuming I find a signed firmware for .707 I would simply be able to flash it on the .401? Or would I have to still relock my bootloader.
Also, would the empty os/ version-main be a problem and if so how do I fix it.
Thanks for replying as you've also helped me a great deal the previous time.
wasdapple said:
I believe it may have been the rom ive installed that changed my firmware, along with the fact it writes .401 on my software information page.
Click to expand...
Click to collapse
Flashing a ROM will not change your firmware. It does change software number, so if that is where you are getting 401 from, that is normal. Software number is just the base of your current ROM, not your firmware number.
Your firmware number is indicated on your bootloader screen under "OS" and also as "main version" when doing getvar all.
wasdapple said:
So assuming I find a signed firmware for .707 I would simply be able to flash it on the .401? Or would I have to still relock my bootloader.
Click to expand...
Click to collapse
Are you s-on or s-off?
If still s-on, there is no way you could have ever flashed a 401 firmware on your phone. I still think you are confused between software and firmware numbers, and I don't guess that you ever flashed a 401 firmware.
If you are s-on, I still think you are on 707 firmware, and there is some other factor causing your 4G problem.
Yes, you need to relock your bootloader to flash 707 firmware while s-on. If you are s-off, you don't need to relock the bootloader.
wasdapple said:
Also, would the empty os/ version-main be a problem and if so how do I fix it.
Click to expand...
Click to collapse
It shouldn't be a problem. It will be fixed if you flash a firmware.
This bug was caused by older versions of TWRP. If you flash a current version of TWRP after flashing firmware, the problem should not re-occur.
---------- Post added at 10:19 AM ---------- Previous post was at 10:17 AM ----------
wasdapple said:
Thanks for replying as you've also helped me a great deal the previous time.
Click to expand...
Click to collapse
We always like repeat customers, and satisfied ones.
So is it possible that I am actually on 707 but my rom is making it show 401? Im terribly sorry for my lack of understanding of this whole situation.
Would using the twrp app on the play store update twrp? It should fix the empty main-version ?
wasdapple said:
So is it possible that I am actually on 707 but my rom is making it show 401? Im terribly sorry for my lack of understanding of this whole situation.
Click to expand...
Click to collapse
I know in the past, folks have often used the word "firmware" to mean the same as the ROM. But you should probably erase that notion from your mind. On this device, the word "firmware" is used specifically to partitions that are not flashed when you flash a ROM, and include hboot, radio, WiFi, Bluetooth, and others.
Yes, your firmware may still be 707 (which can normally be found as OS number on hboot screen, or main version when doing getvar all); while your software (ROM) which is shown in Settings>About>Software information can be 401. Firmware and ROM are 2 completely different things.
I've asked twice now, are you s-on or s-off?
wasdapple said:
Would using the twrp app on the play store update twrp? It should fix the empty main-version ?
Click to expand...
Click to collapse
TWRP Manager app will update TWRP, yes.
You can also just download the latest version and flash with fastboot, which is my preferred method: https://twrp.me/devices/htconem8gsm.html
However, this alone won't fix the issue of main version missing, I don't believe. It will only stop if from re-occurring. But the only way to get the main version back is to flash a firmware. After that, having an updated TWRP will stop if from main version displaying "blank" again. If you use an old TWRP, it will blank out the main version again.
Get it?
I'm sorry I kept forgetting to reply to that, I am actually s-on.
So for instance I want to be back on 707 I should just revert to rooted stock?
wasdapple said:
I'm sorry I kept forgetting to reply to that, I am actually s-on.
Click to expand...
Click to collapse
Than its simply impossible for you to ever have flashed a 401 firmware. Some of the firmware partitions (hboot, radio) are write protected with s-on, and can only be flashed with your CID version firmware (707).
wasdapple said:
So for instance I want to be back on 707 I should just revert to rooted stock?
Click to expand...
Click to collapse
Yes, rooted or unrooted should be fine.
But you will want to make sure your firmware and software versions match up. What are your hboot and radio numbers? Do you remember if you were on Lollipop before unlocking the bootloader?
My hboot would be 3.19.0.0000 and my radio is 1.25.21331147A1.06G
Yep I was on lollipop before unlocking my bootloader.
wasdapple said:
My hboot would be 3.19.0.0000 and my radio is 1.25.21331147A1.06G
Yep I was on lollipop before unlocking my bootloader.
Click to expand...
Click to collapse
You can get the stock 4.19.707.2 nandrioid here (Post #2): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Keep in mind, this is a TWRP "nandroid" backup, not a flashable ROM zip. So follow the directions carefully to restore this stock nandroid.
Also note that this is the stock ROM, not the firmware.
Would I get back my 707 if I flashed this instead http://forum.xda-developers.com/htc...-sd-14-19-707-21st-android-5-0-sense-t3010391 ?
im seeing an Asian wwe base and it is 707.
Also I wouldn't be able to dirty flash a completely different rom right?
wasdapple said:
Would I get back my 707 if I flashed this instead http://forum.xda-developers.com/htc...-sd-14-19-707-21st-android-5-0-sense-t3010391 ?
Click to expand...
Click to collapse
Not sure what you mean by "get back my 707", and you need to explain more clearly.
If the intent is to return to 707 firmware, its not needed, I'm confidant you already are on current 707 firmware. And flashing a ROM does not change your firmware (as I've already explained multiple times).
If the intent is to make the main version appear again, flashing a ROM won't do that either. As mentioned, you can only make that reappear by flashing a firmware.zip (not a ROM.zip).
If the intent is to just return to a 707 ROM base, then yes the ROM you linked will do that. But the only reason I see for you to do so, is to see if it helps your network issue. Using ROMs of other bases will not normally affect network service (as long as your carrier's APN is correct). And I've already linked you to stock 707 nandroid, which is probably the best baseline to troubleshoot from. Or are you not comfortable with the nandroid restore process?
Again, you haven't really explained what you are trying to accompish; so its hard to answer the question.
wasdapple said:
Also I wouldn't be able to dirty flash a completely different rom right?
Click to expand...
Click to collapse
If the ROM is a similar enough base, it might be possible to dirty flash. But its not recommended, and still possible to have various severe bugs, or not even boot. Therefore, full wipe is normally recommended when moving between different ROMs (and often even major updates of the "same" ROM).
Any person flashing ROMs should know how to backup and restore their personal data (using Titanium Backup and/or other means) when moving between ROMs.
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
I've actually been trying to update the firmware on my M8 today as well, but when I go to "flashboot flash zip firmware.zip" I am returned the message "not enough space."
I've cleared the cache successfully, and that didn't open up enough space. I tried to delete userdata, but it wouldn't let me do it remotely.
So I'm a little confused as to my next move here...
and I've relocked my phone and s-on.
wasdapple said:
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
Click to expand...
Click to collapse
Yes. You will get your software number back if you flash a 707 based ROM, such as stock.
So, here we go.
Download this 4.19.707.2 RUU onto your PC
When the download is finished, plug your phone into your PC, double click on the downloaded file, and follow the prompts. This will update you to Lollipop and you will be on the stock ROM again.
Since you are S-On, you will first need to relock the bootloader.
In fastboot (obviously) fastboot oem lock before you proceed with this.
Also, THIS WILL WIPE YOUR PHONE, so be sure to backup anything that is important to you.
Is the ruu rooted, or purely stock pre-root?
Kindrex said:
I've actually been trying to update the firmware on my M8 today as well, but when I go to "flashboot flash zip firmware.zip" I am returned the message "not enough space."
I've cleared the cache successfully, and that didn't open up enough space. I tried to delete userdata, but it wouldn't let me do it remotely.
So I'm a little confused as to my next move here...
and I've relocked my phone and s-on.
Click to expand...
Click to collapse
What is your current OS number on the bootloader screen, and what firmware are you trying to flash?
---------- Post added at 10:53 AM ---------- Previous post was at 10:21 AM ----------
wasdapple said:
Sorry for my vagueness in my previous post. Currently in my phone settings, the build number is 4.26.401. , which is the base of my current rom? So supposedly if I flash an Asian wwe would I get my software base back to a 707 as in the link.
The reason why I an unwilling to go through with nandroid is that I am not exactly looking to restore to stock, I like to have customs roms and the root capabilities. My ultimate objective is to get back to 707, or at least get it to appear on my software information screen. To my knowledge, 401 is for the European countries and the basebands for 4g LTE is different, thus I am unable to find out why if I am s-on with my firmware and radio intact I could not connect to my local 4g LTE, and to my point of view, only through flashing a firmware affect everything.
Im sorry for this large amount questions and extremely grateful you have taken the time to tend to it. I sincerely apologise if I seem to keep insisting that my firmware has changed despite your reminders.
Click to expand...
Click to collapse
If the intent it to return to 707 based ROM to see if that helps your 4G issue, then yes the custom ROM you previously posted will do that. It will also make 707 appear for software number in the phone Settings.
wasdapple said:
Also, you mentioned for me to flash my firmware as per my cid, which could be found in most firmware dumps? Would be it be possible to link one to me? And if I am in fact on a 707, do I still flash 707 firmware?
Click to expand...
Click to collapse
I was more talking "if" you can find the 4.16.707 firmware. The main firmware collection I refer to doesn't have 4.16.707, just old 707 firmwares (which you don't want)]: http://forum.xda-developers.com/showthread.php?t=2696282
If the firmware can't be found, the RUU listed by xunxholyx is your best bet if you really want to flash the 707 firmware. But I really don't think this is needed. As I'm nearly 100% sure you are already on the current 707 firmware, and the only benefit of flashing the 707 firmware (by RUU) is to get the OS number to appear again on the bootloader screen and on getvar all (which is really not that important).
On the other hand, RUU to full stock may be a good way to troubleshoot your 4G issue, especially if flashing the 707 based custom ROM still doesn't fix the issue. RUU is not just a stock ROM, but a complete factory image, complete with bootloader, radio, etc.
---------- Post added at 11:08 AM ---------- Previous post was at 10:53 AM ----------
wasdapple said:
Is the ruu rooted, or purely stock pre-root?
Click to expand...
Click to collapse
It appears to be 100% official and stock (unrooted). It will also wipe your phone.
---------- Post added at 11:09 AM ---------- Previous post was at 11:08 AM ----------
xunholyx said:
Yes. You will get your software number back if you flash a 707 based ROM, such as stock.
So, here we go.
Download this 4.19.707.2 RUU onto your PC
Click to expand...
Click to collapse
Nice find. I didn't know Asia version had any RUUs.
redpoint73 said:
Nice find. I didn't know Asia version had any RUUs.
Click to expand...
Click to collapse
Yeah, they are hard to come by. I was helping a user here six to eight weeks ago, and told him I didn't know of any Asia RUUs. He came back the next day replying that he found one, so I asked for the link and gave it to Sneakyghost and Alex (from AFH) to upload to androidruu.com
They have a few that aren't common there, and are always looking for more hard to find ones. If you come across one, you could PM me or Sneakyghost to have it added. Always nice to have a good RUU repository to go to.
Hey everyone. I'm having a similar issue, and I don't want to start a new thread, so I'm going to add on to this one.
I've been on AOKP since it was released for this phone, so I've missed out on some OTA updates. Every time I try to flash a Lollipop ROM I get all these weird issues (WiFi not working, systemUI crashes, etc.), and after reading a few threads, I believe its an issue with the firmware.
I tried going back to stock, but the only Nandroid backup I could find for my phone isn't compatible with my firmware (WiFi refuses to work, only data). So I was wondering what else I could do to update the firmware. Reading this thread, it looks like the RUU is another method, but I'm not too sure how to get started with that, or which one to use, as my OS in the Bootloader and my version-main is blank.
Any advice is appreciated, please let me know if you need more info.
My Device:
Rooted
TWRP 2.8.7.0
S-Off
CID-TELUS001
watidk said:
I tried going back to stock, but the only Nandroid backup I could find for my phone isn't compatible with my firmware (WiFi refuses to work, only data). So I was wondering what else I could do to update the firmware. Reading this thread, it looks like the RUU is another method, but I'm not too sure how to get started with that, or which one to use, as my OS in the Bootloader and my version-main is blank.
Any advice is appreciated, please let me know if you need more info.
My Device:
Rooted
TWRP 2.8.7.0
S-Off
CID-TELUS001
Click to expand...
Click to collapse
What are your hboot and radio numbers?

HTC M8 from Three UK stuck

Hello everyone.
I have an M8 with a corrupted software.
Always stuck on HTC logo.
Sometimes when it boots, it shows "3" , which means it's from Three UK.
I looked everywhere but couldn't find the corresponding RUU, except on http://www.htcdev.com/devcenter/downloads , but it's only around 500 MB !
It's in zip format.
I can go to the bootloader, but it doesn't accept to FACTORY-RESET (gets stuck on HTC screen)
Software status: Official
RELOCKED
Any ideas?
Thanks in advance.
I unlocked the bootloader in order to try to install another RUU.
Now it shows "UNLOCKED" .
I installed twrp and superuser (I guess).
According to the thread here http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I have to install the sunshine.apk which I can not because my phone doesn't boot except to the bootloader !
What to do here?
majdykhrais said:
I looked everywhere but couldn't find the corresponding RUU, except on http://www.htcdev.com/devcenter/downloads , but it's only around 500 MB !
It's in zip format.
Click to expand...
Click to collapse
That isn't an RUU, its kernel source, and not going to be of any help to you.
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
majdykhrais said:
I unlocked the bootloader in order to try to install another RUU.
Now it shows "UNLOCKED" .
Click to expand...
Click to collapse
Unlocking the bootloader will not allow you to run another version's RUU. I don't know why you think that, but its not correct information.
---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------
majdykhrais said:
I installed twrp and superuser (I guess).
According to the thread here http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I have to install the sunshine.apk which I can not because my phone doesn't boot except to the bootloader !
What to do here?
Click to expand...
Click to collapse
S-off is not the correct path, to do what you want (nor should it be necessary - save yourself $25). As you've figured out, you need a working OS to s-off; but working OS is the reason you want to s-off. So you have a Catch-22 dead end.
If there is no RUU, unlocked bootloader and TWRP are good things to have done. Now restore the 6.13.771.4 stock nandroid backup, using the file and instruction here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Thanks
redpoint73 said:
That isn't an RUU, its kernel source, and not going to be of any help to you.
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
Unlocking the bootloader will not allow you to run another version's RUU. I don't know why you think that, but its not correct information.
---------- Post added at 09:45 AM ---------- Previous post was at 09:41 AM ----------
S-off is not the correct path, to do what you want (nor should it be necessary - save yourself $25). As you've figured out, you need a working OS to s-off; but working OS is the reason you want to s-off. So you have a Catch-22 dead end.
If there is no RUU, unlocked bootloader and TWRP are good things to have done. Now restore the 6.13.771.4 stock nandroid backup, using the file and instruction here: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Thanks for the info.
I know TWRP and S-OFF won't help me here, but I just wanted to show what I've done.
One question, why to restore 6.13.771.4?
How will I know it's the correct one for my phone, and not a part of the pre-installed corruption?
majdykhrais said:
One question, why to restore 6.13.771.4?
How will I know it's the correct one for my phone, and not a part of the pre-installed corruption?
Click to expand...
Click to collapse
This is the main version given in your screenshot in your top post. And you'll see from the stock nandroid collection, that its the correct version number for your CID (carrier version).
Simply put, this is the stock Marshmallow ROM for your M8 version.
Somebody likely made the backup with a working OS. Yours has become damaged or corrupt (most likely) just on your phone. Not every phone with this software number is going to be broken!
didn't work!
redpoint73 said:
This is the main version given in your screenshot in your top post. And you'll see from the stock nandroid collection, that its the correct version number for your CID (carrier version).
Simply put, this is the stock Marshmallow ROM for your M8 version.
Somebody likely made the backup with a working OS. Yours has become damaged or corrupt (most likely) just on your phone. Not every phone with this software number is going to be broken!
Click to expand...
Click to collapse
excellent turorial.
I followed the steps one by one,
didn't get any errors,
but it didn't work.
I got the HTC screen, then "3" screen, then stuck on HTC One screen!
Any ideas?
majdykhrais said:
excellent turorial.
I followed the steps one by one,
didn't get any errors,
but it didn't work.
I got the HTC screen, then "3" screen, then stuck on HTC One screen!
Any ideas?
Click to expand...
Click to collapse
a strange thing I noticed,,
on command prompt on my pc, I can't see the new folder containing the unzipped file, while I can see it through the windows-explorer!
majdykhrais said:
a strange thing I noticed,,
on command prompt on my pc, I can't see the new folder containing the unzipped file, while I can see it through the windows-explorer!
Click to expand...
Click to collapse
Any particular reason why you are looking in command prompt? Since the steps don't use command prompt (unless you adb push the files).
What version TWRP?
Can you post a screenshot of what the TWRP backup folder structure (on the phone) looks like in Windows Explorer? Not sure what we can be missing here. But its worth a look.
Also, you might try the a Lollipop backup. It should work fine with the MM firmware. Although it may cause an issue with OTA updates (mixing LP ROM with MM firmware), at least it (should) get the phone up and running.
twrp backup
redpoint73 said:
Any particular reason why you are looking in command prompt? Since the steps don't use command prompt (unless you adb push the files).
What version TWRP?
Can you post a screenshot of what the TWRP backup folder structure (on the phone) looks like in Windows Explorer? Not sure what we can be missing here. But its worth a look.
Also, you might try the a Lollipop backup. It should work fine with the MM firmware. Although it may cause an issue with OTA updates (mixing LP ROM with MM firmware), at least it (should) get the phone up and running.
Click to expand...
Click to collapse
no reason for command prompt, but I just was there and noticed this.
TWRP 2.8.7.0-m8 according to the turorial.
I want to try Lollipop since it was the o.s. when my phone was working properly before I upgrade to 6 and get the wifi problem.
any specific Lollipop version?
I just want a stable version.
thanks
twrp
majdykhrais said:
no reason for command prompt, but I just was there and noticed this.
TWRP 2.8.5.0-m8 according to the turorial.
I want to try Lollipop since it was the o.s. when my phone was working properly before I upgrade to 6 and get the wifi problem.
any specific Lollipop version?
I just want a stable version.
thanks
Click to expand...
Click to collapse
here's a screen shot
the path on my laptop was the same.
sorry,
I used twrp-2.8.7.0-m8
I'm confused about what you are talking about anymore. Did you sell the phone or not?
http://forum.xda-developers.com/showpost.php?p=66116673&postcount=1498
If this is a different phone, you need to give details.
Fastboot getvar all

Htc one m9 bricked-any solutions?

Hello, everyone. I have a bricked HTC one M9 which for the last 2 days I tried to fix. It has locked bootloader, S-on, download mode does not work, recovery mod simply takes me to a red triangle. I tried a lot of methods, RUU.exe will not work(error 155) I can connect it to pc but it is not identified by ADB as a device, just by PC, even though I tried to instal an adb driver. any solutions? Thanks in advance.
gheorghexyz said:
Hello, everyone. I have a bricked HTC one M9 which for the last 2 days I tried to fix. It has locked bootloader, S-on, download mode does not work, recovery mod simply takes me to a red triangle. I tried a lot of methods, RUU.exe will not work(error 155) I can connect it to pc but it is not identified by ADB as a device, just by PC, even though I tried to instal an adb driver. any solutions? Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-one-m9/help/bricked-issues-return-to-100-stock-t3547433
Try this link. Do you have a custom recovery on the phone?
Gmoney1988 said:
https://forum.xda-developers.com/verizon-one-m9/help/bricked-issues-return-to-100-stock-t3547433
Try this link. Do you have a custom recovery on the phone?
Click to expand...
Click to collapse
No custom recovery. I don't know how to do it. Also to mention usb debugging is off
gheorghexyz said:
Hello, everyone. I have a bricked HTC one M9 which for the last 2 days I tried to fix. It has locked bootloader, S-on, download mode does not work, recovery mod simply takes me to a red triangle. I tried a lot of methods, RUU.exe will not work(error 155) I can connect it to pc but it is not identified by ADB as a device, just by PC, even though I tried to instal an adb driver. any solutions? Thanks in advance.
Click to expand...
Click to collapse
What happens when you attempt to boot into download mode (PWR+VOLDWN)? Do you get any sort of error message?
Download mode is going to be key, as it sounds like the SD card method of applying a RUU is the way to go.
computerslayer said:
What happens when you attempt to boot into download mode (PWR+VOLDWN)? Do you get any sort of error message?
Download mode is going to be key, as it sounds like the SD card method of applying a RUU is the way to go.
Click to expand...
Click to collapse
Well since I put the ruu in the link on sd it starts automatically asking me if I want to install. It failed because it has mismatched so I probably need a different version. So if I am not wrong it works. Maybe it is about the correct version or still something else?
gheorghexyz said:
No custom recovery. I don't know how to do it. Also to mention usb debugging is off
Click to expand...
Click to collapse
Putting it on the SD card is the method that worked for me. You have to have a custom recovery I prefer TWRP. Download the correct RUU and put it on the root of your SD card using TWRP then your phone should recognize in download mode and you can flash it.
gheorghexyz said:
Well since I put the ruu in the link on sd it starts automatically asking me if I want to install. It failed because it has mismatched so I probably need a different version. So if I am not wrong it works. Maybe it is about the correct version or still something else?
Click to expand...
Click to collapse
That's great, actually. You've got a properly functioning download mode - you just tried to apply the wrong RUU.
Delete that file from your SD card and boot into download mode again. We'll need your OS version in order to identify the proper SKU of your device. With any luck, there will be a RUU available to use.
gheorghexyz said:
Well since I put the ruu in the link on sd it starts automatically asking me if I want to install. It failed because it has mismatched so I probably need a different version. So if I am not wrong it works. Maybe it is about the correct version or still something else?
Click to expand...
Click to collapse
Yeah make sure your cid and mid is correct and you have the correct Ruu file.
---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------
computerslayer said:
That's great, actually. You've got a properly functioning download mode - you just tried to apply the wrong RUU.
Delete that file from your SD card and boot into download mode again. We'll need your OS version in order to identify the proper SKU of your device. With any luck, there will be a RUU available to use.
Click to expand...
Click to collapse
What Slayer said. Happy To Help.
computerslayer said:
Delete that file from your SD card and boot into download mode again. We'll need your OS version in order to identify the proper SKU of your device. With any luck, there will be a RUU available to use.
Click to expand...
Click to collapse
FYI, the OS version is listed in the download mode screen in the red text, the line above the date. Please post the complete version number.
Gmoney1988 said:
Yeah make sure your cid and mid is correct and you have the correct Ruu file.
---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------
What Slayer said. Happy To Help.
Click to expand...
Click to collapse
Thanks a lot guys, could you maybe help me find the correct version? I have cid codes where do I find the proper ruu according to them?
computerslayer said:
FYI, the OS version is listed in the download mode screen in the red text, the line above the date. Please post the complete version number.
Click to expand...
Click to collapse
Here is everything about it: htc_himauhl PVT S_ON
LK-1.0.0.0000
RADIO-01.01_U11440792_97.00.51203G-F
OpenDSP- 15.6.1.00522.8994_1026
OS-3.35.401.32
gheorghexyz said:
Here is everything about it: htc_himauhl PVT S_ON
LK-1.0.0.0000
RADIO-01.01_U11440792_97.00.51203G-F
OpenDSP- 15.6.1.00522.8994_1026
OS-3.35.401.32
Click to expand...
Click to collapse
Nice - thank you. From this, we can see that your SKU is 401. Now you can go to the Readme thread in this forum, scroll to the post that talks about RUUs and find the section that has a list of RUU files for your SKU. There is an RUU you can use - it is the 3.35.401.12 version. The other versions won't work because they are too much lower than the one you're currently using.
Please take the time to read the RUU section of the readme thread so that you're comfortable with the process. But all things being equal, this should restore your phone to stock. Recall that it will wipe your internal memory.
computerslayer said:
Nice - thank you. From this, we can see that your SKU is 401. Now you can go to the Readme thread in this forum, scroll to the post that talks about RUUs and find the section that has a list of RUU files for your SKU. There is an RUU you can use - it is the 3.35.401.12 version. The other versions won't work because they are too much lower than the one you're currently using.
Please take the time to read the RUU section of the readme thread so that you're comfortable with the process. But all things being equal, this should restore your phone to stock. Recall that it will wipe your internal memory.
Click to expand...
Click to collapse
Sorry, I am a bit of a "noob". where do i find this "read me " thread?
gheorghexyz said:
Sorry, I am a bit of a "noob". where do i find this "read me " thread?
Click to expand...
Click to collapse
It's one of the two pinned threads at the top of this forum.
computerslayer said:
It's one of the two pinned threads at the top of this forum.
Click to expand...
Click to collapse
It didn't work, it said mismatch and fail 19... i took this version: GSM RUU codename: hima_uhl - MID: 0PJA10000
gheorghexyz said:
It didn't work, it said mismatch and fail 19... i took this version: GSM RUU codename: hima_uhl - MID: 0PJA10000
Click to expand...
Click to collapse
That's only the model ID, though it's correct, for what it's worth. The next and equally important piece of information is the CID, which is matched to your SKU.
When you chose a download link, which SKU section did you choose?
computerslayer said:
That's only the model ID, though it's correct, for what it's worth. The next and equally important piece of information is the CID, which is matched to your SKU.
When you chose a download link, which SKU section did you choose?
Click to expand...
Click to collapse
I choose SKU 401, specifically for my phone cid and formatted sd card in exfat.
gheorghexyz said:
I choose SKU 401
Click to expand...
Click to collapse
Which RUU did you attempt to use?
computerslayer said:
Which RUU did you attempt to use?
Click to expand...
Click to collapse
1.40.401.8
Other versions are :1.32.401.8
1.32.401.15
2.10.401.1
3.35.401.12
Also, good choice! So you're in the right SKU section.
If you'll indulge me, it might be helpful to know the full error message.
---------- Post added at 12:03 AM ---------- Previous post was at 12:00 AM ----------
gheorghexyz said:
1.40.401.8
Other versions are :1.32.401.8
1.32.401.15
2.10.401.1
3.35.401.12
Click to expand...
Click to collapse
Ah. There's your problem. You will ONLY be able to successfully apply RUU 3.35.401.12, because the others are older than your phone is currently using.
Not to be a nag, but this is why it is important to read the readme so that you have a clear idea of what you're doing. This very issue - using your own SKU as an example - is explained in the post that included the download link.

Categories

Resources