Related
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
Hello everyone. I recently purchased the Rezound to test it out and see if I liked it. I have made the decision to send it back and keep my upgrade. I restored a nandroid backup that I made of stock rooted. I thought I was golden and would only need to remove the root apps and re-lock the phone. I went to turn the wifi on and received the "error". I've tried the steps at this link (http://forum.xda-developers.com/showpost.php?p=21442702&postcount=3) but I cannot get into recovery to do steps 1 through 3 first. My update to 2.01.605.11 happened immediately once I activated the phone so I am on the newest version.
Is there a way I can get my phone back to 100% stock out of the box? I understand that it will show as "re-locked", but from what I have read that wont be a problem when I return it. I came from the Droid X2 where we could SBF back to stock through RSD.
I should have known better than to begin rooting and modding before I was sure I was going to keep the phone.
Thank you all in advance for your help with this and I hope you all have a blessed day.
Romans8vs1 said:
Hello everyone. I recently purchased the Rezound to test it out and see if I liked it. I have made the decision to send it back and keep my upgrade. I restored a nandroid backup that I made of stock rooted. I thought I was golden and would only need to remove the root apps and re-lock the phone. I went to turn the wifi on and received the "error". I've tried the steps at this link (http://forum.xda-developers.com/showpost.php?p=21442702&postcount=3) but I cannot get into recovery to do steps 1 through 3 first. My update to 2.01.605.11 happened immediately once I activated the phone so I am on the newest version.
Is there a way I can get my phone back to 100% stock out of the box? I understand that it will show as "re-locked", but from what I have read that wont be a problem when I return it. I came from the Droid X2 where we could SBF back to stock through RSD.
I should have known better than to begin rooting and modding before I was sure I was going to keep the phone.
Thank you all in advance for your help with this and I hope you all have a blessed day.
Click to expand...
Click to collapse
The RUU is the closest we have to SBF. Can you do a battery pull and get into HBOOT? If so then you can still run the RUU after you deal with the mainver problem. http://forum.xda-developers.com/showthread.php?t=1467099
Here is the stock rooted rom. If you dont want to mess with the mainver and ruu.
http://forum.xda-developers.com/showthread.php?t=1467329
Thanks guys. I kept fooling with my phone while waiting on your replies. I now have followed steps 1 and 2 in the link I provided above. I formatted my system in recovery as it stated. I am now in recovery but cannot select either of my two nandroid backups. I'm afraid to shut down or reboot. What now?
I'm ready to go back to my X2 where I know what I am doing!
Romans8vs1 said:
Thanks guys. I kept fooling with my phone while waiting on your replies. I now have followed steps 1 and 2 in the link I provided above. I formatted my system in recovery as it stated. I am now in recovery but cannot select either of my two nandroid backups. I'm afraid to shut down or reboot. What now?
I'm ready to go back to my X2 where I know what I am doing!
Click to expand...
Click to collapse
In the Vigor rom collection on the development selection they now have posted the most recent RUU based on the OTA so you can flash that and you will be back to stock. Just have to be relocked and on stock recovery.
Hello, and sorry for filling up the forums here in the Q&A. I really need some help, It is quite urgent. I am losing work, and all this stuff. I am running Amon Ra, and CleanROM 4.1
My phones keeps rebooting, randomly. Even if I remove the back cover, sim card, and SD card. I can't touch the dialer, If I do. BOOM, reboot. I will get 2 minutes to mess around, them reboot. Sometimes 2 seconds. This is very annoying. Should I flash a different Rom? GO back to complete stock? Flash this? Flash that? I need a professional answer here guys :/
Is this the first Rom you flashed? Did the problem present immediately? The more details the more we can narrow down your problem.
I have flashed countless amount of roms, this starting happening when I flashed this: http://forum.xda-developers.com/showthread.php?t=1556183 Ever since, everytime I power up my phone, I get like 30 seconds of usage then bam, reboot. I tried different roms and everything, It could be a problem, I've also tried Rez Rom, Or just ICS. I have tried a battery from my T bolt and got farther, but still got rebooted on. My SD card, both external and internal are wiped, everything, I mean everything I have wiped individually in amon ra recovery. Could it be my SIM Card? It says SIM CARD IS NOT AVAILABLE, After 10 seconds I get a weak signal, then when I go to dialer, it reboots.
Did the SIM card go bad? The rom could be the culprit, but how? I have flashed 3 different roms since. (Senseless clean rom 4.0, Clean Rom 4.1, Rez Rom 3.2) What could have changed? I haven't used my phone in 6 hours or so. Should I go into verizon to get a new SIM? Should I fear that they wont service me due to my unlocked rezound? I have tried everything. My next step is to flash an old rom, to see what happens.
T Greezy said:
I have flashed countless amount of roms, this starting happening when I flashed this: http://forum.xda-developers.com/showthread.php?t=1556183 Ever since, everytime I power up my phone, I get like 30 seconds of usage then bam, reboot. I tried different roms and everything, It could be a problem, I've also tried Rez Rom, Or just ICS. I have tried a battery from my T bolt and got farther, but still got rebooted on. My SD card, both external and internal are wiped, everything, I mean everything I have wiped individually in amon ra recovery. Could it be my SIM Card? It says SIM CARD IS NOT AVAILABLE, After 10 seconds I get a weak signal, then when I go to dialer, it reboots.
Did the SIM card go bad? The rom could be the culprit, but how? I have flashed 3 different roms since. (Senseless clean rom 4.0, Clean Rom 4.1, Rez Rom 3.2) What could have changed? I haven't used my phone in 6 hours or so. Should I go into verizon to get a new SIM? Should I fear that they wont service me due to my unlocked rezound? I have tried everything. My next step is to flash an old rom, to see what happens.
Click to expand...
Click to collapse
Holy hell, it's crazy in here tonight. There are three people with a similar issue running around right now.
You did install the new RUU right before installing this ROM? If not, your solution is right here.
If so, do it again.
If you've done it again already, give some more details as to when it started and what you did right before.
---------- Post added at 08:28 PM ---------- Previous post was at 08:25 PM ----------
a-jive said:
Holy hell, it's crazy in here tonight. There are three people with a similar issue running around right now.
Click to expand...
Click to collapse
Ha, never mind. You just have two threads on the same topic. Bad form, sir! No flaming from me, but that sort of thing gets some folks around here PISSED.
I am very sorry. How do I check the RUU Version? I don't remember flashing one before flashing that ROM. I don't really know, but does the PRL have something to do with this? I think I have accidentally messed with that by NOT being on that new RUU leak before I flashed the rom, so with that being said, the other new roms, I have to be on that new RUU ( 3.11.605.22 ) to have the rom stable, and not rebooting? Correct? Thank you for your guys help!
T Greezy said:
I am very sorry. How do I check the RUU Version? I don't remember flashing one before flashing that ROM. I don't really know, but does the PRL have something to do with this? I think I have accidentally messed with that by NOT being on that new RUU leak before I flashed the rom, so with that being said, the other new roms, I have to be on that new RUU ( 3.11.605.22 ) to have the rom stable, and not rebooting? Correct? Thank you for your guys help!
Click to expand...
Click to collapse
No prob here. Just warning you! Some of the old hands around here get tired of us noobs (I was a green horn not too long ago myself).
Boot into your bootloader, the newest HBOOT should be listed as 2.21.0000 and the date is Mar 11, 2012. If those are off, check out that link I posted. If you don't remember doing it (it's a PITA) you probably didn't do it.
No matter what though, if you can't get the phone to stop rebooting on you, you should RUU back to stock before trying anything.
When you unlock, make sure you flash the newest version of Amon Ra, because 3.14 has some issues with the new firmware.
Go slow and it'll be fine. For the record, in the instruction I sent he mentions that it may hang on the HTC screen for a couple minutes the first reboot.... it hung for almost 20 min when I did it. So don't get impatient!
Good luck.
Not trying to scold anyone here but next time read ALL the threads about it before trying to update to an RUU and 99% of these problems will just go away
werdna87 said:
Not trying to scold anyone here but next time read ALL the threads about it before trying to update to an RUU and 99% of these problems will just go away
Click to expand...
Click to collapse
No doubt, dude. Personally, I study my ass off before I do something that could kill my $500+ pocket computer. But I don't mind helping out those who skip the important parts.... some days anyway!
Running the new RUU is a nerve wracking ordeal, no doubt! You have to be patient and run everything twice. Patience is the name of the game!
OLDsJUNKIE said:
Running the new RUU is a nerve wracking ordeal, no doubt! You have to be patient and run everything twice. Patience is the name of the game!
Click to expand...
Click to collapse
bad logic to go by, some things brick if you run twice, AKA Froyo radio on the Inc
Hey guys! Just updated to the new version of Amon Ra. I am currently waiting for the new RUU to download. In the meantime, can someone give me a link or tut on how to update HBOOT? I'm currently on 2.11.0000 OCT 6, 2011 and cannot seem to find the new version. Thank you so much for putting up with me guys, means a lot! Sorry for the people I offended with my lack of knowledge! Forums are new to me, looks like I got some brushing up to do!
werdna87 said:
bad logic to go by, some things brick if you run twice, AKA Froyo radio on the Inc
Click to expand...
Click to collapse
Umm, if you check, the new leaked firmware usually needs to run twice. Once for the bootloader and once for basically everything else. If you are running things twice and getting bricks, you are doing something wrong.
---------- Post added at 12:14 AM ---------- Previous post was at 12:12 AM ----------
T Greezy said:
Hey guys! Just updated to the new version of Amon Ra. I am currently waiting for the new RUU to download. In the meantime, can someone give me a link or tut on how to update HBOOT? I'm currently on 2.11.0000 OCT 6, 2011 and cannot seem to find the new version. Thank you so much for putting up with me guys, means a lot! Sorry for the people I offended with my lack of knowledge! Forums are new to me, looks like I got some brushing up to do!
Click to expand...
Click to collapse
When you run the RUU, it will update your hboot to 2.21 in the process.
Ok, I'll keep you guys updated! I'll give it a go!
T Greezy said:
Hey guys! Just updated to the new version of Amon Ra. I am currently waiting for the new RUU to download. In the meantime, can someone give me a link or tut on how to update HBOOT? I'm currently on 2.11.0000 OCT 6, 2011 and cannot seem to find the new version. Thank you so much for putting up with me guys, means a lot! Sorry for the people I offended with my lack of knowledge! Forums are new to me, looks like I got some brushing up to do!
Click to expand...
Click to collapse
Just want to make sure you have the process down before.you start...
Once the RUU is downloaded, you will lock the boot loader, put the renamed ruu on your SD, run the RUU from the boot loader (don't try to flash it like a rom). You will then have to unlock and reflash that new among ra.
Then rock out. Just follow that step.by step closely for the RUU. Its kind of a weird process.
a-jive said:
Just want to make sure you have the process down before.you start...
Once the RUU is downloaded, you will lock the boot loader, put the renamed ruu on your SD, run the RUU from the boot loader (don't try to flash it like a rom). You will then have to unlock and reflash that new among ra.
Then rock out. Just follow that step.by step closely for the RUU. Its kind of a weird process.
Click to expand...
Click to collapse
Ok, so go back to HTC Dev.com and just re-lock? Or is there a tool I should use.
Besides that, I got a great feeling this is going to work!
Blah, it seems I have ran into a problem. The file for the new RUU I downloaded was corrupt. Anybody got a download link to the 3.11.605.22? Thanks.
I need a link to the new RUU. All the others are corrupt
T Greezy said:
I need a link to the new RUU. All the others are corrupt
Click to expand...
Click to collapse
Are you still stuck today?
Nope! Got my phone working as new! Updated and everything!
YOU GUYS ROCK, THANK YOU.
I had the exact same problem with my phone two days ago. You have to upgrade to the stock ICS first to update the RUU and junk, then re-flash Amon Ra, then install Cleanrom 4.0 or the dev version.
Howdy. I updated my phone recently to Virus's release of that latest OTA of ICS. I also ran his modified firmware updates, which updated my hboot to 1.58 . Everything ran fine. Wiped the phone and did a restore of my old CM9 backup. Bootlooped. Wiped and installed Virus's OTA again now it has no signal. wiped factory/system/cache/dalvik again, installed ICS OTA and again no signal. Cant even do initial setup, all it wants is wifi. Bars have the X on it.
Bummer. Cant figure it out. Any help is appreciated. I did get that VM firmware awhile back, never had any major problems from it.
Another goofy thing thats happening is sometimes when i try to boot into recovery that PG86M file (or whatever its called) trys to load.
I keep deleting this file and it comes back. Really annoying.
Any help is appreciated, phone is on the ground crying.,.
grandpasghost said:
Howdy. I updated my phone recently to Virus's release of that latest OTA of ICS. I also ran his modified firmware updates, which updated my hboot to 1.58 . Everything ran fine. Wiped the phone and did a restore of my old CM9 backup. Bootlooped. Wiped and installed Virus's OTA again now it has no signal. wiped factory/system/cache/dalvik again, installed ICS OTA and again no signal. Cant even do initial setup, all it wants is wifi. Bars have the X on it.
Bummer. Cant figure it out. Any help is appreciated. I did get that VM firmware awhile back, never had any major problems from it.
Another goofy thing thats happening is sometimes when i try to boot into recovery that PG86M file (or whatever its called) trys to load.
I keep deleting this file and it comes back. Really annoying.
Any help is appreciated, phone is on the ground crying.,.
Click to expand...
Click to collapse
Have you tried updating your PRL/Profile?
That might help. If not, it could be your VM firmware acting up.
Shadow89 said:
Have you tried updating your PRL/Profile?
That might help. If not, it could be your VM firmware acting up.
Click to expand...
Click to collapse
I tried to update PRL and it just checks for update for 5 min; and says connection could not be made. Getting absolutely no signal. VM firmware didn't mess up much for me after initial flash monthes ago. But I certainly suspect something now..
Thanks for the suggestion. Any other ideas why someone night be getting no signal
Phone is crippled. Don't lookforward to giving it to sprint with this VM banner on my phone. Lol. Crap...
grandpasghost said:
I tried to update PRL and it just checks for update for 5 min; and says connection could not be made. Getting absolutely no signal. VM firmware didn't mess up much for me after initial flash monthes ago. But I certainly suspect something now..
Thanks for the suggestion. Any other ideas why someone night be getting no signal
Phone is crippled. Don't lookforward to giving it to sprint with this VM banner on my phone. Lol. Crap...
Click to expand...
Click to collapse
Really not could have done it. Tried new radios, tried booting with the latest firmware again.. no success
im taking suggestion on anything that could help here.
UPDATE
Through Fastboot feature I loaded the 2.08 RUU. STILL NO SIGNAL WTF?
Yesterday i ran 2.17 RUU to take the OTA and i had to Flash my phone again to another carrier on Mexico. MDN, MSID, PRL, and all that info was erased to 0's and i had to use CDMA Workshop to get SPC again(yes, it changed too) and after that to program my phone with QPST again to get signal.
luis4ever said:
Yesterday i ran 2.17 RUU to take the OTA and i had to Flash my phone again to another carrier on Mexico. MDN, MSID, PRL, and all that info was erased to 0's and i had to use CDMA Workshop to get SPC again(yes, it changed too) and after that to program my phone with QPST again to get signal.
Click to expand...
Click to collapse
I think you need check this one... Lol
Send From Sprint-HTC-Evo3D MIUI by Dh
I'm right here with you on this issue. I've tried just about everything to get signal back but its a no go. Happened as soon as I flashed the firmware with hboot included that virus posted. Everything went fine except when it booted back up I had no signal (disconnected because service is unavailable). No roms that i flash will change this. I even ran an old ruu and updated all the way to ics from stock and no dice. Reflashed hboot 1.4 with revolutionary so i could restore my venomrom nandroid, but still the same. Frustrated. Do I need to use qpst or cdma workshop to try to do something? I'm not real familiar with either of those, but feel like I'm out of options now...
mattinky11 said:
I'm right here with you on this issue. I've tried just about everything to get signal back but its a no go. Happened as soon as I flashed the firmware with hboot included that virus posted. Everything went fine except when it booted back up I had no signal (disconnected because service is unavailable). No roms that i flash will change this. I even ran an old ruu and updated all the way to ics from stock and no dice. Reflashed hboot 1.4 with revolutionary so i could restore my venomrom nandroid, but still the same. Frustrated. Do I need to use qpst or cdma workshop to try to do something? I'm not real familiar with either of those, but feel like I'm out of options now...
Click to expand...
Click to collapse
Wow, interesting that your getting it too. Did you ever flash that VM Firmware? This is worse than a brick LOL. im jumping on peoples wifi when i can to even try to use my phone. PM if you find a solution else where. Im about to put a bounty on a fix, if this doesnt get resolved.
I dont even know what CDMA workshop or QPST is, but im willing try anything.
Yes, unfortunately i flashed that firmware but thought id correctly done some method of getting it back to normal. I dont have the banner and im on the 1.53_vin pri. Just seems that mynetwork is all cleared out. Ive tried to reset my espt using ##786# but it fails due to the radio not responding.
Im still looking and will keep u updated.
Sent from my PG86100 using xda premium
Have you tried to force the phone to do a hands free activation?
Save the Drama for your Mama with Tapatalk 2
coal686 said:
Have you tried to force the phone to do a hands free activation?
Save the Drama for your Mama with Tapatalk 2
Click to expand...
Click to collapse
Hey thanks for the suggestion. I tried going through the steps to force hands free activation, but MSL Reader gave me 000000. LOL this phone is fudged up. I welcome any other suggestion, or perhaps MSL Reader showing 000000 means something?
Also ive heard of people flashing new PRL's anyone know where i would find those?
Same here, msl is reset to 000000. It seems that doing a ##786# reset would fix it and return everything the way it was, but it always errors out. No phone all wknd has been frustrating. Guess I need to return to stock and s-on so I can take it in. Of course, when the te h looks and sees my 1.53vin pro I'm pretty sure he'll know I messed things up myself. Gonna play dumb and say this is just was happened after the its to ics. Ugh.
Sent from my PG86100 using xda premium
mattinky11 said:
Same here, msl is reset to 000000. It seems that doing a ##786# reset would fix it and return everything the way it was, but it always errors out. No phone all wknd has been frustrating. Guess I need to return to stock and s-on so I can take it in. Of course, when the te h looks and sees my 1.53vin pro I'm pretty sure he'll know I messed things up myself. Gonna play dumb and say this is just was happened after the its to ics. Ugh.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Fuuudge. Im hoping i dont have to do the same thing. Do they cover that kind of stuff? even if you dont pay for their insurance.
I'll have to get the VM banner off my phone too. lol
coal686 said:
Have you tried to force the phone to do a hands free activation?
Save the Drama for your Mama with Tapatalk 2
Click to expand...
Click to collapse
Yes, when attempting a hands free activation, it errors saying that there is no service.
this happend to me just a few minutes ago!! same thing! i am flashed to cricket. tried reflashing firmware and i cant get signal back at all! i need my phone what can i do?
ZeRo2o9 said:
this happend to me just a few minutes ago!! same thing! i am flashed to cricket. tried reflashing firmware and i cant get signal back at all! i need my phone what can i do?
Click to expand...
Click to collapse
Ugh, bad luck brother. Still no remedy my way though I've talked to virus and unknownforce. I'm still holding my breath that the official ruu will solve this, though lord knows when that will surface. Will update if I make any progress...
man that sucks..thanks for replying man..i hope i can get it fixed..ill keep checking this thread
Y'all should try flashing the 2.17 RUU make sure have a shipped Hboot and turn s-on through adb in that order or you will brick it. This is a last resort because you will lose root until you do junoputbear wire trick or Hboot downgrade but if you don't have a phone to use you have nothing to lose...
Edit: try unknownforce VMware removal tool in sticky..if you flashed the VM Virus...
bpc4209 said:
Y'all should try flashing the 2.17 RUU make sure have a shipped Hboot and turn s-on through adb in that order or you will brick it. This is a last resort because you will lose root until you do junoputbear wire trick or Hboot downgrade but if you don't have a phone to use you have nothing to lose...
Edit: try unknownforce VMware removal tool in sticky..if you flashed the VM Virus...
Click to expand...
Click to collapse
Thanks for the advice. I actually have flashed every RUU known to man I think lol. I went way back and flashed and did all the updates until I was on ICS again, and still no luck. Problem with the VM removal tool is that you need to have your MSL and this issue resets the device MSL to 000000.
---------- Post added at 04:49 PM ---------- Previous post was at 04:45 PM ----------
grandpasghost said:
Hey thanks for the suggestion. I tried going through the steps to force hands free activation, but MSL Reader gave me 000000. LOL this phone is fudged up. I welcome any other suggestion, or perhaps MSL Reader showing 000000 means something?
Also ive heard of people flashing new PRL's anyone know where i would find those?
Click to expand...
Click to collapse
Also, I tried manually updating the PRL through ##775# with the .prl file on my root, but it didn't take. It locates the file and then tries but throws a no radio signal error or something and doesn't change anything.
saw an old thread on google but it was deleted. this has happend before i know we arent the only ones..hopefully someone sees this and sheds some light in this
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