Develop Bugs

Rumrunner won't pass test 1

Hi there
I am trying to gain s-off via rumrunner. I followed the instructions closely but when it attempts to check the bootloader and fastboot, it fails. My phone (Sprint m8), boots to boot loader but then it just sits there and rumrunner fails.
What is going wrong and how do I fix it? My phone is rooted and unlocked. I've got insertcoin and twrp flashed. Is there something wrong with fastboot? Please help as I am eager to gain s-off. I am thinking about just using Sunshine, but I don't want to pay the fee if it's not even going to work.
Thanks
G

garyg199 said:
Hi there
I am trying to gain s-off via rumrunner. I followed the instructions closely but when it attempts to check the bootloader and fastboot, it fails. My phone (Sprint m8), boots to boot loader but then it just sits there and rumrunner fails.
What is going wrong and how do I fix it? My phone is rooted and unlocked. I've got insertcoin and twrp flashed. Is there something wrong with fastboot? Please help as I am eager to gain s-off. I am thinking about just using Sunshine, but I don't want to pay the fee if it's not even going to work.
Thanks
G
Click to expand...
Click to collapse
Rumrunner hasn't worked for over a year and a half, and Firewater hasn't either.
Sunshine is the way to do it now if you want/need S-Off. You could buy a Java Card, but it would be more expensive.

Oh, wow , okay thanks. Yeah I thought it was weird but I was watching a video that was uploaded one week ago and the user was using rumrunner. I'm still a bit of a noob with this but the reason I am trying to gain s-off is because when I flash a new rom I either get stuck at the bootloader or the boot image. I'm guessing it's because I'm a-on and I would have to flash using abd commands on my pc? If I am wrong can someone please let me know? It's a bit confusing. Thanks

garyg199 said:
Oh, wow , okay thanks. Yeah I thought it was weird but I was watching a video that was uploaded one week ago and the user was using rumrunner. I'm still a bit of a noob with this but the reason I am trying to gain s-off is because when I flash a new rom I either get stuck at the bootloader or the boot image. I'm guessing it's because I'm a-on and I would have to flash using abd commands on my pc? If I am wrong can someone please let me know? It's a bit confusing. Thanks
Click to expand...
Click to collapse
Is your firmware up to date?
Tell me what it says next to "OS" in your bootloader. If you are using an old version of TWRP, it may be blank. If it is, post the results of fastboot getvar all to determine the firmware version from that, but remove your IMEI and serial# first as that is private info.

Well it is blank. It just says "OS-".
How do I execute the fastboot getvar etc. ? In a command window on my computer or? Sorry. Noob is shining here

I just updated twrp like last week though?

Yeah my twrp version is 2.8.5.0

garyg199 said:
Well it is blank. It just says "OS-".
How do I execute the fastboot getvar etc. ? In a command window on my computer or? Sorry. Noob is shining here
Click to expand...
Click to collapse
Did you buy the phone rooted, or did you use ADB and fastboot to root yourself? Yes, you do it in CMD with the SDK/ADB software. Hook your phone up to your PC, open CMD in ADB (shift+right click and choose "open command window here")
enter adb reboot bootloader
then fastboot getvar all

I rooted it myself. I just tried it and got nothing after it says <waiting for device>. I could also be doing this wrong too though. SDK...Is this android audio whatever? Because I've been trying to find that and that's where it brought me, from every link. I downloaded the actual package with the program tools so I think I have it right but I'm not sure. Thanks for all the help by the way

I think I've got the right sdk tools and all. I just found another thread where someone had the same issue. He said it fixed magically overnight, but another said to uninstall the HTC drivers and reinstall on my pc. Guess I'll try that, unless you know another solution?

garyg199 said:
I think I've got the right sdk tools and all. I just found another thread where someone had the same issue. He said it fixed magically overnight, but another said to uninstall the HTC drivers and reinstall on my pc. Guess I'll try that, unless you know another solution?
Click to expand...
Click to collapse
Okay. You "think" you have SDK? I'll tell you right now, your firmware is out of date. Run the software update/RUU from HTC's US website. I would tell you if you should run Sprint's standard RUU, or the Sprint H/K RUU, but since you have failed to provide me with the information to direct you to the proper firmware update that I asked for, I guess you can figure it out on your own by searching your CID and MID from your getvar output.
Here's a link to the HTC US Software Download page.
Good luck!

garyg199 said:
I think I've got the right sdk tools and all. I just found another thread where someone had the same issue. He said it fixed magically overnight, but another said to uninstall the HTC drivers and reinstall on my pc. Guess I'll try that, unless you know another solution?
Click to expand...
Click to collapse
If you unlocked the bootloader yourself, you have a working adb/fastboot environment.
Be sure you are booted into OS, and have "USB Debugging" enabled in settings, to issue the adb command suggested by xunholyx.

Thanks @redpoint. Sorry for my ignorance and lack of knowledge guys, just trying to get things straight. Im guessing my next step as of now is to get my boot loader locked again and get my stock recovery back so I can update my firmware. It seems like I can't do much until I do so. I downloaded sunshine and it gave me an error about flashing a "non debuggable ram disk". Thanks again for your help. Any other advice is much appreciated

