Database Users

Rooting A5 2016 marshmallow

Hello guys,
I really want to root my a5 2016 running on marshmallow but every thing fails.....Kingroot fails, kingoroot the same and when i try to do that with cf-auto root it says that flashing passes but "recovery is not seandroid enforcing".... I have ticked the oem unlock and the usb debbuging but still nothing....The only way to get my phone back working is to reflash the firmware that i had (the official marshmallow) but then it is not rooted!!! If anyone can help i would really appreciate it...
Thanks

i ran into these problems also, autoroot not working etc. and managed to fix it like this :
- Reminder but very important : as you mentioned first of all make sure oem settings is still enabled in settings/developper settings
- Flash TWRP for marshmallow with the NEWEST Odin, i used Odin3 v3.12.3 (my older version did not make TWRP stay after reboot, i tried like 10 times)
When you have twrp installed download UPDATE-SuperSU-v2.76-20160630161323.zip (or use the one from my attachment) and flash it, if root is not available from first try, flash again, i had to do it 2 times also.
I hope this works for you too

contrinsan said:
i ran into these problems also, autoroot not working etc. and managed to fix it like this :
- Reminder but very important : as you mentioned first of all make sure oem settings is still enabled in settings/developper settings
- Flash TWRP for marshmallow with the NEWEST Odin, i used Odin3 v3.12.3 (my older version did not make TWRP stay after reboot, i tried like 10 times)
When you have twrp installed download UPDATE-SuperSU-v2.76-20160630161323.zip (or use the one from my attachment) and flash it, if root is not available from first try, flash again, i had to do it 2 times also.
I hope this works for you too
Click to expand...
Click to collapse
Thanks man for your help but i have also tried to install twrp and it doesn't even boot to it....I try to boot to recovery and it shows neither the stock one nor the twrp...Can u give me a link and the exact steps you followed in order to manage to do it??

BillyGrls said:
Thanks man for your help but i have also tried to install twrp and it doesn't even boot to it....I try to boot to recovery and it shows neither the stock one nor the twrp...Can u give me a link and the exact steps you followed in order to manage to do it??
Click to expand...
Click to collapse
Sorry forget it i just realised u have given the link already lol

contrinsan said:
i ran into these problems also, autoroot not working etc. and managed to fix it like this :
- Reminder but very important : as you mentioned first of all make sure oem settings is still enabled in settings/developper settings
- Flash TWRP for marshmallow with the NEWEST Odin, i used Odin3 v3.12.3 (my older version did not make TWRP stay after reboot, i tried like 10 times)
When you have twrp installed download UPDATE-SuperSU-v2.76-20160630161323.zip (or use the one from my attachment) and flash it, if root is not available from first try, flash again, i had to do it 2 times also.
I hope this works for you too
Click to expand...
Click to collapse
It worked mate!!!! Thank u very much!!!!I really appreciate it

[Guide][How to]Update Bootloader/Firmware to OOS3/H2OS2 w/o installing OOS/H2OS

Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ones who are on stock recovery and just want to update their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
I created this thread to help the CM13(Official or Sultan's)//any custom rom using new BL,users who want to update their BL without flashing the OOS through the tedious way just to update BL and users who are stuck on bootlogo due to old BL with roms using new BL.
Here I will guide you through the required steps to update our bootloader "In easiest and fastest way without wiping and restoring anything".
So what are we waiting for ,lets start .
Prerequisites
you will need two files for this process,nothing else.
1 . First one is BLUpdater zip --->Here.
2. Second is TWRP compiled from latest sources use either This or the one from Here<--use v41 or use Sultan's from Here OR if you are Martin's fan like me and want to use his MutiRom TWRP goHere.
PS:I am assuming you have Unlocked Bootloader and have either
official/blu_spark/sultan's/ Multirom TWRP installed,in a working condition on OOS2.x BL(if not what are you doing here).
Note: make sure oem unlocking is checked in developer options in your current rom,else updating the BL may cause it to get locked ,and you will have to unlock it again and flash the recovery manually through fastboot itself.
Now the steps
1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
NOTE:If you chose to use Sultan's recovery.zip then just flash it normally.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Now voila you should have updated your firmware/BL.Congrats.
You can now install any rom that supports the new BL.Older roms won't boot on the new MM BL.So check the rom thread before installing the rom and later on quacking here about your device being stuck at bootlogo.
Notes
i)Neither I nor XDA will be responsible if your OPX bricks or explodes or ditches you and flies to space.
ii)We are not touching system partition so last installed ROM will be intact.
iii)This guide will leave you into bootable rom only if you have a rom installed that works on latest firmware.
iv)This can also be used to restore all your OPX partitions back to OOS3.x partition state,if you messed any.
v)In case you are using latest nightly (cm13) and face bootloop - go Here
psst:If you are not diggin the new BL,and wanna downgrade again ,back to old BL,check this post.
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you

