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!!!!!!!!!!!!!
Related
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
For those who want root and custom recovery on 4.4.2 here is my way without root binary errors or recovery issues....
1. Downloaded 4.4.2 for Canada from Sammobile and flash via odin
2. Install this Recovery https://mega.co.nz/#!kEUzAS5a!a6TA0xuSg-pEYxSmZxnjmcB7cNOwRCZ_MqMiwXvD65c via odin Credits to Angel_666
3. Install this SuperSU http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip?retrieve_file=1 via TWRP Recovery
4. Reboot and enjoy
Thats how i did and have now fully working 4.4.2 with custom recovery and root access ...
hey
Thanks.
now better
Already rooted
I already have my tab 3 10.1 rooted so if i install the new KitKat 4.4.2 will i need to reroot??
lindsay56 said:
I already have my tab 3 10.1 rooted so if i install the new KitKat 4.4.2 will i need to reroot??
Click to expand...
Click to collapse
Ofcourse , you'll need to reroot it .
Don't forget to press the thanx button!!!!!
Sent from my GT-P5210 using XDA Premium 4 mobile app
If i am on 4.2 stock rooted (US version), will this Canadian 4.42 ROM and root procedure work for me?
Thanks
OKAstro said:
If i am on 4.2 stock rooted (US version), will this Canadian 4.42 ROM and root procedure work for me?
Thanks
Click to expand...
Click to collapse
Yeah , It will work . I have also USA version . Just download firmware from sammobile & flash through odin v3.09 . And then follow what this guide says .
Don't forget to press the thanks button!!!!!
Sent from my GT-P5210 using XDA Premium 4 mobile app
Use this app to flash recovery img file, in case you have difficulties installing cwm or philz: https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
mzheng086 said:
Use this app to flash recovery img file, in case you have difficulties installing cwm or philz: https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools
Click to expand...
Click to collapse
following this guilde you need custom recovery to root so you can't use root app's without root
Can any one say whether the Canadian 4.4.2 has multi user enabled, if not has any one tried to apply the multi user hack.
Newbie question. If I wanted to temporarily disable the root so that apps which may have an issue with rooted device can continue to work how would this be done. I saw in one forum where someone said they were only able to do this with the 4.2.2 ROM.
Legendsmoker -
I just got prompted when starting KIES for the KitKat update. I have the US version of the Tab 3 10.1 (5210). I assume I can use your root steps to root the US KitKat firmware?
Here's what KIES says:
Current firmware version : PDA:NB2 / CSC:NB2 (XAR)
Latest firmware version : PDA:NH2 / CSC:NH2 (XAR)
Thanks
OKAstro said:
Legendsmoker -
I just got prompted when starting KIES for the KitKat update. I have the US version of the Tab 3 10.1 (5210). I assume I can use your root steps to root the US KitKat firmware?
Here's what KIES says:
Current firmware version : PDA:NB2 / CSC:NB2 (XAR)
Latest firmware version : PDA:NH2 / CSC:NH2 (XAR)
Thanks
Click to expand...
Click to collapse
Sure you can
Wysłane z mojego SM-G900F przy użyciu Tapatalka
Thanks, rooted without any problem.
norms123 said:
Newbie question. If I wanted to temporarily disable the root so that apps which may have an issue with rooted device can continue to work how would this be done. I saw in one forum where someone said they were only able to do this with the 4.2.2 ROM.
Click to expand...
Click to collapse
Use the xposed framework and there is a plugin called rootcloak.
Fix?
I recently did the Samsung update to Android 4.4.2. I've tried multiple times to root my device, but each time, the SuperSu has not functioned properly. The first time it would not update correctly, so I tried a different .zip and the SuperSu in that one would freeze every time I would try to use it. Will this fix the problems I am having?
thatgentleman said:
I recently did the Samsung update to Android 4.4.2. I've tried multiple times to root my device, but each time, the SuperSu has not functioned properly. The first time it would not update correctly, so I tried a different .zip and the SuperSu in that one would freeze every time I would try to use it. Will this fix the problems I am having?
Click to expand...
Click to collapse
just follow my guide
LegendSmoker said:
just follow my guide
Click to expand...
Click to collapse
Yeap! as LegendSmoker is referring, it seems chainfire SuperSU-v2.02 is the only one to survive 4.4.2 anti-root attacks!
LegendSmoker said:
just follow my guide
Click to expand...
Click to collapse
Thank you. Worked perfectly!
Updated files help
Thanks so much. i kept using guides that were for older android versions ergo older non-updated root files and recovery files :good::good:
Hi everyone,
Trying to root my Galaxy s6 SM-G920I India version but no luck. Had to restore stock firmware thrice today. Every time I used ODIN 3.10.6 with Unibase or Unikernal it would say kernel is not SEAndroid enforcing and stick to a bootloop. If I use the CF auto root method it says Recovery is not SEAndroid enforcing and again bootloop.
Trying the alternative method of installing TWRP also does not work and I get the same recovery enforcing message and bootloop. Please help. R/L is off.
I had the same problem with Indian firmware. The latest one.
I quit trying to get root.
Sent from my SM-G920I using Tapatalk
chubutnet said:
I had the same problem with Indian firmware. The latest one.
I quit trying to get root.
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
I got the latest update about a week ago. Did you too?
aweracker said:
Hi everyone,
Trying to root my Galaxy s6 SM-G920I India version but no luck. Had to restore stock firmware thrice today. Every time I used ODIN 3.10.6 with Unibase or Unikernal it would say kernel is not SEAndroid enforcing and stick to a bootloop. If I use the CF auto root method it says Recovery is not SEAndroid enforcing and again bootloop.
Trying the alternative method of installing TWRP also does not work and I get the same recovery enforcing message and bootloop. Please help. R/L is off.
Click to expand...
Click to collapse
tried the same things u tried and no success at all....guys plz help us...
Sent from my SM-G920I using Tapatalk
aweracker said:
I got the latest update about a week ago. Did you too?
Click to expand...
Click to collapse
No I haven't, I flash the firmware with odin, I had zto before.
Still can't root, don't know who else ask for help
chubutnet said:
No I haven't, I flash the firmware with odin, I had zto before.
Still can't root, don't know who else ask for help
Click to expand...
Click to collapse
I got the solution and I have also written a blog post on it. Here is the guide. Recovery or Kernel error will be tackled with this guide. Please refer to it. Please refer to my blog. Techzane dot com. The first article.
i found a tutorial to install TWRP on galaxy s6 . very easiest tutorial.
https://www.youtube.com/watch?v=9-SM0LX5n4U
doesnt work on some of the newer 5.1.1 firmwares
emmawilliam834 said:
i found a tutorial to install TWRP on galaxy s6 . very easiest tutorial.
https://www.youtube.com/watch?v=9-SM0LX5n4U
Click to expand...
Click to collapse
I have the issue too guys. The newest UAE firmware(CSC XSG) is not letting the TWRP stick after flashing with Odin. I've asked for help over in the Help & Troubleshooting section. Hopefully we can figure this out.
aweracker said:
I got the solution and I have also written a blog post on it. Here is the guide. Recovery or Kernel error will be tackled with this guide. Please refer to it. Please refer to my blog. Techzane dot com. The first article.
Click to expand...
Click to collapse
I read your blog. The thing is that I can't root the India firmware. Is the firm I'm using and I don't want to change it cause it's working really well.
But seems that is unable to root. And I want to erase some bloatware to make it lighter
Thanks anyway for your help
Sent from my SM-G920I using Tapatalk
aweracker said:
Hi everyone,
Trying to root my Galaxy s6 SM-G920I India version but no luck. Had to restore stock firmware thrice today. Every time I used ODIN 3.10.6 with Unibase or Unikernal it would say kernel is not SEAndroid enforcing and stick to a bootloop. If I use the CF auto root method it says Recovery is not SEAndroid enforcing and again bootloop.
Trying the alternative method of installing TWRP also does not work and I get the same recovery enforcing message and bootloop. Please help. R/L is off.
Click to expand...
Click to collapse
I also tried to root my Indian S6 5.1.1 with Unikernel but my phone got stuck on boot loop. Then i had to flash a new stock firmware. I also tried to downgrade to 5.0.1 but no luck again boot loop. Someone please help us to root S6 5.1.1. Thanks in advance.
sonu42197 said:
I also tried to root my Indian S6 5.1.1 with Unikernel but my phone got stuck on boot loop. Then i had to flash a new stock firmware. I also tried to downgrade to 5.0.1 but no luck again boot loop. Someone please help us to root S6 5.1.1. Thanks in advance.
Click to expand...
Click to collapse
the only way i was able to root was flash the g920f twrp recover then flashing the beta supersu 2.66...
but that root was not so stable so i also reflashed the stock firmware and today i have no root...
just waiting for marshmallow...
Sent from my SM-G920I using Tapatalk
Cyanandroid said:
the only way i was able to root was flash the g920f twrp recover then flashing the beta supersu 2.66...
but that root was not so stable so i also reflashed the stock firmware and today i have no root...
just waiting for marshmallow...
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
When you rooted your S6 G920F that time was your phone having 5.1.1 android and DOL5 bootloader.
sonu42197 said:
When you rooted your S6 G920F that time was your phone having 5.1.1 android and DOL5 bootloader.
Click to expand...
Click to collapse
yeah
Sent from my SM-G920I using Tapatalk
Cyanandroid said:
yeah
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
When you flashed twrp on your phone you didn't got in a bootloop. Because when i tried this method i got in bootloop.
chubutnet said:
I read your blog. The thing is that I can't root the India firmware. Is the firm I'm using and I don't want to change it cause it's working really well.
But seems that is unable to root. And I want to erase some bloatware to make it lighter
Thanks anyway for your help
Sent from my SM-G920I using Tapatalk
Click to expand...
Click to collapse
Scroll up, I have written the solution there. refer to this website - techzane dot com
aweracker said:
Scroll up, I have written the solution there. refer to this website - techzane dot com
Click to expand...
Click to collapse
I tried this method on this website but no luck.????
There is a thread on xda about how to root DOL5 formware by an INDIAN USER USING G925I.
Not all had success with it. I would suggest sticking with DOK9 firmware and wait for a few days as android 6.0.1 has started rolling already in Korea for s6(both variants)
The changes between DOK9 and DOL5 is not huge and not worth an upgrade
aweracker said:
Hi everyone,
Trying to root my Galaxy s6 SM-G920I India version but no luck. Had to restore stock firmware thrice today. Every time I used ODIN 3.10.6 with Unibase or Unikernal it would say kernel is not SEAndroid enforcing and stick to a bootloop. If I use the CF auto root method it says Recovery is not SEAndroid enforcing and again bootloop.
Trying the alternative method of installing TWRP also does not work and I get the same recovery enforcing message and bootloop. Please help. R/L is off.
Click to expand...
Click to collapse
I have rooted my s6 today only with 5.1.1 Android and DOL5 bootloader. I flashed twrp
down below is link. You will face a little bit of problem while going in recovery but dont worry you will be able to enter after some tries. When u enter there flash super su 2.66 and u have rooted your s6.
i know it's not country speific, but was trying to flash TWRP.. and in some guide it was written you need to enable OEM unlock..
kakabakk20 said:
i know it's not country speific, but was trying to flash TWRP.. and in some guide it was written you need to enable OEM unlock..
Click to expand...
Click to collapse
Don't worry about it. International unlocked version doesn't have that option. Just go ahead and flash twrp and then whatever you want.
kakabakk20 said:
i know it's not country speific, but was trying to flash TWRP.. and in some guide it was written you need to enable OEM unlock..
Click to expand...
Click to collapse
No need to Unlock Bootloader, International Devices comes with Unlocked Bootloader. So flash twrp through odin and supersu through twrp or any custom kernel.
So make sure after you flash twrp through odin, flash supersu or custom kernel or else device will be stuck in bootloop
The title of this post : OEM unlock option missing in s6 nougat G920i(india)
@kakabakk20 that device is G920I (LATAM, Singapore, India, Australia) its not Global device... and yes its country speific!
Global device is G920F!
Look under the variants of S6 flat screen.
Versions: G9200 (Hong Kong), G9208 (China), G9208/SS (China), G9209 (China), G920A (AT&T), G920F (Global), G920FD (Pakistan, Philippines), G920I (LATAM, Singapore, India, Australia), G920S (Korea), G920T (T-Mobile)
vforvlive said:
The title of this post : OEM unlock option missing in s6 nougat G920i(india)
@kakabakk20 that device is G920I (LATAM, Singapore, India, Australia) its not Global device... and yes its country speific!
Global device is G920F!
Look under the variants of S6 flat screen.
Versions: G9200 (Hong Kong), G9208 (China), G9208/SS (China), G9209 (China), G920A (AT&T), G920F (Global), G920FD (Pakistan, Philippines), G920I (LATAM, Singapore, India, Australia), G920S (Korea), G920T (T-Mobile)
Click to expand...
Click to collapse
the bracket in which i wrote india was just to tell people in which country i am using.. i am not trying to encapsulate all the countries which are using G920I.....(i think so you took me wrong there by country specific i just meant india... so technically i am correct).. thanks for your help but my problem was solved after the first two answers only!
Boot loop problem after flashing
raju.d said:
No need to Unlock Bootloader, International Devices comes with Unlocked Bootloader. So flash twrp through odin and supersu through twrp or any custom kernel.
So make sure after you flash twrp through odin, flash supersu or custom kernel or else device will be stuck in bootloop
Click to expand...
Click to collapse
Hi, I'm new here... I just found your answer and it's what it is happening to me... I'm stucked in bootloop after flashing twrp...
is it happening because I don't have oem unlock option?
actually the thing is this...
I have a galaxy s6... android 7 official from spain PHE international version i think
when i flash twrp with odin... it says pass... the phone start but then I cant go to twrp mode... (just the normal one)
so I tried to start the recovery mode buttons and it worked.... I cloud flashed magisk and did my things....but
when i tried to flash uninstall magisk and boot system it get stucked in bootloop and I think it is releated to the first problem
could you please help with this??
I'm asking you because I saw you wrote this:
So make sure after you flash twrp through odin, flash supersu or custom kernel or else device will be stuck in bootloop
I dont understand very well the sentence but I see you mention the bootloop problem after flashing twrp
Thank you so much and Im sorry for my poor english
Mulder89 said:
Hi, I'm new here... I just found your answer and it's what it is happening to me... I'm stucked in bootloop after flashing twrp...
is it happening because I don't have oem unlock option?
actually the thing is this...
I have a galaxy s6... android 7 official from spain PHE international version i think
when i flash twrp with odin... it says pass... the phone start but then I cant go to twrp mode... (just the normal one)
so I tried to start the recovery mode buttons and it worked.... I cloud flashed magisk and did my things....but
when i tried to flash uninstall magisk and boot system it get stucked in bootloop and I think it is releated to the first problem
could you please help with this??
I'm asking you because I saw you wrote this:
So make sure after you flash twrp through odin, flash supersu or custom kernel or else device will be stuck in bootloop
I dont understand very well the sentence but I see you mention the bootloop problem after flashing twrp
Thank you so much and Im sorry for my poor english
Click to expand...
Click to collapse
Sorry about that, but once you have flashed twrp through odin. You have to flash supersu or magisk else device will go in bootloop.
As you have installed a custom recovery, so as per what i know it wont let the boot.img to load and goes into bootloop.
So after flashing twrp in odin, the next step you need to do is flash supersu or magisk any one of these as per you choice.
Then your good to go and boot.img will be able to load and no more bootloops.
---------- Post added at 11:33 AM ---------- Previous post was at 11:29 AM ----------
Mulder89 said:
Hi, I'm new here... I just found your answer and it's what it is happening to me... I'm stucked in bootloop after flashing twrp...
is it happening because I don't have oem unlock option?
actually the thing is this...
I have a galaxy s6... android 7 official from spain PHE international version i think
when i flash twrp with odin... it says pass... the phone start but then I cant go to twrp mode... (just the normal one)
so I tried to start the recovery mode buttons and it worked.... I cloud flashed magisk and did my things....but
when i tried to flash uninstall magisk and boot system it get stucked in bootloop and I think it is releated to the first problem
could you please help with this??
I'm asking you because I saw you wrote this:
So make sure after you flash twrp through odin, flash supersu or custom kernel or else device will be stuck in bootloop
I dont understand very well the sentence but I see you mention the bootloop problem after flashing twrp
Thank you so much and Im sorry for my poor english
Click to expand...
Click to collapse
Download twrp from here https://twrp.me/devices/samsunggalaxys6.html
Better use supersu, not a big fan of magisk though.
If its not uninstalling magisk, flash boot and recovery file in odin.
So this clears magisk from system or you can do is clear cache/dalvik cache/data all these 3 options to get rid of magisk but it will reset you device but your files wont be deleted, but it will factory reset your device.
AUSTURIA DRE to not have oem unlock. device not international device is bradnded Drei 3
Hey. I did and successfully tested the mod of stock firmware 6.0 T585XXU2AQA2 SEK region (Ukraine, although it does not matter).
The bottom line is that, you install via Odin the firmware itself and the custom recovery - TWRP , that is, two in one . And after successfully installation firmware via Odin automatically opens immediately TWRP, where I recommend immediately to install SuperSU or latest magisk and then fix or attach below . In result we have a stock firmware with TWRP and root.
Notice. Do factory reset before flashing.
P.S. I tried this mod over current 6.0 rom with installed TWRP. I think if try this mod without installed TWRP you need checked internal memory. If you have 0mb you need to do Format data before flashing supersu and fix.
Downloads : https://www.androidfilehost.com/?fid=673368273298975848
UPDATE. I did mod based on the 8.1 OS firmware
Latest builds no need fix only magisk!
Downloads all builds for SM-T585 and SM-T580(Updatable)
Importantly :
If you have issue with download change your browser to Firefox or use downloader.
Credit:
@followmsi for his awesome TWRP
Did the same for 7.0 .
Download: https://www.androidfilehost.com/?fid=817550096634790062
repey6 said:
Did the same for 7.0 .
Download: https://www.androidfilehost.com/?fid=817550096634790062
Click to expand...
Click to collapse
Works fine. Very comfortable. Thanks.:good:
It works fine; In place of SuperSu, I installed Magisk!
Thanks
Thanks
Thanks
orianco said:
It works fine; In place of SuperSu, I installed Magisk!
Thanks
Thanks
Thanks
Click to expand...
Click to collapse
Thanks for good feadback and info about magisk!:good:
Hello, I have a simple question. I am getting the SM-T585 soon and found your thread while searching for TWRP for that tablet. I like the idea of having stock with the custom recovery. I have currently the Tab 9.7 with uses a single file for firmware. The question I have is where in odin do I put the HOME file? or can that one be skipped? Thanks in advance for any responses that answer this. Peace
bobfrantic said:
Hello, I have a simple question. I am getting the SM-T585 soon and found your thread while searching for TWRP for that tablet. I like the idea of having stock with the custom recovery. I have currently the Tab 9.7 with uses a single file for firmware. The question I have is where in odin do I put the HOME file? or can that one be skipped? Thanks in advance for any responses that answer this. Peace
Click to expand...
Click to collapse
CSC HOME saved your data . CSC OXE format your data . Do your choice.
Next 3 files to appropriate tabs : BL to BL , AP to AP , CP to CP .
Hello,
I have a tablet SM-T585
I have used your "Simplest method to get ROOT & TWRP"(https://forum.xda-developers.com/galaxy-tab-a/how-to/root-t3674409) to get root with SuperSU : it works perfectly.
I have used ODIN to flash TWRP : no problem.
After some modifications on the Settings,I made a BackUP.
Now my question : is it possible to install this Backup via ODIN ?
Thanks for your advice
sophivan said:
Hello,
I have a tablet SM-T585
I have used your "Simplest method to get ROOT & TWRP"(https://forum.xda-developers.com/galaxy-tab-a/how-to/root-t3674409) to get root with SuperSU : it works perfectly.
I have used ODIN to flash TWRP : no problem.
After some modifications on the Settings,I made a BackUP.
Now my question : is it possible to install this Backup via ODIN ?
Thanks for your advice
Click to expand...
Click to collapse
No , only you can restore your backup via TWRP.
Thank you, I ll try it once the download is completed in 2 hrs.
But my question is I have this SM-t585 with originally android 7.0, & I want to downgrade it to 6.0, is it possible?
Jasmin74 said:
Thank you, I ll try it once the download is completed in 2 hrs.
But my question is I have this SM-t585 with originally android 7.0, & I want to downgrade it to 6.0, is it possible?
Click to expand...
Click to collapse
Yes. Need to do wipe data&cache or use CSC OXE not Home.
So the 6.0 is included with your file??
Mod have full stock archive . Only AP tar.md5 changed
Hello,
I got : Re-Partition operation failed.
Jasmin74 said:
Hello,
I got : Re-Partition operation failed.
Click to expand...
Click to collapse
Log screenshot please. What the device you flash?
sorry, I closed it now. it's Tab A 2016 - sm-t585
https://samsungodin.com/ for info.
repey6 said:
Did the same for 7.0 .
Download: https://www.androidfilehost.com/?fid=817550096634790062
Click to expand...
Click to collapse
buen trabajo good:good:
---------- Post added at 03:13 AM ---------- Previous post was at 03:09 AM ----------
jesusrios said:
buen trabajo good:good:
Click to expand...
Click to collapse
is very good worquin:good:
Everything is fine now..thank you.
UPDATE. I made another mod based on the firmware T585XXU2BRB2 with cut userdata and without CSC. TWRP latest 3.2.1-0 from @followmsi. CSC can not be added to Odin, it remains the same.