yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] winnower:
I hit the "OK" on the OTA box without thinking, and only realized my mistake when TWRP came up after it started it's process.

I can get all the way back into the Launcher, but after about 60 seconds is reboots.

I'm guessing all I need to to undo one thing, or maybe flash a new/stock bootloader, but I don't really know where to start. I am coming from Samsung phones, so the terminology is rather different with HTC.

I've already made a backup of boot, system, and data, from within TWRP and copied it off the phone. I also quickly moved the OTA zip off my phone as well in order to keep a copy of it. Lastly, I can boot into "Safe Mode" (which I discovered by accident) and it doesn't do the reboot thing.

Any help at all is appreciated.

Thank you.

EDIT: Success!

Turns out I needed to re-flash my SuperSU binary from TWRP. I re-flashed the version I had first which actually removed the SuperSU apk. I re-downloaded it from Play Store, then flashed the 2.01 update. Runs like a charm.

Thanks to everyone for the help.
[One (M8) Q&A, Help & Troubleshooting] hdorius:
Hi,if you already backup your ROM before OTA,just restore it
[One (M8) Q&A, Help & Troubleshooting] winnower:
I only did the backup after I got into the reboot cycle.

I haven't tried restoring it, but I don't imagine that it will work.
[One (M8) Q&A, Help & Troubleshooting] hdorius:
Can u please post your cid?u can find the stock nandroid backup that linked at my signature
[One (M8) Q&A, Help & Troubleshooting] Modding.MyMind:
No it will not work. Just delete the backup and save you the time and trouble messing with it. If you can grab a good backup from someone then you will be ok. Simply restore and all should be well. Then, make sure you remove your custom recovery prior to accepting the OTA.

---------- Post added at 07:44 AM ---------- Previous post was at 07:42 AM ----------

Another method you could do would be to heavily modify the updater-script within the OTA. Removing the checks should suffice and thereby allow you to install the OTA via your custom recovery but it is easier said than done lol. A lot of lines to go through.
[One (M8) Q&A, Help & Troubleshooting] winnower:
Ok, I need to do a bit of reading it seems.

I installed TWRP and SuperSu, but didn't modify my CID or get S-OFF (yet). I have a Bell Mobility version if that helps.

Thanks, I kinda figured the backup wouldn't help.

I would at least like to be able to restore the /data partition to keep my apps and such. I assume the /data backup I made after ****ing this thing up will not work for restoring /system files, but my data does matter to me.

I looked into the OTA zip file and found a /firmware.zip/recovery.img file. Will that recovery image work?
[One (M8) Q&A, Help & Troubleshooting] hdorius:
Just use the command "fastboot getvar all" it will read your CID and find the backup at Stock Nandroid Backup that match your phone and restore it

Edit: oops the thread that i linked is closed and all the links are removed
[One (M8) Q&A, Help & Troubleshooting] Modding.MyMind:
The recovery image is based for the new OTA. Won't necessarily be the same as what your device currently used but it should still work. If by any chance it does not then it is because of the Bootloader version you are currently running which is causing the problem. Which at that point you will need to grab the other stock recovery.img prior to the update.

---------- Post added at 09:56 AM ---------- Previous post was at 09:55 AM ----------

I don't have your device so I can't really provide any links to assist even further but I ca build you a foundation to go off of. The logic with this stuff is relatively universal across common android devices for the most part.
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
Since you have the OTA, can you put the details of android-info.txt that you have inside it ?? This will definitely help you to find the right recovery/backup.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Have you actually seen this done? AFAIK stock recovery is required to install OTA; but perhaps I'm mistaken. In any case, its far easier to restore stock recovery if the intent is to install OTA. However, the current installed ROM must also have no system files altered, as this is also a requirement for OTA installation.

Another (probably easiest) way out of this loop would be to mount the memory, find the OTA file and delete it. The phone should then stop trying to find stock recovery to install the OTA (which is the cause of the bootloop).
[One (M8) Q&A, Help & Troubleshooting] Modding.MyMind:
[MENTION=660462]redpoint73[/MENTION], that is a valid question to ask. I have not seen any guides made available to the public however, I can vouch it works. I once did it myself many many many months ago once I did some extensive studies on how an OTA was applied. Though, I won't hesitate to mention that it's a tedious process and I wouldn't recommend it less it were your only absolute option since there are so many easier methods to use.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Good to know, thanks for the explanation. Interesting that custom recovery will actually work (technically) with an OTA, that its just security checks that keep if from happening.

