Can't update firmware to Oreo. - HTC 10 Questions & Answers

Hey, I'm having a bit (or a **** ton) of trouble updating my firmware from Marshmallow to Oreo, and it's getting really frustrating.
I was on RR before, so I never really updated the firmware, but since Xposed for Oreo is out, I decided to update to LeeDroid. The problem is that, since LeeDroid requires the latest Oreo firmware, I had to update it (or try to), and no matter any method I've tried, it won't work. And the problem is, it doesn't even allow me to update for Nougat either.
At first I thought it was some issue with the CID (maybe I downloaded the wrong RUU), so I downloaded firmware for my CID and tried to update via both fastboot and download mode's SD card thing and neither worked. When using fastboot, it would give me "9 RU_SECURITY_FAIL" and when using SD card, it would give me "14 RU_ZIP_INFO_ERROR android-info missing or malformed" even though I checked the zip I was flashing, and the android-info text file was there (and this is Nougat firmware). Nothing is helping and it's becoming extremely frustrating.
I also tried using stock Marshmallow (which I was able to get via TWRP backup since that was the only way I could get pure stock) and tried just doing an OTA from there, but it didn't work, no update showed up.
Phone's info:
CID: HTC__J15 (which I believe is GCC).
MID: 2PS620000
Current Firmware: 1.95.401.4
S-ON
Bootloader unlocked (obviously).
I'm using Pure Fusion temporarily.
Update: I managed to go S-OFF but I still can't flash any RUUs. I can flash firmware files, but any RUU zip I've downloaded just causes some kind of error. I tried flashing some kind of stock recovery to apply an update (if that would even work) but I keep getting an error screen (the one with a phone and a red sign on its screen).
Phone's info (as of update):
CID: 11111111 (SuperCID).
MID: 2PS620000
Current Firmware: 1.95.401.4
S-OFF
Bootloader unlocked (obviously).
Update 2: Nevermind, I killed the phone and paid $25 for nothing. Yay.

You cannot just update the firmware if s-on... Thats first issue... You will need to revert to current build,flash stock recovery and take the ota's in sequence...As far as no notifications... It would be instant may take a bit
majidamiri15300 said:
Hey, I'm having a bit (or a **** ton) of trouble updating my firmware from Marshmallow to Oreo, and it's getting really frustrating.
I was on RR before, so I never really updated the firmware, but since Xposed for Oreo is out, I decided to update to LeeDroid. The problem is that, since LeeDroid requires the latest Oreo firmware, I had to update it (or try to), and no matter any method I've tried, it won't work. And the problem is, it doesn't even allow me to update for Nougat either.
At first I thought it was some issue with the CID (maybe I downloaded the wrong RUU), so I downloaded firmware for my CID and tried to update via both fastboot and download mode's SD card thing and neither worked. When using fastboot, it would give me "9 RU_SECURITY_FAIL" and when using SD card, it would give me "14 RU_ZIP_INFO_ERROR android-info missing or malformed" even though I checked the zip I was flashing, and the android-info text file was there (and this is Nougat firmware). Nothing is helping and it's becoming extremely frustrating.
I also tried using stock Marshmallow (which I was able to get via TWRP backup since that was the only way I could get pure stock) and tried just doing an OTA from there, but it didn't work, no update showed up.
Phone's info:
CID: HTC__J15 (which I believe is GCC).
MID: 2PS620000
Current Firmware: 1.95.401.4
S-ON
Bootloader unlocked (obviously).
I'm using Pure Fusion temporarily.
Click to expand...
Click to collapse

Wonders_Never_Cease said:
You cannot just update the firmware if s-on... Thats first issue... You will need to revert to current build,flash stock recovery and take the ota's in sequence...As far as no notifications... It would be instant may take a bit
Click to expand...
Click to collapse
The S-ON thing I get, but with current build, I sat there with stock MM and hit check for updates like a million times and nothing came up. Aside from that, I still don't know how to go S-OFF without having to pay that $25, because that much money just seems absurd to pay.

That 25 bucks is really good investment. Trust me. Makes your life with htc 10 much easier.

