Related
background, running DI01 rooted with stock 2.1. never upgraded to anything else since my phone worked like i wanted it to. upgraded the wife's phone every time an update came out but still left mine stock, rooted. now i have tried to upgrade to 2.2 several times with no success. keep getting the IP error. have done everything i can think of, unrooted, battery pull, rebooted, you name it, still get errors. what are my options for getting OEM 2.2? should i just go with one of the custom builds or wait till some newer 2.2 roms come out now that the developers have the OEM 2.2? options people, im at whits end with this one. my brain is fried and my search fu is exhausted. FYI i have oden as well as the current drivers for the phone.
Follow this thread to get yourself back to stock.
http://forum.xda-developers.com/showthread.php?t=1053567
Once there you can continue to follow steps to get to latest and greatest rom, or simply stay at stock. Your choice.
Also, just as an fyi, make sure your wifi is turned off when you try to get updates OTA from Verizon.
i am stock, other than being rooted. thats the part i cant figure out. it should update OTA with no problems. all i have doen is root so i can use "other" programs not in the market place.
superchunkwii said:
Follow this thread to get yourself back to stock.
http://forum.xda-developers.com/showthread.php?t=1053567
Once there you can continue to follow steps to get to latest and greatest rom, or simply stay at stock. Your choice.
Also, just as an fyi, make sure your wifi is turned off when you try to get updates OTA from Verizon.
Click to expand...
Click to collapse
+1 I'd do this just to be positive. Something isn't right there. THOUGH, while OTA updating I have gotten that same error, but it wasn't for very long at all, just Verizon's servers being shotty. Odin back, it will wipe everything. OR, I am running the 2.2 Community ROM, and it is amazing, your choice. I doubt you'll be seeing many more 2.2 ROMS coming out.
going to give this a try. to bad it takes so long for this stuff to DL. should have it done by this afternoon.
From what a Verizon tech was telling me it wont work rooted and just to prove he actually knew what he was talking about he told me just how well they can actually track stuff. He told me i activated my fascinate on Feb 8th, that's true, then he told me on Feb 16 I rooted my fascinate and voided the warranty, also true, but HOW THE HELL DID HE KNOW THAT, so if he says it wont work with your phone being rooted, i now believe him. So i went back to bone stock DI01 and started updating. ED01 update took like 3 hours to OTA DL for me.
A couple weeks ago, I decided it was time to root my phone, since I missed running the custom ROMs on my Droid. So I unlocked it and rooted it and everything went all fine and dandy. I decided for my first ROM, I would flash Xtreme Outcast's ICS ROM (v2.0, I think). When I first flashed it, my data worked fine (however downloading apps from the market gave me some issues, but I think that was another problem..). However, before long, like later that day, the 4g and 3g stopped working. After it stopped working, I decided to try to restore my nandroid stock ROM, but when I went back to it, not only did the 4g and 3g not work, the wifi just said 'error' when I tried to turn it on. So after that, I tried to flash the GB OTA RUU, but that gave me some issues, but I've figured out where that went wrong (mainver error).
Anyway, what I'm trying to figure out is what I can do to try to fix the issue. My mobile data IS on, the battery cover IS on, and the SIM card is inserted and, to my knowledge, working just fine. Would flashing an RUU help? Am I just having bad luck with this ROM and need to flash a different one? Should I update to the new RUU? Any help would be fantastic, and I'd award you 456789876435974 awesome points!
Sounds like you may have had a bad ROM zip. I would try re-downloading the ROM and re-flashing making sure you wipe all/factory reset first. If that works and you are feeling adventurous, I highly recommend Scott's ROMs new CleanRom 4.1 which requires an RUU. Check out his web site and developer thread here for more info. I took the leap and love it.
woodyt74 said:
Sounds like you may have had a bad ROM zip. I would try re-downloading the ROM and re-flashing making sure you wipe all/factory reset first. If that works and you are feeling adventurous, I highly recommend Scott's ROMs new CleanRom 4.1 which requires an RUU. Check out his web site and developer thread here for more info. I took the leap and love it.
Click to expand...
Click to collapse
Thanks for the response, but do you think it was just a bad flash if it affected the stock nandroid backup too? I will try flashing a new ROM soon either way, though. Is it possible to download an older version of CleanRom? I can't find a link on the first page of the thread, though I might have just overlooked it. I'm just not sure if I want to update to the new RUU right now, but if there are no other options, I might just pull the trigger on it.
Go to Scott's ROMs web site and you can download ISCE 3.7 which is still on the old firmware so no RUU needed. His roms are pretty slick and he provides great support.
Good point on the nandroid so I'm not sure what's going on. Hopefully the new ROM flash helps.
Well, I flashed the ICS RUU, and now my data works! but now...I can't get my phone to root. Is there a guide for rooting on the new RUU?
CollinswithanS said:
Well, I flashed the ICS RUU, and now my data works! but now...I can't get my phone to root. Is there a guide for rooting on the new RUU?
Click to expand...
Click to collapse
It is just easiest to install and ICS new firmware ROM that is already rooted.
There is however a couple of thread in the development forum on rooting and there is an ICS root tool there
I'm trying to get my note back to original stock GB so I can ota upgrade to ICS.
I did a complete 'backup' of the original rom before I started messing around, and now, no matter what I do, I can't get that backup to reinstall on the phone.
I've done a lot of searching around, and found many threads about getting notes back to AT&T stock, and am very wary about doing that.
I've also found a few threads about getting back to original bell stock firmware etc, but whenever I run the files through odin, I get wierd errors (some with chinese writing), and just get frustrated.
I liked a few of the custom rom's I found, but the crazy thing, is the spen gestures (specifically the double-tap with button down for quick memos) are just too important to be without. I got the phone for work, and thought those where neat 'features'. Well.. seems I can't live without them.
But NOTHING I can find helps. I've tried methods listed on rootgalaxynote.com to unroot and get back to stock, and everything looks fine till I try either ota updating or kies updating. The phone simply isn't recognized in kies, and the ota update says nothing is available. and I know it IS available, cause I did the upgrade just after it was released, before I did all this custom rom stuff.
I'm start to get at my wits end. I simply want my original stock firmware etc. back on the phone, upgraded to ICS, and then I can just forget about everything else.
Is there anyone that can help?
P.S. if you know of any links I may have overlooked, please just post them. Believe me when I say I've spent well over a week just browsing the forums and google, doing searches etc. Its entirely possible it's something obvious that I just didn't see... with my 3 older kids and a newborn, I'm getting almost zero sleep, and am constantly frazzled. I sometimes don't even realize my wife is talking to me (on the worse days).
Anyways, thanks for anyone's help.
Ragnarkov said:
I'm trying to get my note back to original stock GB so I can ota upgrade to ICS.
I did a complete 'backup' of the original rom before I started messing around, and now, no matter what I do, I can't get that backup to reinstall on the phone.
I've done a lot of searching around, and found many threads about getting notes back to AT&T stock, and am very wary about doing that.
I've also found a few threads about getting back to original bell stock firmware etc, but whenever I run the files through odin, I get wierd errors (some with chinese writing), and just get frustrated.
I liked a few of the custom rom's I found, but the crazy thing, is the spen gestures (specifically the double-tap with button down for quick memos) are just too important to be without. I got the phone for work, and thought those where neat 'features'. Well.. seems I can't live without them.
But NOTHING I can find helps. I've tried methods listed on rootgalaxynote.com to unroot and get back to stock, and everything looks fine till I try either ota updating or kies updating. The phone simply isn't recognized in kies, and the ota update says nothing is available. and I know it IS available, cause I did the upgrade just after it was released, before I did all this custom rom stuff.
I'm start to get at my wits end. I simply want my original stock firmware etc. back on the phone, upgraded to ICS, and then I can just forget about everything else.
Is there anyone that can help?
P.S. if you know of any links I may have overlooked, please just post them. Believe me when I say I've spent well over a week just browsing the forums and google, doing searches etc. Its entirely possible it's something obvious that I just didn't see... with my 3 older kids and a newborn, I'm getting almost zero sleep, and am constantly frazzled. I sometimes don't even realize my wife is talking to me (on the worse days).
Anyways, thanks for anyone's help.
Click to expand...
Click to collapse
If I'm you I would continue with a custom rom. GNote replaces what you want. You can always install a TW based ROM. What I do is have Gnote as a shortcut on my homescreen. With Gnote I can still write with my Spen. Personally, I'd never use a NON-JB Paranoid ROM. ICS has melted over the summer! Being able to tweak my DPI settings is very important for me for each app. The default DPI and screen layouts are too fricken big, ie; status bar and icons. My eyes are still fine so I don't everything humongous on my screen.
Make sure you have Odin3 v1.85 on your pc. Download the Bell ICS ROM from here:
http://www.hotfile.com/dl/163095548/c1447e9/I717MUGLF4_I717MBMCLF4_BMC.zip.html
Unzip it on your pc. Restart your phone to Download Mode (Hold "Volume Down" and "Power" to start your phone). Once in download mode connect to your pc and start Odin. Put the ROM.MD5 file in the PDA slot that you just unzipped and update away.
This will give you the Bell ICS stock ROM. Better than the OTA when it comes to rooting it. If you have been reading for a week then I am sure you know what that means.
SOLVED
Thanks for the tips/suggestions.
I did a little more reading, and came to this thread:
http://forum.xda-developers.com/showthread.php?t=1599127
Flashed the kernal/system/recover like it said, and still a nogo. So then I figured wth, lets flash modem too.
BAM. booted it back, and its currently snagging the ota update.
So now that I have the methods and files to get back to stock, I am no longer worried too much about the future. I did have paranoid 2.0 for a while, and was loving it, but the simple idea of doubletapping while in ANY app to get a quick memo was still missing. Maybe after a bit I'll be hating the touchwiz ui yet again, and need a change. But at least I know now how to get back to stock.
Go figure. The thread itself looks vaguely familiar from earlier in the week, but I for some reason must have skipped it. I just got off a nice nap my wife let me have, and HEY... i figured it out. Guess 'sleep' is actually kinda important
Modem is the most important part for having you phone recognized properly for the OTA update. Link I gave you would have given you the update.
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
NoClemency said:
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
Click to expand...
Click to collapse
S-OFF is really the way to go if it's still an option for you it's the only way to get the new firmware without relocking and taking the OTA then unlocking and rooting again read post 2 in the lazypanda thread found here http://forum.xda-developers.com/showthread.php?t=1737123 just go down the list and verify everything works before running lazypanda there are plenty of members that subscribe to that thread so there is plenty of help availiable
Also, rerooting won't do anything. You're already rooted? Think the problem is in the rom u installed. Possibly a bad download. Try downloading from a good connection and install it again. If it is close to stock like flex's stock w goodies just clear cache and dalvik in recovery.
And what do u mean u tried a few recoveries? Cwm doesnt work well with the evo LTE. Try twrp 2.2 and leave it alone until its updated again.
What is your hboot? What rom did you try flashing?
Sent from my lair.
Im also getting this issue and i know its not anything to do with rooting and all that since ive been rooted since i picked this up from best buy on preorder release day and ive been flashing and running the same rom and mods forever now also i was using wifi yesterday soooo yea lol
Recognized Hooker Killer
First, I don't believe I can make my phone S-off, because it has software version 2.13.651.1 710Rd on it and even though I do have a nandroid back on 1.13 hboot, for the default rom from a long time ago with my old HTC EVO LTE, I can't flash back a hboot to 1.13 so I believe I'm stuck S-On for now. Let me know if I'm wrong.
I've attempted several different roms including fresh rom 5.1.1, viper4G_1.0.0, and a jelly bean rom (cm-cfX-20120904-OFFICIAL-jewel all with the same problem. As for recoverys, I should have said I've tried restoring back to several different nandroid backups that I created in the past that were working just find with my old HTC EVO LTE.
Right now my phone is unlocked and rooted. I am running H Boot-1.19.000, I am S-On, and Radio-1.12.11.0809.
I know this problem has something to do with flashing new roms, because when I do a nandroid back up to the default rom, I don't have this problem, and the wifi is working great, I only have this problem if I try to flash any custom rom or use a nandroid backup that I made with my old HTC EVO LTE.
Again, this is not my first time around the track with an HTC EVO LTE, this just happens to be a new phone that I recently got from Sprint when they were thinking my dropped calls were caused by my phone when in fact they figured out they had a tower down. Since then, the tower is back up, so that is why I just rooted this new phone they gave me.
Let me know if you have any suggestions or if you need anymore information.
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Please Help
NoClemency said:
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Click to expand...
Click to collapse
Hey im having the same exact issue I however went back to my stock backup from right after I rooted. The issue I had was I flashed a CMX nightly. I had been running them fine and suddenly everything went haywire i was bootlooping but only after about 30 seconds after the rom would load up. I'd have just under a minute to fish around and the it would reboot again. it was in this short window that I saw the wifi error and that it would not connect to the sprint network at all for voice or data. Im S-On Hboot 1.15 Evo LTE. I used Flash GUI to go from Stock sense to CMX as im sure youve figured out you have to do. Since i had backups of previous CMX nightlies I tried to just restore But none of my nandroids would fix the looping issue I managed to flash the boot img from the CMX rom i was previously on through adb/fastboot and it took but still my device kept looping. Finally i found this http://forum.xda-developers.com/showthread.php?t=1917106 but I didn't have any Sense Based Roms only my Stock Nandroid back up. So i used the Boot Image Flasher Tool, it took, then Instead of rebooting the system I went straight to my custom recovery and restored my Stock Sense BackUp since the tool flashes the stock sense kernel. To my relief the phone booted right up no problem connected to the network and all but to my dissmay the wifi is STILL broken somehow it says error and will not switch on. Everything else seems to be working fine though. This is crucial there is no way I can go without wifi on my phone. I don't want to ruin anything further or permanitely but i do plan to move forward. My plan is to download a sense rom (MeanRom) which im doing now but it's taking forever on 3G. Wipe everything (using TWRP 2.2) Data Dav rom and use super wipe, and try to install MeanRom. If anyone has any other suggestions Im all ears. Also im alittle confused on the Hboot kernel limitations I know I have to use Flash GUI if Im going from a sense Rom to Aosp and vise versa but do I have to use it when say Going to a nandroid backup of a sense rom while currently on a Aosp rom because I couldnt find a boot.img file in my backup file when i used the tool to extract it. I hate S-On HTC really screwed us with this. And I hate my original evo which had S-Off for dying on me on the 15th day and me having to get this replacement with 1.15 im sorry guys I love this phone but it has become a nightmare and the Evo 3D was no walk in the park either. I apprectiate any comment from anyone this is the first time in almost 8 years of hacking I've been truely worried I may not be able to fix something.
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
You also might want to try a different rom with its corresponding boot img. I'm currently running Venom rom with its boot img file and its working great. Right now, it sounds like your kernel is what is giving you problems like mine, so flashing the correct boot img should fix it.
vel7wil said:
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
Click to expand...
Click to collapse
Thank you I'll be sure to try this out quick update, in TWRP recovery I had (force MD5 check on all zips?) checked now I don't remember checking it or if it came checked by default but as soon as I unchecked it I was able to run superwipe and flash MeanRom which both failed multiple times when it was checked on. Not sure if this was the cause of my problem but I agree I think I got a bad kernel in the CMX nightly. Either that or the Flash GUI app didnt exract the boot image properly. Either way I haven't been brave enough to try another AOSP rom man I hate having S-On my first Evo was perfect then I get stuck with this locked down replacement. One question though is that boot image for a stock/sense rom just wanna be sure.
vel7wil's advice worked for me I was having the same issue. Download the zip he recommends. Use flash image gui to flash the kernel and clear dalvik and cache. I just did a standard reboot after that and it said "android updating... apps x of xx" then everything was back to working.
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