Phone Locked in Limbo after HTC Lock Screen Update - Verizon HTC 10 Questions & Answers

I'm running Viper 4.3.1 on an unlocked HTC 10 on Verizon. I've been extremely happy with this build and saw no reason to update to the systemless version of Viper. I've been careful not to install updates that would cause problems, but I got sloppy two days ago and let it update the HTC Lock Screen app. Now the phone is stuck on a flashing stock lock screen and won't do anything else.
I can boot into bootloader and recovery, but the phone is not recognized when I plug it into my PC.
So my question(s) is this: Is there a simple way to return to a working version of Viper 4.3.1? Perhaps sideloading an earlier version of lock screen?
I guess at this point I also should ask if I'm fighting a losing battle by trying to stay on an older version of Viper?
Any help is much appreciated.
PS -- If this should have been posted in the ROMs section, I apologize.

hunteditor said:
I'm running Viper 4.3.1 on an unlocked HTC 10 on Verizon. I've been extremely happy with this build and saw no reason to update to the systemless version of Viper. I've been careful not to install updates that would cause problems, but I got sloppy two days ago and let it update the HTC Lock Screen app. Now the phone is stuck on a flashing stock lock screen and won't do anything else.
I can boot into bootloader and recovery, but the phone is not recognized when I plug it into my PC.
So my question(s) is this: Is there a simple way to return to a working version of Viper 4.3.1? Perhaps sideloading an earlier version of lock screen?
I guess at this point I also should ask if I'm fighting a losing battle by trying to stay on an older version of Viper?
Any help is much appreciated.
PS -- If this should have been posted in the ROMs section, I apologize.
Click to expand...
Click to collapse
You can try manually removing the updated app.
Use Twrp > advanced > file manager
Locate the /data/app/com.htc.lockscreeen-1 folder or whatever it's called in there and delete that entire folder.
Try to reboot, may or may not help...
Sent from my HTC6545LVW using Tapatalk

Almost There
santod040 said:
You can try manually removing the updated app.
Use Twrp > advanced > file manager
Locate the /data/app/com.htc.lockscreeen-1 folder or whatever it's called in there and delete that entire folder.
Try to reboot, may or may not help...
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
That didn't work, but by trying it, I think it will be as simple as installing a previous version of the lockscreen. Now just have to find one.

hunteditor said:
That didn't work, but by trying it, I think it will be as simple as installing a previous version of the lockscreen. Now just have to find one.
Click to expand...
Click to collapse
http://www.apkmirror.com/apk/htc-corporation/
Sent from my HTC6545LVW using Tapatalk

Related

98.18.78 update

I have a Motorola droid razr m model XT907. It's rooted and GSM unlocked. I'm using it on Straight Talk currently. Verizon is pushing this 98.18.78 update which I hear unroots the phone. I want to know which of the verizon apps I need to freeze or remove to prevent this update.
Thanks in advance
Blufx1 said:
I have a Motorola droid razr m model XT907. It's rooted and GSM unlocked. I'm using it on Straight Talk currently. Verizon is pushing this 98.18.78 update which I hear unroots the phone. I want to know which of the verizon apps I need to freeze or remove to prevent this update.
Thanks in advance
Click to expand...
Click to collapse
Just a heads up, you posted in the Razr HD forum, but no big deal the procedure will be the same for both. When I was running stock ROMs, I would freeze the updater.apk in TiBU to prevent OTAs. However, the new update is rootable with Motochopper 1.3, but you can't unlock the bootloader. If I was in your situation, I would unlock the bootloader now, take the update (for the improvements it offers), re-root it, and unlock it for GSM again. Once your BL is unlocked and you have a custom recovery installed, all you have to do is flash SU in recovery to regain root.
I thank you for the answer. You make it sound so easy,. However, I needed step by step instructions to get where I am now. Can you point me to some to do this? I've unlocked the GSM a couple of times using CellZealot's post. That's no problem. I have titanium backup to freeze the updater.apk, but what is TiBU? I'll get Motochopper in the meantime.
Duhhhh, I just figured out what TiBU is.
Blufx1 said:
Duhhhh, I just figured out what TiBU is.
Click to expand...
Click to collapse
If you don't want to unlock the bootloader and want to take the OTA, then root afterwards, you can find Motochopper 1.3 here:
http://www.droidrzr.com/index.php/t...oot-razr-m-xt907-for-locked-devices-on-91878/
If you want to unlock the bootloader, look for Motopocalypse here (you'll need root access for this, so unlock prior to updating. The OTA does block the ability to unlock the BL, but does not block the ability to root):
http://wiki.cyanogenmod.org/w/Template:Motopocalypse
Once you unlock the bootloader, look for the TWRP thread in the Development section, there should be instructions, along with the file you need to install the recovery. Once TWRP is installed, get the updater SuperSU .zip and flash it in recovery and you will re-gain root. If you want to update after unlocking, you can take one of the several stock ROMs running around here and flash in recovery.
SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Long story short:
- You can stay as is, by just freezing the updater.apk
- You can OTA and re-root with Motochopper 1.3
- You can unlock bootloader and re-root afterwards.
Thanks again. I'll work on this tomorrow and post back.
Blufx1 said:
Thanks again. I'll work on this tomorrow and post back.
Click to expand...
Click to collapse
No probem, let us know how it turns out.
RikRong said:
If you don't want to unlock the bootloader and want to take the OTA, then root afterwards, you can find Motochopper 1.3 here:
http://www.droidrzr.com/index.php/t...oot-razr-m-xt907-for-locked-devices-on-91878/
If you want to unlock the bootloader, look for Motopocalypse here (you'll need root access for this, so unlock prior to updating. The OTA does block the ability to unlock the BL, but does not block the ability to root):
http://wiki.cyanogenmod.org/w/Template:Motopocalypse
Once you unlock the bootloader, look for the TWRP thread in the Development section, there should be instructions, along with the file you need to install the recovery. Once TWRP is installed, get the updater SuperSU .zip and flash it in recovery and you will re-gain root. If you want to update after unlocking, you can take one of the several stock ROMs running around here and flash in recovery.
SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053
Long story short:
- You can stay as is, by just freezing the updater.apk
- You can OTA and re-root with Motochopper 1.3
- You can unlock bootloader and re-root afterwards.
Click to expand...
Click to collapse
To add to this, if you unlock, you will permanently be able to root...
Sent from my Nexus 7 using Tapatalk 4
Ok. I have the bootloader unlocked. I downloaded a rom from here. It's been cleaned up of bloatware and stuff. I have SuperSU and updater SuperSU, but I dont know what to do with it. I also installed TWRP manager. I need just a little more guidance.
Blufx1 said:
Ok. I have the bootloader unlocked. I downloaded a rom from here. It's been cleaned up of bloatware and stuff. I have SuperSU and updater SuperSU, but I dont know what to do with it. I also installed TWRP manager. I need just a little more guidance.
Click to expand...
Click to collapse
Ok, so first, you need to disable the install-recovery script. I built an app to do this (YOU GET TO BE THE FIRST TESTER YAY!)
Install this app: ftp://kd8rho.net/RecoveryFlasherDisabler-public-test.apk
Choose "disable install-recovery"
That will (theoretically - can't test cause my phone's rooted and ROMMed) allow you to install a custom recovery without any hassle.
Once that's done, follow the installation instructions in this thread http://forum.xda-developers.com/showthread.php?t=2226729, starting with this line:
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
Click to expand...
Click to collapse
You won't have to boot directly into recovery because that app *should* fix that for you. You can boot the phone normally after installing and run something like "adb reboot recovery"
I downloaded and installed your app. When I ran it, it said the installer was found, but disabled. moving on to step two now. Thanks
Hello. This is way off base but does the update fix the screen glitch? Are there any roms that will fix the glitch?
Thanks in advance!
Xt907 JESUS IS THE WAY, THE TRUTH, AND THE LIGHT! *BE BLESSED*
The screen glitch isn't fixed from the update. It might be better. I have a hunch the new radio isn't good for customers with unlimited data in areas with 4G coverage. My phone seems more eager to switch to 3g after the update. Besides that, I can't tell this update foes anything positive. It would be nice to use fastcharge while powered off but for some reason my device will not turn off while it's plugged in. It used to turn off and charge, then one day it quit working. If my battery is low enough and I turn the phone off the green light glows solid for s few minutes then the xt907 turns itself on. Can I downgrade to the previous radio or am I stuck with the new 3g friendly radio that presumably serves Verizon's purposes and not mine?
Sent from my XT907 using xda app-developers app
zombolt said:
The screen glitch isn't fixed from the update. It might be better. I have a hunch the new radio isn't good for customers with unlimited data in areas with 4G coverage. My phone seems more eager to switch to 3g after the update. Besides that, I can't tell this update foes anything positive. It would be nice to use fastcharge while powered off but for some reason my device will not turn off while it's plugged in. It used to turn off and charge, then one day it quit working. If my battery is low enough and I turn the phone off the green light glows solid for s few minutes then the xt907 turns itself on. Can I downgrade to the previous radio or am I stuck with the new 3g friendly radio that presumably serves Verizon's purposes and not mine?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Yea...all I did was flash the radio and it feels like I'm being throttled now that I have the new radio...still on the.3/.78 just with the new radio... I'll try and flash the old radio here in a min ... Are you on an unlocked bootloader?
Sent from my XT907 using xda app-developers app
zombolt said:
The screen glitch isn't fixed from the update. It might be better. I have a hunch the new radio isn't good for customers with unlimited data in areas with 4G coverage. My phone seems more eager to switch to 3g after the update. Besides that, I can't tell this update foes anything positive. It would be nice to use fastcharge while powered off but for some reason my device will not turn off while it's plugged in. It used to turn off and charge, then one day it quit working. If my battery is low enough and I turn the phone off the green light glows solid for s few minutes then the xt907 turns itself on. Can I downgrade to the previous radio or am I stuck with the new 3g friendly radio that presumably serves Verizon's purposes and not mine?
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Unfortunately I am locked. Bought the phone *right* after the may update. I migrated from the droid incredible, which has an open bootloader I believe. So it's been pretty rough after having that phone!
Sent from my XT907 using xda app-developers app
What "screen glitch" are you talking about?
Oh, I forgot to post back. I managed to screw it up royally. But I have it straightened out now after a flash.
The screen will occasionally glitch on the left side, pushing the screen right and changing the color for about 1-2 seconds
Sent from my HTC6435LVW using XDA Premium 4 mobile app

[Q] no wifi rooted at&t S4 4.4.2 NB1

greetings!
I've been searching for hours and bashing my brains trying to get wifi working. It originally broke after an OTA update
tried all the tips and still nothing works permanently. The things I have tried are too numerous to remember or list.
It's not a hardware issue as wifi can work for periods of time but it always breaks - I assume because of an update that downloads and breaks it.
i see talk of reflashing "modules" with safestrap but safestrap has never worked properly and now does not work at all ("unfortunately safestrap has stopped") Can modules be flashed from Odin?
TIA !
Sorry to hear about your troubles man. Been there, done that...
IMHO, if you don't have hardware issues, this what you should do:
ODIN to stock http://forum.xda-developers.com/show....php?t=2616221 (post 1, the Returning to Stock / ODIN section)
After that root
Root with towel root (https://towelroot.com/)
Install SuperSU (PlayStore) and let it disable Knox.
Install BusyBox (PlayStore) and let it cook
Install SELinux Mode Changer (PlayStore). Run and set it to Permissive.
Install Safestrap (http://forum.xda-developers.com/show...php?p=45693712)
Now it's time to flash you favorite rom (Safestrap has the list). Copy the following to your SD card:
Your favority ROM
SuperSU.zip file. (http://download.chainfire.eu/451/Sup...erSU-v2.01.zip)
Your modem zip file (http://forum.xda-developers.com/show...96&postcount=1).
I337 Build.prop/APN (http://forum.xda-developers.com/show...81&postcount=9)
Same boat as well I believe, need help please.
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.
Few screens to help out
Here are a few screen shots that I hope help someone out. Please let me know what I can do if anything.
ONLY DRAGONMIKE said:
I have a Samsung Galaxy S4 AT&T I337 ucufnbn1 MDF. And I've tried to get into the UMTS menu with every possible number and trick I can find on Google, here, YouTube. And nothing works. I just want to be able to sim unlock it and also be able to put cwm recovery on it so I can put ROMs on it. I do have it rooted with Towel and have busy box installed as well as SU. Cyanogen's website picks it up by its other name jfelte or whatever and has a lot of ROMs. If someone could please help me finish getting the rest of the way, that would be greatly appreciated.
Click to expand...
Click to collapse
You won't be able to put cwm on it or cm. See index, all things at&t......in the general forum
Sent from my Nexus 5 using XDA Free mobile app
Ummmm a tiny bit more help please lol
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.
ONLY DRAGONMIKE said:
I looked at the stuff in that link and like eating ice cream to fast , I got a brain freeze or headache........ Lol. I'm getting that I need to downgrade to mk this and flash that. Could someone be kind enough to give me a quick but correct step by step run through. Again it'd be very appreciated.
Click to expand...
Click to collapse
Just click on the spoiler for nb1 need users. The step by step is there. It's in the first post
Sent from my Nexus 5 using XDA Free mobile app
So this one
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.
ONLY DRAGONMIKE said:
So are you talking about this one and if so, why would I do that when that's what I'm already on. I'm on nb1 4.4.2 rooted with towel. So I'm lost in what your trying to explain.
Click to expand...
Click to collapse
You're on nb1 and rooted. The next step is to install safestrap 3.72
Sent from my Nexus 5 using XDA Free mobile app
So Safestrap 3 it is
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.
ONLY DRAGONMIKE said:
So I need to install Safestrap. I heard with my s4 being MDF , it would damage it. I could be wrong and if so cool. Just let me know no probs.
Click to expand...
Click to collapse
What's mdf?
Sent from my Nexus 5 using XDA Free mobile app
MDF Reply
Security software Version
MDF v1.0 Release 2
MDF Reply
Here is a screenshot of where I'm talking about. Oh and Safe strap 3.72 is installed perfectly thank you so very much for that. Your awesome. And a lot of people are saying when you reboot and it shows the "Safestrap is disabled" screen you can't get back into it. I did just fine.
ONLY DRAGONMIKE said:
Here is a screenshot of where I'm talking about.
Click to expand...
Click to collapse
You're on nb1 firmware, safestrap is ok
Sent from my Nexus 5 using XDA Free mobile app
NB1 discussion
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.
ONLY DRAGONMIKE said:
Ok , well I honestly appreciate your help with this. With this setup can I install any ROMs at all? Am I limited to certain ones or can I install any compatible ones for my model? I know sometimes when your on a certain stock ROM your stuck with only like certain types. Like Paranoid or whatever it is, and a few others.
Click to expand...
Click to collapse
You can not install any roms. The i337 on any firmware higher than mdl can only flash touch wiz based roms. See the index, all things at&t.... for roms that are compatible.
Sent from my Nexus 5 using XDA Free mobile app
This mini-guide should work!
The problem is, in order to get WiFi working, you need to install the NB1 modules, but to do that, you need to install Safestrap. However, you can not install Safestrap because the app keeps closing on you. There is a simple fix to this, which I will explain later. For now, just read this WHOLE post BEFORE you do anything, and keep in mind that I am NOT held liable if you mess up your phone. Use this at your own risk.
1.) Root your phone
If you're already rooted with something like SuperSU or Superuser, skip this. If not, read ahead. Download and install the Towelroot APK file attached to this post, open it, and click 'make it ra1n'. If your phone didn't reboot, now you have root (they need to trademark that). Now, down below, I also included the APK for SuperSU. Download and install it. Now open it. When you open it, let it install the 'Normal' way, not via the 'TWRP/CWM' way. Also, when it asks you to disable KNOX, say yes, wait a couple of minutes (it will still be loading) and reboot your phone. Open up SuperSU again, click 'Yes' to disable KNOX again, and now you have a good base to start from.
2.) Install Safestrap AFTER fixing the error
The error your are getting is easily fixed. Go to the Play Store and install 'SELinux Mode Changer'. Open it, grant it root access, and change the mode to 'Permissive'. Now, open up Safestrap again (you mentioned you already installed it), and it shouldn't force close. Click 'Install', and if the 'Reboot to Recovery' option below is not grayed out after that then it worked.
3.) Download and install the NB1 modules
On your phone, download the included NB1 modules ZIP file I attached for you, and once that is done you need to reboot. After the Galaxy S4 logo, you'll see a screen that says 'SAFESTRAP: DISABLED' and there will be a little robot. TIP: To enter Safestrap, press the menu button (physical, hardware key) under 'Recovery' at that screen. To continue to Android, press the back key (again, physical) under the 'System' tab. For now, press the menu button under 'Recovery'. Now, click 'Install' which should be in red, click 'Add zips', and navigate to your Downloads folder. Now click on the NB1 modules ZIP you just downloaded. Swipe to install, and reboot. This time, hit the back key under 'System'.
All done!
Now, Android should (and will) boot up, and you'll have working WiFi! If, for some odd reason, you don't have WiFi- do NOT panic! Just search around for the MF3 modules and flash those! All is good, all is good. A lot of this guide was taken from my post about my personal method of SIM unlocking the AT&T Galaxy S4 without the dialer codes or an AT&T SIM. It was just modified a little to work for you.
Remember, hit thanks! :good:

Just caught my Turbo trying to update on it's own

I was sitting in my car and looked at the screen and I noticed that the phone was downloading MotorolaOTA 4.0 Does anyone know what it is? I am currently running KitKat 4.4.4 and never did the Lollipop update.
I also stopped the download in process but it appears that the phone would love to continue the download.
Thanks
gman
The phone has an app called MotorolaOTA, which is responsible for downloading system updates. If it was a software update it'd say it's 23.11.39.
Sent from my Droid Turbo using Tapatalk
Just caught my Turbo
I am running KitKat 4.4.4. version 21.44.12 the file it's trying to download is 770 megabytes. Could it be trying to sneak in Lollipop?
gman781 said:
I am running KitKat 4.4.4. version 21.44.12 the file it's trying to download is 770 megabytes. Could it be trying to sneak in Lollipop?
Click to expand...
Click to collapse
Yes, it will download the update but, afaik you MUST confirm installation of it... It's not going to install on it's own...
smokie75 said:
Yes, it will download the update but, afaik you MUST confirm installation of it... It's not going to install on it's own...
Click to expand...
Click to collapse
For over a month I have been getting the update screen and I would just put it off. Now it seems like it is pushing it's way into my phone.
Motorola confirmed recently that they would be patching the Stagefright exploit for the Turbo via OTA. I wonder if they can somehow force the update since it's such an important security issue this time around. I seem to remember Samsung doing something similar with the S6 shortly after release. I would recommend disabling Motorola OTA until more is known.
Not rooted, cannot disable.
Caught my phone doing the same thing. Is Lollipop larger than 770MB? I thought so, but haven't checked into it.
That's what I have been trying to figure out.
TheHolyCobra said:
Caught my phone doing the same thing. Is Lollipop larger than 770MB? I thought so, but haven't checked into it.
Click to expand...
Click to collapse
CM 12.1 ROM (Lollipop 5.1.1) for our Quarks is only 390 MB.
So, yeah, Lollipop 5.1 with Verizon bloatware is probably 770MB.
But the 5.1 OTA for Droid Turbo XT1254 posted here is 1.1GB:
http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Still 770MB is huge.
Just freeze it
Sent from my XT1254 using XDA Free mobile app
Not rooted and will not allow disable.
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
drtweak said:
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
Click to expand...
Click to collapse
Before my turbo was rooted, I was able to block the OTA's by installing the motorola drivers on my windows pc and installing Minimal ADB / Fastboot. Go here for instructions http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
However, I never did download any of the OTA's to my phone but I hope this helps. I believe this is by Rootjunky as far as credits are concerned.
Also by Misterxtc
gman781 said:
Not rooted and will not allow disable.
Click to expand...
Click to collapse
RL_Wells said:
Before my turbo was rooted, I was able to block the OTA's by installing the motorola drivers on my windows pc and installing Minimal ADB / Fastboot. Go here for instructions http://forum.xda-developers.com/showpost.php?p=57436867&postcount=26
However, I never did download any of the OTA's to my phone but I hope this helps. I believe this is by Rootjunky as far as credits are concerned.
Also by Misterxtc
Click to expand...
Click to collapse
The debloat tool is a much easier way to disable any app on your phone. On kitkat it disables and on lollipop it hides the apps. The hide command on lollipop has the same effect as the disable command on kitkat.
---------- Post added at 02:12 PM ---------- Previous post was at 02:10 PM ----------
drtweak said:
My phone downloaded it. Been telling it no thanks for a few days now. Some home after telling it to remind me later it then decided to reboot and start installing. I haven't rooted yet but I have bought moforoot and don't want my 20 bucks to go to waste! Of course I can boot up without it wanting to install. Went into bootloader and powered it off. Almost though i couldn't get into that.
Any way I can stop this thing? Trying to get someone at home to turn on my PC since that is where my moforoot is at and stupid me didn't put it on my server which is on 24/7. Any ideas?
Click to expand...
Click to collapse
Enter recovery mode, clear cache and use the debloat tool to disable the OTA.
[/COLOR]
Enter recovery mode, clear cache and use the debloat tool to disable the OTA.[/QUOTE]
Yea no go on Recovery. It just goes straight to "Installing System update" Got my PC on, downloaded my mofo to my work PC, and not installing drivers and also downloading a stock but rooted version of 4.4.4. not quite ready to move on to 5.1 yet.
Thanks for the help though and tryin to help out! Now to finally jump into my Turbo after 8 months of having it. I miss the days of TWRP on my Razr HD. Funny because i had to reload an old backed up image so i could get some old wifi passwords.
UGH this damn phone. Won't power off when in Fastboot, so i just have to let it sit in fastboot and watch it and just restart everytime it starts up. got 20 minutes left of downloading an image. About ready to say F'it and just factory reset it for now and see if that fixes it or not.
Well flashing a stock rooted rom didn't work. Uses the rooted Quark 21.44.12 image that I download and I know i was on 21.44.12 when i checked last time. So don't know if it was because of the starting up the update or what.
Soft bricked my turbo, time to use RSD Lite again. Haven't had to use this in a LOOOOOONG time (Like Droid X Days)
drtweak said:
Well flashing a stock rooted rom didn't work. Uses the rooted Quark 21.44.12 image that I download and I know i was on 21.44.12 when i checked last time. So don't know if it was because of the starting up the update or what.
Soft bricked my turbo, time to use RSD Lite again. Haven't had to use this in a LOOOOOONG time (Like Droid X Days)
Click to expand...
Click to collapse
I'm probably too late but have you tried this to get back to KitKat? I used it earlier today and it worked great.
Misterxtc said:
I'm probably too late but have you tried this to get back to KitKat? I used it earlier today and it worked great.
Click to expand...
Click to collapse
No I had to get my phone backup asap. using the RSD Lite method actually didn't work. the program would keep freezing right after it read the zip file and then crash. Had to use Root Junky's method. I was able to restore back to stock 21.44.12 and everything was there as if nothing happened so I'm all good.

Android Nougat is coming to the M9 sometime in the "far" Future

Lets see if it comes faster to our Device then Marshmellow...after Google released it to the Manufactures.
And it comes as it seems just to three Devices. (A9,M9, HTC 10)
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Got that system security OTA notification as well today. I'm using the stock ROM with root (SuperSU flashed via TWRP). Can I stay rooted to apply the OTA with the stock recovery or do I have to flash the RUU first?
Solved:
Make a backup with Titanium or however you like. Save all your data from internal SD. Afterwards apply latest RUU.exe from HTC (depending on your carrier). If you wanna reroot, I would suggest SuperSU 2.65, because newer versions end up in bootloops.
Don't expect Nougat this year...
It's the August security update
Sent from my HTC One M9 using Tapatalk
hope this year released
matmaneyre said:
You can't install OTAs with a custom recovery. You'll need to flash the stock recovery first and try again.
Click to expand...
Click to collapse
Do you have 3.39.531.12 stock recovery??
missicolin said:
Do you have 3.39.531.12 stock recovery??
Click to expand...
Click to collapse
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Amishrabbit said:
If you are flashing from 3.39.531.7 to .12 then you need the stock recovery from 3.39.531.7 to be installed.
If you've already flashed a custom recovery like TWRP, then just pull down the RUU from HTC's Web site. Be warned, however, that it will wipe the phone back to factory-fresh, so back up all your files/data/photos/music etc. and remove the SD card just to be safe.
RUU 531.12 T-Mobile
And to answer your specific question, I don't have the stock recovery for 531.12, but I presume that I will later today after I RUU my own device. I don't know how to archive the stock recovery but I plan to flash over it immediately with TWRP.
Click to expand...
Click to collapse
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
any news on Android N at least not official
drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
you should
" fastboot oem lock "
to relock your bootloader - remeber - to save alll yor apps / settings (via TitaniumBackup for exaple) before
(re) unlocking bootlader will wipe all data
...
rtoledo2002 said:
I just got a OTA message to move from 3.39.531.7 to 3.39.531.12 I'm with T-MO and have it rooted with Teamwin recovery 2.8.7.1_CPTB-B1 on 6.0 Marshmallow
I just wish I knew how to do the upgrade all I do is go round and round, when I tell it to update it boots into the TRWP mentioned above and I have no idea what to do next.
guess I will wait until the smart people figure it out
Click to expand...
Click to collapse
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
rtoledo2002 said:
I just got a OTA message and doing the upgrade to 3.39.531.21 will let you all know how it goes.
since I had TWRP installed , I had to download the RUU from HTC to do the first update to .12 , it went well 2 weeks ago when I first posted here, except it wiped out TWRP. then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ?? I always loose 5 people I call all the time.
will post in here what new bugs crop up with this PART 2 upgrade of 7.0 nougat 63 things updating now
adios :cyclops:
Click to expand...
Click to collapse
here is a screen shot
rtoledo2002 said:
then 3 days ago my phone started complaining , when ever I tried to change permissions on apps , with a message telling me to turn off draw over on the apps, all the searches on google, sent me to people telling me it was Twighlight causing the problem , EXCEPT I don't have that app installed, then it said something about turning off sidekeyborad? I never found it, I hard reset the phone, and as usual it ruined some of my contacts ??
Click to expand...
Click to collapse
That's not a bug but a security feature introduced by google. It's meant to prevent malicious apps from making you accept things/permissions you don't want (keyword: tapjacking). Go to settings > app > open the three dot menu > configure apps > draw over other apps. There you can revoke that permission from any suspicious app.
There is an article about tapjacking on the xda portal if anyone wants more information. It's called "How tapjacking made a return with android marshmallow - and nobody noticed". Btw, the article explains why the security feature isn't perfect, too. (Using xda labs at the moment I can't add a direct link to the article. However google should be able to find it.)
I just hope for the classic Non-GP Sense UI. The one with the Grid View Recent Apps.
HTC One M9 is the last chance for the full Sense experience on Nougat, because is the last Non-GP HTC that is being updated.
Rollout started
rhisendark said:
any news on Android N at least not official
Click to expand...
Click to collapse
Read that Rollout started in America for Brand free devices
HTC root mobiles cannot install OTA, RUU are only way when rooted
drakeNas said:
Is it okay if i flash the RUU with unlocked bootloader or do i need to relock it?
Click to expand...
Click to collapse
Yeah you only need to flasb the RUU it would solve your problem

Beginner root question on opp2.170420.019

Hey guys,
This is almost certainly a stupid question but I would be grateful for any help. I have a Nexus 6p thats upgraded to the lastest Android O beta version of OPP2. I wanted to finally go around rooting it. I have enabled USB debugging, always allowed the PC's RSA fingerprint and checked allow OEM unlocking. Nothing else has been done before, I plan on following a step by step guide that will help me unlock bootloader, install custom recovery and root etc.
I tried googling and to my surprise I could not find any root guide for this version of Nexus 6p (maybe I am just blind?)
Just tossing this out there. Old, but should still do what you need. Now that I think about it, I should probably go ahead and update parts of it....
Android Job Box
Woah. Cheers mate! so i just need to plug my Nexus 6p in, execute the file and click on unlock bootloader? I assume i have to install super su after that and that will be it? :3 Sorry. I know i am asking stupid questions and you are obv a pro. Also the fact that my version is opp2.170420.019 makes no difference right?
chevycam94 said:
Just tossing this out there. Old, but should still do what you need. Now that I think about it, I should probably go ahead and update parts of it....
Android Job Box
Click to expand...
Click to collapse
No, shouldnt make a difference. SHOULDNT. lol
The first thing I would do is download TheFlash's TWRP build, and flash that using the tool once you have your bootloader unlocked. That can be a lifesaver. Let me know if you have any questions. Questions directly about the tool, please post in my tools release thread.
Allrighty then, ill take the plunge real soon! Thank you for all the help Any specific why I should go with TheFlash's build instead of this one: dl.twrp(dot)me/angler/? As far as I can see it only supports F2FS which I will probably not be using.
chevycam94 said:
No, shouldnt make a difference. SHOULDNT. lol
The first thing I would do is download TheFlash's TWRP build, and flash that using the tool once you have your bootloader unlocked. That can be a lifesaver. Let me know if you have any questions. Questions directly about the tool, please post in my tools release thread.
Click to expand...
Click to collapse
None, specifically. But he seems to always be ahead of the curve for almost everything he does. And I really like his work. Personal preference I guess.
Well your tool works well Bootlocker unlocked and TWRP isntalled. But i flashed the SR3-SuperSU-v2.79-SR3-20170114223742.zip and nothings happening. there is a super su app in the drawer but when i click it it says super su binary not installed. Dont suppose you would have any idea why this is?
Update: okay false alarm. installed supersu v2.8 and appears to be rooted now. although super su keeps on crashing.
Update2: actually no, not working properly. Some apps are getting root - others arent I guess
chevycam94 said:
None, specifically. But he seems to always be ahead of the curve for almost everything he does. And I really like his work. Personal preference I guess.
Click to expand...
Click to collapse
UsmanPirzada said:
Well your tool works well Bootlocker unlocked and TWRP isntalled. But i flashed the SR3-SuperSU-v2.79-SR3-20170114223742.zip and nothings happening. there is a super su app in the drawer but when i click it it says super su binary not installed. Dont suppose you would have any idea why this is?
Update: okay false alarm. installed supersu v2.8 and appears to be rooted now. although super su keeps on crashing.
Update2: actually no, not working properly. Some apps are getting root - others arent I guess
Click to expand...
Click to collapse
Only SuperSU 2.79 SR4 or Magisk v13 will have functional root on Android O.
Magisk:
https://github.com/stangri/MagiskFiles
SuperSU:
https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip
Even more unstable lol, built for OPP1 not OPP2 apparently. Phone actually crashing now and rebooting after a few mins. Meh, srsly cold feet, am out. Going to flash it back to stock. hope that works atleast.
chevycam94 said:
Only SuperSU 2.79 SR4 or Magisk v13 will have functional root on Android O.
Magisk:
https://github.com/stangri/MagiskFiles
SuperSU:
https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip
Click to expand...
Click to collapse
UsmanPirzada said:
Even more unstable lol, built for OPP1 not OPP2 apparently. Phone actually crashing now and rebooting after a few mins. Meh, srsly cold feet, am out. Going to flash it back to stock. hope that works atleast.
Click to expand...
Click to collapse
It works the same on OPP1 and OPP2. But all in all, you'll have better luck with Magisk v13.
I flashed it to 7.1.1 N4F26T using NRT and now the it has severe lag and keeps freezing and screen isnt accepting touch commands. Since this is a fresh install I assume the RSA fingerprint and USB Debuugging option has been unchecked as well? I have downloaded the official stock image of 7.1.2. Can I apply it using recovery or something?
chevycam94 said:
It works the same on OPP1 and OPP2. But all in all, you'll have better luck with Magisk v13.
Click to expand...
Click to collapse
Okay, flashed it to 7.1.2 using recovery. Everything seems fine now. Thank god. Helpful tip to any noob out there trying to root Android O Beta 2 on your nexus 6p: dont.

Categories

Resources