Now on Note3 N9005 there are some members or Dev's that advise to tick or mark the Phone Bootloader Update in ODIN when we flash a full single Rom whit Bootloader in AP or PDA.
But them not explain why they advise that.
I not understand why and I need known the reasons for this. Single Yes or Not are not enough for me.
I'm on my 11º Samsung device, I used some Odin versions from 1.83 to 3.09 and the Odin Multi Dowloader V4 also.
I flashed already many, many Roms by Odin and...
I Never ticked the PHONE BOOTLODER UPDATE... NEVER... NEVER...
Why now here?
Is it because the Knox Bootloader? But the S4 Mini LTE + Mega 6.3" LTE + N7100 3G have also the Knox Bootloader but anybody advise to tick the Boot Update. (N7100 is now on 4.3).
I think:
1- We must not tick it if we flash a new full Bootloader.
2- We must tick it if we flash one Mod to Update the Bootloader installed.
3- Or we must tick it in some special devices for some reason.
Please people help me to understand this but whit good explanations.
Thank You
Hi Moderation
If You think this must be on Q&A, please move it.
Thank You
ValenteL said:
Hi Moderation
It You think this must be on Q&A, please move it.
Thank You
Click to expand...
Click to collapse
Click the orange triangle, there you can report a thread move to a moderator.
To upgrade to Kitkat, you'll need to upgrade your bootloader, if you're upgrading to another 4.3 then its not needed
Ather said:
To upgrade to Kitkat, you'll need to upgrade your bootloader, if you're upgrading to another 4.3 then its not needed
Click to expand...
Click to collapse
well simple , some roms required bootloader to upgrade either you tick or no they update it and some roms didn't required upgradation of bootloader at that point if you tick then BL will upgrade otherwise don't
now Hit likes
Ather said:
To upgrade to Kitkat, you'll need to upgrade your bootloader, if you're upgrading to another 4.3 then its not needed
Click to expand...
Click to collapse
For me not true.
I flashed from XXUDML2_OXXDMK3 Android 4.3 to XXUENA6_OXXENA5 XEO Android 4.4.2 Kitkat without tick Phone Bootloader Update and all well, no issues. I never ticked this and I'm now on XXUENB3 Kitkat.
I made full wipe data+cache+dalvik and format system on customer recovery before flash Kitkat.
I continue doubting from that. Sorry
newstar said:
Well simple , some roms required bootloader to upgrade either you tick or no they update it and some roms didn't required upgradation of bootloader at that point if you tick then BL will upgrade otherwise don't
Click to expand...
Click to collapse
Well not simple for me, Sorry. I download always from SamMobile and I have only this:
Model: SM-N9005
Model name: Galaxy Note 3
Country: Poland
Version: Android 4.4.2
Changelist: 636608
Build date: Sat, 08 Feb 2014 05:20:27 +0000
Product Code: XEO
PDA: N9005XXUENB3
CSC: N9005OXXENB1
MODEM: N9005XXUENB1
Instructions
Extract (unzip) the firmware file
Download Odin v3.09
Extract Odin zip-file
Open Odin v3.09
Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait a few minutes
Then where have I on SamMobile if this Rom need Phone Bootloader Update ????
Thanks
Ather said:
To upgrade to Kitkat, you'll need to upgrade your bootloader, if you're upgrading to another 4.3 then its not needed
Click to expand...
Click to collapse
N900->> I've just upgraded to 4.3(MK2) to 4.4.2(NA6) without BL update tick.
That's a fact.
What is the big point? To tick or not to tick?
I'm really sorry, but I miss the importance and use of this thread.
For me ( using N900W8 ) it didn't made any difference whether I tick it or not. Flashing from 4.3 to 4.4 and vice versa didn't give me any problem.
tkaragoz said:
N900->> I've just upgraded to 4.3(MK2) to 4.4.2(NA6) without BL update tick.
That's a fact.
Click to expand...
Click to collapse
And N900 have Knox Bootloader also?
Thanks
ValenteL said:
And N900 have Knox Bootloader also?
Thanks
Click to expand...
Click to collapse
It has knox bl.
In MK2 download mode, I saw only warranty bit and I saw knox warrany void in NA6 download mode.
Bootloader changed automatically i believe.
Pierre118 said:
What is the big point? To tick or not to tick?
I'm really sorry, but I miss the importance and use of this thread.
Click to expand...
Click to collapse
To You may be, for me not.
If the tick is for this:
2- We must tick it if we flash one Mod to Update the Bootloader installed. (from OP).
I'm afraid in this case, if Odin flash the new BL over the oldest without wipe this one, in some cases we can have issues.
May be I'm in error but I'm thinking.
tkaragoz said:
....
Bootloader changed automatically i believe.
Click to expand...
Click to collapse
You can see the bootloader on Shell Terminal Emulator from Play store, type getprop ro.bootloader and You have it.
ValenteL said:
You can see the bootloader on Shell Terminal Emulator from Play store, type getprop ro.bootloader and You have it.
Click to expand...
Click to collapse
When I upgraded my stock non rooted 9005 to KK I had to tick the box or I got a boot loop.
if u don't update to KK boot loader... phone doesn't charge when switched off... u try charging it switches back on... this happens on n900 not sure about 9005
Sent from my SM-N900
Related
So today Kitkat update for Samsung Galaxy Note 3 SM N9005 has leaked and to update and download we have made a simple and short guide.
NOTE
-Your data will be wiped. So, back it up!
- You are doing this at your OWN risk. We are not responsible if you brick your device or your cat eats your phone.
- It will NOT increase your binary counter NOR void your warranty.
- This test firmware is a pre-release build and not official from Samsung.
Download
N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX.zip
Odin3_v3.09.zip
INSTRUCTIONS
Step 1
Extract (unzip) the firmware file
Extract Odin v3.09.ZIP file
Step 2
Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
Step 3
Connect phone and wait until you get a blue sign in Odin
Step 4
Add AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 to AP
Add BL_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 to BL
Add CP_N9005XXUENA2_REV03_CL1277177.tar.md5 to CP
Add CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar.md5 to CSC
Note No need to update bootloader as suggest in #2
Step 5
Make sure re-partition is NOT ticked
Step 6
Click start button, relax and wait a few minutes and phone will restart.
ENJOY YOUR KITKAT NOTE 3
CREDITS: EASY HOWTO UPDATE NOTE 3 to latest leaked kitkat build
Please remove the BL step or people will be stuck in 4.4.2 leak without being able to revert.
Has anybody tried on a US Carrier Device?
Sent from my SM-N900T using Tapatalk
Skander1998 said:
Please remove the BL step or people will be stuck in 4.4.2 leak without being able to revert.
Click to expand...
Click to collapse
This ^^^
Upgrading bootloader means you cannot revert to 4.3! -- EDIT: You MUST upgrade bootloader to install this
from the 'leaked kitkat' thread, it seems that if you dont flash BL step, this updated wont work and will cause errors.
http://forum.xda-developers.com/showthread.php?t=2608178&page=18
:highfive:
aliguu said:
from the 'leaked kitkat' thread, it seems that if you dont flash BL step, this updated wont work and will cause errors.
http://forum.xda-developers.com/showthread.php?t=2608178&page=18
:highfive:
Click to expand...
Click to collapse
Yup 100% confirmed, Need Bootloader to install KK
radicalisto said:
Yup 100% confirmed, Need Bootloader to install KK
Click to expand...
Click to collapse
ok updated
Sir,
I'd like to ask. I just updated my device to 4.4. I noticed that it is no longer rooted.
I tried rooting again my device, but it is not working because of bootlooping problem.
Is there any remedy for this in order for me to be able to root my 4.4 device?
Thanks in advance.
Have you got the right cf autoroot file? - if not head over to chainfire.eu and grab the latest for Kitkat
Sent from my SM-N9005 using XDA Premium 4 mobile app
Skander1998 said:
Please remove the BL step or people will be stuck in 4.4.2 leak without being able to revert.
Click to expand...
Click to collapse
BL step is a must! without update the BL, your flash will fail and phone stuck.
KitKat 4.4.2 ROM must update the BL and they is no chances revert back to older 4.3 ROM.
Andrewtst said:
BL step is a must! without update the BL, your flash will fail and phone stuck.
KitKat 4.4.2 ROM must update the BL and they is no chances revert back to older 4.3 ROM.
Click to expand...
Click to collapse
That was corrected shortly after - I'm aware of this.
why did you guys need to update BL ??! i was on MJ7 and just went to Sammobile got the file and simpley flash it with odin now my phone is on kitkat :good: maybe because you were not in MJ7 hmm ??
btw how to root this kitkat version ??? konx doesn't matter.
I've just downloaded the Firmware from here http://www.sammobile.com/2014/01/13/breaking-android-4-4-2-kitkat-rolling-out-to-galaxy-note-3-sm-n9005/ and flashed it. Now Im on KitKat WITHOUT WIPING DATA! All My Apps,Music,Photos..are still there
hapticc said:
So today Kitkat update for Samsung Galaxy Note 3 SM N9005 has leaked and to update and download we have made a simple and short guide.
NOTE
-Your data will be wiped. So, back it up!
- You are doing this at your OWN risk. We are not responsible if you brick your device or your cat eats your phone.
- It will NOT increase your binary counter NOR void your warranty.
- This test firmware is a pre-release build and not official from Samsung.
Download
N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX.zip
Odin3_v3.09.zip
INSTRUCTIONS
Step 1
Extract (unzip) the firmware file
Extract Odin v3.09.ZIP file
Step 2
Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
Step 3
Connect phone and wait until you get a blue sign in Odin
Step 4
Add AP_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 to AP
Add BL_N9005XXUENA6_340325_REV03_user_low_ship_MULTI_CERT.tar.md5 to BL
Add CP_N9005XXUENA2_REV03_CL1277177.tar.md5 to CP
Add CSC_OXX_N9005OXXENA5_327209_REV03_user_low_ship_MULTI_CERT.tar.md5 to CSC
Note No need to update bootloader as suggest in #2
Step 5
Make sure re-partition is NOT ticked
Step 6
Click start button, relax and wait a few minutes and phone will restart.
ENJOY YOUR KITKAT NOTE 3
CREDITS: EASY HOWTO UPDATE NOTE 3 to latest leaked kitkat build
Click to expand...
Click to collapse
Even easier just download this http://live.samsung-updates.com/det...e_3_Snapdragon/SM-N9005/XEO/N9005XXUENA6.html
step to unzip and open odin 3.07 or 1.85
put in pda
flash and all is good!
Do you sure this way OK with Note 3 N9005 16G HongKong ver?
Please continue any discussion here. Thanks.
Susses Downgrade 4.3 to 4.1.2 Step by step
1.install Odin Mobile Pro susses
2. Open Mobile Odin Pro wait minute
3. Open File
4. Ext.SdCard go to keep official rom (N7100XXDMF2_N7100OLBDMD2_N7100DXDMF1_HOME.tar)
5. OK
6. Option Full Check and chose Root+SuperSU
7. Continue
8. Skip
9. Now device Reboot and Mobile Odin start
10. Compete device Reboot
11. Susses
Now you can get back setting rom 4.1.2 But ! until device have new bootloader 4.3 good luck.
Can device back to 4.1.2 but until Knox have 0x1
Didnt work
Im on BTU N7100XXUEMK9 and it didn't work...
Completely bogus...
srfairhurst said:
Im on BTU N7100XXUEMK9 and it didn't work...
Click to expand...
Click to collapse
Ok. I use rom N7100XXUEMK1 and get back to 4.1.2 N7100XXDME1 4.1.2 THL , Maybe but not work on BTU N7100XXUEMK9 sorry :crying:
Downgrading don't means the rom, it's downgrading bootloader so as to avoid knox trigger
And you have flashed rom through mobile odin which doesn't flash bootloader which is possible for everyone
BTW, this is not a development topic, mod should move it to general
माझ्या नोट 2 मधील टपाटाॅक प्रो मधुन पाठविला
succes back from ml6 with new bootloader very thanks
fyh said:
Downgrading don't means the rom, it's downgrading bootloader so as to avoid knox trigger
And you have flashed rom through mobile odin which doesn't flash bootloader which is possible for everyone
BTW, this is not a development topic, mod should move it to general
माझ्या नोट 2 मधील टपाटाॅक प्रो मधुन पाठविला
Click to expand...
Click to collapse
Ok. I say my device can back to 4.1.2 never say remove knox trigger . How topic is not good mod can delet now. Thank
Its Working...But The BootLoader Remains Same
rajvyas33 said:
Its Working...But The BootLoader Remains Same
Click to expand...
Click to collapse
Yes until have new bootloader 4.3 but I hope remove new bootloader 4.3 for future.
I have just updated my rooted 4.3 i9505 to 4.4.2 using mobile odin Pro v4. Here are the steps i followed:
1) Download firmware for your region from sammobile.com
2)Make a copy of firmware and Extract bootloader from firmware: aboot.mbn, rpm.mbn. sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn and Pack into a bootloader tar file with Total Commander (google it)
3) Use Mobile Odin Pro v4 to flash firmware from step 1 above. It will not update bootloader in firmware. Make sure you tick:
a) Enable Everoot
b) Inject Superuser (SuperSU)
c) Inject Mobile Odin
d) Download mode after flash (so that it will boot straight to download mode)
4) Use PC Odin 3.09 to flash bootloader tar file made in step 2 above. Tick Phone Bootloader Update. DO NOT tick Auto Reboot and F. Reset time.
5) Boot again into download mode to check Knox flag which should remain 0x0
6) Reboot device and wait up to 5mins.
Device will be updated to 4.4.2 and retains root and Knox remains 0x0.
Enjoy.
Edit: I used the information here to transform my S4 into S5:
www.androidpit.com/how-to-transform-your-galaxy-s4-into-an-s5
Thanks for the post
I'm curious why it's a two step process. Does mobile Odin not flash the bootloader?
I guess you could do the whole thing with desktop Odin, would I be right in saying you use mobile odin as it does the root for you?
[hello
i have in my s4 i9505 a 4.4.2 rom , no root
is possible use this method to root without tripping knox?
karmac1970 said:
[hello
i have in my s4 i9505 a 4.4.2 rom , no root
is possible use this method to root without tripping knox?
Click to expand...
Click to collapse
you need root first because mobile odin requires root, you are late bro because the new 4.4.2 bootloader has already fix for root de la vega knox 0x0
Upgrading gt-i9505 from 4.2.2 to 4.4.2 WanamLite
I updated from 4.2.2 stock rooted to WanamLite (4.4.2 Touchwiz pre-rooted) yesterday. It was pretty easy:
0) Titanium backup and Nandroid backup. I forgot to back up text messages and a few little things, but no big loss.
1) Flash this from Odin 3.07 (GSM + LTE modem) (as Phone not PDA)
2) Flash XXUEMK9 from here.
3) Install TWRP via custom recovery
4) Flash Wanam as PDA in Odin.
Seemed to work fine
Confusion
To avoid confusion I think people should know this only works if you already have root on 4.3 prior to MKF, it allows you to keep root without tripping knox.
http://forum.xda-developers.com/showpost.php?p=51488982
commandonz said:
Thanks for the post
I'm curious why it's a two step process. Does mobile Odin not flash the bootloader?
I guess you could do the whole thing with desktop Odin, would I be right in saying you use mobile odin as it does the root for you?
Click to expand...
Click to collapse
Mobile Odin does not flash Bootloader. That's why the second step is necessary. Yes, you are right. If you are already rooted, then mobile odin allows you to update the firmware and keep root. You will lose root after updating with desktop odin.
Cheers
Bordo_Bereli51 said:
you need root first because mobile odin requires root, you are late bro because the new 4.4.2 bootloader has already fix for root de la vega knox 0x0
Click to expand...
Click to collapse
You are right. No root method for 4.4.2 (for now) without tripping Knox flag.
I went from 4.2.2 quite easily to 4.4.2 using the steps above. I guess most people are on 4.3 though, 4.2.2 made it easier as Knox isn't on the phone at all.
commandonz said:
I went from 4.2.2 quite easily to 4.4.2 using the steps above. I guess most people are on 4.3 though, 4.2.2 made it easier as Knox isn't on the phone at all.
Click to expand...
Click to collapse
What's your current Knox flag? 0x0?
shayind4 said:
What's your current Knox flag? 0x0?
Click to expand...
Click to collapse
I stayed on a pre-knox bootloader as I went from 4.2.2 to 4.4.2, so I have no knox flag.
commandonz said:
I stayed on a pre-knox bootloader as I went from 4.2.2 to 4.4.2, so I have no knox flag.
Click to expand...
Click to collapse
Lucky you. I'm on 4.4.2 bootloader, Knox flag 0x0, rooted.
shayind4 said:
Lucky you. I'm on 4.4.2 bootloader, Knox flag 0x0, rooted.
Click to expand...
Click to collapse
I deliberately didn't upgrade to 4.3 and held of on 4.4 purely to avoid Knox. It probably wouldn't matter much because I never plan to use Knox, and I think you can still do most things with the knox flag tripped, but it seemed better to avoid.
4.4.2 isn't much different from 4.2.2 really. I'm hoping for a stability increase, maybe a slight performance increase and battery savings. But I mostly just wanted to come up to date.
Hi, you wrote that we need to make .tar file from this files:
shayind4 said:
2)Make a copy of firmware and Extract bootloader from firmware: aboot.mbn, rpm.mbn. sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn and Pack into a bootloader tar file with Total Commander (google it)
Click to expand...
Click to collapse
I found another tutorial for this and that user wrote this:
3. Package 2 Tar files, one with the bootloader ( aboot.mbn,sbl1.mbn,sbl2.mbn, sbl3.mbn), the second one with everything else.
Click to expand...
Click to collapse
Are this files- tz.mbn and rpm.mbn important too? Or it doesn't matter?
pRo_lama said:
Hi, you wrote that we need to make .tar file from this files:
I found another tutorial for this and that user wrote this:
Are this files- tz.mbn and rpm.mbn important too? Or it doesn't matter?
Click to expand...
Click to collapse
Hi
All the 6 mbn files are bootloader files needed for the bootloader tar file.
You need 2 tar files:
A) Downloaded firmware= tar file with all the contents (you dont have to open it). You can make a copy to use in step 2 below for extracting mbn files (bootloader files). You will notice that step 2 in OP says make a copy of downloaded firmware.
B) Bootloader tar = all the mbn files
Mobile odin (OP step 3) does not flash bootloader when you use the downloaded full firmware (in A above). That's why you need the bootloader tar to be flashed via PC odin (OP step 4).
Both tutorials are similar.
Cheers
shayind4 said:
I have just updated my rooted 4.3 i9505 to 4.4.2 using mobile odin Pro v4. Here are the steps i followed:
1) Download firmware for your region from sammobile.com
2)Make a copy of firmware and Extract bootloader from firmware: aboot.mbn, rpm.mbn. sbl1.mbn, sbl2.mbn, sbl3.mbn, tz.mbn and Pack into a bootloader tar file with Total Commander (google it)
3) Use Mobile Odin Pro v4 to flash firmware from step 1 above. It will not update bootloader in firmware. Make sure you tick:
a) Enable Everoot
b) Inject Superuser (SuperSU)
c) Inject Mobile Odin
d) Download mode after flash (so that it will boot straight to download mode)
4) Use PC Odin 3.09 to flash bootloader tar file made in step 2 above. Tick Phone Bootloader Update. DO NOT tick Auto Reboot and F. Reset time.
5) Boot again into download mode to check Knox flag which should remain 0x0
6) Reboot device and wait up to 5mins.
Device will be updated to 4.4.2 and retains root and Knox remains 0x0.
Enjoy.
Edit: I used the information here to transform my S4 into S5:
www.androidpit.com/how-to-transform-your-galaxy-s4-into-an-s5
Click to expand...
Click to collapse
Thank you for your explanation. But I have some questions:
1. Can you use the same method to update keeping root from a 4.3 rooted version to a more recent 4.3 not safe-rootable version (not rootable without triggering the knox)?
2. Can you first flash the new bootloader with PC Odin and then all the rest with Mobile Odin?
3. What happens if you only flash with Mobile Odin everything except the new bootloader (new firmware/old bootloader)? Does the device boot?
4. What happens instead if you only flash the new bootloader with the PC Odin (new bootloader/old firmware)? Does the device boot?
5. Can you use your method (adequately adapted) to downgrade the firmware? That is, after an update to 4.4.2 or a newer 4.3, can you just flash the old firmware with Mobile Odin, keeping the new bootloader so that you do not trigger the knox (new bootloader/older firmware)?
Thank in advance.
odicamillo said:
Thank you for your explanation. But I have some questions:
1. Can you use the same method to update keeping root from a 4.3 rooted version to a more recent 4.3 not safe-rootable version (not rootable without triggering the knox)?
2. Can you first flash the new bootloader with PC Odin and then all the rest with Mobile Odin?
3. What happens if you only flash with Mobile Odin everything except the new bootloader (new firmware/old bootloader)? Does the device boot?
4. What happens instead if you only flash the new bootloader with the PC Odin (new bootloader/old firmware)? Does the device boot?
5. Can you use your method (adequately adapted) to downgrade the firmware? That is, after an update to 4.4.2 or a newer 4.3, can you just flash the old firmware with Mobile Odin, keeping the new bootloader so that you do not trigger the knox (new bootloader/older firmware)?
Thank in advance.
Click to expand...
Click to collapse
Hi
1) Yes. Just update Supersu and disable Knox. I used it safely to update from rooted 4.3 to rooted 4.4.2, nox flag 0x0.
2) No. You need to flash firmware with Mobile odin first so that root can be injected at the same time (before flashing bootloader with PC Odin).
3) The device may boot but not sure with this tutorial. Some people have updated from 4.2.2 (no knox bootloader) to 4.4.2 keeping old bootloader, and they have no KNOX using a different method. Check post #5.
4) It may boot but you will lose root. You cannot safely root afterwards.
5) NO. Flashing older firmware or older bootloader will trigger Knox flag.
regards
nickp27 said:
To avoid confusion I think people should know this only works if you already have root on 4.3 prior to MKF, it allows you to keep root without tripping knox.
Click to expand...
Click to collapse
currently I have MKF, rooted via saferoot, knox 0x0.
spamtrash said:
currently I have MKF, rooted via saferoot, knox 0x0.
Click to expand...
Click to collapse
Hi ,
I wonder the same thing, if the tutorial is working from a MKF 4.3 with saferoot
Thanks for your answers
lukvdb78 said:
Hi ,
I wonder the same thing, if the tutorial is working from a MKF 4.3 with saferoot
Thanks for your answers
Click to expand...
Click to collapse
When I said prior to, I meant including. If you have knox 0x0 and root either through saferoot or kingo then this should work.
Hi folks . Dear @Chainfire update your CF-Auto-Root base and now we get opportunity to have root with the simplest method ! It works now on 5.02 and 5.1.1 stock firmwares . Sorry but knox is tripped .
Now this works on SM-T530 , SM-T530NU , SM-T535 , SM-T532 , SM-T533 ,SM-T330NU , SM-T331
Complete list you can see on https://autoroot.chainfire.eu/ .
HOW INSTALL :
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA(AP)
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin file, press the PDA(AP) button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
DOWNLOADS:
SM-T530
SM-T530NU
SM-T533
SM-T535
SM-T330NU
SM-T331
Added SM-T330NU and SM-T331
worked on 533 but are we now able to install twrp permanent?? anyway thanks a lot for root!
looking-g said:
worked on 533 but are we now able to install twrp permanent?? anyway thanks a lot for root!
Click to expand...
Click to collapse
You better ask @HausiX10 about this in PM .
Wow thank you for this! I successfully rooted my Tab 4 SM-T330NU using 5.1.1 on the first attempt with the files provided here. I had been trying all weekend to successful root my device using other methods and files, but for some reason they all resulted in bootloops. I kept reading through the troubleshoot forums for a solution, but nothing worked. I wish I would have found this thread sooner, it would have saved me a lot of problems!
bootloop
Hi I'm stuck in bootloop; set warranty bit: kernel. Any solutions?
Still working?
"You can find more detailed instructions and assistance at XDA." Mhm, I am on XDA so where are that detailed instructions? And when I finished root Unified daemon, Media memory and TouchWiz - home are stopping working. Is it normal?
I need sm-t537v please
What about the bootloader?
repey6 said:
Hi folks . Dear @Chainfire update your CF-Auto-Root base and now we get opportunity to have root with the simplest method ! It works now on 5.02 and 5.1.1 stock firmwares . Sorry but knox is tripped .
Now this works on SM-T530 , SM-T530NU , SM-T535 , SM-T532 , SM-T533 ,SM-T330NU , SM-T331
Complete list you can see on https://autoroot.chainfire.eu/ .
HOW INSTALL :
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA(AP)
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin file, press the PDA(AP) button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
DOWNLOADS:
SM-T530
SM-T530NU
SM-T533
SM-T535
SM-T330NU
SM-T331
Click to expand...
Click to collapse
Hi @repey6. Thanks for the tutorial.
Do you know if I need to worry about unlocking the bootloader on my device? It's a SM-T531 (Brazil) running 4.4.2.
@Chainfire's auto-root page warns that flashing the auto-root with the bootloader locked will probably brick it, but I'm so noob that I don't even know if mine is locked or not. I can only imagine that it is, since I haven't done anything close to flashing anything on this device.
Thanks for your attention.
BourbonCowboy said:
Hi @repey6. Thanks for the tutorial.
Do you know if I need to worry about unlocking the bootloader on my device? It's a SM-T531 (Brazil) running 4.4.2.
@Chainfire's auto-root page warns that flashing the auto-root with the bootloader locked will probably brick it, but I'm so noob that I don't even know if mine is locked or not. I can only imagine that it is, since I haven't done anything close to flashing anything on this device.
Thanks for your attention.
Click to expand...
Click to collapse
Hi. Your bootloader is not unlocking. But supersu is not actual now. Magisk root is better.
So how to I unlock it?
repey6 said:
Hi. Your bootloader is not unlocking. But supersu is not actual now. Magisk root is better.
Click to expand...
Click to collapse
Thanks for the answer! So, how do I unlock the bootloader then? Haven't been able to find it here in XDA. Also, I've found a post here on the forum where a user claimed Magisk didn't work in 5.0.2 because the kernel was too old. Do you know if Towelroot is better?
Pls help. :crying:
BourbonCowboy said:
So how to I unlock it?
Thanks for the answer! So, how do I unlock the bootloader then? Haven't been able to find it here in XDA. Also, I've found a post here on the forum where a user claimed Magisk didn't work in 5.0.2 because the kernel was too old. Do you know if Towelroot is better?
Pls help. :crying:
Click to expand...
Click to collapse
have you found a solution? same problem here!!!!!!!!!!!!!
A simple guide for users which will help them to install TWRP on their S8 after Oreo Update.
This guide is only for Exynos models.
Requirement -
1. PC/Laptop
2. Original Samsung USB Type-C Cable
3. Prince Comsy Odin (Because some users reported on this thread that normal Odin doesn't work)
Instructions -
1. Backup your important data from internal storage before proceeding towards the installation.
2. Now go to Settings - About Phone - Software Information - Tap On Build Number 7 Times.
3. Now come back to Settings Home and Open Developer Options. Check OEM Unlock is turned ON.
4. Power off device and boot into download mode.
5. Connect your device to the PC/Laptop.
6. Now Open Prince Comsy Odin and click on the AP option.
7. Choose the TWRP .tar file and press the START button.
8. Now after Odin says PASS, press the VOLUME UP, BIXBY KEY, and POWER BUTTON at the same time until device boots into TWRP recovery.
9. Now allow the modifications and go to WIPE option.
10. Choose FORMAT DATA - Type yes - ENTER.
11. Just Reboot Once Into Recovery Once.
12. Flash no-verity-opt-encrypt.zip.
12. Now Choose INSTALL option and install Magisk or SuperSU.
13. Done!
You can also refer to this video for installation of TWRP - https://www.youtube.com/watch?v=2SqgHFcHLMw
Downloads -
Latest TWRP For Exynos S8 - TWRP 3.2.1-0-DREAMLTE
Prince Comsy Odin - https://drive.google.com/open?id=1enVG5a_ocyjhRlta8AX_0b7LLoHWciVU
No dm-verity - https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Magisk - https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
SuperSU - https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Credits -
@jesec for TWRP
@topjohnwu for Magisk
@Chainfire for SuperSU
Prince Comsy Odin
The main problem is that most users dont have oem unlock after oreo update (e.g me)
EugenStanis said:
The main problem is that most users dont have oem unlock after oreo update (e.g me)
Click to expand...
Click to collapse
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox
Ruturaj Kadam said:
Flash this official firmware through Odin if you have Exynos S8, and you'll get OEM unlock option.
I also manually updated to Oreo through this firmware and not through OTA. Also, note that flashing this will not wipe any of your existing data and also will not trip your knox
Click to expand...
Click to collapse
Flashed official XEO for Poland and still OEM unlock isnt there :/
Does the Oreo update affect the the locked bootloader on the Snapdragon version? I thought it was impossible to install TWRP on the Snapdragon versions of the S8?
I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard
EugenStanis said:
Flashed official XEO for Poland and still OEM unlock isnt there :/
Click to expand...
Click to collapse
Try use AQK7 ( 4 file firmware + re-partition PIT)
In my case I 100% success returned form CRAP to AQK7.
OEM unlock is in dev settings, no RMM and FRP.
Powodzenia ^_^
I'm guessing this is not for the US snapdragon variant.
There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.
Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.
Will822 said:
I'm guessing this is not for the US snapdragon variant.
Click to expand...
Click to collapse
I'm sorry! It was one of my friends who told me the method is same. I'm sorry again. OP edited
iamnotexisting said:
There's no way this can work on US Snapdragon, we don't have a OEM unlock option here.
Click to expand...
Click to collapse
I'm sorry for that! Edited the OP! Got misguided due to one of my friends
Silenus21 said:
Tired of the US locked bootloaders.
Next time I'll get a Exynos GS9 for sure.
Click to expand...
Click to collapse
Haha yes! Exynos devices are best in performance and battery too.
This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?
168 hours Open my device oem lock on of after twrp flash data storage 0 dm verity flash wipe data
thiagomed said:
This method trip knox? I can still use Samsung Pay and other features that require Knox to not be tripped?
Click to expand...
Click to collapse
TWRP trips Knox if I'm not mistaken.
i did this guide and everything is went good but when i restarted the phone it went to a softbrick and i had to do a restore...
the error was something on the original binary
to have the OEM option, will I have to go back to crap?
I have just tried this method and booted into TWRP but the screen was totally unresponsive, rebooted and still the same. I had to go back to Oreo.
How do I get around this problem?
dr.vetony said:
I have installed but now shows me 0 mb on inernal sotorage , ive tried to change data but nothing cant mount sdcard
Click to expand...
Click to collapse
Wipe / format data - " yes"