Assalom-o-Alaikum!
How to Root and Flash TWRP on Samsung Galaxy A51 SM-A515F Android 11 – Build number DUB1 – Android security patch level: February 1, 2021. The TWRP version is 3.5.0 developed and brought to you by [email protected] senior developer and figured by Hendra Manudinata. You need installed TWRP for rooting or installing custom rom. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Downloads
Enable Developer Options: go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Enable OEM unlock and USB debugging options ( Settings -> Developer options )
Make sure the bootloader are unlocked.
Download and Extract ODIN v3.13.1 from https://odindownload.com/SamsungOdin
Download and Install Samsung Mobile Phone Drivers
Download Latest Magisk and Magisk Manager
Download Twrp+vbmeta_A11.tar
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Flashing TWRP on Galaxy A51 DUB1 firmware Android 11 :
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing Twrp+vbmeta_A11.tar as AP in ODIN, then click start.
TWRP is now successfully flashed to your device! Several steps before you can properly use the device.
DO NOT SKIP THIS STEP! Don’t remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
Select Install – Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip Swipe to confirm Flash
Select Wipe -> Format data, type ‘yes’ and confirm
Select Install – Magisk Magisk-v21.2.zip or latest, Swipe to confirm Flash (Rooting)
Select Reboot to System
Setup the phone, Done!
Rooting Instructions
Connect the Phone to Internet
Open Magisk Manager ( If you can not see it, just wait for a moment)
Done! You can use Root Checker to check it, Enjoy!
Watch this video:
Credit:
1. @ianmacd
2. @hendramanu
3. @redymedan
I can't do step 6 because the phone boots in to Download mode before it can get in to recovery.
load_kernel: Could not do Normal boot. (DR LOAD_Fail)
vbmeta: Error verifying vbmeta image: OD_NOT_SIGNED (3)
irajawi-fadif said:
I can't do step 6 because the phone boots in to Download mode before it can get in to recovery.
load_kernel: Could not do Normal boot. (DR LOAD_Fail)
vbmeta: Error verifying vbmeta image: OD_NOT_SIGNED (3)
Click to expand...
Click to collapse
DO NOT SKIP THIS STEP! Don’t remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
For more info please See the video.
Mohd Masab said:
DO NOT SKIP THIS STEP! Don’t remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
For more info please See the video.
Click to expand...
Click to collapse
I did that but it still boots in download mode and the cable is connected
Great work, Thanks! But after flashing A11+ TWRP and it's working, but i cannot access files of phone from recovery. I see all files Name mingled and encrypted, both from pc (when phone at TWRP recovery) and from TWRP itself. I'll upload pics. Can you help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And i see also i cannot backup:
Do you have good working TWRP for A51 for A11 ?
Thanks very much for your work!
tzahik1 said:
Great work, Thanks! But after flashing A11+ TWRP and it's working, but i cannot access files of phone from recovery. I see all files Name mingled and encrypted, both from pc (when phone at TWRP recovery) and from TWRP itself. I'll upload pics. Can you help?
And i see also i cannot backup:
Do you have good working TWRP for A51 for A11 ?
Thanks very much for your work!
Click to expand...
Click to collapse
I think you need this https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
irajawi-fadif said:
I think you need this https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
Click to expand...
Click to collapse
Thanks! I already installed Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip as in the instructions.
But maybe i didn't do it right.
I'll try again.
Don't know what is the order exactly. the zip last or first.
See there are same problems in Android 10:
TWRP for Android 10
Mohd Masab said:
DO NOT SKIP THIS STEP! Don’t remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
For more info please See the video.
Click to expand...
Click to collapse
@irajawi-fadif @Mohd Masab
I tried again and again, and nada. After booting at the end to recovery i see all files encrypt. installed at the last AGAIN Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip and files are encypt when booting from twrp recovery.
And i cannot Backup because all files are gibberish!
Can you check also on yours what happening after you show in the video to enter to TWRP recovery - can you see files on internal phone and can you do Backup. Please.
If i cannot backup from recovery what is the point of TWRP?
Thanks.
Can Anyone backup from recovery after all this?
Please check and tell. Thx.
Bingo!
@Mohd Masab @irajawi-fadif
You have an error in the steps and in the video:
YOU NEED TO REPEAT STEP 7 AGAIN AFTER STEP 9 (!!!)
You need to flash Disable_verity twice! before and right after all zips!
so after flashing Magisk (step 9) Repeat step 7.
Without that YOU CANNOT ACCESS phone data from recovery (only from system boot)
And YOU CANNOT BACKUP from recovery (data is encrypted)
You can see this method also in this guide:
TWRP on galaxy M51
Please fix it also in the video!
Thank you.
tzahik1.
tzahik1 said:
Great work, Thanks! But after flashing A11+ TWRP and it's working, but i cannot access files of phone from recovery. I see all files Name mingled and encrypted, both from pc (when phone at TWRP recovery) and from TWRP itself. I'll upload pics. Can you help?
And i see also i cannot backup:
Do you have good working TWRP for A51 for A11 ?
Thanks very much for your work!
Click to expand...
Click to collapse
Watch this video how to fix it
This is not my thread I can not edit it Enjoy!
redymedan said:
Watch this video how to fix it
This is not my thread I can not edit it Enjoy!
Click to expand...
Click to collapse
Thank you.
If you can, please check why sideload on TWRP recovery (Advanced--->ADB Sideload)
is not working
(I know this twrp was intended for Android 10 but still...)
If it worked, you don't need external SD card to flash all the zips...
Thanks
tzahik1 said:
Thank you.
If you can, please check why sideload on TWRP recovery (Advanced--->ADB Sideload)
is not working
(I know this twrp was intended for Android 10 but still...)
If it worked, you don't need external SD card to flash all the zips...
Thanks
Click to expand...
Click to collapse
This TWRP is not for Android 10, this is developed for Android 11. You can not use ADB on Samsung Galaxy device in TWRP. need or not SD Card it depends on what you want to do.
redymedan said:
This TWRP is not for Android 10, this is developed for Android 11. You can not use ADB on Samsung Galaxy device in TWRP. need or not SD Card it depends on what you want to do.
Click to expand...
Click to collapse
I saw TWRP 3.5.0 was for A10.
You are wrong. I use a lot my S9+ TWRP recovery with ADB Sideload to flash zips on my pc to device.
This however is not working. when you press ADB sideload (as i said above in the menu) USB connection to pc is disconnecting. When you press cancel and return to TWRP menu , connection to pc is back and you can see from "adb devices" the device at recovery state.
If you can fix it , it will be great because we won't need External SD card to flash zips, we can do it from pc.
Thanks.
irajawi-fadif said:
I did that but it still boots in download mode and the cable is connected
Click to expand...
Click to collapse
I have the exact same problem, where you able to solve it?
when i try to flash in odin i get (only official released binaries are allowed...)
SperguzeX said:
I have the exact same problem, where you able to solve it?
Click to expand...
Click to collapse
nope..
hello
Does this twrp will also work in the SM-A516U model?
Thanks
DroidJP said:
hello
Does this twrp will also work in the SM-A516U model?
Thanks
Click to expand...
Click to collapse
No
Do I have to use ODIN v3.13.1 or do I use the newer versions now?
Related
Install Gummy TWRP 2.7.1.0 Based Recovery on Oppo Find 7 (X9077/X9076)
Warning: Note: No one but yourself is responsible for what you do to your device.
X9077 = Chinese TD-LTE support // X9076 = EU FDD-LTE or US FDD-LTE support
Requirements:
Download / unzip the file --> AndroidSDKSlim.zip
Download this file --> Gummy-TWRP-2.7.1.0-find7.img
Make sure you have a charged battery (50 % minimum)
How to install:
Connect your phone to your PC. You should see a window with the drivers in an application called 'setup.exe '.
Start the installation process and wait until it ends. then disconnect the phone from the PC.
Extract the contents of the file ' AndroidSDKSlim.zip ' on your desktop. You should have a folder named ' android-sdk-windows ' where there is another folder: 'platform-tools.'
In this folder, move the .img files you downloaded ( Gummy-TWRP-2.7.1.0-find7.img)
Turn off your mobile.
Restart your mobile in fastboot mode by pressing the High Volume + Power buttons until the appearance of the word ' Fastboot ' .
Connect your phone to your PC via the USB cable.
In platform-tools folder 'with your mouse, do' right click 'while holding down the 'Shift ' button, then select ' Open a command window here . '
In this window, type the following code to verify that your device is recognized.
Code:
fastboot devices
Then type the following command to install the TWRP :
Code:
fastboot flash recovery Gummy-TWRP-2.7.1.0-find7.img
Do not reboot your phone, but just flash the "UPDATE-SuperSU-v2.01.zip " to gain root !
How to root :
Just download the attached file --> UPDATE-SuperSU-v2.01.zip
Copy/paste it on your memory phone
Reboot into recovery mode
Flash the file & next reboot your phone
Enjoy ! You're root !
Note: If don't work, try the " [11-07-2014 UPDATE Thread] How to get ROOT with ColorOS v1.2.3i on X9076/X9077/X9007/X9006 " section from this THREAD
Credits & Thanks
papi92
Team Gummy
Chainfire
dhacker29
EthanChen
Your feedback is welcome
Fantastic!
Great news!
Thanks for the instructions. Can anyone confirm if this works on the Find 7 X9076?
Just tested and it works great [Find 7 X9076].
Recovery and root access. Done!
Thank You. :good:
I can load the recovery, but as soon as I press Volume + or - within the recovery I have the following error message:
E:touch_calibrate: EVIOCGABS failed
From there on, if I initiate the touch screen UI by touching any part of the screen, I can no longer use Volume +/- and Power button combination properly. as soon as I use any of those button, it just automatically launch the first option that is on whatever the recovery menu is.
Am I the only one having this issue?
Thank you. This worked. (Find 7 X9076)
kingcedz said:
I can load the recovery, but as soon as I press Volume + or - within the recovery I have the following error message:
E:touch_calibrate: EVIOCGABS failed
From there on, if I initiate the touch screen UI by touching any part of the screen, I can no longer use Volume +/- and Power button combination properly. as soon as I use any of those button, it just automatically launch the first option that is on whatever the recovery menu is.
Am I the only one having this issue?
Click to expand...
Click to collapse
Same here. Got the error, unsure if I had exactly the same problem as you.
binaryfalcon said:
Thank you. This worked. (Find 7 X9076)
Same here. Got the error, unsure if I had exactly the same problem as you.
Click to expand...
Click to collapse
can you try use go into the recovery, use the touch screen on any of the option, then try volume+ or volume - or power button? when I do that, it just automatically press the 1st available option on the menu.
kingcedz said:
can you try use go into the recovery, use the touch screen on any of the option, then try volume+ or volume - or power button? when I do that, it just automatically press the 1st available option on the menu.
Click to expand...
Click to collapse
Confirmed. Seems like I went through the same problem, since it selected reboot twice earlier.
binaryfalcon said:
Confirmed. Seems like I went through the same problem, since it selected reboot twice earlier.
Click to expand...
Click to collapse
ok thanks, at least that is consistent between phones. Unfortunately i m not smart enough to do any fixings, hope this get highlighted and resolve in the future version of the recovery.
Yeah, it's still early though. Just glad it's working this well.
Hi,
Worked fine for me, thanks for the clear easy to follow guide. I noticed the error E:touch_calibrate: EVIOCGABS failed on the screen but all movements in the recovery seemed fine, I used physical keys first then tried the touch screen and that worked too.
At the end of the process it asks if you want to prevent the ROM from flashing the default recovery, I choose yes. Might be worth adding that for completeness as some people might be unsure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 09:54 PM ---------- Previous post was at 09:37 PM ----------
Just been back into the recovery to do a backup. Which ever button you press you get the error but all the buttons work fine. This sounds like a daft question but you are not getting the buttons back to front are you. On the Find 7 the volume buttons and power buttons are reversed to a lot of phones and it's easy to press power instead of volume.
Sorry if this is not the case. It's just it seems to respond to everything for me and that might explain why you were entering on the first option. Could you double check?
worked for me too
Works great on X9076, thanks OP!:good:
after that we must return to stock recovery if we want to update via ota?
No. I received an update yesterday when I reverted to.colorOS but kept the gummy recovery
Sent from my X9076 using XDA Premium 4 mobile app
Worked on the X9077 too but it didn't recognise my exFAT formatted external card...
Also, like TWRP, it's half size.... Which proves it's not the size but how you use it that matters...:laugh:
ultramag69 said:
Worked on the X9077 too but it didn't recognise my exFAT formatted external card...
Also, like TWRP, it's half size.... Which proves it's not the size but how you use it that matters...:laugh:
Click to expand...
Click to collapse
lol it's the true
Tks for your feedback . Try with another external sd card...
scumpicule said:
lol it's the true
Tks for your feedback . Try with another external sd card...
Click to expand...
Click to collapse
I think it doesn't like exFAT, FAT32 seems to work ok but that seems silly to me to have a kickass hd screen and not use it with hd movies...
Stock Recovery
How can I backup my Stock recovery image before flashing this. Or is the Stock X9076 Recovery already available for download?
Can official Oppo Stock Roms (ColorOS 1.2.1i for example) be installed with this recovery?
Fasboot not working
which system did you use it?
- I tried to Windows 8.1 x64 with USB 3, and I could not find the find 7 (x9076). No detect the phone.
Do you have any idea, how I can use it?
gazsyka said:
which system did you use it?
- I tried to Windows 8.1 x64 with USB 3, and I could not find the find 7 (x9076). No detect the phone.
Do you have any idea, how I can use it?
Click to expand...
Click to collapse
Use Win 8.1 64bit too.
Make sure you are going to fastboot on the phone by pressing up volume +power until Oppo logo appears, release power but keep holding up volume, you should see fastboot on the screen...
Using the ADB files, make sure you open the files until you can see the .exefiles, it helps to have the file you wish to flash in there too, and hold "shift" key down while right clicking on white space in the window. Choose "open command window here".
Connect the Find 7 to the PC & type "Fastboot Devices" in command propmt. You should get a serial number and device found or something, if you don't try a new cable or usb port...
Once the phone has been detected type "fastboot flash recovery "the file name of the recovery.img", to make it easy, the file needs to be in the ADB file and after you type the 1st letter of the file you want to flash, press "tab" it will autofill the filename (just make sure you have different names for the files).
Then you can follow the other instructions with Supersu to get root....
Team Win Recovery Project 3.0.2-0
This is for the Exynos SM-J710F, SM-J710FN, SM-J710GN, SM-J710MN, SM-J710K models only!
WARNING: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxyj72016exynos.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2-0 - Initial build on twrp.me
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported yet in TWRP 3 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/jcadduono/android_device_samsung_j7xelte (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_exynos7870 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
@jcadduono ,
Thanks for official TWRP.
Hello guy !
@jcadduono , thank you very much for great work ! It's fully working for my SM-J710FN
My internal storage doesnt mount. Requires to format data. And when i format the data, it becomes ok, and when you try to enter recovery again it doesnt mount the data, internal storage..
Sent from my SM-J710GN using XDA-Developers mobile app
Not sure if both are related but I had flashed this TWRP 4-5 days back. Last night after reboot (wasn't the 1st one after flashing certainly), phone didn't boot because of custom binary FRP lock. Had to reflash firmware.
@jcadduono why is the internal storage is not showing and why data is not mounting it gives always error
Amit.A said:
@jcadduono why is the internal storage is not showing and why data is not mounting it gives always error
Click to expand...
Click to collapse
jhampzkidoodle said:
My internal storage doesnt mount. Requires to format data. And when i format the data, it becomes ok, and when you try to enter recovery again it doesnt mount the data, internal storage..
Sent from my SM-J710GN using XDA-Developers mobile app
Click to expand...
Click to collapse
Normally on the newer Samsung devices we can flash https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt/ and then go to the wipe page and use [Format Data] to turn off encryption.
It seems there is a bug with the Exynos 7870 devices that causes vold to encrypt the device regardless of whether or not boot image fstab actually calls for encryption, and I've tried removing all hints of encryption support from the boot image and yet still the system will start encrypting on the next boot.
TWRP does not support Samsung's closed off encryption as it relies on the Android OS frameworks.
I've tried submitting this issue to Samsung's Mobile Security team but they just shrugged it off and said you can't turn it off on purpose.
So pretty much you're SOL for data partition (internal storage is inside that) reading in TWRP until someone comes along with system modifications to disable encryption or a custom ROM.
Hi bro... @jcadduono
Thanks for making Official TWRP Recovery for our J7 2016. Really its great work Thanks again. :good:
I have a 2016 SM-J700P... with the Exynos processor. Will this TWRP work for me?
Guys, will the fact that I now have TWRP recovery (I have a J7 J700M Model, from Brazil), using Android 5.1.1 -> Android 5.1.1 (debloated) cause any harm if I try to install 6.0.1 Marshmallow (http://live.samsung-updates.com/index.php?device=SM-J700M) using ODIN??
Thanks!
@jcadduono with the custom kernel http://forum.xda-developers.com/galaxy-j7/development/recovery-samsung-galaxy-sm-j710f-t3380736 encryption can be turned off.
thewinelover said:
I have a 2016 SM-J700P... with the Exynos processor. Will this TWRP work for me?
Click to expand...
Click to collapse
I doubt it, it has different exynos processer
artssa said:
Guys, will the fact that I now have TWRP recovery (I have a J7 J700M Model, from Brazil), using Android 5.1.1 -> Android 5.1.1 (debloated) cause any harm if I try to install 6.0.1 Marshmallow (http://live.samsung-updates.com/index.php?device=SM-J700M) using ODIN??
Thanks!
Click to expand...
Click to collapse
Offtopic post you have. Shouldn't be a problem for flashing a firmware for your device via Odin, whichever ROM you are using.
Join us Samsung Galaxy J7 2016 users Samsung Galaxy J7 ? Official Group in Telegram
Here you can chat with anyone.
Here many xda developers are present.
Here you can share any kind of data and files in any size.
And the biggest thing is that here you will get instant solution to any problem. :good:
Telegram Group Link : https://telegram.me/joinchat/Cmh8LUAs6AFEJUfawPCiWg
Regard by @KeMii :good:
I Root the Device but After root there were many issues..... I Keep on getting an notification that unauthorized action ...
and also my device keeps lagging it lags just for a second but this games every 2-3 mins
I also freezed KNOX with lucky patcher but the problem still persists any meathod to solve the problem Thanks
Installed Xposed... Few Modules and Partition Crushed... It was my Brand NEW Phone :'(
Hello, TWRP backup not properly block set. The size of EFS equal to 4 MB in size, inside the reserve of zeros.
No IMEI as all zeros!
Need to fix, or put my. In my TWRP you can flash system.img from firmware.
Good luck to everyone! TWRP is correctly bekapit EFS.
Extract postcode to flash the IMG.
http://4pda.ru/forum/index.php?s=&showtopic=763247&view=findpost&p=51990201
Here you can find a lot of useful for this smartphone. Please forgive me for my English :laugh:
The Lord does not forget to thank! And then I see the downloading is not weak and thanks to zero.
ermakovermakov7878 said:
Hello,your TWRP backup is not correct unit is specified. The efs size is equal to 4MB, inside backup zeros.
I took apart and tell it like it is. That's correct TWRP backup efs + setting backup System.img
Unpack the zip to flash the img.
http://4pda.ru/forum/index.php?s=&showtopic=763247&view=findpost&p=51990201
Here you can find a lot of useful for this smartphone.
Please excuse me for my English :laugh:
Click to expand...
Click to collapse
But it is all in russian :/
Will this work with J7-2016 with Snapdragon 617 ?
Skylinestar said:
Will this work with J7-2016 with Snapdragon 617 ?
Click to expand...
Click to collapse
No
will it work on Galaxy J7 prime ? it has same exynos 7870..
jcadduono said:
Team Win Recovery Project 3.0.2-0
FULL STEPS FOR OBTAINING ROOT
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Make sure your don't have Factory Reset Protection enabled in your Google account or you may never be able to boot again!
More information: https://support.google.com/nexus/answer/6172890?hl=en
Extract Odin_3.10.7.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for j7xelte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot, under Options tab disable Auto Reboot, then press [Start].
Once the flash is complete (Odin should tell you in the log, and progress bar on phone should stop), you can pull the battery then place the battery back in. Now hold [Volume Up] + [Home] + [Power] buttons until you reach recovery mode.
If you end up in stock recovery, start again from download mode step.
At this point, you will reach the screen asking you if you want to allow system modifications.
You will want to swipe to allow, otherwise the OS will replace TWRP once you boot!
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
Click to expand...
Click to collapse
i have SM-J710FN. if I only follow below 3 steps, then will i b able to root my device ??
1. allow usb debugging and OEM unlock
2. flash official TWRP via Odin ... then re insert battery & reboot into TWRP
3. wipe data in TWRP and then falsh SuperSU via TWRP
is it enough.. Do I need to flash kernels first ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unofficial TWRP 3.3.0 For J7 2017Disclaimer
I am 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 me for messing up your device, I will laugh at you.
Special features:
Code:
- built from Pie kernel source
- built in full 64bit mode
- updated TWRP source to 3.3
- Full F2FS Support
- fully compatible with all Oreo roms
Downloads:
J730x - Latest Release
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
Optional - Download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
J530x device tree - https://github.com/omnirom/android_bootable_recovery
Credits:
@corsicanu
@Dyneteve
@yshalsager
@TwrpBuilder
XDA:DevDB Information
TWRP_J730, Tool/Utility for the Samsung Galaxy J7 (2017)
Contributors
ananjaser1211, corsicanu
Version Information
Status: Stable
Current Stable Version: 3.3
Stable Release Date: 2019-04-17
Created 2018-08-30
Last Updated 2019-04-18
This TWRP is Android 8.1 Ready, when J7 officially receives Oreo this will be a direct flash either via .tar in odin or just update .img inside twrp itself.
This is also built on updated TWRP trees and all that good stuff. enjoy
sources are here if anyone wants to modify
**F2FS support is not there**
You are the best big thanks ?
Thanks @ananjaser1211 great job in making twrp for j7 specially this one is oreo ready. Too bad samsung crappy update is as late as ever.
flarestar123 said:
Thanks @ananjaser1211 great job in making twrp for j7 specially this one is oreo ready. Too bad samsung crappy update is as late as ever.
Click to expand...
Click to collapse
it will come eventually, lets hope it doesnt act like the current J5 update it broke multiple phone speakers so far :laugh:
ananjaser1211 said:
it will come eventually, lets hope it doesnt act like the current J5 update it broke multiple phone speakers so far :laugh:
Click to expand...
Click to collapse
Haha now even with dolby mod you will live in peace. No loud noise . And btw all those looking for the download link they are posted in github releases under assets
ananjaser1211 said:
[*]Based on Updated TWRP Tree
[*]Build with OMNI_8.1
[*]Support for 7.0/7.1.1/8.0/8.1
[*]ARM64 (2GB+ Zip)
[*]Working MTP (Windows/Linux)
[*]Propper System Mount/unmount
[*]EFS/Radio Backup enabled
[*]Aroma Support
[*]Disabled RED Debug Text
[*]Adjusted Partition Sizes
Click to expand...
Click to collapse
hey,
all is very fine.
NiceWork
plz can u disable Kernel warning line on boot to TWRP
Thanks
Thanks dev :good:
@ananjaser1211 Weird! Could not flash it. Odin FCs. (Win 10). twrp_3.2.1_1 works.
Greight said:
@ananjaser1211 Weird! Could not flash it. Odin FCs. (Win 10). twrp_3.2.1_1 works.
Click to expand...
Click to collapse
try to update twrp, not sure why it wouldnt work to begin with,flash 3.2.1 then download the twrp but .img , then flash it from twrp 3.2.1 as a workaround
What is different from Latest releases and Official TWRP Builder?
ananjaser1211 said:
try to update twrp, not sure why it wouldnt work to begin with,flash 3.2.1 then download the twrp but .img , then flash it from twrp 3.2.1 as a workaround
Click to expand...
Click to collapse
Thanks. Installed TWRP this way, but when I reboot to recovery, this message comes up in red:
recovery is not seandroid enforcing
Click to expand...
Click to collapse
Any ideas?
quanghuy226 said:
What is different from Latest releases and Official TWRP Builder?
Click to expand...
Click to collapse
Nothing, just wanted to keep twrp builder there as it gets auto updated every month, while mine would only be updated if im experimenting more stuff.right now they are on the same thing
Greight said:
Thanks. Installed TWRP this way, but when I reboot to recovery, this message comes up in red:
Any ideas?
Click to expand...
Click to collapse
Does it boot after ? that red msg is normal, if it stays on splash, what is your variant
ananjaser1211 said:
Does it boot after ? that red msg is normal, if it stays on splash, what is your variant
Click to expand...
Click to collapse
Yes and it works fine. BTW only appears on TWRP pre-boot screen. I have the G model.
Greight said:
Yes and it works fine. BTW only appears on TWRP pre-boot screen. I have the G model.
Click to expand...
Click to collapse
ok thanks for clarification, i thought it was stuck, ill add a patch to remove that red logo later.
New TWRP out:
Changes:
switched to TwrpBuilder official builds
included crypto for LineageOS software encrypted data, thanks to @Option58
made preload partition wipeable in recovery
included cpefs and m9kefs partitions in backup for safety reasons
Downloads:
J730x - https://github.com/TwrpBuilder/android_device_samsung_j7y17lte/releases
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
Optional - Download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
All the best!
I replaced my touch screen and your twrp is touch screen is not working and a8+ rom.....
EyuphanKundakci said:
I replaced my touch screen and your twrp is touch screen is not working and a8+ rom.....
Click to expand...
Click to collapse
Don't use fake displays. Done
ananjaser1211 said:
Don't use fake displays. Done
Click to expand...
Click to collapse
Other roms work excellent but your roms doesn't work please fix bro.
EyuphanKundakci said:
Other roms work excellent but your roms doesn't work please fix bro.
Click to expand...
Click to collapse
My ROMs work fine. And they are Oreo. Your device probably won't work with stock Oreo as well. Don't go cheap on a screen replacement
How to Root Samsung Galaxy A50 SM-A505F Android 11 with Magisk + OrangeFox ( OneUI 3.1 ). The OrangeFox Recovery ( Brought to you by @enzoaquino ) support Galaxy A50 One UI 3.1 Android 11, Android security patch level: 1 March 2021. It may be works for SM-A505F, SM-A505FN, SM-A505G, SM-A505GN. The OrangeFox R11.0 comes with Magisk Patched. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
LET US KNOW IF IT WORKS FOR:
SM-A505FN, SM-A505G, SM-A505GN ( NOT TESTED )
Manual Instructions:
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing OrangeFox-R11.0-Stable-a50dd_magisk.tar as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until OrangeFox Recovery Appears.
Format data
Install multidisabler-samsung-2.6.zip
Reboot to Recovery
When SAMSUNG logo appears wait for a few minutes or more then press and hold volume down + power key until the screen blank
Setup the phone
Connect Phone to Internet
Tap Magisk app: "Upgrade to full Magisk to finish the setup. Download and Install?" tap OK
Install and Open Magisk Manager, Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Video Instructions
Download
OrangeFox-R11.0-Stable-a50dd_magisk.tar
Credits to @Enzoaquino for OrangeFox A50 A11
Magisk patched and packed to .tar by me
The multidisabler isnt flashing it says zip file format errorhttps://drive.google.com/file/d/1-9UADSgWzPX2EHaaNOoMSd7_Thz_ft8b/view?usp=drivesdk
It worked just fine and got root with it but im curious about the multidisabler zip. What does it do and what is the fnction of it? It give me an eror while flashing both 2.6 and the latest version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I made it.
multidisabler-samsung-2.6 didn't work on SM-A505F
USE
multidisabler-samsung-3.1.zip
I tried both 3.1 and 2.6 but still failed to flash
Is it working or not?
redymedan said:
How to Root Samsung Galaxy A50 SM-A505F Android 11 with Magisk + OrangeFox ( OneUI 3.1 ). The OrangeFox Recovery ( Brought to you by @enzoaquino ) support Galaxy A50 One UI 3.1 Android 11, Android security patch level: 1 March 2021. It may be works for SM-A505F, SM-A505FN, SM-A505G, SM-A505GN. The OrangeFox R11.0 comes with Magisk Patched. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
LET US KNOW IF IT WORKS FOR:
SM-A505FN, SM-A505G, SM-A505GN ( NOT TESTED )
Manual Instructions:
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing OrangeFox-R11.0-Stable-a50dd_magisk.tar as AP in ODIN, then click start.
DO NOT SKIP THIS STEP! Don't remove USB Cable, let it connected. Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until OrangeFox Recovery Appears.
Format data
Install multidisabler-samsung-2.6.zip
Reboot to Recovery
When SAMSUNG logo appears wait for a few minutes or more then press and hold volume down + power key until the screen blank
Setup the phone
Connect Phone to Internet
Tap Magisk app: "Upgrade to full Magisk to finish the setup. Download and Install?" tap OK
Install and Open Magisk Manager, Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Done!
Video Instructions
Download
OrangeFox-R11.0-Stable-a50dd_magisk.tar
Credits to @Enzoaquino for OrangeFox A50 A11
Magisk patched and packed to .tar by me
Click to expand...
Click to collapse
send pls zip without magisk
Ok i worked around the "invalid zip format error"
i tried all the versions from v2.0 to 3.1.. none worked
then i extracted the version 3.1 on my pc, i went inside the folder and i created the zip file of the "META_INF" folder
then i copied META-INF.zip file to my mobile and it worked
Hope this helps everyone
This is my first time rooting a device btw.. lol
i was using twrp btw
msuroxy said:
Ok i worked around the "invalid zip format error"
i tried all the versions from v2.0 to 3.1.. none worked
then i extracted the version 3.1 on my pc, i went inside the folder and i created the zip file of the "META_INF" folder
then i copied META-INF.zip file to my mobile and it worked
Hope this helps everyone
This is my first time rooting a device btw.. lol
i was using twrp btw
Click to expand...
Click to collapse
Soo you only need meta-inf and compress it to a zip file??
PetiHun08 said:
Soo you only need meta-inf and compress it to a zip file??
Click to expand...
Click to collapse
yes extract the downloaded zip "multidisabler-samsung-3.1.zip"
go into folder "multidisabler-samsung-3.1"
right click "META-INF" folder and create Zip
Copy "META-INF.zip" file to mobile and flash
it worked for me!
msuroxy said:
yes extract the downloaded zip "multidisabler-samsung-3.1.zip"
go into folder "multidisabler-samsung-3.1"
right click "META-INF" folder and create Zip
Copy "META-INF.zip" file to mobile and flash
it worked for me!
Click to expand...
Click to collapse
Okay i'm going and try it cuz i have to fix my soft bricked a50 and root it( i have bricked it with no multidisabler after installing twrp cuz it failed)
do let us know if it worked or not..!
msuroxy said:
do let us know if it worked or not..!
Click to expand...
Click to collapse
Almost done...
PetiHun08 said:
It worked my phone booted properly with twrp and didn't replaced it. Thamks! :highfive:
Click to expand...
Click to collapse
My model: A505fn/ds eu model
wohoo.. cheers man!! now i have to figure out what i can do with a rooted device.. first time rooting a device.. any pointers??
msuroxy said:
wohoo.. cheers man!! now i have to figure out what i can do with a rooted device.. first time rooting a device.. any pointers??
Click to expand...
Click to collapse
Speed the device up with lspeed, Change boot animation, reset knox trip with triangle away, hack games with gameguardian(it works like cheatengine), install custom roms and lots of more!
PetiHun08 said:
Speed the device up with lspeed, Change boot animation, reset knox trip with triangle away, hack games with gameguardian(it works like cheatengine), install custom roms and lots of more!
Click to expand...
Click to collapse
thanks man.. i'll see you around
q1pa said:
I tried both 3.1 and 2.6 but still failed to flash
View attachment 5274351
Click to expand...
Click to collapse
My file flashed without error. u may try it.
Why does magisk dissappear when I reboot? I'm not talking about when Magisk asks to reboot, i get past that magisk is still good but if i have to reboot again it dissappears.
UPDATE
Flash at your own Risk !!!
Tested Working:
Backup
Flash zip
Fastbootd support
Flash gsi roms
Not Working:
Usb Otg
You tell me
How to Flash on Android 11
1. Reboot Device to Downloadmode
2. Unlock Bootloader
3. Install adb and Fastboot driver and Device Drivers ( Google will Help )
4. Download the VBMeta-disabled.tar and the twrpa22v3.tar from Attachments
5. Download Odin3 from Attachments and start Odin on PC
6. In Odin Press on Options and untick Auto Reboot
7. Flash VBMeta-disabled.tar with Odin ( In Odin click on AP - select the vbmeta-disabled.tar and press start )
8. After flash vbmeta without errors press on AP and select twrpa22v3.tar and press on start
9. If all is Flashed without errors longpress power and vol- on device
10. instantly after device goes Blackscreen press and hold power and vol+ for 5-8 seconds to boot to TWRP
11. In TWRP press on Advanced - than on Terminal - and write " multidisabler " and press on the blue button
12. repeat step 11
13. press on reboot - than on recovery
How to Flash on Android 12
1. Reboot Device to Downloadmode
2. Unlock Bootloader
3. Install adb and Fastboot driver and Device Drivers ( Google will Help )
4. Download the magisk patched.tar and the twrp12.1_a225f-A12.tar from Attachments
5. Download Odin3 from Attachments and start Odin on PC
6. In Odin Press on Options and untick Auto Reboot
7. Flash magisk patched.tar with Odin ( In Odin click on AP - select the magisk patched.tar and press start )
8. After flash magisk patched.tar without errors press on try to reboot download -device reboots to dl mode
9. Flash twrp12.1_a225f-A12.tar with Odin ( In Odin click on AP - select the twrp12.1_a225f-A12.tar and press start )
10. If all is Flashed without errors longpress power and vol- on device
11. instantly after device goes Blackscreen press and hold power and vol+ for 5-8 seconds to boot to TWRP
12. In TWRP press on Advanced - than on Terminal - and write " multidisabler " and press on the blue button
13. repeat step 12
14. press on reboot - than on recovery
How to flash gsi:
Use the google platform tools adb/fastboot Download from Attachments
Boot to TWRP
1. In TWRP press Wipe-Advanced Wipe- select Dalvik, data, cache, metadata and swipe to wipe
2. After wipe go back to main screen and press Reboot- than press Fastboot
3. Device reboots to TWRP with Fastboot Interface
4. now plugin Device to PC open platform tools and execute cmd-here.exe
5. Type : fastboot devices - if no output check your Drivers/Usb connection
6. If device is Found by "fastboot devices" command enter " fastboot flash system PATHTOYOURGSI.img"
maybe it writes :Invalid sparse file format at header magic - but this can be ignored
After flash completed without errors type : fastboot reboot and press enter
GSI Download (Tested and bootable ) :
Only Arm64-BGZ Variants are bootable
( BTW gsi imgs with .xz File Format must be extracted ! Don't simple rename it to .img )
CrDroid 11 (Face-unlock and Fingerprint works)
android 12
Bliss 11
caos11
Credits:
afaneh92 For the a32x Devicetree
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
KI
Device Tree base used : https://github.com/mohammad92/android_device_samsung_a32x
A22 4g A11 Tree :https://github.com/deader89/galaxy-A22-4g-twrp-Tree
A22 4g A12 Tree :https://github.com/deader89/a22_TWRP12.1_tree.git
Thanks. Will test this.
I'm in the process of wiping through TWRP. It says
"Failed to mound '/metadata' (Invalid argument)
I've already converted the format partition from FAT to EXT4, and wiped the selected items but I'm stuck with the error above. Idk if this won't make me able to proceed to flashing the gsi
nice. Wish there were clear instructions on how to flash this phone, though.
nptoonix said:
Thanks. Will test this.
I'm in the process of wiping through TWRP. It says
"Failed to mound '/metadata' (Invalid argument)
I've already converted the format partition from FAT to EXT4, and wiped the selected items but I'm stuck with the error above. Idk if this won't make me able to proceed to flashing the gsi
Click to expand...
Click to collapse
did you run the multidisabler ?
Cheese-ass said:
WIP WIP WIP WIP
UPDATE
Flash at your own Risk !!!
Tested Working:
Backup
Flash zip
Fastbootd support
Flash gsi roms
Not Working:
Usb Otg
You tell me
how i Flashed it:
Flash this VBMeta with Odin - https://forum.xda-developers.com/t/...-galaxy-a32-5g-mediatek.4286631/post-85593097
Follow this Guide: https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a32-5g-mediatek.4286631/ but use twrpa22v2.tar added under Attachments
How to flash gsi:
use the google platform tools adb/fastboot
Boot to TWRP
In TWRP press Wipe-Advanced Wipe- select Dalvik,data,cache,metadata and swipe to wipe
after wipe go back to main screen and press Reboot-Fastboot
Device reboots to TWRP with Fastboot Interface
now plugin Device to PC open platformtools adb/Fastboot
Type : fastboot flash system PATHTOYOURGSI.img and press enter
maybe it writes :Invalid sparse file format at header magic - but this can be ignored
After flash completed type : fastboot reboot
GSI Download (Tested and bootable ) :
CrDroid 11 (Face-unlock and Fingerprint works)
android 12
Bliss 11
caos11
Credits:
afaneh92 For the a32x Devicetree
View attachment 5409225View attachment 5409227View attachment 5409229
Device Tree base used : https://github.com/mohammad92/android_device_samsung_a32x
Kernelbase is same as my custom Kernel: https://forum.xda-developers.com/t/root-galaxy-a22-sm-a255f--android-11.4329471/
Click to expand...
Click to collapse
Hey, so I really want to root my A22, but I would want some more info. I would like more info on how to flash the A12 GSI, like what about vendor etc, I mean I know stuff about roms but no stuff about GSI'S whatsoever, so like is vendor needed etc? And also can you give me a more detailed tutorial on how to flash it? I'd love Android 12 on this phone.
BlueTower said:
Hey, so I really want to root my A22, but I would want some more info. I would like more info on how to flash the A12 GSI, like what about vendor etc, I mean I know stuff about roms but no stuff about GSI'S whatsoever, so like is vendor needed etc? And also can you give me a more detailed tutorial on how to flash it? I'd love Android 12 on this phone.
Click to expand...
Click to collapse
Generic system images | Android Open Source Project
source.android.com
There you find everything about gsi
Cheese-ass said:
Generic system images | Android Open Source Project
source.android.com
There you find everything about gsi
Click to expand...
Click to collapse
No, I just wanted a better tutorial on hiw to install it with twrp or fastboot or whatevrr
BlueTower said:
No, I just wanted a better tutorial on hiw to install it with twrp or fastboot or whatevrr
Click to expand...
Click to collapse
BlueTower said:
No, I just wanted a better tutorial on hiw to install it with twrp or fastboot or whatevrr
Click to expand...
Click to collapse
How to flash GSIs on devices with dynamic super partition
* Disclaimer * I am not responsible for bricked devices, dead SD cards, thermonuclear war, * or you getting fired because the alarm app failed. Please do some research * before flashing GSI! YOU are choosing to make these modifications, and if *...
forum.xda-developers.com
Can you write a rookie-level tutorial?
As confusing as it sounds it literally is what it is.
BlueTower said:
As confusing as it sounds it literally is what it is.
Click to expand...
Click to collapse
I have been thinking of buying an a22.
Have you got TWRP to install ok?
physwizz said:
I have been thinking of buying an a22.
Have you got TWRP to install ok?
Click to expand...
Click to collapse
Yepp... perfectly works. No issues, efs just might break sometimes like it already did to me and you have to flash stock if you didn't back up efs
BlueTower said:
Yepp... perfectly works. No issues, efs just might break sometimes like it already did to me and you have to flash stock if you didn't back up efs
Click to expand...
Click to collapse
Ok
I might see if I can build a custom kernel for it
Cheese-ass said:
UPDATE
Flash at your own Risk !!!
Tested Working:
Backup
Flash zip
Fastbootd support
Flash gsi roms
Not Working:
Usb Otg
You tell me
How to Flash:
1. Reboot Device to Downloadmode
2. Unlock Bootloader
3. Install adb and Fastboot driver and Device Drivers ( Google will Help )
4. Download the VBMeta-disabled.tar and the twrpa22v3.tar from Attachments
5. Download Odin3 from Attachments and start Odin on PC
6. In Odin Press on Options and untick Auto Reboot
7. Flash VBMeta-disabled.tar with Odin ( In Odin click on AP - select the vbmeta-disabled.tar and press start )
8. After flash vbmeta without errors press on AP and select twrpa22v3.tar and press on start
9. If all is Flashed without errors longpress power and vol- on device
10. instantly after device goes Blackscreen press and hold power and vol+ for 5-8 seconds to boot to TWRP
11. In TWRP press on Advanced - than on Terminal - and write " multidisabler " and press on the blue button
12. repeat step 11
13. press on reboot - than on recovery
How to flash gsi:
Use the google platform tools adb/fastboot Download from Attachments
Boot to TWRP
1. In TWRP press Wipe-Advanced Wipe- select Dalvik, data, cache, metadata and swipe to wipe
2. After wipe go back to main screen and press Reboot- than press Fastboot
3. Device reboots to TWRP with Fastboot Interface
4. now plugin Device to PC open platform tools and execute cmd-here.exe
5. Type : fastboot devices - if no output check your Drivers/Usb connection
6. If device is Found by "fastboot devices" command enter " fastboot flash system PATHTOYOURGSI.img"
maybe it writes :Invalid sparse file format at header magic - but this can be ignored
After flash completed without errors type : fastboot reboot and press enter
GSI Download (Tested and bootable ) :
Only Arm64-BGZ Variants are bootable
( BTW gsi imgs with .xz File Format must be extracted ! Don't simple rename it to .img )
CrDroid 11 (Face-unlock and Fingerprint works)
android 12
Bliss 11
caos11
Credits:
afaneh92 For the a32x Devicetree
View attachment 5409225View attachment 5409227View attachment 5409229
Device Tree base used : https://github.com/mohammad92/android_device_samsung_a32x
Kernelbase is same as my custom Kernel: https://forum.xda-developers.com/t/root-galaxy-a22-sm-a255f--android-11.4329471/
Click to expand...
Click to collapse
Hi there, I'm a noob regarding to this, but I was able to follow this guide successfully for my A225m.
But I'd like to understand what's going on here, can you give an explanation about each step and what does it do?
Also, can the vbmeta flashing be done _without_ Odin? For example using only fastboot (which works on Linux unlike Odin).
itaranto said:
Hi there, I'm a noob regarding to this, but I was able to follow this guide successfully for my A225m.
But I'd like to understand what's going on here, can you give an explanation about each step and what does it do?
Also, can the vbmeta flashing be done _without_ Odin? For example using only fastboot (which works on Linux unlike Odin).
Click to expand...
Click to collapse
https://android.googlesource.com/platform/external/avb/+/master/README.md this is documentation about vbmeta
i think it cant be flashed without odin before twrp is installed
Cheese-ass said:
Not Working:
Usb Otg
You tell me
Click to expand...
Click to collapse
I've been using this for a while in my A225M and the Ambient Light/Proximity sensor doesn't work.
itaranto said:
I've been using this for a while in my A225M and the Ambient Light/Proximity sensor doesn't work.
Click to expand...
Click to collapse
twrp wouldn't cause that
physwizz said:
twrp wouldn't cause that
Click to expand...
Click to collapse
I know, should I report this to https://github.com/eremitein/treble-patches ?
Thank you for following your tutorial, successfully rooting, and flashing the system
There are three problems with crdroid, the dual card manager cannot work quickly, the hotspot cannot be used, and the system cannot mount the phone storage