garyg199 said:
Thanks @redpoint. Im guessing my next step as of now is to get my boot loader locked again and get my stock recovery back so I can update my firmware.
Click to expand...
Click to collapse
You shouldn't be "guessing" anything.
You have failed to provide the proper information (output from fastboot getvar all) which has been requested 3 times now. Can't provide the proper guidance without more info.
garyg199 said:
Thanks @redpoint. I downloaded sunshine and it gave me an error about flashing a "non debuggable ram disk".
Click to expand...
Click to collapse
s-off isn't going to automatically (all by itself) fix your problem (flashing a ROM), if that is what you think.
You have 2 potential (probable) issues:
1) The ROM won't boot if your firmware is outdated (s-off makes it a bit easier to update firmware, but its not strictly required to do so)
2) ROM also won't boot if its does not specifically support the Sprint version M8

I'm failing to provide the info because it's not giving me the info! I'm guessing because I'm doing this on my own more or less

garyg199 said:
I'm failing to provide the info because it's not giving me the info! I'm guessing because I'm doing this on my own more or less
Click to expand...
Click to collapse
I have no idea what that means. Your computer is sensing you are doing this "on your own" and deciding it doesn't like that?
If you are having issues executing the advice given to you, you need to state that, along with the specific results, error messages, etc. A screenshot may also be helpful.
If you don't post that you tried, and it failed; all we can do is assume that you ignored or missed the advice.
If the computer is hanging "waiting for device" when you try "fastboot getvar all" then you should try another USB cable, another port, re-install HTC Sync, or even try another computer (if possible).
But I have no idea of knowing what the issue is, if you don't tell us.

Cid- SPCS_001
MID-0P6B70000

I hope those are the correct numbers that were needed

garyg199 said:
I hope those are the correct numbers that were needed
Click to expand...
Click to collapse
I want the full getvar output (minus IMEI and serial number, which are personal info) not just 2 pieces of it.

Here's what I got
Had to use the all in one toolkit to get it. Wasn't giving it to me with just the commands.

Updating to Android 6.0 not possible?

Hello,
I am in need of some help.
2 weeks ago i bought the HTC One M9.
A few days ago the update to android 6.0 message popped up.
I have probably tried updating it like 15 times already, but everytime the first part is downloaded, and my phone reboots, after 1/4th of the updating it shows a red triangle with an exclamation point in it.
I have tried wiping the cache, it didn't help.
Honestly i don't have a clue what's wrong, or where i can find out what went wrong, so i would really appriciate all the help i can get.
Example of what happens:
malmgrens [dot] org/bilder/htc_recovery_mode [dot] jpg

A few more details will be helpful:
- what variant do you have (locale & carrier)?
- is your phone modified (ie, custom recovery and/or root)?
In order to take an over-the-air update, the phone must be completely stock. If it is not, you'll need an RUU to restore your phone to stock (be sure to backup your information first). Then you'll be able to take the OTA update.

computerslayer said:
A few more details will be helpful:
- what variant do you have (locale & carrier)?
- is your phone modified (ie, custom recovery and/or root)?
In order to take an over-the-air update, the phone must be completely stock. If it is not, you'll need an RUU to restore your phone to stock (be sure to backup your information first). Then you'll be able to take the OTA update.
Click to expand...
Click to collapse
Hey, thanks so much for your reply
I am pretty sure i got the dutch version, it might be belgium.
The carrier is vodafone.
I am pretty sure its not rooted etc, since i didn´t do anything with it.
What does stock and RUU mean?(I am a total noob with this.)

appie.0606 said:
Hey, thanks so much for your reply
I am pretty sure i got the dutch version, it might be belgium.
The carrier is vodafone.
I am pretty sure its not rooted etc, since i didn´t do anything with it.
What does stock and RUU mean?(I am a total noob with this.)
Click to expand...
Click to collapse
Hi there,
To clarify - your phone boots to its current software with no problem, right? If so, it would be a wise thing for you to determine your MID (model ID) and CID (carrier ID). There are a number of guides - Google is your friend. I recommend looking up ADB installation, your OS (Mac, Windows, Linux) and going from there.
Once you know your MID & CID, we can help you find out what firmware is available for you.
To learn about RUUs, VenomROM has a great page that explains about what they are and how to use them.
Peace,
Computerslayer

computerslayer said:
Hi there,
To clarify - your phone boots to its current software with no problem, right? If so, it would be a wise thing for you to determine your MID (model ID) and CID (carrier ID). There are a number of guides - Google is your friend. I recommend looking up ADB installation, your OS (Mac, Windows, Linux) and going from there.
Once you know your MID & CID, we can help you find out what firmware is available for you.
Peace,
Computerslayer
Click to expand...
Click to collapse
Yes my phone boots to current software without any problems right now.
Some info i found:
CID: VODAPE17
MID did not show for some reason. I tried multiple ways using adb shell and fastboot, but shell doesnt show anything and fastboot gets stuck at waiting for device.
Is finding my MID nessecary to fix this update problem? If so how can i find it?

Power of your M9
Power on & press at the same time to enter in the bootloader, volume -
on the top of the screen, is it writed locked or unlocked?
You can see more information in download mode...

