Develop Bugs

[Q] HTC One M8 Unlocked won't unlock bootloader not update OTA

Hello everyone,
I've tried everything in order to solve this myself (even contacting HTC support by mail), but can't get this to work. I'm actually facing 2 problems with my HTC One M8 Unlocked:
Can't unlock bootloader
Updating software via OTA won't work successfully
Let me briefly explain each problem:
I've tried to unlock my bootloader via htcdev.com but it's not working. I can enter fastboot, get my token, send it to HTC, receive my Unlock_code.bin file and send it to the phone. After selecting "Yes" when the phone asks me if I want to unlock the bootloader, it factory resets (as expected) as if everything went fine, but when I enter fastboot again, I see it's still saying "LOCKED". Tried this several times (manually, via AIO toolkits) but no luck.
My current software version is 2.22.1540.3. I get a notification stating there is an update for my phone in order to take it to version 2.22.1540.4. I download it, install it, but when it boots it says that my phone has been successfully update to 2.22.1540.3 (that is...my current version). So no update is really taking place. After that, I get again the notification that an update is available.
Those are the 2 problems I'm facing. Any ideas on what else can I try?
This is what I get from fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.22.1540.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What's even more weird (and I've just noticed this) is that in one of those variables it says "version-main: 2.22.1540.4".

Your main version (OS or software) hboot and radio baseband all match the latest OTA, so you are already updated. There is just something wrong that is causing notifications, but not sure what that might be.
The bootloader unlock issue is odd. I haven't seen it before on this device yet, but on the One X EVITA there were instances where folks had to try the bin code multiple (even dozens) of times before it worked. So maybe just keep trying, and make sure the syntax is exactly correct. Not sure what else can be done?

redpoint73 said:
Your main version (OS or software) hboot and radio baseband all match the latest OTA, so you are already updated. There is just something wrong that is causing notifications, but not sure what that might be.
The bootloader unlock issue is odd. I haven't seen it before on this device yet, but on the One X EVITA there were instances where folks had to try the bin code multiple (even dozens) of times before it worked. So maybe just keep trying, and make sure the syntax is exactly correct. Not sure what else can be done?
Click to expand...
Click to collapse
That helps! Will keep trying to unlock the bootloader until it works then. Thanks!

I have the same problem. Have you solved your problem?
---------- Post added at 12:21 PM ---------- Previous post was at 11:46 AM ----------
I just find these problems might be caused by automatic factory reset, but I don't know how to solve it.

mkiderek said:
I have the same problem. Have you solved your problem?
---------- Post added at 12:21 PM ---------- Previous post was at 11:46 AM ----------
I just find these problems might be caused by automatic factory reset, but I don't know how to solve it.
Click to expand...
Click to collapse
Didn't solve it yet (haven't had time to try again). What do you mean by automatic factory reset?

nachochiappe said:
Didn't solve it yet (haven't had time to try again). What do you mean by automatic factory reset?
Click to expand...
Click to collapse
Ignore that please. I tried to flash 2.22.1540.4 ruu and failed. The one who help me says it might be caused by physical or logical damage on memory, service center is required to solve this issue. I have decided to return it to amazon and bought a new one. Hope the new one has no problem.

mkiderek said:
Ignore that please. I tried to flash 2.22.1540.4 ruu and failed. The one who help me says it might be caused by physical or logical damage on memory, service center is required to solve this issue. I have decided to return it to amazon and bought a new one. Hope the new one has no problem.
Click to expand...
Click to collapse
Will try flashing the RUU on mine too. Where did you get it from?

nachochiappe said:
Will try flashing the RUU on mine too. Where did you get it from?
Click to expand...
Click to collapse
http://bbs.gfan.com/android-7629706-1-1.html
You will need to register first.

mkiderek said:
http://bbs.gfan.com/android-7629706-1-1.html
You will need to register first.
Click to expand...
Click to collapse
Great! Thanks!

The can upload to another server?, Or you can link to download private message to another server?, Thank you very much.

I am also having the same issue with my m8. Have attempted to unlock the bootloader about 15 times with a different token id each time, and nothing, its remaining locked. I also get a persistent notification to update to 2.22.1540.3 regardless of how many times I install it. Any ideas?

