I installed the CLEANrom tapped edition rom after wiping everything as instructed. It boots and initially I had issues with wifi working, but that seems to be working after flashing a stock kernel. Now if I try to play anything with sound or change the volume using rockers or in the phone itself it forces a reboot.
Any ideas?
Thanks
You are probably on old firmware and need to flash the patch
http://www.myandroidfiles.com/Downloads/Rezound/3.14.605.5/GB%20Firmware%20Patch.zip
Sent from my Rezound
Still having issues
Thanks for the reply. I actually ended up flashing it back to the rom that I had. I also made sure I flashed it to the original recovery as well which is amon ra. The rom I flashed it back to was the clean rom standard 4.4.
Unfortunately, I'm having the same problem no. If I go into the dialer and hit a number it freezes and force reboots. If I hit the volume rocker, it freezes and force reboots. It just force reboots for almost everything except for texting and going into apps.
any thoughts? The 4.4 worked fine on the firmware that's on here, and I did do the wipe and reset before I installed back. Maybe I bricked it?
Definitely not bricked. You wouldn't be able to even boot if bricked. What firmware are you on?
Here is some information
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Mr. Lando said:
CleanROM standard 4.4
htc sense version 3.6
android version 4.0.3
kernel 3.0.16
I think the hboot was 2.11 or something like that.
Yeah, I figured it's not totally bricked. It should be on ICS. The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
Even though your on ics, it looks like your on gb firmware. Search for the gb patch for ics and flash in recovery and problem solved
2.11 hboot is gb firmware, 2.21 or up is ics firmware
Mr. Lando said:
The issues started when I removed my old rom and put on this tapped edition clean rom which was listed as a good rom to use in the rezounds rom options. Kinda stupid that it would create this whole mess if it actually was a working rom. Maybe it shouldn't be listed... lol
Click to expand...
Click to collapse
It runs just great on the correct firmware lulz
Correct Process for Updating firmware
Hello,
You stated that 2.11 in the hboot indicates gb firmware. Do you know a link to the correct thread that would give me the appropriate process for updating the FW one that will work with the CLEANrom 1.4 dev version? I got the wifi working again after flashing the "old firmware patch" and then reloading CLEANrom 4.4 everything went back to normal. However, I hate sense and I would like something without it which is what the dev version provides, but if I cannot get wifi working then it's kind of useless. When I say "if I cannot get wifi working" what I am indicating is that when I try to run the cleanrom dev version 1.4 WIFI gets stuck on "turning on" but never turns on and eventually just says "error" with no further details. I searched through forum feeds and found a few forums that hinted on steps, but many people have seemed to be confused by this issue in the past and perhaps it is related to firmware as you said.
Thanks
i would wipe everything again, reflash the rom, and then immediately the patch. that should fix everything. key thing is flash the patch before booting the rom. ive flashed the patch after rebooting before and had things go haywire. not a promise that it will work, just letting you know what ive run into
Scosler has everything listed in the op for the rom, and all files are there as well. There's a bunch of different instructions for however your phone is set up.
Sent from my Rezound
Continuing...
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
If s on and on 2.11 hboot Method 4:
-Copy ROM to SD Card AND PH98IMG.zip AND GB Firmware Patch to ROOT of SD Card
-Reboot to recovery
-wipe data / Factory Reset
-Flash ROM
-Flash GB Fimrware Patch
-Use Developer Menu to reboot to bootloader and flash the boot.img file in the PH98IMG.zip
-Reboot
-Profit!
Based on what you typed you didn't flash the firmware fix...
Mr. Lando said:
Hi,
Not to sound like a total idiot here, and I probably do, but you had mentioned I should update the firmware so that hboot indicates 2.21 or higher. Is there an easy process for this or a thread I can turn to so that I can be sure it's updated. I believe I already did the step you mentioned.
I wiped/reset ----> flashed the 1.4 rom ----> ran the PH98IMG.zip----> then boot ----> then no PROFIT. wifi will not work. Maybe it's firmware after all. I don't know how I ended up on gb, I had a friend walk me through this the first time and I'm pretty technical. I used the automated tool by that one guy to flash the amonra recovery and I thought that was 2.21 or higher, but maybe I'm wrong.
Click to expand...
Click to collapse
If i were you i would either s-off or flash one of the ics leak ruu's. that will help. there are many ways to solve your problem but those are your best bets
My issue is resolved. Thanks for all of your help and insight.
Sent from my ADR6425LVW using XDA
Care to share what you did? I am having exact same issue . . .
nvm - resolved: applied GB Patch right after ICS ROM flash (who would have known - I was kind of ignoring those GB patch instructions, since they did not apply to ICS).
Related
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
bandtrumpet7 said:
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
Click to expand...
Click to collapse
Well you shouldn't panic. Which radio did you flash? I would flash the MR2 one from this link http://forum.xda-developers.com/showthread.php?t=1154010 . If that doesn't work, I would download the rom directly from Synergy here http://androidfilehost.com/XxXViRuSXxX/roms/synergy/thunderbolt/
From recovery, wipe everything manually (Wipe data/cache/dalvik) than flash the file from where it is on your SD card. If you need specific instructions feel free to ask.
bandtrumpet7 said:
Oh, fuuuu...crap.
I may have screwed up here. I rooted my device using Revolutionary, and then using ROM Manager installed the latest Synergy mod on my stock (unrooted Froyo) Thunderbolt. Everything loaded fine, it seemed to be flawless ... but after the update I'm not getting any signal at all. I figured this was a radio issue, so I downloaded the latest radio that was leaked (the 2.11.605 one), put it on my SD card, and flashed that. It said it was "updating" the radio (RADIO_V2), but still no luck. I've tried a few different versions, and although it seems to "flash" and update fine, there's still no signal. Not 1x, 3g, or 4g. Nada. :-\
According to HBOOT, "RADIO" is 1.16.00.0223r, if that helps.
Any ideas on how I can basically undo all this, or have I spectacularly failed at this?
-BT7
Click to expand...
Click to collapse
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
loonatik78 said:
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
Click to expand...
Click to collapse
Sure hope he's just confused...
loonatik78 said:
Am I reading this right???? You said you rooted with Revolutionary.... Then you flashed some Synergy mod with ROM Manager (always a no-no).... onto your STOCK, UNROOTED FROYO Tbolt???? How did we go from rooted with Revolutionary to stock, unrooted Froyo? I'm confused.
Click to expand...
Click to collapse
Lol I saw that, I decided not to say anything, I guess you have the sharper tongue than me
Ya pretty scary. I'm hoping he meant he rooted his phone and when he said unrooted, he meant "stock" froyo build on his phone.
Sounds like he is able to boot up, just not get any signal.
I'm guessing he is not too skilled in the ways of Android yet.
Lol just found something interesting. Synergy isn't even on rom manager? I was checking to see if the version ofcsynergy he was using was a previous froyo build, and I can't even find it on rom manager
He probably meant that he used Rom Manager to load the rom rather than using recovery.
haha weird
OK, so I was tired when I wrote my initial post, and I probably didn't make a whole lot of sense. Let me be a bit clearer.
For reference, no, I'm "not too skilled in the ways of Android yet". I've been living with Froyo, anxiously awaiting Gingerbread, and then got fed up and read about all the benefits that come with rooting. Now that an easier method has presented itself - the Revolutionary method, as opposed to opening a command prompt and doing the adb stuff, which I can do - I rooted a friend's phone - but decided to not take the plunge myself - I decided to go ahead and give GB a shot.
So let me break down what happened:
- My phone was unrooted previously, running the same software it came with. I'd done a few OTA updates that Verizon provided but had never gone into my phone. That's why I called it "stock", sorry if that terminology confused people. I just meant it was the OS that came on my phone - Android 2.2 w/ HTC Sense and all that jazz.
- I ran the Revolutionary method posted in the "Thunderbolt Android Development" forum. Worked fine. Ran Recovery and installed Superuser permissions as the documentation said. Worked great. Have a phone where if HBOOT launches, it says -Revolutionary- at the top, and it's got -S OFF. My phone technically is rooted.
- The Synergy mod was also posted in the "TB Android Development" forum. I downloaded that and installed it using ROM Manager (Install ROM from SD). Worked fine ... but then had no signal. Every other aspect of the phone seemed to be working. My radio just wasn't working.
- Downloaded an updated radio from the TB Android Dev. forum, ran that, it said it was updating the radio. Rebooted the phone after the update ... still no signal.
I "solved" this problem by flashing the leaked HTC/TB Gingerbread build, the latest one that was like 400 MB, and when I booted my phone up again I had Gingerbread on my phone with HTC Sense 2.1, and I had signal. So I'm living right now with a fully working phone, but I wanted to dip my foot into custom ROMs. So now I have a backup method just in case the radio thing doesn't work again, but what can I do to install a custom ROM and ensure that I get signal?
Thanks for the response, xebryus - and to everyone else, sorry I was a little confusing. Everybody starts from somewhere, right?
-BT7
Download the GB ROM you want, boot into clockwork (please don't install VIA ROM Manager). In clockwork using you Volume keys to move and the Home button to select....
Select Wipe Data/Factory Reset
Select Wipe Cache
Select Advanced
Select Wipe Dalvik
Select Go Back
Select Mounts and Storage
Select Format /system
Select Go Back Until you are at the first screen
Select Install from SD Card
Select Choose ZIP
Go to the folder where you downloaded the ROM
Select ROM
Select Yes.
When it is done Reboot.
Enjoy!
Sent from my SHIFTAO5P using XDA App
Hey, at least you didn't brick your phone, so kudos for you for getting that far.
As others have stated there are basically two kinds of radio versions out there. One that work with Froyo builds and ones that work with GB builds.
So depending on the rom you are loading, you just have to make sure you have the right radio to match the rom(the rom thread should tell you what radio it requires). From what you were saying, it sounded like you just had the wrong radio.
Anyways, couple of things you want to make sure you do. Any check to make sure the checksum is correct on the radio (so that it's not corrupt) otherwise you could have some major issues. Also, once you flash the radio and you get your phone back up, make sure to either rename or delete the PG05img file from your SD root, otherwise, again a major hassle.
Check out the noob thread at the top of this forum also. It has great info there that will help you on your journey.
Good Luck.
I have always felt more in control flashing from recovery or hboot but I'm curious why no rom manager?
Sent from my Tbolt running Das Bamf 3.0...
RevosFTS said:
I have always felt more in control flashing from recovery or hboot but I'm curious why no rom manager?
Sent from my Tbolt running Das Bamf 3.0...
Click to expand...
Click to collapse
When the TB first came out, it seemed that people were having issues with using rom manager to flash roms (alot of force closes, things in general not working correctly). So many experienced people said to use recovery rather than rom manager to flash anything on the TB.
I guess that idea just kinda stuck after that.
Ok thanks. I will still use recovery anyhow I am more used to it. Plus I'm kinda old school I love adb haha
Sent from my ADR6400L using XDA App
I have downloaded Synergy Rom and have no problems except that I am not able to get the radio to flash. I am on verizon and chose the MR3.5 radio. I did a battery pull and then pressed the power and volume down button to enter HBoot but I do not have an option to Upgrade. What am I doing wrong any help is appreciated. I need help quick, thanks!!!
1more thing when i am in the HBoot window my only options are Fastboot, Recovery, Factory Reset, Simlock, Hboot USB, System Info, Image Crc..... it says radio is 1.16.00.0402w.
Does this mean the radio was already upgraded. Why can I not get a signal then?
Did you rename the .zip and have it on the root of your SD card?
Sent from my ADR6400L using XDA App
HarlyFan said:
1more thing when i am in the HBoot window my only options are Fastboot, Recovery, Factory Reset, Simlock, Hboot USB, System Info, Image Crc..... it says radio is 1.16.00.0402w.
Does this mean the radio was already upgraded. Why can I not get a signal then?
Click to expand...
Click to collapse
Nope..402w is still MR1. Sounds like you are already in bootloader so at this point if it isn't updating then more than likely the file is named incorrectly as stated above.
Radios HAVE to be named PG05IMG.zip (3rd character is a ZERO, not the letter "O"). It HAS to be in the root folder of your SD card. Now, turn the phone OFF.
Next, hold down the VOL-DOWN button. Keep it held down. Is it still held down ? If so, push and hold down the POWER button. When the screen turns on, you can release both. This menu will automatically look for 3 or 4 files with certain names. One of the names (files) it looks for is .... PG05IMG.zip. When/if it finds it, it will check it and ask you if you want to load it. Tell it to load it and then leave your phone alone. It will update it and reboot like normal (if successful).
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
Well I caught a break with the Rezound deal, I'm free from evil Motorola ~ droid X2
Is this a proper Rezound understanding?
1) The process is: htcdev-[unlock bootloader]
2) Use a perm root "application"
3) Install 1 of the 2 recovery modes
4) Pick a Rom ~ (do you need to be on a specific stock version first?)
From lots of searching, Cleanrom's ICS developer edition and Bamf (I'm not sure what version of it is better) appear to be the most reasonable choices?
I'm not sure if either of them have the "beats" tweak, or if the Bravia engine is a big improvement. Also, the custom kernels don't work with ICS right now I believe?
Finally, coming from Moto SBF, I don't realize how dangerous romming is with HTC, aka safety net.
I'd GREATLY appreciate any help/comments on the speculations and questions <3
Watercycle said:
Well I caught a break with the Rezound deal, I'm free from evil Motorola ~ droid X2
Is this a proper Rezound understanding?
1) The process is: htcdev-[unlock bootloader]
2) Use a perm root "application"
3) Install 1 of the 2 recovery modes
4) Pick a Rom ~ (do you need to be on a specific stock version first?)
From lots of searching, Cleanrom's ICS developer edition and Bamf (I'm not sure what version of it is better) appear to be the most reasonable choices?
I'm not sure if either of them have the "beats" tweak, or if the Bravia engine is a big improvement. Also, the custom kernels don't work with ICS right now I believe?
Finally, coming from Moto SBF, I don't realize how dangerous romming is with HTC, aka safety net.
I'd GREATLY appreciate any help/comments on the speculations and questions <3
Click to expand...
Click to collapse
You don't need to permanent root it. Most (if not all) ROMS include root, and you can install root with Amon ra (DON'T use clockwork mod)
Cleanrom de is great. I use that one. I believe it has the beats Audio, but if it doesn't there is a flash able mod for it (link in my sig). And as far as the Sony bravia engine goes, I didn't notice any real improvement with it.
Custom kernels don't work in ICS for now....
Whatever you do DON'T upgrade to the ICS RUU it screws up most people's phones
And it is not possible to brick an s-on htc phone as far as I know. So romming is 120% safe
I disagree about the upgraded firmware. it doesn't necessarily harm anything. for me I get slightly better signal if not equivalent. problem with the newer radios is that you can't revert back to older without s-off. be sure to flash the old firmware patch before flashing the ics rom if u decide not to update. also amon ra 3.15 is the latest stable for ics,it won't give you memory card detection issues
use the "thanks" if I helped you at all
dyetheskin said:
I disagree about the upgraded firmware. it doesn't necessarily harm anything. for me I get slightly better signal if not equivalent. problem with the newer radios is that you can't revert back to older without s-off. be sure to flash the old firmware patch before flashing the ics rom if u decide not to update. also amon ra 3.15 is the latest stable for ics,it won't give you memory card detection issues
use the "thanks" if I helped you at all
Click to expand...
Click to collapse
Well I have worse signal since the update, my wifi constantly dropps out, and my CPU is always running at max clock speed making my phone hot and my battery life crap. Some other people have this issue, so best not to try than to try and have bad results not being able to go back.
AshtonTS said:
Well I have worse signal since the update, my wifi constantly dropps out, and my CPU is always running at max clock speed making my phone hot and my battery life crap. Some other people have this issue, so best not to try than to try and have bad results not being able to go back.
Click to expand...
Click to collapse
radio can only effect phone related issues as low signal/bad reception. the new firmware wont effect wifi. cpu trouble is due to stock kernel of ics. not firmware related. need your facts right. I'm on new firmware with cleanrom de for awhile now with none of your issues since I use the conservative cpu governor and underclock to 1.18ghz. if the firmware would effect anything for me or anyone who upgraded is the low signal,bad reception,slow mobile data rates. that's it. it's hit or miss with phone related connections. just a gambling risk. won't actually cause harm. won't notice a thing if you're close to towers
use the "thanks" if I helped you at all
dyetheskin said:
I disagree about the upgraded firmware. it doesn't necessarily harm anything. for me I get slightly better signal if not equivalent. problem with the newer radios is that you can't revert back to older without s-off. be sure to flash the old firmware patch before flashing the ics rom if u decide not to update. also amon ra 3.15 is the latest stable for ics,it won't give you memory card detection issues
use the "thanks" if I helped you at all
Click to expand...
Click to collapse
You need to flash the patch after the rom install if running the old firmware.
1. HTC Dev Unlock
http://htcdev.com/bootloader/
2. Recovery
Install amon ra in fastboot
http://forum.xda-developers.com/showpost.php?p=23781936&postcount=428
download that from there then get to fastboot and type
fastboot flash recovery "nameofrecovery".img
in the command line in where your fastboot stuff is
3. ROM
Probably don't use the newest unofficial ruu
a.So find a rom you like
b. make sure it will work without the newest ruu (firmware) or will with a patch
c. Flash the rom in recovery
4. KERNEL
depends on the rom either
a. flash the boot.img in fastboot
"fastboot flash boot boot.img"
b. install the PH98IMG.zip in the bootloader
- deleted the ph98img.zip off the sd card after you flash it to avoid later problems
Hope i helped!!
EDIT: heres a rom that is oldish but i know it works on the old firmware without any patch.
ROM : http://dl.dropbox.com/u/53731771/ICSSENSELESS403REDEFINED.zip
-it's by Joelz and a senseless pretty good - thanks Joelz
Kernel for that ^ rom http://dl.dropbox.com/u/53731771/PH98IMG-senseless1.7.zip
I think that kernel is over clocked a bit too.
so to recap you would put the rom on your ext sd card and flash in recovery
then rename the ph98img-senselsblahblah.zip to just ph98img.zip
place on ext sd card
then boot into bootloader and accept the update and it will load the kernel for you.
Then reboot and delete the ph98img from your sd with a file explorer
To boot into bootloader is turn off phone then hold volume down and power at the same time untill your in a white screen with some stuff.
Navigate with the volume to go up or down and power to select.
.... thats a lot of info ... again thanks to all the dev's (mandatory to thank the devs at least 1 bajillion times a day, for all the free awesome stuff they do)
Edit numero dos: The safety net for htc phones are the ruu's just stay on the official released ones.
A RUU resets EVERYTHING to stock, it's a .exe that you run on your computer while in fastboot mode on the phone (must re-lock bootloader to run/ "fastboot oem lock")
dyetheskin said:
radio can only effect phone related issues as low signal/bad reception. the new firmware wont effect wifi. cpu trouble is due to stock kernel of ics. not firmware related. need your facts right. I'm on new firmware with cleanrom de for awhile now with none of your issues since I use the conservative cpu governor and underclock to 1.18ghz. if the firmware would effect anything for me or anyone who upgraded is the low signal,bad reception,slow mobile data rates. that's it. it's hit or miss with phone related connections. just a gambling risk. won't actually cause harm. won't notice a thing if you're close to towers
use the "thanks" if I helped you at all
Click to expand...
Click to collapse
Just throwing my experience out there so this guy doesn't have the same problems I did. And I'm not the only one who has problems with this firmware. And the CPU frequencies don't scale properly for some users, which is why I get bad battery life even though I have the CPU underclocked to 810mhz. And I'm well aware that it has todo with the kernel but for now we can't do anything about it. Need your facts right
I'm on the new firmware and haven't had any problems, though others have. Most of the current ICS roms now have a patch so you don't have to risk it. There are both GB and ICS kernals available that allow you to overclock, etc. Just make sure you're installing the correct kernal for your version of android. I've flashed most of the roms available right now and have been very happy with Cleanrom and Rezrom.
I recommend CleanRom DE I'd you like senseless. Been running it since the latest of his updates. Runs like a champ, and there are even some themes available.
Sent with a Rezounding HELL YEA!
So I can use a Temp-root and not even bother unlocking the bootloader?
and what about reflashing different roms ontop of a current custom rom?
Watercycle said:
So I can use a Temp-root and not even bother unlocking the bootloader?
and what about reflashing different roms ontop of a current custom rom?
Click to expand...
Click to collapse
Don't temp root. Definitely use the htc unlock. And what do you mean by flash a rom on top of a custom rom exactly?
can't flash one over the other aka dirty unless it's an update to the same rom. example would be cleanrom 1.2 over 1.1. it's possible but not supported. always best to wipe and install fresh after a backup
Well, as I understand, I should update my phone with system updates, htc unlock, use oneclickroot/zergrush, install amonra recovery, and just flash/follow the steps from cleanrom ~ the all in one seems like it could help, i'll probably try the sequence on there XD
But then what if I wanted to switch over to the Evita one to give it a try?
The "s on/off" thing confuses me to, is that the bootloader?
haha, sorry for the questions, thank you for help =)
Watercycle said:
Well, as I understand, I should update my phone with system updates, htc unlock, use oneclickroot/zergrush, install amonra recovery, and just flash/follow the steps from cleanrom ~ the all in one seems like it could help but it never mentions root.
But then what if I wanted to switch over to the Evita one to give it a try?
The "s on/off" thing confuses me to, is that the bootloader?
haha, sorry for the questions, thank you for help =)
Click to expand...
Click to collapse
after you unlocked the bootloader with htcdev you go right to a recovery. reboot to bootloader and once it's in fastboot you run the flashing recovery command,reboot to recovery and follow the roms instructions. if were to try another rom you backup what you need then wipe/follow steps for the next rom. reason you skip rooting before an install is because nearly any rom you pick is already rooted
thank you that clears it up =)
one final worry is the RUU (what is it?) and phone version, should I just update everything prior to doing this stuff?
I would go ahead and update through settings before you root. (there's no reason not to really). As to whether or not you flash the leak, that's entirely up to you. I personally notice no difference.
The ruu (ROM update utility?) is a package that contains a complete update. (rom, kernel, etc.)
S-on/s-off refers to the security flag. HTC sets the flag to on which prevents the changing of radios (and splash screens, among other things) and makes other changes more difficult (though still doable, such as kernel changes).
Sent from my ADR6425LVW using XDA
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