matwaking said:
Okay guys first let me tell you why I have created a new thread just for updating the BL and Firmware ,
I know we already have methods of updating like:
1. flashing the full OOS3 zip through stock recovery ,this method is quite simple for the ons who are on stock recovery and just want to their OOS version.If you fall in this category then you have no purpose here,you may leave.
2. Is method provided by our fav helping hand @Joshwin Aranha ,that method is sure for the rest of us who dont fall in the above category,but is way too long,although simple and effective still "long".
So I created this thread just to shorten the process provided by Joshwin.I also created this thread to help the official CM13 users who have problem with latest nightlies due to new bootloader or are stuck in bootlogo.
...
PS: (second one,I know) This guide was made by taking inspiration from Joshwin's post and devtry method.
Also click Thanks if I helped you
Click to expand...
Click to collapse
Booomshkalaka!!!
Great guide, can't test (already have new bootloader and too lazy to switch back but look very good.
Thx to all
Kurt

Kurt Krummbein said:
Booomshkalaka!!!
Click to expand...
Click to collapse
Lol .
Thanks mate.

Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?

jonrodz said:
Will this work if I'm in bluspark twrp but the previous version..? Or do I have to change to official twrp?
Click to expand...
Click to collapse
Will work with any twrp,no requirement of official one.

Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?

jonrodz said:
Thanks, bro. One more doubt. I'm currently on DU rom with custom kernel... Do you think rom will boot after this..?
Click to expand...
Click to collapse
No it wont,right now almost all the custom roms need to update to support new firmware.Only latest cm13 nightlies are booting now,also aosp compiled by olddroid for new BL(shh its only for testers right now)
also maybe the MIUI8 port ,just posted in the forums.

I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?

jerikooo said:
I'm a litte bit confused.
Currently I'm on nighty October 1st. (cm-13.0-20161001-NIGHTLY-onyx.zip)
Can i update the Bootloader with your method and after that booting up my current nightly version?
Or do I have to update after the bootloader update to nightly version 12 (the currently latest)?
Click to expand...
Click to collapse
no update the BL using the steps above ,then flash the latest nightly.That way it would be good.
Or you can flash nightly first then update BL.Choice is yours.I recommend updating the BL first.

I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.

Duplicate post.Deleted

ccaappton said:
I followed your guide with a locked bootloader, and now I'm in bootloops . Just suggest you put a big red "make sure your bootloader is unlocked" in the steps, not in the footnote.
Click to expand...
Click to collapse
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader

matwaking said:
Reboot into fastboot mode and
Code:
fastboot oem unlock
And using a custom recovery and custom rom makes me assume one have unlocked bootloader
Click to expand...
Click to collapse
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!

ccaappton said:
Thanks! I actually relocked my bootloader not long after installed cm13, and disabled "unlock oem" in "developer settings"(I don't know why I did this). So both system and rec is inaccessible, and fastboot is useless in this case. Fortunately I followed the unbrick guide: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 and get the old bootloader back. Now I could enter CM13-09-28 with all my data intact.
Just hope to let people know the hard lesson I learned, and how to deal the bootloops.
And guys, NEVER RELOCK BOOTLOADER AGAIN!
Click to expand...
Click to collapse
Well no fix without any problems hehehe,.Haapy 4 u.
Click that button if you think my posts are useful

Is this enough to install CM14 or do i have to install the whole room and them flash CM14?

Manelit said:
Is this enough to install CM14 or do i have to install the whole room and them flash CM14?
Click to expand...
Click to collapse
taking you wanna flash ashwins cm14 right. You just wanna follow the instructions in first post and then flash the cm14.No need to install the whole Oos zip.
This way you should have updated BL and working cm14.
Just flash the cm14 after booting into new TWRP

I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm

slaav said:
I've just followed the procedure from OP and all went smooth as butter. Thanks
Directly after that (without reboot) I've installed the latest CM13 (with GApps) and Arsenic R24. Working as a charm
Click to expand...
Click to collapse
Press that sweet sweet button mate

1.First copy both of the above files in your sdcard or otg or ext-sdcard,any place accessible in recovery.
2. Now boot into recovery Choose Install and choose the "OPXBLUpdateOOS3.1" zip and flash it.
3. Don't reboot now ,go to Install again ,this time use "Install Image" button in lower right corner,navigate to folder where you copied the new TWRP,you should be able to see the file,select it ,choose recovery in the next menu and flash.
4. Don't reboot come back to TWRP home ,goto reboot and recovery ,if TWRP says no OS installed ignore it.
Click to expand...
Click to collapse
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)