Same issue with me, but it actually messed up my phone for good -
Ill post the whole issue was it happened -
1. Tried to unlock bootloader using HTC Dev, 3 times. Each time it would successfully take the token and stuff, reset the phone, but the bootloader would still be locked.
I tried this using 3 separate HTC Dev accounts. Same result.
2. Now the 4th time when i did this, the phone went back the RUU firmware mode (but with 4 triangles on the corners).
3. I can boot into the stock ROM, the one the phone came with by using - fastboot oem boot. But i have to do this every time the phone shuts down or has to be restarted.
From my understanding the bootloader, recovery and hboot partitions are corrupt. Best case scenario, only the bootloader. And i cannot flash either of the partitions since im not unlocked nor S-off.
Another issue would be, why was i not able to unlock my bootloader? The first time i thought maybe i made a mistake in copying the the unlock string. But that wasn't it.
If it helps, the phone came with Android 4.4.3 with Hboot 3.18 (2.22.1540.3).
The phone is a 32 GB US Unlocked version. CID - BS_US001 MID - 0P6B12000
And i cannot for the life of me find a RUU for this phone. The phone is just 1 day old.
Any help would be appreciated. I couldn't find anyone with the same 4 triangle issue on the forums.
UPDATE :
Just fixed the bootloader issue by flashing the firmware zip from here :
http://forum.xda-developers.com/showpost.php?p=55067300&postcount=1605
Though i still have not been able to unlock the bootloader.

mkiderek said:
http://bbs.gfan.com/android-7629706-1-1.html
You will need to register first.
Click to expand...
Click to collapse
I registered and still can't download this file. Would you consider uploading for us?

soundwavedj said:
I registered and still can't download this file. Would you consider uploading for us?
Click to expand...
Click to collapse
I tried to downloaded the file from other sources, by googl'ing the file name, the file downloads a rom.zip but i cant open it no matter what.
Winrar and 7zip both say the file is corrupt.
Try this - http://pan.baidu.com/wap/share/home?uk=1275354262&third=0
Do let us know if it works for you.
I am also now facing the constant OTA update notifications. I emailed HTC Dev about the whole thing yesterday.

bloodhawk said:
I tried to downloaded the file from other sources, by googl'ing the file name, the file downloads a rom.zip but i cant open it no matter what.
Winrar and 7zip both say the file is corrupt.
Try this - http://pan.baidu.com/wap/share/home?uk=1275354262&third=0
Do let us know if it works for you.
I am also now facing the constant OTA update notifications. I emailed HTC Dev about the whole thing yesterday.
Click to expand...
Click to collapse
That link worked for the download but the download says 15 hours until complete [emoji16]

soundwavedj said:
That link worked for the download but the download says 15 hours until complete [emoji16]
Click to expand...
Click to collapse
Pretty weird.. I get around 1.5-2 MBps down from this site. My actual is 8MBps.

Try downloading from this link :
http://pan.baidu.com/share/init?shareid=1861479922&uk=288682052
Password : q7ad
I haven't still tried the file, since im waiting to hear back from HTC. Keep us posted if someone else is willing to try.

Unlock Bootloader not working
I am also having trouble unlocking bootloader through htcdev.com
I tried it about 5-6 times, it resets phone but remains locked.
Have you guys found a solution?

Do post your Firmware and Hboot version. Ill try passing on the info about other people not being able to do it to the HTC Dev.

Firmware and hboot versions
bloodhawk said:
Do post your Firmware and Hboot version. Ill try passing on the info about other people not being able to do it to the HTC Dev.
Click to expand...
Click to collapse
Firmware 2.22.1540.4
Hboot 3.18.0.0000
Thanks for your dedication

[Q] "clean install"

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

deleted OS, been trying to return to stock

So I've been reading a ton of these threads to try to help me fix this. It seems like a really easy fix but it's not working for me. My device cid is htc__01 and I'm S-On. I'm trying to do an HBoot of the nandroid zip for my cid that I got from https://forum.xda-developers.com/showthread.php?t=2701376.
I downloaded the "4.16.401.10 - TWRP Thanks to Clumsy" under CID HTC__01 of nandroid backups. I put it on my SD card and I renamed it to 0P6BIMG.zip.
My HBoot is 3.19 btw. When I start HBoot, it says "no image or wrong image"
I'm also currently "unlocked" but I also tried running HBoot when I was "relocked" and it didn't work.
Any tips?
edit: Here are some pictures to show what I'm getting and what my info is
http://i.imgur.com/dsISZpB.jpg
http://i.imgur.com/IekCgFp.jpg

