Related
Hey,
I know there's already a thread on this but I wanted to ask which order I need to carry out the process and any help would be greatly appreciated. I need to return my DHD as there are problems with the speaker. I have a new radio, eng-off, s-off and a custom ROM. Which ones do I revert first in order to return to stock without messing up the phone?
Thanks !
You may be able to get away with sending the phone back even if it's not on a stock ROM. I have read other posts on here where people have sent their phones in for repair with custom ROM's and HTC have not been bothered about it, and whenever you send your phone in for any type of repair - they will always wipe the phone and re-install the phone with the latest stock ROM.
From what you have described about the problems you have got with your phone, I imagine the first thing HTC will do before doing any physical repairs on the phone is to re-flash the phone with the latest stock ROM to see if it fixes any of the problems on the phone.
My DHD has been back to HTC twice for the same camera blur problem and I had previously rooted the phone, Radio S-OFF and installed a custom ROM but then I did revert it back to stock with Radio back to S-ON right before I sent it back to HTC for the repair. The first time it went back HTC, all they did was re-flash the phone with the latest stock ROM and sent the phone back to me and hoped that it cured the problem. Within 10 minutes of getting the phone back I knew that the problem was still present and then within a couple of days it was back with HTC again for the same problem and that is when they finally physically repaired the phone.
Edit - from what I have just found out, it doesn't matter which ROM you have installed but the most important thing is to make sure that you revert the phone's Radio back to S-ON before sending it back.
Liam
Thanks, so I just have to get radio S-on back? What about eng-on ? I used the two tools to do it originally, so I'll just have to use them again ?
otibarns said:
Thanks, so I just have to get radio S-on back? What about eng-on ? I used the two tools to do it originally, so I'll just have to use them again ?
Click to expand...
Click to collapse
Yes that's right, just use the tool to revert them back to ON. When I did the process and after I used the tool to revert them back to ON, I just downloaded a stock RUU ROM that you run through Windows and then the program re-flashes your phone back to the stock ROM.
Liam
i would back to stock, just in case... i really don't think htc bothers with it, because it's way more simple to fix the phone than fight against the client.
but, since with the original RUU is very easy to back it to stock, i don't see why you shound't do...
regards!
Ok thanks. I have got radio back to S-ON but I still have eng-off. Will this matter? I can't seem to find out how to revert it back to on.
otibarns said:
Ok thanks. I have got radio back to S-ON but I still have eng-off. Will this matter? I can't seem to find out how to revert it back to on.
Click to expand...
Click to collapse
Did you read the instructions in my tool's thread? It says pretty clearly there that you should run stock RUU
I've been thinking this for a while, since I have an issue with volume rockers (they aren't as outside the chassis as a friend's) from the very first moment I bought.
Does anybody have this issue? or think it's a hardware problem HTC would repair?
Ty
jkoljo said:
Did you read the instructions in my tool's thread? It says pretty clearly there that you should run stock RUU
Click to expand...
Click to collapse
Ok So I just have to flash An RUU and ENG-OFF will dissapear? Thanks
otibarns said:
Ok So I just have to flash An RUU and ENG-OFF will dissapear? Thanks
Click to expand...
Click to collapse
When you install an official RUU you revert to original factory state. I believe bootloader,root,ENG/SOFT-OFF etc... dissapears
otibarns said:
Ok So I just have to flash An RUU and ENG-OFF will dissapear? Thanks
Click to expand...
Click to collapse
almost everything desappear by flashing original RUU, except Radio S-OFF, that can be changed by jkoljo's tool.
but, since you lose the root when you flash RUU, you will root your phone again with visionary, after that, use the jkoljo's tool to get s-on, unroot and uninstall visionary. done, just it.
Juduth said:
I've been thinking this for a while, since I have an issue with volume rockers (they aren't as outside the chassis as a friend's) from the very first moment I bought.
Does anybody have this issue? or think it's a hardware problem HTC would repair?
Ty
Click to expand...
Click to collapse
well, is what you are talking about? http://forum.xda-developers.com/showthread.php?t=915895
thiagodark said:
well, is what you are talking about? http://forum.xda-developers.com/showthread.php?t=915895
Click to expand...
Click to collapse
Not exactly but close. My volume rockers work, it's just they are sunken to bottom and haven't that normal touch i've seen on other DHDs
Anyway, thanks for linking post. I'll talk a bit there
Ever since I upgraded to 1.28.x I have an annoying bug (phone hangs when trying to play any sound without having the headphones on - music, ringtone etc) and phone reboots soon after..
How do I go back to the previous version?
If I were you, I'd factory reset the phone first, because this shouldn't happen
just did, no luck.. it seems the problem lies within the 1.28 update.. I might screwed it up by not having enough battery to finish the process... I was borderline 35% (but plugged in) I think when I went to see my phone after the upgrade it was switched off... I should try (somehow) to re-apply the 1.28 upgrade...
gkatsanos said:
just did, no luck.. it seems the problem lies within the 1.28 update.. I might screwed it up by not having enough battery to finish the process... I was borderline 35% (but plugged in) I think when I went to see my phone after the upgrade it was switched off... I should try (somehow) to re-apply the 1.28 upgrade...
Click to expand...
Click to collapse
Okay, you should download the original RUU from HTC, and install the OTA update afterwards (on a charged batt).
Is there a how-to / manual on how to do that?
"Do not update while the charger is plugged in, this may cause interuptions"
There you go.
Root and flash a custom firmware or any firmware you want.
Better than having a half working phone.
crap, where was that written?
RomNoR said:
"Do not update while the charger is plugged in, this may cause interuptions"
There you go.
Root and flash a custom firmware or any firmware you want.
Better than having a half working phone.
Click to expand...
Click to collapse
You could do that, but if you don't want do take the risk of S-offing/rooting your phone/installing another recovery img, I'd install the RUU.
A RUU is a windows executable file containing the official ROM (no su, just std). You can download it here http://www.filefactory.com/f/7cc7b2fbdd03c031/. Choose the right version for your location (1.26), plugin your phone on USB and run the RUU. It'll revert the OTA changes.
Thanks! Any other way to get links for these RUU? (filefactory is quite busy..) Are these RUU in the official HTC website? (safer)
I don't believe so, HTC hasn't officialy released a RUU (yet) :S
Those RUU's are leaked (though final) versions of the htc one x rom. Agreed it would be safer if HTC released them...
You can't roll back without S-OFF as you can't downgrade the HBOOT
no clue what S-OFF is! are you sure it won't work?
gkatsanos said:
Thanks! Any other way to get links for these RUU? (filefactory is quite busy..) Are these RUU in the official HTC website? (safer)
Click to expand...
Click to collapse
Before you click "OK" to install, same as the 35% battery warning.
EddyOS said:
You can't roll back without S-OFF as you can't downgrade the HBOOT
Click to expand...
Click to collapse
you actually can I just did it, installed 1.26 RUU over 1.28 one..
gkatsanos said:
you actually can I just did it, installed 1.26 RUU over 1.28 one..
Click to expand...
Click to collapse
How did you install 1.26 RUU over 1.28 one?
It gives me error!!!
don't know, just did.. no errors... phone is unlocked (no carrier)
thats where I got the RUU from http://www.xdafileserver.nl/index.php?dir=HTC/One+X/Stock+Rom/Endeavour then I got HTC SYNC from http://www.htc.com/uk/help/?dl_id=1073&news_id=910 et voila...
i'll be trying this right away. i tried rolling back from OTA 1.28 with RUU 1.26 from filefactory (took 6 hours to download!) but it gave me a bootloader version error at the end. although my phone was unlocked, recovery changed, changed back, relocked. maybe that makes a difference.
I tried with no luck
gkatsanos said:
you actually can I just did it, installed 1.26 RUU over 1.28 one..
Click to expand...
Click to collapse
Then you're the first person in history to do it without S-OFF as you can update an HBOOT but can't go back in normal circumstances
maybe his specific ota update to 1.28 didn't include the new bootloader...
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!
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!
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