As you mentioned, there are many much easier options to recovery; so what you mentioned is just a method of "last resort".
[One (M8) Q&A, Help & Troubleshooting] winnower:
OTAfile/firmware.xip/android-info.txt:

modelid: 0P6B16000

cidnum: BM___001

cidnum: SASKT001

mainver: 2.23.666.2

btype:1

aareport:1

hbootpreupdate:12
[One (M8) Q&A, Help & Troubleshooting] winnower:
Ok, downloaded fastboot-win.zip from HTC's dev site.

C:\Android\m8>fastboot getvar cid

cid: BM___001

finished. total time: 0.000s

So, if those links are offline, do you have another source or just use the one I got with the OTA?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Did you try to just find the OTA file and delete it, as I previously suggested? This should get the bootloop to stop.
[One (M8) Q&A, Help & Troubleshooting] winnower:
Yes, the OTA is no longer on the phone.

It's not really "bootlooping", it boots normally into the Sense launcher, then after about a minute it restarts. It's not stuck on the HTC logo or anything; it's more like a restart-cycle.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Were you on a stock ROM, or custom before this OTA mess started? My recommendation would just be to pick a custom ROM of your choice on the phone (either via adb push or on the removable SD) and flash it in TWRP and forget this OTA business. Making it more complicated than it needs to be, and OTAs don't really have any business on modded phones anyway, for the most part.
[One (M8) Q&A, Help & Troubleshooting] winnower:
I was on stock Sense6. I had previously unlocked and loaded TWRP since I assumed I'd switch ROMs very shortly after getting the phone. I was coming from Samsung's world where running my own ROM was mandatory since TouchWiz was so awful.

The only thing keeping me from flashing a custom ROM right now is my data/apps. In my sleep deprived state, I didn't think to make a backup (or to not accept the OTA in the first place). If I can flash a customized Sense6 ROM and keep my apps/data then I will.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
The phone isn't really working for more than a minute or so. So I'd just do a wipe and install a custom ROM. Something is broken now, so a clean slate is probably your best bet.
[One (M8) Q&A, Help & Troubleshooting] winnower:
Yeah, I'm just trying a few last things.

I tried flashing the newest TWRP and the stock recovery.img I got with the OTA; no luck.

I still have the full OTA zip though... Is there any way for me to adb push that file on the /sdcard/ to force it to complete the update? That way I can just re-flash TWRP and SuperSu and keep my data.

Thanks for all the help.
[One (M8) Q&A, Help & Troubleshooting] Keithn:
Pull your /data/data, its where your app data is stored. You should be able to put what you want back after reinstalling your apps. If you have enough time to do it using titanium backup might be easier. Also you can set titanium backup to do backups on a schedule which could help you in a situation like this in the future.

Sent from my One M8
[One (M8) Q&A, Help & Troubleshooting] exocetdj:
just wondering of maybe, flashing stock recovery then manually applying OTA via stock recovery would work? or would the rom on the system be corrupted by TWRP trying to apply the update?
[One (M8) Q&A, Help & Troubleshooting] winnower:
TWRP didn't do anything... it just loaded up and I rebooted after my brain reminded me that I am dim.

Found this link for applying the OTA zip manually (using method 1):

http://android-revolution-hd.blogspot.ca/2013/12/how-to-manually-install-ota-update.html

Obviously not exactly the same, but a small modification to step 6 (copy the OTA to /sdcard/update.zip) should work right?

Is there a better/safer method?
[One (M8) Q&A, Help & Troubleshooting] exocetdj:
that guide should work ok in normal circumstances. you could try and install the stock recovery and then flash the ota using the guide. failing that, the best way would be to reflash a custom recovery then rom and start from fresh
[One (M8) Q&A, Help & Troubleshooting] winnower:
Well, it didn't work.

The phone sat on the boot screen for about 3 minutes, then rebooted back to the launcher; Settings still showed 4.4.2. Then about a minute later; restart.

Ok, I've made backups of as much as I can (SMS, apps, photos)... I will re-load TWRP, do a full wipe, then install a custom ROM. I wish I didn't have to go through all this hassle.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
There are certainly ways to "manually" install an OTA, but I'm not that versed in it. Try some searching around, I know its been discussed.
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
Why don't you start over ?