Zeezala said:
That 25 bucks is really good investment. Trust me. Makes your life with htc 10 much easier.
Click to expand...
Click to collapse
Hmmmmm, well I do have the money for it, but just a question: is it safe if I know what I'm doing, flash wise? Like my phone won't get screwed up for no reason?

In my case, S-OFF app did everything itself. If you know, what you are you doing with your phone, it shoulnt get screwed.
Do some reading about S-OFF and firmware updates and so on.
Honestly, i did some reading, but Im not 100% sure what Im doing. Fortunately, my phone is still alive...

Zeezala said:
In my case, S-OFF app did everything itself. If you know, what you are you doing with your phone, it shoulnt get screwed.
Do some reading about S-OFF and firmware updates and so on.
Honestly, i did some reading, but Im not 100% sure what Im doing. Fortunately, my phone is still alive...
Click to expand...
Click to collapse
Okay, what the hell? I decided to go with S-OFF and installed the SunShine APK, then did all the tests and whatnot and paid for the license. Then the phone rebooted, but when I went into the bootloader to check, it still said "S-ON."

Try run it againg or check some thread related to Sunshine. I can remember i installed app, paid, run it, i took some time, phone rebooted couple of times... Last thing was question, what i want. S-OFF locked, S-OFF unlocked...

Zeezala said:
Try run it againg or check some thread related to Sunshine. I can remember i installed app, paid, run it, i took some time, phone rebooted couple of times... Last thing was question, what i want. S-OFF locked, S-OFF unlocked...
Click to expand...
Click to collapse
I ran it 3 times so far, still the same thing. I just opened a ticket with SunShine and hope they reply soon.

And that sunshine test was ok? Your bootloader is unlocked?

Zeezala said:
And that sunshine test was ok? Your bootloader is unlocked?
Click to expand...
Click to collapse
Actually, nevermind that. SunShine replied and they helped me S-OFF, but the problem now is that I can't flash any RUUs for some reason. None of them work.

Try changing to Super CID, then you can flash any RUU made for the 10. You could also try an SD card-version of an RUU, "2PS6IMG.zip".
Just Google for:
Code:
htc 10 change to super cid

Sunshine
majidamiri15300 said:
I ran it 3 times so far, still the same thing. I just opened a ticket with SunShine and hope they reply soon.
Click to expand...
Click to collapse
Did you do a Google search for the video by rootjunky?
https://www.google.com/search?safe=...3i22i29i30k1j33i160k1j30i10k1.103.ONfztkfIoNc

roirraW "edor" ehT said:
Try changing to Super CID, then you can flash any RUU made for the 10. You could also try an SD card-version of an RUU, "2PS6IMG.zip".
Just Google for:
Code:
htc 10 change to super cid
Click to expand...
Click to collapse
The MID has to match as well

majidamiri15300 said:
Actually, nevermind that. SunShine replied and they helped me S-OFF, but the problem now is that I can't flash any RUUs for some reason. None of them work.
Click to expand...
Click to collapse
You must be flashing the RUU wrong. You never needed to go S OFF and you don't need supercid either. Here is the RUU you need
https://androidfilehost.com/?fid=817550096634797504
Rename to 2PS6IMG.zip
Place on ex SD card
Boot to download mode
Press vol up to flash.
RUU will erase everything. once the RUU has flashed turn you phone back on and take the OTA.

yldlj said:
You must be flashing the RUU wrong. You never needed to go S OFF and you don't need supercid either. Here is the RUU you need
https://androidfilehost.com/?fid=817550096634797504
Rename to 2PS6IMG.zip
Place on ex SD card
Boot to download mode
Press vol up to flash.
RUU will erase everything. once the RUU has flashed turn you phone back on and take the OTA.
Click to expand...
Click to collapse
THANK YOU SO MUCH, spent HOURS bricking my device trying to get oreo, this worked !

breakfrecell said:
THANK YOU SO MUCH, spent HOURS bricking my device trying to get oreo, this worked !
Click to expand...
Click to collapse
Your welcome
Sent from my OnePlus6 using XDA Labs

Related

Quick RUU Question, need to bring my phone back to TMO

