Related
Hello
I had some problems with installing TWRP because there is no mirror for a flashable .zip file to our custom recovery. Also the flashing in ODIN caused a little headscrath but luckily some people of the forum helped me and i would like to help others - so here is a little guide.
Thanks to Bogeyof and another343.
Prerequisites
Stock device with stock recovery
Samsung drivers installed for your device
Download Odin above 3.09 (this guide is with 3.12) (others might work but i have best results in this version and above in general)
Download Odin TWRP Recovery (thanks to DJ_Steve) (It's linked in the attachements because of dead links in the other thread)
Download a custom rom of your choice (note the modelnumber of your device, ie. G800F)
1. Press and hold volume down, startbutton and power on button until the Samsung bootloader logo appears.
1. a. Now you are almost in download mode - press volume up once to be in download mode.
2. Plug the phone in with USB cabel.
3. Open Odin
4. Go to options (depending on the version) and remove the Auto Reset option but leave on the F. Reset time.
5. Press the AP button (depending on the version)
6. Find the recovery.tar.md5 file.
7. Make sure the phone is found in Odin (it will display in ID:COM and the Log)
8. Press Start (depending on the version) and it will start flashing - it will only take a couple of seconds.
9. Power down the phone and boot into recovery. (Volume up, startbutton and power on until logo appears)
Now you are in TWRP recovery.
I will update this guide at a later time. Any suggestions are valued. :fingers-crossed:
Can not get the TWRP 3.0.0
Where did you get TWRP 3.0.0, all the links I could find are dead.
One of the links worked shortly but i uploaded the file so you can get it.
hedgegee said:
One of the links worked shortly but i uploaded the file so you can get it.
Click to expand...
Click to collapse
Thanks, it worked perfectly!
No problem - i plan to upload Odin, etc. so everybody can have a working link.
Didn't work for me. Flashed. Odin showed that everything went fine but the phone still showing the green android picture and "Downloading... Do not turn off target!!"
If I power down and boot into recovery, I get the standard android recovery not TWRP..
: (
EDIT: My bad. Wrong buttons pressed. Everything is fine (I was doing Vol Down - Home - Power. Vol Up - Home - Power works)
Worst case
I could NOT believe that this guide promote the worst case!!!
Running Stock Rom (5.11 from sammobile G800FXXU1BPE3) plus CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5 and recovery.tar.md5.
Backup by TWRP 3.0 runs perfect, but the restore of that backup caused a hang on the start screen forever!!!!!!!
I had to flash everything again, lost all data, apps and settings (ended up like a factory reset), cause even a data restore ended up with the same hang at the start screen. Pretty ****ty that recommendation!!!!!!!!
Can you explain some more (maybe google translate?) its hard to understand what you mean? It has worked fine for others.
Worst case
hedgegee said:
Can you explain some more (maybe google translate?) its hard to understand what you mean? It has worked fine for others.
Click to expand...
Click to collapse
Shure, tell me what you need to know (not just explain some more), cause all facts are mentioned!
What I mean is said as well - softbrick after restore!
If it worked for others fine, I gess they have not tried a restore, cause simply a backup by TWRP 3.0 is fine and does not show the disaster!!!!!
Here again:
S5 Mini - Lollipop 5.11 DBT Version (Germany) G800FXXU1BPE3 from Sammobile 2016-06-08
Rooted with unlocked Bootloader by Chainfire Version CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5
all flashed by Odin
and than your Guide
TWRP Version recovery.tar.md5 downloaded from your guide side and flashed by Odin
So far no problem.
Backup by TWRP no problem.
Restore of that backup - softbrick!!! - phone hang on the start screen forever!!!!!!!
I can not make it more clear!
Problem BootLoop TWRP 3.0 after restore backup
aniksha said:
Shure, tell me what you need to know (not just explain some more), cause all facts are mentioned!
What I mean is said as well - softbrick after restore!
If it worked for others fine, I gess they have not tried a restore, cause simply a backup by TWRP 3.0 is fine and does not show the disaster!!!!!
Here again:
S5 Mini - Lollipop 5.11 DBT Version (Germany) G800FXXU1BPE3 from Sammobile 2016-06-08
Rooted with unlocked Bootloader by Chainfire Version CF-Auto-Root-kminilte-kminiltexx-smg800f.tar.md5
all flashed by Odin
and than your Guide
TWRP Version recovery.tar.md5 downloaded from your guide side and flashed by Odin
So far no problem.
Backup by TWRP no problem.
Restore of that backup - softbrick!!! - phone hang on the start screen forever!!!!!!!
I can not make it more clear!
Click to expand...
Click to collapse
idem restoration with TWRP 3.0 produces eternal bootloop also in KitKat, perhaps TWRP 2.8 works well
Bootloop at startscreen
RicSou said:
idem restoration with TWRP 3.0 produces eternal bootloop also in KitKat, perhaps TWRP 2.8 works well
Click to expand...
Click to collapse
Hi RicSou,
Do you known any link for TWRP 2.8 (to flash with Odin) ???
Cause at the official TWRP side is no S5 Mini (G800F). Just S5 Neo, Plus, Qualcomm.
That's why I used the link from this guide side and I though that recommendation is fine (but it ended in a disaster).
aniksha said:
Hi RicSou,
Do you known any link for TWRP 2.8 (to flash with Odin) ???
Cause at the official TWRP side is no S5 Mini (G800F). Just S5 Neo, Plus, Qualcomm.
That's why I used the link from this guide side and I though that recommendation is fine (but it ended in a disaster).
Click to expand...
Click to collapse
Yes twrp 2.8. https://www.androidfilehost.com/?fid=24052804347794463 look at private messages
RicSou said:
Yes twrp 2.8. https://www.androidfilehost.com/?fid=24052804347794463 look at private messages
Click to expand...
Click to collapse
TWRP 3.0 and 2.8 fails to restore nandroid backup... and I can not find the reason for the failure, restore someone without problems?
restore nandroid backup
Hi,
is there a version of TWRP that can restore a nandroid backup ? I just see a lot of problems with the TWRP recovery and nobody seems to be able to do a working restore on a G800F .
somebody ? with which version ??
I also tried TWRP 3.0 if I remember correctly posted by Steve and this recovery seriously destroyed my phone. I couldn't install any OS because most of time CRASH. I couldn't even turned on the phone again after installation of this file. - [ I ADVICE EVERY ONE TO NOT INSTALL THIS VERSION OF TWRP ] -
Greetings and Thank you G
Don't know if you have tried these https://aykevl.nl/android I have not tried them myself and not sure if they are the same as what has been posted before or even suitable ?
Backup solution by FlashFire
RicSou said:
TWRP 3.0 and 2.8 fails to restore nandroid backup... and I can not find the reason for the failure, restore someone without problems?
Click to expand...
Click to collapse
Too many 'greenshorns' publish untested guides, that's the problem!
The only backup app, which does the job absolutely perfect on a G800F is FlashFire!
At least with my configuration (mention before in that threat).
Chainfire is serious and FlashFire an awesome app.
The best investment I ever made (Pro Version).
Even with a bootloop (and without TWRP) the job is done within 30 minutes.
Just flash the firmware (from sammobile with Odin) root it (by Chainfire with Odin), install FlashFire and run the FlashFire backup.
That works perfect !!!
FlashFire can also restore its own backup by TWRP, but there is no official TWRP Version for G800F !!!
I have not tested that option yet.
---------- Post added at 11:34 PM ---------- Previous post was at 11:31 PM ----------
lop1 said:
Hi,
is there a version of TWRP that can restore a nandroid backup ? I just see a lot of problems with the TWRP recovery and nobody seems to be able to do a working restore on a G800F .
somebody ? with which version ??
Click to expand...
Click to collapse
Too many 'greenshorns' publish untested guides, that's the problem!
The only backup app, which does the job absolutely perfect on a G800F is FlashFire!
At least with my configuration (mention before in that threat).
Chainfire is serious and FlashFire an awesome app.
The best investment I ever made (Pro Version).
Even with a bootloop (and without TWRP) the job is done within 30 minutes.
Just flash the firmware (from sammobile with Odin) root it (by Chainfire with Odin), install FlashFire and run the FlashFire backup.
That works perfect !!!
FlashFire can also restore its own backup by TWRP, but there is no official TWRP Version for G800F !!!
I have not tested that option yet.
Tanks a lot for your answer. I fully trust a Chainfire solution ( highest respected android guy ), and you have used it without problems .
So this will be my solution for backup/restore , I am going to buy flash fire right away.
Best regards
Dear hedgegee,
you have published that guide!
So let us know under which phone 'configuration' your superguide was working for you?
Have you made a restore by a TWRP backup ???
It is time for the truth now!
Like to hear from you.
Hi Dudes,
My S5 Mini won' accept the TWRP Flash with Odin. Whatever .tar i use, ODIN says "Pass" and after reboot i still get the original samsung recovery.
Samsung KIES is installed and disabled during installation. (for the drivers)
I used ODIN 3.10.6 and 3.12.3 and the linked twrp.
Any ideas?
Thx so far.
Adittional: My Samsung ROM is Nr. LMY47X.G800FXXU1BPE3 if i have to downgrade or smth...
EDIT: Problem solved. You need to flash CF-Autoroot first.
download.chainfire.eu/523/CF-Root/CF-Auto-Root/CF-Auto-Root-kminilte-kminiltexx-smg800f.zip
Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
xperia ray said:
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
Click to expand...
Click to collapse
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Anlle said:
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Click to expand...
Click to collapse
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
xperia ray said:
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
Click to expand...
Click to collapse
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Anlle said:
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Click to expand...
Click to collapse
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/gal...j7nxt-t3974337
xperia ray said:
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
Click to expand...
Click to collapse
Thanks
According to the photos shown, you need to use MiracleBox, as it is prenormal
Try using this tutorial
From the forum I followed these step to install magisk:
- Patched my boot.img of my current rom using Magisk Manager and flashed via fastboot
- After rebooting from fastboot it got stuck in recovery so had to wipe all data and it booted finally
- After booting up installed Magisk Manager and both Magisk and Magisk manager shows green tick (installed)
But at this stage, whenever I open Magisk, it shows a recommendation to install a ZIP, if I agree to install it, phone gets stuck in recovery again.
If I choose not to install recommended zip and click Install > Direct Install, phone gets stuck in recovery again anyway
Everytime it gets stuck I have to wipe all data and start all over again. Anyone else facing same issue? Any solution?
Really frustrated right now.
My current rom is : DAVINCIIN INDIAN Global_V11.0.2.0
Used latest magisk manager 7.4.0
I have official recovery, not TWRP.
Afraid that flashing TWRP now will brick it for good.
UPDATE: Got the solution here, thanks @pikchu289 !
Twrp up to now is the best way
But check some stuff first
1.unlock the boot loader
2.chech if the magisk zip/img is corrupted or any file
3.does your os support this magisk version
Any way you can flash twrp because many people had already tried it and tested it from installing zips/ROMs/mods etc.. to backup files/data or even fixing some corrupted files that caused boot loops manually
But there are various things that doesn't work usually such as restoring system partition but never worry about this because if any thing failed just use miflash tool to go back to official/stock rom
Edit : I think something's wrong with your magisk version number
I have no idea which rom youre using or why on earth you didn't install TWRP before messing around with the os but some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Solve this solution
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
pikchu289 said:
Dear stone_henge!
I found a method to solve this solution after a lot of days I tried a lot of times! As follows:
1. I back up my Internal storage to my PC
2. Format Data (In TWRP: Wipe -> Format Data)
3. I reboot back into recovery
4. I connected my device to PC via a cable and copy two files: "Magisk-v20.1.zip" and "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" into Internal storage. Then rename "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" to "Disable_ForceEncrypt.zip"
4. I flash "Magisk-v20.1.zip", then I reboot back into recovery again.
5. I flash "Disable_ForceEncrypt.zip" . Reboot to system and setting my phone like after flash a new room, and then I installed "MagiskManager-v7.4.0.apk"
It's working for me!
You can download "Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip" here: https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Click to expand...
Click to collapse
Finally someone with an answer!
Thanks... Will try and see if it works...
UPDATE: IT WORKED!
Aserar said:
I have no idea which rom youre using
Click to expand...
Click to collapse
Maybe I should've used font size 72 while writing the rom I'm using above.
Aserar said:
why on earth you didn't install TWRP before messing around with the os
Click to expand...
Click to collapse
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
Aserar said:
some roms dont work with latest magisk and you have to use a specific older version depends on your rom, and you can't update magisk at any point as long as youre on this version of the rom. Ive always used custom recovery and when facing an issue with magisk you just boot to recovery and flash the 'magisk uninstaller' zip (available on magisk xda page) and reboot and you get system. No need to start from scratch
Click to expand...
Click to collapse
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
stone_henge said:
Maybe I should've used font size 72 while writing the rom I'm using above.
Yeah some people prefer to have stock recovery and not mess with the phone that much... But while you seem to be an expert on what to do, maybe you could try be helpful a bit and provide with the guide of flashing TWRP on k20? Yeah i can obviously see there are guides already in the forum but I'm curious to know which one you followed.
None of these lines actually answer my problem or even help in any way. But thanks for enlightening me. -_-
Click to expand...
Click to collapse
Aserar said:
It's true I did miss the part where you mentioned your rom but let's recap..
I did tell you you should install custom recovery.
I did tell you you should probably stick with the magisk version that works and not to update.
I did tell you you don't need to start over every time you get a problem caused by magisk and you can just flash magisk uninstaller and get your system back.
You don't see any of that helpful??? That's fine bc I got news for you.. THIS FORUM IS FREE! Do I have to research your problem for you and give you a step by step guide or else you whine about it?? Plus this is a public forum. People share the knowledge they have with everyone who reads it now and in the future and might get a piece of information out of it.
If you use the time you waste attacking people who used their time to try and help you (instead of saying thanks anyway like the rest of us do) into doing your research (like the rest of us do too) you'll probably be fine.
Click to expand...
Click to collapse
Sorry for being harsh... I understand you actually tried to help. It's actually really frustrating when facing a problem that has no straightforward solution.
Sorry mate.
finally i founded how to fix this issue without formating data of ur device
--just the flash the same the full custom rom or stock rom that u r using currently on . and boom restart. and ur issue fixed
Install a magisk zip without TWRP. TWRP takes too long. Instead use Aodin to flash a rom specific to your device version. Make sure it is not corrupted as well
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.