You do it all wrong ... the nandroid backup zip is to be extracted and restored not renamed and flashed.
Read this post #1 on how to use a nandroid to restore to stock - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you want the RUU.zip that can be renamed 0P6BIMG.zip and flash via hboot,
you need this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but this will get your device updated to Marsmallow directly.
Just saw your EDIT - Forget the above ... you have a AT&T device ... you'll need AT&T RUU
Can you post fastboot getvar all result (without serial & imei no.), need to see what's your device current status ... still an AT&T or converted to Intl GSM.

ckpv5 said:
You do it all wrong ... the nandroid backup zip is to be extracted and restored not renamed and flashed.
Read this post #1 on how to use a nandroid to restore to stock - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
If you want the RUU.zip that can be renamed 0P6BIMG.zip and flash via hboot,
you need this - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
but this will get your device updated to Marsmallow directly.
Just saw your EDIT - Forget the above ... you have a AT&T device ... you'll need AT&T RUU
Can you post fastboot getvar all result (without serial & imei no.), need to see what's your device current status ... still an AT&T or converted to Intl GSM.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:-
(bootloader) imei: -
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__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: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.342s

refsner said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) security: on
Click to expand...
Click to collapse
You do have a AT&T device.
The best place for your reference is @redpoint73 thread - https://forum.xda-developers.com/showthread.php?t=2751432
Are you in US and on AT&T network ?
If yes .. to get back to stock and updated to Marshmallow, you can follow this guide - https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7

ckpv5 said:
You do have a AT&T device.
The best place for your reference is @redpoint73 thread - https://forum.xda-developers.com/showthread.php?t=2751432
Are you in US and on AT&T network ?
If yes .. to get back to stock and updated to Marshmallow, you can follow this guide - https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Click to expand...
Click to collapse
Yes I'm in the US but I'm using an AT&T phone with T-Mobile network. So would I need to follow the other steps in your second thread linked?

refsner said:
Yes I'm in the US but I'm using an AT&T phone with T-Mobile network. So would I need to follow the other steps in your second thread linked?
Click to expand...
Click to collapse
If you want a Masrhamallow stock ROM, yes the second thread. But I'm not sure about the SIM lock status of AT&T and the AT&T HD Voice whether these will impact your network on T-Mobile.
Need someone familiar with AT&T like @redpoint73 to comment.
I suggest you to wait for other comments.
Meantime - you can restore nandroid backup 4.28.502.2 which available on my backup thread to have a working phone. Don't do any RUU install yet.
EDIT - based on your screenshots/getvar result - you have a KitKat firmware, restore 3.42.502.1 to have a working phone. The above backup, you'll have wifi problem because that's a Lollipop.

ckpv5 said:
If you want a Masrhamallow stock ROM, yes the second thread. But I'm not sure about the SIM lock status of AT&T and the AT&T HD Voice whether these will impact your network on T-Mobile.
Need someone familiar with AT&T like @redpoint73 to comment.
I suggest you to wait for other comments.
Meantime - you can restore nandroid backup 4.28.502.2 which available on my backup thread to have a working phone. Don't do any RUU install yet.
Click to expand...
Click to collapse
Got it I'll do that. Thank for helping me out

refsner said:
Got it I'll do that. Thank for helping me out
Click to expand...
Click to collapse
Read my edit - you have a KitKat firmware, restore 3.42.502.1

ckpv5 said:
Read my edit - you have a KitKat firmware, restore 3.42.502.1
Click to expand...
Click to collapse
Ok! Will I be able to update to marshmallow at all afterwards?

refsner said:
Ok! Will I be able to update to marshmallow at all afterwards?
Click to expand...
Click to collapse
You won't be able to OTA when not on AT&T but you can get to Marshmallow using the guide that I put here - https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
The only thing that I'm not sure whether the phone is SIM locked to AT&T or not.
If you're sure it is not SIM locked, you can straight away follow the guide.
Or if it is SIM locked but you do have the SIM unlock code .. then go ahead with the Marshmallow RUU.
About the HD Voice, I believe that will affect users on AT&T network but running custom ROM.

