So I'm no stranger to running RUU's on my device as the amount of times I have changed from Sense to GPE is ridiculous. However I have been thinking about getting the M8 so went back to stock sense, locked everything back up and put S-On. When I turn the phone on everything is fine as normal, and it starts receiving ota's, however it wont update past 4.3. Does anyone know if there are any issues with the HTC ota's for HTC__001? It also won't go past with super cid, yet when I unlock and S-Off again I can convert it to H3G__001(not what it should be but I am with the 3 network) it updates absolutely fine to sense 6, 4.4.2.
If anyone knows anything that might shed some light it would be most appreciated.
Thanks.
v28 said:
So I'm no stranger to running RUU's on my device as the amount of times I have changed from Sense to GPE is ridiculous. However I have been thinking about getting the M8 so went back to stock sense, locked everything back up and put S-On. When I turn the phone on everything is fine as normal, and it starts receiving ota's, however it wont update past 4.3. Does anyone know if there are any issues with the HTC ota's for HTC__001? It also won't go past with super cid, yet when I unlock and S-Off again I can convert it to H3G__001(not what it should be but I am with the 3 network) it updates absolutely fine to sense 6, 4.4.2.
If anyone knows anything that might shed some light it would be most appreciated.
Thanks.
Click to expand...
Click to collapse
That is very strange, got to be something to do with the HTC Servers, however, are you trying to update with super cid or with HTC__001 ? I ask as I e noticed that super cid isn't in any of the android info txt files for the 401 updates, I've returned to stock a few times, and never had any problems, but I always start from the 401 kitkat ruu which is 4.19.401.9
Thanks for the reply, I've used both Cid's in the past and both have updated to sense 6 no problem. The only reason I go back to such an early RUU is to S-On as after 1.28 if you try and S-On your phone becomes a paperweight.
Possibly a server thing I guess, but thanks again.
Sent from my Nexus 7 using XDA Free mobile app
Has anyone else in the UK on HTC__001 had this problem recently?
v28 said:
Thanks for the reply, I've used both Cid's in the past and both have updated to sense 6 no problem. The only reason I go back to such an early RUU is to S-On as after 1.28 if you try and S-On your phone becomes a paperweight.
Possibly a server thing I guess, but thanks again.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
no it doesn't become a brick, unless your using a modified firmware and then you should never s-on, what happens is after HBOOT 1.55 I think it is which will be 3.62.401.XX, if you s-on past that then you get the ***TAMPERED*** flag back.
Ahh ok thanks for that, always good to learn something new.
Related
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
+1
Are you s off?? Downgrade your hboot to 1.44 and then flash the ruu for your device....
Sent from my HTC One using xda premium
No unfortunately im s-on... Funny how being a good boy and being s-on HTC rewards me with no option to go back to stock...
Sent from my HTC One using xda app-developers app
LOL............ I am in same postion . want to go back to stock for updates but cant !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
ipmanwck said:
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
2 things:
1) I'll quote what I said, I never said S-Off was available .. "Obviously you'll need S-Off for Hboot 1.54 if/when it happens"
2) What I said above for going to stock is a way of doing it, a Nandroid is not the only way.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
ossman said:
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Nah, the stock firmware for 2.24.401.8 is not available yet, only a customised one which would require S-Off anyway. The method I mentioned is the only way at the moment to get as close to stock as possible without being able to go S-Off and flash an older RUU. When Mike gets hold of the stock firmware to post, I'm sure he will ... I can't see any 2.24 RUU's being available seeing that HTC are pushing for a 4.3 release by the end of September, so I'd wait anyways, unless you need to return your device for warranty purposes of course.
As for you getting OTA updates ... I haven't installed the .8 ROM but it shouldn't affect it as the base you are on is still an older base than what you'd be trying to update to but I'm not 100% on that as I haven't flashed it as my device is away for repair lol. I would imagine that the 2.24.401.8 firmware would be about soon enough and then you would be able to revert to stock with the newest base but obviously as you said yourself, without S-Off you wouldn't be able to wipe any trace of you flashing and modding.
I think HTC only allow you to unlock your bootloader because they can void so many warranties that way and bill for repairs lol ... Maybe I'm being cynical but I do agree that they could provide a stock RUU for people to return to stock, without all the hassle of S-Off or waiting months before any suitable RUU is available but sometimes you have to just suck it up and live with what we have lol
ossman said:
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
Click to expand...
Click to collapse
i got an nandroid backup for you fully stock unrooted : https://mega.co.nz/#!AUZGkKwC!EAfhUXYAgjpAR42jGzG_mhzWJjwcs1j7R_tm_HPMDAo
So today I turned on my phone and I have noticed that there is about an inch in depth line across the screen which isn't picking up touches anymore, so I rung HTC and it's going in for an in warranty repair on Monday. Of course, I need to convert it completely back to stock, but the only problem is I converted it to a Google Edition, changing the CID and, more importantly, the MID. I followed this thread when doing it originally, but I wanted to know if anyone knows if I can flash the same ENG HBOOT onto my GE phone and not have it brick on me? Then I can change my MID and CID back and flash the EU RUU for my phone and send it in on Monday with no issues...hopefully.
Or is there an easier way? Will they check the MID? I changed it to PN0712000 from PN0710000 and CID to GOOGL001 from HTC__001. If I just changed the CID and left the MID, would it matter? Would I still get OTA's on the stock Sense ROM on that MID?
Thanks in advance.
EDIT: So of course I've tried flashing an RUU in the meantime, but I can't. I've tried 2 of those .exe ones but they both fail, I'm assuming because of my changed model ID. I can't find an unencrypted one either that I can change the headers of so I can flash it...ugh. This is becoming a massive pain the bumholey.
RUU's fail because of MID? I thought if you have s-off any RUU would work? I need to know this too cause I might have to RUU and send in for warranty.
I don't know. But I've gone back to complete stock now, great! Of course, there's another problem FFS.
WiFi now doesn't work at all, it just says error. Fabulous. This only happened once it did a system update to the 1.29 update. Now it's asking me to update to 2.24, but I don't have enough data left on my usage to download it to see if it'll fix it, so now I don't know what to do. I've tried Googling this issue, and it appears as though some people might have had it, but I can't find a solution or anything. HALP!
EDIT: I reflashed the RUU and the WiFi is working again. I'm going to try the update again and see if it causes WiFi to not work again, if so then...I don't know what I'll do. Flash OTA's through CWM and see if it fixes it...?
EDIT2: And this time the WiFi works fine. Something must have happened the first time...but all's working fine now. Hooray! Apart from the screen, which is why I'm sending it back to HTC...
May I ask You how did You manage to go back to stock ROM? I'm on stock 4.3 GE Now. I've got S-OFF and bootloader locked. When I go to the fastboot mode and start the RUU (exe file) goes fine, but half way through (when It's moving the ROM to the internal memory) error shows up saying there are some (no specific details) problems that I can fix, but when I do all 4 fixing steps it doesn't help.
I've taken the stock Sense RUU from here
http://www.androidruu.com/index.php?developer=M7
M7/RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I'd love to know how you accomplished this, I've got the same issue going on so I need to revert back to stock using an RUU, but it keeps failing.
can you give us the breakdown of how you did it?
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
From what I've read, having HBOOT 1.54 basically means that you can't S-off your device (as this is only available for 1.44). This means that you won't have access to deeper customisation for your phone (flashing different firmware and changing CID). CID determines what region your phone belongs to so this translates to how early you can get official OTA's as some regions get updates earlier than others. Also, if you want to fully transform your phone into a Google Edition HTC One, this is only open to units with a specific CID.
As for firmware, not really clear on what the differences between firmwares are but you can still flash different radios which are a component of firmwares (thus getting some of the benefits of newer firmware anyway).
That being said, you can flash the whole range of custom ROMs and kernels available on these forums provided that you've unlocked your boot loader. Directions for this can be found on the HTC website.
If you want an optimised stock ROM, try ARHD Sense which is basically your stock ROM with many performance improvements (especially when it comes to signal). For more customisation on Sense, you can try ViperOne.
Honestly there are so many excellent ROMs here that you can easily lose days trying every single one. The Google Edition ROMs are excellent too.
Hope this helps!
Sent from my HTC One using XDA Premium 4 mobile app
Thank you both for detailed replies! This helped me ease my mind on the HBOOT-thing. Thanks!
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Michiel0211 said:
So here's the deal: I bought a HTC ONE back when it was released and I've enjoyed every minute of it, I loved the stock rom - it was smooth and worked like a charm. I have a lot of experience with flashing ROMS, had quite a few HTC phones before this one, but so far haven't tried ANYTHING with the ONE.
I got the update to the latest Android and I noticed there's something about HBOOT 1.44 vs. 1.54 - I checked and I have the 4.2.2 ROM running HBOOT 1.54.
I really want to get into custom roms and start testing a few out; but I have no idea where to start.
Normally I'd pick a guide and work the steps but I'm hesitant now that I've read bits and pieces about this HBOOT thing - I'm not sure what I means, why people are bummed out because they have 1.54 (which I have).
So yeah, I have no idea where to start. Can somebody give me a rundown, some guidelines, what does HBOOT 1.54 mean for me, where do I start?
Thanks,
Michiel.
Click to expand...
Click to collapse
All you have to do is unlock your bootloader via htcdev.com (note, this will wipe your data) and then flash a custom recovery. You can use this tool http://d-h.st/mas to simplify the process.
CoryTallman said:
What no one mentioned is that S-off allows you to remove the ****Tampered**** flag from the boot loader.
With S-off you can lock the boot loader. (With S-on it will show Re-Locked)
With S-off you can flash any RUU to return to stock. Without it you can only flash RUU's that match your CID and are newer than your current firmware.
These may not be important to you, but they're good to know before you jump in.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
sixty_oz said:
Oh sweet I think I found something helpful. I just got my HTC one 6 days ago. I'm s-off so no tampered tag. Do I need to change my cid to flash any ruu? Do I need s-on to flash ruu's? I'm with Rogers in Canada. No RUU for me but there are ota's. Can I flash a different ruu and then the Rogers ota to bring be back to stock? I have s off can I leave it off so if the hboot gets updated by a future ota it will be ok? Thanks for any help.
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
No matter what, you should stay s-off, it does not affect OTA's or RUU's in any way whatsoever. To flash any RUU, you need to be with a cid of 11111111
It's not possible for you to flash an ruu for something else and then flash the rogers ota I don't think
Thanks in advance for any help... I've searched and come up empty in terms of up-to-date stuff. I'm super-cid, unlocked bootloader, s-off (phone came that way off a private sale) with a RUU conversion to GPE. I want to take advantage of the sense 6 update especially the new battery saving mode. Really wondering weather:
1- downgrading firmware is still a thing coming from GPE and going to the latest Sense 6 roms
2- Weather I should use an RUU or try flashing a custom recovery and a wrong
3- Weather there's any other watch-outs I should know
Change your CID/MID accordingly for Dev edition and run the http://www.androidruu.com/getdownlo...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
This will get you going all the way to Sense 6 with a few updates. Do not LOCK boot loader or turn S-ON
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Without further details can't help
komienski said:
Thanks! I tried this and got an ruu fail. My phone was left in a weird version of the recovery/fastboot screen that said ruu but I rebooted and it was fine. Just not sure if I should try again.
Click to expand...
Click to collapse
Based on the google searches I've done, this is normal. The HTC RUU installation never actually finishes. You just need to wait until the progress bar stops moving, make a coffee, then reboot and hope you haven't just bricked the phone.
SaHiLzZ said:
Without further details can't help
Click to expand...
Click to collapse
See above--what happened to him is normal.
Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.
komienski said:
Just to clarify it rebooted back into the previous (gpe) system. Flashing the ruu failed with a message about getting the correct one for my phone, which is odd because I am supercid and s-off.
Click to expand...
Click to collapse
Change cid to BS_US001 and make sure mid is PN0712000
Sent from my HTC One using XDA Free mobile app
I've been seeing a lot of really weird things going on with my phone. I've been flashing lots of updates and various images, but it really surprised me to see it locked/S-ON again. It happened in my bootloader while I was playing with the ramdump, image crc, simlock, and smartsd. Iv e tried to replicate the situation, but It's not happening again. As of now, it's back to unlocked and S-OFF. How is that even possible? Has anyone else seen this happening?
Sleepycloud said:
I've been seeing a lot of really weird things going on with my phone. I've been flashing lots of updates and various images, but it really surprised me to see it locked/S-ON again. It happened in my bootloader while I was playing with the ramdump, image crc, simlock, and smartsd. Iv e tried to replicate the situation, but It's not happening again. As of now, it's back to unlocked and S-OFF. How is that even possible? Has anyone else seen this happening?
Click to expand...
Click to collapse
The bootloader(your Hboot image) is where you make the changes to S-Off etc but I've never seen or heard of a phone reverting to S-On...as far as I know that's impossible. I am S-Off but my bootloader says Locked and S-On but that's because I flashed an Hboot file designed to do exactly that...the phone is actually still unlocked and S-Off but it appears otherwise. Are you sure you didn't do something similar when you were messing around?
slimbrady said:
The bootloader(your Hboot image) is where you make the changes to S-Off etc but I've never seen or heard of a phone reverting to S-On...as far as I know that's impossible. I am S-Off but my bootloader says Locked and S-On but that's because I flashed an Hboot file designed to do exactly that...the phone is actually still unlocked and S-Off but it appears otherwise. Are you sure you didn't do something similar when you were messing around?
Click to expand...
Click to collapse
Man... It sounds crazy, but it's true. I've been flashing for a couple of years now. I've never seen such a thing happen. I didn't flash any modified hboot masks though. I"m unlocked and S-OFF, but I saw it turn to S-OFF while I was jacking arouind in my bootloader. It stayed that way for a couple of days, then it went back to unlocked and S-OFF without any more changes made by myself.
Curious as to what exactly you did to swap back between S-on & S-off. Any chance you could provide the steps you took?
Sent from my HTC device
Magnum_Enforcer said:
Curious as to what exactly you did to swap back between S-on & S-off. Any chance you could provide the steps you took?
Sent from my HTC device
Click to expand...
Click to collapse
Kinda curious about this myself. Seems kind of impossible.
Sent from my 831C using XDA Premium 4 mobile app
Mine reverted to S-ON somehow. I know I was S-OFF because I manually flashed the last firmware update through fastboot, but now it says tampered, unlocked and S-ON.
I'm not getting magically switched back though I used Firewater, so I'll just try that again.