Before I do anything else to screw this up!
I'm sitting at an exclamation in a triangle
here what I did..
1. installed stock/rooted rom
2. used clean flash to put on stock recovery
3. ran OTA Keeper to back up root
4. downloaded and started OTA update
it then rebooted and began but then Red Exclamation In A Triangle
anyone know where I should go or what I should do from here?
Thanks.
If your pc detects the phone- you'll prob have to do an ruu.exe to get it totally stock and then start over.. I did it earlier but I was having a diff problem (stuck in hboot)-- never got triangle/exclamation. I used the ruu from scottsroms (1.02.605.6).
yeah ok... I'll look into that. I haven't turned it back on yet.. Thanks
Just realized i forgot to "un-root" with the OTAKeeper app... I'm hoping that's what I did wrong. It booted back to where i was and said the update failed. So... I'm a tryin' again.
Thanks for the reply.. One can feel soooo alone when making mistakes
There's some other information in the OTA threads in "general" of others that have had the red triangle and were able to work around it.. I didn't read the specifics but check in there.
das0527 said:
7. Enjoy OTAed, unlocked, rooted kickassness of my Rezound while bouncing off the walls waiting for ICS.
Click to expand...
Click to collapse
Why wait?
I'm going to run through those steps later and check out the other threads. I'm able to get back to my phone as the update looks to of just been aborted....
If you guys don't have wives, keep it that way, I want to work on this all day but...... so I'll check in later and post how it goes. I don't see why those steps won't work though... Thanks a ton guys.
I planned on waiting until the official build of ICS & Sense is released OTA, especially after today's news about the new features in Sense 4.0, which I'm actually extremely impressed with.
Cool- well I'm sure you've already read elsewhere- but you can't really go wrong w/ any of the custom ics roms in the dev section. If you can handle a very occasional screen flicker every once in a while they're pretty much perfect.
reggie cheeks said:
Before I do anything else to screw this up!
I'm sitting at an exclamation in a triangle
here what I did..
1. installed stock/rooted rom
2. used clean flash to put on stock recovery
3. ran OTA Keeper to back up root
4. downloaded and started OTA update
it then rebooted and began but then Red Exclamation In A Triangle
anyone know where I should go or what I should do from here?
Thanks.
Click to expand...
Click to collapse
Did you lock the bootloader?
Sent from my ADR6425LVW using xda premium
No. I didn't. That was my mistake. Dumb of me. I'm gonna do the ruu and start over later, I'm out n about.
Sent from my ADR6425LVW using Tapatalk
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
esheesle said:
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
Click to expand...
Click to collapse
Had Ineffabilis from 12/29, was great, put Clean ICS on it from 1/24, worked well except for the bluetooth pain in the patookie. (and I use bluetooth ALOT)...
I flashed back to GB, I have Team Bamf on mine right now because it included the kernel. I am getting ready to put clean rom on it with the new main ver but I would like to put the new radio's on it first.
Can I put the new radio's on it without going through the steps above (flash stock, re lock, ruu, ota update, unlock, flash, etc) and if so how?
Thanks!
Figured it out. Gonna make a post.
esheesle said:
Why lock the bootloader? There are a bunch of us who were able to successfully OTA without doing so. My radios are all updated as well as the OS. If you debloated, you need to reenable the bloat prior. No need to unroot either.
Click to expand...
Click to collapse
Right now I'm on Vigor Stock Rooted WWE 1.02.605.6 Deodexed . That's my mistake, right? I've got all the bloat.
Sent from my ADR6425LVW using Tapatalk
It's possible the deodexed part of it is the problem.
Do you have a nandroid made from right after you flashed Amon Ra recovery? Also, did you flash a stock recovery or do you still have Amon Ra? It won't work unless you have stock recovery.
If you don't have a nand, you can either run RUU (if you don't have the updated mainver issue) or have a look in this thread:
http://forum.xda-developers.com/showthread.php?t=1467329
con247 has made a stock ROM with the OTA in it so you don't have to download the update.
There aren't any instructions on what to do with the file you download and I didn't use his method so I can't really help but hopefully you'll get it. I don't remember it being spelled out in the thread anywhere which is why I decided it was just as easy for me to use my nand and flash a stock kernel and recovery and download it myself.
I had stock recovery and kernel at the time I ran the update. I've since went back to amon and I've downloaded vigor ota stock rooted and I was about to try that.
Oh and...I'm pretty sure my earliest back up was not my original, I think I made the mistake of flashing a Rom before my first backup
I do however really wish I had some instructions for the vigorotastockrooted.
& one last thing.. Ive never had mainver update.
Sent from my ADR6425LVW using Tapatalk
Yeah, I wish there were instructions for that stock + OTA too.
The OTA will update your mainver but to the official release that is in the OTA. Just so you know, I can now not flash the dbs kernel I was using before because I'm getting a "mainver is older" message.
I was trying to reflash kernels because my wifi is not working now, when I select "turn on wifi" that changes to "error". I had restored my nand of the Innedfabilis ROM I made right before reverting to stock and updating with the OTA. Just mentioning it since I'm posting here to try to help you and I guess it's just full disclosure.
Hmm. I'm thinking of sticking pre-ota as well, at least until I feel more confident about it. Thanks
Edit.... I ended up using con's vigorOta and xtreme tools (for simpler lock/relock) to update . Thanks for the help/insight!
Sent from my ADR6425LVW using Tapatalk
Related
Just updated the ruu found in the bamf remix 1.5 post and lost my root? Or seemed to.
First post because most the time I can find the answers through posts but this I can't seem to find.
I was previously rooted, flashed the new ruu via hboot and everything went smooth. Reboot, reinstall superuser and clockwork via marketplace, and superuser wouldn't take an auto update when it prompted me there was a new version out. Clockwork says I need root before it can do anything.
Few notes to consider :
- s-off is still there (least it says so in hboot)
- my first root I did was the longer way with Android sdk command line, no one click, no 400mb file
- dumb me is dumb, got excited about the new ruu and no nandroid backup
Now I'm chilling here, tried reboots, flash in hboot, and all I can do is sit here staring at my stick Rom like.... Herpa derp want root and bamf back
Help??? Please? Would rather not have to re root. As I won't have access to my computer for days.
-
Did you update to bamf 1.5, or someone posted the stock untouched ruu and you decided to flash that?
Download titanium back up and root, hit "problems?"
and install busybox.
Sometimes when I flash roms it will say i dont have root access, and go through titanium, hit problems, and keep installign busybox (ive had to do it up to 3 times)
and then it works for me
I used the ruu file that was posted in the bamf remix 1.5 thread in the first post right above the zip file for the actual Rom
And I didn't make it to installing bamf. Just finished with the ruu flash via hboot and was on my way to flash bamf when clockwork told me I didn't have root. This is when I went forum hunting about two hours ago :/
Samsuck said:
Download titanium back up and root, hit "problems?"
and install busybox.
Sometimes when I flash roms it will say i dont have root access, and go through titanium, hit problems, and keep installign busybox (ive had to do it up to 3 times)
and then it works for me
Click to expand...
Click to collapse
Wish I could say it worked for me... *sigh* guess I just really lost root then :/
So you didn't do any RUU, you flashed the radio. I flashed that radio before i flashed BAMF 1.5 and everything is working fine over here. Did you check MD5 sum to make sure that it downloaded correctly?
g00s3y said:
So you didn't do any RUU, you flashed the radio. I flashed that radio before i flashed BAMF 1.5 and everything is working fine over here. Did you check MD5 sum to make sure that it downloaded correctly?
Click to expand...
Click to collapse
Yeah. Little goofy on the terminology, fairly new to Android least. But yeah I always check any Rom or kernel or anything like that
I'm not sure, I don't understand how you can lose root just by flashing the radio, never heard of it happening before, sorry.
g00s3y said:
I'm not sure, I don't understand how you can lose root just by flashing the radio, never heard of it happening before, sorry.
Click to expand...
Click to collapse
No problem. I assume I did something wrong but I can't put a finger on it.
Ah well. I appreciate the help m8!
I'm gonna go out on the limb here and say that when you first rooted you never removed the zip file from you sd card and hboot pulled that image instead of the radio update.
afewgrams said:
I'm gonna go out on the limb here and say that when you first rooted you never removed the zip file from you sd card and hboot pulled that image instead of the radio update.
Click to expand...
Click to collapse
Possibly.... If I delete that. Download the new radio, and flash via hboot any ideas what would happen?
Edit... Yup that's what I did. I know... Im a genius swear I had moved that file and over written. Took a lot longer to flash that old file lol. Thanks!
Now just live with the stock sense UI and no root till I can redo that, /cringe
No Pants Hero said:
Possibly.... If I delete that. Download the new radio, and flash via hboot any ideas what would happen?
Edit... Yup that's what I did. I know... Im a genius swear I had moved that file and over written. Took a lot longer to flash that old file lol. Thanks!
Now just live with the stock sense UI and no root till I can redo that, /cringe
Click to expand...
Click to collapse
It's an honest mistake. I had the file on my sd for awhile before I found out. Glad I could help.
I did the same thing but I am stuck in Fastboot/HBoot. If I select reboot or power down in the Fastboot menu, I just come back to Fastboot. If I choose bootloader, I can't use the volume keys to select any of the menu options except the first one (Fastboot). After a few seconds it looks like it starts running the update process on PG05IMG but fails and says "Main version is older." Google/forum searches haven't shown me anything and I don't know where to go from here.
Similar problem
Hi, and thanks for bearing with a noob.
I have a HTC desire, rooted using unrevoked 3. I and I have tried a couple different ROMs successfully and was able to use Titanium Backup and ROM manager successfully, but after flashing cyanogen 7, I want to start using Titanium Backup, but it tells me could not aquire root priv., I went to the problems tab and it tells me make sure im rooted. did I lose root? the only choices it gives me from there is 'prefrences' and 'upgrade superuser' when i upgrade su. I did that to no avail.
also going into ROM manager it tells me ; superuser was not found.
anyway, i have been trying to search for the answer to this for a few days and have tried a couple things. my question is basically, did I lose root and need to unroot and reroot? or is there a way to enable superuser?
Thanks for any help
Does the thunderbolt need to be rooted to upload a stock PG05IMG from my SD card? Im trying to load PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_release_174685_signed.zip from my SD card as my handset is stuck at the bootup screen, thus wont reload through an RUU.
The phone was previously rooted by someone else and I did a system clear through the clockwork recovery (Version 3.1.0.2) menu to wipe their info. Afterwards, it only showed the bootscreen. Oops....
Ive tried to load the aforementioned file through the bootloader screen by renaming it PG05IMG.zip, etc, but the phone keeps rejecting it.
killgorian said:
Does the thunderbolt need to be rooted to upload a stock PG05IMG from my SD card? Im trying to load PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_release_174685_signed.zip from my SD card as my handset is stuck at the bootup screen, thus wont reload through an RUU.
The phone was previously rooted by someone else and I did a system clear through the clockwork recovery (Version 3.1.0.2) menu to wipe their info. Afterwards, it only showed the bootscreen. Oops....
Ive tried to load the aforementioned file through the bootloader screen by renaming it PG05IMG.zip, etc, but the phone keeps rejecting it.
Click to expand...
Click to collapse
What exactly are you trying to do? Completely unroot the thing and put S-On? I'd like to be sure before I dole out instructions. And why such an old RUU? Why not the 1.70 RUU. And how was the Tbolt rooted and S-Off'd before?
Honestly, Im just trying to get it to boot again as easily as possible. I dont care if it's rooted, unrooted, anything, I'd just like it to work.
I grabbed the old RUU because I figured I could update from there. It actually makes no difference to me at this point what's on it, I just want it to work again. lol
killgorian said:
Honestly, Im just trying to get it to boot again as easily as possible. I dont care if it's rooted, unrooted, anything, I'd just like it to work.
I grabbed the old RUU because I figured I could update from there. It actually makes no difference to me at this point what's on it, I just want it to work again. lol
Click to expand...
Click to collapse
I hope wiser minds than mine chime in, but I don't think flashing an old RUU would be wise if Revolution was used. Revolution replaces the hboot and I don't think flashing a new RUU replaces it. I'm not sure what bad would come of it, actually.
It sounds to me like you just need to flash a new ROM. I don't know what radios you have, but you probably have newer ones since those are the radios of choice for newer ROMs. I'd try that first. If that doesn't do it, then I think what needs to happen next it to figure out what hboot you have. If it was done via the jcase method, then flashing an RUU should work fine. If not, well... I'm not an expert on that front, but there are threads on that subject. I wish I could dish out a real simple answer, but I'm not sure it so simple.
Definitely sounds like all that is needed in the OP's case is to flash a new ROM (custom or stock) from recovery as loonatik suggested or possibly restore a backup if one exists. Just sounds like /system was formatted and nothing flashed afterwards.
Absolute_Zero said:
Definitely sounds like all that is needed in the OP's case is to flash a new ROM (custom or stock) from recovery as loonatik suggested or possibly restore a backup if one exists. Just sounds like /system was formatted and nothing flashed afterwards.
Click to expand...
Click to collapse
Thanks for confirming. If you can hold volume-down while powering it up and get into ClockworkMod, flashing another ROM is just a matter of a few button pushes.
Exactly what I thought. I've loaded custom roms on the a855 and Eris before, but the above file won't load. I'm wondering if the bl is locked but it has clockwork, so I'm confused...
That's an entire RUU. That's why. Go get just a ROM and flash through clockwork.
Hey just wanted to say that worked and thank you very much. I am a bit curious however as to why the full RUU didnt work...
killgorian said:
Hey just wanted to say that worked and thank you very much. I am a bit curious however as to why the full RUU didnt work...
Click to expand...
Click to collapse
A full RUU contains a LOT more than just a ROM. It must also be flashed differently; through the bootloader and not recovery. An RUU contains a new bootloader and radios, as well as a ROM. If you'd flashed that RUU correctly through the bootloader, you probably would have lost S-Off and root, or ended up with a device that did even less desirable things... like bootloop.
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Edit: Nevermind, it seems to be good to go. Thanks again for the help.
killgorian said:
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Click to expand...
Click to collapse
in the rom thread most devs put what radios are compatible and a link to the radio. Not sure how new plainjane is, but most of the newer radios work with all the custom roms.
killgorian said:
Thats what I actually tried to do. I renamed and tried to upload through bootloader but it failed. I've flashed RUU's before but never had the issue which worries me a bit. Could be my "bad luck" saved my butt from a more serious issue.
However I loaded the PlainJane rom and it appears I killed my radio now so my journey through aggravation has not yet ended. lol. Im going over your very helpful Q&A post now and seeing if I have a compatible radio for the ROM.
Click to expand...
Click to collapse
If you used Revolution or updated to the patched bootloader, it's designed to not allow flashing over. That's probably why it failed.
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Are you s-on then?
Did you RUU first? Might want to do that since you had made changes before. That will bring you back to nice and fresh stock.
The latest one is here:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
IF YOU ARE S-ON... you can relock, RUU and then flash the recovery again and get root and see if that helps.
If you are s-off then await someone else's answer, but I think you run the RUU without relocking.
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
disdard said:
Ya, s-on. That looks like what I need to do, just wasn't sure what to call the process and search for... Unfortunately with my 4g internet via my phone gone, I gotta sit here and wait on the download to complete on my slower internet. Greatly appreciate the fast response!!!!
Click to expand...
Click to collapse
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
GetRipped said:
The answer isn't always RUU. Running an RUU will reverse everything that you just did. You will lose root. You're phone will be wiped. And you'll have to relock. What I recommend trying first is rebooting into recovery. Twrp in this case for you. You can do this by getting into bootloader (power and volume down on boot up) and hitting recovery. Once in recovery try wiping cache and dalvik. Reboot. If that fixes it... Cool. If not.. reboot into recovery again and wipe data. This time it should almost certainly work. You won't have root. But you will be stock.
Flashing a custom ROM will fix your problem as well.
There is almost nothing that you can screw up to the point of HAVING to RUU. Most people only use an RUU to update firmware and radios when new versions are released
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
feralicious said:
Well it's not like one should avoid RUU like the plague, geez.
As to wiping your phone, flashing a custom ROM can/will do that as well. Relocking and unlocking again are really no big deal, just a couple commands. Rerooting is simple. It's really not as bad as you make it out to be, imo. And in fact, there's a ton of threads suggesting running an RUU to solve issues and get a fresh start.
I like to run an RUU since it brings you back to a nice fresh stock install, and yes, it will update if the phone is not up to date. In this case to global, which is a bonus.
Click to expand...
Click to collapse
Oh hai there.:angel:
disdard said:
I used Hansoons all in 1 toolkit to root my rezound, I unlocked the bootloader, loaded the twrp recovery and flashed supersu. Now when my phone boots all I get is the bar across the top with the signal strength, battery level, and time. What can I do to get my phone to function again??
I had previously unlocked with the toolkit and ran a few root apps and removed some blotware. I then relocked and everything was working fine until I tried to root it again.
Click to expand...
Click to collapse
It sounds like you just need a new launcher. If you're getting to that point are you able to pull it down and see the notification area?
If yes then you could use Droid Explorer to push another launcher to the phone.
If not, yeah you maybe looking at starting over. Have you tried using a different recovery? I know personally I've had issues with every launcher except for Amon Ra.
I ran RUU, and once reset to stock breezed through the process of rerooting. Unfortunately had that done before any of the other replies, because it would have been easier to just do the resetting. But I got into the mess while trying to straighten out the issue of my dialer and people app disappearing so just fully going back to stock ensured I got the entire mission accomplished. And at the point it would boot to, you couldn't pull up the notification window so a new launcher wouldn't have fixed it.
Atleast I learned a bunch through the process!!! Just getting into rooting and customization, took the first step and rooted and kinda figured out how things work. Once I figure out a little more and decide which ROM I want to try, I'd like to try a custom ROM. All stuff I'm familiar doing with computers just gotta figure out exactly how it all works on phones....
Glad you are back up and running! Sorry if my method was more involved/time consuming.
I would suggest that before you flash a custom ROM you make a nandroid of your stock set up. Then you can always flash back to that if you don't like the ROM or run into issues and avoid troubleshooting or RUUing just to fix something.
It's a good safety net and a good habit to always have a nandroid to go back to in case of issues. I usually keep one handy of stock and of any ROMs I like, and always make one before flashing a new ROM or even a theme for a ROM.
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
You should get it. But if any system files are changed by root, the OTA will not install. Otherwise, you should be good to go.
BTW, the Dev Edition 4.4.3 ROM is already posted in Development.
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
noobsquared said:
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
Click to expand...
Click to collapse
He probably made a nandroid backup of his stock rom so that he could always go back to stock in cases like this.
You could technically use someone else stock nandroid as well just as long as all the numbers match up. I believe there was a thread here on that.
---------- Post added at 02:13 AM ---------- Previous post was at 02:08 AM ----------
iArtisan said:
Some news sites are saying AT&T will push it mid August.
In preparation, I've already returned to the stock 4.4.2 ROM and have flashed stock recovery. I'm still rooted, however. Will I still get the OTA update when it is released?
Click to expand...
Click to collapse
Make sure you restore all the bloatware as well or it won't update. I found this out with the last update. I would hold off on the update until you know it's safe to proceed without losing root unless you want to confirm it first for us. [emoji16]
noobsquared said:
What ROM were you running and how did you get back to stock? I'm stuck on ARHD 10.1 and can't get back to stock
Click to expand...
Click to collapse
What do you mean when you say you "can't get back to stock". What did you try and what was the result?
You can just flash a stock rooted ROM, a stock nandroid (as previously suggested) or run the 1.58 RUU.
volcalstone said:
He probably made a nandroid backup of his stock rom so that he could always go back to stock in cases like this.
You could technically use someone else stock nandroid as well just as long as all the numbers match up. I believe there was a thread here on that.
Click to expand...
Click to collapse
redpoint73 said:
What do you mean when you say you "can't get back to stock". What did you try and what was the result?
You can just flash a stock rooted ROM, a stock nandroid (as previously suggested) or run the 1.58 RUU.
Click to expand...
Click to collapse
I got this nandroid (1.12.502.18 - TWRP 2.6.3.3 Thanks to Wonders_Never_Cease) from http://forum.xda-developers.com/showthread.php?t=2701376 and tried to restore, it ends abruptly leaving wifi and boot screen broken. Phone still boots in ARHD 10.1 but doesn' work perfectly. I put the folder from rar file under TWRP Backup folder and it picked up fine but won't restore. Maybe because I have TWRP 2.7.1.0?
I just picked up the phone and it is S-ON with bootloader unlocked/tempered. I'm trying to get back to stock till we have RUU to convert it to DE eventually like the M7.
I was not able to download the RUU EXE file since it keeps ending abruptly like others suggested. I also tried the HBOOT no PC required version of RUU but it would end abruptly at parsing. Maybe because I'm S-ON? I checked the MID and CID, they are both AT&T stock.
Try flashing a stock rooted ROM from my Index (under CUSTOM ROMs): http://forum.xda-developers.com/showthread.php?t=2751432
noobsquared said:
I was not able to download the RUU EXE file since it keeps ending abruptly like others suggested.
Click to expand...
Click to collapse
I know lots of folks have been having this problem. One guy was going to post a mirror of the RUU, so you might see if he got around to that.
But honestly, the OTA isn't rolling out yet, so why bother at this point? I would just reflash Viper and get your phone fully working again and worry about the OTA later.
And why bother with the OTA at all, or wait for it to roll out? There are already 4.4.3 custom ROMs available. And there is also an AT&T version specific ROM based on the 4.4.4 Dev Edition RUU: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The AT&T "official" OTA will probably have little if anything different from the DE ROM, aside from all of AT&T's crappy bloatware apps.
redpoint73 said:
Try flashing a stock rooted ROM from my Index (under CUSTOM ROMs): http://forum.xda-developers.com/showthread.php?t=2751432
I know lots of folks have been having this problem. One guy was going to post a mirror of the RUU, so you might see if he got around to that.
But honestly, the OTA isn't rolling out yet, so why bother at this point? I would just reflash Viper and get your phone fully working again and worry about the OTA later.
And why bother with the OTA at all, or wait for it to roll out? There are already 4.4.3 custom ROMs available. And there is also an AT&T version specific ROM based on the 4.4.4 Dev Edition RUU: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
The AT&T "official" OTA will probably have little if anything different from the DE ROM, aside from all of AT&T's crappy bloatware apps.
Click to expand...
Click to collapse
Thanks for the links and everything man but the whole reason I'm trying to go back to completely stock is that I feel there is something wrong with my phone or maybe this is normal for M8. When I flash ARHD 10.1 and click on finish installation, screen gets back to TWRP but then it goes dark for around 2 minutes. I thought it was dead but it finally lit back up and let me restart the phone. Tap on restart and it took a minute. First boot took well over 5 minutes. Been working fine since but I'm not sure why it sometime just sits there with screen off and pimps on it's own. I may try the full AT&T 4.4.3 ROM since it's very close to stock. If I update firmware, can I not go back to stock nandroid? Which I can't anyways but just wondering.
noobsquared said:
When I flash ARHD 10.1 and click on finish installation, screen gets back to TWRP but then it goes dark for around 2 minutes. I thought it was dead but it finally lit back up and let me restart the phone.
Click to expand...
Click to collapse
So after the ROM fully installs (progress bar fills up) and you click "Finish" in AROMA, the screen goes blank for 2 minutes? I haven't seen that. But it might be a ARDH anomaly (I've never flashed it).
noobsquared said:
First boot took well over 5 minutes.
Click to expand...
Click to collapse
Totally normal on the first boot after any ROM flash.
noobsquared said:
Been working fine since but I'm not sure why it sometime just sits there with screen off and pimps on it's own.
Click to expand...
Click to collapse
Ummm, not sure what is being said here "pimp on it's own". I'm guessing a typo or darned auto correct!
noobsquared said:
If I update firmware, can I not go back to stock nandroid? Which I can't anyways but just wondering.
Click to expand...
Click to collapse
I would highly recommend updating firmware if anything is acting buggy on a 2.22 base ROM.
You should be able to restore a nandroid fine with updated firmware. Only thing, is if the nandroid was based on a 1.XX ROM and doesn't play well with the new firmware, you may need to downgrade the firmware.
But honestly, things tend to be always moving forward firmware-wise. It won't be long until all custom ROMs are based on 2.XX, and the 1.XX base wil become obsolete; with most folks being on the newer firmware and few (if any) reasons to go back or be on old firmware.
redpoint73 said:
So after the ROM fully installs (progress bar fills up) and you click "Finish" in AROMA, the screen goes blank for 2 minutes? I haven't seen that. But it might be a ARDH anomaly (I've never flashed it).
I would highly recommend updating firmware if anything is acting buggy on a 2.22 base ROM.
You should be able to restore a nandroid fine with updated firmware. Only thing, is if the nandroid was based on a 1.XX ROM and doesn't play well with the new firmware, you may need to downgrade the firmware.
But honestly, things tend to be always moving forward firmware-wise. It won't be long until all custom ROMs are based on 2.XX, and the 1.XX base wil become obsolete; with most folks being on the newer firmware and few (if any) reasons to go back or be on old firmware.
Click to expand...
Click to collapse
Yes, once the rom is installed, it exits out to TWRP, I get a flash of TWRP screen and then it goes dark. I press power button and wait for 2 minutes for it to come back on. I'm tempted to just convert it to Dev Edition but with all the issues people are having with phones these days, I want to make sure I can get it fixed under warranty or something if hardware craps out.
I am not even able to restore the nandroid for AT&T at this point. TWRP starts restoring nandroid and then goes back to TWRP main screen and the ARHD rom becomes very buggy (wifi won't turn on, gets super slow, developer warning on boot screen goes away, etc.)
I will try to update the firmware and try to get on that AT&T Rom bandwagon to see how it goes. Thanks for all your help and input. I wish it wasn't so complicated with M8. M7 was so easy to mess with or maybe I got used to that lol
noobsquared said:
I am not even able to restore the nandroid for AT&T at this point. TWRP starts restoring nandroid and then goes back to TWRP main screen and the ARHD rom becomes very buggy (wifi won't turn on, gets super slow, developer warning on boot screen goes away, etc.)
Click to expand...
Click to collapse
After a aborted TWRP restore, I'm actually surprised to see the formerly installed ROM (I think that is what you are saying) to boot at all. Wipe and reflash ARHD.
Broken WiFi is a known issue with the 2.22 based ROMs + outdated firmware. Not sure about the other issues, but updating the firmware and reflashing ARHD might do the trick.
noobsquared said:
Yes, once the rom is installed, it exits out to TWRP, I get a flash of TWRP screen and then it goes dark. I press power button and wait for 2 minutes for it to come back on.
Click to expand...
Click to collapse
That's odd. Did this only happen once, or can your reproduce this bug? Any mention of this on the ARHD thread?
You might also try to wipe cache and re-install TWRP. Could just be a bad TWRP install.
noobsquared said:
I'm tempted to just convert it to Dev Edition but with all the issues people are having with phones these days, I want to make sure I can get it fixed under warranty or something if hardware craps out.
Click to expand...
Click to collapse
FYI, as long as you are a current account holder, AT&T doesn't give a darn what you change in software, they will still honor the warranty if there is a hardware issue.
redpoint73 said:
After a aborted TWRP restore, I'm actually surprised to see the formerly installed ROM (I think that is what you are saying) to boot at all. Wipe and reflash ARHD.
Broken WiFi is a known issue with the 2.22 based ROMs + outdated firmware. Not sure about the other issues, but updating the firmware and reflashing ARHD might do the trick.
That's odd. Did this only happen once, or can your reproduce this bug? Any mention of this on the ARHD thread?
You might also try to wipe cache and re-install TWRP. Could just be a bad TWRP install.
Click to expand...
Click to collapse
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
noobsquared said:
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
Click to expand...
Click to collapse
Just an FYI- the black screen is a common problem with aroma installers and is well known.. All the other issues? I haven't a clue.
Hello!
I'm using 2.22 WWE version stock rom with 4.4.3, but I have long boots of device with old AT&T firmware.
Is there any way to update firmware?
I'm s-on, and firewater doesn't works.
noobsquared said:
Thanks for the information on hardware warranty. I hope it never comes to that.
I actually installed ARHD twice or 3 times last night since every attempt to go back to AT&T stock failed and I had a half working jacked up device. I went in TWRP, re-installed ARHD and everything was good to go. Every time I installed the ROM, I had to wait a couple minutes to hit reboot after ROM installation since TWRP would take a nap. I'm not too worried about it since everything seems to be working fine but it's still kinda bothersome, you know?
At this point in time, everything is running well on ARHD 10.1 so I guess I will take a chill pill.
Thanks once again for all your help
Click to expand...
Click to collapse
OP here.
The black screen you're getting is due to TWRP timing out. You can turn that off in the settings. This is a non-issue though and nothing to worry about.
The long boot times, however, is a problem. This is happening because you're on the old AT&T firmware. Unfortunately, there's no way to flash the latest firmware without S-OFF. Your only option is to return to stock and wait for the official 4.4.3 OTA. Flash a nandroid backup (I'll send you a link to the one I used later, or just search around for the master list here.) through TWRP and then flash stock recovery through fastboot. Let me know if you need detailed instructions on how to do this.
Thanks guys for all the help and support. I messed with the phone quite a bit and tried quite a few things and all the posts here help me learn a lot too. I was able to go all stock after s-off using that RUU method. I tried a couple other roms and finally back to dev edition stock for now. Was able to convert completely to stock with all the info and so far so good.
Once again, thanks a bunch everyone
Sent from my HTC One_M8 using XDA Free mobile app
iArtisan said:
OP here.
The black screen you're getting is due to TWRP timing out. You can turn that off in the settings. This is a non-issue though and nothing to worry about.
The long boot times, however, is a problem. This is happening because you're on the old AT&T firmware. Unfortunately, there's no way to flash the latest firmware without S-OFF. Your only option is to return to stock and wait for the official 4.4.3 OTA. Flash a nandroid backup (I'll send you a link to the one I used later, or just search around for the master list here.) through TWRP and then flash stock recovery through fastboot. Let me know if you need detailed instructions on how to do this.
Click to expand...
Click to collapse
I bit the bullet and just paid $25 for SunShine so I could get S-OFF and update the firmware
http://forum.xda-developers.com/showthread.php?t=2792487
cachookaman said:
I bit the bullet and just paid $25 for SunShine so I could get S-OFF and update the firmware
http://forum.xda-developers.com/showthread.php?t=2792487
Click to expand...
Click to collapse
I had to do the same thing but given that what a pain it is without s-off, I'm not complaining. $25 is a small fee to pay for the peace of mind that you ha e almost full control of the device now.
Sent from my HTC One_M8 using XDA Free mobile app
Hey guys,
Yesterday I tried to update my ViperOne from 2.5 to 3.2 and being the dumbass that I am, I didn't read the note saying my wifi wouldn't work unless I have 4.4.4
It installed fine but I wanted to go back so I followed Viper's guide on reverting to another version. After hours of dicking around, my phone got stuck on the white htc screen. I did power + vol up and got to the recovery menu and remembered that I had a backup of my stock firmware. Lesson learned (always make backups)
Anyways, i booted into the back up image and now everything is working.
My question is, is my phone ok? After the white screen I'm kinda scared I might've ****ed something up. If it's working then I don't have to worry about anything, correct?
Thanks for your help!
XtremelyNooby said:
Hey guys,
Yesterday I tried to update my ViperOne from 2.5 to 3.2 and being the dumbass that I am, I didn't read the note saying my wifi wouldn't work unless I have 4.4.4
It installed fine but I wanted to go back so I followed Viper's guide on reverting to another version. After hours of dicking around, my phone got stuck on the white htc screen. I did power + vol up and got to the recovery menu and remembered that I had a backup of my stock firmware. Lesson learned (always make backups)
Anyways, i booted into the back up image and now everything is working.
My question is, is my phone ok? After the white screen I'm kinda scared I might've ****ed something up. If it's working then I don't have to worry about anything, correct?
Thanks for your help!
Click to expand...
Click to collapse
Nice to know you at least had a backup. You didn't mess anything up you just needed to update your firmware for it to work without any above mentioned issues.
Have you read about S-OFF?
Are you S-OFF?
jball said:
Nice to know you at least had a backup. You didn't mess anything up you just needed to update your firmware for it to work without any above mentioned issues.
Have you read about S-OFF?
Are you S-OFF?
Click to expand...
Click to collapse
I've read about S-OFF
I am S-On
XtremelyNooby said:
I've read about S-OFF
I am S-On
Click to expand...
Click to collapse
You need s-off to update firmware. Once you have s-off, then the firmware I would recommend for use on AT&T's network is 3.28.1540, which is posted on the ROM thread here: http://forum.xda-developers.com/att-htc-one-m8/development
Otherwise, your other option is to return to full stock ROM and stock recovery and install the official 4.4.4 OTA once it rolls out from AT&T (rumored mid-December) which will automatically update the firmware. After the OTA, you will then need to re-install custom recovery, to flash a custom ROM.