Database Develop

My HTC One is screwed?

Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
Here you can find the RUU. I don't know wich one you want ..
Install this RUU in Fastboot (USB) otherwise it won't recognize your phone!

MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.

Athrun88 said:
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Click to expand...
Click to collapse
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.

MrAdrianP said:
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Try this

MrAdrianP said:
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Click to expand...
Click to collapse
If your are S-ON you cannot flash an RUU that is older than your current firmware that's why its not working, you either have to stay on the same firmware or upgrade but you cannot downgrade so what you have to do is sideload a ROM using the tutorial dgtiii provided and everything will be back to normal, don't worry

[Q] HTC one reboots - Regardless of rom flashed

Hello everyone,
I've got a weird issue where I can recovery/fastboot/adb just fine.
But no matter what rom I install on my HTC One it boots up to a certain point (past the HTC logo to a midpoint of google boot up logo, sometimes into the os)
I had GPE 4.3
I tried to install 4.4 with the new radios. (S-Off)
It messed up once, I re-flashed cwm (had twrp) through fast boot - tried GPE 4.3 again .. still rebooting
re-flashed through fast new twrp again (just in case) - did advanced wipe - tried both roms still the same thing.
I've tried adb push and sideload.
Am I overlooking something here ? Any help or point to some reading material would be greatly appreciated.
I've been searching and searching and it seems most in similar situations can adb sideload roms when internal storage is not accessible and be right back up. I m stil stuck in the boot loop.
Currently downloading htc one sense 4.4. if I could get GPE 4.4 to work it'd be great.
Thank You in advance.
EDIT:
Phone is HTC ONE Rogers (Canadian)
Rooted - S-Off
Downloaded New ROM from - http://forum.xda-developers.com/showthread.php?t=2341395
Original ROM - http://htconeroot.com/htc-one-root/google-play-edition-rom-android-4-3-for-htc-one/

yasink said:
Hello everyone,
I've got a weird issue where I can recovery/fastboot/adb just fine.
But no matter what rom I install on my HTC One it boots up to a certain point (past the HTC logo to a midpoint of google boot up logo, sometimes into the os)
I had GPE 4.3
I tried to install 4.4 with the new radios. (S-Off)
It messed up once, I re-flashed cwm (had twrp) through fast boot - tried GPE 4.3 again .. still rebooting
re-flashed through fast new twrp again (just in case) - did advanced wipe - tried both roms still the same thing.
I've tried adb push and sideload.
Am I overlooking something here ? Any help or point to some reading material would be greatly appreciated.
I've been searching and searching and it seems most in similar situations can adb sideload roms when internal storage is not accessible and be right back up. I m stil stuck in the boot loop.
Currently downloading htc one sense 4.4. if I could get GPE 4.4 to work it'd be great.
Thank You in advance.
EDIT:
Phone is HTC ONE Rogers (Canadian)
Rooted - S-Off
Downloaded New ROM from - http://forum.xda-developers.com/showthread.php?t=2341395
Original ROM - http://htconeroot.com/htc-one-root/google-play-edition-rom-android-4-3-for-htc-one/
Click to expand...
Click to collapse
are you flashing the required version of TWRP ? TWRP_2.6.3.3_m7
also flashing rom's doesn't update radios .. flashing radios or firmware updates radios

Roger that
clsA said:
are you flashing the required version of TWRP ? TWRP_2.6.3.3_m7
Click to expand...
Click to collapse
Yep ... that is the exact one I got.
openrecovery-twrp-2.3.3.3-m7

yasink said:
Yep ... that is the exact one I got.
openrecovery-twrp-2.3.3.3-m7
Click to expand...
Click to collapse
are you doing fastboot erase cache after updating the recovery ?

As you are S-off, run a full RUU to remove any problematic flashes.

