yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
I believe this is what he meant by settings up device normally

So on step 2 after unlocking bootloader, device gets wiped and we land on setup wizard that welcomes us and shows is various device setup options like phone name and connecting to wifi and entering Google counts etc.

OP SAYS TO SKIP THIS SETUP WIZARD AS MUCH AS we can

In step 3, settings up device normally means to go through each step of setup wizard ( like you normally did when you first bought your phone and set it up). It doesn't mean to restore smart switch backup.

Wipe again. Reflash stock rom and start from square 1. Don't restore any backup until you have twrp, root and unlocked bootloader.

Report again with your result

---------- Post added at 08:47 PM ---------- Previous post was at 08:44 PM ----------

Brother, did you unlocked bootloader like OP says.

Did you got that green download mode screen where you unlocked your bootloader??
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Apekator:
Yes, after unlock oem & enable usb debug.

Then shutdown, press power + vol up.

And select Reboot to bootloader for flash.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
It's power + volume down to enter download mode

Power + volume up is to enter recovery

Anyways can you take a photo of your screen in download mode and share it here so we all can try to troubleshoot your problem.

Make sure the text at recovery screen is ij focus
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ikkanomyoju:
not an easy one to crack

Ok. So wiped, reflashed AP from stock rom & started all over.

no joy, SAME RESULT: either bootloop or TWRP.

No more booting the system after Magisk patched recovery.img install under TWRP.

[MENTION=4443334]Grarak[/MENTION]: Am I the only one not getting Magisk ROOT to jive in this thread ?

