Database Develop

Rooting 10.3.1.A.0.244 Firmware.

Instructions for obtaining the rights to the .244. This method seems to work for many and has been confirmed over at a private forum.
If you already have downloaded 10.3.1.A.0.244,
1. Flash 10.1.1.A.1.310 with all Wipes using flashtools (All data will be erased.)
2. Obtain Root using the toolkit.
3. Flash this Recovery to your device.
4. Download the System only Rom and put it on the sd-card.
5. Go into Recovery (when the press "Volume up" when the blue LED lights up)
6. Search for the previously downloaded System only Rom file and flash it in CWM recovery.
7. Boot into flash mode (when booting from USB-connected cable to press "Volume down")
8. Flash 10.3.1.A.0.244 through FlashTool without system (tick the box Exclude) / / After loading you will have the new firmware./ /
9. Flash Recovery again.
10. Download the latest version SuperSU (at the bottom of the link to the zip file), add this file to the sd-card.
11. Go into Recovery, flash the archive SuperSU / / After loading you will have the new firmware with the normal working Root privileges./ /

thanks for the info.
can you please put screen shot tutorials or video tutorials for this?
i'm newbie @ flashing and rooting.
don't know where can i find recovery for xperia zr.

akash4357 said:
Instructions for obtaining the rights to the .244. This method seems to work for many and has been confirmed over at a private forum.
If you already have downloaded 10.3.1.A.0.244,
1. Flash 10.1.1.A.1.310 with all Wipes using flashtools (All data will be erased.)
2. Obtain Root using the toolkit.
3. Flash Recovery.
4. Download and put it on the sd-card.
5. Go into Recovery (when the press "Volume up" when the blue LED lights up)
6. Search for the previously downloaded file.
7. Boot into flash mode (when booting from USB-connected cable to press "Volume down")
8. Flash 10.3.1.A.0.244 through FlashTool without system (tick the box Exclude) / / After loading you will have the new firmware./ /
9. Flash Recovery again.
10. Download the latest version SuperSU (at the bottom of the link to the zip file), add this file to the sd-card.
11. Go into Recovery, flash the archive SuperSU / / After loading you will have the new firmware with the normal working Root privileges./ /
Click to expand...
Click to collapse
So are you now using this rooted 4.2.2? No more bootloop?

I haven't tried it yet as I'm out right now. But people at the other forum say that it's working and they have root access.
Sent from my C5503 using Tapatalk 2

akash4357 said:
I haven't tried it yet as I'm out right now. But people at the other forum say that it's working and they have root access.
Sent from my C5503 using Tapatalk 2
Click to expand...
Click to collapse
with locked or unlocked bootloader?
i'm wating unlocked one.

@akash4357 Which recovery would that be?

Thanks akash4357, appreciate your efforts however I have a couple questions though.
akash4357 said:
If you already have downloaded 10.3.1.A.0.244,
1. Flash 10.1.1.A.1.310 with all Wipes using flashtools (All data will be erased.)
2. Obtain Root using the toolkit.
3. Flash Recovery.
4. Download and put it on the sd-card.
5. Go into Recovery (when the press "Volume up" when the blue LED lights up)
6. Search for the previously downloaded file.
7. Boot into flash mode (when booting from USB-connected cable to press "Volume down")
8. Flash 10.3.1.A.0.244 through FlashTool without system (tick the box Exclude) / / After loading you will have the new firmware./ /
9. Flash Recovery again.
10. Download the latest version SuperSU (at the bottom of the link to the zip file), add this file to the sd-card.
11. Go into Recovery, flash the archive SuperSU / / After loading you will have the new firmware with the normal working Root privileges./ /
Click to expand...
Click to collapse
6. when you wrote "search for the previously downloaded file", do you mean I should install the .zip file from SD card?
9. How can you flash the recovery if you will not have root access? Or recovery can still be installed with out root?
---------- Post added 7th August 2013 at 12:13 AM ---------- Previous post was 6th August 2013 at 11:50 PM ----------
Noonski said:
@akash4357 Which recovery would that be?
Click to expand...
Click to collapse
Here you go Boss, this is the one i am using, just made a thread about it. Not sure which Recovery is being used in the instructions on this thread however.
http://forum.xda-developers.com/showthread.php?p=44361947#post44361947