Thank you for the replys.
I've tried this fastboot cache erase .. didnt work
ruu is quite hard to find for Rogers HTC one (so far no luck ../ found some old ones links broken ... will keep looking)
I also got a chance to try and flash htc stock sense 5.5 with 4.4 kitkat from here:
(durm it .. can't post outside links yet sorry ..)
Phone still reboots before fully getting to os.
Weirdly enough, if I turn it off during this cycle. It turns back on by itself too.
So far to stop the loop, I have to boot to recovery (TWRP currently) and lock it.
I am guessing I should find a way to S-ON then flash an older rom.
Anything else I could try? :fingers-crossed:
Thank You everyone.

yasink said:
Thank you for the replys.
I've tried this fastboot cache erase .. didnt work
ruu is quite hard to find for Rogers HTC one (so far no luck ../ found some old ones links broken ... will keep looking)
I also got a chance to try and flash htc stock sense 5.5 with 4.4 kitkat from here:
(durm it .. can't post outside links yet sorry ..)
Phone still reboots before fully getting to os.
Weirdly enough, if I turn it off during this cycle. It turns back on by itself too.
So far to stop the loop, I have to boot to recovery (TWRP currently) and lock it.
I am guessing I should find a way to S-ON then flash an older rom.
Anything else I could try? :fingers-crossed:
Thank You everyone.
Click to expand...
Click to collapse
try this TWRP Nandroid Backup
http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-roger001-3-22-631-1-zip/
To use – download the latest version of the needed recovery and install it via fastboot:
fastboot flash recovery CWM.img
or
fastboot flash recovery TWRP.img
Then enter recovery either by holding power and vol down button until bootloader displays and then select recovery or if device is booted into the OS use this adb command:
adb reboot recovery
Now perform a test backup and allow it to complete. Then make a note of the folder in which the backup was created. Now copy the downloaded stock Nandroid into that same folder so that recovery will see the backup and allow you to restore it.
Click to expand...
Click to collapse

That nandroid backup method did take me the furthest so far.
(did wipe before doing it also)
The phone went into the os ... but only to reboot about 30 seconds later.
On the second reboot .. it said an app is asking for super user permission, before i could select allow or anything,
the phone has been boot looping again.
Weird.

yasink said:
That nandroid backup method did take me the furthest so far.
(did wipe before doing it also)
The phone went into the os ... but only to reboot about 30 seconds later.
On the second reboot .. it said an app is asking for super user permission, before i could select allow or anything,
the phone has been boot looping again.
Weird.
Click to expand...
Click to collapse
try wiping everything and try again

hi clsA,
thank you for replying.
I did try that, still bootloops. I also further tried:
install teaMseven - sense55 - kk - v2.3.6 with the new stock sense 5.5 rom flashed first.
I forgot to mention earlier, I did flash a radio after initially trying to upgrade to GPE 4.4.
The radio flashed was: RadioUpdate_4T.21.3218.21_10.16.1718.01L.zip
only because it was mentioned i'd get a boot loop going to GPE 4.4 without that update.
Theres no sim in the tray, could this radio update be causing this ? I tried re-downloading this radio for a fresh copy of the file also.
IF the radio is/could be causing this, is there a way to determine which radio to try?
I found: http://forum.xda-developers.com/showthread.php?t=2325564
Out of any further ideas for now

[SOLVED]
Hello everyone,
After so many days of trying, I finally found a way to fix my phone.
I noticed a lot of requests all over the web of a Rogers RUU. This is how I was able to bring my Rogers HTC back to life and stock.
I found this guide:
http://www.htc1guru.com/guides/return-stock-guide/
(Same website, that has the nandroid backup posted earlier by clsA)
follow ... that guide. Should be good.
I flashed 4.4 GP afterwards (as originally intended) and then OTA'd to 4.4.2. Everything seems to be running perfectly.
Thank You for the nandroid backup and leading me to that website clsA.

[Q] PLEASE POST full STOCK HTC ONE ROM exe for AT&T new kitkat Vers: 4.18.502.7

ISSUE RESOLVED: keeping post since active since I still need the rom exe. But boot looping fixed.
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!

more info
by the way, when it crashed i had installed the ota update and then restarted play around with it, then rebooted in bootloader and unlocked, reinstalled twrp and AndRev HD 51. I've noticed two problems there. The first is that the Xposed module's latest update totally defeats my internet wifi and especially crashes vpn sevice. prior versions did not and I could not down-install to prior version (is preinstalled in HD 51). The other problem is that in looking around for this boot loop probably, turns out that TWRP apparently doesn't get along well with the encryption. don't know why. this stuff may or may not be part of the problem, but at this point i have no OS, an erased cache and can't even get into recovery (tried flashing twrp, older twrps and CWM. thanks.

You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device

randomOne1111 said:
My AT&T HTC One is stuck in boot loop, probably to do with the KK OTA update. I have looked everywhere, read posts all night, and tried all of the various reboots and reflashings of recovery files and firmware, erased caches, locked and unlocked bootloaders. Can anyone post the executable RUU for the stock ROM KK version 4.18.502.7? I'd really appreciate it. I can't sideload a zip (it stalls). I'm aware of the other post asking for the same thing and the response in it with a link to the file, but that link actually is only to a recovery zip with darkbootloader, which seems also to require S-OFF, even if I did have some way to sideload it.
The firmware updated before it began looping, so I can't just reinstall a prior stock ROM exe file, as far as I can tell. I tried anyway!
I hesitate to install the .1540. Dev. Ed. version of the ROM that's available because it says in the notes that it's "compatible" with my cid and PN, etc, but I think they mean for recovery file purposes and not for a full ROM install. So I think I just need the ROM exe, if anyone has it? Thanks!
Click to expand...
Click to collapse
This RUU does not exist yet, only the FOTA version - I've been in talks with HTC about this very thing. They do not have an ETA for the RUU, unfortunately.

SaHiLzZ said:
You are screwed if you have no recovery, and the phone is s-on. You need to find a way to get in recovery. Alternatively try to flash the firmware only from OTA to get stock recovery.
sent from my mobile device
Click to expand...
Click to collapse
Hm. I did flash the firmware from an OTA. But couldn't actually boot into recovery after that. I can flash custom recoveries but can sideload without the intall stalling about a third of the way through (just hangs, no error messages). Then after that if I restart it loops. I can maybe fix the "tampered" warning and swap it out somewhere. I think it's the encryption while using twrp maybe resulted in some hiccup. But I thought the firmware flash would fix that. And I'm not sure how you can actually tell whether the flashed firmware is successful. (it says it is in the command prompt, but the phone doesn't really do anything all that different and i already updated with the OTA so the numbers won't change).
Looking at the board today and reading through the posts I see many people reporting basically being in the same boot loop boat after the OTA update, though with diff versions maybe there's some FW problem. weird so many posts of similar boot looping.
Thanks for responding.
This issue is temporarily resolved, was able to push ARHD in TWRP (would not sideload without erroring out during install, but was able to push zip to sdcard and then install from there) after much wiping using both twrp and cwm. Did notice when using CWM recovery would not install ARHD off sdcard push, and would flag unknown files .... android..security during wipes, so i am guessing that encrypting a custom ROM at least with TWRP as recovery was a bad idea. hopefully this will stay stable until the KK OEM RUU EXE is available. Thanks for the help.

[Closed] How to Return to Stock Recovery for OTA Updates

Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)

You can install stock recovery using fastboot command.
However to apply OTA, if your phone is S-On, you must lock the bootloader.
You don't have to lock bootloader if your phone is Soff, for OTA, just stock recovery is good enough.

lyciansarpedon said:
Hello all again. It's been almost year since last here, and clearly I have learnt nothing in the meanwhile.
First, specifications:
I have an HTC One M7 (AT&T) that had been updated to 4.3 OTA, then unlocked via htcdev, flashed with CWM 6.0.4.3 recovery, and then rooted with the Superuser zip on the CWM site. The device remains S-On.
Now, for the detailed inquiry:
I've been in the Stone Ages (see, Jelly Bean) for a while and have been planning on updating my phone for some time. However, the easy way, i.e. OTA, requires that I return to stock recovery. Now, as far as I know, this would require the use of an RUU (I'm not quite sure which one - perhaps "RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2.exe" from AndroidRUU?) which would require that I lock my bootloader (correct?) which would also happen to wipe my device. I was hoping that I might be able to flash the stock recovery image (which I have been unsuccessful thus far in finding on my friend Google, since I assume it was deleted from my phone when I flashed CWM?) without having to go through an RUU. Is such a thing feasible? Where would I find the appropriate stock recovery image file to do so? And is there a way, once I (hopefully) receive the OTA update, to copy that new stock recovery image to my PC before I switch back to custom recovery to avoid bothering all you fine folks about this again?
Thank you all for taking a look, and I appreciate any direction you may provide. (Seriously, though, I'm suspecting that the reason I haven't gotten an LTE signal the past couple months is because my radio is so outdated.)
Click to expand...
Click to collapse
Just flashing the stock recovery will probably not allow you to successfully install OTAs. You have to have stock rom, stock recovery and possibly some /preload/ files that were deleted when you unlocked your bootloader. The quickest way to stock for OTA would be to flash a RUU. I would propose this route:
Option A
Lock your bootloader
Flash RUU 3.17.502.3
Receive OTA updates if they are still available
Option B
Lock your bootloader
Flash in bootloader: firmware 4.18.502.7
Flash RUU 4.18.502.7
Flash in bootloader: firmware 5.12.502.2
Flash TWRP 2.6.3.3
Download Guru Reset 5.12.502.2 and place on your sdcard
Boot into TWRP and install GURU Reset
For complete stock Say no to installing Root when exiting TWRP and Flash the Stock Recovery

