Hey guys, i am looking for some help on how to upgrade my rooted s7 edge from MM to Nougat.
First of all let me tell you that I bought the phone used and rooted, it worked perfectly for some time until one day it had the Custom Binary blocked by FRP error. I tried to fix it by myself flashing a new rom. Everything worked fine except for the Signal and Data. I didn’t have any. I couldn’t fix it so I went with a guy that repairs these things. Nowdays I have the phone working on MM, but I would love to have Nougat.
I don’t know exactly what he did to make it work, I just noticed the phone has another IMEI and SuperSU with ADB Shell on it.
The problem is that the man told me I cannot update to Nougat or the “fix” he did would stop working. I want to know if there is a way to do it because I want to have the latest update.
I would just go stock and upgrade.
Related
For a few weeks now, I have been unable to update my galaxy s5 to lollipop 5.0. I the download the update perfectly fine, but when I go to install it, it loads for a minute then says error. Now my phone was rooted, but one day it became unrooted. I tried to reroot it but it didn't work at all. I have a feeling when it unrooted, it didn't fully unroot? So I may have done something wrong here.. if anyone has similar issues and knows what may be wrong can you please help me!! I have reset my phone many times and nothing works!!
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
MGArcher007 said:
Hey everyone!
I've got an interesting predicament here. A little back story: a while back I installed TowelRoot, and then Xposed Framework. Everything was kosher until I got an OTA update (I believe the NG3 update) and it killed the root. No problem, I'm fine without root. But now that Lollipop has come out, I want to update but can't. My buddy applied the same root, but did not do Xposed. The difference between our phones after that OTA update: mine says "Custom" with an unlocked padlock at the Samsung boot screen; his does not.
I read in another thread that someone took their phone to Best Buy and the guys at the Samsung booth were able to fix the problem because they can pull updates and apply them via USB. So we went there yesterday and they had no problem getting Lollipop on my buddy's S5 Active. Mine, however, would not take the update. The Samsung S.M.A.R.T. tool they use on the PC was saying that "my device is running an unauthorized operating system", even though I have never flashed a custom ROM.
When I go into download mode, the Knox flag does not appear to be tripped. I've also performed a clean factory reset with a data wipe and that still didn't allow me to update. Whenever I try to update, it downloads the entire 4.4.4 update (which needs to be done first, before the 5.0 update) and it starts to install, failing at 25%, without hesitation, every single time.
I've attached a couple of screenshots that I hope will help. Any ideas will be greatly appreciated.
Click to expand...
Click to collapse
Have you resolved this issue, if so, would you mind sharing how you did it. I've been combing the net for a few days trying to discover what is going on and your issue appears to be exactly what I am experiencing. I've read about flashing back to my stock firmware using Odin but I cannot get into download mode, when I try and get there, the phone only says "recovery reboot" in blue small font on the top of the screen and reboots.
Thanks
Ladies and gents, I apologize for abandoning this thread. I forgot exactly how I got to get the phone to update, but if I recall correctly, it had to do with me putting the phone in download mode, downloading the original firmware and using ODIN to flash it. Afterward, the "unlocked" padlock symbol disappeared and the phone was able to get the OTA update from AT&T.
I have since moved from an LG G4 to a V20 and that is what I am currently playing with. I also have a Samsung Galaxy S6 Edge (which T-Mobile replaced my G4 with when the touch screen stopped responding). I was quite stoked to find out that there is a way to root it and (seemingly) unlock the bootloader, so I'll be toying with that this weekend to see what I can do. I'd love nothing more than to just wipe that Samsung-ified Android and install a vanilla Android or CM.
Good luck to anyone who is still trying to fix this issue. Again, my apologies. I'll dig through my archives and see if I can piece together what I did to get it going again. I still have the S5 Active. Best phone by far. It's a great backup phone for when the new stuff goes kaput.
Hey guys, i am looking for some help on how to upgrade my rooted s7 edge from MM to Nougat.
First of all let me tell you that I bought the phone used and rooted, it worked perfectly for some time until one day it had the Custom Binary blocked by FRP error. I tried to fix it by myself flashing a new rom. Everything worked fine except for the Signal and Data. I didn’t have any. I couldn’t fix it so I went with a guy that repairs these things. Nowdays I have the phone working on MM, but I would love to have Nougat.
I don’t know exactly what he did to make it work, I just noticed the phone has another IMEI and SuperSU with ADB Shell on it.
The problem is that the man told me I cannot update to Nougat or the “fix” he did would stop working. I want to know if there is a way to do it because I want to have the latest update.
I Haven't rooted my phone yet but it keeps telling me this when I open android pay, when I first got my phone I set my up my card but now it saying that phone is either rooted or bootloader unlocked which isn't the case.
On Vodafone UK, before this I used my OP3 with Magisk with Android Pay but I haven't used that since I've got my s8 so I'm not sure what the issue could be.
Any insight to this?
Besides the usual factory reset.
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
I'm having the same issue on a Galaxy S8 via Tmobile. I've never rooted it, have no clue if the bootloader is unlocked and I'm stock since I reset the phone the first time I got the error. Still getting the error and Android pay help chat was not useful.
Same issue here, on Voda UK. I used Package Disabler pro and thinking I might have disabled something I need.
So since I had OEM unlock enabled after disabling it, it passes and safetynet now.
I had no problems adding cards, but a few days later when I wanted to add more cards, I get the error. I can't remember what I did in between that would've caused this, but definitely not rooting! I turned developer option to off and still get the error.
My S7 is rooted and TWRPed and have no problems adding cards!!!!???
Very weird. Working just fine on my rooted s8+ with magisk.
I'm on T-Mobile with a S8 and Android Pay connected to my PayPal is getting card read error everywhere I try to use it.
Safety net says everything is ok too. Not sure what's going on. I have the newest update and not rooted.
Sent from my SM-G950U using Tapatalk
I installed different Samsung Pay Framework apk and now I want to revert back and downgrade to another version to make Spay work.. when I click uninstall updates it wont let me. (Gives message that App is needed by system administrator.. when I open sys admin nothing there. hidden app)
Any ideas or suggestions on how to downgrade Samsung Pay Framework?
Thank you in advance,
Joe
xeathpk said:
Very weird. Working just fine on my rooted s8+ with magisk.
Click to expand...
Click to collapse
Hi Can you let me know how you managed to root with Magisk and get Android pay etc to work?
My phone:
Model: SM-G955F
SW: G955FXXU1AQF7
I tried rooted and couldn't get it working, and now recovered to official ROM and still can't get it to work?!?
Dont you people know anythin?
All EU(exynos) S8 and other galaxies come with unlocked bootloaders. Thats causing the problem
Lock it
Hi all,
I already posted a question in the Official stock upgrade but it got lost in the other comments, so I'm trying my luck again.
I had an italian branded SM-G950F (OMN), I wanted to remove all the Vodafone stuff, so I installed a MULTI-CSC as per the official stock firmware upgrade thread, when I did it I had my Australian sim card in and I got a weird UK CSC (the multi CSC didn't have australia in it), after installing everything I noticed that Android Pay didn't work, so I did a factory reset with my italian sim card in and still Android Pay was complaining that my firmware was modified or rooted.
I decided to use an australian specific firmware so I downloaded an XSA firmware and did the procedure again.
At this stage Secure Folder and Samsung Pay work (the phone is NOT rooted, this update has been the only "mod" I have done) but Android Pay is still saying that my rom may be modified or rooted so it doesn't open.
It is pretty important for me because my back supports android pay but not samsung pay
The phone is not rooted, if I reboot the phone in download mode the warranty void bit is 0 (which is good).
If I use Root Checker Pro, under safety net tab, I get CTS profile match as FAIL, I was thinking this could cause Android Pay to fail.
any idea?
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
degsyh said:
same here EE UK S8 not rooted (yet) but comes up with same error message. It worked fine on my rooted and hidden with magisk S6
edit - oh and factory reset doesn't work as I already tried that. I thought it might have had something to do with bringing over magisk app from my google backup but I specifically didnt install that the 2nd time around. Knox hasn't been tripped so its not that
Click to expand...
Click to collapse
Does rooting in UK\Europe void our warranty?
mariuscrist said:
start to uninstall suspicious apps, then restart . worked with my un-rooted S8. OEM unlock: OFF
Click to expand...
Click to collapse
Hi mariuscrist,
I'm not sure what app can be suspicious, I have reinstalled the apps I had before the firmware update and I could use android pay then. I'll see what it can be, probably it could be worth to do a factory reset and test android pay before anything else?
hey-o, So i wanted to root my phone quick and easy just afew ahours ago, after i odin'd in TWRP on my S7 Edge, it couldn't read data, i was pretty confused, i restarted my phone, told me verfication had failed, and in base, the entire OS has basicly went corrupt, am really not sure how, but has anyone else had this problem? SM-G935F EE UK, need more info i can provide.
Correction, I installed the EE firmware AFTER i had to fix my phone due to what TWRP did, My phone is actualy BTU Firmware.
Knox has been tripped.
Video visualization: https://youtu.be/o-9aKxWXaG8
Minerspark said:
hey-o, So i wanted to root my phone quick and easy just afew ahours ago, after i odin'd in TWRP on my S7 Edge, it couldn't read data, i was pretty confused, i restarted my phone, told me verfication had failed, and in base, the entire OS has basicly went corrupt, am really not sure how, but has anyone else had this problem? SM-G935F EE UK, need more info i can provide.
Correction, I installed the EE firmware AFTER i had to fix my phone due to what TWRP did, My phone is actualy BTU Firmware.
Knox has been tripped.
Video visualization: https://youtu.be/o-9aKxWXaG8
Click to expand...
Click to collapse
Update: After serveral attempts, i finaly got it running a CFW, i had to flash the OFFICAL firmware, and leave download and reenter it before the phone even boots and then flash TWRP, and i installed magiskmanager and everythings looking alright from here, i'll update if i have any problems.
3rd update, i offical cannont find the firmware this phone was on, it WAS SIM-FREE when i bought it, now i installed this version every app crashes on launch, am pretty lost myself. anyone know a way i can get or know the Very first firmware?
Considering i've got literly no help, this thread can be closed, i installed some random stock firmware and i suppose i will have to put up with broken settings menu and a barly working keyboard for now.
Minerspark said:
Considering i've got literly no help, this thread can be closed, i installed some random stock firmware and i suppose i will have to put up with broken settings menu and a barly working keyboard for now.
Click to expand...
Click to collapse
If you are US flash the smg935u as it works for every carrier