Btw. device is A-705F. Stock-ROM from January 2020.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
[

--------- Post added at 02:55 AM ---------- Previous post was at 02:00 AM ----------

https://ibb.co/ws6Dqzk

---------- Post added at 03:37 AM ---------- Previous post was at 02:55 AM ----------

Enable Unlock OEM & USB DEBUG : https://ibb.co/p0wmgSC

Info Software : https://ibb.co/QXT5GMg

Result : https://ibb.co/ws6Dqzk

---------- Post added at 03:39 AM ---------- Previous post was at 03:37 AM ----------

Help me, Please.[/QUOTE]

Your problem is that you have enabled the oem unlock in developer settings but your bootloader is still locked.

See the text vbmeta blocked by oem lock.

What you need to do is to start with unlocking bootloader.

Ensure pen unlock is enables along with usb debugging.

Then as per OP instruction go. To. Download mode where you will get an option to. Unlock bootloader. Selecting that option will take you to the process of unlocking bootloader at end of which your phone will factory reset and you will land on setup wizard.

Skip through this setup wizard as much as you can and go back to developer option to. Ensure oem unlock is turned on and gray. That means now your bootloader is unlocked and you can flash vbmeta.

---------- Post added at 03:48 AM ---------- Previous post was at 03:45 AM ----------

Another senior should pip in

But I would have liked you to flash whole rom in odin not just AP. So you would have stock everything and then start from there.

Also please ensure if your downloaded files are okay and not corrupt

. Just a thought

But I'll like for someone more experienced to come and take over
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Apekator:
Your problem is that you have enabled the oem unlock in developer settings but your bootloader is still locked.

See the text vbmeta blocked by oem lock.

What you need to do is to start with unlocking bootloader.

Ensure pen unlock is enables along with usb debugging.

Then as per OP instruction go. To. Download mode where you will get an option to. Unlock bootloader. Selecting that option will take you to the process of unlocking bootloader at end of which your phone will factory reset and you will land on setup wizard.

Skip through this setup wizard as much as you can and go back to developer option to. Ensure oem unlock is turned on and gray. That means now your bootloader is unlocked and you can flash vbmeta.

---------- Post added at 03:48 AM ---------- Previous post was at 03:45 AM ----------

Another senior should pip in

But I would have liked you to flash whole rom in odin not just AP. So you would have stock everything and then start from there.

Also please ensure if your downloaded files are okay and not corrupt

. Just a thought

But I'll like for someone more experienced to come and take over[/QUOTE]

Yes ofcourse, i make sure the file is okay and not corrupt.

---------- Post added at 04:02 AM ---------- Previous post was at 03:54 AM ----------

I dont understand "Ensure pen unlock is enables along with usb debugging"

I feel like I have enable unlock oem & usb debug.

So, any solution for my problem "bootloader still locked"
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Apekator:
Thanks, i can unlock bootloader now...

And install twrp. ??? Thanks.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
if you want to keep stock os, follow the guide up to the point that twrp is installed including vbmeta. then after reboot and setup fully, go back to twrp and install magisk. if you are updated to android 10 stock, this will not work at all for you.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Apekator:
Crash.

only official released binaries are allowed to be flash

https://ibb.co/JddPP4X

Help...

---------- Post added at 05:37 AM ---------- Previous post was at 05:35 AM ----------

now what should I do brother?
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
lets goto pm so we don't flood the thred, we can post results when done. I need to get some info about your device.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Apekator:
Check pm bro
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
so everyone knows, whats going on with Apekators device is that Vbmeta wasn't flashed properly so the device tells you that the device is locked and it has to be returned to get fixed or something like that, don't worry, boot to download mode and no matter what that screen says,flash your stock rom using odin 3.13.3 then reboot. if you run into this issue, you WILL need your stock rom. you must use odin version 3.13.3.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
Vbmeta file corrupted during download most probably.

In the odin linked in OP there are two version of odin. One named as odin 3.13.3 and another odin despatched. Which one do I use?

---------- Post added at 08:14 AM ---------- Previous post was at 08:13 AM ----------

Now flash Vbmeta. Check integrity of your download and if possible download a fresh copy
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Apekator:
Bootloop again... After flash vbmeta with odin v3.13...

https://ibb.co/6X2Q1p7

Anyone know step by step...? Flash twrp, Because not work...

I dont know, where the problem...

Step :

1. UBL DEVICE (Work)

2. FLASH VBMETA with Odin v3.13 (ERROR)

3. I want to Flash TWRP (Can't to recovery)

#Flash stock rom again ??
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
What are you repacking your twrp with?

Winrar or 7 zip or some other tool
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Apekator:
With zip

Add to archive zip -> select format tar
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] kac222:
Read instructions in first post. There is all what you need.

Wysłane z mojego SM-A705FN przy użyciu Tapatalka
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] Apekator:
Yes bro...

I extract from rar and repack With zip

Add to archive zip -> select format tar
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ikkanomyoju:
usb debugging ?

1.) Not sure if this helps, but there's no mention you should enable USB debugging in OP - just OEM Unlock.

Maybe try without ?

2.) Also had the same issue - not being able to flash vbmeta bcause "only original", "Phone lock" & "service center blabla".

- The solution was to reflash STOCK ROM (at least the AP, which was just enough to boot normally again, flash vbmeta and get TWRP functional)

---

Bis: has anyone here succeeded doing the OP procedure & get TWRP + MAGISK ROOT on A705F working together - hello ... somebody out there ?

+ question for the experts: is strong protection option mentioned after 5.) in OP relevant at all to make Root work/system boot normally ? OP says there it should be mostly fine wether enabled or disabled, TWRP just won't b able to read /data. What's your mileage ?
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
So your problem persists?

You can either get twrp and functional phone. Or flashed magisk patched twrp and get into bootloop?
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
can anyone confirm that they have twrp working with stock rom?

can anyone confirm that they have magisk with stock rom?

---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------

ive uploaded vbmeta and recovery to android filehost. you do not need to repack these, just flash in odin, recovery first. here are some short steps, install stock rom and set it up as normal, check oem unlocking. boot to download mode, flash twrp, reboot directly back to download mode and flash vbmeta, reboot to twrp and make sure you do a factory reset, DO NOT FORMAT DATA OR WIPE ANYTHING, FACTORY RESET ONLY.