walsash said:
Hi, everyone
I'm accidentally reboot device after second step. Now device freezing on "+1 powered by android". Can I remove this zip, or... what can I do next?)
Click to expand...
Click to collapse
u can flash bluespark twrp via fasboot
Sent from my ONE E1003 using XDA-Developers mobile app

[GUIDE] Error 7 Solution While flashing 7.1.2 ROMs

A brief Intro.
Starting from the 7.1.2 ROMs most of the developers decided to follow the process of checking modem version at the time of flashing the rom. Many peoples ended up in
"Error 7- assert(xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1")"
The main reason for this is the outdated firmware or it is happened to those who had unofficially unlocked the bootloader.
Some more info..
1. You must be on MM build bootloader. If you are unofficially unlocked bootloader it will give you ERROR7.
@TheStrix have alreday given a short information about it in his Official LineageOS thread. If you are unaware of it read it here
2.Outdated Firmware.
Your firmware must be from from MIUI Global DEV v7.5.4 or above.
Get MIUI Global DEV v7.5.4 from here
or the latest firmware from here
NB:-
- Iam using the MIUI Global DEV v7.5.4 firmware. All working fine including Volte. I dont know about the second one,you can give it a try.
-If you are unofficially unlocked ,MIUI Global DEV v7.5.4 will re lock your bootloader you will end up in bootloop.
- I will not be reponsible for any damages.
Solution 1 [Permanent Solution] ..
1. So if you are unofficially unlocked, i will suggest to clean flash the latest MIUI Fatboot Rom. Kenzo users get it from here.
2.Flash it using MIFlashTool ,and officially unlock it.
HOW TO UNLOCK THE BOOTLOADER OF REDMI NOTE 3?
PART 1 : REQUESTING FOR UNLOCK PERMISSION
Step 1 – Open up your favorite web browser in your computer (Chrome is recommended) then go to this link
Step 2 – You’ll see the official page of “Unlock Your Mi Device”. Now simply click on the blue “Unlock Now” Button in the middle of the page.
Step 3 – You’ll see a login page in the next page which is in Chinese. If you use Google Chrome to open the page, then you can simply use its built-in Google Translate feature.
Step 4 – Once logged in, you’ll see the Unlock Application Permissions page.Now simply fill in all required fields then click on that green Apply Immediately button.
Step 5 – In the next page, you’ll need to enter a verification code sent to you via SMS. Check your phone for any SMS verification sent by Xiaomi server. The code is usually valid for only 5 minutes so you need to enter it immediately.
Step 6– Once you have submitted the 6 digits code, you’ll then be redirected to another page saying that from the point toward all you need to do is just waiting for Xiaomi Developers to review and approve your application. Once approved, you’ll get another SMS which normally arrives in 15 min(Atleast for me. For some it may take time). The approval process is manual so just be patient on this.
PART 2 : BOOTLOADER UNLOCKING PROCESS
Requirements for Bootloader Unlocking :
-An active Mi account linked to your device, your phone number and it has permission to proceed with bootloader unlock (follow previous steps above)
-Please backup your data for just in case scenario.
-Again, if you are not fully aware of flashing custom ROM, then you better stay away of unlocking your phone’s bootloader.
Download Mi Flash Unlock tool for Windows here, and install it on your computer / PC.
Step 1 – On your device, please login to your Mi account.
Step 2 – Put / reboot your device into bootloader mode. To do that, simply turn off your device, press the Power button and Volume down ( – ) button at the same time.
Step 3 – On your computer, open MiFlash Unlock tool you’ve just installed. Click on the Agree button when asked.
Step 4 – Login to MiFlash Unlock tool with the same Mi Account.
Step 5 – Now connect your phone to computer using its USB cable.
Step 6 – Once your phone is connected, the Unlock button will become active. Next, simply click on the Unlock button to start the process. The unlock process will take about 10 – 15 seconds to complete. That’s all.
After unlocking your phone’s bootloader, you’ll be able to flash TWRP and other custom ROM. Enjoy..
Please take these as your concern upon unlocking bootloader :
One Mi account could only unlock one device within 30 days.
If you see a notice saying that “current user is not logged in connected device” then please reboot your device normally then login with your account in the device (see Step 1).
Unlocking bootloader will wipe all user data especially if your device is encrypted. That’s why you’ll need to create backup before going to proceed.
Neither Xiaomi or I will guaranteed if anything goes wrong during and as the result of unlocking. Proceed with your own risks.
Also, unlocked Xiaomi devices will be marked in the official service end.
PART 3 : Installing TWRP and Custom Rom.
Step 1 –. Get latest TWRP from here. Flash it via fastboot { I will not be explaining that in details}
Step 2 –. Take back up of EFS using Twrp. Wipe Everything including internal storage.
Step 3 –. Install Firmware-Rom-Gapps in order. Error 7 will be solved
Solution 2[Temporary Solution] ..
Only try this method if you are not able to officially unlock your device . Dont use the Firmware by Strix.It will relock your bootloader.
Step1 - Downalod the rom to your pc.
Step2 - Use any notepad. Suggestd one Notepad++. Get it from here
Step3 - Open the Rom.zip{dont extarct}. Navigate to META-INF/com/google/android/updater-script.
Double click on updater-script and open it with notepad++. Edit and remove this line from the file
Code:
assert(xiaomi.verify_modem("MSM8976.LA.1.0.c3-30041-STD.PROD-1.77504.1.83742.1") == "1")
Allow the file to save and close the zip.{Rom will recompress by itself}.
Step4 - Flash in order. Firmware -Rom-Gapps.
Some FAQ's ..
1. Iam not getting volte
Ans:- Restore the EFS. Try rebooting your phone 2 or 3 times. After Clean flash ,I had to reboot 3 times to get volte working. :fingers-crossed:
2.Iam not able to see FingerPrint Option?
Ans:- Your are defenitely on an old Firmware.Update to Latest Firmware It will work.
3.Iam getting Some other Errors. :crying:
Ans:- Post your Screen Shot Below.Will Check.
4.Iam getting some other problems in ROM.
Ans:- Report it with proper logs to the developer.Iam helpless.
5.I bricked my device
Ans:- I will Laugh at you. Always do everything at your own risk. :silly:
Some Advices ..
* At least use search once in your life time. From my observation its clear that no one ever uses search in the Rom Section. Even is there is a solution in every page you keep on asking same questions.
*Dont flood the thread.
*Dont qoute the whole op.
*Respect other members
If this was of help to anyone hit the like :fingers-crossed:

First

There's a problem with not updating the bootloader (aboot) and staying with a LP bootloader, you will most likely encounter bootloops. Say you edit that code line for the modem check, it will flash but it won't boot/work properly. You must update the bootloader in order to boot newer ROMs. And you need to update the modem and other stuff so you won't face issues. You need to offcially unlock no matter what you do, it's very easy.

Asphyxiate666 said:
There's a problem with not updating the bootloader (aboot) and stay with a LP bootloader, you will most likely encounter bootloops. Say you edit that code line for the modem check, it will flash but it won't boot. You must update the bootloader in order to boot newer ROMs. And you need to update the modem and other stuff so you won't face issues. You need to offcially unlock no matter what you do, it's very easy.
Click to expand...
Click to collapse
that's why I wrote temporary method..only for those who are lazy and not willing to start from root by flashing fastboot rom

adithyan25 said:
that's why I wrote temporary method..only for those who are lazy and not willing to start from root by flashing fastboot rom
Click to expand...
Click to collapse
I understand but with their laziness they will ruin their devices then come here and say "omg sir it doesn't boot wtf is this useless rom crap developers".

Asphyxiate666 said:
I understand but with their laziness they will ruin their devices then come here and say "omg sir it doesn't boot wtf is this useless rom crap developers".
Click to expand...
Click to collapse
I know that...most people don't even bother to use search..even if there is a solution just above their question they won't give a damn to look it..

guys help..i had officially unlocked the bootloader..and i don't remember the firmware i had installed...n i am still getting the error code 7..do i need to flash the kenzo global or dev firmware from the link..??

