Related
Hi
I am not sure if there is someone who can help me but here is my problem. I have tried to upgrade my Galaxy S to froyo via Odin without the 3 buttons combo available(Now I know this is stupid:| ). I've used adb to enter the download mode and while Odin tried to install the upgrade I got a green freeze screen on my phone and Odin has freeze too. After rebooting the phone it always stuck in the recovery mode and displays the following error:
E:/Can't mount/dev/block/stl11
Right now I can only connect to my phone trough adb console and Odin but only in recovery mode. When I run the "adb reboot download" command the phone only reboot in recovery mode, not in download mode.
Is there something I can do to bring my phone in download mode?
Any help on this issue will be much appreciated
Thanks!
Hi guys, the thing is that i have a Galaxy S I9000b, with a broken power button, and a bad CWM ROM. I installed CWM recovery through fastboot mode, but i can't access it. Also i have tried removing "--no-reboot" from de command in heimdall, it reboots, but it stucks on the first boot screen (device model and brand). Also i can't boot the device, so i can't install any app to reboot in recovery mode. There is a way to boot recovery mode with a battery trick or through fastboot? Or even flash CWM ROM through fastboot? There is a way so that after installing the kernel it reboots automatically into recovery? Thanks beforehand, hope you can help me. (Sorry for my bad english, i'm from Chile )
xavipr69 said:
Hi guys, the thing is that i have a Galaxy S I9000b, with a broken power button, and a bad CWM ROM. I installed CWM recovery through fastboot mode, but i can't access it. Also i have tried removing "--no-reboot" from de command in heimdall, it reboots, but it stucks on the first boot screen (device model and brand). Also i can't boot the device, so i can't install any app to reboot in recovery mode. There is a way to boot recovery mode with a battery trick or through fastboot? Or even flash CWM ROM through fastboot? There is a way so that after installing the kernel it reboots automatically into recovery? Thanks beforehand, hope you can help me. (Sorry for my bad english, i'm from Chile )
Click to expand...
Click to collapse
Search Google for adb commands to boot downloadmod or recovery I'll post some when I have acsess to computer.
xavipr69 said:
.....i have a Galaxy S I9000b, with a broken power button..... Also i can't boot the device, so i can't install any app to reboot in recovery mode. There is a way to boot recovery mode with a battery trick or through fastboot?
Click to expand...
Click to collapse
You can enter your recovery mode with ADB prompts.
Here is a nice thread about simple solution:
http://forum.xda-developers.com/showthread.php?t=1474956
And here you can find much more about ADB:
http://forum.xda-developers.com/showthread.php?t=879701
Quote me again if you need more help, but try yourself upon the guides, all is very well described there. Also there are plenty of tutorial videos on YouTube about how to use ADB.
tetakpatak said:
You can enter your recovery mode with ADB prompts.
Here is a nice thread about simple solution:
http://forum.xda-developers.com/showthread.php?t=1474956
And here you can find much more about ADB:
http://forum.xda-developers.com/showthread.php?t=879701
Quote me again if you need more help, but try yourself upon the guides, all is very well described there. Also there are plenty of tutorial videos on YouTube about how to use ADB.
Click to expand...
Click to collapse
Hey, thanks for the help, but the thing is that i can't access the phone OS, so i can't enable USB debugging to start ADB, by the way i'm a little bit noob in this ADB thing, but i have installed android SDK, java and the drivers, i don't know if i need anything else. When in the command prompt i type "adb devices" but no device is recognized. Please help! Thanks beforehand
tetakpatak said:
You can enter your recovery mode with ADB prompts.
Here is a nice thread about simple solution:
http://forum.xda-developers.com/showthread.php?t=1474956
And here you can find much more about ADB:
http://forum.xda-developers.com/showthread.php?t=879701
Quote me again if you need more help, but try yourself upon the guides, all is very well described there. Also there are plenty of tutorial videos on YouTube about how to use ADB.
Click to expand...
Click to collapse
Please check my last post! Thanks
xavipr69 said:
Please check my last post! Thanks
Click to expand...
Click to collapse
Ouch, you're really in uncomfortable situation
I consider as best you can do to try to flash a stock ROM with Odin. I don't know if it will work, as your USB debugging isn't enabled (I must admit that I've never disabled it). I hope it will work!
If it works, it will result in data loss. Your photos and music will probably remain, but SMS, calls, contacts and all else will be lost. If you flash the same ROM you've used before your system crashed, you may be able to restore with Titanium app all the backups you did.
You can inforce your phone to run in the download mode by connecting an USB jig, that can be bought on eBay for ca $2. I hope our forum mate @xsenman will post for you more usable info, he is an angel of helping in such situations and knows specific questions about i9000B better than me. I am more familiar with the i9000
xavipr69 said:
Hi guys, the thing is that i have a Galaxy S I9000b, with a broken power button, and a bad CWM ROM. I installed CWM recovery through fastboot mode, but i can't access it. Also i have tried removing "--no-reboot" from de command in heimdall, it reboots, but it stucks on the first boot screen (device model and brand). Also i can't boot the device, so i can't install any app to reboot in recovery mode. There is a way to boot recovery mode with a battery trick or through fastboot? Or even flash CWM ROM through fastboot? There is a way so that after installing the kernel it reboots automatically into recovery? Thanks beforehand, hope you can help me. (Sorry for my bad english, i'm from Chile )
Click to expand...
Click to collapse
Basically, IF you cannot enter download mode because of power button, you can use other methods, look here in My Android Solutions for recovery / download mode solutions
You cannot use fastboot for Samsung galaxy phones, its all done by Odin3, heimdall or Mobile Odin , so go here and download the required files to flash. or i9000B Roms :- here & here or here for original stock ROM's
If you already had a ROM, and unable to boot you can flash a i9000B kernel to see IF it boots, from above link. For Normal Flash procedure look here
You only follow the procedure with the ROM's meant for i9000B, do not use other ROM's meant for other devices
Check this out! Links to useful Guides and " Banned " Documentaries
Hi everyone
I am attempting to boot my phone in download mode but I get the error above.
I followed this guide so that I can bypass the google account but in order to do that, I need to put the phone in download mode
http://www.techzai.com/bypass-google-account-galaxy-a6-a6/
It gets to recovery mode but not download mode
List in recovery has options such as :
Reboot options
Reboot to bootloader(doesn't do much other than starting the phone up normally)
apply updates via adb or sd card
wipe data cache(tried all options and successful but they haven't done anything)
mount system
view recovery logs
run graphic test
Can anyone tell me how I can flash the phone or what am I doing wrong ?
Thank you in advance
cpu2007 said:
Hi everyone
I am attempting to boot my phone in download mode but I get the error above.
I followed this guide so that I can bypass the google account but in order to do that, I need to put the phone in download mode
http://www.techzai.com/bypass-google-account-galaxy-a6-a6/
It gets to recovery mode but not download mode
List in recovery has options such as :
Reboot options
Reboot to bootloader(doesn't do much other than starting the phone up normally)
apply updates via adb or sd card
wipe data cache(tried all options and successful but they haven't done anything)
mount system
view recovery logs
run graphic test
Can anyone tell me how I can flash the phone or what am I doing wrong ?
Thank you in advance
Click to expand...
Click to collapse
Hello for download mode u need to press Volume Down and Vol Up when ur phone is off and at the same time plug ur usb cable to ur phone ;D
OMG That worked! Thank you so much!
Hi guys,
I just bought an SM-T290 for my wife and I was unable to find any info here about rooting it.
As most Tab-A tablets "are here", can I use a guide (and twrp) for an older tablet for this newer model?
I'm interested too. Bump!
interested too. This is somewhat confusing, so much things changed in the past 10 years. I remember using a single app and it was done...
I was reading through magisk documentation and it was saying that devices coming with android 9 are NON-A/B and requires magisk to be installed on recovery.... However, inputting the command getprop ro.treble.enabled returns true therefore confirming the device is A/B on the command line sooooooo I'm not sure what to do or where to start reading lol
Can anyone help please
collmomo said:
interested too. This is somewhat confusing, so much things changed in the past 10 years. I remember using a single app and it was done...
I was reading through magisk documentation and it was saying that devices coming with android 9 are NON-A/B and requires magisk to be installed on recovery.... However, inputting the command getprop ro.treble.enabled returns true therefore confirming the device is A/B on the command line sooooooo I'm not sure what to do or where to start reading lol
Can anyone help please
Click to expand...
Click to collapse
getprop ro.treble.enabled does not confirm the device is A/B.
All devices released with Oreo> should return that value irrespective of their file system layout.
Samsung devices released with Pie are SYSTEM AS ROOT and A only.
Is there a root that works for the T290?
treahuggs said:
Is there a root that works for the T290?
Click to expand...
Click to collapse
With MagiskManager processed the AP file from T295 firmware.
Files boot.img;recovery.img;vbmeta.img changed.
Unlocked the bootloader, which is done in 2 stages, however the file magisk_patched.tar does not flash through ODIN
Can a line in Downloading mode KG Status: Checking interfere?
I answer my own question ... I installed a pure stock firmware for the BTU region, blocked the bootloader, made the initial configuration after a reset, went into Downloading mode, there is no KG Status line! The bootloader unlocked again, there is no KG Status line, but the problem has not disappeared - the files patched by Magisk are still not flashing ...
P.S. I came to the conclusion that the problem is in Magisk, it does not know how to work with our model ...
You need to contact the Magisk developer, but is he interested in our device?
bump --- looking to root the sm-t290
Bump
Yeah i hope a dev will be also be able to have a custom rom for it
Talich52 said:
With MagiskManager processed the AP file from T295 firmware.
Files boot.img;recovery.img;vbmeta.img changed.
Unlocked the bootloader, which is done in 2 stages, however the file magisk_patched.tar does not flash through ODIN
Can a line in Downloading mode KG Status: Checking interfere?
I answer my own question ... I installed a pure stock firmware for the BTU region, blocked the bootloader, made the initial configuration after a reset, went into Downloading mode, there is no KG Status line! The bootloader unlocked again, there is no KG Status line, but the problem has not disappeared - the files patched by Magisk are still not flashing ...
P.S. I came to the conclusion that the problem is in Magisk, it does not know how to work with our model ...
You need to contact the Magisk developer, but is he interested in our device?
Click to expand...
Click to collapse
Can you post a step-by-step explaining how you unlocked the bootloader?
Also, I found a website that has a .tar file named "T290_U1_9.0_ ROOT_ Kernel_Magisk" specifically for the SM-T290 but I can't post the link here because I am a new user. I'm not sure if it will be of any help.
I tried flashing the file on that website with Odin 3.13.1 on my tab A with download mode on but it failed with the error "RQT_CLOSE". Maybe it's because I don't have the bootloader unlocked yet? Idk. I just got the device and I'm trying to figure out how to root it, but if it's unable to be rooted it is completely fine. I also tried flashing it with two other versions of Odin; however, those versions just got stuck on "boot.img" until I manually restarted the device. Any help will be appreciated
Here is the full log when I tried flashing it on Odin 3.13.1:
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 10 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
Koerst said:
Can you post a step-by-step explaining how you unlocked the bootloader?
Also, I found a website that has a .tar file named "T290_U1_9.0_ ROOT_ Kernel_Magisk" specifically for the SM-T290 but I can't post the link here because I am a new user. I'm not sure if it will be of any help.
I tried flashing the file on that website with Odin 3.13.1 on my tab A with download mode on but it failed with the error "RQT_CLOSE". Maybe it's because I don't have the bootloader unlocked yet? Idk. I just got the device and I'm trying to figure out how to root it, but if it's unable to be rooted it is completely fine. I also tried flashing it with two other versions of Odin; however, those versions just got stuck on "boot.img" until I manually restarted the device. Any help will be appreciated
Click to expand...
Click to collapse
B. Unlocking Bootloader :
https://forum.xda-developers.com/showpost.php?p=80116925&postcount=1
I found a similar file for my T295 for U1 & U2, but they also do not flash
Although the bootloader is unlocked ...
Talich52 said:
B. Unlocking Bootloader :
https://forum.xda-developers.com/showpost.php?p=80116925&postcount=1
I found a similar file for my T295 for U1 & U2, but they also do not flash
Although the bootloader is unlocked ...
Click to expand...
Click to collapse
This works for the T290? What rom did you install? I would love to get away from the Samsung version.
Talich52 said:
B. Unlocking Bootloader :
https://forum.xda-developers.com/showpost.php?p=80116925&postcount=1
I found a similar file for my T295 for U1 & U2, but they also do not flash
Although the bootloader is unlocked ...
Click to expand...
Click to collapse
I appreciate the help, but the instructions on the post are unclear to me. I enabled the OEM unlocking option in developer settings, but when I tried the instructions on the post it just does not work. I am able to get into download, bootloader, and recovery modes but I'm not sure what else to do.
Koerst said:
...I enabled the OEM unlocking option in developer settings, but when I tried the instructions on the post it just does not work. I am able to get into download, bootloader, and recovery modes but I'm not sure what else to do.
Click to expand...
Click to collapse
Before entering the firmware mode, the device first enters the warning screen and here you need to press and hold the Volume Up button for more than 10 seconds, after which the device will go into reboot with data reset... After booting, the item unlock OEM will become gray and inactive, in firmware mode there will be a line OEM LOCK: OFF (U), and at each reboot there will be a warning screen that the bootloader is unlocked.
xsnipuhx said:
This works for the T290? What rom did you install? I would love to get away from the Samsung version.
Click to expand...
Click to collapse
I can't check for T290, since I have T295 ,but both models are Tab A 8.0 2019
Unfortunately, unlocking the bootloader did not give anything,I could not root the device and even install at least one custom file
Talich52 said:
Before entering the firmware mode, the device first enters the warning screen and here you need to press and hold the Volume Up button for more than 10 seconds, after which the device will go into reboot with data reset... After booting, the item unlock OEM will become gray and inactive, in firmware mode there will be a line OEM LOCK: OFF (U), and at each reboot there will be a warning screen that the bootloader is unlocked.
Click to expand...
Click to collapse
I was able to successfully unlock the bootloader after trying a number of button combinations. Thanks a lot for the help!
I will try flashing that file again soon.
Koerst said:
I was able to successfully unlock the bootloader after trying a number of button combinations. Thanks a lot for the help!
I will try flashing that file again soon.
Click to expand...
Click to collapse
What did you do to unlock your SM-T290? And for treble support, what do I choose? Arm or arm64, a only or A/B? And how would I install the GSI without a TWRP recovery?
secretwolf98 said:
What did you do to unlock your SM-T290? And for treble support, what do I choose? Arm or arm64, a only or A/B? And how would I install the GSI without a TWRP recovery?
Click to expand...
Click to collapse
These are the steps I took to unlock the bootloader that worked for me:
1. Power off the tablet (And make sure OEM unlocking is enabled in developer settings)
2. This is the part that was a little tough for me to figure out, but this is generally how I think I did it. I pressed the power button once, then instantly after I pressed one of the volume buttons (Not sure which one I pressed) and then held both volume buttons and the power button. You'll get to this screen with a bunch of text and a few options. If this way doesn't work then you should try out some other combinations.
3. One of the options on the screen is to unlock the bootloader, which tells you to hold volume up in order to unlock it.
4. The tablet will factory reset and the bootloader will be unlocked. To prove it is unlocked, the OEM unlock option in dev settings will be grayed out and will say "The bootloader is already unlocked"
I don't know about treble support or GSI, I've never actually heard of those things before and I'm sure you're much more of an expert at them than I am.
Koerst said:
These are the steps I took to unlock the bootloader that worked for me:
1. Power off the tablet (And make sure OEM unlocking is enabled in developer settings)
2. This is the part that was a little tough for me to figure out, but this is generally how I think I did it. I pressed the power button once, then instantly after I pressed one of the volume buttons (Not sure which one I pressed) and then held both volume buttons and the power button. You'll get to this screen with a bunch of text and a few options. If this way doesn't work then you should try out some other combinations.
3. One of the options on the screen is to unlock the bootloader, which tells you to hold volume up in order to unlock it.
4. The tablet will factory reset and the bootloader will be unlocked. To prove it is unlocked, the OEM unlock option in dev settings will be grayed out and will say "The bootloader is already unlocked"
I don't know about treble support or GSI, I've never actually heard of those things before and I'm sure you're much more of an expert at them than I am.
Click to expand...
Click to collapse
GitHub explanation: https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
XDA explanation: https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
secretwolf98 said:
GitHub explanation: https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
XDA explanation: https://www.xda-developers.com/goog...ze-android-so-oems-can-update-devices-faster/
Click to expand...
Click to collapse
Thanks for the explanations.
I would like to add that to anyone who wants to attempt to unlock the bootloader, you should do so carefully and with precautions, because your device will do a factory reset and the process can even brick your device. Backup your device before you do it.
I bricked my tablet earlier today, not right after unlocking the bootloader but after a couple of times that I rebooted it and tried flashing the file that I found on that site. I was able to somehow unbrick it by wiping the cache partition and doing a factory reset. That didn't instantly unbrick it, but after one reboot I held the volume up button and somehow my tablet started up again. Whew. Anyway, I'm most likely going to stop searching for ways to root this thing. I think I have concluded that it is unrootable until further support is given by the developers of TWRP/Magisk/whoever and someone else who has more knowledge than me is able to figure something out.
Some tips for people who may need them:
- To get into recovery mode, I discovered that all you have to do is power off the tablet, then power it on again while holding both the volume up and power buttons. Then you can let go once the screen pops up.
- From recovery mode, you can wipe the cache partition, perform a factory reset, reboot the device normally, and do a bunch of other stuff. This is what I used to unbrick my tablet.
- To get into download mode (If you're trying to flash something using Odin) I could not figure out the hardware combination for it; however, I was able to get into download mode by installing the proper drivers on my computer, downloading Minimal ADB and Fastboot, connecting my tablet to my computer, and using the command "adb reboot download" on the ADB and Fastboot command prompt.
- If your tablet does get bricked (stuck on the Samsung logo) after unlocking the bootloader, try holding down the power button and see if that reboots it. If it does, do it again but this time hold the volume up button with the power button to get to recovery mode. You can try wiping the cache or resetting the device as that is what I believe worked for me.
Koerst said:
- To get into download mode (If you're trying to flash something using Odin) I could not figure out the hardware combination for it; however, I was able to get into download mode by installing the proper drivers on my computer, downloading Minimal ADB and Fastboot, connecting my tablet to my computer, and using the command "adb reboot download" on the ADB and Fastboot command prompt.
Click to expand...
Click to collapse
With the bootloader unlocked, this is simple:
Send the device to reboot, first the warning screen for the unlocked bootloader appears ... Press any volume button and see a menu where we select Recovery with the same volume buttons and press power ... the device enters ODIN mode firmware mode
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.