I got a OTA update today and I "installed" it but I dont see that anything changed Android is still 4.4.3 and software number is still 1.12.502.18. Dont think anything has changed. Also when I do update my phone restarts and goes into the TouchWiz (I think it was) startup screen.
4.4.3 hasn't been released for the carrier version M8s yet. Version 1.12 (and the newest 1.58) is on 4.4.2. TouchWiz is for Samsung products, you probably mean Sense.
If you're rooted it won't have installed - I don't even know if it would have downloaded. But if it did it definitely won't have installed. You need to be completely stock and unrooted for the OTA to take, including setting the tampered flag back to untampered, and relocking the bootloader. S-Off, if you did that, is ok to keep.
mewikime said:
4.4.3 hasn't been released for the carrier version M8s yet. Version 1.12 (and the newest 1.58) is on 4.4.2. TouchWiz is for Samsung products, you probably mean Sense.
If you're rooted it won't have installed - I don't even know if it would have downloaded. But if it did it definitely won't have installed. You need to be completely stock and unrooted for the OTA to take, including setting the tampered flag back to untampered, and relocking the bootloader. S-Off, if you did that, is ok to keep.
Click to expand...
Click to collapse
Thanks for the reply man, idk what screen it took me to after it rebooted, it had Install, Backup, Boot, Restart, and a couple other options in it. And yeah thats my fault I meant 4.4.2
But wow what a pain in the ass to update the phone. I'll just wait till 4.4.3 gets released to update.
CavyS said:
Thanks for the reply man, idk what screen it took me to after it rebooted, it had Install, Backup, Boot, Restart, and a couple other options in it. And yeah thats my fault I meant 4.4.2
But wow what a pain in the ass to update the phone. I'll just wait till 4.4.3 gets released to update.
Click to expand...
Click to collapse
You could always flash the stock 1.58 rom. http://forum.xda-developers.com/showthread.php?t=2752956
Don't forget to hit the thanks button
gracefullido said:
Thanks
Click to expand...
Click to collapse
im on kangakat 4.4.2 and the phone is telling me i have an update available. is there anyway to disable the pesky "install update now" warning?
sheek360 said:
im on kangakat 4.4.2 and the phone is telling me i have an update available. is there anyway to disable the pesky "install update now" warning?
Click to expand...
Click to collapse
Titanium backup
Hi, just got my new m8 and I rooted s_off and unlocked, the picture I uploaded shows my current state... I did not know what I should do next.. such as my version of hboot and radio or firmware.. idk if I should have taken the ota, b4 s_off & unlocking.. I didn't want to take a chance with an ota.. anyway.. as you see in the pic .. this is my status.. I'm stock with twrp 2.7.0.2
And I didn't know if I could just flash skyfall rom being my hboot is different,
What should do.. can I flash roms that say 1.58.502 over what you see in the picture?
View attachment 2784641
derekdauzat said:
What should do.. can I flash roms that say 1.58.502 over what you see in the picture?
View attachment 2784641
Click to expand...
Click to collapse
I would say yes. There is not a lot changed in either the hboot or the ROM, that would impact what ROMs you can or can't flash.
I've actually seen its more frequently the case that staying on an older hboot is better, for the purpose of flashing ROMs. For instance on I've seen (my old device) where some AOSP ROMs could not be flashed on newer hboots, due to the fact that the new hboot number has not been included on the version check when the ROM is flashed. Users had to downgrade their hboot in order the flash those ROMs, until the ROMs were updated to include the new hboot number in version check.
If you want to install the new firmware package without the OTA, its been posted in the thread in General about the update; and possibly elsewhere.
EDIT: I see you asked for the firmware package here, and it was linked by another user.
Related
So Sprint finally said there was a system update to ICS so I downloaded it and installed and it instantly popped up an error, didn't have any words it was just a picture of the guy with the warning sign. So I waited and it never did anything. I figured I would clear everything/factory reset and see if that fixed it. Nope. Even moreso, it wouldn't let me install any other ROM either. I did enough superwipes and stuff that I finally got the stock ROM to work so I'm back where I started.. One clue might be that I cannot seem to clear the sd-ext, it gives me an error there.
With it back in working order, if I don't clear anything and just try and install ICS from bootloader, what I show in the pic is what happens.
The last part about the E:error in sd card is what I was getting when all the other ROM's were screwing up.
Maybe bad sdcard
Sent from my PG86100 using Tapatalk 2
I don't see how when it works fine now. It's like something is messing with it but I have no clue what.
Re-lock your device and apply the update again.
Just do a fastboot command "fastboot oem lock".
Ugh, you cannot take an OTA if you are rooted with a custom recovery.
sitlet said:
Ugh, you cannot take an OTA if you are rooted with a custom recovery.
Click to expand...
Click to collapse
I had Revolutionary with CWM installed on mine w/ Gingerbread. Installed via EXE method and everything works.....
js593 said:
I had Revolutionary with CWM installed on mine w/ Gingerbread. Installed via EXE method and everything works.....
Click to expand...
Click to collapse
Right, that is not an OTA.
Sent from my PG86100 using xda app-developers app
wow! are you F***ing serious? OH I'M ROOTING AND I'M GOING TO TAKE AN OTA? SERIOUSLY!? lmao! Other than that, I'm not going to say anything more. lol. I WISH I WAS ROOTED AND HAD 1.4 INSTALLED WHEN I GOT MY PHONE! but no! it came with 1.5 and it took a year to figure out how to downgrade. lol. oh well. now they've figured everything out. can s-off with being on 1.5. love everyone on here. Anyway, DO NOT TAKE AN OTA!
I am not the greatest with these things. You are saying I need to unroot my phone for this to work? And I need to somehow get rid of the revolutionary recovery thing? I don't know what OTA means but I can see it's part of the file name. Is there a non-OTA version of it that I can use? For some reason a lot of ROM's don't work. I have hboot 1.5 with s-on and cynogenmod and a lot of ICS ROM's just hang on the HTC screen.
You are saying I need to unroot my phone for this to work? And I need to somehow get rid of the revolutionary recovery thing?
Click to expand...
Click to collapse
You don't need to unroot, but you need to lock your bootloader and get the stock recovery back to take the OTA. The easiest way to upgrade to ICS without doing all that is to flash the new firmware, then flash a stock rooted rom if you want to stay on the stock rom.
I don't know what OTA means but I can see it's part of the file name.
Click to expand...
Click to collapse
Over The Air, i.e. the update that Sprint sends out.
Is there a non-OTA version of it that I can use?
Click to expand...
Click to collapse
Upgrade firmware through bootloader, then flash a stock rooted rom or a custom rom based on ICS. If you want to use the new kernel, you will have to upgrade hboot as well, or you can keep your current hboot and use the VM leak kernel.
For some reason a lot of ROM's don't work.
Click to expand...
Click to collapse
Could be a number of reasons, you need the new firmware to run an ICS rom, and you need the new hboot if those roms use the new kernel.
I have hboot 1.5 with s-on and cynogenmod and a lot of ICS ROM's just hang on the HTC screen.
Click to expand...
Click to collapse
You can't flash kernels with s-on, so you will need to get s-off before you want to use an ICS rom.
I am trying to update the HTC software on my phone. I take to understand the flash will include a radio baseband upgrade which will improve LTE signal lock.
That will be nice, since Sprint has rolled out LTE service here in Baltimore.
Code:
Software version
1.13.651.1 710RD
PRI Version
2.28_003
PRL Version
25006
Android version
4.0.3
HTC Sense version
4.0
Baseband version:
1.02.12.0427
Build number
1.13.651.1_R2 CL60201 release-keys
Firmware update: "No firmware update available"
Rooted: YES
Bootloader unlocked: NO
Many bloatware apps Disabled (Google, HTC, Sprint)
*** TAMPERED ***
*** LOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
When I hit up System Updates>HTC Software Update, it tells me
A system update is available.
System update 1.22.651.3 (41.7 MB)
I DL'd the package, and tried to install it. When the phone reboots, I get a Red Exclamation Mark. Forcing a reboot, and it hangs with a white HTC screen. Forcing a reboot again, I can get back to my home screen.
Some things have updated, or changed, because I previously disabled the default launcher Rosie.apk in favor of ADWLauncherEX, and now the default is back.
I tried Temp unrooting (via Voodoo) and repeating the process, no difference.
I'm guessing you took the ota without restoring the stock recovery first
om4 said:
I'm guessing you took the ota without restoring the stock recovery first
Click to expand...
Click to collapse
Thanks, but that is definitely not right. Sorry if I wasn't clear in in the OP.
I do not have an unlocked bootloader, so I never modified the stock recovery.
Just checking, phone states tampered, since you are locked you are limited to trying an ruu. It should get you going
Hmmm... actually, I just rebooted into the bootloader, then selected Recovery.
I got a few seconds of green triangle with down arrow, then it went to Red Exclamation Mark.
And then after about 2 min, it restarts on its own.
So maybe this problem isn't strictly about my HTC software upgrade?
Or maybe it started there and now persists? I believe I've booted into recovery successfully in the past...
I tried adb reboot recovery, and it gave the same results.
Hmmmm...
om4 said:
Just checking, since you are locked you are limited to trying an ruu. It should get you going
Click to expand...
Click to collapse
I appreciate the reminder that ruu is an option, but I didn't really learn or understand anything like that.
Since the phone actually functions fine, that seems like a rather drastic step.
Also, it blows away everything I have on the phone, which will be annoying to restore.
I'm having trouble understanding the problem. I was thinking the phone didn't boot android at all. If the phone boots fine then yeah that is a drastic step.
om4 said:
I'm having trouble understanding the problem. I was thinking the phone didn't boot android at all
Click to expand...
Click to collapse
When I tried to do HTC System Update, it rebooted and gave the Red Exclamation recovery, and just hung there.
That's not what is supposed to happen, is it?
It shouldn't hang it should show the phone with a progress meter, I wonder if the update was bad. I'm not too familiar since I don't ever accept ota updates
It looks like from your original post that you removed bloatware. You need to restore these apps to be able to install the OTA update. See this thread on more information and how to accomplish this. Let me know if you have further questions but that is why it is failing with the red exclamation point. If you press volume up and the power button there should be some explanation of what app it is failing on. Anyway, good luck. If it is a lot of bloatware you removed it could be tedious to restore all of them.
OK, I don't know what is going on here, but I guess I don't care. I was going to get to this eventually so I think the answer is going to be this:
Back up everything
S-OFF with LazyPanda (which will clear all data on my phone)
http://forum.xda-developers.com/showthread.php?t=1737123
Flash custom Recovery
TWPR
http://forum.xda-developers.com/showthread.php?t=1675738
or maybe CWM
http://forum.xda-developers.com/showthread.php?t=1675430
Re-root if necessary
http://forum.xda-developers.com/showthread.php?t=1671577
Flash new radio manually
http://forum.xda-developers.com/showthread.php?t=1704612
Wait patiently for CM10
I can always S-ON later if I need to
http://forum.xda-developers.com/showthread.php?p=28133124
credit:
compiled links from these two excellent threads
F.A.Q.s - Massive Question Round Up Thread
http://forum.xda-developers.com/showthread.php?t=1693205
HTC EVO4G LTE Tutorial/Vids ● ROMs ● How 2 Root ● Radios ● More
http://forum.xda-developers.com/showthread.php?t=1645890
I think that's your best option since you have 1.12. There are people that would kill for that hboot. Once you get soff just flash the firmware zip and upgrade everything but recovery, hboot and kernel.
Sent from my EVO using xda premium
ScottHW said:
OK, I don't know what is going on here, but I guess I don't care. I was going to get to this eventually so I think the answer is going to be this:
Back up everything
S-OFF with LazyPanda (which will clear all data on my phone)
http://forum.xda-developers.com/showthread.php?t=1737123
Flash custom Recovery
TWPR
http://forum.xda-developers.com/showthread.php?t=1675738
or maybe CWM
http://forum.xda-developers.com/showthread.php?t=1675430
Re-root if necessary
http://forum.xda-developers.com/showthread.php?t=1671577
Flash new radio manually
http://forum.xda-developers.com/showthread.php?t=1704612
Wait patiently for CM10
I can always S-ON later if I need to
http://forum.xda-developers.com/showthread.php?p=28133124
credit:
compiled links from these two excellent threads
F.A.Q.s - Massive Question Round Up Thread
http://forum.xda-developers.com/showthread.php?t=1693205
HTC EVO4G LTE Tutorial/Vids ● ROMs ● How 2 Root ● Radios ● More
http://forum.xda-developers.com/showthread.php?t=1645890
Click to expand...
Click to collapse
I'm pretty sure you need to be rooted to run lazy panda I think you stated your bootloader was locked?
bigdaddy619 said:
I'm pretty sure you need to be rooted to run lazy panda I think you stated your bootloader was locked?
Click to expand...
Click to collapse
Ummm... I am rooted, but do NOT have an Unlocked Bootloader.
I took to understand that LazyPanda would give me S-OFF, which would allow me to flash a custom recovery (TWRP), and thus manually flash radios, kernels, custom ROMs, etc.
I guess possibly there is a fine distinction between S-OFF and Unlocked Bootloader that I might be missing...
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed (error: i have 3.0.1)
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Flash new radios now my phone is bricked and get teh DLOAD drivers on windows.
I'm gonna take a guess and say you flashed the latest firmware 3.16 without flashing the previous firmware update 3.15.
There is no radio only zip available from the latest OTA update for this very reason.
If this is the case your phone is unrecoverable . back to sprint
Sent from my EVO using xda premium
Shad Stang said:
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Click to expand...
Click to collapse
u must have did something u wasnt suupposed to do cause meanbean would not hurt your phone in anyway bro
I second this, I am having issues as well.
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Cruise was right, i thought i had the radio that came with 3.15 but i really had the radio that came with 1.22 XD.
Need to Update...not sure how!
cruise350 said:
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Click to expand...
Click to collapse
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
KEMODREAMS said:
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
Click to expand...
Click to collapse
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Need to Update...not sure how!
ronniemayo said:
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Ok so I did that and it says I'm s-on. Now what? Do I take the OTA update that says "This will update your ROM (MeanBean) to version MeanBean_3.06"? If so, once it's downloaded what do I do? Restart into bootloader? Also my Titanium backup is saying that it "could not acquire root privileges" What does that mean? Thanks for your help.
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Shad Stang said:
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Click to expand...
Click to collapse
You should read Captain _Throwback's firmware thread
You can root the latest OTA just click the link in my sig
Sent from my PoS MoPho
hello all,
I am trying to bring my phone back to stock, I already relocked with bootloader with fastboot.
and when I ran the ATT RUU (RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe)
it came back with an error saying "ERROR [132]: SIGNATURE ERROR"
p.s. I was running cyangen mod 10.1 when trying all this....how do i fix this?
UPDATE: now when I try to reboot the system it goes straight to the bootloader, it wont even boot into an OS.
are you s-off?
skinsfanbdh said:
are you s-off?
Click to expand...
Click to collapse
no, it was never s-off...i thought ATT phones couldn't be s-off.
cms062407 said:
no, it was never s-off...i thought ATT phones couldn't be s-off.
Click to expand...
Click to collapse
s-off is working for all variants i believe but i know it works for at&t
you might be trying to install the wrong ruu.
Ruu fail
cms062407 said:
hello all,
I am trying to bring my phone back to stock, I already relocked with bootloader with fastboot.
and when I ran the ATT RUU (RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe)
it came back with an error saying "ERROR [132]: SIGNATURE ERROR"
p.s. I was running cyangen mod 10.1 when trying all this....how do i fix this?
UPDATE: now when I try to reboot the system it goes straight to the bootloader, it wont even boot into an OS.
Click to expand...
Click to collapse
If you came from a CM variant you might want to re flash what you had. If you want to flash ruu you need to relock bootloader. It took two times for my One to take the update. FYI you will NOT have root with ruu. BTW most US roms are built on that base. If you just want a newer base the international roms like trick droid ( what i am running ), ARHD and insert coin are on the newest builds with jelly bean 4.2.2. just sayin'
skinsfanbdh said:
s-off is working for all variants i believe but i know it works for at&t
you might be trying to install the wrong ruu.
Click to expand...
Click to collapse
Is there a link to all the ATT RUUs? I did notice it said my current version was different than the "your phone will update to this" version.
cms062407 said:
Is there a link to all the ATT RUUs? I did notice it said my current version was different than the "your phone will update to this" version.
Click to expand...
Click to collapse
there is a tread on the international forum in general that has a list of ruus
Stock
myvwrocks said:
If you came from a CM variant you might want to re flash what you had. If you want to flash ruu you need to relock bootloader. It took two times for my One to take the update. FYI you will NOT have root with ruu. BTW most US roms are built on that base. If you just want a newer base the international roms like trick droid ( what i am running ), ARHD and insert coin are on the newest builds with jelly bean 4.2.2. just sayin'
Click to expand...
Click to collapse
I just reread you want to go back to stock. Same applies. Check international att original andriod development boards. They have stock newer builds there than the cingular build. It took three tries to get it to take on my One.
myvwrocks said:
If you came from a CM variant you might want to re flash what you had. If you want to flash ruu you need to relock bootloader. It took two times for my One to take the update. FYI you will NOT have root with ruu. BTW most US roms are built on that base. If you just want a newer base the international roms like trick droid ( what i am running ), ARHD and insert coin are on the newest builds with jelly bean 4.2.2. just sayin'
Click to expand...
Click to collapse
bootloader has been relocked
is there more than one RUU?
myvwrocks said:
I just reread you want to go back to stock. Same applies. Check international att original andriod development boards. They have stock newer builds there than the cingular build. It took three tries to get it to take on my One.
Click to expand...
Click to collapse
hehe international ATT?
International att
cms062407 said:
hehe international ATT?
Click to expand...
Click to collapse
Yes it sounds funny. But there alot of developers building international built completly stock roms for us at&t users
there might be. without s-off you can only install the ruu that is the exact same firmware version your phone came with i believe and yes sometimes it takes a few times to get it to finish without errors
try downloading the RUU again. There's Only ONE RUU for AT&T. Also if you unlock the bootloader again your phone will boot. With a locked bootloader and S-ON, only a fully stock ROM will boot.
okey dokey...i will try again in a bit (my phone isn't charged to 30%)
skinsfanbdh said:
there might be. without s-off you can only install the ruu that is the exact same firmware version your phone came with i believe and yes sometimes it takes a few times to get it to finish without errors
Click to expand...
Click to collapse
sooo the RUU says my current image version is 1.26.502.10 and the updated image version is 1.26.502.12....I read somewhere these numbers have to be the same? is that true???
cms062407 said:
sooo the RUU says my current image version is 1.26.502.10 and the updated image version is 1.26.502.12....I read somewhere these numbers have to be the same? is that true???
Click to expand...
Click to collapse
i think so but im not sure. easiest way if you cant get that to work after a few tries is to reunlock bootloader as gunny said and boot back to your current rom. achieve s-off and supercid then relock bootloader and flash the ruu you have
gunnyman said:
try downloading the RUU again. There's Only ONE RUU for AT&T. Also if you unlock the bootloader again your phone will boot. With a locked bootloader and S-ON, only a fully stock ROM will boot.
Click to expand...
Click to collapse
hmmmm.....i re-downloaded the RUU and tried to reinstall and got the exact same error...
skinsfanbdh said:
i think so but im not sure. easiest way if you cant get that to work after a few tries is to reunlock bootloader as gunny said and boot back to your current rom. achieve s-off and supercid then relock bootloader and flash the ruu you have
Click to expand...
Click to collapse
No. .12 is the latest stock firmware and the only RUU we saw leaked.
gunnyman said:
No. .12 is the latest stock firmware and the only RUU we saw leaked.
Click to expand...
Click to collapse
hmm, that's what I thought on the .12.....
I just noticed the RUU is getting stuck at the "sending" part to my phone, it seems like it isn't even getting to send the RUU to my phone....any idea about this?
i have heard a lot that people get errors a few times then it just works all the sudden. so try a few more times you dont need to keep redownloading it everytime just try flashing. if that doesnt work do what i said before
These are the steps i took to get the Kit Kat update.
I couldnt get the update OTA like most people and i was completely stock.
So if you are in a similar position these steps may help.
DO AT YOUR OWN RISK!
1. Unlock your bootloader and get root access. I did by following these instructions from this video.
Credits goes to sakitech.
https://www.youtube.com/watch?v=kJYAS2KN17Y&feature=youtu.be
2. Gain S-OFF by following these instructions from this video.
Credits goes to sakitech.
https://www.youtube.com/watch?v=NeFwsqU4YL4
3. After you have completed these steps successfully head over to @clsA thread and download the AT&T 4.4.2 OTAPkg.zip and the
stock Recovery_Cingular_US_3.17.502.3.img. Link to the thread http://forum.xda-developers.com/showthread.php?t=2659374
4. Place the downloaded .zip on the root your phone storage.
5. follow the steps in @clsA post and flash Recovery_Cingular_US_3.17.502.3.img via fastboot.
6. Navigate to recovery from fastboot on your HTC ONE. If you see "Mount SDCard failed" ignore it. goto to phone storage and locate the update.zip and flash it.
Click to expand...
Click to collapse
this worked for me, it should also work for anyone else.
ALL CREDITS goes to the creator of the video - sakitech and Senior Member here on xda clsA
Click to expand...
Click to collapse
r3al_0g said:
These are the steps i took to get the Kit Kat update.
I couldnt get the update OTA like most people and i was completely stock.
So if you are in a similar position these steps may help.
DO AT YOUR OWN RISK!
this worked for me, it should also work for anyone else.
Click to expand...
Click to collapse
So am I the only person who went into settings and Clicked AT&T update and got the 4.4.2 update that way. I have never had a phone in all my life tell me an update was ready. I always had to check manually about once or twice a week out of boredom. Did the same with my ONE last week and sure enough there was an update and it downloaded and installed fine.
Solarenemy68 said:
So am I the only person who went into settings and Clicked AT&T update and got the 4.4.2 update that way. I have never had a phone in all my life tell me an update was ready. I always had to check manually about once or twice a week out of boredom. Did the same with my ONE last week and sure enough there was an update and it downloaded and installed fine.
Click to expand...
Click to collapse
i have been clicking the check for update link at least 10 times a day since the update was released and i didnt get it ota i had to do it manually
If you're stock, you should be able to get the update just by changing the date. I brought my phone back to stock (3.17.502.3) then just kept hitting Software Update. If it didn't update, advance the date and try again. After a few date changes, the update was offered.
chp said:
If you're stock, you should be able to get the update just by changing the date. I brought my phone back to stock (3.17.502.3) then just kept hitting Software Update. If it didn't update, advance the date and try again. After a few date changes, the update was offered.
Click to expand...
Click to collapse
ok thanks for the info.. ill add it to the post if its not a prob
r3al_0g said:
These are the steps i took to get the Kit Kat update.
I couldnt get the update OTA like most people and i was completely stock.
So if you are in a similar position these steps may help.
DO AT YOUR OWN RISK!
this worked for me, it should also work for anyone else.
Click to expand...
Click to collapse
Will it work if you are running a custom recovery like TWRP?
ExcelonGT said:
Will it work if you are running a custom recovery like TWRP?
Click to expand...
Click to collapse
Custom recovery won't work.. U will have to b on stock 4.3 and S-OFF with stock recovery thats mentioned above..
Sent from my LG-D801 using Tapatalk
r3al_0g said:
Custom recovery won't work.. U will have to b on stock 4.3 and S-OFF with stock recovery thats mentioned above..
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Anyone know if there are issues with S-Off and rooting since the update? I am 100% stock, non rooted, never installed a rom. Its been stock since the day I got it. I planned on getting the AT&T update to 4.4.2, rooting, making an update then testing some roms.
I know with other phones the update screwed some things up so I didn't know if rooting/s-off were an issue since the update.
Thanks ll!
Edit:
nevermind...found it: http://forum.xda-developers.com/showthread.php?t=2663122
So what exactly do we need to get OTA?
Stock recovery, android 4.3, locked bootloader?
I have all that, and still not finding an OTA update. Manually looking for the update, and I'm just not getting it.
lettuceman44 said:
So what exactly do we need to get OTA?
Stock recovery, android 4.3, locked bootloader?
I have all that, and still not finding an OTA update. Manually looking for the update, and I'm just not getting it.
Click to expand...
Click to collapse
unlocked bootloader, stock 4.3 and s-off, stock recovery.. download the ota place it on ur phone reboot into recovery and flash it.. that worked for me
r3al_0g said:
unlocked bootloader, stock 4.3 and s-off, stock recovery.. download the ota place it on ur phone reboot into recovery and flash it.. that worked for me
Click to expand...
Click to collapse
Oh, I meant from at&t over the air. I feel like I'm missing something, so trying to find out what the ota requirements are.
I can't flash it yet, I only have a windows 8.1 computer with usb 3.0 ports. Fastboot doesn't work.
lettuceman44 said:
Oh, I meant from at&t over the air. I feel like I'm missing something, so trying to find out what the ota requirements are.
I can't flash it yet, I only have a windows 8.1 computer with usb 3.0 ports. Fastboot doesn't work.
Click to expand...
Click to collapse
@chp recommend advancing your date and try and see if the update comes through. Try it a few times and see if it will work for you also
Sent from my LG-D801 using Tapatalk
Tried that with no luck. Had to do a factory reset because I went to far, and my OTA check was in -300 hours.
You guys are forgetting that to be able to update the OTA, you need to have an ACTIVE at&t sim card inserted to your phone. I think this is the reason for all the confusion around since not everybody lives in the US
Downgrade to 4.3
OK, so I was able to upgrade but now I messed it up trying to patch default.xml. :crying:
I am trying to revert to the 4.3 with RRU but I get error 155.
I am S-Off, HBOOT 1.56.
I tried with bootloader re-locked, unlocked, locked. I tried with stock recovery and with ClockWM recovery both locked and unlocked.
I also tried to re-apply the patch with stock recover but it fails verification...
Any ideas how do I go back or fix this?
Thanks
Adrian
Tutorial
How to Update HTC One AT&T android 4.4.2 and root:
http://forum.xda-developers.com/show...79356166999787
Gabe09196 said:
You guys are forgetting that to be able to update the OTA, you need to have an ACTIVE at&t sim card inserted to your phone. I think this is the reason for all the confusion around since not everybody lives in the US
Click to expand...
Click to collapse
i kinda figured n yea im not from the US so this was the only method that worked for me
agoyeneche said:
OK, so I was able to upgrade but now I messed it up trying to patch default.xml. :crying:
I am trying to revert to the 4.3 with RRU but I get error 155.
I am S-Off, HBOOT 1.56.
I tried with bootloader re-locked, unlocked, locked. I tried with stock recovery and with ClockWM recovery both locked and unlocked.
I also tried to re-apply the patch with stock recover but it fails verification...
Any ideas how do I go back or fix this?
Thanks
Adrian
Click to expand...
Click to collapse
The BEST way to make sure that you can run the RUU, whether it be the ATT version, or the Dev Edition is to make sure you downgrade the HBOOT to 1.44. You will never see than error again. No problems at all. Why on Earth though would you want the ATT version, when you can Dev it, and take the 4.4.2 OTA with no carrier BS?
hack14u said:
The BEST way to make sure that you can run the RUU, whether it be the ATT version, or the Dev Edition is to make sure you downgrade the HBOOT to 1.44. You will never see than error again. No problems at all. Why on Earth though would you want the ATT version, when you can Dev it, and take the 4.4.2 OTA with no carrier BS?
Click to expand...
Click to collapse
Thank you.
Actually that is what I did. After downgrading HBoot I was able to use the RRU.
Unfortunately I use my phone for work with Mobileiron and will flag it to IT if I'm rooted. I have tried a couple of workaround so but did not work very well. Every time I try to monkey with it IT starts getting emails every 30 min saying my device is not compliant and I am rooted.... So my best solution is to unlock boot loader and flash mods there. Which got me into this trouble....
I can't navigate to the recovery after I flashed Recovery_Cingular_US_3.17.502.3.img to install the OTA. I've tried going to recovery mode and then pressing Power + Vol. Up to no avail. Any help?