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.
Related
After unboxing my new nexus it downloaded an update to Android 4.3 (probably the new patch to the OS). It gets as far as rebooting then when applying the update I get an Error and the Android laying on its back... A reboot brings me back to life however still with the old ROM. Has anyone else experienced this or can tell me how I can fix it? I have tried resetting the device back to how I got it but the problem still persists. Any help is appreciated.
if you are totally stock then you are probably suffering from the corrupt /system issue.
Try flashing factory images using this technique:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
I have read around regarding this problem without luck, and hope that someone can advise if I have missed anything.
I used to use this phone and as I liked to tweak it was running a custom rom (think it was Wanams). Anyway I got an upgrade ages ago, and my wife carried on using the phone for a while. As she just needs a standard rom I recently decided to factory reset and use Odin to flash the newest stock rom (N7100XXUFNE1 - UK). This is when the problems started. Initially the Wifi wouldn't come on, but after factory resetting and using the Samsung Updater in Kies I finally managed to get Wifi back. Then, while setting it up and installing apps from the Play store it started freezing and had to be rebooted every 5 or 10 mins. Finally after doing this a couple of times, all the apps were installed and after leaving it to "settle" it seemed to be better. Now however, 2 or 3 times a day, when playing games or using other apps, it will just reboot.
What I have tried is:
* I have tried clearing cache through the stock recovery
* Tried a number of Factory Resets
* After reading about the SDS problem I have tried running the "dummy file generator" to fill the internal memory and this completes ok. I guess this means that although I have memory that is/was susceptible I applied the original SDS fix early enough with the custom rom that all the memory is still ok?
As I have the newest bootloader I can't downgrade that, but as I don't care about triggering Knox I was thinking of rooting and installing a custom rom to see if any of the other Kernels help?
Has anyone got any idea's what could be causing this and what I can do to fix it?
Thanks.
Got my Note 4 rooted it right away with no issues been running smoothly for a week or so. This weekend it has just got into a bootloop several times, the only thing I have been able to do is wipe data and start over. I mean I have Titanium Backup of all the apps but it is still a hassle. The only thing I have noticed is in the stock recovery it says "dm-verity failed"
I have read running a non-stock kernel will take car of this but not sure this is the issue. Has anyone else had this issue or have a solution?
It's the root. That root is causing that error to pop. Un-root your device.
I am trying to correct this issue as well for s friend who bought a used note smn910p.
It boots up
Its in the abnormal factory reset, reactivation loop i have to provide samsung account from unknown previous owner
rooted s5 smg900r4
fixed dm verity issue using kies3, updated firmware and initialization option.
rooted s5 smg900r4
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..
Hey guys,
My Pixel 2XL initially had some reboot issues so I decided to root it, and was able to do that successfully with magisk on stock firmware with some modules installed as well. It regained its functionality for the most part but unfortunately the Wifi stopped working (kept searching, could'nt find any network). It would sometimes randomly work on some reboots but whenever it did, the phone would auto-reboot after a while and lose the function again (but would work perfectly otherwise).
So I decided to unroot and factory reset with stock firmware thinking it might be a partition defect, just to see if that fixes it but it didn't. And what's more, the phone has once again returned to bootlooping like before root. Can anyone help me find out the issue here? And if I can manage to root it again and get it working, is there some way to resolve this issue (maybe through a custom kernel)?