https://www.androidfilehost.com/?w=files&flid=311031
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
Use peazip software for windows.

Unpack the provided recovery zip to Get recovery.img file.

Right click this .img file and add to peazip archive.

Select tar as output format.

Make sure the output name is recovery

Once tar file is generated re-ensure file name as recovery.tar and this must contain only 1 file named recovery.img

Flash this recovery.tar in odin and report
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] brambles1234:
I need help - I flashed the magisk update today and this resulted in my A70 boot looping. Afterwards I tried to flash the Magisk zip file via TWRP however, this did not work. Next I tried to uninstall magisk using the uninstall zip however, it showed an error when flashing that said that 'Magisk is not installed' ?

My A70 is encrypted in TWRP so I cannot find the original saved boot.img as everything is a jumble of numbers and letters. Therefore, I am a bit stuck at present,and would appreciate some help please, so I don't lose my data on phone.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ikkanomyoju:
Happened just the same to me.

In OP it says make a backup of /boot partition in TWRP on SDCARD - did you follow that step ?

If yes, all you need to do is boot into TWRP & tap

-> restore

-> image

& find that folder on SDCARD

boot image is 64 Mb. Restores in 4 seconds & you're ready to reboot normally.

If no, there might be another option.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] brambles1234:
Thanks for getting back to me. Unfortunately I didn't make a back up of boot partition as my TWRP is encrypted, always has been since I rooted it.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
Encryption affects internal storage and affects data backup/restore.

Other partitions like system and boot etc can be backed up and restored.

Make sure backup location is external micro sd card
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ikkanomyoju:
the other option

So the other option, in case for example you use STOCK ROM, might be to extract boot.img from the AP file and flash it via Odin.

Link

Not guaranteed to work but maybe worth a try if you're desparate.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
Can someone confirm that the recovery.img is 80mb

And magisk patched.img is 26mb ( was patched via magisk canary Channel app)?
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ikkanomyoju:
recovery.img 78.9M

magisk_patched.img 26.8M (canary channel)
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
reinstall the rom and gapps
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ikkanomyoju:
[MENTION=5720765]fizzingbees[/MENTION]

The firmware is downloaded from samfrew website. What would be your method to check for file corruption ? -

On sammobile integrity of files is stated, if they show the .tar.md5 extension. There seems to be no place where md5 checksums of firmware files are provided to be checked against. Do you know of any ?
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
If a website provides you with md5 checksum then you can use utility like md5/SHA to telly the checksum and know integrity of your download.

I use samfirm utility v0. 3.6 for windows. It download at max speed , checks file integrity through CRC32 and then decrypt zip.enc4 to yield a zip file containing all firmware files( opening this zip file also gives your firmware files with tar.md5 extension thereby further confirming integrity of download.)
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] MarvinMod:
load the .md5 file into odin, it will check it for you.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
stuck at magisk may 2020 update

[MENTION=6698960]MarvinMod[/MENTION]

[MENTION=9127625]mindlery[/MENTION]

[MENTION=9216517]JakunTech1010[/MENTION]

a little help. i followed OP steps and [MENTION=9127625]mindlery[/MENTION] steps. everything went normal uptil twpr installation. but when i installed patched_magisk.img i went into bootloop where after 2nd boot it would land in twrp. There was no vbmeta or such error,just constant bootloop like this . so i went into twrp,restored backedup boot.img and i could boot up okay. then i followed [MENTION=9216517]JakunTech1010[/MENTION] where i booted into twrp,format data ,then wiped dalvik and cache , then installed magisk_patch.img and reboot...that worked .i had to reinstall magisk manager.

on opening magisk manager it asked for additional step and downloaded some zip and then rebooted itself to trwp. i DIDNT flashed anything and booted back to system and i had one bootloop and then it booted succesfully. again on opening magisk it after a while threw notification that DTBO has been patched ,reboot......so i rebooted and then i got stuck in bootloop. Also weirdly i had at this stage .on samsung A70 powered by android screen, information on top with some DID code . here oem lock=on ....weird....i could access twrp but restoring original boot.img didnt worked.