I'm done with these issues that my phone is having. It keeps locking up no matter what ROM I use or how little apps I have installed. Something has got to be wrong with my phone and it's time to bring it back to TMO for repair/replacement.
I found this link on HTC to download the RUU: http://www.htc.com/us/support/rom-downloads.html#tmobile
My question is, would this be enough to bring my phone back to stock so that they don't know I've rooted it?
Edit: Also, I just remembered about my bootloader being s-off/unlocked. Would this make a difference or would the RUU set everything back like it should?
Edit again: I found this thread: http://forum.xda-developers.com/showthread.php?t=2735235
So, would I be able to follow his instructions but change the CID to t-mob010 instead of the ones he has listed?
Nobody? I could really use some input on this, I don't want to brick my phone. I have to do this today, I can't take the lockups anymore.
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
jshamlet said:
There is a thread dedicated to returning your device to stock. It's intended for European users, but the instructions apply equally well to US users.
The first step is running the RUU, then locking (not relocking) the bootloader using adb commands. Reference http://forum.xda-developers.com/showthread.php?t=2708571 (for instructions on locking your bootloader)
Note that you can run the RUU without locking your bootloader if you are S-off. Once you are back to bone stock (recovery + OS), you can then go back S-on if you are concerned about the warranty, though I strongly advise AGAINST this in general.
Also, you may find that simply re-running the RUU will clear up your issue. I'd run it for a few days after restoring the phone before assuming a hardware fault.
Click to expand...
Click to collapse
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
ned4spd8874 said:
Yes, I did find that post and am planning on following those instructions. However, you've confused me. According to that thread, they say to lock the bootloader first and then install the RUU; but you said the opposite. Which is it?
http://forum.xda-developers.com/showthread.php?t=2735235
Also, why are you against turning back S-on? I had planned on it because I don't want to take the chance of TMO or HTC having a problem.
Click to expand...
Click to collapse
You are S-off, which means you do NOT have to lock the bootloader first. Most instructions for running an RUU assume you are S-on, however, which does require your bootloader to be locked. It's one of the checks that is disabled by S-off.
Also, S-off is getting harder to obtain, so unless there is a pressing reason to go S-on, it's safer to remain S-off. Warranty support could be that pressing reason.
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
ned4spd8874 said:
Time to turn back S-on. Even after the RUU, it's still very buggy. Locking up, slow, lag, etc. Time to bring it back to TMO.
Anyone know what that will work? I do have the warranty service on it. So will they just replace my phone with a refurb M8, will it be sent out, what can I expect?
Click to expand...
Click to collapse
If you think your phone has bad hardware, then yeah, at this point you need to go ahead and S-on with the assumption that you will get a refurb - especially now that the M9 has been out a while. Who knows what you will get, though. You might even luck out and get a "new old stock" device with 4.4.2. Or, the refurb place could RUU it up to the latest. It's purely the luck of the draw.
Well this sucks. Can't get adb to recognize my phone in recovery. I can when it's booted into the system, but not recovery or the bootloader....
What a pain this is becoming!!!!!!!!!!!! I'm even trying to get into shell when the phone is booted up and sure I can do that, but I can't su! The binary isn't installed. So, what now I have to f'ing install a different ROM, s-on it and then ruu again????
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
ned4spd8874 said:
So I f'ed up and turned S-ON by mistake before I did the commands to clear the bootloader modified messages. And now I can't get S-OFF for the life of me! Sunshine can't get root it says, SuperSU is installed and says a binary needs updating, but when I click on it, it just freezes and won't update the binary. I tried pushing it down via zip/bootloader but that doesn't help. I ran a root checker and it says my phone is rooted, but nothing is working like I expect it to.
I'm still running the stock ROM from the RUU, could that be the issue? Do I have to install a different ROM before I can S-OFF and then RUU again? This is such a pain!!!
Click to expand...
Click to collapse
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
jshamlet said:
If you are still bootloader unlocked, install TWRP, restore an appropriate nandroid backup for your device, root that install, and re-run Sunshine.
If you are bootloader locked, restart the phone into bootloader mode and select the RUU option. Then, re-run the RUU. If your bootloader is locked, it should run and restore everything to stock. Note that if you updated to Lollipop, you may have to use Kingroot to get temp root. I meant to suggest you RUU down to the original version (4.4.2) prior to going S-on and forgot - sorry about that.
Click to expand...
Click to collapse
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
ned4spd8874 said:
Bootloader is still unlocked, but even after installing a couple different ROMs, sunshine just won't work. Says it's incompatible. It says to flash a stock sense or near stock rom. I'm on SkyDragon right now...
I'm at a loss. Anyone have a industrial shredder?
Click to expand...
Click to collapse
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
jshamlet said:
There are probably some T-mobile nandroid backups around here somewhere. Get one, put it on an SD card, and use TWRP to flash it. Unfortunately, I only have DevEd and AT&T images.
Click to expand...
Click to collapse
Things are looking up! Found a ROM called something like Alex V that was stock enough to get SunShine to work. Also, I was using the original version so once I got it to run, it was giving network errors. Once I installed the latest version, that's when I got was able to go S-OFF. So, now I'm S-OFF, the bootloader is saying Official and locked so now I'm going to RUU and throw it in TMO's face!

