yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] spideyngo:
EDIT: SuperSU version 2.56. Sorry about that.

I am have an AT&T HTC One M8 on stock Marshmallow. SuperSU 2.76 puts my Marshmallow M8 in a boot loop. You may need to flash a rooted stock ROM to repair booting. S-off not needed, but makes your life easier.
[One (M8) Q&A, Help & Troubleshooting] frozst:
Thanks! the problem was the old SU version, solved now and testing different ROMs. Any recomendations?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Hadn't heard that. I wonder if its a known issue experienced by others? If so, I'll fall back to my previous recommendation to use 2.65, which was the former "latest" STABLE version; and no complaints that I am aware of.
[One (M8) Q&A, Help & Troubleshooting] kbytes:
Hello, HTC One M9 (Sprint here) I'm stuck in a bootloop too after unlocking the bootloader and installing SU. Tried several version of SuperSU without anyluck. Can anyone help please ?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
This forum is for the M8, any advice you get may not be correct. Post in the M9 forum.

But what I can say, is if you say "several version" SuperSU is not specific enough (when you post to the correct device forum). Be specific as to what version numbers you tried. Nobody can help, if you don't give the proper info to see what you did wrong. In particular, you need to provide info on what Android version your phone is currently on, what TWRP version, what SuperSU version(s) you tried.

But again, post to the M9 forum, not here.
[One (M8) Q&A, Help & Troubleshooting] weismanak:
Stuck on HTC Screen.

I've read through here and see that someone got their M8 off of the HTC start screen. I've installed the SuperSU, and TWRP, the phone restarted and now is stuck on the HTC screen. I am unable to hard reset the phone at all. Its stuck on that screen. Help?
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
You probably used an old version TWRP and/or old version SuperSU.

TWRP 3.0.2 and SuperSU 2.76 is recommended.

Hold power+vol up for a minute or so, to force a reboot.

Once the screen goes dark to reboot

, let go of the buttons, and only hold vol down. Don't let go of vol down, until you are in bootloader. If the phone just gets stuck on the logo screen again, you just got the timing wrong; either didn't start pressing vol down soon enough, or let go too early. Just repeat the process, until you get to bootloader.

From there, restore TWRP backup (which you should

always

make before attempting to root) and try again, with the proper versions TWRP and SuperSU.

If no TWRP backup, flash proper version TWRP in fastboot, then get proper version SuperSU to the phone (adb push, or put the file on SD card).
[One (M8) Q&A, Help & Troubleshooting] weismanak:
Still stuck in boot loop... but different place.

Whew!! OK, so I got past that hurdle (Thank you so much). I'm using the WinDroid Toolkit version 3.1 to unlock the bootloader, flash the TWRP, then flash the SuperSU. The phone is now stuck at the bootloader. If I select "Recovery" it simply comes back to the "Fastboot-usb". I've attached a screen shot (maybe) to demonstrate what I'm seeing on the phone.

Thanks for all your help, I'm a noOb to this process. Recent convert from iOS.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Meaning you used the TWRP version and SuperSU version included with the toolkit? If so, that toolkit hasn't been updated in a long time, and likely is not using the versions TWRP and SuperSU that I specified previously.

Additionally, I don't personally recommend using such toolkits. Doing so robs you of a valuable learning experience, and therefore guarantees that you stay a n00b. Also, the toolkits constitute an additional point of failure (even when they are updated) that is not necessary. I've often seen processes fail using the toolkits, when the exact same steps complete just fine if done "manually".

Since it appears you've successfully unlocked the bootloader (can be verified if it says UNLOCKED near the top of the bootloader screen), than I would advise:

1) Manually flash TWRP 3.0.2 with fastboot using the instructions here: https://twrp.me/devices/htconem8gsm.html

2) Download SuperSU 2.76 from here, and put it on SD card (alternately, adb push to phone - but that may be a bit complicated for you).

3) Boot into TWRP, under Install, navigate to the SuperSU 2.76 zip, and flash it.
[One (M8) Q&A, Help & Troubleshooting] ajay vadaparthi:
but when checked with root checker, it is showing not rooted. i'm not able to install root apps like flashify, supersu, root explorer. they all say that the phone is not rooted. i'm on mokee 60.1 release running on my redmi 2
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
have you flashed the latest supersu.zip ?

does the flashing process ended with success ?

you may try to enable root in developer options and see

also you are in the wrong forum
[One (M8) Q&A, Help & Troubleshooting] tigarstyle:
Can I re-flash SuperSU over an existing one?

Hi - Long time listener, first time caller!

So, I have a similar issue. After having my HTC M9 for almost 2 years, I decided to take the plunge and get the bootloader unlocked in order for me to update to v7 Nougat (currently on v6 Marshmellow) as Vodafone UK are a little slow in getting the update push out.

I followed a UTube video and all seemed to be going well after I restarted the handset after the bootloader unlock. I then had to enable the Dev Options and enable the USB Debugging in order for me to flash SuperSU 2.46 via TWRP 3.0.2.0.

However, TWRP informed me that the root was successful and to go ahead and reboot. Which I did. But it's now stuck on the HTC One splashscreen and won't proceed any further.

I still have access to TWRP and my PC was able to find the phone when connected with a usb cable (so in a state of softbrick). The FOOLISH thing I now realise, is that I didn't do a back-up of the stock ROM before flashing SuperSU. I've tried to search for a suitable RUU that I can download and get back to stock ROM (and then to unlock the bootloader so I can get v7 Nougat OTA). I'm surprised that there isn't a suitable RUU for my device (details below) and the 2 zips that I have downloaded via XDA simply wouldn't extract for me to get into the tool to flash the stock.

I've decided to go for a custom ROM (one that is with Nougat architecture/feel) if I can't allocate an RUU for my device.

I've come across too many forums and advice that I'm now overloaded with info and not sure which one to follow! Any help would be greatly appreciated as this device is one of the best handsets I've ever had (I've had handsets from early 2000's inc. an iPoo) and need to get it back up and running.

From the bootloader menu these are the details I have:

HTC_HIMA UHL PVT S-ON

LK - 1.0.0.0000

Radio - 01.01_U11440792_96.00.51201G_F

OpenDSP - 15.6.1.0052.8994_1026

OS - 3.35.161.12

Dec 17 2015, 00:40:10 (671447)

MRA58K_Release-Keys

This is a UK Vodafone carrier, model OPJA100 fcc id NM8OPJA100 M9u.

As the title of this thread suggests; can I simply delete the SuperSU v2.46 zip from the root directory, and download / paste SuperSU v2.76 to fix the stuck bootloader screen?

Or, as I have 2 downloads of the RUU.zip file, can I rename one, place it on my external SD card (64gb), go to bootloader and let the device install the stock?

As this device is softbricked, I'm open to suggestions for either stock ROM or custom ROM install.

Thanks in advance.
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
your first post in the wrong forum :( this forum for m8 );)

if you can flash a rom then flash it,will save the hassle of flashing RUU

and you used an outdated version of supersu ( i don't know if this will fix it but try to flash the latest version on top the older )

you can rename the RUU to 0PJAIMG.zip and put it in the sd card root ( formatted as fat32 or exfat , 3.xx can flash RUU from exfat cards ) then reboot to download mode and follow the instruction

if you have any question ask in the m9 forum as you may get a wrong answer here :silly:
[One (M8) Q&A, Help & Troubleshooting] tigarstyle:
Thanks a lot. I didn't realise this forum was for M8 only, my mistake. I've now posted in the correct forum.

I'll see what they suggest, but I didn't want to flash another SuperSU on top of another in case my phone was hard bricked. I guess I'm lucky that I have a connection with the PC as I can see the internal storage of my device still and I still have access to TWRP.

One thing that the other forums I've read so far didn't mention, is whether or not it matters that I can't extract the RUU.zip file on my PC. I'm I supposed to just place it on the SD Card and let it flash the Stock ROM, or do I need to extract the zip file in order to get to the utility program? Just thought it might be worth sharing for anyone who is on M8 and stuck on the HTC One splashscreen like I am.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
If the phone was hard bricked, you wouldn't be able to flash anything. The screen wouldn't come on at all. A hard brick means you need to open the phone to repair it (new motherboard or JTAG, at a minimum). You don't have a hard brick.

Do you mean to ask if flashing the proper SuperSU would brick the phone (if its safe to flash)? If that is the question, you best direct it to folks knowledgeable to the M9. On the M8, its fine to flash the newer SuperSU (and the proper fix after flashing obsolete SuperSU). But that doesn't meant the M9 is the same. And following advice meant for another device

can

possibly damage the device.

Nowhere

in any instructions for flashing RUU.zip will you see anything about extracting files from the RUU.zip.

Therefore, don't do it.

The file is encrypted and signed. Even if you were able to extract anything, you wouldn't be able to flash it with s-on (s-on can't flash unsigned RUU zips).
[One (M8) Q&A, Help & Troubleshooting] tigarstyle:
Excellent, thank you. I was wondering why the zip file wouldn't extract on the PC. I saw videos explaining that in other to get to Stock ROM, you'd do it via the RUU.zip. So when I downloaded the RUU.zip Stock ROM file, I thought I had to extract the zip in order to get to the application, then flash the device.

Thanks for taking the time out to explain in detail...much appreciated.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
You've got it a bit backward. RUU.exe would be the RUU Windows application, which contains the ROM.zip file.

The RUU zip file you can use as-is, either rename and put on SD card; or flash with fastboot in fastbootRUU mode.
[One (M8) Q&A, Help & Troubleshooting] tigarstyle:
...which is why you are a sensai, and I'm still the young grasshopper!

I'll take your advice when I get home. I'll rename the zip file, pop it onto the SD Card, boot it to bootloader and wait for it to flash.

:good::good::good::good::good:
[One (M8) Q&A, Help & Troubleshooting] Zephyrshr:
I installed Super SU app that is available on Play store and when i opened in it, it opened up TWRP recovery and installed supersu but when i tried to boot after that, i was stuck on bootloop. i was on Nightly cm 14.1 and i tried flashing official cm 13 and still the results were same. I've tried erasing everything but the supersu folder wont go away. flashing the zip you gave and manually deleting also didnt work for me. anything that can be done ? im using oneplus one
[One (M8) Q&A, Help & Troubleshooting] ahmed.ismael:
wrong forum :crying: means you will not get a proper answer

things that work on HTC One M8 maybe will not work on OPO ask in a proper forum/thread

the version 2.56 is outdated now flash the latest 2.79

and try to flash the stock rom if this didn't help
[One (M8) Q&A, Help & Troubleshooting] Merrin Joseph123:
SuperSU flash bootloop fix

Flash magisk much better than SuperSU

No errors while flashing

No bootloops
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
While I agree that Magisk is the better root option at this point (lots of benefits, where SuperSU doesn't provide any tangible benefit over Magisk);

no

root option is guaranteed to flash without error or bootloop for every user in every situation.

I've seen folks get bootloops and errors with Magisk. Always make a TWRP backup of the stock ROM before any root method. Stuff happens.
[One (M8) Q&A, Help & Troubleshooting] feel456:
im in bootloop help

how though:crying:
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
What do you mean "how though"? I assume since the topic of this thread is "stuck . . . after flashing SuperSU" that you already have the bootloader unlocked, and flashed TWRP and SuperSU. And therefore, already know how to do those things.

If there is a specific step you don't know how to do, or understand, than you need to ask specifically and clearly. I see you are brand new to the forum. But best practice is to describe your issue or question with as much detail as possible. Asking for help with just one or 2 sentences is not sufficient information for anyone to help. You'll just be wasting time (yours and ours), as we ask you for more details that you should have provided in the first place.

You also need to be careful, as it appears (from the post your quoted) you are considering following info from a post from over 2 years ago (July 2016). Typically, if you are rooting, you should be using the most up to date files and methods. There are some exceptions, but again, since you gave no specific info about the current condition of the device, it's hard to provide proper help. For the best advice, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about your device.

But in general, stuck at boot after trying to root is almost always due to old version TWRP and/or old version SuperSU. ANd flashing the correct versions will often fix the "stuck" issue. Need more specific info (as requested) to be sure about what version TWRP to use. But for most folks, they will want to use latest TWRP 3.2.3-1 using fastboot. You can get TWRP from here: https://dl.twrp.me/m8/

Then In TWRP, flash current version SuperSU 2.82 from here: https://xdaforums.com/app...lease-t3452703

But to be honest, I would suggest Magisk at this point. It is a newer root method than SuperSU. And SuperSU appears to be dead, anyways. Not only is Magisk still being updated and supported, but it seems to work a little more reliably. Plus, Magisk has a ton of cool and useful features, that SuperSU does not. Suggested Magisk version is 18.0: https://xdaforums.com/app...mless-t3473445
[Tilt, TyTN II, MDA Vario III General] BennTech:
This is one of several problems with my AT&T Tilt. My 30 day return policy ends November 8, so I'm trying to figure out which problems are specific to my phone and which are just Kaiser in general.

Once or twice a day, my phone screen gets corrupt with overlapping text and only the screen locks up. Also, ActiveSync no longer connects. Otherwise, the phone is still fully functional. The screen still responds to touch (although I can't tell what I'm touching), sounds still works, I can make/receive calls, and Voice Command works and even announces incoming calls. The only way I've found to unfreeze the screen is to soft reset.

This happens on both the AT&T and Helmi ROMs with minimal apps and tweaks commonly used by fellow XDA members. So I'm thinking either the problem is my phone's video chip or it's the video driver common to Kaiser ROMs. But if it's the latter and it's happening to other people twice a day, too, I can't imagine that no one would have posted about this irritating problem.

Note that this is different from the thread "random freezing on tilt", where their phone locks up for a few seconds then unfreezes. In my case, ONLY the SCREEN locks up and NEVER unlocks.

Anyone's Kaiser having this only-screen-frozen problem?
[Tilt, TyTN II, MDA Vario III General] BennTech:
Is it only me?

I take by the complete lack of responses and very low view count that no one has this problem except me?

I'm thinking I just got a f'd up Tilt based on these constant lockups on two different ROMs, my Bluetooth problems (which no one else seems to have), plus the 2 dead pixels on the screen (one locked blue above the Start icon and the second locked red just above the hour digits on the HTC Home clock). Guess it's back to the crappy AT&T ROM for me, then wait for a lock up as partial proof of my problems and go the AT&T store to request a new Tilt (which, according to another recent thread, AT&T no longer has in stock).

Just for future reference, it seems that I actually get two types of lockups.

The most common lockup is as described, where the screen gets corrupted with overlapping text and locks up, but phone and touchscreen are still fully operational.

Less common is a complete phone lockup, which causes me to miss calls. The screen doesn't get corrupt, but the phone is completely frozen except for the power button turning the screen off/on.
[OnePlus 3 Questions & Answers] MeeGz:
Hello XDA,

I can't seem to get zANTI(the merged version of dSploit) to work properly. When it scans my network in it's initial auto mode as well as in its nmap mode no open ports are detected nor are any operating systems. Conversely cSploit see open ports and operating systems, as does fing.

I'm guessing that this is a problem with the nmap binary however I'm not entirely sure how to go about installing it. I've read the various instructions online without luck. I wish we had apt or were able to use a standard makefile! (maybe we can... I've never tried)

Does anybody have any idea how to fix this? It's kind of annoying because zANTI seems like a great pentesting tool. I just don't want to play around too much as I've broken my Android installs in the past!

-MeeGz

EDIT: I'm curious if systemless root has anything to do with this... Also, I've noticed that there is no bin in /sdcard/opt/nmap-6.46(I'm in the process of installing 7.12)
[OnePlus 3 Questions & Answers] MeeGz:
EDIT: Meh... Turns out that it was bad permissions in /data/data/com.ziperium.zanti/files/nmap

I actually replaced the nmap binary with a newer version and then replaced it with the older binary before realizing that the permissions were fubar'd... Good thing I installed 'MiXplorer' because 'ES' wouldn't even show me the directory. I've never had to play with an apps file's in the past....
[OnePlus 3 Questions & Answers] evertking:
How did you fix it?

Also have you tried cSploit.org

---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------

I have not been able to get zanti or cSploit to work like they did back on 4.4.4
[OnePlus 3 Questions & Answers] MeeGz:
I can't really help you with cSploit because I haven't had any issues with it. With zANTI just go to the above mentioned directory and make sure that everything you need is executable and that the "owner" matches the correct app id. A word of advice though; use "miXplorer" to browse for the files and makr sure that you're rooted before attempting any of this...
[OnePlus 3 Questions & Answers] zadarr:
I put 755 permissions on all files in that directory. All files have the same owner and group app ID, but still I can't get open ports in Zanti.

Can you be more specific.

Thanks!
[OnePlus 3 Questions & Answers] kalim_714:
Did you find any solution?

I have the same issue on my lg v10.

Thank you
[OnePlus 3 Questions & Answers] KaviarV:
Yeah, having the same problem with my 3T. Tried fixing the permissions to the app but with no success.
[OnePlus 3 Questions & Answers] ozsteyr:
Still no info on a fix? Same issue on zanti 2.5, S8+ , Nougat.

Batman ROM and kernel. Aswell as OP3 on MM and nougat. This issue has been around for a LONG time. I was told by Zimperium that this is known issue and would be fixed with the next major update. This was at version 2.4.
[Moto Maxx Themes and Apps] Nitefire77:
I'm attaching below the new Command Center Clock/weather Widget from the Moto Z phones.

It comes courtesy of XDA member gourabpa and was posted over on the Moto X Style (Pure) Forums

and I'm just resharing the APK here.

Enjoy :)
[Moto Maxx Themes and Apps] quantum tao:
I tried it but they made the fonts unnecessarily small. Went back to version 2 for people with old eyes.
[Moto Maxx Themes and Apps] Gand4lf23:
Thank you for posting it!
[Moto Maxx Themes and Apps] ProjectNeko:
Thank you!

Thank you so much for posting this! I was living this widget on the Moto Z before it stopped working on my AT&T line. I feel complete again with this on my phone!
[Moto Maxx Themes and Apps] mateus.ferreira1992:
Calendar

Do you know if I can access the calendar by clicking on the date in this widget?
[Moto Maxx Themes and Apps] Nitefire77:
Nope
[Moto Maxx Themes and Apps] fenix3nk0r3:
i like
[Moto Maxx Themes and Apps] Gilad.i:
Hay, I get that line in the widget, is there a way to remove it?
[Moto Maxx Themes and Apps] LironImaN:
Same here, I'm pretty sure it's because we use RTL language, so it's not compatible.
[Moto Maxx Themes and Apps] samcook2003:
How do you open this I have Nova
[Moto Maxx Themes and Apps] overon37:
You can not
[Moto Maxx Themes and Apps] enetec:
File name is indicated as .apk, but downloading it it's a .zip. More, this zip is indicated as "not secure" by Smartscreen by Microsoft. :eek:

It's all ok? How can I install it? By flashing it in TWRP? Works fine on Moto Z?
[Moto Maxx Themes and Apps] Nitefire77:
I just extract the zip and install the APK. It works great
[Moto Maxx Themes and Apps] enetec:
There is no apk inside! It's the zip that have to be renamed as .apk! I've found the apk elsewhere and in fact two files are identical but the extension! ;)
[Moto Maxx Themes and Apps] Globus1002:
Спасибо! Я счастлив!!!

: D
[Moto Maxx Themes and Apps] Globus1002:
Ð° ÐµÑÐ»Ð¸ Ð½Ð°Ð¶Ð°Ñ‚ÑŒ Ð½Ð° Ð¼Ð¾Ð»ÑŒÐ±ÐµÑ€Ñ‚ Ð¿Ð¾Ð´ Ð±Ð°Ñ‚Ð°Ñ€ÐµÐµÐ¹, Ñ‚Ð¾ Ð¼Ð¾Ð¶Ð½Ð¾ Ð¸Ð·Ð¼ÐµÐ½Ð¸Ñ‚ÑŒ Ñ†Ð²ÐµÑ‚ Ð¸Ð½Ð´Ð¸ÐºÐ°Ñ‚Ð¾Ñ€Ð° Ð·Ð°Ñ€ÑÐ´Ð°.

:Ñ…Ð¾Ñ€Ð¾ÑˆÐ¾:
[Moto Maxx Themes and Apps] Globus1002:
Hello!

How do I change the alarm clock on the date, under the age?
[Moto Maxx Themes and Apps] Brooklnd:
Guys... Isn't this version compatible with Nougat? I tried to install it on my OnePlus 3 with OxygenOS 4.0 (Nougat), running Nova Launcher Prime, and it installed fine. But when I add the widget to the homescreen, it just keeps spinning without loading any font. It does this on every launcher (tried OnePlus stock launcher, Action, Next, Go and Apex as well). It has already been granted all permissions. Can anybody help, please?
[Moto Maxx Themes and Apps] tuxworld:
xt1225

doesnt work with mine I dont know why?
[Moto Maxx Themes and Apps] Nguyhen4wd:
Which one version of Android works ? i like this widget ...
[Moto Maxx Themes and Apps] mr.s¹:
;)

I have m;)

I
[Moto Maxx Themes and Apps] MrRamziaB:
Been looking for this forever!

THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! THANK YOU! :laugh::laugh::laugh::laugh:
[Moto Maxx Themes and Apps] Digoloco:
Wallpaper Bro :good:
[Moto Maxx Themes and Apps] cleonti:
Widget Installs, But Not In List To Use

I have installed this on my Verizon Z2 Force and not having any luck actually using it. The widget installs, shows as running when I check system apps but does not show up in my widgets. To make sure I didn't miss something I should do, I did the following:

Download the APK.

Tap the APK and elected to install it (already had sideloading enabled).

Received confirmation that Command Center had been installed.

Press and hold on home screen and select Widgets.

Scroll through list, but don't see it listed as Command Center or under any other name when I check entire listing.

If I open apps and enable Show System I do see Command Center there and it looks like it is running. I have power cycled with no change in ability to add the widget. I also checked the apps list and didn't see it though I didn't expect it to be there.

I would love to have this widget so any suggestions to successfully use it would definitely be appreciated.
[Moto Maxx Themes and Apps] MSSathvik:
Can anyone tell me how to install this widget on Nougat 7.1.1. I'm not able to install it.