i have gone back to stock now .

my bootloader is still unlocked. OEM unlock is grayed out in developer options

please tell me what should i do now. What is this DTBO that was patched and can i avoid it ?

i am using magisk canary version to patch twrp.img

edit 1= repeated whole process so currently i have unlocked bootloader +twrp+magisk installed. magisk did additional steps and rebooted fine( albiet with 1-2 reboots and then landing in twrp from where i was able to reboot to system)

now it has send me DBTO patch done notification again which i have for time being ignored and havent rebooted phone. checking with root checker apps shows i have succesful root access( superSU prompt does show up).

now guide me what do i do about this DTBO that gave me bootloop last time.?
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] raeumler:
hi, because of just flashing boot doesnt work, i just deleted the system, userdata and vendor imgs from the AP file, patched the AP via magisk manager, then i flashed it with all the other stockfiles together: BL, MagiskPatched AP, CP and HOME_CSC. so if i loose root because of rebooting via hardwarebuttons or something else i simply can reflash it again without loosing data or data/media. but there is no twrp and root is lost when booting into stockrecovery. i really would like to know why its reflashing boot when reboot via powerbutton, instant reboot via app works, but then there is no shutdown logo. seems like android runs a script to change boot back to stock like it does when booting with a custom recovery (its a sh script: /system/bin/install-recovery.sh. seems that the imagefile is /system/recovery-from-boot.p) maybe there is such a script for rebooting. but i didnt find anything, logcat is to large and my knowledge about system is not that good...... its sm-a705fn with android 9 and binary U5 (i think that its the android 10 bootloader cause of when twrp is installed it doesnt decrypt)
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ikkanomyoju:
Tried your suggestion:

>downloaded Firmware again using FRIJA (1st source SAMFREW) -

>flashed the whole ROM - ODIN checks MD5 sums & all r ok (just as with firmware from SAMFREW btw.)

>started all the steps from 0

>used LATEST Magisk Canary (2d old) to patch Grarak's recovery.img & install magisk_patched.img via TWRP to /boot

Result: nothing changes.

In this case, all the steps were followed as in OP, but no result.

Which firmware do you use ?

Exactly. Though there is still access to TWRP using power+vol.up to get out of bootloop. It's the system that doesn't boot anymore.

For all those who successfully followed the procedure in OP & got root using it, would you mind posting your firmware version ?

This would greatly help. Thanks in advance.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
i have a70 FN/DS on stock android 9 stock ASL4 version with jan security updates( bootloader also updated ..i assume it v5 now ).

i unlocked bootloader+ flashed twrp+ got magisk working as per OP instructions and some other users specifically on post #336 by mindlery and post #367 by JakunTech1010

. But i am kinda stuck with magisk. specifically DTBO patch that magisk does and then requires reboot. previously on rebooting i got stuck in bootloop and had to flash stock rom again. now i got the notification but havent rebooted yet. root checker apps works fine too.

someone mentioned that bootloops are caused by magisk itself and instead of allowing magisk to reboot , manually shut down and boot to recovery and then from there reboot system.

i am currently waiting for senior member to help me this DTBO patching and bootlooping issue and how do i tackle it
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
DTBO patched now bootloop on reboot,FIX???

[MENTION=9127625]mindlery[/MENTION]
[MENTION=9216517]JakunTech1010[/MENTION]

can you guys offer some aid to my issue!
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
Honestly I am in the same boat.

To get out of bootloop, restore stock boot.img then reboot system.

Once you have successfully booted up, reboot onto recovery, factory reset, then install Magisk-patched image then reboot.

It's easier till this step.

Once your system boots up, install magisk manager, then it do additional steps and it will automatically reboot, maybe even to twrp from where you can reboot system.