PrathaM X said:
guys help..i had officially unlocked the bootloader..and i don't remember the firmware i had installed...n i am still getting the error code 7..do i need to flash the kenzo global or dev firmware from the link..??
Click to expand...
Click to collapse
you must format your phone (not wipe) using twrp then install fw-rom-gapps...use fw by strix from above method(permanent)

I flashed v8.5.1.0 using MiFlash and it said flash completed successfully. However now it is stuck on the Mi splash screen with "powered by android" logo at the bottom. The dots are moving so I assume it is loading but it's been on that same screen for the past 10 minutes now.
Previously, the bootloader was officially unlocked but some stuff broke as I tried to upgrade to a new ROM and that's why I decided to flash v8.5.1.0 in order to go back to stock and start from scratch.
Edit: It works!

adithyan25 said:
you must format your phone (not wipe) using twrp then install fw-rom-gapps...use fw by strix from above method(permanent)
Click to expand...
Click to collapse
I'm on Marshmallow boot loader (flashed faatboot ROM) and officially unlocked & formated data.
Yesterday I did a update RR ROM (9th july) then I got error 7.
at the time of flashing I was on latest firmware 7.7.6.
So reflashed 7.5.4 firmware and it's worked.
So we should always stick to 7.5.4 firmware ? For avoiding error 7?

baku2313 said:
I'm on Marshmallow boot loader (flashed faatboot ROM) and officially unlocked & formated data.
Yesterday I did a update RR ROM (10th july) then I got error 7.
at the time of flashing I was on latest firmware 7.7.6.
So reflashed 7.5.4 firmware and it's worked.
So we should always stick to 7.5.4 firmware ? For avoiding error 7?
Click to expand...
Click to collapse
yep..in my knowledge the latest firmware has a change in modem version(updated version) so it wont match with one in updater script... so i will say to stick with some older firmware unless the developers chabge it in the roms update-script file...
iam using strix fw 7.6.15

adithyan25 said:
yep..in my knowledge the latest firmware has a change in modem version(updated version) so it wont match with one in updater script... so i will say to stick with some older firmware unless the developers chabge it in the roms update-script file...
iam using strix fw 7.6.15
Click to expand...
Click to collapse
Can you provide me the link please.

baku2313 said:
Can you provide me the link please.
Click to expand...
Click to collapse
its in the aosp extended 4.4 update op...
im quite busy now...i will share it later if you havent found it .... you will find the link in aosp extended thread

adithyan25 said:
its in the aosp extended 4.4 update op...
im quite busy now...i will share it later if you havent found it .... you will find the link in aosp extended thread
Click to expand...
Click to collapse
Strix updated his thread with 7.7.6 firmware (Kenzo).

I am on MM on Redmi note 3 Snapdragon version! I tried firmware (7.7.0 I guess) and then ROM Zip but still got the Problem ! Any thing else I can do?

What if i have locked bootloader and flashed twrp through miflash?

coolguy22 said:
What if i have locked bootloader and flashed twrp through miflash?
Click to expand...
Click to collapse
In theory it should work I guess? Assuming you used the guide from @khajiit here you should have a MarshMellow bootloader, as the MIUI version linked there is based on MM (kate_global_images_6.11.3_20161103.0000.00_6.0_global_16db0fc5fa), so it shouldn't relock. Can't try myself since I unlocked mine recently.

Amon_Re said:
In theory it should work I guess? Assuming you used the guide from @khajiithere you should have a MarshMellow bootloader, as the MIUI version linked there is based on MM (kate_global_images_6.11.3_20161103.0000.00_6.0_global_16db0fc5fa), so it shouldn't relock. Can't try myself since I unlocked mine recently.
Click to expand...
Click to collapse
Ok so if i get the latest firmware and install some 7.1.2 rom it shouldn't bootloop?

coolguy22 said:
Ok so if i get the latest firmware and install some 7.1.2 rom it shouldn't bootloop?
Click to expand...
Click to collapse
In theory, it should work.

..

Is there root for t817p? On nougat?

I didn't see any threads with this model

I'm on NOUGAT. Official build stock. Simple root same as always,
1. Developer options - own unlock
2 Download mode - flash TWRP 3.2.1
3. TWRP recovery - flash Magisk 16
Profit!
SM- T817
Btw u can flash unbranded FW XAS variant for Sprint, or 817R4 for all other carriershttps://updato.com/firmware-archive-select-model?record=6923350DAEEC11E7963AFA163EE8F90B