ckpv5 said:
You won't be able to OTA when not on AT&T but you can get to Marshmallow using the guide that I put here - https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
The only thing that I'm not sure whether the phone is SIM locked to AT&T or not.
If you're sure it is not SIM locked, you can straight away follow the guide.
Or if it is SIM locked but you do have the SIM unlock code .. then go ahead with the Marshmallow RUU.
About the HD Voice, I believe that will affect users on AT&T network but running custom ROM.
Click to expand...
Click to collapse
I think the first time I received the phone, it was SIM locked but I was able to get a SIM unlock code. I'll place my bets and do the Marshmallow RUU. I'll let you know if it goes well.

refsner said:
I think the first time I received the phone, it was SIM locked but I was able to get a SIM unlock code. I'll place my bets and do the Marshmallow RUU. I'll let you know if it goes well.
Click to expand...
Click to collapse
Ok
Another thing is your device is S-On, you need to relock bootloader before you install the firmware.zip and RUU.
You already know how I believe - fastboot oem lock

ckpv5 said:
Ok
Another thing is your device is S-On, you need to relock bootloader before you install the firmware.zip and RUU.
You already know how I believe - fastboot oem lock
Click to expand...
Click to collapse
Yeah I made sure to do that thank you. I'm in the process of installing the RUU right now. Going a little slow. The RUU says to turn on the phone. Does that mean put it into fastboot USB? It didn't work when I had it just on the HTC logo white screen.

Yes - put the device on fastboot mode.
You already did the firmware installation ?
Install firmware first then RUU - all these on fastboot mode

ckpv5 said:
Yes - put the device on fastboot mode.
You already did the firmware installation ?
Install firmware first then RUU - all these on fastboot mode
Click to expand...
Click to collapse
Yes I did the firmware installation first. Then I ran the RUU, this time on fastboot mode (haha). It is still in the process of updating right now.
Edit: It's starting up. Seems to have worked. I appreciate all your help. I would have probably spent many more hours trying to figure this mess out!

refsner said:
Edit: It's starting up. Seems to have worked.
Click to expand...
Click to collapse
:good:
So no problem with SIM as it is still remain unlocked ? Hopefully yes as usually once SIM is unlocked it should remain unlocked.

ckpv5 said:
:good:
So no problem with SIM as it is still remain unlocked ? Hopefully yes as usually once SIM is unlocked it should remain unlocked.
Click to expand...
Click to collapse
No there was no problem at all. I inserted the SIM card and immediately got LTE T-Mobile coverage. Super fortunate

refsner said:
No there was no problem at all. I inserted the SIM card and immediately got LTE T-Mobile coverage. Super fortunate
Click to expand...
Click to collapse
Great .. this will be a good reference for someone else on same situation.

ckpv5 said:
Need someone familiar with AT&T like @redpoint73 to comment.
I suggest you to wait for other comments.
Click to expand...
Click to collapse
Looks like ckpv5 has the OP sorted out, before I even woke up! :good:
But let me know, if there are any further AT&T specific questions.

Which RUU can i flash?

So, I had a marshmallow update on my phone, and later i converted into GPE, but didn't like it. Went back to Sense, but it just doesn't feel as good as before. One day, the battery died, and when i tried turning it on, it would give me all sorts of errors. This never happened while i was on marshmallow before conversion to GPE. Had to reset it from the recovery. I think it hasn't returned to Sense properly.
As i am S-Off, i was thinking of flashing it with a RUU which is compatible with my device. Please suggest me which is compatible.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.21450002
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.708.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------------------
(bootloader) imei: --------------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.090s

Based on your MID, looks like you're on a GSM M8? I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.

I have read here that flashing carrier RUU can brick the device radio for good. So, this is why I wanted to confirm.

cytherian said:
I'd go to HTC Dev and download their stock ROM, or go the appropriate carrier sub section for the M8 and use an RUU there.
Click to expand...
Click to collapse
HTC does not post the RUU for his version on HTC Dev.com (many versions are not posted there)
OP's version doesn't have a carrier forum sub-section.
---------- Post added at 09:38 AM ---------- Previous post was at 09:36 AM ----------
xexux said:
(bootloader) version-main: 6.16.708.1
Click to expand...
Click to collapse
I don't know if there is an RUU for this version number.
One alternative, is to restore the TWRP backup 6.16.708.1 from here: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 09:42 AM ---------- Previous post was at 09:38 AM ----------
xexux said:
Went back to Sense, but it just doesn't feel as good as before.
I think it hasn't returned to Sense properly.
Click to expand...
Click to collapse
How exactly did you go back to Sense?