Returning to stock issues.

I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Webbage said:
I'm currently running Android Revolution HD on my new M9, unlocked, s-off also.
Found out that I have the battery is faulty, so I need to return it to stock, and get it back the shop for a replacement.
However, I stupidly didn't make a back up of my stock rom.
The CID of my phone is O2___01
I've downloaded the stock rom from this site, and flashed it using the RUU command. However when it flashes, then tells me to reboot, it still has Android Revolution HD on it.
I've spent a few hours browsing the forum, and still I've come to no avail.
Any help would be well appreciated!
Click to expand...
Click to collapse
You don't provide much information so it's hard to help. So let's start at the bginning: What firmare version are you using? (It's stated in Download Mode in the line with "OS" at the beginning.)
You tried to flash a RUU? Which one? Have there been any error outputs? If yes, which ones? Since you're S-OFF flashing a RUU should not be a problem at all so these outputs are very important if you want any help.
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Webbage said:
I tried to flash 1.40.206.8 -> 2.10.206.2 from this page
Code:
http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Also I followed this,
Code:
http://forum.xda-developers.com/one-m9/development/firmware-t3068243
downloaded the correct RUU zip, tried to flash, got the error code telling me I need to immediately flash again which I did. Rebooted, and it just set up Android Revolution HD again.-
My firmware currently is 2.10.206.2
Im sure it's something stupid I missing out?
Click to expand...
Click to collapse
As far as I know Sneakyghost doesn't provide any RUUs. Those are only firmware packages that do not contain a rom. So it's no miracle that you're still booting ARHD.
You can download O2 RUUs from here, here or here. Any of the X.XX.206.X files will work since you are S-OFF. Do you have a SD card that is not bigger than 32gb? If yes, format it to fat32, copy one O2 RUU to its root directory and rename that file to "0PJAIMG.zip". If you then boot to Download Mode you will be asked to push the Volume Up button and the RUU will start flashing. If it reboots to system instead of rebooting to Download Mode you will have to power off your phone and boot to Download Mode manually. The RUU will continue then. At the end you will be asked to push the power button so that your phone gets shut down. If you now start your phone you will be back on a stock system.
Be aware that there is no RUU for your current firmware. Since you're S-OFF that doesn't matter but your phone will be downgraded at the end.
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Webbage said:
Ahh no wonder! haha
Going to try this shortly, so will let you know how I get on!
After its flashed, I'll be good to lock again and go s-on? Then return to the shop?
Click to expand...
Click to collapse
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Agreed, use the s-off command to change back to "LOCKED" and leave it s-off. Too much of a risk otherwise.
If in the unlikely event they see it, you can play dumb, because a few rare people have gotten s-off phones from the factory and it doesn't prove you did anything.
Flippy498 said:
Relock only after you successfully tested that your device is booting normaly. After that you theoretically could re-S-ON. (But I would never do that because there is always a risk of hardbricking your phone if you re-S-ON and there is anything still modified that you didn't notice. For safety reasons S-OFF should always be considered as a oneway.)
Edit: I'm not completely sure but I actually doubt that they will check whether your phone was S-OFFed or not. If I think about the people who are working at the O2 or vodafone shops in my city I would say they do not even know what a bootloader is...
Click to expand...
Click to collapse
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Webbage said:
All sorted mate! Thanks a lot for your help!
What recovery am I best restoring on it?
Click to expand...
Click to collapse
Didn't the RUU flash the corresponding stock recovery?
Flippy498 said:
Didn't the RUU flash the corresponding stock recovery?
Click to expand...
Click to collapse
My bad, I didn't check.
All sorted now, thanks again bud!

Full stock Dev Ed M8 won't take OTA or RUU for MM

I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
fyarf said:
I have a Dev edition M8 that i zip RUU'ed back to lollipop. i took a security update successfully, then the 3 preinstall updates in prep for marshmallow. however, I now get an error when taking the actual OTA for marshmallow. I am s-off and bootloader unlocked. I then downloaded the RUU from HTC to run the exe, but i always get error 155. I read @Sneakyghost post about firmware and it said it was either region ID's not matching, or the bootloader being unlocked. I don't see why the unlocked bootloader would be a problem when im s-off and its a dev edition, which is bootloader unlocked out of the box. Anyone know what is causing this?
Click to expand...
Click to collapse
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Sneakyghost said:
Haha nice man I just finished downloading that exact RUU and I have that exact phone in the exact same state. I got it from someone in the US.
I'll let you know how it goes on mine...
Click to expand...
Click to collapse
heres my recovery message, just to maybe help troubleshoot it. it mentions userdata being busy (i got an error in the zip ruu flash for userdata, had to flash the ruu zip twice to get an okay), then kidmode missing. not sure what to do besides flash the firmware from http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Sneakyghost said:
Modified system apps, sir. That's what it is. Did you root your system?
Edit:
Maybe not. Maybe just can't find those apps cuz it can't mount data.
Something wrong there.
No idea.
I'll see where I end up.
Click to expand...
Click to collapse
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
fyarf said:
i did a factory reset from stock recovery, and kid mode is present now, maybe im onto something...
Edit: not rooted directly from a factory ruu zip (well, hopefully the zip creator did a factory dump and was unmodified) but kid mode wasnt an option before the factory reset
Click to expand...
Click to collapse
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Sneakyghost said:
Unfortunately, I'm with family tonight and won't be able to assist until much later. But note this: the factory reset could well help. I can explain later.
Click to expand...
Click to collapse
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
fyarf said:
ok so i got mine to work.. apparently the zip RUU isnt good. i ran the exe 4.16.1540.8 from here http://forum.xda-developers.com/showthread.php?t=2701376 and then updated ota from there without issue. so my guess is the RUU zip wasnt perfect system-wise,while the exe is straight from htc.
Click to expand...
Click to collapse
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Sneakyghost said:
ok. Where you got that zip from? Cuz I downloaded the 6.xx RUU.exe straight from HTC USA...
Click to expand...
Click to collapse
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
fyarf said:
zip was from the same thread, i tried the exe instead because it was an HTC file instead of a contributor. now on MM sense. The 6.xx RUU refused to work no matter what i did, so i OTA'd to the latest version.
Click to expand...
Click to collapse
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Sneakyghost said:
I seem to be having an entirely different problem. After swapping cables, phones and laptop ports as well as updating drivers, it appears that the usb port of my M8 is broken. I'll have to see at someone else's computer, maybe tomorrow. Pretty frustrating right now as I'm liking the M8 better than my M9 and M7.
[EDIT]
I could stabilize the connection enough to run another, international RUU. The RUU worked fine while the 6.12.1540.4 kept getting stuck at either "checking header" or "sending" - both times with a successfully established connection. I already tweeted HTC asking to have that RUU checked. I assume your findings were correctly indicating a bad RUU, since a.) It also didn't work here and b.) people from my team have confirmed seeing several fail scenarios with that RUU spread over XDA.
Guess that's that then. Thanks for raising the issue. I would have messed around with it much longer otherwise since the error messages are not clearly pointing towards a broken RUU.
[EDIT]
More updates: searching the M8 forum for 6.12.1540.4 turned up this: http://forum.xda-developers.com/showthread.php?p=64320571
That'd mean the RUU fails at the hboot pre-update reboot. All that's needed apparently is to flash only the hboot manually first, so it can proceed. Hence also error 155 which usually indicates issues with the system image. You experienced that most likely because the older hboot couldn't extract the system.img from the rom.zip.
Usually, the procedure is:
RUU updates hboot
RUU reboots to boatloader
RUU updates rest of firmware
RUU sends over the system image in parts
Hboot now decrypts and flashes the part.zips
It just looks like mandatory hboot-first-flash didn't happen right, either not rebooting after it or not flashing it at all.
However, this seems to be fixable by running the hboot/firmware package first and then the complete RUU.
Click to expand...
Click to collapse
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Double_a2013 said:
I'm not sure about OP, but that worked perfectly for me. I wonder how HTC let a broken RUU.exe past testing?
Click to expand...
Click to collapse
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Sneakyghost said:
They frequently do. Nothing exciting. That's why I notified HTC. They take their time with fixing them. The earlier the better.
Click to expand...
Click to collapse
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Double_a2013 said:
Wow, I didn't realize that. Now if only they'd fix the ATT LTE issues on the dev rom :silly:
Click to expand...
Click to collapse
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
fyarf said:
My ota to the latest dev version got lte on at&t no problem, sure your apn settings are correct?
Click to expand...
Click to collapse
I've never had to reconfigure them before, regardless of if I'm using GPE or Sense RUUs. I'll give it another shot, and get back in a more timely manner
Edit: Apn settings seem fine. It's using the Nextgenphone one from ATT
Edit #2:
http://forum.xda-developers.com/att...ming-calls-lte-mode-m8-att-arhd-34-0-t3026710
Found this thread about a similar issue. I guess I'll disable HD Voice (Honestly, its borderline useless anyway) and see if that solves anything