@beatbreakee Does it work for the AT&T (T817A) too?
And by the flash you mean, is it through Odin? I'm so scared that if i flash the wrong TWRP, it will get brick (because as long as i know, T817 is different with T817A)
---------- Post added at 04:01 PM ---------- Previous post was at 03:55 PM ----------
beatbreakee said:
I'm on NOUGAT. Official build stock. Simple root same as always,
1. Developer options - own unlock
2 Download mode - flash TWRP 3.2.1
3. TWRP recovery - flash Magisk 16
Profit!
SM- T817
Btw u can flash unbranded FW XAS variant for Sprint, or 817R4 for all other carriershttps://updato.com/firmware-archive-select-model?record=6923350DAEEC11E7963AFA163EE8F90B
Click to expand...
Click to collapse
And by the Own unlock, is that a typo? Was it OEM unlock?
And can i also flash T817's ROM ((such as Lineage) to T817A?
Thanks so much before! I'm hoping for your answer

Yes .. sorry it took so long I must have notifications turned off. And yes I meant OEM UNLOCK. (Autocorrect must have gotten me). And yes use Odin to flash TWRP, then use TWRP to flash Magisk. Here's what I have .. mine is an SM-T817P but this TWRP will work for all the 817 models, here's a link from Team Win website.
https://dl.twrp.me/gts210velte/twrp-3.2.1-0-gts210velte.img.tar.html
And then just Flash MAGISK 16.0 from here.
http://tiny.cc/latestmagisk
I take no credit for creation or discovery of these files. I had help from a few developers here when I needed it regarding my tab. I'm sure u will be fine, just make sure you double check 3 things.
1. Make sure OEM unlock is turned on in developer options
2. Make sure you flash the TWRP using Odin 3.07 (I used)
3. Uncheck AUTO REBOOT in Odin options. (This is important because on initial reboot you have to reboot into recovery 1st, otherwise the stock Rom will erase TWRP and go back to stock.)
MAKE SURE WHEN U FINISH THE TWRP FLASH, THAT YOU DO A HARD REBOOT, AND BOOT INTO RECOVERY AT LEAST 1 TIME BEFORE YOU LET YOUR STOCK ROM RUN. THIS WILL ENSURE TWRP STAYS INSTALLED.
Take care

beatbreakee said:
Yes .. sorry it took so long I must have notifications turned off. And yes I meant OEM UNLOCK. (Autocorrect must have gotten me). And yes use Odin to flash TWRP, then use TWRP to flash Magisk. Here's what I have .. mine is an SM-T817P but this TWRP will work for all the 817 models, here's a link from Team Win website.
https://dl.twrp.me/gts210velte/twrp-3.2.1-0-gts210velte.img.tar.html
And then just Flash MAGISK 16.0 from here.
http://tiny.cc/latestmagisk
I take no credit for creation or discovery of these files. I had help from a few developers here when I needed it regarding my tab. I'm sure u will be fine, just make sure you double check 3 things.
1. Make sure OEM unlock is turned on in developer options
2. Make sure you flash the TWRP using Odin 3.07 (I used)
3. Uncheck AUTO REBOOT in Odin options. (This is important because on initial reboot you have to reboot into recovery 1st, otherwise the stock Rom will erase TWRP and go back to stock.)
MAKE SURE WHEN U FINISH THE TWRP FLASH, THAT YOU DO A HARD REBOOT, AND BOOT INTO RECOVERY AT LEAST 1 TIME BEFORE YOU LET YOUR STOCK ROM RUN. THIS WILL ENSURE TWRP STAYS INSTALLED.
Take care
Click to expand...
Click to collapse
Wow man, thanks so much! I was so confuse about this TWRP thing. I'm not sure if will the TWRP for T817 works for T817A, P, etc. and vice versa. I'm really appreciated your help

i need efs and cert file for t817p.
pls mate, i need efs and cert file for t817p. pls i need it ugently for imei repair or does anyone have any way to repair imei on t817p sprint 3600000000000

TWRP, Rooting and Custom Rom HELP SM-T510 Tablet Tab A 10.1

Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)

You don’t unzip the .tar files. Keep them as is.

secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5

My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.

fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.

is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse

fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!

framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?

framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.

lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.

framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.

lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!

lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY

framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.

lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!

framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.