Hi There will be a root release or twrp? Thanks you xda. All is in the title.
Magisk by default should have the ability to root this. Follow the instructions for the Tab S6 and you should be good to go
Hi,
trying to root with Magisk SM-P610 (S6 Lite Exynos) but it failed with :
vbmeta: Error verifying vbmeta image: OK_NOT_SIGNED (3)
vbmeta: VERIFICATION_DISABLED bit is set.
Doing wrong or not yet supported ?
Thanks
Try patching only boot.img
I think the same method for A51 and A71 should work here as well.
1) Download Firmware
2) Flash Using Odin
3) Unzip AP and copy boot.img.lz4 to your computer.
4) If you have LZ4 Decompress Tool use that to convert boot.img.lz4 to boot.img otherwise use ZArchiver. Anyway you need boot.img.
5) Patch boot.img using Magisk Manager Latest One.
6) Copy the patched file and rename it to boot.img and then use 7Zip to convert it into boot.tar.
7) Restart the phone to recovery and then boot to bootloader.
8) Uncheck Auto Reboot option in Odin and then flash boot.tar. Once it's successful then boot into recovery and then Wipe Data and Cache.
9) reboot into system and then use Magisk Manager to check if your device is rooted.
Change img file to .tar first
arjun_m4 said:
I think the same method for A51 and A71 should work here as well.
1) Download Firmware
2) Flash Using Odin
3) Unzip AP and copy boot.img.lz4 to your computer.
4) If you have LZ4 Decompress Tool use that to convert boot.img.lz4 to boot.img otherwise use ZArchiver. Anyway you need boot.img.
5) Patch boot.img using Magisk Manager Latest One.
6) Copy the patched file and rename it to boot.img and then use 7Zip to convert it into boot.tar.
7) Restart the phone to recovery and then boot to bootloader.
8) Uncheck Auto Reboot option in Odin and then flash boot.tar. Once it's successful then boot into recovery and then Wipe Data and Cache.
9) reboot into system and then use Magisk Manager to check if your device is rooted.
Click to expand...
Click to collapse
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
shark2003 said:
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
So it’s working for you finally?
**Snobilik** said:
So it’s working for you finally?
Click to expand...
Click to collapse
yup
---------- Post added at 06:12 PM ---------- Previous post was at 06:06 PM ----------
shark2003 said:
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
All these rooting instructions for the S6 Lite need to be corrected to save people from a headache. Why would people post instructions that are wrong. If they had did the steps themselves they would know and shouldnt post or copy someone elses instructions that are wrong.
shark2003 said:
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
Sorry I think I messed up some steps. I used the same method for new Tab S7
arjun_m4 said:
Sorry I think I messed up some steps. I used the same method for new Tab S7
Click to expand...
Click to collapse
Yeah I tried the AP and wiped out my os quite a few times until I got this right. It wasn't just your post its all over the internet and none of them mention that it has to be done in that order.
shark2003 said:
Change img file to .tar first
After spending countless hours because no one bothered to correct one simple step. The boot.img file needs to be converted to .tar first AND THEN patched with Magisk or this will never work.
.tar first then patch with Magisk and flash with Odin. I wanted to scream when I figured this out after spending hours f**king with this!!
Click to expand...
Click to collapse
I might add, that this is probably a false positive information
Just because I had the same errors over and over, until I stumbled upon another thing: Creating the .tar was my problem. Using an (old) 7-Zip created a boot.tar which gave me "unassigned file" errors. When patching the whole AP, I got vbmeta errors.
So I started from scratch with a fresh Odin flash and transferred the boot.img.lz4 to my phone and worked with ZArchiver which extracted the .img and created the .tar - and this was flashed with Odin without any errors, finally.
Related
Hi,
I wanted to update to OB2 and was kinda in a hurry, so long story short: I screwed up and am now on OB2 without root or TWRP.
Primarily I need root, so if anyone can point me to a guide, that would be much appreciated.... booting TWRP through fastboot doesn't seem to work.
If you have a good guide for also flashing TWRP, that would also be much appreciated, only stuff I found was guides with "patch the boot.img" ... hell, i don't know how to do that
thanks
momsi said:
Hi,
I wanted to update to OB2 and was kinda in a hurry, so long story short: I screwed up and am now on OB2 without root or TWRP.
Primarily I need root, so if anyone can point me to a guide, that would be much appreciated.... booting TWRP through fastboot doesn't seem to work.
If you have a good guide for also flashing TWRP, that would also be much appreciated, only stuff I found was guides with "patch the boot.img" ... hell, i don't know how to do that
thanks
Click to expand...
Click to collapse
Hello, check this out https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
I've seen this post, but how do i patch the boot img of OB2?
or do i do that with the OB1 file ?
momsi said:
I've seen this post, but how do i patch the boot img of OB2?
or do i do that with the OB1 file ?
Click to expand...
Click to collapse
No, with the OB2 file. You can extract it also with the same method and patch it.
the same file?! there is no open beta 2 file ... you can only download the OB1 from oneplus and have to OTA to OB2..
I know how annoying it is when some noob (thats how i feel now) asks for step by step "click this button" guides, but can you please lend me a hand on this
I see .... i miss the old days with the nexus series or the first oneplus phones ... none of all the crap, no million partitions and A and B slots and all that ... just flashing...
momsi said:
the same file?! there is no open beta 2 file ... you can only download the OB1 from oneplus and have to OTA to OB2..
I know how annoying it is when some noob (thats how i feel now) asks for step by step "click this button" guides, but can you please lend me a hand on this
I see .... i miss the old days with the nexus series or the first oneplus phones ... none of all the crap, no million partitions and A and B slots and all that ... just flashing...
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
Know exactly what you mean. I did the same thing. Will break it down more granular.
1) Download the OB2 file
2) Unzip the OB2 zip file.
3) Download program found in (use this tool for it LINK <--- thanks @tidschi)
4) Unzip said program
5) Take payload.bin file and put it in the payload_input folder
6) Run the payload_dumper.exe found in the root payload folder (payload_dumper-win64)
7) Take the boot.img file from the payload_output folder and copy it to your phone
8) Open Magisk Manager on the phone and click INSTALL
9) Click INSTALL again
10) Click Select and Patch a File
11) Choose the boot.img file you copied from your computer (phone will create a magisk_patched.img file in your download folder)
12) Copy magisk_patched.img file from your phone to your computer
13) Fastboot your phone and install the magisk_patched.img file
14) Go back to Magisk Manager. It should now say it is rooted.
15) Go to Modules in Magisk and hit the + sign
16) Find your TWRP Zip file and install it.
You should now be rooted and have TWRP installed on your phone again.
Cheers!
swehes said:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
Know exactly what you mean. I did the same thing. Will break it down more granular.
1) Download the OB2 file
2) Unzip the OB2 zip file.
3) Download program found in (use this tool for it LINK <--- thanks @tidschi)
4) Unzip said program
5) Take payload.bin file and put it in the payload_input folder
6) Run the payload_dumper.exe found in the root payload folder (payload_dumper-win64)
7) Take the boot.img file from the payload_output folder and copy it to your phone
8) Open Magisk Manager on the phone and click INSTALL
9) Click INSTALL again
10) Click Select and Patch a File
11) Choose the boot.img file you copied from your computer (phone will create a magisk_patched.img file in your download folder)
12) Copy magisk_patched.img file from your phone to your computer
13) Fastboot your phone and install the magisk_patched.img file
14) Go back to Magisk Manager. It should now say it is rooted.
15) Go to Modules in Magisk and hit the + sign
16) Find your TWRP Zip file and install it.
You should now be rooted and have TWRP installed on your phone again.
Cheers!
Click to expand...
Click to collapse
I thank you very much, really..... but now I feel even more stupid .... I again fail at the very first step. Which OB2 file? In the thread you linked, i only find the patching tool, no OB2 file, and at the oneplus site you can only download the OB1 file.
momsi said:
I thank you very much, really..... but now I feel even more stupid .... I again fail at the very first step. Which OB2 file? In the thread you linked, i only find the patching tool, no OB2 file, and at the oneplus site you can only download the OB1 file.
Click to expand...
Click to collapse
That's the rom itself, the full OxygenOS zip Open Beta 2: https://forum.xda-developers.com/on...7-repo-oxygen-os-builds-t3937152/post80254958
From there you need to extract the boot.img and patch it as explained before :good:
Well.... that did the trick ....
Thank you very much. :highfive:
magisk_patched image not flashing
swehes said:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
12) Copy magisk_patched.img file from your phone to your computer
13) Fastboot your phone and install the magisk_patched.img file
You should now be rooted and have TWRP installed on your phone again.
Cheers!
Click to expand...
Click to collapse
while flashing magisk_patched.img I am getting this error
C:\Android>fastboot flash boot magisk_patched.img
target reported max download size of 805306368 bytes
sending 'boota' (49232 KB)...
OKAY [ 1.136s]
writing 'boota'...
FAILED (remote: (boota_a) No such partition)
finished. total time: 1.145s
what should I do ?
Update : got the new updated twrp which can be booted from fastboot
swehes said:
https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
Know exactly what you mean. I did the same thing. Will break it down more granular.
1) Download the OB2 file
2) Unzip the OB2 zip file.
3) Download program found in (use this tool for it LINK <--- thanks @tidschi)
4) Unzip said program
5) Take payload.bin file and put it in the payload_input folder
6) Run the payload_dumper.exe found in the root payload folder (payload_dumper-win64)
7) Take the boot.img file from the payload_output folder and copy it to your phone
8) Open Magisk Manager on the phone and click INSTALL
9) Click INSTALL again
10) Click Select and Patch a File
11) Choose the boot.img file you copied from your computer (phone will create a magisk_patched.img file in your download folder)
12) Copy magisk_patched.img file from your phone to your computer
13) Fastboot your phone and install the magisk_patched.img file
14) Go back to Magisk Manager. It should now say it is rooted.
15) Go to Modules in Magisk and hit the + sign
16) Find your TWRP Zip file and install it.
You should now be rooted and have TWRP installed on your phone again.
Cheers!
Click to expand...
Click to collapse
Will this still work even though I am on Stable 10.0.1 OOS?
Sobakel said:
Will this still work even though I am on Stable 10.0.1 OOS?
Click to expand...
Click to collapse
Yes, but you can do it easily with newer methods
Sorry to ask what is perhaps an easy question, but what are those newer methodes?
Sobakel said:
Sorry to ask what is perhaps an easy question, but what are those newer methodes?
Click to expand...
Click to collapse
See here https://forum.xda-developers.com/oneplus-7/how-to/guide-unlock-bootloader-flash-twrp-root-t3954559
Hi All
Noob too the tab scene (paradoxically developing a rom module to "reasonable success" haha)
Found found the time to put a guide together following updating to BTF2 firmware and installing TWRP in one flash.
This has probably been posted before but hopefully its useful nonetheless
Prerequisites
- May security patched TWRP image - its highly advisable to make sure your TWRP and any kernels used match the security patch date of your firmware use This awesome online tool thanks @evdenis - Mentalmuso's TWRP is running perfectly on mydevice patched to may with BTF2 firmware
-VBmeta.img from Mentalmuso's tar
- BL, CP, HOMECSC and Magisk patched AP with the May patched TWRP renamed as "recovery.img" and replacing the stock recovery and the VBmeta.img from Mentalmuso's tar replacing the stock one
- Multidisabler 2.3 linked below thanks @ianmacd
Process
1 - Backup anything you need to keep onto external SD as you will need to format internal storage to get TWRP working.
2 - Reboot to download and open odin - uncheck auto reboot and then load BL, Magisk Patched AP, CP and HOMECSC (from BTF2 firmware)
3 - Flash the files and when done hold vol down and power to exit download and immediately hold power and vol up until in initial TWRP screen (after holding it whilst it reboots you'll end up at the screen where it asks you if you want to allow system modifications) Check the box and swipe right
4 - You'll notice by going into install that your internal storage folders are now nonsense - go to wipe in TWRP then Format data and type yes then enter - your internal storage will be wiped (hence having to backup) but your internal storage will now be usable.
5 - Immediately flash the multidisabler 2.3 zip and then reboot recovery - You are now fully updated and have TWRP installed and working
6 - i have a personal stock debloated rooted base that I use for installing my rom module on - linked here for T865 ONLY - wipe data, system, vendor, cache and dalvik and then flash the base zip (stock rooted based on BTF2 DBT firmware) - FOLLOWED BY MULTIDISABLER ONCE MORE - reboot and set up
Hopeloos ....
Thanks.
It didn"t directly help. But now I know I didn"t do whats needed, for rooting my 865 lol
Any idea where I can find how to root specificaly my tab. Already rooted smartphones but this tablet seems a bit different. Or can you help me?
Downloading and looking at your multidisabler zip, seems you are dutch. So am I
Thanks for reading and hopefully waiting your respos
El
PS: om moedeloos van te wordena
Hi, thank you for the short guide.
Could you post expanded steps please?
I don't want to f' things up.
exocetdj said:
Prerequisites
- May security patched TWRP image - its highly advisable to make sure your TWRP and any kernels used match the security patch date of your firmware use This awesome online tool thanks @evdenis - Mentalmuso's TWRP is running perfectly on mydevice patched to may with BTF2 firmware
Click to expand...
Click to collapse
All clear and done, took 3.4.0-gts6l and patched it to May 2020.
exocetdj said:
-VBmeta.img from Mentalmuso's tar
Click to expand...
Click to collapse
Found that Magisk patched AP also has an empty VBmeta.img inside.
exocetdj said:
- BL, CP, HOMECSC and Magisk patched AP with the May patched TWRP renamed as "recovery.img" and replacing the stock recovery and the VBmeta.img from Mentalmuso's tar replacing the stock one
Click to expand...
Click to collapse
As Magisk on Samsung devices installs into recovery.img instead of boot.img (see https://topjohnwu.github.io/Magisk/install.html#additional-info), won't I kill Magisk if I overwrite the recovery.img inside the Magisk patched tar? Should I first add the recovery to the AP before Magisk patching it?
exocetdj said:
- Multidisabler 2.3 linked below thanks @ianmacd
Process
1 - Backup anything you need to keep onto external SD as you will need to format internal storage to get TWRP working.
2 - Reboot to download and open odin - uncheck auto reboot and then load BL, Magisk Patched AP, CP and HOMECSC (from BTF2 firmware)
3 - Flash the files and when done hold vol down and power to exit download and immediately hold power and vol up until in initial TWRP screen (after holding it whilst it reboots you'll end up at the screen where it asks you if you want to allow system modifications) Check the box and swipe right
4 - You'll notice by going into install that your internal storage folders are now nonsense - go to wipe in TWRP then Format data and type yes then enter - your internal storage will be wiped (hence having to backup) but your internal storage will now be usable.
5 - Immediately flash the multidisabler 2.3 zip and then reboot recovery - You are now fully updated and have TWRP installed and working
Click to expand...
Click to collapse
Should manage to do that
exocetdj said:
6 - i have a personal stock debloated rooted base that I use for installing my rom module on - linked here for T865 ONLY - wipe data, system, vendor, cache and dalvik and then flash the base zip (stock rooted based on BTF2 DBT firmware) - FOLLOWED BY MULTIDISABLER ONCE MORE - reboot and set up
Click to expand...
Click to collapse
If it won't work, I'll give that a try.
Again, thank you very much for this thread.
Regards,
sub
Cool any issues pop into the 420 telegram chat. Im working for next 5 hours but we can help there if you're stuck
Yay, stuck at the Samsung logo (after bootloader warning and "unofficial software" nag).
Followed all steps to the letter.
Created 3 APs:
- Stock magisk patched
- Stock magisk patched with replaced recovery.img
- Unpacked AP, replaced recovery.img with TWRP, repacked, then magisk patched
I managed to boot one variant (can't remember which) into safe mode somehow, but only once.
Trying to restore TWRP backup now.
I hate Samsung
Edit: At least the TWRP restore worked fine and the tablet booted
Edit 2: Played around again. This time flashed full stock BTF2 firmware. Now everything that contains a modded vbmeta fails. Let's see if I can get anything to work again.
Edit 3: Any non original vbmeta now fails to start at all.
I hate Samsung even more.
(partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM recovery
VBMETA T865XXU3BTF2, 31809105R)
subworx said:
Yay, stuck at the Samsung logo (after bootloader warning and "unofficial software" nag).
Followed all steps to the letter.
Created 3 APs:
- Stock magisk patched
- Stock magisk patched with replaced recovery.img
- Unpacked AP, replaced recovery.img with TWRP, repacked, then magisk patched
I managed to boot one variant (can't remember which) into safe mode somehow, but only once.
Trying to restore TWRP backup now.
I hate Samsung
Edit: At least the TWRP restore worked fine and the tablet booted
Edit 2: Played around again. This time flashed full stock BTF2 firmware. Now everything that contains a modded vbmeta fails. Let's see if I can get anything to work again.
Edit 3: Any non original vbmeta now fails to start at all.
I hate Samsung even more.
(partition recovery
Reason recovery: Error verifying vbmeta image: invalid vbmeta header (6)
CUSTOM recovery
VBMETA T865XXU3BTF2, 31809105R)
Click to expand...
Click to collapse
If you get stuck at SAMSUNG screen again, try and force a reboot
Why don't I see a CP file in my firmware file?
All that's in there is :
AP
BL
CSC
HOME CSC
************************
T860 wifi
Do I just leave the CP slot blank?
exocetdj said:
If you get stuck at SAMSUNG screen again, try and force a reboot
Click to expand...
Click to collapse
Ok will do. If I can get myself to try that whole thing again, that is: TWRP backup to external SD alone takes more than 1,5 hours
Thank you.
Edit: Another thing I found: after flashing everything, my internal storage is *not* scrambled. Still formatted it last time around, though, but not sure if that would absolutely be necessary. Think the original rooting instructions on here (cannot find them any more) included installing "Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip" which should remove the need for formatting.
jhill110 said:
Why don't I see a CP file in my firmware file?
All that's in there is :
AP
BL
CSC
HOME CSC
************************
T860 wifi
Do I just leave the CP slot blank?
Click to expand...
Click to collapse
Looks like a broken download. Where did you get that from?
Both T865XXU2BTC7_T865OXM2BTC7_DBT and T865XXU3BTF2_T865OXM3BTF2_DBT contain AP, BL, CP, CSC, HOME_CSC.
Possibly try sammobile, they should have complete ROM archives, although they're slow as hell on non-premium.
Regards,
sub
subworx said:
Looks like a broken download. Where did you get that from?
Both T865XXU2BTC7_T865OXM2BTC7_DBT and T865XXU3BTF2_T865OXM3BTF2_DBT contain AP, BL, CP, CSC, HOME_CSC.
Possibly try sammobile, they should have complete ROM archives, although they're slow as hell on non-premium.
Regards,
sub
Click to expand...
Click to collapse
Well that's interesting... I paid the $$ for faster downloads from Samobile. An hour is far better than 12 or 13. It's where I got the file(s) in the first place.
I downloaded the file again just to be sure and it's the same thing. It works so what the heck.
I'm curious as to what that particular (CP) slot/file is...
Oh btw, I'm T860 wifi.
jhill110 said:
Well
I'm curious as to what that particular (CP) slot/file is...
Oh btw, I'm T860 wifi.
Click to expand...
Click to collapse
CP is related to the Modem. Since your T860 doesn't have a 3G modem chip, you don't need the CP file.
I *think* that's correct anyway.
I followed the instructions here to a T. Except, there is no .img file named Vendor_boot.img in the payload.bin file.
I even tried eliminating that part of the process and just patching the boot.img file, but as you can imagine I am now stuck in Fastboot mode (don't worry I know how to fix that).
Sorry if this Q is repetitive, but how the heck to I root this damn thing with Magisk without the vendor_boot.img?
clarkcant said:
I followed the instructions here to a T. Except, there is no .img file named Vendor_boot.img in the payload.bin file.
I even tried eliminating that part of the process and just patching the boot.img file, but as you can imagine I am now stuck in Fastboot mode (don't worry I know how to fix that).
Sorry if this Q is repetitive, but how the heck to I root this damn thing with Magisk without the vendor_boot.img?
Click to expand...
Click to collapse
[GUIDE] Root and keeping root options
Update 230526: Correct numbering of "B.1.1 Simple" to "B.1.2 Simple", use "OOS 13+" instead of "OOS 13" as OOS 13.1 is now available A. First time rooting This process is common across all options A.1 Flashing Magisk patched boot image There...
forum.xda-developers.com
i've been looking for one everywhere but i cant really find one..
but if someone tells me how to like make a twrp for it (the latin variant), it'd be nice
thank you!
so, are there any news about this?
kalii_ said:
so, are there any news about this?
Click to expand...
Click to collapse
Nobody supports or develops for that variant of the A12. The only time was a custom recovery, that was abandoned and doesn't work anymore.
kalii_ said:
so, are there any news about this?
Click to expand...
Click to collapse
Nevermind... Ask @physwizz for your version.
TheWorldYT said:
Nevermind... Ask @physwizz for your version.
Click to expand...
Click to collapse
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
If it doesn't work I can easily modify it
physwizz said:
[AOSP-11] [OFFICIAL] Samsung SM-A125F TWRP
DISCLAIMER: I WAS NEVER, HAVE NEVER BEEN, AND WILL NEVER BE RESPONSIBLE OF ANY DAMAGES AGAINST YOUR DEVICES BY YOUR OWN MIS-OPERATIONS Install instructions: 1. Download an arbitrary SM-A125F firmware zip package on SamMobile.com, whose Android...
forum.xda-developers.com
If it doesn't work I can easily modify it
Click to expand...
Click to collapse
well, it doesnt work for me sadly, since the A125F model is a little different from the 125m, itll just start rebooting. if you can make a modifed version for it, ill glady test it for you. the firmware that i got is the ZTO A125MUBU3BVG6
Thank you
kalii_ said:
well, it doesnt work for me sadly, since the A125F model is a little different from the 125m, itll just start rebooting. if you can make a modifed version for it, ill glady test it for you. the firmware that i got is the ZTO A125MUBU3BVG6
Thank you
Click to expand...
Click to collapse
Send me your stock recovery.img.lz4
And I'll see what I can do
physwizz said:
Send me your stock recovery.img.lz4
And I'll see what I can do
Click to expand...
Click to collapse
here it is:
recovery.img.lz4
Download recovery.img.lz4 for free from KrakenFiles.com
krakenfiles.com
kalii_ said:
here it is:
recovery.img.lz4
Download recovery.img.lz4 for free from KrakenFiles.com
krakenfiles.com
Click to expand...
Click to collapse
Ok
kalii_ said:
here it is:
recovery.img.lz4
Download recovery.img.lz4 for free from KrakenFiles.com
krakenfiles.com
Click to expand...
Click to collapse
thank you for the response, but unfortunally it soft bricks and won't boot past the boot screen. is there a way i can help to make it work?
hey, i've found the issue, i gave you the wrong file, sorry about that. if you got paypal maybe i can send you 5 dollars just to compensate you for my mistake...
thank you
@physwizz
kalii_ said:
hey, i've found the issue, i gave you the wrong file, sorry about that. if you got paypal maybe i can send you 5 dollars just to compensate you for my mistake...
thank you
@physwizz
Click to expand...
Click to collapse
Lol.
I don't take money
physwizz said:
Lol.
I don't take money
Click to expand...
Click to collapse
well, alright. just wanted to support you
kalii_ said:
well, alright. just wanted to support you
Click to expand...
Click to collapse
I do this for fun and to keep my old brain active
Unzip to get the tar file.
Installing instructions in next post
Installing Custom Recoveries
A. Preparation.
1. Download firmware for your device
2. Extract ap file using Zarchiver and extract recovery.img from recovery.img.lz4 and compress it to recovery.tar
3. Patch the ap file with a magisk which will patch both boot.img and vbmeta.img (from magisk, choose install then select file to patch)
Exynos 850 Resources
t.me
Alternatively you can extract boot.img.lz4 and vbmeta.img.lz4 from the ap file and compress them into a new tar file and then patch that file.
note: if you don't want root then just extract the vbmeta.img and use zarchiver to add it to my twrp.tar file.
You can flash this new file from odin at step 5
For Exynos 850 android 11 use a21s patched magisk.
For Exynos 850 android 12 and most other devices use delta magisk
4. Unlock OEM in developer options
5. Attach phone to pc and reboot to download mode
6. flash patched ap file.
Or..
Extract boot.img and vbmeta.img and add them to the TWRP zip.
7. Download recovery.img or download twrp.tar and extract recovery.img using Zarchiver.
B.Installation
Method 1.
1. Connect to pc and boot into stock recovery
2. Factory reset
3. Reboot into download mode.
4. flash twrp.tar into the ap slot
5. reboot to recovery
6. Advanced, terminal. Type multidisabler (twice).
7.
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
8. Reboot to recovery from main menu (not just reboot)
Backup boot, data, super and dtbo
9. Reboot to system
Method 2.
If you have already installed recovery and decrypted.
Extract recovery.img
1. Boot to recovery.
2. Install recovery.img
3. Choose recovery partition
4. Reboot to system then reboot to recovery
Backup boot, data, super and dtbo
(For Pitch-black just install the zip)
Method 3.
1. Install TWRP app
Extract recovery.img
2. Install TWRP
3. Choose file to flash.(don't select device)
4. Select recovery.img.
5. Reboot to recovery.
6. (You may need to change data partition to ext4 first if format ruins your system)
7. Reboot to recovery.
8. Wipe, format data, type YES.
9. Advanced, terminal.
10.Type multidisabler (twice).
Or flash samsung multidisabler zip
Or, for older phones flash dmverity zip
11.Reboot to recovery
12. Flash Magisk for root(only for method 3)
13. Backup boot, data, super and dtbo
Method 4
Using a second phone
Physwizz Collection
To flash TWRP from phone1 to phone2 Only if you have already installed recovery and decrypted. 1. Install this termux on phone1 2. Setup storage termux-setup-storage 3. Install this Heimdall Magisk module on phone1 Or install chroot Linux on termux and then install heimdall 4. Copy...
t.me
C. Recovery Problems
Most recovery issues can be solved by attending to the following issues.
1. Did you root using the full ap file patched Magisk .
(This contains the patched boot.img and vbmeta.img)
Exynos 850 users must use the special a217 magisk?
2. Did you then go all the way through the setup process?
3. Did you download the recovery to match your baseband?
See https://t.me/a127f_res/54 for Exynos 850 recoveries
4. Did you hold down power and volume up after Odin says pass?
5. Did you format data from stock recovery?
If you forgot to do this, just install stock recovery.img from TWRP and reboot.
6. Did you type multidisabler twice?
7. Did you reboot to recovery by choosing reboot from the menu and then choosing recovery?
8. To avoid touch issues go to settings and untick "allow time out"
D.To restore Stock Recovery
1. Attach phone to pc and reboot to download mode
2. flash patched ap file or stock recovery.tar
3. reboot
Or just flash stock recovery.img from twrp and reboot.
@physwizz
Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up
Feox said:
Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up
Click to expand...
Click to collapse
Feox said:
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
Click to expand...
Click to collapse
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.
ethical_haquer said:
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.
Click to expand...
Click to collapse
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...
Feox said:
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...
Click to expand...
Click to collapse
So you are following the official installation instructions? I'm pretty sure you don't have to:
Feox said:
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
Click to expand...
Click to collapse
as the official installation instructions for a Samsung device running A9 or higher say:
"
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Press the Install button in the Magisk card
If your device does NOT have boot ramdisk, check the “Recovery Mode” option
Choose “Select and Patch a File” in method, and select the AP tar file
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
"
It doesn't sound like you have to isolate the boot.img.
Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?
Feox said:
Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?
Click to expand...
Click to collapse
Just read the official installation instructions I linked to. I only copied part of it and pasted it here so you could see it.