I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.

xexux said:
I tried the guide here, but I just couldn't complete it, as i received some modelid error. Tried multiple times to no avail. So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Good to hear that it worked out and thanks for posting. :good:

cytherian said:
Good to hear that it worked out and thanks for posting. :good:
Click to expand...
Click to collapse
This is how I got Sense back, and after that, I started experiencing bugs with M8 as explained in my first post.

xexux said:
So, i tried the TWRP nandroid method, and restored to Sense that way.
Click to expand...
Click to collapse
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?

redpoint73 said:
Which TWRP backup did you restore? Did you flash firmware, or only restore the TWRP backup?
Click to expand...
Click to collapse
I restored it with the latest TWRP backup for my model. About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.

xexux said:
I restored it with the latest TWRP backup for my model.
Click to expand...
Click to collapse
What version number exactly? Perhaps you still have the files on your computer, and can look?
I've seen a number of times, folks say and think they restored the right version for their model, and once we ask for version numbers, we see they actually got it wrong.
xexux said:
About firmware, I am not sure, but i do see that firmware version in 'fastboot var all' data.
Click to expand...
Click to collapse
I can see it too. But doyou actually remember manually download and flash the firmware in RUU mode?
Did you convert to GPE using the RUU?
xexux said:
Since I am S-off, is there any Marshmallow RUU which i can try without bricking anything? May be a developer version or RUU for european/asian variant? Or the ones linked at gsmhosting M8 page? I have read people experiencing LTE radio problem with that. I hope that's not the case anymore, and there is a work around.
Click to expand...
Click to collapse
It's possible. But flashing another region's RUU will also change the radio baseband, and therefore changes the specific bands supported. It may have undesirable results (not support the 3G or LTE band or bands used by your local carrier).

My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash

Bukss said:
My htc one m8 has no os due to an unsuccessful update, I have s-on, boot loader unlocked and not fully rooted. I have twrp as recovery. What are my options to get the official ruu to flash
Click to expand...
Click to collapse
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).

redpoint73 said:
First of all, the phone won't update with TWRP installed (need stock recovery) so that is one reason for the update to fail.
Also, if the ROM is not stock (such as custom ROM, root) in any way, it needs to be returned to stock in order to update. I don't know what "not fully rooted" means. But if it was rooted, you need to re-install the stock ROM (such as stock TWRP backup) as most other "unroot" methods do not work (update will still fail).
RUU will update the phone, and bypasses the above requirements. But we would need to know more about the phone to know if your version M8 has an RUU. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
c:\miniadb_m7>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 99000499834418
(bootloader) product: m8_wlv
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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: RUU
(bootloader) commitno-bootloader: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.036s

Abnova said:
Hello guys. I took my M8 to someone to repair and they completely messed up the phone. Now no matter how you try to boot up the phone, a black screen with a silver HTC logo in the middle and 4 silver triangles in the corner shows up. I cannot reboot into bootloader, it brings me back to the same screen. Here is a getvar of my htc one m8, i was wondering if you could point me to the right RUU to use.
(bootloader) version-main: 5.07.1700.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m8_wlv
(bootloader) modelid: 0P6B12000
Click to expand...
Click to collapse
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).

redpoint73 said:
Wow, this is quite a mess!
Was this a repair shop, or just some person you knew that tried to "fix" the phone. Either way, it is probably apparent that they shouldn't be trusted, and don't seem too knowledgeable (at least with this specific device).
Although there are a few details I'm not clear on, and you should clarify:
1) If you can't get to bootloader, how did you do fastboot getvar all?
2) What exactly was wrong with the phone that the shop/person tried to "fix" for you (and the specific condition before you gave it to them)? Was it able to boot to OS? Something else wrong (no SIM, etc.)?
What is clear, is that your device is the US Verizon version M8 (as shown by the product ID m8_wlv). But at some point (not completely clear if it was the repair person, or before that) it had its MID changed to that of the US Developer's Edition (0P6B12000). And had the Google Play Edition (GPE) firmware and/or RUU installed.
Those last two things (changing to Dev Ed MID, and running GPE RUU/firmware) are a very bad idea on the Verizon version M8. Reason being, the Verizon M8 is peculiar, and can only run firmware/RUU intended for the Verizon variant M8 (so Verizon RUU or firmware). Installing any other RUU/firmware will result in a radio brick, possibly permanent. And is probably also the reason the phone won't boot to OS now. It may be fixable. But first, I'd like more information (items above) on the history of the phone, and exactly what was done to it before the repair person worked their "magic" (as much as you know).
Click to expand...
Click to collapse
Yeah I realised how big of a mess I was in when I got it back. Anyway
1.)On further investigation it seems like the the phone is in a wierd RUU mode. So it still can interface with the laptop through fastboot. Like I said earlier, trying to reboot to bootloader brings you to the same black screen with the silver Logo (see attached). When the phone is plugged in to the laptop or switches to the HTC silver Logo screen however when it's unplugged, it goes to a wierd bootloader like screen but black and only has the option for RUU. ( See attached)
2.) I took it to them to replace the battery because . The phone would switch off even at 100% battery. It only worked when it stayed plugged in , like a PC. I'm guessing the repair guys saw I had modified the software (I was running Dirty Unicorns, Android 7.1.2, Latest TWRP with a relocked Bootloader, S-Off) and had thought the problem actually had to do with the software. I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Anyway I hope this information helps. Thanks for your help.

