yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] gdpaull:
Theoretically, downloading and flashing this will work? It says not rooted...does that mean I'll just have to re-root, but I'll be back to the stock ROM?

TMOUS_1.27.531.11_Stock_Odex_Not_Rooted_m7_signed_072813.zip

952.9MB Jul 28, 2013 | 04:23PM

---------- Post added at 01:37 PM ---------- Previous post was at 01:34 PM ----------

Thanks! So, I'm downloading the HTC One T-Mobile zip from there. Just flash with TWRP as normal, and I'll be back to the way my phone originally came, with stock recovery, able to get OTA updates, etc??
[One (M7) Original Android Development] zelendel:
I honestly dont know. I dont do OTA. But I doubt it as you have to be completely stock to get OTA, so your best bet would be to run the RUU which also means you will lose root. So you will have to reroot.
[One (M7) Original Android Development] gdpaull:
I see. Re-rooting is really the least of my problems right now. I'm starting to think that getting S-Off and flashing an updated firmware may make more sense than trying to successfully revert to stock to get the OTA firmware update, and then try to get back to 5.0. Of course getting S-Off on 5.0 is nothing but a headache so far.
[One (M7) Original Android Development] zelendel:
YEah I would flash one of the 4.4 RUU and then get S-off ($25 I know it sucks main reason this is my last HTC unless it is changed) then flash a 5.0 update.
[One (M7) Original Android Development] gdpaull:
Oh, for real? There's no way around having to pay for S-Off at this point?? Thanks for the advice on the RUU...now I'll have to learn the whole adb flashboot process :) I had the original Galaxy S...amazing how simple it was to tinker on that. I feel like even Sheldon Cooper would need a hand in this. :laugh:
[One (M7) Original Android Development] zelendel:
Yeah no way around it at the moment. I have the Galaxy S as well and to be honest the only other one that was that good was the s2. After that Samsung made the IMEI on an erasable partition so that some roms erased it when flashed and then you were SOL without sending it back.
[One (M7) Original Android Development] gdpaull:
Funny, I actually erased the IMEI on my Galaxy S, went out and bought the S2 (after I dried my tears), but through the magic of ODIN, somehow my IMEI was restored, and the S2 went back to the store the next day. I'd still use the Galaxy S today if the hardware kept up with software.

Anyway, it looks then, like my best best here (without spending money), is to figure out how to revert to stock T-Mobile, hope for the OTA update and official 5.0 push that came out this week, and then get CM12 back. I guess the big question now, is how much am I willing to risk to get my GPS working again on an otherwise flawless ROM. I'd hate to have this be the reason I brick, and have to go out and drop $600 on a new device. I may as well just buy a cheap $75 GPS for the car and call it a day.

Again, thank you (and everyone) for the help.

EDIT: Am I really still the only T-MO user who lost GPS with this? My wi-fi seems ok, but the damn GPS!!!!!!
[One (M7) Original Android Development] zelendel:
Even if you go back to stock and then come back to CM you will face the same issues. CM will never compare to OEM based roms on some things like GPS and others. This is just the nature of different drivers and such. You shouldnt have to much issues going back to stock. HTC are kinda hard to brick really. As long as you make sure to do the needed reading.
[One (M7) Original Android Development] gdpaull:
Oh, ok. I was under the impression that once I updated the firmware with the OTA update, that would be the fix. Maybe I'm wrong about that.

Ok, now to research the revert...I step forward, 2 steps back.
[One (M7) Original Android Development] gdpaull:
OK...I think I have to concept down after doing some research on how to revert back to stock...but here's my question. As far as RUUs go for T-Mobile, I'm finding some that I can't decipher between.

One site had the following--I assume I need to find the one that matches my radio, but where can I see which radio model I'm using.

RUU Zip M7 UL JB 50 TMOUS 1.27.531.11 Radio 4A.17.3250.20 10.40.1150.04 Release 324846 Signed - (Decrypted by crushalot)