Bricked my HTC 10, What to do next?

Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Have you tried doing a factory reset using the stock recovery?
See if you can get a system.img to flash manually. If you can get an OS boot you should be able to fix your device.
tkoreaper said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
Using the adb shell command (recovery --wipe_data)? Yeah I've tried that, but I get a device not found error. adb isn't working right now, however I am still able to get fastboot commands, and the phone recognizing them at least. Otherwise, no I haven't what would I need to do?
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
5m4r7ph0n36uru said:
@tw1tch175 is right. Try to find an untouched system image first and try to flash it in download mode.
Could you in addition tell a bit more about what you did to reset the device to stock instead of flashing a RUU in the first place prior to writing secureflag 3!? And further more what did you do prior to it, did you flash unsigned firmware, or one of the "no red text on boot" aboot provided here!?
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
tw1tch175 said:
Are you making sure you are in download mode for fastboot commands. Also double check your driver in the device manager.
Edit: woops re-read, and he meant use the UI in the factory recovery to reset
Click to expand...
Click to collapse
Yes. I just figured that out while searching haha. I did go through and use the UI, but I had no luck. I am looking for an img like you said but I am not having luck so far. Is there one of the Stock guide on my original post?
Ok so for ALL HTC the only proper way to s-on is to use fastboot/download and for oem writesecureflag 3, you should NEVER EVER EVER us echo/dd /hexeditor to go s-on.
For 2016+ phones, you should use sunshine or another tool to go from unlock/relocked to lock, do NOT use anything not designed for the phone in question, or attempt to do it manually. I can only vouch for SunShine's capability to safely change the bootloader status, I can't vouch for any other method or tool. I know SunShine does it right.
See http://forum.xda-developers.com/htc-10/how-to/psa-htc-10-s-off-s-lock-unlock-t3371264 for my PSA on the subject.
If the phone won't flash with a proper RUU, well you need to find someone with a EMMC write tool to rewrite all your firmware, this is probably going to run $100-200.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
bob3rt said:
Sure. I originally ran the factory wipe/reset via the ROM (Which was the stock rom). Then after that I booted up into the download mode, tried relocking the bootloader with fastboot oem lock. I also flashed the stock recovery for my model. Once I saw that I had the stock recovery on, the bootloader was locked, and everything else, I tried to do a twrp restore and relock it, but it wasn't working so I said "Screw it" and rewrote the secureflag, rebooted and...yeah everything was gone.
The only thing I did before all of this was when I got the phone unlock the bootloader, SOFF, Custom Recovery, and sideload super SU for root. The only "unofficial" radios/firmware/etc I had was the Verizon Radio on my phone.
Other than that I kept it clean. I'm looking for an image now to try that.
Click to expand...
Click to collapse
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
5m4r7ph0n36uru said:
So as I thought. You indeed flashed - at least parts - of an unofficial firmware. Prior to relocking the bootloader with SunShine, as well as setting S-ON you should've taken care that ALL its stock. A simple factory reset in the ROM settings wasn't enough.
I'd guess that the wrong radio led to a problem when booting with stock recovery of your ROM, relocked bootloader and secureflag set to S-ON.
If I saw it correctly all RUUs for your device are *.exe files. Best would be to extract the ROM.zip from this exe, using 7zip, rename it to 2PS6IMG.zip, place it on an external SDCard (formatted extFAT or FAT32) and reboot to download mode, to give it a shot.
Hope this will help.
Edit: ... nvm... @jcase ninja'd me. Wanted to post the exact same link.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Ah gotcha. That makes sense. Wouldn't have been the only thing that slipped my mind. I lost access to my Steam authenticator too. I was able to get the zip from the exe file like you said, after I put that on an SD card and boot to download mode do I just fastboot flash zip?
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
tkoreaper said:
If there's one thing I remember when using Sunshine to go S-OFF on two different HTC 10's it was that it mentioned something about going S-ON and how something wasn't guaranteed, I forget what exactly, but if I remember correctly I understood it as you shouldn't go back to S-ON because it wasn't guaranteed to work or something like that. Anyone know what I'm talking about?
Click to expand...
Click to collapse
That is in regards to wiping data, earlier versions of sunshien wiped data on all htc 10 going s-off, thats not the issue here. Issue here is he improperly set the phone lock/s-on. Gotta use sunshine to set it locked, and fastboot to set s-on.
Hey Everyone just wanted to give an update since yesterday evening.
Just wanted to give out some props to @5m4r7ph0n36uru . Following his advice of extracting the Rom.zip from RUU .exe I was able to run it in download mode and loaded up an OS on the phone. So Now I am unbricked! Yay. I had to find out how to do that using process monitor and everything, but it was a success. and I can breathe easy. Thankfully doing that was easier that doing the Database call handler stuff from today at work XD
Thankfully my lesson is learned and I'll flash correctly to full stock next time. Thank you all for your help in the matter.
bob3rt said:
Hey everyone, so I am pretty sure I bricked my HTC10.
To Start off my specs are the HTC 10 Unlocked version
htc_pmewl
CID: BS_US001/BS_US002
MID: 2PS650000
OS: 1.80.617.1
OpenDSP: 18.2.8996.00524_0321
(orignially Stock ROM)
I was trying to reset everything to stock settings before I returned the phone (Unrooting, Locked Bootloader, Stock Recovery, etc) and everything was going fine until after I rewrote the S-OFF flag to S-ON (I'm pretty sure it happened there, maybe when I relocked the bootloader?). Now I don't have a ROM, the CID and MID's are missing on the fastboot (download-mode) page. The Bootloader is relocked, and I have a stock recovery.
I tried going here to get the RUU's and everything to fix what I had done. However the RUU.exe gives me a error 120 Low Battery when I run it (Even though I have a fully charged battery). I tried going to a different PC to run the RUU, but the RUU never runs past the initial install.
I also tried re-unlock the bootloader so I could reinstall TWRP and flash that way. Unlocking went fine, but when I try to flash the twrp img via fastboot I get an error (9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKED).
I'm really at my wits end here. I haven't actually done anything this stupid in all of my customizing my M8, S6, Razr or all my tablets so I honestly don't know what to do. If you guys could throw me a lifeline I'd be grateful.
Thanks
Click to expand...
Click to collapse
Hello,
Just to inform that if I try to run RUU.exe from PC when the phone is in bootloader menu, I get battery low error. However, if I "boot to download mode" in the bootloader menu, I can run the RUU.exe from the computer without any error.

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?

Categories

Resources