WOW
akash4357 said:
Instructions for obtaining the rights to the .244. This method seems to work for many and has been confirmed over at a private forum.
If you already have downloaded 10.3.1.A.0.244,
1. Flash 10.1.1.A.1.310 with all Wipes using flashtools (All data will be erased.)
2. Obtain Root using the toolkit.
3. Flash Recovery.
4. Download and put it on the sd-card.
5. Go into Recovery (when the press "Volume up" when the blue LED lights up)
6. Search for the previously downloaded file.
7. Boot into flash mode (when booting from USB-connected cable to press "Volume down")
8. Flash 10.3.1.A.0.244 through FlashTool without system (tick the box Exclude) / / After loading you will have the new firmware./ /
9. Flash Recovery again.
10. Download the latest version SuperSU (at the bottom of the link to the zip file), add this file to the sd-card.
11. Go into Recovery, flash the archive SuperSU / / After loading you will have the new firmware with the normal working Root privileges./ /
Click to expand...
Click to collapse
well... it was a real pain in the a** but it worked!

gmengass said:
Thanks akash4357, appreciate your efforts however I have a couple questions though.
6. when you wrote "search for the previously downloaded file", do you mean I should install the .zip file from SD card?
9. How can you flash the recovery if you will not have root access? Or recovery can still be installed with out root?
---------- Post added 7th August 2013 at 12:13 AM ---------- Previous post was 6th August 2013 at 11:50 PM ----------
Here you go Boss, this is the one i am using, just made a thread about it. Not sure which Recovery is being used in the instructions on this thread however.
http://forum.xda-developers.com/showthread.php?p=44361947#post44361947
Click to expand...
Click to collapse
for number 6, he means to flash the file you have downloaded on step 4. for number 9, you already have root access on that point given that you have followed all preceding instructions. The file you flashed on step 6 is the pre-rooted system partition of the 244 firmware, that is why on step 8 he indicated that you should not include flashing of the system part.
offtopic: now that there is a root method for xperia ZR, I will be buying it in the coming weeks. =))

Now it all seems to work fine so far. But what still hold me back is the pre-rooted zip file with the system partition from an unknown source. I always run custom ROM on my Android phones but usually they're from the developer directly. Flashing zip files downloaded from these Russian websites seem a bit risky. Anyone knows more about the source of it?

itandy said:
Now it all seems to work fine so far. But what still hold me back is the pre-rooted zip file with the system partition from an unknown source. I always run custom ROM on my Android phones but usually they're from the developer directly. Flashing zip files downloaded from these Russian websites seem a bit risky. Anyone knows more about the source of it?
Click to expand...
Click to collapse
It's a very trusted private forum. Why would i post something from somewhere that I don't trust?
Moreover Root on 4.2.2 is now active!!

itandy said:
So are you now using this rooted 4.2.2? No more bootloop?
Click to expand...
Click to collapse
Yes no more bootloops! Rooted and everything is fine :good:

akash4357 said:
It's a very trusted private forum. Why would i post something from somewhere that I don't trust?
Moreover Root on 4.2.2 is now active!!
Click to expand...
Click to collapse
Seems like I'm also going to flash it soon. Thanks! :laugh:

I can confirm the method working.
@akash4357 I took the liberty of adding a few more links and words to your description.
I also don't get the reboots I had on the .310 rom with SuperSU while deleting System apps using Titanium Backup.

request :/
can you guys make a flashable rooted zip of the 4.2.2 firmware please? i was deleting some bloatware and looks like i did something wrong and got a bootloop for some reason. Now i had to wipe data and everything, even the internal storage was formatted when wiping data!!! Reinstall the firmware and lost root, so ill have to do it all over again for the love of god, please!:crying:

zytres said:
can you guys make a flashable rooted zip of the 4.2.2 firmware please? i was deleting some bloatware and looks like i did something wrong and got a bootloop for some reason. Now i had to wipe data and everything, even the internal storage was formatted when wiping data!!! Reinstall the firmware and lost root, so ill have to do it all over again for the love of god, please!:crying:
Click to expand...
Click to collapse
The file zr244-system-supersu.zip is already a flashable zip of system partition with busybox, su and Superuser.apk. So you might find your missing files there or flash it for the whole system partition.

also..
itandy said:
The file zr244-system-supersu.zip is already a flashable zip of system partition with busybox, su and Superuser.apk. So you might find your missing files there or flash it for the whole system partition.
Click to expand...
Click to collapse
Also i forgot to mention that i was unable to enter recovery. It turned on the green led and i tried with both volume up and volume down and it didnt work several times.

Noonski said:
I can confirm the method working.
@akash4357 I took the liberty of adding a few more links and words to your description.
I also don't get the reboots I had on the .310 rom with SuperSU while deleting System apps using Titanium Backup.
Click to expand...
Click to collapse
Thanks for the edit! You saved me some time.
Are you by any chance planning any ROM development for the ZR?

Just followed the instructions and upgraded to 4.2.2 with root. Data is preserved and so far everything seems fine. Finally see lockscreen widgets again!

is anyone able to get into recovery? pressing up or down during the green light doesnt do anything. the only way i can access recovery is to reflash it every time.

Get Root after Update to Lollipop on T-800 (WIFI)

Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.

dadanepal said:
Here is what I had to do to get ROOT on Lollipop.
-
Upgrade to Lollipop ( I did it the ODIN method but shouldn't matter if you do OTA)
- ODIN Flash CF-AutoRoot from the first thread. http://forum.xda-developers.com/show...34&postcount=1
- Let Device Reboot
- Go to Download Mode Again
- ODIN flash the latest TWRP. http://twrp.me/devices/samsunggalaxytabs105.html
- Let device reboot.
- Download latest SuperSU here and store it in your device. http://download.chainfire.eu/696/Sup...erSU-v2.46.zip
- Go into Recover by Power+Home+Volume Up.
- Instal the SuperSU zip you downloaded.
You should be good.
Took me a while to get this figured out so just sharing what i found.
If this helped please hit the thanks button.
Click to expand...
Click to collapse
I can confirm that this process does work. It's the method I went through when I upgraded my Tab S.

Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372

ashyx said:
Tbh that is a long winded way to achieve something much easier. The Cf-autoroot step was totally unnecessary. It only does what the supersu zip does or twrp does itself.
Just flash TWRP from the first post. It will root your device with the latest binary.
http://forum.xda-developers.com/galaxy-tab-s/development/test-twrp-2-8-60-recovery-mod-t3066372
Click to expand...
Click to collapse
Thanks for the update. Are you going to keep up with every new SU updated binaries and update TWRP every time the binaries are update. That would be great if you are willing to do that. I rather rely on the actual TWRP and SuperSU Developers to give me the zips etc. and flash my self as long winded as that may seem but people can choose.

Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue now.
Regarding cf-autoroot. I don't think people realise there is nothing special about how it roots.
It basically does the same thing that twrp does itself or flashing a super su zip.
Cf-autoroot simply installs a modified stock recovery which runs a script to Install root then flashes back stock recovery.
If someone intends to install a custom recovery anyway then there is no point in running cf-autoroot.
Twrp will do exactly the same thing and so does installing a super su zip.
They all accomplish the same thing using a slightly different method.
The only difference will be that chainfire may keep each cf-autroot updated with the latest binary.
The reason chainfire created it is for people who want to stick with stock recovery instead of custom

ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse

deno24 said:
ashyx said:
Twrp is updated more often than the super su binary, but team win never seem to update the binary, so I'll just update it myself with each release. Not only that, each new twrp release has the same problems as mentioned in my original post.
I'm also looking for a way to get MTP working properly as that is the only issue n
So i tried the auto root no luck, what mode do i flash twrp in odin?
Click to expand...
Click to collapse
Mode? Just load it and flash it.
Click to expand...
Click to collapse

ashyx said:
deno24 said:
Mode? Just load it and flash it.
Click to expand...
Click to collapse
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse

deno24 said:
ashyx said:
yeah in AP mode?
im trying to root this
Click to expand...
Click to collapse
That's the one.
Click to expand...
Click to collapse

ashyx said:
deno24 said:
That's the one.
Click to expand...
Click to collapse
cool so i flash twrp and ill have root? been a cpl oif years since ive done this last root was note2
Click to expand...
Click to collapse

Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.

ashyx said:
Just flash twrp, boot into it then hit reboot. Twrp will give you the option to root.
If doesn't then you are already rooted and probably just need to update the super su app.
Click to expand...
Click to collapse
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks

d3xtr0 said:
I did that and I can't boot into twrp, samsung recovery is shown. Looks like it can't rewrite the original recovery. Used your version from 30th March with Odin 10.6.
Thanks
Click to expand...
Click to collapse
That's a feature of lollipop. It overwrites with stock recovery. Happens on many devices. You need to boot into recovery immediately after flashing twrp, twrp will then patch it so stock recovery can't replace it.
When flashing uncheck auto reboot in odin. When it finishes flashing hold power + vol down + home. As soon as the screen goes blank hold power +vol up + home to boot into recovery.

Thanks for the information, but now I've flashed your new package root+twrp and it's working great
Thanks again.
Sent from my MI 4W

Whith this method, what is the knox value?

Knox is one ( .. )
Newer thread opened yesterday.
Edit:
http://forum.xda-developers.com/showthread.php?t=3079488
[ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805 [Tab S 10.5 ]
Sent from my MI 4W

[RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A5(2015) SM-A500F/FU/G/H/M

Unofficial release -TWRP recovery for the Galaxy A5 - SM-A500F/FU/G/H/M, Qualcomm MSM8916
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
SEANDROID warning fix
Recovery reboot fix
Modem, APNHLOS, EFS and Recovery partition backup
29/4/2016 - Time offset fix
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
Instructions:
Flash with ODIN 3.10.7 in the AP slot:
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Flash with TWRP:
Extract the recovery.img from the tar archive then in TWRP select Install>>Install image.
twrp_3.0.2-1_sm-a500
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
http://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
DEVICE TREE: soon
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Credits: Me, Teamwin and my testers- icesehman, -CALIBAN666-, jimbomodder
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
.

I'll be keeping an eye on this thread

Thankyou.... Working Fine..
No reboot issue.. A500G

Any tried to see if aroma files now flash OK?
From the giver of stock roms
Edit..
Works fine finally [emoji122] [emoji122]

Hello! You're the best! Can you make TWRP 3 for Galaxy A7 SM-A700FD? How to fix recovery reboot?
Thank you!

jazzzzy said:
Hello! You're the best! Can you make TWRP 3 for Galaxy A7 SM-A700FD? How to fix recovery reboot?
Thank you!
Click to expand...
Click to collapse
Isn't there already twrp for A700FD?

ashyx said:
Isn't there already twrp for A700FD?
Click to expand...
Click to collapse
All unofficial versions have reboot bug. And as far as I new - you managed to fix it!

only problem when reboot from xposed power menu mod (wanam, apm+, etc). Need to flash again via odin and uninstall the module.

icesehman said:
only problem when reboot from xposed power menu mod (wanam, apm+, etc). Need to flash again via odin and uninstall the module.
Click to expand...
Click to collapse
Thank you.
OK, I'll try to disable wanam's power menu and flash TWRP. I'll write the result. ...
I disabled wanam's power menu, flashed TWRP 3.0.0 without autoreboot ticked and rebooted into recovery.
Then I set time settings in TWRP and started backup. Backup completed...
Reboot from TWRP (Reboot System) - Reboot normal !!!
I will watch its behavour ... and perhaps the problem is solved.

jazzzzy said:
All unofficial versions have reboot bug. And as far as I new - you managed to fix it!
Click to expand...
Click to collapse
I'll see what I can do, time permitting.

So Far So Good.
Good job Mr. @ashyx , I've tested this recovery and two problems fixed out of three.
SEANDROID Error: Fixed.
Recovery reboot : Didn't fixed
EFS, APNHLOS etc... partitions Backup : Fixed
I reverted back to 2.8.7.0 recovery until recovery reboot get fixed.
I'll post a recovery log soon.
I'm using A500H Duos.
Thanks.

Ahmed_Khalifa said:
Good job Mr. @ashyx
Recovery reboot : Didn't fixed
Click to expand...
Click to collapse
Others say this issue is fixed?

ashyx said:
Does this fix the touchscreen and reboot issue?
https://www.androidfilehost.com/?fid=24499762636004631
Click to expand...
Click to collapse
That links for a300
Sent from my SM-A500FU

Whoops wrong thread!
Sent from my HTC One_M8 using XDA Free mobile app

Little Confused.
ashyx said:
Others say this issue is fixed?
Click to expand...
Click to collapse
Are they using A500H or other variant?

Ahmed_Khalifa said:
Are they using A500H or other variant?
Click to expand...
Click to collapse
You need to be sure it's a problem with the recovery. Power off your device and boot to system normally.
Using a terminal emulator type:
su
reboot recovery
Do you still get a recovery loop?

recovery reboot problem.
ashyx said:
You need to be sure it's a problem with the recovery. Power off your device and boot to system normally.
Using a terminal emulator type:
su
reboot recovery
Do you still get a recovery loop?
Click to expand...
Click to collapse
Here is what I did:
I flashed the recovery via flashify.
I rebooted the device normally.
After the phone restarts, it shows the Yellow colored warning Set warrenty bit: recovery.
The device boots into TWRP recovery mode.
After that I press reboot -> system.
After restart, it goes back to step 3.
Thank you.

That seems like you have flashed the boot partition with the recovery.img.
Please don't flash with Flashify. You cannot trust that it is flashing correctly.
Use the recovery image flash option in TWRP itself or use ODIN.
Sent from my HTC One_M8 using XDA Free mobile app

If we reboot directly to recovery, i mean through wannam xpossed power menu, recovery reboot issue occurs.. Pls fix this too..
Otherwise all are perfect

the error still exists.
ashyx said:
That seems like you have flashed the boot partition with the recovery.img.
Please don't flash with Flashify. You cannot trust that it is flashing correctly.
Use the recovery image flash option in TWRP itself or use ODIN.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I used the flash option in TWRP but it still reboots into recovery.
I posted a recovery log maybe it'll help you fix the problem.
by the way, can you tell me which baseband,pda,csc you're using?
my software might be a little old?
Thanks.

How to install MAGISC without TWRP and locked bootloader?

Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk

Not to hijack your thread, so consider this a free bump, but I am also curious. Galaxy S7 G920T here and looking for the same options.

JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Sent from my Redmi 2 using Tapatalk

fake2die said:
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Click to expand...
Click to collapse
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.

veez21 said:
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
Click to expand...
Click to collapse
Right! So you can accomplish a Magisk install without a custom recovery for example using the Magisk Manager or Flashfire but as stated above, in order to boot a modified boot.img the bootloader needs to be unlocked or otherwise it will refuse to boot it.

There should be an option to install magisc like a systeme update with the stock recovery.
Gesendet von meinem XT1650 mit Tapatalk

JRapsky said:
There should be an option to install magisc like a systeme update with the stock recovery.
Click to expand...
Click to collapse
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.

Sytis said:
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Click to expand...
Click to collapse
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?

COOLPLAY6FAN said:
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
Click to expand...
Click to collapse
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).

JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Actually you can boot into twrp rather than install/flash twrp which means u must use cmd to boot twrp everytime for flashing something~ As for locked bootloader, just like others said, you must unlock it.

Didgeridoohan said:
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
Click to expand...
Click to collapse
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance

COOLPLAY6FAN said:
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
Click to expand...
Click to collapse
There are installation instructions on how to create the patched boot image with the Magisk Manager in the release thread.
When you have the patched_boot.img file, you'll need to flash it to your device. On most normal devices you can do this with fastboot. Check out your device's forums/DuckDuckGo/Google/Whatever-search-engine-you-use for instructions on that.

I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
* Unlocked bootloader is needed. Period.
* A custom recovery is needed to flash Magisk. TWRP for instance.
* That custom recovery prevent the built-in OTA update to work
* But TWRP can flash OTA updates that can be downloader from XDA for example
Am I correct?
Also,
* Magisk needs a patched boot image
* This image has no impact on the OTA process at all
* There are encryption matters to take care of (I don't understand them yet though).
Is everything correct?
Thanks.

Krystanos said:
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
Click to expand...
Click to collapse
Let's see about answering those statements/questions.
* Unlocked bootloader is needed. Period.
Click to expand...
Click to collapse
Yes.
* A custom recovery is needed to flash Magisk. TWRP for instance.
Click to expand...
Click to collapse
Not necessarily. You can let the Magisk Manager patch your device's stock boot image and then flash it to your device with fastboot. See the installation instructions in the release thread.
* That custom recovery prevent the built-in OTA update to work
Click to expand...
Click to collapse
Yes.
* But TWRP can flash OTA updates that can be downloader from XDA for example
Click to expand...
Click to collapse
No. And yes. Official OTA files can (most of the time) not be flashed in TWRP. ROM zips and flashable firmware packages can.
* Magisk needs a patched boot image
Click to expand...
Click to collapse
Yes, that's all Magisk is about.
* This image has no impact on the OTA process at all
Click to expand...
Click to collapse
It definitely does. See the official docs
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips for more info on how to keep OTA capabilities for your device.
* There are encryption matters to take care of (I don't understand them yet though).
Click to expand...
Click to collapse
Possibly. Depends on what you're talking about.

Great answers. It's more clear for me now. Many thanks sir!

JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Hi!
There are good news for you, rooting with magisk is very easy that way . No bootloader unlocking, custom recovery,
adb and fastboot command, no sdk no mtk tool . NOTHING but Sp flashtool - our best friend. This method really works with mtk phones android 5.0+ .
What U only need is
Sp flashtool and its drivers /scatter file with the ROM/ -I think not mtk devices with their own flashtool will work too
the ROM of your device
Magisc manager app on the phone
First of all you need clear up the device / after backup somewhere if needed/with sp flashtool - flash the whole ROM in format+download mode.
Install Magisc manager app , it will load for U a zip file in the map of the app
Put the boot img file of your rom in that map too
Run install option - it will create a patched boot img file within the app s map
Run again sp flashtool with download mode , mark only the boot section , and flash that patched boot img in phone
After reboot phone it is rooted
best regards

Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it? 
 @Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)

lefteriskmail said:
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
Click to expand...
Click to collapse
Install Magisk Manager.
Press install.
Select "Patch Boot Image File".
Select the stock boot image you've previously saved on your device.
Wait.
Flash the patched boot image to your device.
Done.
All of this is covered in the installation instructions...
The folder being mentioned above is MagiskManager on your internal storage (where the patched boot image is also stored).

Magisc
Hi!
Magisc works fine for me from the first time. Excuse me I won't do installation again to see how it goes. Really it causes some hesitation but in the end it's clear.
I use Total commander, and magisc folder is on the external SD card after installing magisc manager app. Factory reset later will not clear the root. After installing manager it says "not installed" till the end of the rooting process. Opening the app it begins to look after the downloadable zip file, you have to wait and download it. This zip and the stock boot img must be in the same place in a folder, and the app itself makes the patched boot img but I don't remember what was the name of the option. This is the flashable img file. In the end after flashing with flashtool and rebooting, magisc manager says "installed". Good luck

Hi, I am trying to centralise this sort of information and am compiling it in another topic for Magisk and android-based media centres too.
Trying to properly document things (full sentences with references, links, and examples) rather than just writing some brief summarised steps that most people will not understand - not just for myself but to share should it assist others learn and understand the preparation and steps involved, plus consequences and ramifications of their actions (which never seem to be stressed enough).
Here is what I have compiled. Hopefully it will help and prevent you going loopy!? :silly:
- - - - - - - - - - - - - - - - - - - -
*** EXTREMELY CLEAR MAGISK ROOT INSTRUCTIONS ***
(Work In Progress! To Be Verified & Critiqued By Others)​
Connect your WiFi so that all auxillary files can be downloaded during the rooting process.
Ensure you have a minimum of 2GB of free disk space. Allow for 1-2 hours to perform these steps. Do not rush!
Bootloaders come with every Android device, and give it all the instructions on how to boot and what to execute. If your Bootloader is locked, then you have not flashed anything like TWRP previously, or, you have re-flashed a stock Bootloader and Recovery, etc. The process is much easier when you have previously rooted the device using another method, and the Bootloader already unlocked.
To preserve your System partition, Magisk only modifies the unlocked Bootloader boot partition, which can easily* be restored and 'locked' later.
0. Before starting anything, always perform a FULL Backup (ADB) of your device, using a good quality USB cable and ADB FastBoot toolkit. Or on some devices you can use a Micro SD card with a TWRP recovery.img to boot into TWRP to perform a backup of partitions. Do both if you want! Make sure you search for the appropriate commands and usage of ADB FastBoot backup so that all data is backed up and included.
> ADB FastBoot: https://developer.android.com/studio/releases/platform-tools.html
> TWRP: https://dl.twrp.me/twrpapp/ \\ https://twrp.me/FAQ/
> Plus various other solutions...
1. Identify your device's firmware, build number, Bootloader, full unique model number, etc. Download any two of these apps:
a) AIDA64 ("System", "CPU" & "Android" tabs.)
b) Device Info HW ("General" & "System" tabs.)
c) DevCheck ("Hardware" & "System" tabs.)
2. Download the stock Bootloader, Recovery and Firmware (___.tar.md5) for your device model, variant and OS. (e.g. match your firmware, build number, bootloader, full unique module number, etc). Some sites will force you to pay to download - search around and you can get free download links, or sometimes from the manufacturer's site. From this firmware, we need to either extract or download the stock Bootloader.img image separately.
3. Install Magisk Manager v5.3-v5.6 as of 2017.02.22 ("Magisc" is typo by guy above).
4. Open Magisk and go to settings, adjust theme, change the language, enable notify for updates, change prompt timeout, etc.
5. On the home screen of the Magisk Manager app, click "Install" then in the pop-up select "Install" again.
a) If you have root access already, choose "Direct Method" - Select, wait, reboot and done (very easy!);
b) If you have stock recovery & locked bootloader, choose "Patch Boot Image File" - in the pop-up explorer, browse for the downloaded Bootloader Image.
c) ... I don't know about "Download ZIP Only" - I assume for flashing with Odin or ADB FastBoot from PC or existing root/unlocked user....?
NOTE: If you are being asked to browse and select a file, be aware that there is no confirmation! As soon as you click, that JPG or RAR archive will be used for patching (and result in an error if cannot be extracted!!!)
6. A file will likely be downloaded in the background (flashable ZIP), a black screen will pop-up processing etc. Wait.....
The processed Boot image will be processed and output to the /MagiskManager/ directory.
If you do NOT have root, or custom recovery, you will need to:
a) grab a PC, install the USB drivers for your device and confirm your device is fully recognised
b) then flash the "patched" Boot image from the Magisk Manager directory with ODIN for Windows or FastBoot on Windows via a good-quality USB cable.
7. ...
8. ...
I think that is it... I may have forgotten something. Please advise if something needs to be fixed or corrected. My Media Centre was already unlocked, so I did not have to unlock and flash the Bootloader.
9. Install free TWRP on your device, and choose to backup any partitions, should you wish to restore them later. Set an alarm to backup your device every few months! What are you prepared to lose if your device was lost/squashed/washed/crunched et al.???
Say thank you and donate to the amazing and all powerful Magisk developer 'TopJohnWu' and team!
Sweet! :fingers-crossed:

[RECOVERY][UNOFFICIAL][ROOT] TWRP for Galaxy A70

Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
[I]#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/[/I]
I’d recommend to read everything in this post, if you care about your expensive phone.
Let’s start with the installation process
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
If you already installed a previous version of TWRP, start with step 4.
If you already have TWRP installed and just want to root, start with step 5.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Now you need to overwrite vbmeta partition, so you can flash third party partitions. Download vbmeta.tar then go into download mode on your device. Put vbmeta.tar to AP in Odin, click start. This should finish pretty quickly, so pay attention when your device reboots, because you need to boot into recovery (Hold power and volume up after the screen turns black). When booted into recovery, wipe your data and reboot normally into system. Now you can setup your phone as usual and make sure oem unlocking is still greyed out and enabled!
Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
(Optional) You might have lost root access by flash TWRP if you followed this standard guide for rooting. If you did lose it and want to gain root access again (you can also root your device with this method, even when you never rooted your device), download the latest Magisk Manager from the canary channel and install the apk to your phone.
If you are on stock:
Push the recovery.img file you just download for TWRP to your phone. Open Magisk Manager and hit install and patch a file. Select recovery.img and Magisk should start the patching process. Once Magisk is done, boot into TWRP. Backup your boot partition first and afterwards go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
If you are on an AOSP based rom:
Reboot to TWRP. Create a backup with boot partition. Reboot back to system, then open Magisk and hit install and patch a file. Locate the TWRP backup folder and look up your backup you just created. Select boot.emmc.win for patching. Once Magisk is done, reboot back to TWRP. Go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
So that was the easy part. The hard part is to completely read these following points!
Encryption/Decryption
Decryption works on this TWRP release, but only partially. That means you have to open the Settings Application first on your phone and disable a feature called strong protection. You can find it in Settings->Biometrics and security>Other security settings. It doesn’t matter when you disable it. Flash TWRP first and disable it, fine. Disable it and flash TWRP afterwards, fine. Never disable it, also fine, TWRP just fails to decrypt your data, but won’t do any harm. When this feature gets turned off, the device will generate a key which doesn't require any authentication for decryption, currently only this allows TWRP to decrypt the data partition successfully. This only applies to stock roms though, if you are using an AOSP based rom, then you don't have to do any of this.
Disabling decryption
Disabling decryption will create many problems. First TWRP will refuse to unmount system partition and thus you might run into problems flashing various zips. So I advise you to not disable decryption. If you still want to disable it you have to open terminal in TWRP and type in "stop servicemanager" everytime you want to unmount the system partition.
Backup and Restore
Because of encryption it's more complicated to backup your data partition.
If you want to backup data you have to make sure TWRP successfully decrypted your internal storage, otherwise you will run into problems backing up.
Restoring is even more complicated. Every time you set up a rom, new crypto keys will be generated and you can't backup these. That means if you want to restore data you have to restore the whole rom first excluding data. Format data partition completely, boot it up, then go back to TWRP and restore data. You will lose your internal storage, so I'd recommend you move important stuff to external storage.
Developers specific details
Sources
https://github.com/Grarak/android_device_samsung_a70q-twrp
https://github.com/Grarak/android_device_samsung_a70q
https://github.com/Grarak/android_bootable_recovery-1
Recovery image size
For some reason the ramdisk has a size limit, so I used LZMA compression to get its size down as much as possible.
During kernel compilation you will run into a DTC error. Apparently Samsung didn’t bother to update their DTC source in the kernel and you have to use their precompiled binary. I edited my kernel sources to automatically use their dtc binary.
Credits
Device tree of Redmi Note 7 Pro (https://github.com/TeamWin/android_device_xiaomi_violet). Helped a lot!
Topjohnwu for the detailed installation guide (https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
TWRP Galaxy S10 thread for describing System-as-root pretty well
(https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
Downloads
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases (Also changelog)
Note The download is a zip file, unpack it and you will get the recovery image. To flash it in Odin pack it as tar with 7zip or a compression tool of your liking.

reserved

nice work, I'll buy the phone in this 2 days to start some works.

Thanks bro ?
Screenshot please

thanks alot ! development can start on this phone ! (i confirm twrp work)

BK☑️ said:
thanks alot ! development can start on this phone ! (i confirm twrp work)
Click to expand...
Click to collapse
Which version do you have?

devilhunter47 said:
Which version do you have?
Click to expand...
Click to collapse
TWRP version is 3.3.1
actual firmware is A705FNXXU3ASG6_A705FNOXM3ASG6_BTU (july security patch) (United kingdom)
prev. firmware was A705FNXXU1ASE4_A705FNOXM1ASE4_XEF (may security patch) (France)
edit 1 : the ui freeze completly when phone is booted up , had to flash all back
i'm going to flash A705FNXXU1ASD1_A705FNOXM1ASD1_BTU (april security patch) (United kingdom) and see if it boot correctly...
edit 2 : cant flash previous firmware due to 'security reasons' ,i flashed back stock recovery, it doesnt freeze anymore, i guess we will have to wait for a custom kernel

cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?

MTP
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
MTP doesnt work in this build
edit: it work in this build thanks
---------- Post added at 09:38 PM ---------- Previous post was at 09:30 PM ----------
kristiansja said:
cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?
Click to expand...
Click to collapse
i dont think this build is made for treble roms, so probably not

BK said:
MTP doesnt work in this build
Click to expand...
Click to collapse
Uploaded the wrong version. Fixed

Grarak said:
Uploaded the wrong version. Fixed
Click to expand...
Click to collapse
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
BK said:
lemme check
Click to expand...
Click to collapse
edit : it work now thanks!

Thanks dev! Astonished at the progress you've made despite Sammy's carelessness

BK☑️ said:
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
edit : it work now thanks!
Click to expand...
Click to collapse
With July security patch?

Okay, so can anybody else see if system or system images backup crashes TWRP?

FriendlyNeighborhoodShane said:
Okay, so can anybody else see if system or system images backup crashes TWRP?
Click to expand...
Click to collapse
yep , i tried backups yesterday but twrp crash when backing up system.img
---------- Post added at 09:04 AM ---------- Previous post was at 09:01 AM ----------
devilhunter47 said:
With July security patch?
Click to expand...
Click to collapse
i was refering to MTP , the link been fixed, MTP work now , but phone crash after boot up , or just wont boot at all, i were also stuck in prenormal RMM, thats why it wouldnt boot

Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse

Kernel source A70Q
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?

BK said:
Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse
Seems to be a kernel problem. Probably have to wait for Samsung to update their sources.
BK said:
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?
Click to expand...
Click to collapse
No
Click to expand...
Click to collapse

Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i contacted the guys from Samsung Opensource Center for kernel and platform source release, ill see what they say...

How to install TWRP can anyone tell step by step....