RUU Zip M7 UL JB43 SENSE50 MR TMOUS 3.24.531.3 Radio 4A.21.3263.03 10.38m.1157.04 Release 336982 Signed 2 Decrypted - (Decrypted by crushalot)

Also, on the HTC official site, they have the latest RUU with the latest firmware. Can I install that one off the bat, or do I need to revert all the way back to the original, and then upgrade from there? Which brings me back to my first question...how can I know exactly which RUU I need? In the bootloader, it says RADIO-4T.27.3218.14. So, do I need to specifically find an RUU that matches that, or is that the radio model for CM12?? I think once I get the RUU, I'm ready to go. I would just hate to brick at this point simply by having the wrong RUU file.
[One (M7) Original Android Development] gdpaull:
.....and I think I'm bricked....can't seem to get back to bootloader menu...trying to get to recovery just bootloops the Teamwin logo...am I F'd? Originally, I was able to get the whole fastboot set up on the computer, so that part maybe is promising...yet, I don't think there's any way to get back into fastboot on the phone now that I can't get into the bootloader, and recovery just keeps looping, right?

---------- Post added at 09:29 PM ---------- Previous post was at 09:01 PM ----------

Welp, it was fun while it lasted...off to T-Mobile tomorrow for something new...didn't even make it 2 years.

Any recommendations on a 2nd best phone behind the M7?
[One (M7) Original Android Development] zelendel:
If you can get into recovery then your not bricked.
[One (M7) Original Android Development] Cheeky_Fink:
Has Tap & Pay been removed from CyanogenMod? I tried to use it earlier for the first time since I switched from ViperOne, no dice. So I went into Google Wallet thinking it deactivated when I upgraded, and there's no option for it. Then I checked the NFC settings, and there's no longer a Tap & Pay thing in there either.
[One (M7) Original Android Development] gdpaull:
Right, but I can't get into recovery. The TeamWin logo just bootloops forever...doesn't actually let me into recovery mode.
[One (M7) Original Android Development] Leebert225:
Lock Screen

I setup a screen lock using the swipe and PIN method yesterday and it was working fine. I woke up this morning and went to enter my PIN and the device says its the wrong PIN which is not the case.

Actually when you type in the PIN the characters are not appearing in the field as they should so the device thinks a PIN was not entered.

So as of right now I'm locked out of my device.

Has anyone else seen this or know of a fix?
[One (M7) Original Android Development] gdpaull:
For those of you keeping track...

I talked to HTC today, and I sent my phone in for HOPEFULLY a repair. They know it was my fault, so obviously all costs will be on me. Hopefully, it can be repaired to brand new for under $100...sucks, but it's certainly a better option than a brand new phone right now...currently back to my wife's old S2 (perhaps until the Galaxy S6 is out...)
[One (M7) Original Android Development] MajorGaz:
Where you able to get into the bootloader section (where you select to go into recovery)?

If so, you may have been able to run the recovery img from there using adb and fastboot

Then you might have been able to flash the T-Mobile RUU that just came out (http://www.htc.com/us/support/htc-one-t-mobile/news/), however i have never flashed an RUU before (only firmware using the above method)

At any rate, hopefully it all works out.
[One (M7) Original Android Development] gdpaull:
Nope, couldn't get into bootloader, and believe me, I tried for quite a while... all I could do was get the TWRP logo in an infitine bootloop. If HTC is able to fix the phone, I'll post my results here, in case any of you may be in the same boat. I took a calculated risk, and I lost the good fight... tinkered a bit too much this time.
[One (M7) Original Android Development] MajorGaz:
How did you get into recovery without going into the bootloader (hold down power+volume down)?

I thought you had to get to that menu to get to recovery?
[One (M7) Original Android Development] gdpaull:
Somehow when I tried to get to the bootloader with the power and volume method, it bypassed it and went right to the TWRP logo...I couldn't actually get into recovery (I wish I could have!), but rather just a bootloop of the TWRP recovery logo.

So, no way to flash anything via recovery, and no way to get the phone into fastboot with the computer commands.
[One (M7) Original Android Development] MajorGaz:
Very odd.

At any rate hopefully HTC fixes your phone without too much issue :) :good:
[One (M7) Original Android Development] gdpaull:
Hope so...even if it's $100 or so, I'll be happy to have my M7 back, and I can then just update to 5.0 with the newly-released OTA update.

