Hello.
So, I rooted my T-Mobile Samsung Galaxy Note 4. It went flawlessly. I flashed TWRP and rooted it without a hitch. Now fast forward a few months, to today. I decide to restart my phone again. Nothing has changed, except that my "helpful" antivirus "conveniently" turned off USB Debugging. I restart it and it brings up a screen. It has a "caution" sign with the exclamation mark. Some text is there as well, saying:
Custom binary blocked by FRP.
SECURE FAIL: KERNEL
Granted, I was upset. My phone won't boot up. I've tried booting into TWRP, but the same screen appears. I can't use Odin because USB Debugging was forcibly shut off by my antivirus.
If I don't have my cell phone, I will struggle in school, as the only other device I have is this laptop which has no working battery and runs on outlet power alone. I don't have the money to purchase a new device, and I feel like I'm out of options, so if I don't get some help, I'm a dead man. If anyone could help, I'd be very grateful. On the Odin Mode screen, info is as follows:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910T3
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: ON
KNOX WARRANTY VOID: 0X1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I don't know how much of that is relevant.
Help me, XDA Developers. You're my only hope.
Thanks,
A stupid Wizard with a bricked phone.
Did you try to use Odin to reflash twrp or the stock firmware? You dont need usb debugging on to reflash stock firmware. If you were on stock, i would just reflash with Odin, tuen on usb debugging and reroot. If u were on custom rom, you might have to odin back to stock, and then do factory reset from recovery.
RaySCLA said:
Did you try to use Odin to reflash twrp or the stock firmware? You dont need usb debugging on to reflash stock firmware. If you were on stock, i would just reflash with Odin, tuen on usb debugging and reroot. If u were on custom rom, you might have to odin back to stock, and then do factory reset from recovery.
Click to expand...
Click to collapse
I tried to reflash the TWRP, but it failed. An error message appears:
Custom Binary(recovery) Blocked By FRP Lock
ShadowedWizard said:
Hello.
So, I rooted my T-Mobile Samsung Galaxy Note 4. It went flawlessly. I flashed TWRP and rooted it without a hitch. Now fast forward a few months, to today. I decide to restart my phone again. Nothing has changed, except that my "helpful" antivirus "conveniently" turned off USB Debugging. I restart it and it brings up a screen. It has a "caution" sign with the exclamation mark. Some text is there as well, saying:
Custom binary blocked by FRP.
SECURE FAIL: KERNEL
Granted, I was upset. My phone won't boot up. I've tried booting into TWRP, but the same screen appears. I can't use Odin because USB Debugging was forcibly shut off by my antivirus.
If I don't have my cell phone, I will struggle in school, as the only other device I have is this laptop which has no working battery and runs on outlet power alone. I don't have the money to purchase a new device, and I feel like I'm out of options, so if I don't get some help, I'm a dead man. If anyone could help, I'd be very grateful. On the Odin Mode screen, info is as follows:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910T3
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: ON
KNOX WARRANTY VOID: 0X1 (2)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
I don't know how much of that is relevant.
Help me, XDA Developers. You're my only hope.
Thanks,
A stupid Wizard with a bricked phone.
Click to expand...
Click to collapse
FRP is referring to "Factory Reset Protection" , that means you had the Samsung Reactivation Lock turned on and the phone detected a change in the software preventing it from booting up. Now there are two ways to get the phone back up, first try going into download mode (Holding power button+volume down) then restart it by holding down power+volume up) if by chance this doesn't work then the other option would be to use odin and reinstalling the stock rom but it would need to be the same version currently installed.
glm0025 said:
FRP is referring to "Factory Reset Protection" , that means you had the Samsung Reactivation Lock turned on and the phone detected a change in the software preventing it from booting up. Now there are two ways to get the phone back up, first try going into download mode (Holding power button+volume down) then restart it by holding down power+volume up) if by chance this doesn't work then the other option would be to use odin and reinstalling the stock rom but it would need to be the same version currently installed.
Click to expand...
Click to collapse
How would one install a ROM directly from Odin? I know how to do it from the recovery, but I can't access it.
EDIT: After more research and a helpful PM, I am using Kies to wipe everything and restore the stock ROM.
EDIT 2: Success! After resetting using Kies, I was able to reflash TWRP and get rooted again. Thanks to everyone who helped.
ShadowedWizard said:
I am using Kies to wipe everything and restore the stock ROM.
Click to expand...
Click to collapse
No. You should have used ODIN (from your desktop / laptop PC) to restore a stock ROM so that you could have kept your data
Anonymously_Unknown said:
No. You should have used ODIN (from your desktop / laptop PC) to restore a stock ROM so that you could have kept your data
Click to expand...
Click to collapse
I had attempted to do restore the stock ROM, and I recieved the same error as with reflashing the recovery.
I restored to stock with Keis, then flashed TWRP, re-rooted, and installed a new ROM. I then restored my important data (contacts, app info, etc.) from a Titanium Backup on a microSD.
And don't turn on factory reset protection. Useful for casual users who don't root and install cudtom ROMs, but a real problem for those who do.
I believe there is a null/dummy ODIN file floating around you can flash in Odin that will clear that message and get it to boot again.
You're getting it because your lock is on and it's trying to flash something, and will continue to try every time you reboot, there doesn't seem to be a way for it to clear itself after unsuccessful attempts.
edit: pretty sure this is the one I used, but I'd recommend doing your own research before blindly taking my advice:
http://forum.xda-developers.com/showthread.php?t=1766399
RiverCity.45 said:
And don't turn on factory reset protection. Useful for casual users who don't root and install cudtom ROMs, but a real problem for those who do.
Click to expand...
Click to collapse
What is a good way to get that same protection that for a rooted/custom rom user?
blindskater39 said:
What is a good way to get that same protection that for a rooted/custom rom user?
Click to expand...
Click to collapse
There an app floating around that bypasses the reactivation lock.
gal419 said:
There an app floating around that bypasses the reactivation lock.
Click to expand...
Click to collapse
I am wondering if there are security app made for rooted devices to prevent a thief from stealing flashing or getting sensitive information in the device.
Is there a way to disable the FRP so it doesn't accidentally get turned on?
Related
I bricked my SM-T900 Wifi while attempting to root it. Can anyone help me get it un-bricked?
Here's a step by step list of what I did and what happened:
1. Turned on USB debugging mode
2. Downloaded and installed Samsung kies
3. Downloaded the file for SM-T900 from autoroot [dot] chainfire [dot] eu/ (it won't let me post outside links)
4. Turn off tablet, get into custom firmware installation mode by holding power, volume-, and home, then confirm the warning
5. run Odin (v3.07, came in the zip file)
6. plug in tablet, tablet showed up as a com port but did NOT show any other information. I don't know if it was supposed to show anything else but I hadn't though about that at the time.
7. Clicked on PDA and selected the file CF-Auto-Root-v2wifi-v2wifixx-smt900.tar.md5
8. Clicked start
9. Waited, it said it was doing something with cache, I don't recall exactly what it said
10. after about 3 minutes the screen looked wrong, all the pixels were different colors, (rainbow static?)
11. Waited about 10 minutes just in case that was not a sign of failure, then Odin reported that it failed.
Now when I press the power button, I get the screen that says "Firmware upgrade encountered and issue. Please select recovery mode in Kies and try again"
I tried using that in Kies but Kies can't connect to my tablet any more. When I try to use Odin using the recovery with power, vol-, home, it detects that I plugged it in but when I try to click start it fails and nothing happens.
I have exact the same problem.
I have read many articles, who said it was easy to root.
That's not true !!!!.
Maybe because the tablet became an update today ?
What I did to recover the tablet: (phew !!!)
Download this bootloader:
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
Connect to Odin and flash it.
A few seconds, it says OK, reboots and voila: there's your tablet again revived !!!!.
rumaro said:
I have exact the same problem.
I have read many articles, who said it was easy to root.
That's not true !!!!.
Maybe because the tablet became an update today ?
What I did to recover the tablet: (phew !!!)
Download this bootloader:
http://forum.xda-developers.com/attachment.php?attachmentid=2591013&d=1392923580
Connect to Odin and flash it.
A few seconds, it says OK, reboots and voila: there's your tablet again revived !!!!.
Click to expand...
Click to collapse
Unfortunately Odin fails before it manages to even connect to my tablet so I'm not sure it will work for me but I'll give it a try. It managed to connect before when I tried to flash the root files but now it fails every time. I'll update this when I get home and try flashing that.
Edit:
Got home, tried your fix. I am happy to report it worked and it only took a few seconds. Thanks!
Edit:
To anyone reading this thread, if you tried rooting your SM-T900 using the SM-T900 files for rooting, try using the SM-P900 files instead! I just tried that and it seems to be working fine.
I'm glad I could help. :good:
It's bad for your heart when you see that your expensive tablet is bricked.
Hello everyone. Where do I flash the bootloader in odin? Do I use PDA or Bootloader and do I need to check the bootloader update box? Just wanted to confirm before further messing up my tablet. Thanks!
Edit: Never mind, figured it out. Thanks for the help!
This method just worked for me. Flashed the bootloader with Odin after getting "stuck" and it booted right up.
Jim
sizedlemming65 said:
Hello everyone. Where do I flash the bootloader in odin? Do I use PDA or Bootloader and do I need to check the bootloader update box? Just wanted to confirm before further messing up my tablet. Thanks!
Edit: Never mind, figured it out. Thanks for the help!
Click to expand...
Click to collapse
What did you do exactly to fix it? I'm having the same issue. Just sits at screen and says:
ODIN MODE
Product Name: SM-T900
Current Binary: Custom
System Status: Official
KNOX Warranty Void: 1
RP SWREV: A1
How do you use that recovery.img file?
For the top most problem flash cwm or TWRP recovery through Odin or through recovery mode then boot into cwm or TWRP recovery delete all files and install a supported rom.
If u want full explained steps mail me
- [email protected]
Sent from my SM-J500F using XDA Forums
it's 2022 & my T900 finally went into bootloop in model logo, does anyone know the real reason for this? is it hardware or software problem?
- I can flash any version via odin but still bootloops
- TWRP worked once after that can't get in anymore
- the only button working is for the download mode PWR + Vol Down
- before all this LED Stayed on until batt drained then bootloops
it's a good tab to watch movie while on a treadmill
I rooted my T-Mobile Galaxy Note 4 early last week using Odin v3.09 and cf auto root and flashed TWRP recovery using Odin. I disabled Knox as SuperSU suggested, and I created a back up after root. Saturday I flashed Dynamic Kat v 3.0, and go everything set up the way I wanted it. I didn't mess with any of the security settings, other than setting a pin for the lockscreen. This morning I rebooted into recovery to create a back up, but instead of going to recovery, I got a black screen with an exclamation point and an error message saying Custom binary blocked by Reactivation Lock. Secure Fail: Recovery that would just keep looping when I tried to restart it. I tried pulling the battery and restarting, but still had the same message at restart. I then tried to run odin and cf autoroot again, but got the same message and Odin said that it failed. Now the phone just keeps boot looping on the Samsung Galaxy Note 4 powered by android screen.
If I go to the download mode the top of the screen says:
Odin Mode (High Speed)
Product Name: SM-N910T
Current Binary: Custom
System Status: : Custom
Reactivation Lock(KK): On
Knox Warranty Void: 0x1 (4)
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download : Enable
UDC Start
How can I fix this, what can I do?
Get a stock odin flashable and start over from downloadmode...
Tryna find that link or it may be samsmobile
Look here.
http://forum.xda-developers.com/showthread.php?p=55968427
If your pc does not see the phone in download mode then you need to run kies emergency firmware recovery..
Flashvetrin said:
Get a stock odin flashable and start over from downloadmode...
Tryna find that link or it may be samsmobile
Look here.
http://forum.xda-developers.com/showthread.php?p=55968427
If your pc does not see the phone in download mode then you need to run kies emergency firmware recovery..
Click to expand...
Click to collapse
Thanks, I found where someone had the same issue with the Note 3 and used kies emergency firmware recovery to fix it as well, so I started the process. It just finished, and I'm back up and running.
omega_wolf said:
Thanks, I found where someone had the same issue with the Note 3 and used kies emergency firmware recovery to fix it as well, so I started the process. It just finished, and I'm back up and running.
Click to expand...
Click to collapse
Thats good news..
[emoji1] [emoji109] [emoji106]
can you link me to where you went? fml this just happened to me after flashing same rom you did.
jrocks213 said:
can you link me to where you went? fml this just happened to me after flashing same rom you did.
Click to expand...
Click to collapse
Yea, I followed the steps posted in this thread: http://forum.xda-developers.com/showthread.php?t=2486564&page=2
1. download KIES 3 (for note 4)
2. Click tools>Firmware upgrade and initialization
3. Put phone into download mode (press Volume down+Home Button+Power Button and then volume up)
4. Connect your phone (it is OK if it is not recognized by KIES, just keep it connected)
5. Now do as it says by typing in your Phone model number (check the battery compartment).
6. Type in the S/N.
7. Let it do its business and download the firmware.
8. Once firmware is downloaded, It will start communicating with the phone.
9. You can see a blue progress line on the screen under the android guy.
10. Let it finish and restart.
You will have to re-root after this.
omega_wolf said:
Yea, I followed the steps posted in this thread: http://forum.xda-developers.com/showthread.php?t=2486564&page=2
1. download KIES 3 (for note 4)
2. Click tools>Firmware upgrade and initialization
3. Put phone into download mode (press Volume down+Home Button+Power Button and then volume up)
4. Connect your phone (it is OK if it is not recognized by KIES, just keep it connected)
5. Now do as it says by typing in your Phone model number (check the battery compartment).
6. Type in the S/N.
7. Let it do its business and download the firmware.
8. Once firmware is downloaded, It will start communicating with the phone.
9. You can see a blue progress line on the screen under the android guy.
10. Let it finish and restart.
You will have to re-root after this.
Click to expand...
Click to collapse
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
---------- Post added at 01:21 AM ---------- Previous post was at 01:04 AM ----------
jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
Click to expand...
Click to collapse
Thanks for all your help brotha. Kies wasn't working for me. I used odin to flash cf root and pulled battery and started into download mode pressed down to cancel and it boot up for me. I flashed Dynamic kat and checked off Reactivation Lock. That's why it did that to me for people with further problems.
jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
Click to expand...
Click to collapse
Try entering the model number and S/N and pressing Ok before connecting the phone, or double check to make sure 0s aren't Os or vice versa. It took a minute or 2 to get started on my phone, and took awhile to complete.
jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
---------- Post added at 01:21 AM ---------- Previous post was at 01:04 AM ----------
Thanks for all your help brotha. Kies wasn't working for me. I used odin to flash cf root and pulled battery and started into download mode pressed down to cancel and it boot up for me. I flashed Dynamic kat and checked off Reactivation Lock. That's why it did that to me for people with further problems.
Click to expand...
Click to collapse
This happened to me before and this is what i did. Easier than messing kies I think. Flash cf auto root in odin with the reset and auto reboot unchecked. Very important to uncheck those. It will fail to flash. Pull out your battery and put back in. It will boot as normal. Now go into security and uncheck that reactivate crap. That feature should be disabled completely custom roms to prevent this occurance i think.
Airtioteclint said:
That feature should be disabled completely custom roms to prevent this occurance i think.
Click to expand...
Click to collapse
I agree, it wasn't checked by default when I rooted the phone, nor when I flashed another ROM, so I didn't even think to check when I flashed Dynamic Kat, but I'll be double checking gem here on out.
jrocks213 said:
I'm doing as it says but when i put s/n says check phone again. What am I doing wrong?
---------- Post added at 01:21 AM ---------- Previous post was at 01:04 AM ----------
Thanks for all your help brotha. Kies wasn't working for me. I used odin to flash cf root and pulled battery and started into download mode pressed down to cancel and it boot up for me. I flashed Dynamic kat and checked off Reactivation Lock. That's why it did that to me for people with further problems.
Click to expand...
Click to collapse
Hi, Im in the same boat, locked out, etc, I am trying kies where I dump the s/n in etc, it downloads the firmware, sees the phone then crashes, same with ODIN, the blue bar underneath the android man, starts but locks up. Does not go anywhere and freezes the phone. I have to take the battery out or leave Kies to give me an error. Any idea?
smileruk.ss said:
Hi, Im in the same boat, locked out, etc, I am trying kies where I dump the s/n in etc, it downloads the firmware, sees the phone then crashes, same with ODIN, the blue bar underneath the android man, starts but locks up. Does not go anywhere and freezes the phone. I have to take the battery out or leave Kies to give me an error. Any idea?
Click to expand...
Click to collapse
Odin flash cf autoroot, it will fail but once it restarts it will boot up to your android screen,
also you can Odin flash the full firmware, but then u need to odin flash twrp again and root.
I've searched around the forum and haven't hit a solution, so sorry if it's out there.
So, I have a Galaxy S4 Active (i537) ATT. I was given to me in a bootlooping state, and if I fix it I can keep the device.
What I have done to the moment:
Flashed every stock rom found in the forum with Odin (No luck on the device booting)
What the device does:
It shows the samsung splash, and restarts over and over, sometimes it doesn't even manage to get to the samsung splash.
Attempting to boot into recover mode produces the same result, it says booting recovery and it restarts.
Info on Download mode:
Product name: SGH-i537
Current Binary: Samsung official
System Status: Official
Knox kernel lock: 0xfffffffc
Knox kernel warranty void: 0xfffffffc
CSB-CONFIG-LSB: 0x30
Write protection: enable
emmc burst mode enabled
I'm new to samsung devices, so I hope someone can help me out here.
Thanks in advanced!
rguilamo said:
I've searched around the forum and haven't hit a solution, so sorry if it's out there.
So, I have a Galaxy S4 Active (i537) ATT. I was given to me in a bootlooping state, and if I fix it I can keep the device.
What I have done to the moment:
Flashed every stock rom found in the forum with Odin (No luck on the device booting)
What the device does:
It shows the samsung splash, and restarts over and over, sometimes it doesn't even manage to get to the samsung splash.
Attempting to boot into recover mode produces the same result, it says booting recovery and it restarts.
Info on Download mode:
Product name: SGH-i537
Current Binary: Samsung official
System Status: Official
Knox kernel lock: 0xfffffffc
Knox kernel warranty void: 0xfffffffc
CSB-CONFIG-LSB: 0x30
Write protection: enable
emmc burst mode enabled
I'm new to samsung devices, so I hope someone can help me out here.
Thanks in advanced!
Click to expand...
Click to collapse
It's hard to say what is wrong, but it sounds like you definitely need to flash stock firmware. One question, is it definitely the AT&T version (with the AT&T logo on the back cover) or could it be the Mexican version?
If it's the AT&T version, then flash the NE3 firmware by following the instructions in i537 Firmware Install Guide. The OP of the guide will ask you which firmware you're currently on, but for NE3 it doesn't matter which one you select because all the instructions will be the same. Make sure you don't have a corrupted download by checking the MD5 of the file you downloaded against the MD5 posted in the i537 Firmware Thread.
If you have the Mexican/Uruguayan version, you need to download the latest version of the firmware from sammobile and flash that. Flashing AT&T firmware on a Mexican/Uruguayan phone could result in the bootloops you are experiencing.
Devo7v said:
It's hard to say what is wrong, but it sounds like you definitely need to flash stock firmware. One question, is it definitely the AT&T version (with the AT&T logo on the back cover) or could it be the Mexican version?
If it's the AT&T version, then flash the NE3 firmware by following the instructions in i537 Firmware Install Guide. The OP of the guide will ask you which firmware you're currently on, but for NE3 it doesn't matter which one you select because all the instructions will be the same. Make sure you don't have a corrupted download by checking the MD5 of the file you downloaded against the MD5 posted in the i537 Firmware Thread.
If you have the Mexican/Uruguayan version, you need to download the latest version of the firmware from sammobile and flash that. Flashing AT&T firmware on a Mexican/Uruguayan phone could result in the bootloops you are experiencing.
Click to expand...
Click to collapse
Yes I'm sure It's AT&T. I had already tried NE3, as I said, I've flashed as many stock firmwares as I have been able to lay hands on. I did notice that when I tried NE3 again, knox kernel lock and knox kernel warranty changed from my previous posted states to these:
Knox kernel lock: 0x0
Knox kernel warranty void: 0x1
I cand add that exactly when Odin sends the reboot the phone tries to boot but into recovery mode, instead of just booting normally.
The only thing I can think of now, is that the device must have a hrdware issue.
rguilamo said:
Yes I'm sure It's AT&T. I had already tried NE3, as I said, I've flashed as many stock firmwares as I have been able to lay hands on. I did notice that when I tried NE3 again, knox kernel lock and knox kernel warranty changed from my previous posted states to these:
Knox kernel lock: 0x0
Knox kernel warranty void: 0x1
I cand add that exactly when Odin sends the reboot the phone tries to boot but into recovery mode, instead of just booting normally.
The only thing I can think of now, is that the device must have a hrdware issue.
Click to expand...
Click to collapse
It's supposed to try to reboot into recovery mode when you first Odin back to stock NE3. I just recovered from a soft brick myself where I couldn't boot at all. Flashed NE3 through Odin and the first time it rebooted, it went to stock recovery (I assume to finish installing the stock rom), did what it needed, and eventually rebooted normally. Plus (sorry, I just have to ask), you are using download mode for Odin (not recovery mode), correct?
thisisapoorusernamechoice said:
It's supposed to try to reboot into recovery mode when you first Odin back to stock NE3. I just recovered from a soft brick myself where I couldn't boot at all. Flashed NE3 through Odin and the first time it rebooted, it went to stock recovery (I assume to finish installing the stock rom), did what it needed, and eventually rebooted normally. Plus (sorry, I just have to ask), you are using download mode for Odin (not recovery mode), correct?
Click to expand...
Click to collapse
Yes I'm using Download mode for ODIN, the thing is, when it tries to boot to recovery mode after flashing with ODIN, and the reboot command is sent, the recovery never boots, the screen goes off, and then it just starts restarting itself
rguilamo said:
Yes I'm using Download mode for ODIN, the thing is, when it tries to boot to recovery mode after flashing with ODIN, and the reboot command is sent, the recovery never boots, the screen goes off, and then it just starts restarting itself
Click to expand...
Click to collapse
And you definitely don't have a corrupted download, and you've tried different usb cables, different usb ports, and different computers?
Devo7v said:
And you definitely don't have a corrupted download, and you've tried different usb cables, different usb ports, and different computers?
Click to expand...
Click to collapse
Checked MD5's, used original Samsung cable, Asus Nexus 7 Cable, tried Windows 7 (Desktop), and windows 8.1 on two different laptops.
Curiously I said to myself, let me try and charge it, since all this flashing might have taken out the battery. When I plugged in the USB cable the device showed the Samsung splash, and turned off, yet I let it be and didn't disconnect it, after an hour or so, I came back and saw him charging the battery, with the red light indicator on, about 20 minutes later it tried to boot, got to the ATT logo, and after I while with the ATT logo (I assume since it has to compile the dalvik, because it's the first boot) it just turned off again, and back to ATT logo, and it was bootlooping like this until I unplugged it and gave up.
so i recently got a note 3 from a friend to fix for her. it boots to the samsung logo then vibrates and reboots over and over, recovery just says "booting recovery" then it goes blank and reboots to the same booting recovery screen, shes doesnt know what version it had prior to bricking. she said one day it was working then turned off and never back on again, the odin mode screen had a2, a3 on it ill post a pic later anyway i can get into download mode so i figured id just flash with odin and be good, i tried to narrow down the proper firmware with the a3, but after flashing nc2, nl1, oc1, im still stuck odin says everything passed, i tried flashing the big main file, tried flashing them in each box at the same time, even tried it with the pit file, tried flashing with odin 3.9 and 3.10.7. same result odin says passed still cant access recovery or os. any help would be greatly appreciated. thanks
Open Odin, uncheck everything except f reset time, flash rom. When you see reset on the statutes window, remove USB cable from the phone, remove battery, wait 5 seconds, replace battery, boot directly into recovery, perform a factory wipe, reboot.
does it matter what version i flash? since im not really sure what version it had prior?
I can't figure out how to upload a photo I have xda 4.0, and can't post outside links yet. Anyway
It says
Product name:N900A
Current binary: Samsung official
System status official
Knox void status 0x0
Qualcomm Secureboot enabled(csb)
Ap swrev s2 t2 a2 a3 p2
Secure download enable
Udc start
Hope that helps
Ran Odin again with the settings you said, after the battery pull the phone says recovery booting, then turned off vibrated twice then same screen again and again. Thanks for the suggestion though any our ideas? I was searching and thought I seen somewhere that to unbrick it it needs to be the same firmware it had before, but I don't know what that was.
ghost5825 said:
Ran Odin again with the settings you said, after the battery pull the phone says recovery booting, then turned off vibrated twice then same screen again and again. Thanks for the suggestion though any our ideas? I was searching and thought I seen somewhere that to unbrick it it needs to be the same firmware it had before, but I don't know what that was.
Click to expand...
Click to collapse
You should probably ask her if she had Lollipop. If she did then that narrows it down to OC1 or OC2.
She doesn't know, not very phone literate as far as software, any ideas? I read in another thread to flash a modified version of nc2 but can't seem to find that version, this is the thread http://forum.xda-developers.com/showthread.php?t=2703006
Don't know if I can't find it, kinda confusing as far as what I need, like I said I've tried everything except oc2 cant find a link I've tried googling, and that thread says Odin files but can't find a full one for oc2, there's ones for safestrap but can't find Odin
I'm officially fed up. I (STUPIDLY) attempted to root my galaxy using ODIN and have been trying to get it back to normal for 3 weeks I'm finally asking for help , if anyone can offer any..
My situation. ....
I used ODIN and a root file I downloaded. . I did it all just the way the guide said.
My phone restarted and I got a message fr ok m samsung + device health check, warning me that my device is rooted
Next , I go to install superuser etc . Get error messages that my devices is NOT rooted and there is no binary.
So I'm stuck with this device that functions but is constantly giving security warnings that unauthorized activity has occured. Knox and Samsung pay say that my device is "Custom" and those apps , along with others won't allow me access for that reason.
This is the info from my screen in download mode (ODIN MODE)
PRODUCT NAME SM-928A
CURRENT BINARY SAMSUNG OFFICIAL
SYSTEM STATUS CUSTOM
REACTIVATION LOCK OFF
KNOX WARRANTY VOID (0x0000)
I have tried -
reflash stock rom , odin just locks up and then I get FIL message
I've factory recovered the device, wiped cache and partition etc numerous times to no avail.
Kies says my device is not compatible, smart switch says software is up to date and that my device doesn't support initialization for recovery.
Any ideas.. I'm all ears! Thank you!
TechChallengedHere said:
I'm officially fed up. I (STUPIDLY) attempted to root my galaxy using ODIN and have been trying to get it back to normal for 3 weeks I'm finally asking for help , if anyone can offer any..
My situation. ....
I used ODIN and a root file I downloaded. . I did it all just the way the guide said.
My phone restarted and I got a message fr ok m samsung + device health check, warning me that my device is rooted
Next , I go to install superuser etc . Get error messages that my devices is NOT rooted and there is no binary.
So I'm stuck with this device that functions but is constantly giving security warnings that unauthorized activity has occured. Knox and Samsung pay say that my device is "Custom" and those apps , along with others won't allow me access for that reason.
This is the info from my screen in download mode (ODIN MODE)
PRODUCT NAME SM-928A
CURRENT BINARY SAMSUNG OFFICIAL
SYSTEM STATUS CUSTOM
REACTIVATION LOCK OFF
KNOX WARRANTY VOID (0x0000)
I have tried -
reflash stock rom , odin just locks up and then I get FIL message
I've factory recovered the device, wiped cache and partition etc numerous times to no avail.
Kies says my device is not compatible, smart switch says software is up to date and that my device doesn't support initialization for recovery.
Any ideas.. I'm all ears! Thank you!
Click to expand...
Click to collapse
All I had was the security message for my S6 Edge. What I did to get the notification to go away is that I froze SecurityLogAgent (package name: com.samsung.android.securitylogagent), which of course, root is required to do so.
Use Factory cable.
TechChallengedHere said:
I'm officially fed up. I (STUPIDLY) attempted to root my galaxy using ODIN and have been trying to get it back to normal for 3 weeks I'm finally asking for help , if anyone can offer any..
My situation. ....
I used ODIN and a root file I downloaded. . I did it all just the way the guide said.
My phone restarted and I got a message fr ok m samsung + device health check, warning me that my device is rooted
Next , I go to install superuser etc . Get error messages that my devices is NOT rooted and there is no binary.
So I'm stuck with this device that functions but is constantly giving security warnings that unauthorized activity has occured. Knox and Samsung pay say that my device is "Custom" and those apps , along with others won't allow me access for that reason.
This is the info from my screen in download mode (ODIN MODE)
PRODUCT NAME SM-928A
CURRENT BINARY SAMSUNG OFFICIAL
SYSTEM STATUS CUSTOM
REACTIVATION LOCK OFF
KNOX WARRANTY VOID (0x0000)
I have tried -
reflash stock rom , odin just locks up and then I get FIL message
I've factory recovered the device, wiped cache and partition etc numerous times to no avail.
Kies says my device is not compatible, smart switch says software is up to date and that my device doesn't support initialization for recovery.
Any ideas.. I'm all ears! Thank you!
Click to expand...
Click to collapse
Make sure you are using the original cable that came with your phone when flashing...
Ensure you are using the newest version of odin.
If odin detects your phone in download mode. Then you should be able to flash.
Make sure usb debugging ... and OEM UNLOCK are both enabled.
Clear devilik cache in recovery mode (Not download mode)
Make sure you are trying to flash the correct recovery files for your phone. (Correct region)
I have supplied the recovery files for OGG AND OJ1 stock firmware on the "obtain a little freedom" thread for the G928A
Flash back to stock, and use smartswitch to restore your (pre-backed up information)
Also what version of Windows are you working with?