Okay, so ive been trying to get nougat to work rooted on my s5 neo 903w - i can, technically root, with the chainfire method through odin, but this process messes up some files and functions. torch stuck wont function, display brightness slider doesnt actually function, the LED stayed on a dim light blue despite no notifications, battery wouldnt charge while powered off, and who knows what else i didnt discover. but clearly as this was before i uninstalled anything via root access, that wasnt about to work. So then, after i reflashed stock *again* (and let marshmallow upgrade to nougat before rooting, the only reliable free way now that sammobile is charging for older OS, and since i cant even back it up wtihout twrp...) I want to try magisk rooting, but this needs custom recovery first. twrp will flash, supposedly properly in odin, but it doesnt stick. it just still goes to the stock recovery.
Anyone else faced this have any suggestions?? This is really frustrating!
Related
Last night I got a Galaxy S5 as an anniversary gift and successfully rooted and installed TWRP and Alliance Rom 4.4.2 and everything is going smooth for the most part except for fingerprint scanning.
When going to define a new fingerprint or access fingerprint options it gives an error: "An error has occurred with the fingerprint sensor...".
The process I took to mod it was use Odin to downgrade the kernel back to a towelroot friendly one, use towelroot to gain root, install busybox, flash previous kernel back using Odin, installed Safestrap (nandroid backed up), installed Alliance Rom via Safestrap recovery, installed SuperSU (disabled KNOX) and here I am. Does disabling KNOX cause the issue?
Any advice would be greatly appreciated! Thanks XDA
Yes I have searched forums and google before posting. Yes I wiped prior to installing the rom.
Unrelated problem: the phone also does not shut down. When going to shut down the samsung shut down animation plays then the screen goes black and just hangs there. The LED shows a blue light and the bottom soft keys are lit up and it will stay that way until I pull the battery. Any advice?
Hey guys,
So I've got a problem. When I had originally rooted my phone in the beginning, I hadn't installed safestrap; I installed everything else: busybox, superuser, etc. So I kept on regularly using my phone and what not, updating and making sure I kept root. I was able to follow muniz_ri's tutorials to stay up to date and keep root. So eventually I was on OE1 stock rooted rom and had stopped there (accidentally accepted an OTA update after OE1 so I quickly froze the update thing [forget what it's called] through TiBU, hence not being on the most current firmware).
I wanted Snapprefs but needed Xposed. And to get Xposed, you need safestrap (from my understanding). I followed this to get safestrap (I think that's what the overall goal of the tutorial was for) and got safestrap working. Then, tried to install xposed using this and this. Successfully got the app, but then it said something along the lines of "you have not installed the framework" or something like that (that would be the zip file that I had to download right? The file that came from following the flow chart?). Used safestrap to install the framework (aforementioned zip file), then rebooted. However, after the Samsung Galaxy S5 menu and the safestrap menu, the screen just stays black. There is nothing. When I have my phone connected to the computer, the computer makes its jingle like it recognizes it (however, nothing comes up on the computer), the phone stays black for 2-3 minutes maybe, then boots into recovery mode (not safestrap recovery but stock recovery, where you use the volume buttons). I did a wipe data/factory reset (or whatever the option is called) in the stock recovery menu hoping it would fix something but it didn't. Just trying to include as much info as possible. Would flashing with this in Odin help? Read somewhere that it would put me back at square one so I could do everything over again, which I am not opposed to. However, I thought you couldn't downgrade from OE1 or anything higher?
I'm at a loss as to what to do next. Searched everywhere but couldn't find anyone with the same problem as me. Any help would be appreciated.
Thanks guys!
P.S. Sorry for going parentheses crazy
Found out what to do right after posting. Had to flash the BOE1 factory tar image in ODIN so back to stock, unrooted with all this bloat
Will be checking back periodically in hopes of a root method for latest firmware.
I originally had OOS3.0.2, and I tried to get Beanstalk rom installed. Beanstalk didn't load correctly, and I softbricked my phone. I managed to go through the recovery of downloading the qualcomm drivers and that weird updating program and then sideload an older version of OOS (2.2). I went to this link and did method 1 https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/. But when I get things fixed up, I can't seem to update to CM13, or even to do a normal update with root, without root, with twrp, without twrp. Nothing. Strangely enough, no matter what I've been doing, the data I had from the very original pre-screw-up time is still all there. Every time I try an update it hangs on the 1+ screen and stays there. How can I get past this? I can't seem to upgrade, and I'm stuck in lollipop.
Well I was still able to get into my phone and do a stock recovery from the Update and Restore option from the phones settings menu, so that fixed it.
Just got the OTA update for nougat, every time I go to install it my phone crashes and switches off.
Anyone else having this problem?
Also, how to I flash stock recovery, I think it's to do with that STUPID twrp recovery that doesn't even work.
Megacamz said:
Just got the OTA update for nougat, every time I go to install it my phone crashes and switches off.
Anyone else having this problem?
Also, how to I flash stock recovery, I think it's to do with that STUPID twrp recovery that doesn't even work.
Click to expand...
Click to collapse
You need to flash back stock recovery. You can NOT update OTA updates when you have TWRP, it will crash, just what happened to you.
Use SPFT and flash back stock recovery for the current rom you are on. You can extract it from the scatter file. (If you don't know what that is, GOOGLE IT!!!!!!!!!!!!!!!!!!!!!!)
Btw I would avoid the update for now. It's buggy to say the least and you will loose fast charging.
Yea this OTA still needs improvement. Fast charging gone, fingerprint STILL not working, battery drain. Practically, latest Marshmallow is better then this OTA.I regret upgrading. If you gonna need downgrade use SPFT, their is a simple guide in umi community.
I did install iit and now I can not phone out or receive a call on Bluetooth phone Buzzzes loudly and the net work closes out, I use the bluetooth because of my hearing aids as the volume of the UMI super isn't very loud. I don't know how to fix this short of resetting back to origional except that way I loose all my info and have to start again. waiting for an answer.
Hello there,
Today I flashed TWRP 3.0.2-1 using Odin 3.10.7 on my sisters Galaxy A5 2016 (sm-a510f). After that, I installed SuperSU 2.78 using TWRP.
Since that, the WiFi does not turn on. When you press the button to turn it on, it shows the "loading circle", and seems to do nothing. The circle stays forever.
Other than that, the phone appears to work fine. It did never report any error messages.
I already tried wiping cache, dalvik and data. I also made a factory reset using the option in the settings.
Later I found a newer version of TWRP (3.1.1-0) by Zonik . Flashing this did not fix the problem.
Do you have any ideas on what I could do to make it work again?
Edit:
In the meantime, I flashed a custom rom. Everything appears to work fine at the moment.
I didn't want to do that initially, so the phone could get the stock updates without me doing anything.
But still I am interested, what steps should I have done, to keep stock? And where might I be able to download the stock rom?
You should have flashed a later version of SuperSU.
You can use Samsung Smart Switch to restore factory settings.
Alternatively you can always find the latest firmwares on updato.com
Oh, I have just seen that I forgot to reply to that. I'm sorry.
@ashyx Thank you, I'm going to do that the next time. I was following a manual someone wrote on the Internet. I should have been smart enough not to trust a manual that's been lying around for some time.
@Vinhixus I tried that. Samsung Smart Switch did not like to do that (Don't ask me why, it said the device is not supported for factory reset).
Finally I "fixed" the wifi-bug by installing a custom rom wich i did not want to do in the first place because I did not want to change the OS on the device, just the bloatware samsung puts on their device.
Not much of a fix, more like a dirty hack to me
Thank you for your support
Actually you needed to flash correct modem. The custom ROM fixes it because modem was compatible for it. For the stock one you need modem that matches it i guess.