Basically, I used fastboot to relock the bootloader, but I didn't flash an RUU right away...I'm sure there's more to it that I can't explain, but I lost any chance of getting back into bootloader or recovery. If HTC cannot fix it, they're going to send it back to me at no extra labor charge. If one of you wants to have a go at it for a few bucks, I can send it your way!
[One (M7) Original Android Development] MajorGaz:
Fair enough.

Very odd that the bootloader menu disappeared and all that was left was your phone booting into recovery and then restarting again.

I thought the bootloader couldnt be altered or removed without S-OFF.

Would be interested to know how it happened so i can avoid doing the same thing.
[One (M7) Original Android Development] gdpaull:
Yeah, I wish I could remember exactly at what point my night got ruined, but I'm not exactly sure at which step. I'm not sure if I could necessarily say the phone booted into recovery per se....Maybe it's possible that the main recovery boot logo somehow was almost seen by the phone as being the main boot up image or something? I wouldn't really say the phone was booting into recovery, because it really was just looping the initial logo. When I tried to start the phone regularly, it'd give me the white HTC screen, but then that'd keep looping as well. It just seemed like the phone wasn't sure where to go after that point, ya know?
[One (M7) Original Android Development] MajorGaz:
Ok that makes a bit more sense.

If it wasnt booting into TWRP or CWM then rebooting then it means it was just boot looping.

Shame you couldnt get to the bootloader :(
[One (M7) Original Android Development] kevace1:
Are bug reports being followed here? When you enable the circle battery in options and want to select the "text in the icon" option, it still does not do it. It puts the percent next to the icon. Anyone else experience this in the latest nightly? Also, when a call comes in sometimes when the phone is asleep, it will just come on for a second and then turn right back off not allowing me to pick up the phone. I would have to press the power button to turn the screen back on, sometimes 2 or 3 times so that I may slide to pick up. I'm on the latest 12-20150311 nightly
[One (M7) Original Android Development] gdpaull:
Yep, exactly. It kept giving the false hope of booting into recovery, and at the last second saying, "nah, just F'ing with you, n00b!"

I figured it can't hurt to send to HTC...worse-case is they send it back and it just cost me $5 in shipping (plus $700 for the new Galaxy S6 :D). Best case is I get my phone back with brand new software for $100 or so.
[One (M7) Original Android Development] Leebert225:
I think the first part only happens when you are charging because it puts the lightning bolt inside the circle. When you unplug the device the percentage will be inside the circle.

I don't experience the second part of your question.
[One (M7) Original Android Development] Gravityrat:
I have a TMO HTC One M7 with CM 12 and about once a day it will completely lock up and nothing works, can't even reboot. I have to wait for the battery goes dead and then restart it. Also it acts strange when trying to play YouTube videos, does not like too play full screen. I am currently on the march 2 nightly. Any advice would be greatly appreciated.
[One (M7) Original Android Development] Cheeky_Fink:
I experience the battery thing when charging, but that's it. As far as the screen turning off, I've been experiencing the same thing and it seems to me that it's activating the proximity sensor before the call is answered.
[One (M7) Original Android Development] genseng:
Hold volume down and power buttons until the screen turns off or until it goes to the bootloader screen. No need to wait for the battery.

I'm curious; are you running a custom kernel?
[One (M7) Original Android Development] Gravityrat:
Volume down with power button doesn't work either.

Oh and can anyone tell me what the star and pound sign in the notification bar next to my signal strength indicator mean.
[One (M7) Original Android Development] Cheeky_Fink:
No matter what mine is doing, holding down just the power button for about 15-20 seconds will shut it down. That's in bootup, system, recovery, or bootloader, whether it's frozen or not. Have you tried that?

I believe pound sign means something is accessing root, it went away after I switched to SuperSU instead of using the built-in SU. Dunno what the star is tho.
[One (M7) Original Android Development] 9Lukas5:
Hey I get more and more random reboots atm. Could someone check my last_kmsg what's the problem?

https://www.dropbox.com/s/1ebmu1h95uxhbvx/2015-03-13_last_kmsg?dl=0

Thanks in advance,

L

Gesendet von meinem One mit Tapatalk
[One (M7) Original Android Development] kevace1:
OK yeah that was it. But now another bug here to report....I cannot start a new SMS conversation from the stock messaging app. I press the plus sign at the bottom, and the second in pick someone from the contact list, it force closes. The only way to start a new conversation is by going to the contacts app and selecting the contact and pressing the message icon....
[One (M7) Original Android Development] emrekys:
Hey lads Im new here and I never rooted or flashed a phone ever before. For what it is im a noob and have two questions.

Since a few days I rooted my HTC one m7 and used the latest twrp recovery. Do i need a newer one and why cant the current one do the job ?

Also the boot img where do i find that and can i put it in the same fastboot folder as I used for rooting my phone ?

Thanks in advance for your replies.
[One (M7) Original Android Development] kbal:
boot.img is inside rom zip.

You flash it with:

fastboot flash boot boot.img
[One (M7) Original Android Development] mgutierrez218:
Tap and Pay

Hey all. I am running the nightly build from 20150228 and realized Tap and Pay is not part of my settings. Is that normal?

This is my first time using CyanogenMod on my HTC One and wanted to still use Google Wallet Tap and Pay like I previosuly did with Stock.

Thank you.
[One (M7) Original Android Development] dc66:
Unofficial TWRP 2.8.5.6 is out: http://mdmower.cmphys.com/twrp-m7/

Just tested it... Great! It solves the data decryption issue. Back to a fully usable recovery allowing backups, restore and flash with files from data :)
[One (M7) Original Android Development] ByHarry02:
i don't like this cm12. But i really like cm12 dialer+contacts+messenger+clock apps. i really want it. can we install this apps to another rom? Please i want it so much
[One (M7) Original Android Development] gdpaull:
For those following my uber-excited case, HTC is going to fix my phone for $90. They told me that the $90 is a GUARANTEE that it will be fixed, not a "$90 for labor to tell me it's totally borked fee". I'll let you all know how it is when I get it back (so you can sleep at night and stop wondering!). :good:
[One (M7) Original Android Development] elherr:
Tap & Pay does not work with AOSP NFC NXP.
[One (M7) Original Android Development] MajorGaz:
Anyone getting bluetooth audio pops and skips?

Only started to happen in the lastest few nightlies
[One (M7) Original Android Development] Cottaer:
I'm haveing issues with the camera. I'm on the nightly from 28.02.2015. It didn't happen the first days I was using the rom, but started, when I deinstalled Google Goggles (it did seam to me, this was preventing my phone from sleep). I'm not sure, if this is just coincidence, but as this app also uses the camera...

Sometimes I can take several pictures, sometimes just one. Sometimes it says, the camera app crashed and I can still work with the phone (but not the camera), sometimes the phone reboots when using the camera.
[One (M7) Original Android Development] mrtarrouk:
Although "Vibrate on Call Waiting" is a good feature added to this ROM, but it is not working with me, anyone knows what might be the reason?
[One (M7) Original Android Development] debianmain1:
The camera lockup/reboot is a known issue with CM12--It's slightly better with Google Camera (look here: http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900 for the gapps), but still has problems--no real answers to the issue yet.... Take a look back a few pages in this thread for the discussion...
[One (M7) Original Android Development] sa_ma:
Hi,

for the crash of the camera ,

do you also have this when you look at the last_kmsg ?

[ 0.186950] ------------[ cut here ]------------
[ 0.187011] WARNING: at /home/sami/android/system_12/kernel/htc/msm8960/arch/arm/mach-msm/cache_erp.c:455 msm_l2_erp_irq+0x1d0/0x24c()
[ 0.187042] L2 master port error detected[<c010aee8>] (unwind_backtrace+0x0/0xe0) from [<c0180ea4>] (warn_slowpath_common+0x48/0x60)
[ 0.187133] [<c0180ea4>] (warn_slowpath_common+0x48/0x60) from [<c0180f14>] (warn_slowpath_fmt+0x2c/0x3c)
[ 0.187194] [<c0180f14>] (warn_slowpath_fmt+0x2c/0x3c) from [<c017d100>] (msm_l2_erp_irq+0x1d0/0x24c)
[ 0.187225] [<c017d100>] (msm_l2_erp_irq+0x1d0/0x24c) from [<c01d62a8>] (handle_irq_event_percpu+0xbc/0x2a0)
[ 0.187286] [<c01d62a8>] (handle_irq_event_percpu+0xbc/0x2a0) from [<c01d64c8>] (handle_irq_event+0x3c/0x5c)
[ 0.187347] [<c01d64c8>] (handle_irq_event+0x3c/0x5c) from [<c01d8c80>] (handle_fasteoi_irq+0xd8/0x124)
[ 0.187377] [<c01d8c80>] (handle_fasteoi_irq+0xd8/0x124) from [<c01d5c5c>] (generic_handle_irq+0x20/0x30)
[ 0.187438] [<c01d5c5c>] (generic_handle_irq+0x20/0x30) from [<c0106288>] (handle_IRQ+0x80/0xb8)
[ 0.187500] [<c0106288>] (handle_IRQ+0x80/0xb8) from [<c010041c>] (gic_handle_irq+0x94/0x110)
[ 0.187530] [<c010041c>] (gic_handle_irq+0x94/0x110) from [<c0105580>] (__irq_svc+0x40/0x74)
[ 0.187561] Exception stack(0xc003fe50 to 0xc003fe98)
[ 0.187591] fe40: c0d45c18 60000013 00060006 00010000
[ 0.187622] fe60: c0d45bc0 e8fa3600 00000022 00000022 c0d45c18 60000013 c0d45bf0 00000000
[ 0.187652] fe80: 00000000 c003fe98 c01d76f4 c08943c8 60000013 ffffffff
[ 0.187713] [<c0105580>] (__irq_svc+0x40/0x74) from [<c08943c8>] (_raw_spin_unlock_irqrestore+0x28/0x5c)
[ 0.187774] [<c08943c8>] (_raw_spin_unlock_irqrestore+0x28/0x5c) from [<c01d76f4>] (__setup_irq+0x290/0x360)
[ 0.187805] [<c01d76f4>] (__setup_irq+0x290/0x360) from [<c01d7a98>] (request_threaded_irq+0xe0/0x12c)
[ 0.187866] [<c01d7a98>] (request_threaded_irq+0xe0/0x12c) from [<c017d3f0>] (msm_cache_erp_probe+0xa4/0x1bc)
[ 0.187927] [<c017d3f0>] (msm_cache_erp_probe+0xa4/0x1bc) from [<c0449690>] (platform_drv_probe+0x14/0x18)
[ 0.187957] [<c0449690>] (platform_drv_probe+0x14/0x18) from [<c04484b4>] (driver_probe_device+0xc8/0x208)
[ 0.188018] [<c04484b4>] (driver_probe_device+0xc8/0x208) from [<c04486a0>] (__driver_attach+0x68/0x8c)
[ 0.188079] [<c04486a0>] (__driver_attach+0x68/0x8c) from [<c0446ee0>] (bus_for_each_dev+0x70/0x84)
[ 0.188110] [<c0446ee0>] (bus_for_each_dev+0x70/0x84) from [<c04475ec>] (bus_add_driver+0xe0/0x224)
[ 0.188171] [<c04475ec>] (bus_add_driver+0xe0/0x224) from [<c0448e08>] (driver_register+0x9c/0x114)
[ 0.188232] [<c0448e08>] (driver_register+0x9c/0x114) from [<c0c00afc>] (do_one_initcall+0x8c/0x150)
[ 0.188262] [<c0c00afc>] (do_one_initcall+0x8c/0x150) from [<c0c00cc4>] (kernel_init+0x104/0x1c0)
[ 0.188323] [<c0c00cc4>] (kernel_init+0x104/0x1c0) from [<c01064a8>] (kernel_thread_exit+0x0/0x8)
[ 0.188385] ---[ end trace 70a9a79682adc558 ]---
[One (M7) Original Android Development] Cottaer:
It seems to me, I have the same. Anyway, I uploaded a full log of last kernel message here:

https://www.dropbox.com/s/8hsccicwtkx4ix3/kernel_last_message2.txt?dl=0

This was produced rebooting the device, starting the camera, taking a several pictures within short time -> reboot; and then I saved the log. I hope it helps.

Is there any way to prevent this bug when using the camera?
[One (M7) Original Android Development] TachyOS:
I'm not sure but the battery drainage is hardcore than CM11

Anyone experience ?
[One (M7) Original Android Development] waldaz:
yes battery is nightmare for me as well. plus camera seems will never work :(
[One (M7) Original Android Development] jpyumul:
Speaking of battery, how to turn off the freaking low battery sound!!! Annoying!!!
[One (M7) Original Android Development] Upquark:
Totally-wild-and-too-lazy-to-confirm-it guess: there's probably an Xposed mod for that.
[One (M7) Original Android Development] Cheeky_Fink:
Delete LowBattery.ogg from /system/media/audio/ui and reboot. You'll have to do that each time you flash a nightly.
[One (M7) Original Android Development] bmeek:
Yes. It's a repeat of an earlier issue where skips will occur after any brief radio inference. For example, if you set down the phone and walk out of range wearing a headset, the streaming media will skip periodically thereafter. Turning the headset off and on will steady the connection until there's another brief interference...
[One (M7) Original Android Development] kbal:
Reporting

03.20 Nightyl + v1.7 AGK kernel + 0Day Pico Gapps

Faux123 Settings:

Smartmax governor, MAX 2.1GHz/ MIN 81MHz, Logo2Wake/Sleep, Fastcharge

SELinux set to premissive

No problems with music (youtube-Viral Pro) over Bluetooth (3.0 reciever). Actually, I have reception through 4 walls, when usually it managed only 2. Could be the solar eclipse :D

Viper4Audio: OK

Nokia Here: GPS is working excellent.

A Better Camera: Took a few pics, and all was good.

FxGuru: OK

AdAway working...

Actually everything is working 100% OK. But battery life is not so good :cyclops:
[One (M7) Original Android Development] jpyumul:
I've been searching for that audio file. Thanks!!!
[One (M7) Original Android Development] TachyOS:
My only wish is for the battery to last a bit longer :)!

Also , I have report a bug (small issue). The Torch light seems delay to turn on. Took about 1~2 sec. Already report on Bug page but no reply.
[One (M7) Original Android Development] sa_ma:
does camera with flash works without crash ?

would be great if you can stress test that part
[One (M7) Original Android Development] adamagic:
It definitely works by me without causing any reboots. I'm on the first Zram build.

Edit: oops, wrong topic. Sorry.
[One (M7) Original Android Development] kbal:
Reboots only if I take a closeup ('macro') pic with flash enabled. Sorry, I forgot to test that before :silly:
[One (M7) Original Android Development] withwolf1987:
I'm on 20.03 to.

My Bluetooth is laggy like the last 2 weeks.

Using a Sony Handset SBH52. after a couple of minutes the lags begin and going to a point that you can't list anymore.

Anyone have same issues.
[One (M7) Original Android Development] jpyumul:
Is there an option somewhere to make wallpaper scrollable?
[One (M7) Original Android Development] dd98:
Only in custom launchers like Apex or Nova
[One (M7) Original Android Development] jpyumul:
I see. Maybe I'm wrong but it used to be scrollable with default launcher. Now I just thought I messed with some settings or maybe the recent cm updates did it.
[One (M7) Original Android Development] dd98:
Probably google disabled this with an update to the google now launcher
[One (M7) Original Android Development] Cottaer:
Is there an issue in the bugtracker of cyanogenmod? If so, could you provide the link to it?