Hello Everyone,
I flashed a rooted stock odexed rom which was this one http://forum.xda-developers.com/showthread.php?t=2752956 for my one m8 and I also flashed the the stock recovery for it. I downloaded the ota update for it and when it tried to update in the recovery, it stoped when it is was about 40 percent and showed the red exclamation mark with the triangle? Help?
What hboot number?
Any error messages?
redpoint73 said:
What hboot number?
Any error messages?
Click to expand...
Click to collapse
My hboot number is 3.16.0.0000.
I get the error "/system/lib/modules/a8293.ko" has unexpected contents.
Launchpad123 said:
I get the error "/system/lib/modules/a8293.ko" has unexpected contents.
Click to expand...
Click to collapse
Something has been altered in the ROM that is preventing the OTA from installing. Its probably easiest for you to relock the bootloader (not required if s-off) and RUU to update, rather than trying to figure out what is altered and returning it to stock in order to OTA.
redpoint73 said:
Something has been altered in the ROM that is preventing the OTA from installing. Its probably easiest for you to relock the bootloader (not required if s-off) and RUU to update, rather than trying to figure out what is altered and returning it to stock in order to OTA.
Click to expand...
Click to collapse
What RUU do I use to update from 4.4.2 to 4.4.4?
Launchpad123 said:
What RUU do I use to update from 4.4.2 to 4.4.4?
Click to expand...
Click to collapse
The AT&T 4.4.4 RUU is linked on my Index thread under "RUUs": http://forum.xda-developers.com/showthread.php?t=2751432
There is also a 5.0.2 RUU, if you want to update to the latest software.
Related
So, using Revolutionary alters your bootloader and so you can no longer receive OTA updates that check that your HBOOT (bootloader) is unmodified. This is pretty much all OTA updates, so you can't recieve OTA at all, save by flashing an uploaded image.
I'd like to receive OTA updates (especially with Honeycomb on the horizon), but I'd also like to root my Flyer. Is this possible? Via installing CWM through HTCDev.com bootloader unlock, maybe? Or does that break OTA updates too?
The HTCDev.com unlock leaves you with S-On, apparently.
porcupineadvocate said:
So, using Revolutionary alters your bootloader and so you can no longer receive OTA updates that check that your HBOOT (bootloader) is unmodified. This is pretty much all OTA updates, so you can't recieve OTA at all, save by flashing an uploaded image.
Click to expand...
Click to collapse
Completely incorrect
All that is required is that you reflash the stock revcovery once you have installed the su zip file.
globatron said:
Completely incorrect
All that is required is that you reflash the stock revcovery once you have installed the su zip file.
Click to expand...
Click to collapse
Really? Wow, great.
globatron said:
Completely incorrect
All that is required is that you reflash the stock revcovery once you have installed the su zip file.
Click to expand...
Click to collapse
Sorry for the dumb question... but stock recovery?
So flashing again once you have rooted, you will keep root and the updates will be ok?
Insinr8 said:
Sorry for the dumb question... but stock recovery?
So flashing again once you have rooted, you will keep root and the updates will be ok?
Click to expand...
Click to collapse
Stock recovery = the one from an RUU or OTA.
Yes, in theory at least. If you ever did get su disabled by an OTA, reflash cwm, reflash su.zip, reflash stock recovery again.
well i just purchased my view today and im trying to root it. where can i find the files and instructions?
In the development forum, the sticky right at the top of the page.
thanks man
Long time reader, first time poster...
I have my DNA rooted, unlocked, s-on currently on 2.04. I got the 2.04 update by re-locking, running the 1.15 RUU, getting the 2.04 OTA, then re-unlocking.
How can I get the latest 2.06 OTA?
I have tried re-locking and running the 1.15 RUU again, but that fails. Any help would be greatly appreciated!
If you're on a stock Rom go here
http://forum.xda-developers.com/showthread.php?t=2025807
dabomb697 said:
If you're on a stock Rom go here
http://forum.xda-developers.com/showthread.php?t=2025807
Click to expand...
Click to collapse
Thanks! Just so I understand, I flash the "stock" recovery, then allow the OTA to run? After the OTA, can I go back to a custom recovery?
alexB1187 said:
Thanks! Just so I understand, I flash the "stock" recovery, then allow the OTA to run? After the OTA, can I go back to a custom recovery?
Click to expand...
Click to collapse
Yup.
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
Hello members,
Looking for some confirmation please as I am finding conflicting information on the forums.
I am currently running 4.1.2 (1.27.531.8). The phone is rooted and s-on (never saw a reason for s-off if anyone is curious) I am also running the ClockworkMod Recovery v6.0.3.2 and hboot 1.44
My phone currently sees the 1.27.531.11 update available, but fails to update. I'm guessing this is because I have a custom recovery installed.
What do I need to do to get to 4.3 (3.24.531.3)?
Do I need to flash stock recovery before I run the official update from HTC? Do I need to upgrade to 1.27.531.11 and then 3.24.531.11?
Most importantly, what happens if I run the official 4.3 update from HTC right now?
Thanks in advance,
Zx
Any insight?
Thanks,
Zx
If I were you I would s-off first, then flash the RUU off HTC's site.
blackangst said:
If I were you I would s-off first, then flash the RUU off HTC's site.
Click to expand...
Click to collapse
What is the benefit of going s-off prior to updating? Do you suppose having a custom recovery is a non issue?
Thanks for the reply.
zx6rrninja said:
What is the benefit of going s-off prior to updating? Do you suppose having a custom recovery is a non issue?
Thanks for the reply.
Click to expand...
Click to collapse
If youre s-off you dont have to worry about flashing stock recovery and hboot.
edit: actually, Im incorrect. You can just run the RUU. Download to desktop, plug phone in while its on, and run RUU. It'll take about 10 mins. You'll then be unrooted stock.
blackangst said:
If youre s-off you dont have to worry about flashing stock recovery and hboot.
edit: actually, Im incorrect. You can just run the RUU. Download to desktop, plug phone in while its on, and run RUU. It'll take about 10 mins. You'll then be unrooted stock.
Click to expand...
Click to collapse
FYI, That failed wonderfully with Error 155 Looks like I may have to lock the boot loader? Mmmm....
Troubleshooting...
After locking the boot loader the RUU successfully upgraded my phone.
zx6rrninja said:
After locking the boot loader the RUU successfully upgraded my phone.
Click to expand...
Click to collapse
Great!
blackangst said:
Great!
Click to expand...
Click to collapse
Indeed! Thanks again blackangst.
Hi everyone,
I have an M8 that has been rooted and has s-off. One of my friends helped me do this. It is at version 4.4.2. When I download the OTA package, it boots to teamwin and when I try to flash the ota package it fails. Is there something that I am missing? Do I need to un-root it and turn s-on? Thanks in advance.
kmac212 said:
Hi everyone,
I have an M8 that has been rooted and has s-off. One of my friends helped me do this. It is at version 4.4.2. When I download the OTA package, it boots to teamwin and when I try to flash the ota package it fails. Is there something that I am missing? Do I need to un-root it and turn s-on? Thanks in advance.
Click to expand...
Click to collapse
You need to revert back to stock recovery. Stock recovery is required to install OTA.
Unrooting is not needed to OTA. Going back S-on is not needed either, and absolutely not recommended.
How would I go about going back to stock recovery? I think I tried this in the past but was never able to get it to work correctly.
kmac212 said:
How would I go about going back to stock recovery? I think I tried this in the past but was never able to get it to work correctly.
Click to expand...
Click to collapse
See is someone has posted it, then flash in fastboot.
You are still on the stock ROM? What software number in Settings>About>Software information?
Alternately, if you don't care about your personal data being wiped and setting up the phone again (there are various ways to backup and restore your data, especially since you are rooted) you can just RUU up to the current OS version.
redpoint73 said:
See is someone has posted it, then flash in fastboot.
You are still on the stock ROM? What software number in Settings>About>Software information?
Alternately, if you don't care about your personal data being wiped and setting up the phone again (there are various ways to backup and restore your data, especially since you are rooted) you can just RUU up to the current OS version.
Click to expand...
Click to collapse
As far as I know it is still the stock Rom. The software number is 1.58.502.1 I would prefer if I did not have to wipe my phone. Thanks for helping, I appreciate it
kmac212 said:
As far as I know it is still the stock Rom. The software number is 1.58.502.1 I would prefer if I did not have to wipe my phone.
Click to expand...
Click to collapse
You can get the stock recovery for that software number here: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
If the ROM isn't stock, the OTA will fail and tell you so. You can get the stock ROM backup from the same thread,
redpoint73 said:
You can get the stock recovery for that software number here: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
If the ROM isn't stock, the OTA will fail and tell you so. You can get the stock ROM backup from the same thread,
Click to expand...
Click to collapse
I used the stock recovery for the same version as my phone, but now when I go into recovery mode, it is a red triangle with an exclaimation mark. Any suggestions for how to get past this? Thanks!
kmac212 said:
I used the stock recovery for the same version as my phone, but now when I go into recovery mode, it is a red triangle with an exclaimation mark. Any suggestions for how to get past this? Thanks!
Click to expand...
Click to collapse
That is what stock recovery is. You can OTA by booting normally and checking for software update in settings.
redpoint73 said:
You can get the stock recovery for that software number here: http://forum.xda-developers.com/att-htc-one-m8/development/att-stock-backups-recoveries-otas-t2855966
If the ROM isn't stock, the OTA will fail and tell you so. You can get the stock ROM backup from the same thread,
Click to expand...
Click to collapse
So I got my recovery back to stock. I download the update fine but when it goes to reboot into recovery, it starts to update and a little into it, I get a red triangle and I have to reboot my phone. When it comes back up, I get the message saying "There was a problem with this software update that prevented installation." Any suggestions?
kmac212 said:
So I got my recovery back to stock. I download the update fine but when it goes to reboot into recovery, it starts to update and a little into it, I get a red triangle and I have to reboot my phone. When it comes back up, I get the message saying "There was a problem with this software update that prevented installation." Any suggestions?
Click to expand...
Click to collapse
Delete the OTA file (believe it should be in Downloads folder) and try to download the update again.
Or just RUU as I mentioned previously.
redpoint73 said:
Delete the OTA file (believe it should be in Downloads folder) and try to download the update again.
Or just RUU as I mentioned previously.
Click to expand...
Click to collapse
Hi Redpoint, I deleted the OTA file and tried again with the same results. How would I go about RUU? And you mentioned before that this will wipe my device, correct? Will it change me being rooted and having s-off? Thank you so much for the assistance, I really appreciate it
kmac212 said:
Hi Redpoint, I deleted the OTA file and tried again with the same results. How would I go about RUU? And you mentioned before that this will wipe my device, correct? Will it change me being rooted and having s-off?
Click to expand...
Click to collapse
RUUs are linked on my Index thread under "RUUs": http://forum.xda-developers.com/showthread.php?t=2751432
Yes, the RUU will wipe the device. So backup anything you want to keep accordingly.
You can RUU all the way up to Lollipop. Just download the RUU to a PC, connect the phone, and run the RUU executable. The rest is self-explanatory by the RUU program, and very easy.
Since you are s-off, no need to relock the bootloader to RUU. Relocking the bootloader is required to run the RUU with s-on. I know that you are s-off (and this doesn't apply to you), but just wanted to add that in case anyone else reads this and tries it (to avoid confusion).
S-off will remain after RUU.
You will lose root. So after RUU, just install custom recovery again, and root by your desire method again. The same would happen if you updated by OTA.