1. Get the backup for 1.55.666.4 from http://xdaforums.com/showthread.php?t=2701376

2. restore that backup

3. flash STOCK RECOVERY 1.55.666.4 also downloadable from that link above

4. reboot and do OTA up to the latest 2.23.666.2

Note : no need to relock bootloader
[One (M8) Q&A, Help & Troubleshooting] winnower:
Success!

Reflashed SuperSU binary.

The delay in the restart cycle was what tipped me off that it wasn't /system level. My adblocker waits a few moments after boot before applying the filters; when it tried to get root permission, that's when the reboot happened.

Updating my first post as well so future visitors can see my solution.
[One (M8) Q&A, Help & Troubleshooting] RockStar2005:
Hello all,

So here's why I'm posting:

I'm having an issue with my T-Mobile HTC One M8 phone. The phone was working great until I tried to install a new third-party TWRP. I don't know if it was miscommunication or what, but in the process of installing it (https://www.dropbox.com/s/ocvavpttfo...ersion_Fix.img), the phone started having issues.

The initial issue was that the phone would get stuck during boot up. The phone was at the current 2.22 build # but in order to make it at least usable again, I flashed an RUU (1.57 build #) and that seemed to fix everything. But then when I went back from stock recovery to my original TWRP, and flashed a recent backup, the phone froze again during boot up. This process worked many times and as recently as yesterday, but now since trying to install that third-party TWRP, it doesn't. I've tried various things but nothing is working. I know that since I can still reach HBOOT and TWRP that there is hope, but I'm at my wits end as to what to do.

I should also mention that I was using the ViperOne M8 ROM (2.1.0). My phone is unlocked/rooted & S-OFF. There were no issues with it again until I tried to install that new TWRP.

I really love my phone, and hope someone on here can help me. After re-RUUing my phone, I'm going to leave it at 1.57 build # and stock recovery (1.12 #) (and USB Debugging on) until I hear from someone. Basically, I just want my phone to be normal again so I can upgrade back to build # 2.22, flash my custom TWRP recovery, and then flash my most recent backup which included the most recent ViperOne M8 update.

Other info you might want:

C:\adb>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.16.0.0000

(bootloader) version-baseband: 1.16.21331931.LA24G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.57.531.7

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno:

(bootloader) imei:

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B13000

(bootloader) cidnum: T-MOB010

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: c3d94491

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.016s

Thank You,

RockStar2005
[Galaxy S 5 Q&A, Help & Troubleshooting] Reechings:
Hi,

I have some photos on my phone that were not taken with my S5 and am finding that when I go to view them with the Gallery app that it is adjusting the color (and not in a good way). The app will momentarily show the proper color when opening the pic and closing it but will kind of whiten it when viewing. The pics look normal using quickpic and the google photos app. Just wondering if anyone else has this happening and if there is any way of turning it off before I try clearing the data for the Gallery app etc.

Thanks!

Tapped It!
[Galaxy S 5 Q&A, Help & Troubleshooting] nbetcher:
Hello,

It's not actually modifying the photo, it is using a Samsung technology to change the colors being displayed on the screen only. You can change your preference (but it appears not shut it off) by going into your Settings, then Display, then 'Screen mode'. But again, your photos aren't modified.
[Galaxy S 5 Q&A, Help & Troubleshooting] Reechings:
Thanks for your help. I did realize that it wasn't actually modifying the photos, I just really didn't like how it made the pictures look. You were totally right with your solution, I changed the display mode to Standard and it works properly now. I was using Adapt Display because I wanted the best sunlight legibility/brightness possible and everything had looked great until I noticed this issue. Thanks!

Tapped It!
[LG Optimus G Pro] alayton09:
This is VERY good work! THANK YOU!
[G Pad 8.3 Q&A, Help & Troubleshooting] Xenosis:
I rooted as per the instructions here: http://xdaforums.com/showthread.php?t=2554121

(I used method 2 to root)

I downloaded the latest awifi twrp 2.7.1.0 and flashed using flashify.

I tested TWRP by backing up the current rom and wiping and restoring it (works perfectly)

So far I have tried to flash a cyanogenmod snapshot CM11 M9 for the v500 and it fails as it says in the title claiming the device is a palman or afaik a v510.

I checked the software/hardware sections of the device and its listed as a LG-V500 & V50010a.

It's definitely not a GPE stock rom as it came loaded with tons of LG stuff.

Build number : JDQ39B

Android : 4.2.2

Kernel : 3.4.0
[G Pad 8.3 Q&A, Help & Troubleshooting] Xenosis:
Solved - need to use this version: http://xdaforums.com/showthread.php?t=2641409

2.6.3.2 instead of latest.
[One (M8) Q&A, Help & Troubleshooting] Rye Cribby Tree:
Any time I try to flash a rom that is sense based my phone instead of booting like a normal phone it boots to the HTC screen then restarts and boots into TWRP. Anyone know of a fix? I tried to wipe system, data, cache and dalvik cache but nothing works.

EDIT: When I try to install the stock rom it says some symlinks failed and error executing updater binary in zip
[One (M8) Q&A, Help & Troubleshooting] syaoran68:
are you using a GPE phone if you are the partitions are a bit different and you have to go through the process of converting your phone.
[One (M8) Q&A, Help & Troubleshooting] Rye Cribby Tree:
It is from ATT, it had sense stock but I accidentally formatted the entire phone now my hboot screen looks different. it is black with a droid in the middle instead of white with the droids on skateboards. and the splash screen has a small black unlocked lock at the bottom instead of the normal htc splash.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
What did you do to "format" it?
[One (M8) Q&A, Help & Troubleshooting] Rye Cribby Tree:
I ticked all the boxes in twrp and deleted everything.
[One (M8) Q&A, Help & Troubleshooting] BenPope:
I think you installed a GPE firmware, you'll need to find a rolled up (rather than an OTA) Sense firmware for your device. I take it you're S-Off?
[One (M8) Q&A, Help & Troubleshooting] Rye Cribby Tree:
Nah, firewater doesn't work for me unfortunately.
[One (M8) Q&A, Help & Troubleshooting] BenPope:
I don't know what's going on. Unless I'm mistaken, that sounds like the GPE boot screen, which you could only flash if you're S-Off.
[One (M8) Q&A, Help & Troubleshooting] Rye Cribby Tree:
I can flash GPE roms fine. :eek:
[One (M8) Q&A, Help & Troubleshooting] BenPope:
My point is that as far as I know, the splash screen is in the firmware. You would need to be S-Off to flash that firmware. Anyway, I can't help.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
If that is in fact the GPEboot splash (I'm not that familiar with GPE) you should still be able to get into bootloader, you might just be doing the button combo wrong. Nothing you wiped affects hboot; nor can it be overwritten with s-on (aside from a signed hboot for your version).

Hold down the Power and vol up button to force the phone to reboot. The

moment

the screen goes dark, let go of vol up, and hold vol down until you see the hboot screen. If you see any screen but the white hboot screen, you probably just pressed vol down too late, or let go of it too early.

Or adb reboot bootloader.
[One (M8) Q&A, Help & Troubleshooting] Rye Cribby Tree:
This is what it looks like. But it use to look like this
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Wow, strange. As I mentioned, I'm not that familiar with GPE, but it must have a different hboot (not a splash screen like the other responses was suggesting). You shouldn't be able to change hboot with s-on.

So did you try to do a GPE conversion? As I mentioned, nothing in TWRP could have caused this.

This also explains why you can't install/boot Sense ROMs. As another mentioned, the GPE partitioning is different, so that prevents Sense ROMs from running.

What version/carrier do you have?
[One (M8) Q&A, Help & Troubleshooting] Rye Cribby Tree:
AT&T, I flashed a stock recovery to try and get OTA's from a GPE rom and it soft bricked my phone. After that all the changes happened. Also the splash screen when you first boot the phone has a small unlocked lock picture at the bottom. It looks like this but under powered by android is a little lock.
[One (M8) Q&A, Help & Troubleshooting] Rye Cribby Tree:
Yeah, I was just talking about the image on the phone.
[One (M8) Q&A, Help & Troubleshooting] fromeo85:
I am in the same boat as the OP. Did the GPE conversion with S-On somehow and here I am stuck with GPe and AOSP ROMs only :eek:
[One (M8) Q&A, Help & Troubleshooting] KuroTheBang:
The Colorscene is nothing to worry. GPE-HTC phones have always been black (Black Hboot = GPE; White = HTC)

Have you tried to use a superCID and flash the first one (iirc 1.54...)Rom? Got that working on my old M7

[MENTION=467786]fromeo85[/MENTION], how was you able to convert your device to GPE with S-On? I mean, you have to change the CID to GOOGL001, which obviously just works if you are S-Off
[One (M8) Q&A, Help & Troubleshooting] alsoscott:
I'm pretty much in the same boat as a few others here - except I know exactly where I went wrong and learned a valuable lesson.....

Before I started all this, I had S-OFF, Root and running ViperOne on my M8

Wanted to try out a AOSP Rom and used a 4.4.3 GPE ROM, which flashed successfully (not sure how, it shouldn't have).

Once the M8 was running 4.4.3 GPE, it prompted for an update to 4.4.4 which I accepted. The update failed and booted into TWRP instead. I was overly determined to get 4.4.4 installed (should have left it alone at this point instead)

I rebooted into bootloader and very very stupidly, flashed the GPE recovery, rebooted and accepted the install to 4.4.4.

This boot looped my phone, corrupted internal storage, and reapplied security (S-On).

I was able to get internal storage cleared up and successfully installed CM11 so at least I'm booting something and its not bricked.

At this point, I'm back to a bootable state with CM11 - but can't return to Sense. I've tried to install InsertCoin and ViperOne - both fail towards the end of installation - writing permissions and installing busybox - same with restoring ROM via recovery. Also, the original GPE ROM fails installation, but doesn't give any errors.

I've tried to S-Off with revone, firewater, SunShine and rumrunner - all fail. I need S-Off to get HBoot back to a version that can boot Sense or open up security so a Sense based ROM can install successfully. Also tried to SuperCID, which requires S-OFF so that fails as well.

So I'm stuck with:

- S-On

- version-bootloader: 3.18.0.0000

- version-baseband: 1.14.21331931.LA02_2G

- modelid: 0P6B13000

- cidnum: T-MOB010

I've tried flashing current (and previous versions) stock Firmware and using different versions of RUU but all fail with hboot version check failed and S-On. Flashing GPE 4.4.x (4.4.3 and 4.4.4) firmware fail as well but cant remember the exact error off the top of my head.

I'm at a loss.. Over the years I've read plenty of tutorials and have a pretty decent understanding of the Android ROM ecosystem. I've searched all over to no avail. If the GPE Recovery and/or 4.4.4 Update would have left Security Off, I wouldn't have any issues since I could flash firmware or HBoot and install ViperOne or any other Sense based ROMs....

I've been racking my brain trying to fix this for 2 days now so I've come here for a bit of help... I've tried to list all my troubleshooting steps in here, but I know I've missed some

Any ideas?? One thing that would really come in handy right now is one of the several S-Off methods to work on AOSP Roms.
[One (M8) Q&A, Help & Troubleshooting] fromeo85:
[MENTION=5994443]CorzCorry[/MENTION] I am not entirely sure but I ended up using Sunshine to gain S-Off when I was on the stock GPE ROM and everything is golden now. Though I am sticking with GPE since I prefer a vanilla experience over any OEM UI overlay.
[Android Q&A, Help & Troubleshooting] Ragan:
Okay,

So I'm very new to this, so I apologize if the answers I seek may be found in an obvious place. However, I recently got my replacement LG G FLEX from my insurance claim. I was wondering if there was a way to restore my phone to a mirror image of my original device, perhaps via some sort of GOOGLE application or account setting. In other words is there a way to replicate how iCloud functions, but the GOOGLE way? =)

Best regards and Maaanyyy many thanks!

Ragan
[T-Mobile HTC One (M8)] billydroid:
Do I have to s-off to flash the Ota? Just go go to stock 1.57 w/ stock recovery. Then just put it on the root of my sdcard and boot into fastboot and let it update right? Since it's a tmobile update and the Id matches. Have have not done it this way in a really long time
[T-Mobile HTC One (M8)] sapplegater:
You don't need S-off for this all you need to have is a complete stock ROM including the file that bootloader unlock deletes (if you've unlocked bootloader) and the stock recovery. And the easiest way to flash it is going to be to put the OTA on the root of your internal storage boot into stock recovery and when you see just an image of a phone hold the power button and then press up on the volume key and it will give you the option to install from internal storage. (It may be power and volume down if up doesn't work.)