After reboot completes and this is where I am getting stuck, magisk will patch dtbo and ask for reboot. If I reboot now, then I get into endless bootloop. I can access twrp, but rebooting system from there again cause bootloop.

I have powered off my device for time being and looking for answers. If nothing I can restore my stock boot.img to at least boot to system.

If someone is reading this and know solution, kindly reply
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
which magisk manager version did you used . can you attach with you post .

---------- Post added at 12:55 AM ---------- Previous post was at 12:43 AM ----------

so i managed to backup original boot+dtbo before i flashed magisk_patched.img the 2 time

restoring dtbo got me out of bootloop and into system. opening magisk manager again throws dtbo was patched. reboot device notification.

root still works

i installed vieper4android from xda labs,its succesfully rebooted device but the driver was abnormal.

rebooted again, this time somehow magisk root disappeared and i had magisk installed=N/A

root checking apps showed incomplete root

viper4android 2.7 was now working all fine.

this all is so bizzare. my hands are numb with anxiety

moreover i cant PM grarak and tell him about this situation.

my plan is to restore stock boot.img ang dtbo from twrp backup, reboot, install canary magiskmanager v283, reboot back to twrp and installed magisk_patched.img ( from canary magisk amanger 283) again. let it do additional steps after reboot and reopening app.

this will essentially bring me back to where i was in my previous post . playing tom and jerry with dtbo.

Update 2=> managed to get things backup and running. Have unlocked bootloader twrp and magisk all properly installed. Still dtbo is pesking me and causes boot loop when phone is rebooted.

So I installed viper4android fromm magisk modules. Open app afterwords. Let it do it thing and phone rebooted..

And again I lost magisk root.. Wtf...:crying:... Now what should I do.

Viper works fine despite no root and magisk manager not working.. Root apps also show unrootes device. But viper still works.. This is so strange

---------- Post added at 01:11 AM ---------- Previous post was at 12:55 AM ----------

is anyone facing dtbo drama with magisk manager (canary version 283) that i am facing.

if someone can provide detailed instructions that i can follow to get things up and working ,i shall be very grateful
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
update 3= welcome dissappointment

update 3= with viper4 android working and magisk manager saying no magisk installed along with root cheking apps saying no root, i tried to uninstall magisk manager>reboot> reinstall magisk manager> patch recovery.img again> reboot to twrp and flash in boot

BOOTLOOP again. no matter how many times i go into recovery and reboot from there. it never works. the only way i can boot system again is either a) factory reset ( where i type yes in twrp) then reflash magisk patched.img and then boot system where i would have working magisk or B) restore stock boot.img where magisk wouldnt work

but this vicious cycle continues and i cant break out of it.
[MENTION=4492846]ikkanomyoju[/MENTION] arent you facing the same issues

i am beyond frustated and disappointed. No one ..literally no one had this issue or can point me in right direction.

with heavy heart i am flashing stock and staying that way until SOMEONE,ANYONE can help with these issues in a more detailed way.

phone= samsung A70 FN/DS

firmware= android 9 pie , ASL4 with Jan 2020 security updates

odin= 3.13.1 downloaded from OP

twrp=downloaded from OP

magisk manager= canary ( version 283 and 284 both tried)
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] ikkanomyoju:
uncertainty

It would be nice if TWRP + Magisk worked together in the first place.

Seems you got farther here.

Looks like we don't even know whether it should work or not with what we have.

Maybe we're trying the unsolvable, waisting our time.

I am considering a Magisk-Root-install following TopJohnWu's guide (flashing magisk_patched.tar AP + rest of stock), just to see if it works on my device/firmware. Tried it yesterday but lost everything due to a checked "autoreboot" in Odin, LOL.

- Will keep posted.
[Samsung Galaxy A70 ROMs, Kernels, Recoveries, & Ot] fizzingbees:
Please do.

I'll keep trying on my end and keep. Updating accordingly.

This thread is very quite and people aren't responding even on PM.