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.
Related
Hello everyone ,
My phone quite recently got soft bricked. It doesn't get past the initial boot image , and i can't even turn the phone off (It keeps rebooting) . I can manage to boot into the screen when you press power button + volume down , but if i click anything there ( such as recovery) , my phone just turns off. Sometimes when i click on recovery , it gets stuck at the TWRP load screen.
I'd be grateful if anybody could help me solve this problem
Go to fastboot mode and again correct flash twrp recovery
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
Flash official twrp
vaisakmct said:
Go to fastboot mode and again correct flash twrp recovery
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
Flash official twrp
Click to expand...
Click to collapse
What do you mean ?
I didn't get you
Anyways , I can't flash TWRP again because I can't enable USB debugging , my phone is stuck in a boot loop.
Any alternatives?
Thanks in advance
Chathur said:
What do you mean ?
I didn't get you
Anyways , I can't flash TWRP again because I can't enable USB debugging , my phone is stuck in a boot loop.
Any alternatives?
Thanks in advance
Click to expand...
Click to collapse
model xt106x?
reefuge said:
model xt106x?
Click to expand...
Click to collapse
Model XT1068
Chathur said:
Model XT1068
Click to expand...
Click to collapse
my signature contains Stock roms for XT1068 with a easy installer - that allows upgrade keeping data - just pick your region (normally 1st rom in post#1)
reefuge said:
my signature contains Stock roms for XT1068 with a easy installer - that allows upgrade keeping data - just pick your region (normally 1st rom in post#1)
Click to expand...
Click to collapse
Alright , thank you!
I'll check it out and get back to you with the result
reefuge said:
my signature contains Stock roms for XT1068 with a easy installer - that allows upgrade keeping data - just pick your region (normally 1st rom in post#1)
Click to expand...
Click to collapse
Hey , I went through your guide , but like I said , I have no means to enable the USB debugging :/
Any solutions ?
Thanks in advance
Chathur said:
Hey , I went through your guide , but like I said , I have no means to enable the USB debugging :/
Any solutions ?
Thanks in advance
Click to expand...
Click to collapse
well obviously you DID NOT as usb debugging NOT required......... this is flashed from pc via usb cable in AP FASTBOOT mode
INSTRUCTIONS for the firmware(s) in my signature
Make SURE you downloaded the correct firmware for your phone Moto G 2nd Gen, this MUST be for your version i.e XT1068 And region.
HOW TO USE:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
--- END ---
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
MENU OPTIONS
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Important Info
Upgrading from STOCK ROM example OPTIONS 1,3,4,6
DOWNGRADING from Custom ROM or HIGHER version of STOCK ROM OPTIONS 1,3,5,4,6 --- NOTE --- FACTORY RESET ALWAYS REQUIRED or phone will HANG
Do not unplug USB cable until phone reboots and remember it take 5 to 10+ mins to set up
So might seem stuck after boot animation... this is normal.
reefuge said:
well obviously you DID NOT as usb debugging NOT required......... this is flashed from pc via usb cable in AP FASTBOOT mode
INSTRUCTIONS for the firmware(s) in my signature
Make SURE you downloaded the correct firmware for your phone Moto G 2nd Gen, this MUST be for your version i.e XT1068 And region.
HOW TO USE:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
--- END ---
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
MENU OPTIONS
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Important Info
Upgrading from STOCK ROM example OPTIONS 1,3,4,6
DOWNGRADING from Custom ROM or HIGHER version of STOCK ROM OPTIONS 1,3,5,4,6 --- NOTE --- FACTORY RESET ALWAYS REQUIRED or phone will HANG
Do not unplug USB cable until phone reboots and remember it take 5 to 10+ mins to set up
So might seem stuck after boot animation... this is normal.
Click to expand...
Click to collapse
Worked like a charm.
Thank you so much , you saved me a lot of trouble and money.
Words can't express my gratitude.
Thank you.So.Damn.Much!
:fingers-crossed::fingers-crossed::laugh::laugh::good:
Hello guys,
Today I spent some hours trying to root & recovery a J3 2016 (J320M) and the process is pretty much the same as on almost all Samsung's smartphone, but the files from others threads did not worked.
Disclaimer: you flash these at your own risk. Knox counter will be tripped. Having the stock firmware to hand is also advised.
I advice that if you try to push the recovery.img from others releases (J320FN and else), may result a boot loop. (Like my first try).
HOW TO SOLVE THE LOOP:
- Run or Install SamFirm software;
- Write the model number and set the region. (You will need to google a little to find out what's the name of yours, mine is ZTO -> Brazil).
- You can fill all the boxes or can check "Auto" to skip it. ("auto" always worked to me).
- And than, click on "Check Update".
***Your mobile don't need to be plugged to do the research.
- If the software find a firmware, UNcheck the option "Check CRC32".
- Download and Decrypt throught the software.
- Using any version of Odin v3.09 or higher, connect the device on Download mode and select the firmware on "AP" slot and hit the start.
BEFORE MAKING MODIFICATIONS, IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK AND USB DEBUGGING FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
To install TWRP:
Boot to DOWNLOAD mode.
Flash with ODIN in the AP slot.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN or remove the USB cable and the battery for few seconds before the key combination.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery not in english.
* To change the language, select the right button and swipe left after the selection. :good:
***IF YOU ALLOW THE TWRP TO AUTO INSTALL THE SU, YOU MAY GET THE BOOT LOOP TOO.
Install the SU application:
Copy to the root of any microsd the file BETA-SuperSU..... below;
Inside the TWRP you have to select the option "Install" and choose the right file.
It's done!
I'M NOT THE OWNER OR CREATOR OF ANY FILE SHARED HERE, I'M ONLY SHARING WITH THE COMMUNITY.
Thanks too much! working Fine!
its nice to see download links without Adds. Really appreciate it!
works amazing! thank you so much!
How to unlock the bootloader
On samsung galaxy j320m
I got boot loop on my fully updated J320M. I found a working version of TWRP here:
https://forum.xda-developers.com/ga...rom-lineageos-14-1-samsung-galaxy-j3-t3667015
The "Recovery TWRP j3xlte 3.1.1 (with f2fs filesystem support)".
---------- Post added at 01:37 PM ---------- Previous post was at 01:35 PM ----------
Lins33130 said:
How to unlock the bootloader
On samsung galaxy j320m
Click to expand...
Click to collapse
Make sure OEM Unlock is enabled in Developer Mode Section.
Is there twerp for j320a?
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
Hey everyone, I no longer have this device, but, I guarantee that these steps will work and not brick your device if you follow them correctly!
PC side:-
1) Download the latest OTA update of android 10 for the Nokia 1 from here
https://android.googleapis.com/packages/ota-api/package/8f064e008ca0bb6616e4506f9c9c0f1d68257347.zip
2) Extract this file and you should see quite a few images, then copy the boot.img to your desktop for safety
Nokia 1 side:-
1) Update your Nokia 1 to the latest os either from the system update in settings or just copy over the .zip file we downloaded to a micro sd and apply the update from recovery
2) after you are on the latest update and no other updates are available, download the magisk canary apk from magisk GitHub and then install it
3) After that, copy the boot image we extracted earlier from the pc to the phone, then patch the copied boot image
4) After it's done flashing copy the patched image (from Downloads) to your pc
5)
PC side:-
1) Load any of the scatter files you have for the Nokia 1, the one from the stock rom is recommended
2) Load it in SP Flash tools
3) After that uncheck everything except the boot partition to be flashed
4) You will see a path of where the stock boot image is loaded from, if you click on it, a window will open asking you to select the boot image
5) select the patched boot image we copied to the pc earlier
and clock select
6) then click on the download button
Nokia 1 Side:-
1) Hold both volume up and volume down buttons together and connect it to your PC
PC side:-
1) It will begin flashing the boot image and will display a success message
Nokia 1 side:-
After it flashes successfully turn your device on and open magisk app, there it should say that magisk is installed
Credits to @GuyGotMadNameGame for the inspiration!
Reserved
Reserved!
Method mentioned in the OP worked 100% for me! Thanks for the amazing tip
I got hold of a discarded device and got it up running. Most of the above mentioned steps I could follow. Problem I have is that the download from the SP tool does not start. I think the exact steps for success must be slightliy different since somewhere else the method to bring the device into "download mode" is pressing volume-up and power simultaneously, not volume-up and volume-down.
What I did and what seems approximately the method for MTK devices is to power down the device and after pressing download in the SP tool to connect the device via USB. But it didn't start.
What could be wrong? Are there perhaps other prerequisites to fulfil, like unlocked bootloader? I was not yet able to achive that either.
linuxteddy said:
I got hold of a discarded device and got it up running. Most of the above mentioned steps I could follow. Problem I have is that the download from the SP tool does not start. I think the exact steps for success must be slightliy different since somewhere else the method to bring the device into "download mode" is pressing volume-up and power simultaneously, not volume-up and volume-down.
What I did and what seems approximately the method for MTK devices is to power down the device and after pressing download in the SP tool to connect the device via USB. But it didn't start.
What could be wrong? Are there perhaps other prerequisites to fulfil, like unlocked bootloader? I was not yet able to achive that either.
Click to expand...
Click to collapse
You need to have MTK USB drivers on your pc, and, I always held down volume up+down while device was fully off and then connected cable and it worked for me, not sure why it isn't working for your device
Hausemaster said:
You need to have MTK USB drivers on your pc, and, I always held down volume up+down while device was fully off and then connected cable and it worked for me, not sure why it isn't working for your device
Click to expand...
Click to collapse
Yeah, works better now. MTK drivers are included in Linux currently, but I needed to add my user to group dialout. Then the pressing of vol up and down worked.
I need to work out why the device told me at boot time that the verification failed (red state). I will try again, with option "keep forced encryption" off in Magisk.
linuxteddy said:
Yeah, works better now. MTK drivers are included in Linux currently, but I needed to add my user to group dialout. Then the pressing of vol up and down worked.
I need to work out why the device told me at boot time that the verification failed (red state). I will try again, with option "keep forced encryption" off in Magisk.
Click to expand...
Click to collapse
Hmm that shouldn't be happening, are you on latest firmware on your Nokia 1? As the boot.img from the link is for the latest Android 10 build
Hausemaster said:
Hmm that shouldn't be happening, are you on latest firmware on your Nokia 1? As the boot.img from the link is for the latest Android 10 build
Click to expand...
Click to collapse
Yes, the device is on the latest FW. Funny is, that after the failure I flashed the boot.img from the link, and the device boots again. That's prove, that the boot.img fits as well as the flashing procedure is working. The only culprit possible seems to be Magisk patching the boot.img.
What about the instructions given here: https://forum.xda-developers.com/t/unlocking-rooting-nokia-1-stock-rom-guide.3832230/post-77399813 ? I tried to unlock the bootloader, and it went as far as the command "fastboot oem key <md5>". Is it possible that it tampered the system? I could not unlock since the option in the developer settings is greyed out.
linuxteddy said:
Yes, the device is on the latest FW. Funny is, that after the failure I flashed the boot.img from the link, and the device boots again. That's prove, that the boot.img fits as well as the flashing procedure is working. The only culprit possible seems to be Magisk patching the boot.img.
What about the instructions given here: https://forum.xda-developers.com/t/unlocking-rooting-nokia-1-stock-rom-guide.3832230/post-77399813 ? I tried to unlock the bootloader, and it went as far as the command "fastboot oem key <md5>". Is it possible that it tampered the system? I could not unlock since the option in the developer settings is greyed out.
Click to expand...
Click to collapse
Did you try using both magisk canary and stable, also don't use mtp to transfer boot images, it damages them sometimes, also, don't unlock bootloader it worked fine when I did it with a locked bootloader for me...
Hausemaster said:
Did you try using both magisk canary and stable, also don't use mtp to transfer boot images, it damages them sometimes, also, don't unlock bootloader it worked fine when I did it with a locked bootloader for me...
Click to expand...
Click to collapse
I will try to use both. But how disable mtp? Do I need to transfer by SD card or cloud, bluetooth even?
linuxteddy said:
I will try to use both. But how disable mtp? Do I need to transfer by SD card or cloud, bluetooth even?
Click to expand...
Click to collapse
Transfer by Sd card is the safest
Hausemaster said:
Transfer by Sd card is the safest
Click to expand...
Click to collapse
I decided to md5-check the boot.img (patched an unpatched), and it all matches between PC and device. Therefore, I tried the Magisk 24.2 version (from stable) instead of the 24.3 canary. And now: It works.
Thanx a lot!
linuxteddy said:
I decided to md5-check the boot.img (patched an unpatched), and it all matches between PC and device. Therefore, I tried the Magisk 24.2 version (from stable) instead of the 24.3 canary. And now: It works.
Thanx a lot!
Click to expand...
Click to collapse
No problem, hope you have fun!
Today the A33 5G 128GB arrived, to flash twrp on it i had to enable oem unlock and usb debugging first in develeoper options.
To do that i had to complete the setup first, it's sick that the phone did NOT even let me complete the setup without connecting to the internet... this is out of control.
Now, i have oem unlock enabled aswell as usb debugging.
{
"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"
}
Next i connect the phone to PC and booted in download / odin mode.
Then i tried to flash this a33x_experimental_twrp.tar created by Zillion with odin, however as you can see on the next screenshot... the phone says "Custom Binary Blocked by OEM Lock"...
Why does the Phone say Custom Binary Blocked by OEM Lock even when i have it enabled in developer options??!
The Phone-Model is SM-A336B/DSN if that matters? I contacted my service provider from who i bought this phone and they told me that they are selling only this model.
Any help is welcome ...
My last hope is that someone from this forum can help me get twrp and lineage running, otherwise i'll have no choice but to return the phone within 14 days. No way i will use this device with the sick psycho spyware it contains.
PS: My only idea that might be worth a shot is booting twrp from adb terminal on pc, but i'm not sure how that works, how do i flash twrp permanently and how do i flash lineageos from adb, while i might be able to flash lineageos i'm not sure if that would work with the stock recovery..?
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
You can also use Adb ( Adb reboot download)
Privacydroid said:
Thanks for the info, i tried doing as you told boot in downloadmode and hold volume up untill unlockscreen appears, i'f been holding volume up for over 20 seconds but nothing happens.
Not that i doubt your instructions but are you sure this has to be done in downloadmode and not recovery?
Or do i have to press another button instead? Vol + doesn't seem to do anything.
Click to expand...
Click to collapse
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
V0latyle said:
Yes, I am sure, bootloader unlock is never done through recovery.
Turn your device off completely with USB disconnected. Leave it off for a minute or so. Then, hold both Volume buttons (DO NOT press Power) and plug in the USB cable from your computer.
This should start the device in Download mode.
Now, hold Volume Up until the bootloader unlock screen appears, which should have an instruction to either press or hold Volume Up to unlock the bootloader.
Click to expand...
Click to collapse
Thank you Sir. i totally forgot about the bootloader, and i didn't know how it works on the newer models (android 12), thanks to your easy insturctions i was able to unlock the bootloader.
V0latyle said:
You have to unlock your bootloader to be able to flash custom images such as TWRP. When in download mode, hold Volume + until the unlock screen appears. This will wipe data.
After you've unlocked the bootloader, you will need to boot to Android, connect to the Internet, and verify that OEM Unlocking is still visible in Developer Options. If it isn't, Vaultkeeper is not yet disabled and flashing custom images will result in boot failure.
Click to expand...
Click to collapse
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Privacydroid said:
I think the bootloader was sucessfully unlocked, just want to mention that after doing that (and the phone was erased) i do not see the oem unlock option under develeoper settings, all other options seem to be listed as normal.
So you are saying i must take care of vaultkeeper before finally flashing lineageos?
How would i handle that?
Click to expand...
Click to collapse
See Magisk installation instructions:
Unlocking the bootloader on modern Samsung devices have some caveats. The newly introduced VaultKeeper service will make the bootloader reject any unofficial partitions in some circumstances.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: power off your device and press the download mode key combo for your device
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again in later steps. Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode
Click to expand...
Click to collapse
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
V0latyle said:
See Magisk installation instructions:
If OEM Unlocking is not visible, Vaultkeeper has not unleashed the bootloader yet and you must fix this before proceeding. Look for "KG STATUS" on the screen when your device is in download mode; if this says "PRENORMAL" you cannot flash a custom image. If it says "CHECKING" you should be fine to flash TWRP, and once you flash TWRP, you can install LineageOS.
Click to expand...
Click to collapse
Well, i tried flashing twrp right now without using magsik, might have been a bad idea.. there's some error now.
Not really a surprise.. i never managed to brick a phone by all the idiotic things i'f done, no clue how to perceed now as the phone keep rebooting to the exact same screen with the exact same error message.
Did i damage the recovery?
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Arealhooman said:
You seem softbricked. You can always flash stock recovery. What happens when you try to boot to system? Is it just stuck in Odin mode?
Click to expand...
Click to collapse
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
Privacydroid said:
How do i boot to system? Just hold power button? Yes it keeps booting to odin mode, it does not even allow me to shutdown, keep booting to Odin.
Remember when you could simply unplug the battery...
Can i use Frija to download stock recovery or is it only for the "system os"?
View attachment 5790277
Click to expand...
Click to collapse
Yes.
Guide to Extract Stock Recovery:
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Btw its in the AP file
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
Indeed the twrp i tried to flash is experimental and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Arealhooman said:
Yes.
Guide to Extract Stock Recovery:
First, download the preferred Samsung stock firmware for your device model.
Extract the firmware zip file on your computer within a folder.
Open the .tar.md5 file using 7Zip. (Download 7Zip)
You will find the ‘recovery.img’ file. This is the stock recovery file for your Samsung device. Select it and hit Extract.
Compress the recovery image file via 7Zip tool in “.tar” format.
Put your Samsung device in Odin Download mode, select ‘AP’ or ‘PDA’ in Odin tool and select the new recovery.tar file, then hit the Start button.
(credit to Getdroidtips)
Click to expand...
Click to collapse
Thanks, i managed to re-flash the stock firmware!
I actually didn't want to whole system (the os) the be re-flashed but only the recovery, however when i extract the AP file i do not get any recovery.img file.
`
Edit: i see recovery.img.lz4 (can i use that aswell to re-flash stock recovery, i never saw .lz4 whatever that is.
I tried flashing twrp with odin by placing it in the AP slot, so since that didn't work would it be worth a shot trying to flash it with adb via pc instead? Or is magisk a hard requirement now to bypass Vaultkeeper to be able and flash twrp?
V0latyle said:
Given that TWRP for this device is experimental, this is pretty unsurprising.
Unfortunately without TWRP you won't be able to install LineageOS, unless there's another way I'm not aware of
Click to expand...
Click to collapse
actually theres a way of repacking using lz4 images, but i dont really know how to do it
Privacydroid said:
After re-flashing the stock firmware i checked the KG-STATUS and it says "broken"
View attachment 5790319
Indeed the twrp i tried to flash is experimentla and made by @Zillion
Might sound like a stupid question, people like andy yan appear to provide GSI's (generic system images) just curious if the same would be possible with twrp? A generic twrp image that is compatible with any/most devices? Basically, if mr Zillions twrp does not function yet, what other twrp could i try?
Click to expand...
Click to collapse
Wich device is that
*A33 TWRP was never meant for final users
The latest build was just a testing one