Related
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
ODIN download mode
- Turn your device off and unplug it
- Wait 30 seconds (screen off doesn't mean the device has finished turning off)
- Press-and-hold the power button and very shortly after (0.5 seconds, but not simultaneously) press-and-hold the left volume button
- Release the buttons as soon as you see something on screen. You should be looking at a USB icon and a digging Android.
- Make sure the digging Android is flashing. If the USB icon is flashing, press the left volume button to switch to the Android.
- Press the right volume button to select and enter download mode
Bootloader unlock
Flashing this firmware will also unlock the bootloader.
Included languages
Deutsch
English (UK)
English (US)
Espanol
Italiano
Nederlands
Portugues
Instructions (Windows)
- Download and extract the attached Odin zip file
- Download and extract the ROM (you should end up with three .tar.md5 files)
- Go into bootloader mode, as described above
- Start Odin
- Look at the attached Odin screenshot, make sure of the following:
--- Re-Partition: NOT checked
--- Auto Reboot: checked
--- F. Reset Time: checked
--- Flash Lock: NOT checked
--- Phone EFS clear: NOT checked
--- Phone Bootloader Update: NOT checked
- Press the big BOOTLOADER button on the right and select the "BOOTLOADER_P7100BUKC8.tar.md5" file
- Press the big PDA button on the right and select the "PDA_SIGNED_HRI83_BUKDF.tar.md5" file
- Press the big PHONE button on the right and select the "MODEM_HRI83_BUKDF_REV_03.tar.md5" file
- Connect your device with the USB cable
- Wait a few seconds, Odin should say it is now connected
- Hit the Start button, and wait until the device boots
- Press the Thanks button below this post and/or donate
Random notes
"adb reboot recovery", "adb reboot download" and "adb reboot bootloader" now appear to be working, they weren't on the KD9 ROM my device came with.
Download
Here is the link: http://www.multiupload.com/LWN6RHF8WJ
NOTICE: FLASHING ALSO WIPES YOUR SD-CARD !
Chainfire said:
Just received my Tab, and minutes before somebody gave me this update, which is indeed newer than the KD9 I had.
Click to expand...
Click to collapse
Nice gift!
My bootloader was locked before this update, and I did not attempt to unlock it. Download mode tells me the OEM lock is now unlocked. Please confirm! (I may be a dumbass )
Click to expand...
Click to collapse
Do you see the open padlock on the boot logo screen?
bcmobile said:
Nice gift!
Do you see the open padlock on the boot logo screen?
Click to expand...
Click to collapse
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Chainfire said:
Just noticed... "adb reboot recovery" and "adb reboot download" now work. They didn't work on the KD9 ROM the device came with.
Click to expand...
Click to collapse
Yay! They do work if you do a adb reboot from the shell, but anyway, that's history now.
If you see the open padlock, you're in business. Im guessing that ROM was not meant for general public... in fact, if it came from where I think it came from, it wasn't
EDIT: So it has the stock recovery menu as well? Can you possibly do a system/boot/recovery dump to save us the pain of Odin?
EDIT2:
Chainfire said:
Yes. I don't think it used to on the old firmware. What is the verdict ?
EDIT: Misread. I do see a padlock, but it is locked !
Click to expand...
Click to collapse
fastboot oem unlock
I love Samsung... now
No Chinese at all, what a pity......
is it android 3.0.1 or android 3.1?
My device (bought in a vodafone ita store) has P7100BUKDF ROM and was already unlocked.
Myeah I was able to flash root after flashing this firmware, so it does unlock, it appears.
EDIT: Someone on twitter confirmed this unlocked the bootloader for him as well.
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
gjroeleveld said:
Thanks, good to have you on board ;-)
Maybe you should mention that this wipes the ENTIRE device, so including the SD-Card (The internal one)
Edit: Seems like I've lost root..
(Duh.. Title: Stock Rom..)
Edit 2: Reboot Recovery results in a Andy and an Exlamation mark
Rooted it with the fastboot method
Click to expand...
Click to collapse
If you press enough buttons the menu appears in recovery
Added the SD-CARD wipe notice for ya
How do root this firmware ?
Thanks
http://forum.xda-developers.com/showthread.php?t=1079781 ?
any one know the difference between this one and stock rom? would be interesting to see if samsung changed anything.
Has anyone tried flashing with Heimdall in Linux?
As for the question about the difference with the original ROM I can tell that as mentioned in the first post more languages are supported.
The rest seems about the same as the previous rom.
Yes, it's also the only change I noticed from the stock room, but in my case is great since now it supports Portuguese (my native language).
I just unlocked my bootloader following your steps. It shows unlocked when booting back up but now it is not recognized by my pc when connecting through usb. I tried rebooting both pc and tablet. I also tried uninstalling the drivers from Samsung and reinstalling it but still no go. I have a Galaxy Tab 10.1v from Google I/O and the usb is gone. I cannot even charge from usb now. Are the files posted the correct ones for this device because it is not working. Does anyone have the correct ones? Any help would be appreciated.
The Google I/O Tab as far as I know is not a 10.1v, thus you shouldn't be using these files on it!
Yeah I figured that out now. I was following the root guide and I thought I was supposed to use this. Everything seems to work but the usb. But I can still connect to Odin and reflash. Is there anyway to get it back?
Disclaimer: This procedure involves a higher risk than normal to brick your device. If you are not really familiar with flashtool please do not attempt to do this! I am not resposible for bricked devices, World War III or your exploding cats!
Also you acknowledge this points:
- This tutorial includes flashing the system partition of a firmware that is for a different device (Z3 Phone D6603)
- At some point your screen will not display anything
- This will not work on non-LTE versions of the Tablet (SGP611 and SGP612). Instructions for SGP611 can be found there.
- You also will loose all of you data, so please make a Backup.
If you are still sure you want to do this then here are the Steps:
1. Get the firmware ftf (SGP621_23.0.1.A.0.167_CE.ftf) for the SGP621 (for example from here or here)
2. Get a vulnerable firmware ftf (D6603_23.0.A.2.93_Generic_20GLOBAL.ftf) for the Xperia Z3 D6603 (for example from here or here)
3. Get the patched giefroot version for our device here
4. Open Flashtool and select flash. Then select flashmode and press OK
5. Select the 23.0.A.2.93 firmware and select to NOT wipe anything (see Picture 1). In the Exclude mark everything BUT system then start the flash process. If you do something wrong here you ran a VERY HIGH risk of bricking your device permanently
6. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
7. Start your device - you'll notice black bars on the left and right of the picture
8. It should boot up and display lots of errors, but still function
9. Go into Settings -> Backup and Reset -> Factory data reset and make a factory reset from there (It seems wiping in flashtool does not work for some people)
10. Do initial configuration and select enable adb debug and allow mock location in developer options
11. Select Security -> Unknown Sources (If you do not do this, giefroot will not work)
12. Open a shell/command prompt and try if adb shell works and brings you to your device <- This step is important because here you authorize the device for adb access that you need later, please select to authorize the connected computer permanently when asked to do so
13. Open Flashtool and select flash. Then select flashmode and press OK
14 Select the 23.0.A.2.93 firmware and select to NOT wipe anything (see Picture 2). In the Exclude mark everything BUT kernel then start the flash process. If you do something wrong here you ran a VERY HIGH risk of bricking your device permanently
15. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
16. Start your device and notice that the Screen stays pitch black, but you can hear the starting Sound
17. Once the tablet has started, go into the folder where you extracted giefroot and launch the install.bat
18. Wait till it is finished and tells you that you achived root (The device will reboot once while rooting, this is normal)
19. Open Flashtool and select flash. Then select flashmode and press OK
20. Select the SGP621_23.0.1.A.0.167_CE.ftf. Select to NOT wipe anything (see Picture 3). In the Exclude mark everything BUT kernel then start the flash process.
21. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
22. Congratulation. After rebooting you should have a rooted SGP621 with the system of a D6603.
23. Now backup your TA with the tool from here
24. Unlock the bootloader via the instructions from Sony here. Do this only if you have your TA partition backed up!
To install CyanogenMod 12 nightly:
25. Download a CM12 nightly build from here.
26. Unpack the boot.img from the downloaded zip file
27. Go into fastboot mode (press volume up and plug device into computer until led flashes blue).
28. Issue 'fastboot flash boot /path/to/boot.img'
29. Issue 'fastboot reboot'
30. Once the led gets purple press volume down to get into recovery
31. Select install -> install via adb
32. Issue 'adb sideload /path/to/downloaded-zip.zip'
33. Wipe data and cache
34. Reboot and enjoy CyanogenMod
To install rooted Stock:
25. Open Flashtool and select flash. Then select flashmode and press OK
26. Select the SGP621_23.0.1.A.0.167_CE.ftf. Leave everything as it is and start the flash process.
27. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
28. Get the advanced stock kernel from here, boot into fastboot mode, execute 'fastboot flash boot /path/to/the/Z3TC-stock-twrp.img'
29. Download RicDefeat from here.
30. Reboot the device and while booting once the led goes purple press the volume down key.
31. In the recovery tap on Advanced and Install with ADB and swipe to activate ADB
32. Issue 'adb sideload /path/to/RICDefeat.zip' (If sideloading does not work, put the zip file on your sd card and install it from there)
33. After that is finished, exit the recovery. It will ask you if you want to root. Answer yes and exit.
34. Open Flashtool again and select flash. Then select flashmode and press OK
35. Select the SGP621_23.0.1.A.0.167_CE.ftf. Select to NOT wipe anything (see Picture 3). In the Exclude mark everything BUT kernel then start the flash process.
36. Put your device in flash mode (hold volume down and plug the device in) -> Wait until flash is finished and restart your device
37. Restore your TA Backup and enjoy root on stock.
Congratulations, you now have a rooted device with either stock or CM12
Update Log
Update 1: I verified that Backup of TA works by reflashing it and checking if DRM is still intact in Service Menu.
Update 2: Changed instructions so wiping is done from the booted firmware directly, because for some users it was not possible to flash userdata from flashtool
Update 3: Added step 11 to enable Unknown Sources as otherwise giefroot will not work
Update 4: Added mirrors for the ftf files
Update 5: Added information to step 12 because it is important to authorize the device
Update 6: Added tutorial link
Update 7: Added tutorial for stock and CM12
Update 8: Update cause new giefroot is able to root our kernel
Thanks to zxz0O0 for giefroot and DevShaft for TA Backup
Good Luck and Have Fun
Your awesome man and thank you I'll give it a try
---------- Post added at 04:12 PM ---------- Previous post was at 03:52 PM ----------
hi boss I don't know if you could make a video on how to do it some of us are not that smart. so if you could please thanks
some screenshots for the "worst" steps too
jaime4272 said:
Your awesome man and thank you I'll give it a try
---------- Post added at 04:12 PM ---------- Previous post was at 03:52 PM ----------
hi boss I don't know if you could make a video on how to do it some of us are not that smart. so if you could please thanks
Click to expand...
Click to collapse
The instructions are very detailed, if you aren't that smart, as you put it, you should not do this process.
I don't know if I will have time to make a video, but I will do some screenshots in a few hours once I am back on my PC
rooting
i suggest taking out variables and automate the entire rooting process. i.e creating a .bat file or program.
why?
i dare say there will be noobs who will screw up the process and brick their tablets.then come crying in xda asking for solutions.
we are dealing with a fw frm another device(even though its in the same family) so there are bound to be risks involved.might as well preempt the possibility of dealing with a grief stricken noob and jus write a rooting progam....
need help with errors
lowtraxx can you tell me what's going on here. I've tried 4 times and I get this error. could you tell what am I doing wrong. I have been following you instructions but I cant get pass the first stage.
jaime4272 said:
lowtraxx can you tell me what's going on here. I've tried 4 times and I get this error. could you tell what am I doing wrong. I have been following you instructions but I cant get pass the first stage.
Click to expand...
Click to collapse
It seems system flashes okay, but the wipe of userdata fails. Could you please try to instead of wiping everything to wipe nothing and only flash system. After that reboot the tablet and you should get a normal bootup with lots of errors. Then go into Settings -> Backup and Reset and make a factory data reset. Then after that finished the tablet reboots and you should get no more errors. Then follow the rest of the steps.
Update: I also changed the tutorial to reflect that problem.
frostmore said:
i suggest taking out variables and automate the entire rooting process. i.e creating a .bat file or program.
why?
i dare say there will be noobs who will screw up the process and brick their tablets.then come crying in xda asking for solutions.
we are dealing with a fw frm another device(even though its in the same family) so there are bound to be risks involved.might as well preempt the possibility of dealing with a grief stricken noob and jus write a rooting progam....
Click to expand...
Click to collapse
I will try to do just that once I have the time. I just wanted to share the way as soon as I could so others that are experienced with flashtool (hence the big red disclaimer ) could try it out while I refine the proccess.
great i will try this!
Hope will succeed. by the way you have mirrors?
infinitylook said:
Hope will succeed. by the way you have mirrors?
Click to expand...
Click to collapse
Mirrors:
D6603_23.0.A.2.93_Generic_20GLOBAL.ftf
SGP621_23.0.1.A.0.167_CE.ftf
great lowtraxx! thank you very very very much it' s a really good workaround!
hi I have run into a little problem after rooting and trying to flash the spg621 rom back it looks like it doesn't and still on z3 and wifi and Bluetooth wont work any idea?
---------- Post added at 10:31 AM ---------- Previous post was at 09:55 AM ----------
when running on cmd giefroot when it says press any key to continue do I just let it be or do I press any key
Follow the giefroot instructions and press a key. For the Wifi and Bluetooth issues; If you flash a update zip you will need to do a factory reset, because otherwise your device could act funny, as configuration data from the D6603 is still there and needs to be erased.
hth
Working for me!
I've managed to get my device back onto rooted stock firmware with locked bootloader and the DRM keys intact. Created a guide for this here.
thank you. ill keep trying even thought i'm a hard time but ill get to it thanks
jaime4272 said:
thank you. ill keep trying even thought i'm a hard time but ill get to it thanks
Click to expand...
Click to collapse
Do not despair. It works, as proven by the people in this thread. You will work it out. For flashing to rooted stock use the tutorial from @CubicU07 in this post.
well I did manage to root even thought I took me some time. but thanks to you lowtraxx I was able to root and backup TA next I will follow his instructions for unloched BL then restore. thanks
Hello, did anybody got it work with the 32gb wifi modell? Thanks a lot
CubicU07 said:
Working for me!
I also managed to get back to rooted stock via the following steps after obtaining root:
1. Backup TA partition using Backup TA.
2. Return to stock unrooted by flashing the SGP621 rom using FlashTool without changing any of the options.
3. Unlock the bootloader (There are various ways to do this, including using FlashTool, just Google for it).
4. Flash the Advanced Stock Kernel by krabappel2548 using FlashTool in FastBoot mode.
5. Download the SuperSU.
6. Using PRFCreator on the SGP621 rom and the SuperSU zip, create a flashable stock rom zip.
7. Copy the resulting zip onto your device.
8. Boot into TWRP on your device and flash the zip.
9. Once complete, restore the TA partition using TA Backup
Note: Restoring TA partition without going back to stock kernel will soft brick your device, thus the need for steps 5 to 8 to return to stock kernel, while retaining root at the same time. This however, means that you lose custom recovery. So if you prefer having custom recovery over getting your DRM keys back into the device and restoring functionality like X-Reality, then skip steps 5 to 9 altogether..
Update: Unfortunately, after a bit of testing, I realized that the root I ended up with, following steps I listed, was not properly installed. I wasn't able to mount system in R/W mode in Root Explorer nor install BusyBox and it seemed like the only way I could make changes to files in the system was via ADB. Since I have no experience at all in Android programming, I'm striking out steps 5 - 9 until someone finds a solution to this. Sorry for anyone who tried this.
Click to expand...
Click to collapse
You need to disable Sony's RIC write protection by inserting the proper kernel module. Look here if the precompiled one works for you. With that you should be able to use the stock kernel (TA intact) WITH r/w to system.
Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet.I Dont Know if it Will Work on Other Firmware. I Tried On 6.0.1
"CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip" Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
Download And Install the Samsung USB Driver in your PC.
Extract the CF-Auto-Root files in your PC.
Switch off your Mobile.Enter into Download mode->Volume Down+Home+Power Buttons.
After entering into Download Mode it will say Warning Press Volume Up button to continue.
Connect Your Mobile With PC via USB Cable.
Launch Odin Application.It Will Show the message added.If you did not get this message Repeat the above steps.
After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file Select it.Tick the Auto reboot.
Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
Reboot again.
You can See the Superuser after the Reboot in your Applications list.
This will trip Knox correct?
Sent from my SM-G920T using Tapatalk
I am also curious will this trip Knox?.. I'm assuming anything involving odin is an automatic yes?.
Yes All Rooting trips knox
Do you need to turn on OEM unlocking?
It failed for me did all the steps.
Copied and pasted the OP and adding my own notes:
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
ktrinh4213 said:
Copied and pasted the OP and adding my own notes:
1) Update Your Samsung Galaxy S6 SM-G920T T Mobile to Marshmallow If You Didn't Done Yet -- CF-Auto Root works on all versions of Android thus far. "CF-Auto-Root-zerofltetmo-zerofltetmo-smg920t.zip"
2) Download CF-Auto-Root Samsung Galaxy S6 SM-G920T T Mobile 6.0.1 Marshmallow.Just Search it in Google And download From Chainfire
3) Download And Install the Samsung USB Driver in your PC.
4) Extract the CF-Auto-Root files in your PC.
5) Go to Settings->About Device->Tap Build Number until Developer Options is unlocked.
6) Go back to Settings-> Developer Options-> Toggle OEM Unlock. This will prevent your device from being soft-bricked (and save you time downloading and reinstalling the OEM ROM).
7) Switch off your Mobile. Enter into Download mode->Volume Down+Home+Power Buttons.
8) After entering into Download Mode it will say Warning Press Volume Up button to continue.
9) Connect Your Mobile With PC via USB Cable.
10) Launch Odin Application.It Will Show the message "ADDED!!!". If you did not get this message Repeat the above steps.
11) After Getting Added Message Select PDA Button then Browse for the CF-Auto-Root file. If using Odin 10.x, look for the AP button, and search for the CF-Auto Root file. Select it. Where the messages populate, go to the Options tab. Tick the Auto reboot. THIS WILL TRIP KNOX.
12) Press Start wait for the tasks to complete.It may enter into Recovery mode to add the SuperSu permissions.
13) Reboot again.
You can See the Superuser after the Reboot in your Applications list.
Click to expand...
Click to collapse
Been searching all day and found this and am curious if it works on the EPF1 build of the s6. I keep hearing that my bootloader is locked and it will brick my device so just wanted some confirmation that someone has done this with the same phone and build that i have and that it works without messing anything up. thanks in advance
kenpachi100 said:
Been searching all day and found this and am curious if it works on the EPF1 build of the s6. I keep hearing that my bootloader is locked and it will brick my device so just wanted some confirmation that someone has done this with the same phone and build that i have and that it works without messing anything up. thanks in advance
Click to expand...
Click to collapse
It works, because I was on stock before I rooted. You have to unlock your OEM bootloader using steps 5 and 6 that I mentioned, or you will soft-brick your phone.
ktrinh4213 said:
It works, because I was on stock before I rooted. You have to unlock your OEM bootloader using steps 5 and 6 that I mentioned, or you will soft-brick your phone.
Click to expand...
Click to collapse
So youve done this on your phone?
I have already toggled the oem unlock option but i was told by samsung support that it doesnt unlock the bootloader.
Sorry not trying to be annoying i just really dont wanna mess my phone up. Just to be certain my s6 is stock ota 6.0.1 from tmobile with the EPF1 build.
kenpachi100 said:
So youve done this on your phone?
I have already toggled the oem unlock option but i was told by samsung support that it doesnt unlock the bootloader.
Sorry not trying to be annoying i just really dont wanna mess my phone up. Just to be certain my s6 is stock ota 6.0.1 from tmobile with the EPF1 build.
Click to expand...
Click to collapse
I know for sure it works because I did it the wrong way, and found out the right way. When you Unlock OEM, it unlocks your FRP (Factory Reset Protection). Without that being unlocked, you will be in a bootloop with the Samsung splash screen with the words FRP Locked (or something similar) at the top left hand corner until you flash the stock ROM from Sammobile via Odin.
Without following the steps I prescribed, you will soft-brick your phone, and ultimately, you will lose all data and information saved on your phone anyway. Unlocking it will remove the FRP lock so that when you reboot after rooting with CF-Auto-Root, you can log into your phone as usual (fingerprint, password, PIN, etc.) rather than being met with that Samsung splash screen.
ktrinh4213 said:
I know for sure it works because I did it the wrong way, and found out the right way. When you Unlock OEM, it unlocks your FRP (Factory Reset Protection). Without that being unlocked, you will be in a bootloop with the Samsung splash screen with the words FRP Locked (or something similar) at the top left hand corner until you flash the stock ROM from Sammobile via Odin.
Without following the steps I prescribed, you will soft-brick your phone, and ultimately, you will lose all data and information saved on your phone anyway. Unlocking it will remove the FRP lock so that when you reboot after rooting with CF-Auto-Root, you can log into your phone as usual (fingerprint, password, PIN, etc.) rather than being met with that Samsung splash screen.
Click to expand...
Click to collapse
So you were on 6.0.1 stock ota when you did it?
Also will doing it this way wipe my data or just install root?
Also also would i just flash twrp via odin after doing this or..?
kenpachi100 said:
So you were on 6.0.1 stock ota when you did it?
Also will doing it this way wipe my data or just install root?
Also also would i just flash twrp via odin after doing this or..?
Click to expand...
Click to collapse
Yes
No, it just installs root.
This does not automatically flash TWRP for you, it's something you have to do yourself.
ktrinh4213 said:
Yes
No, it just installs root.
This does not automatically flash TWRP for you, it's something you have to do yourself.
Click to expand...
Click to collapse
I know it doesnt automatically flash TWRP i was asking how i would flash twrp afterwards. I guess it would have to be odin since you cant flash it from the phone without a custom recovery. Also, again just trying to clarify, your build number had EPF1 when you did this also?
kenpachi100 said:
I know it doesnt automatically flash TWRP i was asking how i would flash twrp afterwards. I guess it would have to be odin since you cant flash it from the phone without a custom recovery. Also, again just trying to clarify, your build number had EPF1 when you did this also?
Click to expand...
Click to collapse
Go to the TWRP website and find the latest build number, or download the TWRP Manager app on the Play Store and you can download and flash it from there.
Yes, my ROM was STOCK OTA.
ktrinh4213 said:
Go to the TWRP website and find the latest build number, or download the TWRP Manager app on the Play Store and you can download and flash it from there.
Yes, my ROM was STOCK OTA.
Click to expand...
Click to collapse
Okay, thanks for answering all my questions and the help!
works like a charm. thanks for sharing!
Will this work for this Build Number which is MMB29K.G920TUVU4EPF1?
php111 said:
Will this work for this Build Number which is MMB29K.G920TUVU4EPF1?
Click to expand...
Click to collapse
Yes it will.
I took the 6.0.1 OTA Update. So is this what I need to do?
First, download 6.0.1 from like the site Sammobile and Flash via ODIN and should I check or uncheck Auto reboot?
Than once I flashed than follow all 13 steps given in post #7 of this thread
Once I followed the 13 steps than flash TWRP? Should I flash via ODIN or recovery? If in ODIN should check or unchecked Auto reboot?
Once I got TWRP than install Super SUPER SU from Play Store
Credits go to: @ashyx, @mauam, @jedld, @Chainfire
Prerequisite:
Padded kernel for T280
http://forum.xda-developers.com/attachment.php?attachmentid=3881481&d=1474417563 (unpack with 7zip and put it to memory card)
SYSTEMMODE SuperSU (REQUIRED)
http://forum.xda-developers.com/attachment.php?attachmentid=3861602&d=1472738213 (put it to memory card)
All required drivers from Samsung Smart Switch
Odin 3.10
TWRP
https://www.androidfilehost.com/?fid=312968872162492913
Your unit should be fully charged
OEM unlock and USB Debugging enabled and allow your host computer
Steps:
1. Connect your tablet with your host computer
2. Open prompt and locate to your adb folder (platform-tools) and enter
Code:
adb reboot download
If it doesn't work, look at your tablet to see any prompt to allow your host computer
3. Open your Odin. Make sure auto reboot is not checked (but TWRP isn't overridden). Choose AP and locate your TWRP file. You may see secure check failed. Don't worry. Just press and hold power+volume down+home key together and wait for few seconds.
4. Enter TWRP by pressing power+volume up+home key together. You should see the boot screen. Keep pressing these buttons until the boot screen disappears. You should enter TWRP.
5. Locate your memory card. Flash systemmode SuperSU first, go back, and flash padded image as "boot".
6. (Optional) wipe cache and dalvik cache.
7. Reboot
8. It may take a while to boot up
9. You tablet rooted.
Hey, this works! Thank you for writing it up!
Success on a Samsung A6 SM-T280 (version 5.1.1 if memory serves).
Instructions weren't clear enough, got **** stuck in toaster...
Nah jk, it worked man!
EDIT: This is a lot harder than I thought it would be.... I lost root and did a reset and did it all again. This time after I got it rooted, I got rid of the SuperSU and downloaded the one from market. It updated binary easily.
sovereignjerk said:
Instructions weren't clear enough, got **** stuck in toaster...
Nah jk, it worked man!
EDIT: This is a lot harder than I thought it would be.... I lost root and did a reset and did it all again. This time after I got it rooted, I got rid of the SuperSU and downloaded the one from market. It updated binary easily.
Click to expand...
Click to collapse
I keep getting Custom Binary (Recovery) blocked from FRP lock. Did you get this as well?
mdsohal02 said:
I keep getting Custom Binary (Recovery) blocked from FRP lock. Did you get this as well?
Click to expand...
Click to collapse
Make sure you OEM unlock under the developer settings.
jedld said:
Make sure you OEM unlock under the developer settings.
Click to expand...
Click to collapse
Thank you Sorry, I haven't rooted an android device since the EVO 4G. Things have changed in the meantime.
---------- Post added at 02:48 AM ---------- Previous post was at 02:11 AM ----------
Does anyone know how to disable the OTA update notification once I am rooted ?
Does really count as a root? I thought needed bootloader...
sovereignjerk said:
Does really count as a root? I thought needed bootloader...
Click to expand...
Click to collapse
Yes, it's root.
The key is the recovery has SHA key embedded to bypass the bootloader.
mingkee said:
Yes, it's root.
The key is the recovery has SHA key embedded to bypass the bootloader.
Click to expand...
Click to collapse
Hi guys, has anyone tried APP2SD after rooting.?
After Step 3 it takes me to a warning screen with two options 1. Vol up to continue 2. Vol down to restart device.
So I go with option 1 but instead of taking me to TWRP it takes me back to download mode and at the top left corner this is what is shown.
ODIN MODE (In Red)
SECURE DOWNLOAD: ENABLE (In Blue)
MDM DOWNLOADBLOCK: O (In Red)
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: OFF
USB Init Start!
USB core reset done
I made sure to uncheck auto reboot but couldn't find anything about TWRP not being overridden so maybe that's the problem, what am I doing wrong?
Can someone do a video tutorial about this root?
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Wingchundub said:
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Click to expand...
Click to collapse
i advise you to search youtube on how to use adb. This is how i learned. Its too complicated to write it. But when you see video its easy. In simplest way adb is cmd opened in adb file. Than in cmd you write commands like adb flash, or adb format and stuff
Wingchundub said:
Sorry for the dumbness, but i have never used this adb, this is only confusing part.
I laptop running windows 10, all drivers, files on sd card as you state.
Any further guidance i would appreciate.
Best wishes
Click to expand...
Click to collapse
You don't need adb. Just boot to download mode normally.
ashyx said:
You don't need adb. Just boot to download mode normally.
Click to expand...
Click to collapse
Ashyx
Will link2sd/app2sd after root.?
ahmedyar91 said:
Ashyx
Will link2sd/app2sd after root.?
Click to expand...
Click to collapse
I don't see why not.
Will try and post
Finally rooted.
I came across this post and worked first time.
I installed supersu via trwp, then flashed img as boot in trwp also.
Worked perfectly
http://forum.xda-developers.com/gal...covery-samsung-galaxy-tab-a6-sm-t280-t3475381
ecstaseey said:
After Step 3 it takes me to a warning screen with two options 1. Vol up to continue 2. Vol down to restart device.
So I go with option 1 but instead of taking me to TWRP it takes me back to download mode and at the top left corner this is what is shown.
ODIN MODE (In Red)
SECURE DOWNLOAD: ENABLE (In Blue)
MDM DOWNLOADBLOCK: O (In Red)
PRODUCT NAME: SM-T280
CURRENT BIN: CUSTOM
SYSTEM STATUS: CUSTOM
FRP LOCK: OFF
USB Init Start!
USB core reset done
I made sure to uncheck auto reboot but couldn't find anything about TWRP not being overridden so maybe that's the problem, what am I doing wrong?
Click to expand...
Click to collapse
Here's a more detailed guide. It's based on this thread: http://www.droidviews.com/root-samsung-galaxy-tab-a-sm-t280-and-install-twrp/
raakaysh said:
Here's a more detailed guide. It's based on this thread: http://www.droidviews.com/root-samsung-galaxy-tab-a-sm-t280-and-install-twrp/
Click to expand...
Click to collapse
That is the old method and no longer relevant.
Just follow the steps in the OP below.
http://forum.xda-developers.com/showthread.php?t=3475381
The purpose of this thread is to have one post with links to all of the following guides:
Unlock Bootloader by @mingkee
TWRP Recovery by @Magendanz
Custom ROM Nexus Stock by @Magendanz - current release is SM-T510 only
Custom ROM LineageOS 16.0 by @Magendanz - SM-T510 only
All credit to @Magendanz and @mingkee for those.
Below are my own observations which supplement but do not replace the guides above. The original posts includes important information not quoted below. You need to read the relevant guides above (depending on what you want to do), and you may get some additional benefit from reading my thoughts below before following the guides above.
***Contents
Overview
Downloads
Buttons
Unlock Bootloader
Rooting
How to use Odin
***OverviewTo root your device you need to first install the TWRP recovery. @Magendanz includes TWRP in his ROMs, so you have two options, TWRP without custom ROM, or TWRP with custom ROM.
To be able to install a ROM or recovery you first need to unlock your bootloader.
WARNING - take note of the kernel version of the custom ROM or TWRP you intend to use, e.g. T510XXU2ASI4. Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware/ROM/TWRP with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.
There are then two paths:
Original ROM:
Read the TWRP instructions
Download any zip you plan to flash (install) from TWRP (e.g. Multi-disable and Magisk) and save to your sdcard. Internal memory will be wiped (formatted) as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
Unlock Bootloader - Click to see original post:
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.
Install TWRP recovery .tar.md5 file via Odin by following the TWRP instructions.
Click to see instructions from the TWRP OP -
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip) file, and then swipe to install
Reboot to system
[Optional] Install Magisk to get root - see Rooting section below
Don't forget to install Multi-disabler before doing Format Data! (as described in the guide) - In TWRP tap Install then select the Multi-disabler zip file.
Custom ROM [Allow several hours for the custom ROM download]:
Read the custom ROM instructions: Nexus Stock / LineageOS 16.0
Download any zip you plan to flash (install) from TWRP (e.g. Magisk) and save to your sdcard. Internal memory will be wiped as a necessary step in installing TWRP (if you follow the instructions correctly). Note that the folder /sdcard is part of the devices internal memory, your actual sdcard data can be found in something like /storage/ABCD-1234 in Android, or external_sd in TWRP.
Unlock Bootloader - Click to see original post:
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.
Install custom ROM .tar.md5 file (which includes TWRP) via Odin, by following the custom ROM instructions.
Click for instructions from OP for Nexus Stock -
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
Click for instructions from OP for LineageOS 16.0 -
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM to AP with Odin
When TWRP launches, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
Note that "wipe data" means Wipe -> Format Data
[Optional] Install Magisk to get root - see Rooting section below
Dirty flash: If you had installed the custom ROM previously and are now updating to a newer version then all you need to do is use Odin to flash the latest tar.md5 file. It will enter TWRP after the flash, no need to Format Data, just reboot to system. Alternatively if the ROM developer provides a flashable zip, you can update with TWRP.
Some users have reported getting stuck on the boot animation after a dirty flash, I don't know if that still happens with the latest versions of @Magendanz's ROMs. If it does the solution is to boot into recovery and flash Multi-disabler.
For TWRP versions before v3.3.1-5 you MUST format the encrypted data partition after flashing TWRP or TWRP will hang on the splash screen. For later versions of TWRP you should format the encrypted data partition after flashing TWRP so that TWRP can access the data partition.
You can use TWRP to flash zip files, e.g. to install newer versions of TWRP itself, or custom ROM zips, as follows:
1. Download the zip file
2. Boot into Recovery
3. Install -> Select the TWRP zip file
4. Reboot to System
You *cannot* use TWRP to flash tar.md5 files, and you must use Odin at least once to get TWRP installed in the first place.
***DownloadsYou may not need ALL of these downloads, this is just a handy list of some of the downloads mentioned in the guides
Samsung Smart Switch (for USB drivers)
Magisk - Download Latest Stable zip file to flash in TWRP (see Rooting below) and Latest Magisk Manager to install as an app
Odin
Multi-disabler (required by TWRP only tar.md5)
Firmwares SM-T510 SM-T515 - allow several hours, at least, for the firmware downloads to complete
WARNING - take note of the kernel version of the custom ROM you intend to use, e.g. T510XXU2ASI4 and your current version (Settings | About tablet). Newer bootloader releases will sometimes prevent downgrading, so if you flash a firmware with a later kernel version you may not be able to flash your desired custom ROM without problems, or flashing an older version than you are currently running may trigger anti-rollback mechanisms. Magendanz suggests matching the version exactly.
***Buttons
Power On: Hold the Power button for 3 seconds
Boot to Recovery (Before unlocking bootloader) Power On and Press and hold Power and Volume Up until you see Recovery running.
Boot to Recovery (After unlocking bootloader) Power On and then press Power and Volume Up as soon as you see the unlocked bootloader warning. No need to hold.
Boot to Download: Press and hold Volume Up and Volume Down and connect to computer with USB cable.
***Unlock BootloaderRead the Unlock Bootloader Guide FIRSTClick to see Unlock Bootloader original post...
Disclaimer: your tablet warranty will void. Proceed with your own risk
Warning: your personal data, except on external SD card or USB drive, will be wiped during the process!
Prerequisite:
Host PC installed Samsung Smart Switch
USB C cable
Your tablet battery should be 70% or higher and you have done data backup
OEM Unlock enabled
1. About tablet
2. Software version
3. Hit Build Number few times
4. Enable USB Debugging
5. Allow your host computer
6. If you don't see OEM Unlocking, wait for 7 days or do the following trick
https://www.xda-developers.com/fix-m...galaxy-note-8/
Are you ready? Let's do it.
1. Turn your tablet off and disconnect USB cable
2. Press and hold both volume up and down buttons and connect to host computer
3. You should see factory reset screen, but this time you should see one more option. Press and hold volume up to unlock the bootloader.
4. If you see a warning screen on boot, the bootloader is unlocked.
After unlocking the bootloader every time you turn the device on a warning about the bootloader being unlocked will appear for ten seconds, unless you dismiss it by pressing the power button.
If you are holding the Power button and Volume Up to boot into recovery this warning screen will flash on and off briefly, at which point you can stop holding down the buttons. Recovery will start a few seconds later.
***RootingRoot can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). From Magisk 19.3 onwards there is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.
You can even install Magisk the first time TWRP runs after flashing one of @Magendanz's tar.md5 files in Odin.
To do so follow @Magendanz's guide up to the point where you have Factory Reset/Wiped Data in TWRP then:
1. Reboot to Recovery
2. Install -> Select the Magisk zip file
3. Reboot to System
4. Install Magisk Manager
Otherwise you can start by installing the Magisk Manager app at any time.
Note: You will need to re-install Magisk after a TWRP update.
***How to use OdinOdin is a Windows tool for firmware flashing on Samsung devices via USB. Odin can be used to flash firmware, kernels, recoveries or ROMs to your device.
* Firmware zip (or rar) files need to be extracted and then install via Odin. Flashable zip files (e.g. new versions of TWRP or custom ROMs) can only be flashed from TWRP, not Odin, though you need to flash a TWRP tar.md5 file using Odin in the first place *
Preparing the device
Charge the device to at least 80%.
Bootloader unlocked
In developer options, turn USB debugging on. Click on Build number in Settings several times until you see the toast notification "You are now a developer". Go to Developer Options and turn on the USB debugging option.
- In the stock ROM Build number can be found here: Settings | About Tablet | Software Information and the "Developer Options" menu item appears below About Tablet in the main Settings screen.
- The locations may be different in custom ROMs. In the Nexus based ROM the locations are Settings | About phone for Build number, and System | Advanced for Developer options
Turn off the phone, hold down the Volumn Up and Volume Down buttons and connect the device to the computer with a USB cable (preferably the cable that came with the device). A warning will appear saying "A custom OS can cause critical problems in phone and installed applications".
Press the Volume Up button briefly to continue.
The device is now in Download mode.
Install Odin version 3.13.3.
When you run it a dialog will pop up in English and Chinese. Click OK.
The Odin window looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Above ID:COM on the left is the progress bar, below ID:COM is the connection indicator which changes colour (and shows the COM id) when your device is connected in Download mode.
Below that is the "Log" tab which gives verbose output showing what's happening. Normally you will not need to go near the Option or Pit tabs.
There are four buttons in the middle of the screen corresponding to the types of file that you can flash: BL (boot loader), AP (Application Processor, PDA), CP (Core Processor, phone/modem), CSC (Consumer Software Customization)
Depending on what you are flashing you will need to load one or more files. To load each file type click on the corresponding button and select the file to be flashed.
Odin will show the following in the "Log" while the file is being processed:
Code:
<OSM> Enter CS for MD5
<OSM> Check MD5... Do not unplug the cable...
<OSM> Please wait...
For AP_ files this can take some time, during which the button will remain greyed out. When the file has loaded the "Log" will say:
Code:
<OSM> Checking MD5 finished Successfully...
<OSM> Leaving CS...
... the button will be enabled again, the text field beside the button will be filled with the fullpath of the selected file, and the checkbox next to the button ticked.
@Magendanz's TWRP and ROM files are both single files flashed to AP, so just click the AP button and the select the tar.md5 file.
If you are flashing firmware ( e.g. https://samfrew.com/model/SM-T510/ ) unzip the download into separate files and load each with the correspong button. The filenames begin with BL_..., AL_... etc so you'll know which is which.
There will be both a CSC_ and HOME_CSC_ file. You could flash HOME_CSC_ to keep your device's settings and data but normally you should use CSC_ for a clean install. If you have an SM-T515 then you'll have a CP_ file too, but if you have a SM-T510 then your firmware will not have a CP_ file because that's for the phone (SM-T510 is wifi only), so just leave CP alone, only load BL, AP and CSC.
Verify that your device is connected in download mode. The box below ID:COM should show the COM id of the connected device and there should be a line in the "log" saying something like <ID:0/008> Added!!
Click Start to flash the selected files. DO NOT UNPLUG THE CABLE UNTIL THE PROCESS IS COMPLETE. You can follow the progress in Odin and on the Download screen on your device. To flash a ROM or firmware will take several minutes.
If you are flashing one of @Magendanz's tar.md5 files then your device will reboot into TWRP once the install is complete. At that point continue following @Magendanz's guide.
Note: You will need to turn on USB debugging again after flashing firmware, or a clean install of a ROM, before you can use Odin to flash again. Also check that OEM unlock is still turned on.
Hi,
Please help, my tablet SM-T515 got stuck at: teamwin Recovery Project 3.3.1-1 ...blue with black/gray screen, at boot. I can't do anything, it keeps on looping to this screen. If I try to do a Power+VolumeDown it resets the tablet but I can't do anything else, nor entering in Download mode or shut it down. I have no idea how to fix it. Can anyone give me some hints, please ?! PS: I wanted to root it...I might have downloaded on the tablet with ODIN some weird TWRP (I didn't found this post before starting the process from some weird site ... ).
Please, help me,
D
@DdDnt The difficulty in rebooting into Download mode is timing. After triggering a reboot by holding Power+VolumeDown for 7 seconds you need to immediately switch to holding Vol Up + Vol Down then connect the cable.
Alternatively you can wait for the battery to run out, then you can press and hold volume buttons and connect. Should get you into Download mode.
The next steps are
Flash stock firmware via Odin
Reboot into system and turn on USB debugging again in Developer options, verify that OEM unlock is still set
Flash TWRP or Custom ROM via Odin
MossyTC said:
@DdDnt The difficulty in rebooting into Download mode is timing. After triggering a reboot by holding Power+VolumeDown for 7 seconds you need to immediately switch to holding Vol Up + Vol Down then connect the cable.
Alternatively you can wait for the battery to run out, then you can press and hold volume buttons and connect. Should get you into Download mode.
The next steps are
Flash stock firmware via Odin
Reboot into system and turn on USB debugging again in Developer options, verify that OEM unlock is still set
Flash TWRP or Custom ROM via Odin
Click to expand...
Click to collapse
Hey, first of all thanks for the nice guide. I followed it to flash Nexus ROM for my T515 but I messed up the tablet and ended up in the emergency recovery mode. No biggie though, I have flashed back to original stock ROM but I can't seem to find OEM unlock option now in my developer settings (the tablet is still unlocked though, I have to use my power key while turning on to skip the warning screen)
So basically, now I can't figure out why I can't flash the nexus rom but was able to flash official firmware and why I don't have OEM unlock option in my developer settings.
Also, I made a clean install of Windows 10, downloaded the good drivers and used my best type C cord and plugged it directly into the motherboard and not into the front I/O panel, and still no luck with the nexus ROM.
P.S. I'm tagging @Magendanz, just in case you find it interesting how odin refuses to flash your Nexus rom. If you want to, I could test the nexus rom on the latest T515 firmware, perhaps the fw refuses to go below the current version I'm on?
P.P.S : added Odin output
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1303)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 3048 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> param.bin
<ID:0/003> product.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Download mode screen spits out Only official released binaries are allowed to be flashed so I guess it is a matter of bootloader unlocking after all?
[deleted]
@fpozar There are two problems that I know of that can cause a FAIL on the product.img line in Odin -
USB debugging not turned on
Incomplete boot loader unlock
Looks like option 2.
As Magendanz has said elsewhere -
Did you reboot with the USB cable inserted holding Vol Up & Vol Down to get the light blue Warning screen and then long press Vol Up to finish unlocking bootloader? A short press, rebooting to bootloader from stock recovery, or adb reboot bootloader in debugging mode won't cut it.
Click to expand...
Click to collapse
Update: More from Magendanz, on missing OEM unlock option:
This is what the VaultKeeper "feature" does. You've got to open Developer Options with internet connectivity for it not to automatically undo your efforts to unlock.
Click to expand...
Click to collapse
So connect to wifi before doing the Developer options thing, then try the bootloader thing.
MossyTC said:
@fpozar There are two problems that I know of that can cause a FAIL on the product.img line in Odin -
USB debugging not turned on
Incomplete boot loader unlock
Looks like option 2.
As Magendanz has said elsewhere -
Update: More from Magendanz, on missing OEM unlock option:
So connect to wifi before doing the Developer options thing, then try the bootloader thing.
Click to expand...
Click to collapse
Yes, I have done the light blue screen long press step.
Now I've held vol buttons while starting the tablet and chose the short click step (the long click step only leads me to locking bootloader again) and entered a bit different looking download mode (the same one you get by using recovery to enter bootloader, but with a bit more colorful text on the sides), but to no avail, the flashing didn't go through and only lead me to emergency recovery. And again, flashing stock worked.
Secondly, OEM trick worked for me, it appeared when I connected to my home network and made it that oem unlock was greyed out and said "oem unlocked".
Tommorrow I'll try to lock the bootloader and unlock it again. It's really weird though because the blue screen part was done correctly it seems (because long pressing leads me to locking).
Bootloader screenshot when entered by volume + and - combination
I'm a bit confused on what I've been doing wrong and where to proceed from here. These are the steps I've done on my most recent try:
1) Downloaded:
- Samsung Smart Switch
- TWRP 3.3.1.5 .tar.md5
- Magisk (Latest Magisk Manager)
- Odin
- Firmware T510 (XAR-T510XXU1ASEF-20190605151710.zip)
- Multi-disabler
2) Followed Unlock Bootloader from mingkee
3) Installed TWRP recovery via Odin
4) Rebooted back into stock ROM
5) Installed Magisk.apk
6) Using Magisk Manager > Selected AP_T510XXU1ASEF_CL15874928_QB23938566_REV02_user_low_ship_meta_OS9.tar.md5
7) That gave me magisk_patched.tar which I moved over to my desktop
8) Boot back into download mode
9) Flash the magisk_patched under AP, TWRP under BL, and HOME_CSC under CSC
10) Then Odin said it failed
Honestly I was pretty confused by the steps going from guide to guide so I'm not sure where I went wrong.
Also I'm not sure where I'm suppose to be flashing multi-disabler. The guide just said don't forget to install it but I'm not sure at which step I should be installing it via TWRP.
Any help would be appreciated.
Edit:
I tried again going with just steps from [GUIDE]Comprehensive T510 root guide.
I unlocked bootloader > patched the AP file I downloaded > Tried flashing the AP file only using Odin and it gave me an error:
"Only official released binaries are allowed to be flashed"
@Orite I'm sorry that I haven't been clearer, but I did say to read the relevant guides and read my thoughts below.
In the OP I said
Root can be achieved by flashing Magisk in TWRP (you also need to install the Magisk Manager app). There is no longer a need to use Magisk Manager to patch a tar.md5 file or anything like that.
Click to expand...
Click to collapse
Full details in the Rooting section in the OP.
You should have been following the TWRP Recovery guide for installing TWRP which clearly states at what point to install Multi-disabler.
If you can boot into TWRP you can flash the Multi-disabler zip file. Tap Install then select the zip file. That should fix the problem of not being able to flash via Odin, though you don't need Odin to install Magisk.
Update : So today I've reunlocked bootloader again and still got stuck at product.img step. Again, this is all on fresh windows and Odin works on original firmware.
This time, the error message displayed on my tablet is :
SYSTEM REV. CHECK FAIL. DEVICE:2 BINARY:1 (PRODUCT)
I can only assume this is some anti rollback feature similar to what happens on LG devices when you try to flash software older than what you're currently at.
I guess now we wait for dev's confirmation and if anyone else has something smart to say please feel free to join the discussion. I would try and download older official firmware and try to flash nexus while on something older, but my network connection is kinda unstable and it takes hours to download without a paid account.
Just to avoid questions, my method of unlocking followed exactly the link in the OP and method of flashing was following the mini guide on Nexus rom's OP.
EDIT : For all the T515 users, it seems odin isn't allowed (by some security features) to downgrade bootloader, and since Nexus ROM is based on May update for T515, anyone on updates newer than May can't flash the ROM. I found the answer on Galaxy s9 forums so that might be untrue for our device, but I didn't see many of us T515 users talking about custom roms so that might be it, and the error code makes sense.
Thanks again @MossyTC for trying to help
@fpozar
Magendanz doesn't explicitly say so in his OPs, but in some of his posts he does suggest matching the kernel versions.
magendanz said:
Well, TWRP is going to use a custom kernel based on the latest kernel source release, which as of yesterday is T510XXU2ASI4. The custom recovery uses this, but it will also substitute a new boot partition with the custom kernel so that Knox boot security features are disabled and you can still boot to system. I'd think the goal would be to match them as closely as possible. That said, often newer bootloader releases will prevent downgrading, so it's not entirely without risk to use the newest release. The safest bet is to always match the version exactly.
Click to expand...
Click to collapse
Anyway it looks like you're stuck with stock until there's a newer t515 custom ROM.
Thank you. I was finally able to figure it out with your response.
Hi, I have seem to messed up my process somehow, this tutorial seems kind of out of place.
When i try moving the multidisabler to my phone, it looks like all my folders and files are encrypted inside twrp and from the mounted drive on my pc.
I tried installing multidisabler using an OTG which worked on twrps side, i then rebooted and launched into OEM. after restarting from OEM android, i now receive a message when trying to do anything involving turning on my tablet "Only Official Release Binary Aloud" I cant do anything with it now. It just Shows that msg and the samsung logo, and then goes away, never booting, never entering recovery.
I tried to google this and it came up with something about knox, which i know nothing about. I really hope i didn't just brick my device.
Does unlocking Bootloader on the T510 change Widevine from L1 to L3? This is my only hestitation to bootloader unlock and root
trashbag1 said:
this tutorial seems kind of out of place.
Click to expand...
Click to collapse
This isn't really a tutorial, more like additional information to help you follow the guides linked in the OP.
When i try moving the multidisabler to my phone, it looks like all my folders and files are encrypted inside twrp and from the mounted drive on my pc.
Click to expand...
Click to collapse
You're internal data is encrypted by default by Android, but the version of TWRP we're using can't handle encryption. We get around that by disabling encryption by wiping the data partition as one of the first things we do when TWRP starts up, as per the instructions in Magendanz's threads. Ideally you should have the Multi-disabler zip on your sdcard before flashing TWRP. I have amended the instructions above to suggest as much.
I tried installing multidisabler using an OTG which worked on twrps side, i then rebooted and launched into OEM. after restarting from OEM android, i now receive a message when trying to do anything involving turning on my tablet "Only Official Release Binary Aloud" I cant do anything with it now. It just Shows that msg and the samsung logo, and then goes away, never booting, never entering recovery.
I tried to google this and it came up with something about knox, which i know nothing about. I really hope i didn't just brick my device.
Click to expand...
Click to collapse
Is your device an SM-T515? You may be having the same problem as @fpozar.
Can you get into Download mode again?
tomdot said:
Does unlocking Bootloader on the T510 change Widevine from L1 to L3? This is my only hestitation to bootloader unlock and root
Click to expand...
Click to collapse
I don't know what will affect Widevine.
I think the bootloader can be relocked, but I can't check right now.
The bootloader *can* be locked, I know as I've done it yesterday. In fact, it can be relocked and renlocked as many times as you want. To lock it follow the guide to unlocking but when you enter the light blue menu, holding vol up will lead you to locking and reseting your tab
another guide? lol pretty soon will b only guide threads in here lol
fpozar said:
The bootloader *can* be locked, I know as I've done it yesterday. In fact, it can be relocked and renlocked as many times as you want. To lock it follow the guide to unlocking but when you enter the light blue menu, holding vol up will lead you to locking and reseting your tab
Click to expand...
Click to collapse
"And resetting". That's the problem. You can't relock without resetting and having to start over from scratch.
elliwigy said:
another guide? lol pretty soon will b only guide threads in here lol
Click to expand...
Click to collapse
Yeah, well there are about twelve Galaxy Series A models and the geniuses at xda put them all in one bucket, so lots of Guides in the Guides, News & Discussion section, lots of ROMs in ROMs, Kernels & Recoveries, etc.