Okay, let me start out by saying that I don't really know much about this stuff.
Anyway, I messed up and deleted some photos that were important for my job and in a panic I used some questionable software in attempt to "root" my phone, in hopes of retrieving those photos.
I never got the photos back, but now I have some type of security issue with my phone. Basically, during the boot screen, I get a custom/unlocked logo, and when it boots up I get the following security message: "Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes". In addition, I cannot use my fingerprint sensor, Samsung Pay, or install updates.
After doing a little research, I downloaded a couple apps to see if 1) my phone was actually rooted (SuperSu) 2) if Knox had been tripped (Knox Status). The answer to both is "no", so hopefully that is a good sign.
Is there anyway to restore my phone to normal, or did I do something that is non-reversible?
Anyway help would be greatly appreciated!
Flash a Sammy Rom via Odin in download mode and you should be good to go.
Related
Morning all,
I apologise if this is in the wrong section but I am new to the forum and in a bit of pickle.
Around a week ago I rooted my lovely new note 3 to hopefully one day install some nice new ROM to get rid of the horrid touch wiz and actually see the full potential of the phones power. However, for some silly reason while I was using titanium backup on my phone I thought it would be a good idea to uninstall touch wiz thinking it would magically go back to basic android however it didn't. It is completely broken now, woops. The first issue I had was it would boot up and stick to the Samsung logo and just glow so I thought it would be an idea to install stock ROM via ODIN to try and revert it back to normal. Once I downloaded the correct stock ROM it was uploading through download mode however at the last minute it failed with a ext4 error which I think it means it's bricked? Not sure, completely new to this. I am now a bit stuck as I am not 100% sure what to do next.
The phone will only boot into either the firmware upgrade has encountered an issue, basically Odin mode or download mode. I have tried recovering it through kies however it cant connect to it. It knows it is there as it will start searching for it when it's connected however says it can't find it. It wont boot into recovery mode.
My phone is a note 3 SN SN-9005. The system status is custom, reactivation lock is off, Knox kernel lock 0x0, Knox warranty void 0x1 and write protection is enabled.
Obviously I would like to get the phone back to normal, I don't care if it has to be completely wiped and brought back to normal I would like it to just work. I've been an complete idiot and fiddled with something I'm not 100% sure on and I would like to not have a 600 quid paper weight hehe.
I have tried putting stock firmware back on but it always fails with an ext4 error.
I will greatly appreciate any help or feedback.
I have recieved some good feedback on this so far however I am unable to get it fixed properly.
apdnote said:
Morning all,
I apologise if this is in the wrong section but I am new to the forum and in a bit of pickle.
Around a week ago I rooted my lovely new note 3 to hopefully one day install some nice new ROM to get rid of the horrid touch wiz and actually see the full potential of the phones power. However, for some silly reason while I was using titanium backup on my phone I thought it would be a good idea to uninstall touch wiz thinking it would magically go back to basic android however it didn't. It is completely broken now, woops. The first issue I had was it would boot up and stick to the Samsung logo and just glow so I thought it would be an idea to install stock ROM via ODIN to try and revert it back to normal. Once I downloaded the correct stock ROM it was uploading through download mode however at the last minute it failed with a ext4 error which I think it means it's bricked? Not sure, completely new to this. I am now a bit stuck as I am not 100% sure what to do next.
The phone will only boot into either the firmware upgrade has encountered an issue, basically Odin mode or download mode. I have tried recovering it through kies however it cant connect to it. It knows it is there as it will start searching for it when it's connected however says it can't find it. It wont boot into recovery mode.
My phone is a note 3 SN SN-9005. The system status is custom, reactivation lock is off, Knox kernel lock 0x0, Knox warranty void 0x1 and write protection is enabled.
Obviously I would like to get the phone back to normal, I don't care if it has to be completely wiped and brought back to normal I would like it to just work. I've been an complete idiot and fiddled with something I'm not 100% sure on and I would like to not have a 600 quid paper weight hehe.
I have tried putting stock firmware back on but it always fails with an ext4 error.
I will greatly appreciate any help or feedback.
I have recieved some good feedback on this so far however I am unable to get it fixed properly.
Click to expand...
Click to collapse
http://www.youtube.com/watch?v=_sMnC6UkJBI
this is a vid on how to unroot i know its not what you want but dose show you how to get back to stock with odin
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.
Hi, I'm sorry if this isn't the right place to post this but Im having to use someone else's windows phone and its hard to navigate through the site.
My problem is that I tried to root my s6 edge plus using an application called King Root. The install got to 17% and then turned the phone off. When I load the phone up now I just get the message "custom binary locked by FRP lock" in red writing and the phone instantly boots off.
Is there a way to get around this without losing my data on my phone? I have some very important photos that are on there that I really don't want to lose, unfortunately nothing is backed up. I've been researching and apparently this is possible using a programme called Odin? I hope this is possible as I don't want to lose my stuff on my phone.
Any help would be great, thank you.
To be brutally honest if you haven't heard of Odin and you're using Kingroot, you're way out of your depth and you shouldn't be even thinking about rooting your device.
Not being nasty, sincerely. But you need to do a LOT of research.
The only way to rescue your device is to flash a stock firmware via Odin. There are guides on this site, read them and then read them again and again. Your photos are probably gone unfortunately. I would say definitely, but mircles can happen..
Good luck!
Maybe just flashing the stock bootloader may help but once you atart flashing the pda i think your photos may be gone. Unless where ever they are stored doesnt get over written they may be recovered uisng a data recovery app on the play store like gt recovery and the deep scan option.. it still finds photos from 5 new rom installs on my opo
Hey all,
I'm trying to get my brother's Verizon S6 Edge+ out of a bootloop due to the lastest OTA gone bad.
My thinking is if I could find that OTA somewhere online, I could ODIN it in, and maybe clear it the problem. I don't know if that'll work, but I can't test my theory because I can't find the OTA for download anywhere.
Smart Switch doesn't work because even though I can get into Download Mode and run Smart Switch's Emergency Recovery all I want, I enter the model number SM-G928V and it asks for the S/N next. No matter what I try, nothing works. I've gone through the logs, pulled serial number from the build.prop. I've tried everything on the original packaging. I've tried the IMEI and all the barcodes right before entering Download Mode - just no S/N registers.
I can reflash the old firmware, PJ3, on there via ODIN, and each time I reflash it tries to install the OTA again. It runs through the update up to 32% and then I get a droid guy on his back with a yellow triangle - every. single. time.
I don't understand where the heck this OTA is stored and how the hell I can zero it out or remove it. I've tried popping in a new PIT, repartitioning, etc. Hell, I've tried a NAND RE-WRITE (against everyone's cries this is a terrible idea).
Does anyone have the very latest G928VVRS3BPL3 that was pushed Dec 29, 2016 to VZW S6 Edge+ devices? I'm even willing to PayPal for a good copy that will ODIN into the VZW S6 Edge+...
Alternatively, if you don't have a copy of PL3, do you know of anyway I could ADB my way into wiping the corrupt PL3 patch away? I can't seem to ADB right now, but maybe you know a trick I don't? I'm thinking I could perhaps zero out the instructions that initiate the patch at launch or something? If I can simply boot up - fantastic, but I'm in this infinite boot loop of installing PL3 to 24% and going belly-up.
I'm almost embarrassed to say I PAID for a copy of PJ3... but I can't find this latest Dec 1st security update patch anywhere on the web.
The phone is out of warranty. Contrary to Verizon store morons (sorry!), my brother didn't try to root the phone. He doesn't know how to do any of that stuff. The OTA is corrupt - plain and simple. Knox isn't even tripped. They accused him of trying to root the thing - heh.
Since the phone is out of warranty, no one will fix it for him. I'm his only hope, and I'm not much of a hope right now.
You're MY only hope.
This is a great phone, too. I feel bad for the guy. He woke up to his phone dead one morning. That's it.
So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.
Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!
Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.