Abnova said:
I live in Kenya and the HTC model available here is the international Gsm model so im guessing it seemed reasonable for them to RUU the Google play edition to try to bring it to a stable, stock, state. It most likely previously worked on the other M8's brought to them. I doubt they realized that I had imported the phone from the US, so they were probably shocked when it failed.
Click to expand...
Click to collapse
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Abnova said:
1.)On further investigation it seems like the the phone is in a wierd RUU mode.
Click to expand...
Click to collapse
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!

Thanks for your contribution, will definitely try tomorrow

redpoint73 said:
"Because it worked before" is not a good philosophy when working with these devices. Different models have their own nuances, for any smartphone. Any repair shop should be smart enough to know that different models/versions of the same phone can have major differences. And assuming otherwise can have catastrophic results!
Not a bad thing, if it is in fact RUU mode. You can try the Verizon RUUs. As mentioned, these are the only RUUs you should try on your device!
https://forum.xda-developers.com/verizon-htc-one-m8/general/official-ruu1-55-605-2-t2883845
You will likely need to change back to the Verizon MID to run those RUUs. Otherwise the RUU will fail with wrong MID.
https://forum.xda-developers.com/showthread.php?t=2708581
If the phone boots to OS, but with no SIM or no signal, the repair shop flashing the wrong RUU may have bricked the radio. You can try to flash an older (Kitkat) Verizon RUU, which sometimes will fix the problem. If it does fix the radio, then you can update up to something more recent (Marshmallow).
Of course, I don't know if any of this will help your original problem of the phone shutting off when not on charger. If it is a software problem, then the original factory image (Verizon RUU) has the best chance of fixing it!
Click to expand...
Click to collapse
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do

Abnova said:
I'm having trouble changing the MID Because adb is not working. However, fastboot is. So I've been stuck and I don't know what to do
Click to expand...
Click to collapse
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.

redpoint73 said:
Ah, yes. Good point. You need adb to change the MID.
Try booting TWRP custom recovery, which should give you adb access.
Download TWRP (I suggest the latest, version 3.2.1-0). Put it in the same folder as fastboot.exe
Then do command: fastboot boot twrp.img
Where "twrp.img" has to match the exact file name of what you downloaded (you can change the name of the file to twrp.img or else type the whole/exact file name as downloaded).
Hopefully, you will see TWRP boot on the phone. Once it does, you should have adb access.
I also believe you should be able to run root (su) commands in TWRP (which is necessary to change MID). But I don't remember if there is an extra step of not to that.
Basically, the repair shop really screwed you by changing the MID and flashing the wrong RUU. Extra steps/tricks to do now, but hopefully we can get some progress anyway.
Click to expand...
Click to collapse
I tried that, it would flash then refuse to reboot to the recovery. I've tried so many things but none of them worked. My only hope is if someone edited the Android.txt file inside the Rom Zip so that the model ID is the same as that of my corrupt phone. That way it'll flash and hopefully fix it. I've tried myself but everytime I tried to edit it says the zip/archive is corrupt on WinRAR. I don't know whether it's a problem with my laptop or if it's a complication related to the rom.zip. I've downloaded it again but it still does the same thing. So basically I'm stuck because there is no way I can change the MID. This probably means the phone is bricked.

HTC One M8 stuck on HTC screen

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: