I just upgraded my phone from BTJ4 to DUF9 and everything seems to be correct except when I try to re-install Magisk to get root again .. after patching the boot.img.lz4 file(via boot.tar) and installing it via Odin AP the phone just enter a bootloop with the black screen and Samsung logo on it.
I've tried everything I can come up with but I get nowhere.. I've tried Magisk v22 and v23 - same result, tried installing with BL+CP+CSC/BL+CP+CSC with vbmeta_disable in USER and the patched magisk boot image in AP .. still no luck.
Magisk seem happy patching both with v22 and v23 so that seems correkt. The file grows from ~20k as boot.tar to ~60k as magisk_patched tar - which I guess is ok..
Would appreciate any help in getting this to work.
hochocnua said:
New version for SM-G985F with region/firmware DBT/G985FXXU6DUB5
Guide firmwares update and file here
Downloads for : Samsung Galaxy S20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Thanks @ianmacd and @afaneh92 for help and guide
1. Select the BL, AP, CP and HOME_CSC files (save data)
** don't run the firmware yet
2. Download Ian's latest TWRP (twrp-z3s-3.5.0_10-A11_x_ianmacd.img) containing TWRP + patched vbmeta.img into USERDATA slot in Odin.
twrp-z3s-3.5.0_10-A11_6+vbmeta_DUB5.tar | by LEAKs Việt Nam for Galaxy S20
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
3. Uncheck the automatic reboot option in Odin
4. run the flashing
5. When the firmware is finished (leave USB connected !!!), hold the Vol Down + Power buttons, and then, as soon as the screen turns black, hold the Vol Up + Power buttons to boot into recovery
*, keep in mind that the first time you boot into recovery, it initializes and then reboots, so just keep the Vol Up + Power buttons pressed for longer than
6. TWRP - Multi-Disabler Firmware
7. Reboot TWRP - Flash Magisk (stable)
8. Flash Fix_warning_up_param_S20 +
9. RESTART.
Click to expand...
Click to collapse
You have to use this method.
Try using canary version of magisk.
Hmm chieco’s post explains pretty much everything
Tried Canary build of Magisk - didn't help.
Installed TWRP according to above .. didn't work at all. Now the phone is completely dead, only thing that boots i TWRP Recovery.
Correction - without flashing anything at all with TWRP I can actually boot into the phone ..
Correction 2 - when I flash the multidisabler-samsung-3.1.zip it stops the phone from booting.
Correction 3 - so after finally trying just about everything I can come up with it seems as when anything at all touches the boot or system partitions it stops the phone from booting normally.
If I just install the rom with twrp+vbmeta everything works as it should. If I then flash anything at all, doesn't matter what, it stops working. If I flash a magisk patched image - it stops booting.
So.. now I'm stuck.. I have no more ideas.
I even installed the previous release DUE4 with the same result.
I tried patching the complete AP file with magisk - same result.. phone refuses to boot normally.
If I do the Magisk patch file patching before doing the first system boot after upgrading it does the optimize apps thingie but then after rebooting it stops with a bootloop. And by the way under all this TWRP gets replaced with the default Android recovery .. no matter what I do - the internal SD card is no longer encrypted tho so I guess the multidisabler has done its thing.
Only thing I have NOT tried yet is a complete factory reset.. but I don't know if that would make any difference ?
So ended up with a full wipe and installing BeyondROM .. now the phone is rooted and booting with twrp functioning.
O well.. the fun begins restoring everything again..
Related
Hello hello,
this will be my "live" thread of bringing AICP 13.1 to my xperia z1c, I found some Guide's that I will follow and I will share with you all the links and knowledge I gained as a newbie that I used to understand and fix my problems on the way.
Maybe this will help you, too.
Main Tutorial: LINK
Target of all this: LINK
My Device:
Sony XPERIA Z1C, 14.6.A.1.236 , Lollipop 5.1.1
My best hint: read carefully, take your time to understand what you're trying to do and do your own research!
Hopefully you will get a aicp custom rom out of it.
_____________________________________________
_____________________________________________
General information: Android 5.1.1 cannot be rooted due to its high security standards, therefore we will downgrade to a lower security stock rom and create root access there. Root access will be needed as well as an unlocked bootloader to install real recovery (TWRP) which is the tool to flash custom roms like aicp. But the aicp custom rom will not have a good working camera, don't ask me why, but the camera seems to be a really difficult thing from the point of developer's view, let's accept this. Aside of that disadvantage, this custom rom is a very nice software and it makes my z1c kind of new. I don't use my camera anyway often at all.
During all this flashing thing I had a very big ??? while implementing real recovery. I was able to flash the .236.ftf but not the openbootloader.ftf as described in section 5 in the main tutorial. The result was twrp boot failed.
Error description:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
boot stock rom works
My solution:
I restarted from scratch and finally with the kind of messed up secquenceI got it:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
flash openbootloader works
flash twrp works
boot twrp works
UPDATE 06.12.2018 as a solution for REAL RECOVERY with working camera <<< RECOMMENDED
0. boot into rom works
1. flash openbootloader works
2. boot into rom works
3. flash .236.ftf works
4. boot into rom & check camera works
3. flash twrp ( business as usal ) works
4. boot twrp ( First boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
5. full wipe, flash aicp-rom, flash gapps, flash magisk-root, boot system works
6. enjoy Oreo 8.1 & camera check !!! works !!!
This routine worked straight forward for me where I started from scratch with my second device.
Flashing aicp was pretty easy, good to know for flashing the rom was full wipe = advanced wipe and select everything except of micro sd
To complete my aicp 13.1 Oreo 8.1 device the camera problem has to be fixed ( Saving the taken picture fails, display goes into freeze, no chance to solve this with camera mods, camera apps )
But @lm089 gave me the right hint, and finally this was my solution! Thanks again @lm089!!
Have fun with your new >> SONY XPERIA Z1 COMPACT <<
How to update TWRP
1. Turn Off your device
2. Start device in fastboot mode by connecting via usb cable to your pc and press Vol- until blue led tuns on
3. use fastboot flash recovery twrp.img to flash it
4. boot twrp ( This first boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
How to update to aicp 14.0 pie 9.0
starting with the running and latest aicp 13.1 oreo 8.1 rom above I just followed the Instructions here. As a specialty I had to install the Magisk Manager App manually into the rom to get root. Downloading supersu.apk from www.supersuroot.org works fine as well.
Your fastboot connection doesnt work for some reason though u had this workin fine in the past? maybe u had a windows update. install your drivers again.
>> LETS KEEP THIS DEVICE ALIVE <<
_____________________________________________
_____________________________________________
More helpful links that I used:
Debug apps by creating logs
what is adb? an xda tutorial
ADB working Download Link and ADB Article on xda
xda flashtool error during setup: click
[NOOBIE] Basic adb commands and device partition overview
Latest TWRP 3.2.3-0 for z1c
root solution using flash tool
Restore DRM functionality after UB
If TA Backup dry restoration restoration fails: Solution and Download *.dll
Boot into recovery or fastboot mode
How to install TWRP
Magisk beats superSU
How to Install Custom ROM using TWRP for Android!
change boot animations
[TUTORIAL] Design Your Own Bootanimation
Backup & Restore Your ROM With TWRP
Terminology: odex and deodex
If the camera goes into freeze or saving the picture fails: This was my solution! /// But you better go straight with the steps of my update 06.12.2018, field tested!
THANKS A LOT TO @colaigor for his [BEGINNERS GUIDE]
Ok. So i dont have much time now but i can give some short directions.
1. Get unlock codes from sony for bootloader unlock
2. Instal adb and fastboot at your system(PC)
3. Instal z1c drivers
4. Instal flashtool
5. Unlock bootloader,root,flash recovery(search forum for "real recovery" ),flash root solution
6. Flash wanted rom,gaps
P.P. On second thought u dont need flashtool. All can be done with adb and fastboot commands from terminal
There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?
derjango said:
There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?
Click to expand...
Click to collapse
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.
Ok thank you :good:
flashtool log of openbootloader.ftf failed:
01/015/2018 13:15:58 - INFO - Device connected in flash mode
01/017/2018 13:17:19 - INFO - Selected Bundle for Sony Xperia Z1 Compact(D5503). FW release : 1. Customization : openbootloader
01/017/2018 13:17:19 - INFO - Preparing files for flashing
01/017/2018 13:17:19 - INFO - Please connect your device into flashmode.
01/017/2018 13:17:19 - INFO - Using Gordon gate drivers version 3.1.0.0
01/017/2018 13:17:20 - INFO - Opening device for R/W
01/017/2018 13:17:20 - INFO - Device ready for R/W.
01/017/2018 13:17:20 - INFO - Reading device information
Click to expand...
Click to collapse
solved, I skipped step 5.2, flashing the .236.ftf in advance
but how can I start TWRP?
doesnt work with POWER + Vol-, vibrate & release power
I tried to flash the following recovery solution using this command:
smartphone in fastboot mode (blue LED enabled)
fastboot flash recovery recovery.img
TWRP from step 5.1 of the GUIDE
TWRP 3.0.2
My formerly flashed .236.ftf rom works fine, but I cant start TWRP the device goes directly to my rom
zlata said:
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.
Click to expand...
Click to collapse
Thats where I'm stuck right now, any ideas how to fix?
okay got it, basically i do not know what the problem is but:
after BLU
flash .236 :good:
flash openbootloader
flash twrp :good:
--> failed to install openbootloader and probably thus twrp failed
solution: I skipped to flash .236 as recommended by the author of the GUIDE (step 5.2)
flash open bootloader :good:
flash twrp :good:
--> failed to start twrp, though it was installed successfully
flash .236 :good:
flash openbootloader (failed again, but it's already on the device and I guess I could have skipped this here)
flash twrp :good:
first boot of twrp is successful :good:
And basically the author explained it in his text, FIRST INSTALL OPEN BOOTLOADER BEFORE WRITING STH TO RECOVERY PARTITION
I think you should use Aicp 14 pie instead of 13.1 Oreo
I feel Aicp 14 PIE is very stable and flash port camera stock this link https://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/port-stock-camera-nougat-roms- t3628791
Nice thread, thank you! Wish I had that when I started rooting and flashing
@lm089 Haha it's quite some work to get into it, right? I just saw that we are running on the same device & custom rom, how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj
derjango said:
how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj
Click to expand...
Click to collapse
Had this situation twice with 2 different oreo ROMs. Both times I solved it following a rather strange sounding suggestion I found on the AICP 13.1 discussion thread. The basic idea is to go back to a stock Sony ROM. Boot into it and make sure the camera is working which for me was the case both times. Then - if necessary - re-root your phone (on first occasion I flashed a pre-rooted .236 version but that caused some extra trouble so next time I decided to flash an unrooted version). And from then on it's the standard way as you described it in your OP.
Good luck!
Okay, thanks a lot for your hint! Unfortunately the camera mod didn't fix the problem, my android-task for this evening is defined:
AICP 13.1 Oreo 8.1 on z1c, root, ulb, magisk 17.1
1. backup my system (done)
2.0 flash stock rom lollipop 5.1.1 (14.6.A.1.236.ftf) with flashtool via usb (done),booting the os for the first time takes quite long (~10m), check camera in the os (done)
interesting fact: recovery is deleted by flashing the rom via flashtool - I thought I can go the lazy way and skip the step of installing twrp again into recovery
2.1 okay, let's do it: install twrp (done) and boot into twrp, NOT into ROM!! (done) (Vol- & Power, wait for vibration & release Power but keep Vol- until TWRP starts up)
3. flash aicp 13.1 following this (full wipe as an advanced wipe: select all EXCLUDING THE SD STORAGE)
Again here, I recognized the first boot of the rom takes quite longer.
4. check camera (done)
!!!! IT WORKS !!!!
(I did it two times)
alright, lets start flashing my second device - now I know how to do it
Thanks guys!!
derjango said:
!!!! IT WORKS !!!![/SIZE]
Click to expand...
Click to collapse
Weird, isn't it?
lm089 said:
Weird, isn't it?
Click to expand...
Click to collapse
Totally But hey, it's a solution
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too
derjango said:
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too
Click to expand...
Click to collapse
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?
lm089 said:
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?
Click to expand...
Click to collapse
Yes, its used as an external storage
derjango said:
Yes, its used as an external storage
Click to expand...
Click to collapse
ok, that's something different; adoptable storage means that your SD or part of it is setup to extend internal storage. If you can access all of your SD from TWRP then it is indeed formatted a external storage.
1) How to unlock bootloader:
https://developer.sony.com/develop/...ed/unlock-bootloader/how-to-unlock-bootloader
2) Download Platform-tools (adb & fastboot) r.26.0.2 as latests version does not work (or just for me):
https://xiaomifirmware.com/downloads/download-platform-tools-adb-fastboot-r-26-0-0/
3) Download TWRP 3.2.3-0 https://androidfilehost.com/?fid=11410963190603854057 and place file in Platform Tools folder on PC
4) Restart in fastboot mode and flash revovery:
fastboot flash recovery Z1C_twrp_3.2.3-0.img
fastboot reboot
5.1) Download AICP Oreo 8.1 http://dwnld.aicp-rom.com/device/amami/WEEKLY/aicp_amami_o-13.1-WEEKLY-20181204.zip and place file in Platform Tools folder on PC
5.2) Download Gapps Pico https://opengapps.org/?download=false&arch=arm&api=8.1&variant=pico and place file in Platform Tools folder on PC
5.3) Download stable Magisk 17.1 https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip place file in Platform Tools folder on PC
6.1) Load TWRP. Advance>ADB Sideload (for Oreo)
adb sideload aicp_amami_o-13.1-WEEKLY-20181204.zip
(do not restart)
6.2) Repeat Advance>ADB Sideload (for Gapps)
adb sideload open_gapps-arm-8.1-pico-2018XXXX.zip
(do not restart)
6.3) Repeat Advance>ADB Sideload (for Magisk)
adb sideload Magisk-v17.1.zip
(restart)
After flashing this there is no need to press that key combo (VOL up key + Power + Bixby) to boot into Magisk mode. Just after flashing this image your S10+ will automatically boot up in the Magisk mode. And that key combo (VOL up key + Power + Bixby) will be used to boot your phone directly into recovery mode.
Download : PrePatched TWRP S10+http://www.mediafire.com/file/uq378oaeb6s80hc/Prepatched_Twrp_S10%2B.zip/file
DISCLAIMER : FLASH AT YOUR OWN RISK AND I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE.
IF MY POST IS USEFUL FOR YOU THEN KINDLY PRESS THE THANKS BUTTON
Special Thanks To : All credit goes to @ianmacd For his amazing Work for Twrp and Latest unofficial magisk for S10 family & TWRP Team &
@topjohnwu for his work for Magisk
Installation Instructions for the Rooted Users : Before Installing Kindly Make a Backup Of Your Phone and Internal storage
1. Requires Root : Download The Image File From The Above Download Link. Place It In The Root Of Your /sdcard folder .
2. Run The Following Commands Via Adb Shell
3. After Installation Do Wipe Your Internal storage and Do Not Factory Reset Your Phone Otherwise It Will Cause BOOTLOOP
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13d60000.ufs/by-name/recovery
Click to expand...
Click to collapse
S10+ Exynos or Snapdragon ? or work for both ?
for s10 + exynos version
Just 3 things i wanna ask.
1. But you didnt mention twrp version?
2. Even if we already are on twrp' latest version we need to wipe because its prepatched?
3. We shouldnt ever factory reset or just after first installation? But we can factory reset from settings?
1. Latest Twrp 3.3.1-7
2. if you have a twrp installed then kindly do not flash it.
3. Kindly make a backup from twrp recovery before making a factory reset in case any thing goes wrong
Sorry for such a rudimentary question but are the adb commands done individually after "su" or is that one command line too long to fit in the box? Sorry, I've just been fighting with getting twrp on my phone since last night. Root works fine but after flashing patched img file I can never get it to go into twrp. Always goes to stock recovery even though flash is successful. I originally thought I was messing up the key combo but I have my suspicions. Any help would be greatly appreciated. Thanks
jtford said:
Sorry for such a rudimentary question but are the adb commands done individually after "su" or is that one command line too long to fit in the box? Sorry, I've just been fighting with getting twrp on my phone since last night. Root works fine but after flashing patched img file I can never get it to go into twrp. Always goes to stock recovery even though flash is successful. I originally thought I was messing up the key combo but I have my suspicions. Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
UPDATE××Got TWRP to boot the first time. First time system booted fine but I lost root. Did a fresh root per magisk install guide and reflashed twrp.img in root shell. Got twrp to boot again but it continues to boot loop. I only wiped internal with no factory reset. I know it's probably something I'm doing. Any suggestions?
jtford said:
UPDATE××Got TWRP to boot the first time. First time system booted fine but I lost root. Did a fresh root per magisk install guide and reflashed twrp.img in root shell. Got twrp to boot again but it continues to boot loop. I only wiped internal with no factory reset. I know it's probably something I'm doing. Any suggestions?
Click to expand...
Click to collapse
It seems magisk not installed properly. Download latest firmware from Carotix folder Here it have prepatched recovery prepatched ap you need not to do anything you need to reflash recovery n system ...use odin flash patched ap cp bl and use HOME_CSC (you will not use any data apps or anything) Just flash using odin everything will work fine.
also download multidisabler from ian's multidisabler thread HERE put it in phone as need to flash after boot into Twrp!
instructions copied from Carotix thread
Download 4 files from OTA/ODIN FILES then follow this guide:
and put the last Multidisabler in your phone
1- Turn off the device and put it in download mode with the bixby / vol down button and inserting the cable to the PC at this point open Odin remove the check mark from autoreboot
2- Load the AP .tar file downloaded from OTA together with the BL the CP and the HOME_CSC .... if you put the CSC you lose all the data
3- Start the flash and wait
4- At the end you disconnect the phone from the cable and with the power / vol down keys force the switch off as soon as the screen goes black press vol + / bixby / power to go in recovery and don't leave the keys until you see the twrp screen, continue to keep the 3 keys pressed and wait for the recovery to start again
5- Flash the multidisabler then from the main screen choose recovery reboot to boot rooted/magisk system.
comsite said:
It seems magisk not installed properly. Download latest firmware from Carotix folder Here it have prepatched recovery prepatched ap you need not to do anything you need to reflash recovery n system ...use odin flash patched ap cp bl and use HOME_CSC (you will not use any data apps or anything) Just flash using odin everything will work fine.
also download multidisabler from ian's multidisabler thread HERE put it in phone as need to flash after boot into Twrp!
instructions copied from Carotix thread
Download 4 files from OTA/ODIN FILES then follow this guide:
and put the last Multidisabler in your phone
1- Turn off the device and put it in download mode with the bixby / vol down button and inserting the cable to the PC at this point open Odin remove the check mark from autoreboot
2- Load the AP .tar file downloaded from OTA together with the BL the CP and the HOME_CSC .... if you put the CSC you lose all the data
3- Start the flash and wait
4- At the end you disconnect the phone from the cable and with the power / vol down keys force the switch off as soon as the screen goes black press vol + / bixby / power to go in recovery and don't leave the keys until you see the twrp screen, continue to keep the 3 keys pressed and wait for the recovery to start again
5- Flash the multidisabler then from the main screen choose recovery reboot to boot rooted/magisk system.
Click to expand...
Click to collapse
Thanks for your help. I had to do it a little unconventional to get it working. None of the prepatched recoveries that are included in all these firmware downloads would work for me using Odin. Only flashing this twrp.img in a root shell would work. I finally just flashed Beyond rom zip after getting into twrp along with the disabler zip. Boots into rooted system with no problems and I can boot into twrp with no problems as well. Oh yea, I flashed Beyond over ASG8 also. Not sure why I could never get ASH6 to work.
[RECOVERY] TWRP 3.3.1 Changelog
v3.3.1-9_ianmacd for G97[035]F [inc. ASH6 kernel (which also works with ASH1 firmware)] (2019-09-17)
Restore working MTP functionality to TWRP. With thanks to bigbiff for the reference and to Geiti for his commit embodying the same fix.
v3.3.1-8_ianmacd for G97[035]F [inc. ASH6 kernel (which also works with ASH1 firmware)] (2019-09-06)
Kernel rebased on Samsung's ASH6 source code.
[System-as-root] MultidisablerChange log
v1.6 (2019-09-18)
Add support for more variants of A50: A505([YG]N|G).
Fix A205G detection.
Hello kkrraazzyy,
can you please explain how to install your twrp.
I already habe twrp installed. an this rom. --> https://forum.xda-developers.com/s10-plus/development/rom-carhdrom-1-t3938987
But a want to install your twrp to boot always with Magisk without to press any key.
I need your help please.
Any proper YouTube guide video for these things, as flashing/rooting became so complicated with so many steps.... Thank you!
So from my understanding this is the first and only way to have the phno boot into the patched recovery automatically without needing top physically press the button combo? Or have I missed something Was just expecting there to have been a lot more attention that's all.
This has actually what has been one of the main reasons holding me back from rooting as it reminds me back in the day of tethered and untethered jailbreaks for iPhones.
Except that this is just a inconvenience while tethered would make the phone practically unusable.
Is there an app i can use to backup and restore my kik chats? I got a new phone, a Samsung Galaxy 10+ and want to tramsfer my kik chats and save data for Digimon Heroes! to my new galaxy 10+ i dont have root on either phones is there a app (apk) or one i can downlod on my laptop to make the backup of them so i can bring them over. Please i only have a dew days left to transfer my number over and have my old phone shut dwn by my previous provider. I need to do it on the next 2 days.
qaz015393 said:
Is there an app i can use to backup and restore my kik chats? I got a new phone, a Samsung Galaxy 10+ and want to tramsfer my kik chats and save data for Digimon Heroes! to my new galaxy 10+ i dont have root on either phones is there a app (apk) or one i can downlod on my laptop to make the backup of them so i can bring them over. Please i only have a dew days left to transfer my number over and have my old phone shut dwn by my previous provider. I need to do it on the next 2 days.
Click to expand...
Click to collapse
Use Smart Switch by Samsung, it includes the possibility of transferring all your data and settings using a USB cable. I transferred everything from my old phone to this one (S10+ SM-G975F). I don't know if it will work on non-Samsung devices, but it's worth a try.
I have android 10 on my s10+, will this twrp work with android q?
possible to boot without root permissions too?
:good:
Hi @kkrraazzyy , could you show us how you did it?
because @ianmacd https://forum.xda-developers.com/ga...covery-twrp-3-3-0-galaxy-s10-exynos-t3924856/
latest version does not seem to provide this awesome function.
When i try to get in to magisk from recovery, it turns on but after like 10 seconds it turns off. i can get my phone to boot in to nonroot system. this has been issue for half a year.
using android 9
model: SM-A505FN
magisk manager version: 7.5.1 (267)
magisk version: not sure. i think i have 19 or 20
installed it by patching ap and flashing the patched file with odin
Voutsjude said:
When i try to get in to magisk from recovery, it turns on but after like 10 seconds it turns off. i can get my phone to boot in to nonroot system. this has been issue for half a year.
using android 9
model: SM-A505FN
magisk manager version: 7.5.1 (267)
magisk version: not sure. i think i have 19 or 20
installed it by patching ap and flashing the patched file with odin
Click to expand...
Click to collapse
android 9 isnt the best for modding like this, works alot better on android 10, if you read the install instructions [https://topjohnwu.github.io/Magisk/install.html];
After installing Magisk in recovery:
(Powering up normally) → (System with NO Magisk)
(power + vol up) → (Splash screen / bootlock warmning) → (Release all buttons) → (System with Magisk)
(Power + vol up) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
I will note that this suffers from random bootloops and things. just update
I used this after update - https://forum.xda-developers.com/galaxy-a50/how-to/guide-samsung-galaxy-a50-btc4-firmware-t4071817
just remember to unlock the boot loader again after flashing 10
can you give me the instructions for updating to android 10 with magisk installed in android 9
Voutsjude said:
can you give me the instructions for updating to android 10 with magisk installed in android 9
Click to expand...
Click to collapse
Just a fresh stock install is the best way to go, updating via ota wont work because of magisk
1) Find you firmware [https://www.sammobile.com/firmwares/search/a505/]
-Clicking on your model will present you with firmware downloads
-Find yours and download it [country and network or just the country should work]
-Extract it somewhere.
2) Get Odin [https://dl2018.sammobile.com/Odin3-v3.14.4.zip]
-Extract it somewhere
-Load it
-Add the files from the firmware folder into the correct sections (i.e/ ap, bl, csc - I cant remeber them all of the top of my head)
3) Get into download mode
-Power off device or if its boot looping Press and hold power + vol down to force a restart
-Press and hold both vol buttons and connect it to your computer with usb
-Odin should now say added in the log
4) press start and wait
-Its easier to set up your phone with no account because your going to wipe it again anyway,
-unlock bootloader
5) Flashing the things
-When selecting the downloads of twrp make sure you get the magisk patched one.
-Start from step 5, as you have just flashed stock. [https://forum.xda-developers.com/galaxy-a50/how-to/guide-samsung-galaxy-a50-btc4-firmware-t4071817]
-When flashing twrp make sure auto reboot is OFF is odin options
notes:
I've updated to magisk 20.4 with no issues, xposed seems to trip the saftey net tho.
i cant figure out which country i should pick.
my build number is A505FNXXS2ASJ1
and csc: A505FNOXM2ASH2
and im from finland but i remember that i took like baltic (SEB) firmware when i installed magisk but not sure which one to pick now
idk why there are not any actually firmwares for finnland...
im gonna say try this one; https://www.sammobile.com/samsung/galaxy-a50/firmware/SM-A505FN/SEB/download/A505FNXXS4BTCA/336036/ ??
I really dont know tho
got it working. updated to android 10 with twrp and magisk installed. thank you
I am not responsible for any damage to your device, when you root you lose the Warranty
This guide collects A107F development info, but with the files ported to the A107M.
Thanks to the Galaxy A10s Development team for the original files.
You need to be on Android 10, if you are on android 11, there are tutorials to downgrade.
[BootLoader Unlock]
- Backup all your media, this process will delete your internal media including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode (Turn off, press VOL- & VOL+ and connect the USB)
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Perfect! Your bootloader now accepts unofficial images in download mode.
[Twrp Install]
At this point, you will need to install Odin on your PC.
Bootloader unlocked is OBLIGATORY.
On your MicroSD, put the "A10s-encryption-disabler.zip" file.
Boot to download mode, load "VBMeta" file in AP and "TWRP Ported to A107M" file in BL
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- With the USB connected, and after the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP Recovery
NOTE: TWRP on this phone is not perfect, after booting to it, the screen will remain black after the Samsung logo disappears, simply wait 10 seconds and press the power button 2 times to have acces to it.
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the "A10s-encryption-disabler.zip" with TWRP. This is done to avoid future bootloops.
- Optional, flash "Magisk.zip" if you want to keep on Stock ROM with root.
- After doing this, boot back to system and you are done
- Wait patiently for the device to boot for the first time
[Custom ROMs Install]
Bootloader unlocked and TWRP isntalled are OBLIGATORY.
Most of the GSI ROMs of this forum works fine on this device.
Only download a64 ROMs, do not confuse with ARM64.
On your MicroSD, put the ROM image.
- Boot to TWRP
- Go to Wipe > Advanced
- Wipe ONLY the System partition
- Go to Install
- At the bottom, select option "Install Image"
- Search for your GSI. It should be something that ends in .img. If it ends in .xz instead, you need to extract the image first
- Optional, if you want Root, flash the "Magisk.zip" file
- Go to recovery main menu
- Go to Reboot
- Reboot to Recovery
- After that, go to Wipe and perform a Factory Reset
- Reboot to System and enjoy!
[Downloads]
>Everything you will need<
I had a problem in Odin an "RQT-CLOSE" error occurred
Lukas203 said:
I had a problem in Odin an "RQT-CLOSE" error occurred
Click to expand...
Click to collapse
I GOT THE SAME THING WHATS HAPPENNING?
Worked perfectly on a107m with binary 6
Alexander_SlowD said:
Worked perfectly on a107m with binary 6
Click to expand...
Click to collapse
If it worked for you, what procedure did you follow? What rom did you use for bit 6? what tools did you use?
It worked for me at first time I see TWRP menu but I didnt followed the instructions correctly , I've tried to do it by myself after that , then I got a unnoficial bootloader error and RQT_CLOSE error when trying to do the Odin process again .
Any working solution are welcome and I will be thankfully , please !
Luciannus said:
It worked for me at first time I see TWRP menu but I didnt followed the instructions correctly , I've tried to do it by myself after that , then I got a unnoficial bootloader error and RQT_CLOSE error when trying to do the Odin process again .
Any working solution are welcome and I will be thankfully , please !
Click to expand...
Click to collapse
The TWRP is slready working for me , now I trying the Magisk part , I did this on Android 11 binary 6 trough A107MUBS6CWA3_ZTO firmware ...
Here's the steps on how to fix it, because Samsung's treble implementation is kinda crap.
(note: might not work for everyone, steps must be done correctly)
These steps assumes that you have your phone bootloader unlocked, rooted,flashed with a custom Recovery, and encryption removed.
Method 1 (easy, no need to download large flash files)
- Go to your custom recovery and then wipe
- Flash the boot.img file given below (note: Flash only on A71 4G. I am not responsible if your device bricked because you flashed this img on A71 5G or other devices. EVEN IF IT IS SIMILAR, IT WON'T WORK!)
- Reboot to recovery (important)
- Your device might boot to a stock recovery as of now. Don't panic if it does. Power off then boot to download mode
- Select "reboot to download"
- Use Odin to flash twrp-3.6.2_11-3_afaneh92-a71.tar (AP slot) that is given below.
- When the device reboots, immediately boot into the custom recovery by pressing volume up + power button.
- Flash Multidisabler, file given below
- Flash your GSI of choice (select install image then flash as system image)
- Flash any fix zips that need to be flashed (if there are any)
- Wipe again just to make sure
- Reboot
Bugs: This TWRP build's encryption/decryption not fully working. Make sure your device storage is already decrypted, as formatting data will not decrypt your device storage.
Method 2 (hard, but almost guaranteed will work)
Thank you @Zainullahk1234 for this fix
install Stock ROM (4 files, search on Samfw or Sammobile for the flash firmware for the A71. I recommend to flash the latest binary, as flashing older builds will not work sometimes) boot into the stock rom and then change date to 3 months from now
check for updates, make sure you're connected to the internet for this
boot into download mode
flash twrp 3.6.2 (file given above) and vbmeta tar file
boot into twrp
do format data
flash multidisabler
flash GSI ROM
flash GSI Fixes (if there are any)
do factory reset
reboot
if it boots you into fastboot again, shutdown then reboot to recovery, flash twrp 3.6.2 via Odin and try another factory reset and reboot (In twrp)
Credits: @ShaDisNX255 for the stock boot.img, extracted from RayOS
@afaneh92 for the TWRP recovery.
Thread - https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a71-snapdragon.4350893/
@ianmacd for the multidisabler
TigerLake said:
Here's the steps on how to fix it, because Samsung's treble implementation is kinda crap.
(note: might not work for everyone, steps must be done correctly)
These steps assumes that you have your phone bootloader unlocked, rooted,flashed with a custom Recovery, and encryption removed.
- Go to your custom recovery and then wipe
- Flash the boot.img file given below.
- Reboot to recovery (important)
- Your device might boot to a stock recovery as of now. Don't panic if it does. Power off then boot to download mode
- Select "reboot to download"
- Use Odin to flash twrp-3.6.2_11-3_afaneh92-a71.tar (AP slot) that is given below.
- When the device reboots, immediately boot into the custom recovery by pressing volume up + power button.
- Flash Multidisabler, file given below
- Flash your GSI of choice (select install image then flash as system image)
- Flash any fix zips that need to be flashed (if there are any)
- Wipe again just to make sure
- Reboot
Bugs: This TWRP build's encryption/decryption not fully working. Make sure your device storage is already decrypted, as formatting data will not decrypt your device storage.
Credits: @ShaDisNX255 for the stock boot.img, extracted from RayOS
@afaneh92 for the TWRP recovery.
@ianmacd for the multidisabler
Click to expand...
Click to collapse
It was simple if you linked my twrp thread, and please drop the image and direct link to my host.
afaneh92 said:
It was simple if you linked my twrp thread, and please drop the image and direct link to my host.
Click to expand...
Click to collapse
Okay, I'll link your TWRP thread.
afaneh92 said:
It was simple if you linked my twrp thread, and please drop the image and direct link to my host.
Click to expand...
Click to collapse
Also btw, TWRP 3.7 caused my phone to not boot, so I reflashed twrp 3.6.2 and this build is what I put here.
TigerLake said:
Also btw, TWRP 3.7 caused my phone to not boot, so I reflashed twrp 3.6.2 and this build is what I put here.
Click to expand...
Click to collapse
Thanks, will try to fix it soon