[Q] Can you guys help me fix my bricked note 3? - Galaxy Note 3 Q&A, Help & Troubleshooting

Hey all, so I tried to unroot my Note 3. Sadly I messed up and my phone is stuck on the Samsung Galaxy Note 3 loading screen. I can go into ODIN mode and Recovery mode. I tried to wipe data/factory reset and wipe cache partition, but that didn't work, still doesn't load. I don't know what to do anymore. If it matters I was using Safestrap. If it helps this is what it says in ODIN MODE
Product Name: SM-N900A
Current Binary: Samsung Offical
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
Qualcomm Secureboot: Enable(CSB)
RP SWREV: S2 T2 R2 A2 P2
Write Protection: Enable

AskoChainz said:
Hey all, so I tried to unroot my Note 3. Sadly I messed up and my phone is stuck on the Samsung Galaxy Note 3 loading screen. I can go into ODIN mode and Recovery mode. I tried to wipe data/factory reset and wipe cache partition, but that didn't work, still doesn't load. I don't know what to do anymore. If it matters I was using Safestrap. If it helps this is what it says in ODIN MODE
Product Name: SM-N900A
Current Binary: Samsung Offical
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
Qualcomm Secureboot: Enable(CSB)
RP SWREV: S2 T2 R2 A2 P2
Write Protection: Enable
Click to expand...
Click to collapse
hi,flash a stock firmware

dabenaute said:
hi,flash a stock firmware
Click to expand...
Click to collapse
Hello, thank you for replying, I got it done and my phone is unbricked, thank you! :laugh:

AskoChainz said:
Hello, thank you for replying, I got it done and my phone is unbricked, thank you! :laugh:
Click to expand...
Click to collapse
My pleasure

AskoChainz said:
Hey all, so I tried to unroot my Note 3. Sadly I messed up and my phone is stuck on the Samsung Galaxy Note 3 loading screen. I can go into ODIN mode and Recovery mode. I tried to wipe data/factory reset and wipe cache partition, but that didn't work, still doesn't load. I don't know what to do anymore. If it matters I was using Safestrap. If it helps this is what it says in ODIN MODE
Product Name: SM-N900A
Current Binary: Samsung Offical
System Status: Custom
Hi I have problem same as you
How did you solve and load stock rom .
help please
Click to expand...
Click to collapse

flash stock
cagodesign said:
AskoChainz said:
Hey all, so I tried to unroot my Note 3. Sadly I messed up and my phone is stuck on the Samsung Galaxy Note 3 loading screen. I can go into ODIN mode and Recovery mode. I tried to wipe data/factory reset and wipe cache partition, but that didn't work, still doesn't load. I don't know what to do anymore. If it matters I was using Safestrap. If it helps this is what it says in ODIN MODE
Product Name: SM-N900A
Current Binary: Samsung Offical
System Status: Custom
Hi I have problem same as you
How did you solve and load stock rom .
help please
Click to expand...
Click to collapse
using odin, you flash stock firmware from sammobile, intended for your device...there are countless tutorial here on xda, so start looking, searching and learn all you can before going at it.....it is very simple once you learn...
Click to expand...
Click to collapse

Related

[Q] SM-N900K Stuck on Odin Mode "“Firmware upgrade encountered an issue"

