How long does it usually take to get an RUU for our phones?..I thought RUU's were usually out just before phones are released...
Related
I have a T-Mobile HTC One (MID PN0713000) and I have been trying to test if my HSDPA on AWS band would work if I flashed a Dev Edition RUU. (I know there wouldn't be a way back without a T-Mobile RUU if I did lose the band, but that's fine.)
My problem is that the RUU is failing even though I have changed my CID to BS_US001 (Dev Edition CID) because my model ID doesn't match. Developer Edition (and AT&T) MID is PN0712000 versus my PN0713000, so it is not allowing the RUU to run. And even if it did, you can't get OTAs without a matching MID, so it would defeat the purpose of flashing a different RUU anyways.
So my question is, besides some modified HBOOT methods that I've seen, that I'm not in the mood to try due to a high risk of bricking the device, is there any way to change the Model ID of the device?
With Super CID you can flash any RUU but you will have the issue you said regarding the MID come OTA time...
EddyOS said:
With Super CID you can flash any RUU but you will have the issue you said regarding the MID come OTA time...
Click to expand...
Click to collapse
That's why I wanna see if there is a way to change the MID. Only point of flashing a Dev or Euro RUU for me would be to have a stock device but still get OTAs faster. And same would apply to the Google RUU if/when it comes out, which will also probably be a different MID.
Hi all,
I'm planning on going the S-Off, CID chnage route to get OTA updates as my carrier (3 UK) clearly can't get its fingers out.
I've read a few guides already and I think I'm all set, the only hiccup is that I'm on a Mac (no bootcamp, vm ware or other...).
I can do the S-off with Revone and chnage the CID but I don't l know how to flash the RUU from my Mac.
Does anyone know how to flash RUU from a Mac?
Thanks for you help.
try this http://winebottler.kronenberg.org it always worked for little programs, never use for heavy ones.
personally i won't never use a RUU with this software, ill prefer waste 20 minutes installing windows with bootcamp
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
i tried searching and could not find a similar scenario:
originally my htc one was on t-mobile with its proper cid. i am no s-offed, google cid and running the gpe 4.3 ruu with the 1.54 hboot. since i am s-off, can't i run any ruu withouth having to revert to 1.44 hboot? t-mobile came out with their 4.3 OTA and wanted to try that or the developer's edition 4.3 ruu,
i was planning to reboot into bootloader put it in fastboot mode, plug it the computer till it reads fastboot usb then run the RUU.exe, am i missing anything?
Think ill subscribe here. Im in the same boat but on mine im using the SuperCID 11111111.
I too have a TMO unit that i converted to GPE and love it. Now that 4.3 is official on TMO id like to go back to it and see how well it performs..
I kinda forgot half the steps i took to get to GPE so i feel like im starting over again. LOL
I had to flash a previous firmware via fastboot first in order for the T-Mobile 1.27.531.11 RUU to flash my One. I used a firmware zip for 1.27.531.11 since I had that on hand already.
So, I want to go back to stock 100% for repairs and I've followed every guide i could find, i promise this is not without many hours of trying...
I restored the Stock_JB_4.3_BM___001_TWRP_3.23.666.1_htc_one_m7 - which may or may not have been what came stock on the phone...
Firmware right now is 4A.14.3250.13
my CID is correct i believe (BM___001 <-- 3 underscores)
HBOOT is 1.44.
I flashed stock recovery and used revone to un-Tamper, lock, and S-ON. But the minute I boot up the phone to a usable state it says "Tamper Detected!" and reboots and HBOOT shows "Tamper" and "Security Warning". Been at this all day and the only thing i can come up with is that I must have either the wrong firmware or the wrong recovery? or the wrong combination of everything?? haha
Anyone encountered something like this? Tips?
Edit: currently sitting S-Off, Unlocked, Tampered..
I swear, i should just give up more often... Naturally the minute i hit post on this thread, after trying all day, i find the piece of the puzzle..Will update when i'm sure but i think the missing link was a mismatched recovery.
*FacePalm* wrong recovery all along. didnt see that huge thread with all the different recovery's available till now.
Things are working. Sorry to waste your kilobytes!