SU update problem - Desire General

Have rooted htc desire, tried update fixer… it just crashed. Downloaded SU 307 zip in to SD, installed from recovery mode.. all went fine.. it said complete and enjoy. Checked my root with root checker, it still says my SU ver is 2.1. . any help will be much appreciated.

BUMP ? Anyone ?

I had all kinds of problems with SuperUser after rooting and flashing a new ROM. In my case, doing a factory reset solved the problem.
The main issue I had was that, no matter what I tried, SuperUser wasn't remembering permissions.
I think I may have mistakenly upgraded through the Market, which doesn't work. I then tried flashing new version but never got it working properly so took a deep breath and did a factory reset - and of problem!

Related

[Q] Back to stock, touchscreen does not work after OTA update

I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-ht...-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. Anyone have idea how to solve this?
I tried different boot.img after the OTA update but none of them solved the problem. Somebody here who has a good idea?
Xanion said:
I did a restore of my One-X to stock rom according to this tutorial.
http://design-extreme.net/restore-ht...-to-stock-rom/
This all went well and without problems. The RUU I flashed is this one.
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Ra dio_5.1204.162.29_release_302015_signed
When I now startup the phone it all works perfect. Then the phone says there is an OTA (to 3.20 I believe)
I download and install the OTA and the phone restarts, but after restarts the phone's touchscreen does not work anymore.
I solved this for now by installing the 3.14RUU again, then it works again. But of course I would like to be able to install the OTA's
To me it sounds like a driver problem in the new version that prevents the touchscreen from working. Anyone have idea how to solve this?
I tried different boot.img after the OTA update but none of them solved the problem. Somebody here who has a good idea?
Click to expand...
Click to collapse
Kicking my own question. No-One who has an idea or thought? I've tried everything I could think off and would appreciate some fresh thoughts.
I have almost the same problem now. I was running CWM 10.2 with the TWRP recovery and reverted back to stock using a backup from this thread: http://forum.xda-developers.com/showthread.php?t=1975140
The installation went fine, but touch isn't working anymore. What could be wrong? I would like to have my phone back to stock and use the OTA from HTC.

[Q] bootloop after supersu binary update

today i updated supersu to 2.17 and it attempted to update the binary but once it shut off it stayed in a bootloop, how do i fix this without having to wipe everything
Same problem here on S4 I9505 International version after automatic update via Google Play just now (2.12.2014, 15:50). Not sure which version i downloaded. Problem seems to have started after it asked the SuperSu binary to be updated by TWRP. The boot loop here occurs after I enter the pin code, apparently after loading various programs (which all are terminated), then reboot is triggered.
Downloaded UPDATE-SuperSU-v2.37.zip but found no way to get it to the S4...
I still have SuperSu-2v.27 on S4, so I reflashed that. Still on bootloop!
Backed up the S4 with TWRP, where I keep previous backups (just in case ...) and recovered my previous backup (one month old).
We'll see if I can update to v2.37 after that.
Flash a rooted ROM should fix this issue. I never install with twrp. Never had this issue.
Deleted. Old post made relevent from a completely different phone user/variant. ...

[Q] Did I lose root? (stock to slimkat)

I recently switched over to slimkat version 8.10 and everything is working like butter so far. The only issue I have come across is anything that needs superuser permissions automatically gets denied. It shows the option on the screen to allow but when i click the field it just does not select., landscape or vertical. I aleady followed the steps to enable developer mode and turn on root access. What could be happening to cause this? It always takes me an hour to configure everything the way i like it so reinstalling would be the last thing I would ever want to do.
I just attempted to use Odin to install cf-auto-root. Still not working. I guess I might opt for the final option... wipe and reinstall rom.
Try flashing supersu from here in recovery:
Super SU 2.16
https://plus.google.com/app/basic/stream/z13tvntrmsmozdc2023wcdp55terwvove
Somehow 2.13 was included with the cf-autoroot that I installed via odin. I did install 2.16 through recovery but I am still having this problem. I mean it doesn't really hurt the usage of the phone... everything is working flawlessly. This is just a rock in my shoe. The only thing I can think might be causing me an issue is that I flashed the dkp kernel. Could that be it?
When you flashed dkp did you clear cashe and dalvik?

Zenfone 2 ZE550ML wont update to latest update 2.18

The update showed up on my phone and so I updated it after unrooting my phone, removing lucky patcher, freedom, sd booster, and so on. After downloading the update, phone rebooted showed it was updating then Error. Rebooted the phone then the update was no longer there, tried using System update but to no avail.
My question is.. how do I fix this for me to be able to update to the latest?
I'm getting a similar problem. However instead of doing what you did to unroot and such, I flashed the 2.17 via their recovery and now I don't get the prompt for 2.18 update at all.
Its confusing as to why its acting like this :/
I already removed all root applications and unrooted the phone then did a factory reset but afterwards it put me to one of its old build and wont freakin update anymore.. Any help regarding this would be very much appreciated..
I am open to rooting and manually flashing the latest build.. Problem is, I was a Sony user whom just switched to zenfone.. So i have no idea how to or what to flash on our zenfone 2..

Issues with OTA update

Hi, I'm trying to update my phone to the latest version. It is rooted with Magisk and hasn't been updated at all since I got it a year and a half ago. The methods I have found so far for updating with root are not working. Every time I try to open System Updates in my Settings, it force closes on me so I can't access it.
Is there a work around for this? I have tried using Oxygen Updater and that failed also. Can I manually install the OTA update and preserve root somehow?
Please help, I haven't found any solutions. I got an error 1 using TWRP, which seems to mean that my boot.img is corrupt?
I managed to solve this by doing a factory reset/data wipe, which was my last resort (and a huge pain to have to restore everything). I still don't know what caused the issue, although I have some suspicions.
But in case anyone else encounters this error, it is definitely not the boot.img and I had no problems retaining root.

Categories

Resources