I have a Korean model Note 3 that I rooted a while back. Tonight I updated the firmware over Kies, everything went fine, then tried to re-root using the same method I previously used (CF Auto root). Obviously a mistake.
Now my phone is stuck on Odin Mode, displaying the "Firmware upgrade encountered an issue" screen. (It actually displays it in Korean but it's the same screen).
Here is what it says:
ODIN MODE;
PRODUCT NAME: SM-N900K
CURRENT BINARY: Custom
CURRENT STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCKFF
KNOX WARRANTY VOID: 0X1
QUALCOOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
After I unsuccessfully attempted use CF Auto Root is also says "Unsupport dev_type" in red at the bottom.
The biggest problem I'm having is that I don't know what to flash. The SM-N900K seems to be an uncommon model, at least in the English speaking world. In fact, when I first rooted I couldn't find the appropriate file for this model so I used the N900 or N900s (which is another Korean model), I can't remember which.
If anyone has any suggestions for how I can fix this, it is greatly appreciated.
More
Update: I flashed the Cf Auto Root for the SM-N900S .
Now I am no longer stuck at the "Firmware upgrade encountered an error mode" but at the regular Odin download mode. Also able to access recovery mode. Still unsure of how to get my phone back track.
Update again:
Was able to install the SM-N900S Clockwork Mod. However, still unable to boot normally. Any help appreciated
Is there any chance I can get back into my phone the way it was, without losing all my data? Or will I need to do a factory reset?
Flash the latest firmware for this model
Sent from my LT26i using Tapatalk
Coolmfarshard said:
Flash the latest firmware for this model
Sent from my LT26i using Tapatalk
Click to expand...
Click to collapse
I am unable to find firmware for SM-N900K, and am wary that if I flash the SM-N900S firmware, it will mess up the phone somehow (they are for different carriers)
You should wipe data/cache partition/dalvik.... and try flashing a custom rom. Sees if it boots up then
Sent from my SM-N9005 using Tapatalk
I was able to install Lidroid ROM successfully, but after reboot it returns to the same Odin Mode screen as before.
dadaclonefly said:
I was able to install Lidroid ROM successfully, but after reboot it returns to the same Odin Mode screen as before.
Click to expand...
Click to collapse
I guess the only way is to wait the official firmware for sm-n900k(KT).
Can you give a picture of the screen at all.... Best bet is goto samfirmware and find the latest firmware for your phone and flash with Odin... If that don't work.. Try the sm9005 mj7 firmware. ... Though Not sure if it will make things worse or not
Sent from my SM-N9005 using Tapatalk
alom5 said:
Can you give a picture of the screen at all.... Best bet is goto samfirmware and find the latest firmware for your phone and flash with Odin... If that don't work.. Try the sm9005 mj7 firmware. ... Though Not sure if it will make things worse or not
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I can't give a picture of the screen but this is what it says:
Could not do normal boot
ODIN MODE;
PRODUCT NAME: SM-N900K
CURRENT BINARY: Custom
CURRENT STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCKFF
KNOX WARRANTY VOID: 0X1
QUALCOOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
Below that there is the green Android logo and it says Downloading Mode (in Korean) and Do not turn off (in Korean)
Edit: Also, samfirmware.com does not have firmware for the SM-N900K unfortunately, only the SMN900S. Does anyone know where I can download other Korean firmwares?
If I try to flash SM-N900S Firmware my phone says the same as before, with the following at the bottom:
SECURE CHECK FAIL : sbl1
So it looks this in download mode:
Could not do normal boot
ODIN MODE;
PRODUCT NAME: SM-N900K
CURRENT BINARY: Custom
CURRENT STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCKFF
KNOX WARRANTY VOID: 0X1
QUALCOOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
SECURE CHECK FAIL : sbl1
Have you tried kies since you had this error? I had problem before and it said to use kies to restore.
It looks like the bootloader... and you may have to wait until you find the original firmware. ..
What version of odin are you using? I use 3.09 ... Try that if you are on a older version.
Sent from my SM-N9005 using Tapatalk
alom5 said:
Have you tried kies since you had this error? I had problem before and it said to use kies to restore.
It looks like the bootloader... and you may have to wait until you find the original firmware. ..
What version of odin are you using? I use 3.09 ... Try that if you are on a older version.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I've tried both 3.09 and 1.85 versions of Odin. And Kies won't recognize the device, unfortunately.
dadaclonefly said:
update: I flashed the cf auto root for the sm-n900s .
Now i am no longer stuck at the "firmware upgrade encountered an error mode" but at the regular odin download mode. Also able to access recovery mode. Still unsure of how to get my phone back track.
Update again:
Was able to install the sm-n900s clockwork mod. However, still unable to boot normally. Any help appreciated
Click to expand...
Click to collapse
good stuff ...
In case anyone happens on this thread while trying to resolve a similar issue, the resolution was that I was unable to fix it on my own. I took it to the Samsung Service Center and they reinstalled the original firmware despite the Knox warranty having been tripped.
dadaclonefly said:
In case anyone happens on this thread while trying to resolve a similar issue, the resolution was that I was unable to fix it on my own. I took it to the Samsung Service Center and they reinstalled the original firmware despite the Knox warranty having been tripped.
Click to expand...
Click to collapse
Did they reset the knox for you?
Sent from my SM-N9005 using Tapatalk
sm n900k
dadaclonefly said:
I have a Korean model Note 3 that I rooted a while back. Tonight I updated the firmware over Kies, everything went fine, then tried to re-root using the same method I previously used (CF Auto root). Obviously a mistake.
Now my phone is stuck on Odin Mode, displaying the "Firmware upgrade encountered an issue" screen. (It actually displays it in Korean but it's the same screen).
Here is what it says:
ODIN MODE;
PRODUCT NAME: SM-N900K
CURRENT BINARY: Custom
CURRENT STATUS: Custom
REACTIVATION LOCK: OFF
KNOX KERNEL LOCKFF
KNOX WARRANTY VOID: 0X1
QUALCOOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
After I unsuccessfully attempted use CF Auto Root is also says "Unsupport dev_type" in red at the bottom.
The biggest problem I'm having is that I don't know what to flash. The SM-N900K seems to be an uncommon model, at least in the English speaking world. In fact, when I first rooted I couldn't find the appropriate file for this model so I used the N900 or N900s (which is another Korean model), I can't remember which.
If anyone has any suggestions for how I can fix this, it is greatly appreciated.
Click to expand...
Click to collapse
I have the same sm n900k.. I successfuly rooted it using sm n900s..via odin.. also the CWM recovery from 900s.
Can I reroot again doing the same procedure via odin because I have unrooted it via supersu .. can I also re install CWM recovery since I updated it at Rom Manager and it show different version now.but it ia still working..
by the way can you post the link of the Lidroid rom you use for sm 900k if it worked out well..thanks!!
im about to get a Note 3 from olleh KT and it is sm-n900k version. also i have messed up a phone trying to root before and took it to kt and a few days they gave me back my phone in working order. they dont seem to care to much if u ruin your phone by software problems. but has any one found how to root note 3 sm-n900k version so i can try it out?
thedawg03 said:
im about to get a Note 3 from olleh KT and it is sm-n900k version. also i have messed up a phone trying to root before and took it to kt and a few days they gave me back my phone in working order. they dont seem to care to much if u ruin your phone by software problems. but has any one found how to root note 3 sm-n900k version so i can try it out?
Click to expand...
Click to collapse
That depends on which exact firmware version you are on.
Pop over to the Galaxy Note 3 Korean Users Thread for more info!
Try this one for SMN-N900K : http://pan.baidu.com/s/1jGA1F98
Tested to be working.

[Q] Seandroid encorcing

Hi guys!
Some weeks ago, I unrooted my i9505. This saturday I wanted to root again, because of the Kitkat roms from jamal and janjan.
When I'm booting my phone there is a message in the top corner:
"KERNEL IS NOT SEANDROID
Set Warranty Bit : kernel"
I read on some different websites that this message isn't cursing any problems, but it would be nice if I could fix it anyways.
Also when i enter download-mode this is what it says:
ODIN MODE
PRODUCT NAME: GT-I9505
CURRENT BINARY:Custom
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMc BURST MODE enabled
Is there any way to fix this?
Before rooting this saturday i had a stock firmware installed, which i found here: http://www.sammobile.com/firmwares/2/
Rooted my phone with this guide: http://forum.xda-developers.com/showthread.php?t=2219803
I've had some random reboots on both roms (jamal and janjan) since then - i don't know whether that is caused by the "enforcing"-error or by the ROM..
Hope you can give me some anwers
Thanks guys
This message appears coz maybe u tried to change the STOCK KERNEL for other different or maybe the ROM u installed have custom KERNEL. I recommend u make WIPE in recovery and install STOCK ROM for let ur system clean. U will can root it and install custom recovery then
So this is what i should do:
1. Boot into TWRP
2. Wipe everything
3. Flash Stock Firmware from ODIN
4. Try to boot, and then the message should be gone
- Or did i misunderstand something?
So this is what i should do:
1. Boot into TWRP
2. Wipe everything
3. Flash Stock Firmware from ODIN
4. Try to boot, and then the message should be gone
- Or did I misunderstand something?
velein said:
So this is what i should do:
1. Boot into TWRP
2. Wipe everything
3. Flash Stock Firmware from ODIN
4. Try to boot, and then the message should be gone
- Or did I misunderstand something?
Click to expand...
Click to collapse
Thanks in advance
Didn't work
velein said:
Didn't work
Click to expand...
Click to collapse
What stock ROM u are flashing?
random reboot is known bug with GE kit kat roms as of now.. wait a month or more, i'm pretty it'll be fixed..
Nothing can change
only CURRENT BINARY:Custom and SYSTEM STATUS: Custom to Official
KNOX WARRANTY VOID: 0x1 you can not change
akadxda said:
Nothing can change
only CURRENT BINARY:Custom and SYSTEM STATUS: Custom to Official
KNOX WARRANTY VOID: 0x1 you can not change
Click to expand...
Click to collapse
But this will not have any effect on my daily use of my phone?
just to be sure.
thanks in advance
velein said:
But this will not have any effect on my daily use of my phone?
just to be sure.
thanks in advance
Click to expand...
Click to collapse
No, you will not have problems
Knox will not work when 0x1
If you install the correct official firmware and this message - "KERNEL IS NOT SEANDROID* Set Warranty Bit: kernel "should be removed

Knox Warranty Void: 0x1

I saw this on my bricked GS4 4.3.1(cyanogenmod 10.2) when I powered it on.
Any way to fix this?
It pops up on recovery mode and when I boot it up.
I really just want to get my S4 working again.
Can I just take it into some place like Best Buy or something and they'd help me?
Product Name: SGH-M919
Current Binary: Custom
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enabled
eMMC BURST MODE enabled
oohrekt said:
I saw this on my bricked GS4 4.3.1(cyanogenmod 10.2) when I powered it on.
Any way to fix this?
It pops up on recovery mode and when I boot it up.
I really just want to get my S4 working again.
Can I just take it into some place like Best Buy or something and they'd help me?
Product Name: SGH-M919
Current Binary: Custom
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enabled
eMMC BURST MODE enabled
Click to expand...
Click to collapse
Please tell me there is hope for me.
oohrekt said:
I saw this on my bricked GS4 4.3.1(cyanogenmod 10.2) when I powered it on.
Any way to fix this?
It pops up on recovery mode and when I boot it up.
I really just want to get my S4 working again.
Can I just take it into some place like Best Buy or something and they'd help me?
Product Name: SGH-M919
Current Binary: Custom
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enabled
eMMC BURST MODE enabled
Click to expand...
Click to collapse
If you can boot to recovery, then I wouldn't say it's "bricked."
As for a place like Best Buy helping you, well I don't know their processes but anyone who checks for a warranty claim can't help you in its current state.
Why not just flash a new ROM?
oohrekt said:
I saw this on my bricked GS4 4.3.1(cyanogenmod 10.2) when I powered it on.
Any way to fix this?
It pops up on recovery mode and when I boot it up.
I really just want to get my S4 working again.
Can I just take it into some place like Best Buy or something and they'd help me?
Product Name: SGH-M919
Current Binary: Custom
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
Write Protection: Enabled
eMMC BURST MODE enabled
Click to expand...
Click to collapse
If your phone is "bricked" than your phone has the same exact functionality as a brick. If your phone can turn on and tell you which version of android your on, well... a brick cant do that.
Well I can't get into recovery mode. Being the idiot I tried to flash 4.2.2 over not thinking what I have done. Well, even before I couldn't get into recovery mode. I can get into download mode however. Is it possible I can flash official 4.3 or some other 4.3.1 rom over?
If you still having the problem..
oohrekt said:
Well I can't get into recovery mode. Being the idiot I tried to flash 4.2.2 over not thinking what I have done. Well, even before I couldn't get into recovery mode. I can get into download mode however. Is it possible I can flash official 4.3 or some other 4.3.1 rom over?
Click to expand...
Click to collapse
Well friend,
don't panic.. as I know all your loses is that you lost your warranty but not your device..
You can install the stock original rom jelly bean 4.3
If you are interested go to www sammoblie com then (firmwares) then search for your device model (I9500) or (I9505) or (I9505G) or (I9506) then download the firmware for your country and carrier and follow their installing instructions
If you can boot to recovery, then I wouldn't say it's "bricked."
As for a place like Best Buy helping you, well I don't know their processes but anyone who checks for a warranty claim can't help you in its current state.
Why not just flash a new ROM?
DUBU said:
If you can boot to recovery, then I wouldn't say it's "bricked."
As for a place like Best Buy helping you, well I don't know their processes but anyone who checks for a warranty claim can't help you in its current state.
Why not just flash a new ROM?
Click to expand...
Click to collapse
bro cant you read that he cant boot into recovery
---------- Post added at 09:58 AM ---------- Previous post was at 09:54 AM ----------
oohrekt said:
Well I can't get into recovery mode. Being the idiot I tried to flash 4.2.2 over not thinking what I have done. Well, even before I couldn't get into recovery mode. I can get into download mode however. Is it possible I can flash official 4.3 or some other 4.3.1 rom over?
Click to expand...
Click to collapse
did you ever fix it , i got the exact same problem , i got a metropcs s4 and i wanted kit kat insane rom and tried to flash a stock tmobile rom because some people said they did and it was fine,. well not for me. i would like to knowif you ever got it fixed, i tried to flash the stock metropcs 4.2.2 that i was on before this happened and odin still fails.
its fixed now , i had to move the stock tar to the same folder as odin, go figure
Haha mate you havent "bricked" your phone.
If your phone enters the recovery, it would be booting into the download mode too.
Try getting the official firmware of your specific phone model nom and just flash it via odin.
Dont worry.
Sent from my GT-I9500 using XDA Free mobile app
DeepankarS said:
Haha mate you havent "bricked" your phone.
If your phone enters the recovery, it would be booting into the download mode too.
Try getting the official firmware of your specific phone model nom and just flash it via odin.
Dont worry.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
I get a message about use kies recovery because firmware upgrade had issues when I try to boot into recovery, and I when I boot download mode flashing the stock rom fails every time.
revized said:
I get a message about use kies recovery because firmware upgrade had issues when I try to boot into recovery, and I when I boot download mode flashing the stock rom fails every time.
Click to expand...
Click to collapse
Yeah that is because you upgraded to 4.3 which has KNOX bootloader.
It wont let you flash 4.2.2 anymore. Like a downgrade is not possible once a knix enavled bootloader is flashed.
Download 4.3 or 4.4.2 and flash. It wont fail.
Thanks if i helped.
Sent from my GT-I9500 using XDA Free mobile app
DeepankarS said:
Yeah that is because you upgraded to 4.3 which has KNOX bootloader.
It wont let you flash 4.2.2 anymore. Like a downgrade is not possible once a knix enavled bootloader is flashed.
Download 4.3 or 4.4.2 and flash. It wont fail.
Thanks if i helped.
Sent from my GT-I9500 using XDA Free mobile app
Click to expand...
Click to collapse
Sounds nice and all although I tried to flash the official 4.3 from Samsmobile and it's fails.
4.4 is not available for mrtropcs customers because the company don't care about it's customers in this regard. LOL
Just for inquiry purposes only, I found a link to a Guy saying he used lunix to delete know bootloader from a tar filehttps://www.google.com/url?sa=t&source=web&rct=j&ei=8PDgU7DSOZTdoATTkIKYDA&url=http://m.youtube.com/watch%3Fv%3D75DKAGNstbM&cd=1&ved=0CB4QtwIwAA&usg=AFQjCNE7yajeB0317RtOmlFeEIB1QgEOGA&sig2=oD8TmSaTKu19-kpy0AKFGQ
Just go to sammobile and find the latest firmware for your model (4.4.2 for example) and dont look at build number.
Just grab it and extract to desktop.
Put your device in recovery mode if you can, and wipe data/cache/system if you can.
Then put your phone in download mode and connect do computer, in ODIN choose AP and add your tar.md5 file from desktop.
Flash it.
Then pull out battery on first reboot when flashin. Put it back and get into recovery by pressing VolUp + Power. Wipe everything again and reboot.
Should be fine.
i was finally able to flash stock 4.3 by just moving the tar file into the same folder as odin, go figure , i still want 4.4!!LOL

Galaxy Note 3 SM N9005

ODIN MODE
PRODUCT NAME: SM-N9005
CURRENT BINARY: Samsung Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x1 (4)
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2, T2, R2, A3, P3
SECURE DOWNLOAD : ENABLE
UDC START
I gave my note3 to a technician, there was a problem (It didn't boot, instead stuck on samsung logo with recovery booting). The technician did his best and the phone began to work. Then I used the phone once ( for 24 hours) and the same problem came back. I tried to flash it with official Rom lollipop 5.0, bootloader and CWM by Odin v3.09, but that was in vain.
I need your help please.
Waiting for your reply.
Take it back to your technician .
Suggestion is a hardware problem .
JJEgan said:
Take it back to your technician .
Suggestion is a hardware problem .
Click to expand...
Click to collapse
I did it before trying by myself to fix the problem, but not solution. If it's a hardware problem, may be I have to try with another technician. Thanks.
This is exactly the same problem I am having.
My phone is now working on stock Lollipop but I was stuck with this for a while.
I found that if i flashed the CWM .tar file with Odin it would reboot and work fine.
Once you get to that point, download a stock rom from Sammobile - I used 4.4.2 just to get it working.
When i had installed 4.4.2 everything appeared fine, i went ahead and booted into stock recovery and did a full reset.
I then let the phone update to stock 5.0 using the built in updater.
Im running it as it is (stock rom, un-rooted and stock recovery) until i can research enough into the problem and how to get around it.
In Odin mode on my phone, there is a "write protection - enabled" line also, which im guessing is causing my problem on not being able to get cwm/twrp to work
My aim was to Root, custom recovery and custom Rom but I hit the exact brick wall you posted in the OP

Help rooting and de-bloating Galaxy S4 SPH-720T

I think something is not right about my phone. I got this this phone 3 days ago and was running lollipop 5.0.1.
I tried to root it with this guide here choosing method one, because in the about section of the settings, it said Galaxy s4 GT-i9500. After flashing the downloaded CF-Auto-Root-ja3g-ja3gxx-gti9500.tar.md5 with Odin and it failed, it could only boot into download mode with the error "Firmware upgrade encountered an issue. Please select ..........blah blah blah".
After failing to unbrick the phone, I took it to a repair shop where they flashed a new stock rom. The model now says Galaxy S4 SPH-L720T in lollipop 5.0.1. It used to be GT-I9500 and to make it more confusing, the sticker at the back read Model: SM-i9500, SSN: -i9500GSMH. And if I boot into downooad mode, the below info is what comes up. How can I successfully root this device and de-bloat it without bricking my phone again? I didn't have to spend the extra money for flashing a new rom.
ODIN MODE
PRODUCT NAME: SPH-L720T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: Enable
Easiest way
Odin custom recovery
Reboot into recovery
Flash latest super user and bianary
Sent from my SPH-L720 using Tapatalk
Thank you. I'm rooted now. I was skeptical at first because I had attempted a root that bricked my phone. I need to remove bloatwares and make wifi tethering work.

Categories

Resources