bzhmobile said:
Power of your M9
Power on & press at the same time to enter in the bootloader, volume -
on the top of the screen, is it writed locked or unlocked?
You can see more information in download mode...
Click to expand...
Click to collapse
Hey thanks for your reply.
It says unlocked. Is that normal or could it be an/the issue?

If you are unlocked, it's related to your issue.
You have to flash a RUU to be "stock" and ready for the OTA...

bzhmobile said:
If you are unlocked, it's related to your issue.
You have to flash a RUU to be "stock" and ready for the OTA...
Click to expand...
Click to collapse
Alright, so if i understand correctly i can flash a RUU (whatever it is lol) without having to backup without doing a clean install. The phone wont wipe my data?
Would this guide be what you mean?
how-to-flash-ruu-firmware-htc-one-m9/
from naldotech
com

If you flash an RUU....your device will be wiped clean....as it came out of the box...
Then you can OTA on a clean....stock rom....g

The Thread is a good one.
More explication of what is needed in post2 or post 3 of TWRP thread (about Google's new limitation for the OTA).
Beware flashing a RUU will wipe everything, don't forget to backup all you take care...

RESOLVED! [SOS!] Phone can't boot past bootloader

My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy

drago10029 said:
My phone is having a bowl of bootloops right now lol.
I have a unlocked htc 10, i unlocked the bootloader (S-on since leedroid thread didn't say it was necessary), flashed the latest TWRP formatted data part, rebooted recovery again, swiped allow modifications, flashed the marshmallow version of the ROM and nothing but bootloops. what am i missing? thanks
first time HTC owner here coming from a 6p so show mercy
Click to expand...
Click to collapse
Are you on MM firmware or N?
Also S-OFF is the way to go.

andybones said:
Are you on MM firmware or N?
Also S-OFF is the way to go.
Click to expand...
Click to collapse
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
If you wish to s-off first, please follow >> THIS GUIDE << by @jcase & return when your device is back up and running.
First boot will take approximately 15 minutes due to Art optimization
Click to expand...
Click to collapse

UPDATE: things have gotten worse.... I was attempting to relock the bootloader since RUU was failing with error 155, someone in a diff HTC thread said locked bootloader was needed for RUU. now phone flashes HTC logo then powers off. buttons pressed not going to recovery right now anyone wanna chime in? please...

@defcomg you know anything about HTC phones? I am currently stuck in the sunken place lol

drago10029 said:
I was on latest stock nougat before I started the process. since the I have tried flashing both leedroid marshmallow zip and the nougat magisk zip also. and what's the deal with s-off?
Everywhere i look they're all how to's about s-off lol. seems hard to find a thread on what s-off is, if it's needed to for a specific ROM or not :/ that being said leedroid it wasn't needed as quoted below. thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=1680928

andybones said:
https://forum.xda-developers.com/showthread.php?t=1680928
Click to expand...
Click to collapse
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also

drago10029 said:
hmmmm according to that post the TWRP i flashed should have reverted on reboot and that hasn't been the case at all since it has survived multiple reboots... any thoughts on that?
"...Basically, all changes made to these partitions while the phone is running is not permanent, and will be reset upon a reboot..."
EDIT: also does that mean unless I have S-off none of the custom ROMs will flash? so what's the point of unlocking a bootloader is that needs to be disabled also
Click to expand...
Click to collapse
Keep in mind the date on that post is from a few years back (2012). You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
From my small amount of time, I think you may be confused about what the difference is between an unlocked bootloader and S-OFF, which I'd need to even go back and read that article, but thought it touched a little on it
The 10 has changed quite a bit too from past phones. Before you'd need to be S-OFF and unlocked bootloader. Now S-OFF unlocked and S-OFF locked are basically the same, but that can be found in threads if you'd like to find more info on that.
Most the info is there, you just need to search. If you need help finding articles, I can try and help with that. I've been surprised with the great info I've found after awhile of coming up empty.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
It seemed you were in a simple bootloop, but I'm not 100%. I think your issue was flashing MM ROM on N firmware. Can't do that.
Also, Verizon doesn't allow us to unlock bootloader on Htc-dev. So if we want to root, we must S-OFF.

andybones said:
Keep in mind the date on that post is from a few years back. You can't put all your eggs into one basket, so to speak. I was just giving you 1 article I found from a simple Google Search. Encryption and TWRP have changed quite a lot, especially since Nougat.
I'm just now seeing all the new posts that came from before I posted and have been on my phone and don't have the time to catch up on it all right now.
Hope things get squared away for you soon, I'll check in when I can.
Click to expand...
Click to collapse
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.

drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash

andybones said:
What method have you tried for the SW?
is it an RUU or just firmware?
I suggest the sdcard method.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure.
https://www.androidfilehost.com/?fid=24545065934258327
Either remove your current fastboot.exe and rename this one to it, or keel it as htc_fastboot.exe and use the correct, htc_fastboot flash, over fastboot flash
Click to expand...
Click to collapse
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?

drago10029 said:
bear in mind I'm still learning all this HTC stuff lol
is it an RUU or just firmware? It's an RUU.exe for HTC 10 unlocked edition that i got from there website
I suggest the sdcard method. you mean installing custom ROM zip from sd card? otherwise i'm not sure what you mean.
Make sure to have the correct htc_fastboot.exe over the standard fastboot.exe, this could be the cause of your failure. hmmm well I used fastboot.exe from minimal adb & fasboot to unlock bootloader and that worked fine, and should i still i just replace fastboot in platform tools folder with fastboot.exe from htc website?
also so s-off shouldn't be needed to install the ROMs? just bootloader unlock?
Click to expand...
Click to collapse
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.

andybones said:
Keep in mind this is me helping in my free time.
Use the linked htc_fastboot.. It's made for htc, it's why I mentioned it..
I've seen many ppl have RUU fail by not using this.
Also an RUU/firmware have 3 methods to install.
I suggest the sd-card method. Safest.
Search. Search. Search. ...
Option 1
Copy 2PS6IMG.zip (THIS IS FOR VERIZON, YOUR CARRIER WILL NEED TO BE RENAMED CORRECTLY) to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
--Taken from
Also read here. This is a great thread.
There's a lot of info out there.
Just search and do your homework.
It's easy to turn that device into a useless brick.
Especially being S-OFF... Secuirty-off..
I know it can be overwhelming, but the info is out there, and if not, just ask, as others most likely have the same question and this will help them.
And correct, with S-OFF isn't needed to flash ROMs. Only bootloader unlock.
Click to expand...
Click to collapse
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.

drago10029 said:
my bad, i hope i didn't come off rude or anything. i do appreciate all your help and i understand it. I do the same here when i have the free time.
I will ask some question's on both those threads you linked. I came across one of them but no s-off and didn't wanna pay for sunshine app. also topjohnwu thread about stock and guides would be helpful if it listed which phones the code names correlate to.
in the end I see your point, keep researching and asking. and I do that very often and promise. today was different since a bunch of PC failed to install updates at work (post wannacry) lol and dealing with my bootlooping phone, my mind was scattered. iv'e bricked before but never on a phone this expensive *__*
thanks again andy!
JUST AN UPDATE: i restored via twrp after i got the bootlooping to stop. I completely forgot I had made one -__- (more scatter brains) so I'm good to go now.... kinda.
Click to expand...
Click to collapse
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.

andybones said:
You didn't come off rude at all, I was actually hoping you didn't take my response as being rude. S-OFF and sunshine is completely worth the $25. However, for a normal user like yourself, you don't need it.
Glad to hear that you're somewhat good to go, lol.
You can always pm me or tag me in a post if needed and I'll do my best to help.
Click to expand...
Click to collapse
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)

drago10029 said:
glad no guns are being drawn here
and since no you offered lol.... how do i get my CID and MID? using the fastboot you kindly spotted me...
fastboot getvar all and fastboot oem readcid: both return nothing but fastboot not recognized..... etc. etc. I am in download mode (unlocked and s-on if that matters)
Click to expand...
Click to collapse
Fastboot isn't recognized? As in it's not working?

drago10029 said:
gotcha and thanks! so for anyone else who wants to help. I have regained access to download mode and bootloader. when attempting to run latest official RUU.exe from HTC's site, i get error 155. via HTC the error means I'm using the wrong update but my phone reports SW 2.48.617.1 and I'm trying to update it to SW 2.48.617.3.
also i have relocked the bootloader and have s-off.
Click to expand...
Click to collapse
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?

andybones said:
Fastboot isn't recognized? As in it's not working?
Click to expand...
Click to collapse
xunholyx said:
2.48.617.3? I don't think there is such a thing. Do you mean 2.41.617.3?
Click to expand...
Click to collapse
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.

drago10029 said:
1st things 1st, SOS is no more. was trying to flash leedroid magisk file, thinking it was a ROM until i noticed the file size so I went back to stock via TWRP backup (i forgot I made) since RUU was giving 155 error.
2nd the HTC fastboot wasn't working for some reason.. adb devices cmd detected nothing, it worked at my job though since i have android studio/platform tools there (shrug) so used that fastboot instead.
3rd I did mean SW 2.48.617.1 that's the exact OS version # that download mode reports currently and was the last official update i took several days before going custom route.
Click to expand...
Click to collapse
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3

xunholyx said:
Okay. Cool that you got it fixed. But you did say you were trying to update from 2.48.617.1 to 2.48.617.3, so that's why I said there was no .3
Click to expand...
Click to collapse
oooh i see lol.. too many numbers.

boot loader . .

How do I unlock the boot loader when there is no oem setting to allow unlocking the boot loader in developer options? I have the token the phone is running marshmallow. It is S off and has CID 11111111. One thing can I flash TWRP to my phone without messing with the boot loader. If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.

jconradb said:
How do I unlock the boot loader when there is no oem setting to allow unlocking the boot loader in developer options? I have the token the phone is running marshmallow. It is S off and has CID 11111111. One thing can I flash TWRP to my phone without messing with the boot loader. If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.
Click to expand...
Click to collapse
I'm not sure what your exact situation is but i don't think OEM unlocking through Settings is an option. Have you tried this ... See link below
https://forum.xda-developers.com/showthread.php?t=2708571

Aimless Rambler said:
I'm not sure what your exact situation is but i don't think OEM unlocking through Settings is an option. Have you tried this ... See link below
https://forum.xda-developers.com/showthread.php?t=2708571
Click to expand...
Click to collapse
Yes my comment is vague, I want to unlock my boot loader but cannot. All settings on the M8 are set such as USB debugging and I have the unlocking code from HTC. When I proceed to unlock the phone and choose option to unlock the phone, phone reboots but the boot loader is still locked. On the HTC web site it states with Marshmallow this can happen and you must go to developers options and highlight OEM option to unlock the boot loader but the option is not there and I'm stuck. Thank you for your reply

Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed

miffymiffy said:
Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed
Click to expand...
Click to collapse
Thank you so much I will try that later today and get back to you. Again thanks for the reply ?

miffymiffy said:
Did you try fastboot oem unlock? If it's soff and supercid, should be all that is needed
Click to expand...
Click to collapse
Far as I know, this will not work.
May need to use the following method (if unlock token doesn't work) and root is also required:
https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------
jconradb said:
If so then I can just use TWRP to flash the model ID and EU RRU thanks in advance. Just read I cannot flash TWRP without unlocking the boot loader.
Click to expand...
Click to collapse
It is correct, you cannot flash TWRP with a locked bootloader (needs to be unlocked) by definition.
But you also don't flash an RUU in TWRP. You also may not need to change the MID, depending on what version you have.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Need to verify some details before supplying advice, which may be harmful to your device.

redpoint73 said:
Far as I know, this will not work.
May need to use the following method (if unlock token doesn't work) and root is also required:
https://forum.xda-developers.com/showthread.php?t=2708571
---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------
It is correct, you cannot flash TWRP with a locked bootloader (needs to be unlocked) by definition.
But you also don't flash an RUU in TWRP. You also may not need to change the MID, depending on what version you have.
Please do fastboot getvar all, and post the results (delete IMEI and serial number before posting). Need to verify some details before supplying advice, which may be harmful to your device.
Click to expand...
Click to collapse
Here you go and thanks

jconradb said:
Here you go and thanks
Click to expand...
Click to collapse
What RUU are you trying to run, and how exactly (command syntax, etc.)?
Are you actually getting a model ID error when running the RUU?

redpoint73 said:
What RUU are you trying to run, and how exactly (command syntax, etc.)?
Are you actually getting a model ID error when running the RUU?
Click to expand...
Click to collapse
I want to change to EU RUU so as I understand I must change model id as mine is developer model id as is my RUU. Plus rooting would be nice

jconradb said:
I want to change to EU RUU
Click to expand...
Click to collapse
I should have been more specific. What RUU number, and where did you get it from?
jconradb said:
I want to change to EU RUU so as I understand I must change model id as mine is developer model id as is my RUU.
Click to expand...
Click to collapse
Your model ID (MID) is for AT&T and Developer's Edition.
You may or may not need to change the MID, in order to run the Euro RUU. Sometimes (often) having SuperCID (11111111) will bypass the MID check for RUUs. So I would suggest running the RUU, and see if it gives you model ID error, or if it just work (before messing with the MID, if you don't have to).

redpoint73 said:
I should have been more specific. What RUU number, and where did you get it from?
Your model ID (MID) is for AT&T and Developer's Edition.
You may or may not need to change the MID, in order to run the Euro RUU. Sometimes (often) having SuperCID (11111111) will bypass the MID check for RUUs. So I would suggest running the RUU, and see if it gives you model ID error, or if it just work (before messing with the MID, if you don't have to).
Click to expand...
Click to collapse
Actually this whole thing started when I installed the developer RUU on the phone. After this I noticed when I launched the camera a message came that the lens is blocked. I think it's a RUU issue. You see the RUU I had before which was Kit Kat camera worked but many other issues. The marshmallow RUU was downloaded from a member of this forum forget his name

jconradb said:
Actually this whole thing started when I installed the developer RUU on the phone. After this I noticed when I launched the camera a message came that the lens is blocked. I think it's a RUU issue.
Click to expand...
Click to collapse
Unlikely an issue with the RUU itself. I was on the Dev Edition RUU for a while (as have many others), and the camera worked fine. But it's not a bad idea to try the Euro RUU, and see if that helps.
jconradb said:
The marshmallow RUU was downloaded from a member of this forum forget his name
Click to expand...
Click to collapse
Wow, that is remarkably vague. The file doesn't have a version number, or name? Not providing any useful info, forces us to guess. Lucky for you, I have a pretty good guess.
Try the following Euro RUU, and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, if you have an SD card, rename the RUU zip to 0P6BIMG.zip put the file on the SD card, insert in phone, and reboot to bootloader, and it should install automatically.
Let us know if it installs, or if you get error messages (and what the error messages are, specifically).

redpoint73 said:
Unlikely an issue with the RUU itself. I was on the Dev Edition RUU for a while (as have many others), and the camera worked fine. But it's not a bad idea to try the Euro RUU, and see if that helps.
Wow, that is remarkably vague. The file doesn't have a version number, or name? Not providing any useful info, forces us to guess. Lucky for you, I have a pretty good guess.
Try the following Euro RUU, and instructions:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Alternately, if you have an SD card, rename the RUU zip to 0P6BIMG.zip put the file on the SD card, insert in phone, and reboot to bootloader, and it should install automatically.
Let us know if it installs, or if you get error messages (and what the error messages are, specifically).
Click to expand...
Click to collapse
Ckpv5 was his name on this forum he uploaded the file

jconradb said:
Ckpv5 was his name on this forum he uploaded the file
Click to expand...
Click to collapse
So to do your install I can do this with the standard recovery and model id I have

jconradb said:
So to do your install I can do this with the standard recovery and model id I have
Click to expand...
Click to collapse
Recovery doesn't matter for RUU install, it will be overwritten by stock recovery regardless of what is presently there.
Model ID is what I mentioned before. The RUU may or may not work with your MID. If it fails with model ID error, we know we need to change the MID. If it works, then it works.

redpoint73 said:
Recovery doesn't matter for RUU install, it will be overwritten by stock recovery regardless of what is presently there.
Model ID is what I mentioned before. The RUU may or may not work with your MID. If it fails with model ID error, we know we need to change the MID. If it works, then it works.
Click to expand...
Click to collapse
Hello I am worried to flash the RUU because I tried to change the mid to EU using adb she'll message permission denied oem blocked, stupid at&t

jconradb said:
Hello I am worried to flash the RUU because I tried to change the mid to EU using adb she'll message permission denied oem blocked, stupid at&t
Click to expand...
Click to collapse
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.

redpoint73 said:
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.
Click to expand...
Click to collapse
OK I will follow your advice thank you for your time and effort

redpoint73 said:
AT&T has nothing to do with it, it's not what "oem blocked" means. This is probably pilot error. Do you have root, since it's required to change the MID?
And you are not following my advice why, because of some assumed or imagined fear that isn't based on any fact? Flashing the RUU with the wrong MID is not going to harm the device. The worst that will happen is an error message (wrong model) and the RUU will not install. The phone remains exactly as it was before you tried the RUU. And meaning you have to change the MID to run the RUU.
Best case, the RUU works, and you no longer have to mess with changing the MID.
Click to expand...
Click to collapse
OK let's assume this RUU works will try tomorrow I think. How would I root this phone remembering the issues to unlock the boot loader. The unlock code did not work because of the oem option missing developer

jconradb said:
OK let's assume this RUU works will try tomorrow I think. How would I root this phone remembering the issues to unlock the boot loader. The unlock code did not work because of the oem option missing developer
Click to expand...
Click to collapse
oem unlocking being "missing" is not the problem. It wasn't on most OS builds for the M8, and was only added later. In fact, I'm not sure it was ever present on this device (or maybe just some versions). If it's not there, you don't need to enable it. Unlocking the bootloader should work normally.
So clearly, something is wrong, if you are doing the bootloader unlock, and it doesn't work. Let's try to run the RUU, and go from there.

HTC 10 does not detect SIM card after battery and LCD replacment.

Hey guys,
After getting overwhelming reading on forums only to get my self confused at the end. Most threads I came across is last edited in 2016. Therefore I am little skeptical about moving forward.
Bottomline problem, Phone is fully working with PixelExperience ROM installed ( Clean flash) at the moment. BUT IT DOES NOT DETECT SIM CARD.
Model : HTC 10
Android Version : 9
Kernel Version : 3.18.120-IceMan-CAF-LA.UM.7.5
The phone was bought unlocked from HTC.
I have bootloader unlocked, but S-on.
TWRP version 3.3.1 (as of July 22-2019)
Upon reading many thread, It boils down to that I need to RUU in order to get my radio back working. (SIM card detection)
now RUU will not work unless I have S-off, in order to get S-off in need to pay sunshine fee.
Now sunshine needs device to be rooted.
My device is never rooted before, now rooting device has choices, something called SuperSu or Magisk etc.
this is where I am super confused.
I need help before I move on.
My understanding is
step 1: root the device as I already have bootloader unlocked. and TWRP installed and working.
Step 2 : get the S-off by paying sunshine fee
Step 3 : RUU the zip to go back to stock!! ( here also one more question , my kernel is already latest what does RUU do? will it downgrade? )
Step 4 : insert sim and use the Phone as intended !!!(lol)
Please help, I am having nightmare.

theteju said:
Hey guys,
After getting overwhelming reading on forums only to get my self confused at the end. Most threads I came across is last edited in 2016. Therefore I am little skeptical about moving forward.
Bottomline problem, Phone is fully working with PixelExperience ROM installed ( Clean flash) at the moment. BUT IT DOES NOT DETECT SIM CARD.
Model : HTC 10
Android Version : 9
Kernel Version : 3.18.120-IceMan-CAF-LA.UM.7.5
The phone was bought unlocked from HTC.
I have bootloader unlocked, but S-on.
TWRP version 3.3.1 (as of July 22-2019)
Upon reading many thread, It boils down to that I need to RUU in order to get my radio back working. (SIM card detection)
now RUU will not work unless I have S-off, in order to get S-off in need to pay sunshine fee.
Now sunshine needs device to be rooted.
My device is never rooted before, now rooting device has choices, something called SuperSu or Magisk etc.
this is where I am super confused.
I need help before I move on.
My understanding is
step 1: root the device as I already have bootloader unlocked. and TWRP installed and working.
Step 2 : get the S-off by paying sunshine fee
Step 3 : RUU the zip to go back to stock!! ( here also one more question , my kernel is already latest what does RUU do? will it downgrade? )
Step 4 : insert sim and use the Phone as intended !!!(lol)
Please help, I am having nightmare.
Click to expand...
Click to collapse
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?

andybones said:
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
Click to expand...
Click to collapse
kindly see the screenshot attached. very first line says S-on people not here.
my model is HTC 10
SN# HT69XBN00387
it is GSM unlocked.

andybones said:
Where are you reading soff is needed for ruu.
That's not true.
You need an ruu for your specific device model.
Which model is your 10?
Click to expand...
Click to collapse
Now I know what you asking. may be this is proper answer.
fastboot getvar all
kernel: lk
product: htc_pmewl
version: 1.0
max-download-size: 1578400000
serialno: HT69XBN00387
slot-count: 0
current-slot:
imei: 354259077770388
version-main: 3.16.617.2
boot-mode: download
version-baseband: [email protected]
version-bootloader: 1.0.0.0000
mid: 2PS650000
cid: BS_US001
Click to expand...
Click to collapse

theteju said:
kindly see the screenshot attached. very first line says S-on people not here.
my model is HTC 10
SN# YOU CAN HIDE THIS.. NOT NEEDED AND SPECIFIC TO YOUR DEVICE.
it is GSM unlocked.
Click to expand...
Click to collapse
Do you see it say FIRMWARE.. that's not an ruu.
Firmware is a way of updating from say N to P without needing to flash entire ruu.
Firmware is in the ruu along with system, boot, recovery..
theteju said:
Now I know what you asking. may be this is proper answer.
Click to expand...
Click to collapse
3.16.617.2 = us unlocked
Simply find the 3.16.617.2 RUU and flash it.
Here.. https://androidfilehost.com/?fid=818070582850487062
This will wipe internal storage..
How to install:
Option 1 - PERSONALLY SUGGESTED
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Option 2
EXE option. Download EXE file below (for windows) and simply double click to start. You can either be booted to OS with USB debugging enabled OR booted into download mode for this to start.
Option 3
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUU zip file and place in your working fastboot/adb directory. Boot your phone to download mode and connect to PC. Issue the following commands.
htc_fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
htc_fastboot flash zip 2PS6IMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "htc_fastboot reboot-bootloader" command and restart option 1 again.
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "htc_fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!

andybones said:
Do you see it say FIRMWARE.. that's not an ruu.
Firmware is a way of updating from say N to P without needing to flash entire ruu.
Firmware is in the ruu along with system, boot, recovery..
3.16.617.2 = us unlocked
Simply find the 3.16.617.2 RUU and flash it.
Here.. https://androidfilehost.com/?fid=818070582850487062
This will wipe internal storage..
How to install:
Option 1 - PERSONALLY SUGGESTED
Download the RUU.zip file. Rename the zip file to 2PS6IMG.zip (being careful that you have file extensions turned on, or are aware that it could be renamed to 2PS6IMG.zip.zip, which is bad) Copy 2PS6IMG.zip to root of a physical SD formatted to fat32 or exfat! No internal storage!
Reboot phone to download mode and follow prompts once RUU is detected by phone.
Click to expand...
Click to collapse
Respected Andybones,
I cannot thank you enough sir. After struggling for almost 48 hours. reading a lot threads. Sleepless nights. Finally my Phone is Back to Stock!!
(I am certainly hoping that it would now see the SIM card. I have to go to At&t store tomorrow to get my IMEI into their system.)
I just want to borrow your brain for few more questions.
I noticed that I am on Android 8 now.
Does this mean, My bootloader is locked again? TWRP is gone?
Can I install custom ROM?
Finally, what caused such issue? I do not understand what happened?
If you own HTC 10, what rom do you recommend? I used LinageOS.
Let me know,
Sincerely,

theteju said:
Respected Andybones,
I cannot thank you enough sir. After struggling for almost 48 hours. reading a lot threads. Sleepless nights. Finally my Phone is Back to Stock!!
(I am certainly hoping that it would now see the SIM card. I have to go to At&t store tomorrow to get my IMEI into their system.)
I just want to borrow your brain for few more questions.
I noticed that I am on Android 8 now.
Does this mean, My bootloader is locked again? TWRP is gone?
Can I install custom ROM?
Finally, what caused such issue? I do not understand what happened?
If you own HTC 10, what rom do you recommend? I used LinageOS.
Let me know,
Sincerely,
Click to expand...
Click to collapse
You're so very welcome.
Trust me, I know how tough it can be to fully understand an htc device and it's workings. Once you start to get into it like you have now, I'm sure you came out with some knowledge, so I'm more than happy to help.
I didn't realize you were still on Android 7. You're on 8 now because the RUU I gave you was android 8.(don't try and downgrade. You can but it's not as easy as flashing the android 7 ruu)
The ruu contains everything to make your device stock again, including stock system, stock kernel, stock recovery.
Flashing ruu doesn't touch an soff flag nor bootloader lock.(boot on into download mode and check it out). But even if it did lock it, which won't ever happen, you can always re-unlock bootloader.
It's only us Verizon users who suffer by blocking us from unlocking. NOT COOL VERIZON!!!
You just need to flash twrp again (get latest version), then flash roms as you desire.
I suggest any recent Pie rom. Thanks to dev Fagyi he has really made this phone great again. He maintains Stock lineage 16 is awesome, and theirs a few roms out based on his lineage, including my crdroidandroid rom. Also Fagyi has I think 2 roms based on AOSP rather lineage.
If you want Sense then LeeDroid is the ROM you want.
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:

andybones said:
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
Click to expand...
Click to collapse
andybones said:
I'm actually not too sure what caused the sim issue unfortunately. I do have faith that att can get it going for you tmw. Fingers are crossed my friend.
Please keep me posted. :good:
Click to expand...
Click to collapse
Respected Andybones,
This is just an update. Please give me your input whenever u get a chance. Here is what happened.
My phone got back to stock succefully. I noticed it did not touch the bootloader. it was still unlocked. S-on. I successfully flashed TWRP again. All went well. Next day morning I was supposed to go to ATT store and get phone working. but I could not wait till morning. That night I flashed the phone with Pixel Experience again, as I thought my radio should be working now. ( I think I should have waited. Not sure why?)
So once again, I have perfectly working phone with Pixel Experience rom on it. but yet again it does not detect SIM card. The difference between stock and this rom is, STock was showing bars on top. at least detecting no cellular network. This is my uneducated guess!! lol
I am one-more time going to RUU with your zip. restore back to stock and shall see what happens. ( I know I should have waited before I flashed with PE)
Just to confirm and make sure.. I believe am currently on Oreo Firmware as the OS - 3.16.617.2 ( displays on download mode)
I think I should still be fine with the RUU zip you gave me.

theteju said:
Respected Andybones,
This is just an update. Please give me your input whenever u get a chance. Here is what happened.
My phone got back to stock succefully. I noticed it did not touch the bootloader. it was still unlocked. S-on. I successfully flashed TWRP again. All went well. Next day morning I was supposed to go to ATT store and get phone working. but I could not wait till morning. That night I flashed the phone with Pixel Experience again, as I thought my radio should be working now. ( I think I should have waited. Not sure why?)
So once again, I have perfectly working phone with Pixel Experience rom on it. but yet again it does not detect SIM card. The difference between stock and this rom is, STock was showing bars on top. at least detecting no cellular network. This is my uneducated guess!! lol
I am one-more time going to RUU with your zip. restore back to stock and shall see what happens. ( I know I should have waited before I flashed with PE)
Just to confirm and make sure.. I believe am currently on Oreo Firmware as the OS - 3.16.617.2 ( displays on download mode)
I think I should still be fine with the RUU zip you gave me.
Click to expand...
Click to collapse
Hey man, I don't think it's any issue you flashed pixel experience. You can always just reflash the ruu and get back to stock. Unfortunately, it could be a physical issue with the sim not getting detected but since stock showed bars, I think you need a new att sim card possibly.
But yes you may flash that same ruu and any that are x.xx.617.x and up. But I think the one I gave is the newest.
.617 refers to your device.
Mine for example (Verizon) is .605
Hope I've been of help. :good:

andybones said:
Hey man, I don't think it's any issue you flashed pixel experience. You can always just reflash the ruu and get back to stock. Unfortunately, it could be a physical issue with the sim not getting detected but since stock showed bars, I think you need a new att sim card possibly.
But yes you may flash that same ruu and any that are x.xx.617.x and up. But I think the one I gave is the newest.
.617 refers to your device.
Mine for example (Verizon) is .605
Hope I've been of help. :good:
Click to expand...
Click to collapse
Your guess was right. Does not seem like ROM issue. It now seems like hardware issue. I may have missed to connect an antenna properly. Or Something got damaged. I cannot say for sure.
I am now on market to for new phone at an odd time of the year !!!
I must thanks again for all your replies and answers with patience.

theteju said:
Your guess was right. Does not seem like ROM issue. It now seems like hardware issue. I may have missed to connect an antenna properly. Or Something got damaged. I cannot say for sure.
I am now on market to for new phone at an odd time of the year !!!
I must thanks again for all your replies and answers with patience.
Click to expand...
Click to collapse
Dang, I'm sorry my friend. And you're so very welcome.
You didn't mention what happened when you brought to att
I wish it could hold for the pixel4, i think im gunna grab one.That or maybe something else, who knows, lol.
but best wishes!

andybones said:
Dang, I'm sorry my friend. And you're so very welcome.
You didn't mention what happened when you brought to att
I wish it could hold for the pixel4, i think im gunna grab one.That or maybe something else, who knows, lol.
but best wishes!
Click to expand...
Click to collapse
I am temperory using iphone 4s. Life is in slowMotion mode using that phone since two weeks. LOL
I am eyeing Nokia 7.1. What are your thoughts?
any comment on Mi9?