Thanks for the feedback. I was a bit surprised to find out about needing to re-lock the bootloader even with stock recovery since a bunch of other places I looked said that I could use an unlocked bootloader as long as everything else was stock (just couldn't find a way to return to stock recovery without an RUU - which would require re-locking the bootloader - at the time). Used this (http://forum.xda-developers.com/showthread.php?t=2545227) from Majmoz's signature and got the relevant recovery.img from it. Since I had it, I figured I might as well try it before going through the process of re-locking the bootloader since being bounced out of the OTA and then going through the full process of relock-RUU-OTA anyhow was the worst that could happen. Turns out it worked.
So, for posterity's sake in case anyone else should come across a similar issue, everything I did (most of it probably unnecessary, but who knows):
-Made CWM backup (in case I happened to need to re-lock the bootloader which would wipe the device data to factory)
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
-Went into recovery from the bootloader, fastboot, plugged in the usb, and flashed the stock recovery (fastboot flash recovery [the downloaded stock recovery .img file in the platform-tools directory])
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
-Went into AT&T Software Update, let it download off the Wi-Fi, and let it apply. Did its thing with the image of the green downward arrow within the circulating arrows followed by reboot a few times, the "Android Update" screen where it runs through your applications, and voila, I am now on 4.4.2.
Updates:
-Have downloaded the updated stock recovery image.
-Flashed CWM Recovery back onto device
-Re-rooted via CWM (confirmed root)
-Made a new backup through CWM.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.

lyciansarpedon said:
-Pulled that backup to my PC in case flashing to stock recovery wiped it (adb pull [backup directory, e.g. /mnt/shell/emulated/clockworkmod/backup/[folder]])
Click to expand...
Click to collapse
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
-Went back to the bootloader menu and entered the stock recovery and rebooted the device from there (I recall having to do that when I flashed CWM for the recovery to "stick", not sure if it was necessary here)
Click to expand...
Click to collapse
no but again its a good practice to check if the recovery is working correctly.
Now, if only I could figure out what the issue with the LTE signal is since I've never fiddled with that - guess I can heckle AT&T tech support for that.
Click to expand...
Click to collapse
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Is your apn correctly configured?

alray said:
Flashing a recovery will not wipe anything but its a good call to backup on your computer :good:
Click to expand...
Click to collapse
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
alray said:
Have you checked you preferred network setting (GSM/CMDA/LTE AUTO)?
Click to expand...
Click to collapse
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!

lyciansarpedon said:
Good to know: the backup directory actually showed as empty while I still had stock, and then each backup's folder reappeared when I put CWM back on - was patting myself on the back for a few minutes there.
It worked! Used *#*#4636#*# to pull that up (didn't know one could do that!) and, sure enough, it was on "WCDMA Preferred" for some reason. Switched it back to "GSM/CDMA/LTE AUTO" and my long-lost signal has returned.
Thanks a ton!
Click to expand...
Click to collapse
youre welcome glad it worked!

Problems with updating CM12

I believe the root problem of this may be using TWRP manager to update recovery, because it happens after I attempt to do that. It asks if /dev/block/mmcblk0p43 is the correct partition, which i believe it is, and attempts to flash it. Once it attempts, it says it is failed, but when I reboot into recovery it is the updated version of TWRP. I think it may be messing up my partitions somehow.
The problem is, I RUU'd last night with the official Sprint exe, and all was fine. Rooted, installed recovery and flashed the latest of CM12. Get it up and running, go about re installing all my apps, and use TWRP manager to update the recovery. Today the new nightly has some M8 specific updates to it, so I decided to flash it. I flash in recovery, get no errors, but once I reboot it stays stuck at the white HTC screen where they threaten to send you into poverty for misusing their software.
Does anyone have any input on how to correct this issue, outside of RUU'ing again?

Krunk_Kracker said:
I believe the root problem of this may be using TWRP manager to update recovery, because it happens after I attempt to do that. It asks if /dev/block/mmcblk0p43 is the correct partition, which i believe it is, and attempts to flash it. Once it attempts, it says it is failed, but when I reboot into recovery it is the updated version of TWRP. I think it may be messing up my partitions somehow.
The problem is, I RUU'd last night with the official Sprint exe, and all was fine. Rooted, installed recovery and flashed the latest of CM12. Get it up and running, go about re installing all my apps, and use TWRP manager to update the recovery. Today the new nightly has some M8 specific updates to it, so I decided to flash it. I flash in recovery, get no errors, but once I reboot it stays stuck at the white HTC screen where they threaten to send you into poverty for misusing their software.
Does anyone have any input on how to correct this issue, outside of RUU'ing again?
Click to expand...
Click to collapse
S-on or S-off? If S-on you have to flash the kernel separately from the ROM.

Magnum_Enforcer said:
S-on or S-off? If S-on you have to flash the kernel separately from the ROM.
Click to expand...
Click to collapse
I've been s-off'd since day one, and I just booted into bootloader and double checked, still s-off.
I did however this morning flash the Blissful kernel and it booted, and noticed your comment when I came to update. It's very strange that it needed the kernel flashed.