{
"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"
}
Official TWRP 3.4.0 for SM-N9750/N9700
*** Not for USA carrier devices, this will only work on devices with an unlocked bootloader
Telegram thread
Built using OMNI source 9.0
TWRP v3.4.0
See post #2 for install steps
Changelog...
v1
Initial build
MTP, OTG and SDcard all working
Encryption not working, but being implemented later
v2
Added N9700 support
Updated kernel to SI3
v3
Fixed img flashing
v5
Encryption support added
Fixed brightness control
v6
Added dtbo
Magisk is no longer patched into imgs
TWRP is now Official
v7
Fixed recovery_dtbo
v8
SJ5 kernel, fixes camera on SJ5 firmware
v17
Updated to twrp 3.4.0
Updated kernel and dtbo (tf1 Android 10 only)
TWRP Downloads
N9750 TWRP 3.4.0 Downloads
N9700 TWRP 3.4.0 Downloads
WETA Kernel
Telegram thread
Thanks to @geiti94 and @klabit87 for allowing me to constantly pick their brains
--------------------->
Beer fund
XDA:DevDB Information
TWRP Galaxy Note 10+ snapdragon, Kernel for the Samsung Galaxy Note 10+
Contributors
Mentalmuso, mentalmuso
Source Code: Kernel source
Kernel Special Features:
Version Information
Status: Stable
Created 2019-09-30
Last Updated 2019-09-30
TWRP installation changed
N9750 TWRP 3.4.0 Downloads
N9700 TWRP 3.4.0 Downloads
WETA Kernel
* Unlock bootloader first
* Reboot recovery and reboot system now behave normally after flashing.
* No more patching in Magisk manager at all.
* Be aware, first clean boot, hangs on building cache, hard reboot after waiting about 3min and you'll boot past this
* If simply updating your existing TWRP, v9 upwards, you only need to flash the TWRP.img in recovery. No need to reflash kernel and Magisk.
Process from bone stock
1. Flash TWRP.tar in Odin
2. Reboot directly into TWRP
3. Format data, reboot recovery
4. Flash kernel
5. Flash encryption disabler.
6. Unmount system, Flash Magisk.
7. Reboot system
Process from existing TWRP
1. Flash TWRP.img to recovery
2. Reboot recovery
3. Flash Kernel zip
4. Unmount system and Flash Magisk zip
5. Reboot system
--->
Has anyone confirmed this working or is the bootloader unlock the deal breaker? I'm rusty with no PC yet. I would've thought that this thread would be flooded by now. Hmm...
Sent from my SM-N975U using Tapatalk
justlovejoy said:
Has anyone confirmed this working or is the bootloader unlock the deal breaker? I'm rusty with no PC yet. I would've thought that this thread would be flooded by now. Hmm...
Sent from my SM-N975U using Tapatalk
Click to expand...
Click to collapse
What's surprising about it? Unlock the bootloader, flash TWRP then disable encryption. Then you'll be free. This is for the global version of the Note 10 +, most people have the US version where you can't even unlock the bootloader. The phone is only a month old, lots of users these days wait until the price drops or they get them second hand. Thanks @Mentalmuso for the recovery, I'll give it a try tomorrow night.
ajsmsg78 said:
What's surprising about it? Unlock the bootloader, flash TWRP then disable encryption. Then you'll be free. This is for the global version of the Note 10 +, most people have the US version where you can't even unlock the bootloader. The phone is only a month old, lots of users these days wait until the price drops or they get them second hand. Thanks @Mentalmuso for the recovery, I'll give it a try tomorrow night.
Click to expand...
Click to collapse
Aha!! Thanks for being so informative and polite. I wish I could slam it in and flash her but yep. Us version. This phone is still beast. Thanks OP @Mentalmuso for all your hard work and dedication.
Sent from my SM-N975U using Tapatalk
ajsmsg78 said:
What's surprising about it? Unlock the bootloader, flash TWRP then disable encryption. Then you'll be free. This is for the global version of the Note 10 +, most people have the US version where you can't even unlock the bootloader. The phone is only a month old, lots of users these days wait until the price drops or they get them second hand. Thanks @Mentalmuso for the recovery, I'll give it a try tomorrow night.
Click to expand...
Click to collapse
Dammit, I forgot to add that info to the op. Thanks
v2 n9750 + n9700
Added support for the n9700 note 10 for any lurkers.
Updated kernel to SI3
[URL="https://nextcloud.justbeca.us/s/WJwQfA4Cz7P5mNw]Download folder[/URL]
Downloads also available in Telegram thread.
--->
v3 n9750 + n9700
Fixed img flashing function
[URL="https://nextcloud.justbeca.us/s/WJwQfA4Cz7P5mNw]Download folder[/URL]
Downloads also available in Telegram thread.
--->
Hi @Mentalmuso,
How did you Unlock the bootloader pls?
I have a snapdragon Note 10 + , SM -N9750/ DS , using TGY Firmware !
Ths for your Help.
B
EDIT01: i saw it here: https://forum.xda-developers.com/galaxy-note-10+/how-to/guide-how-to-root-note-10-t3960031
EDIT02: No Easy process 4 me
sorry but your telegram file link don't working.
Ths to add me pls: @bishopandyou
finally the snapdragon n10 and tab s6 got twrp too for sammy encryption i will let you know more after i get it working too on exynos one
Hello, is it possible to add support for S10 Snapdragon family?
FlatOutRU said:
Hello, is it possible to add support for S10 Snapdragon family?
Click to expand...
Click to collapse
I would say so, I assumed it had it already.
Mentalmuso said:
I would say so, I assumed it had it already.
Click to expand...
Click to collapse
Its a part from Chinese ROM only, not a separate one...
What info do you need to make a twrp for s10+?
FlatOutRU said:
Its a part from Chinese ROM only, not a separate one...
What info do you need to make a twrp for s10+?
Click to expand...
Click to collapse
I've submitted the trees for S10 devices today, I have imgs for the S10 built if you want to test. Hit me up on telegram.
Mentalmuso said:
I've submitted the trees for S10 devices today, I have imgs for the S10 built if you want to test. Hit me up on telegram.
Click to expand...
Click to collapse
@FlatOutRU @Mentalmuso
Let me know how these tests work out. I can link back to here and simplify the S10 guide.
Fznwolf said:
@[email protected]
Let me know how these tests work out. I can link back to here and simplify the S10 guide.
Click to expand...
Click to collapse
Thanks, I'll create an S10 thread once things are made official. Is there just one S10 forum? Or is there an s10e and S10+?
Mentalmuso said:
Thanks, I'll create an S10 thread once things are made official. Is there just one S10 forum? Or is there an s10e and S10+?
Click to expand...
Click to collapse
Sadly one for each. If you post it in the 10 or 10+ I think most people will stumble across it.
Thanks again for your work.
blocked by oem lock?
i have the international sm-n9750. i turn on oem unlock, reboot to download mode and flash TWRP and i get fail on phone it says blocked by oem lock? what am i doing wrong?
Mentalmuso said:
TWRP 3.3.1 for SM-N9750/N9700
*** Not for USA carrier devices, this will only work on devices with an unlocked bootloader
Telegram thread
Built using OMNI source 9.0
TWRP v3.3.1
See post #2 for install steps
Changelog...
1.0
Initial build
MTP, OTG and SDcard all working
Encryption not working, but being implemented later
2.0
Added N9700 support
Updated kernel to SI3 source
TWRP Downloads
Download TWRP 3.3.1 folder
Telegram thread
Thanks to @geiti94 and @klabit87 for allowing me to constantly pick their brains
--------------------->
Beer fund
XDA:DevDB Information
TWRP Galaxy Note 10+ snapdragon, Kernel for the Samsung Galaxy Note 10+
Contributors
Mentalmuso, mentalmuso
Source Code: [url]https://github.com/mentalmuso/android_kernel_samsung_d2q[/URL]
Kernel Special Features:
Version Information
Status: Stable
Created 2019-09-30
Last Updated 2019-09-30
Click to expand...
Click to collapse
andrewgiv said:
i have the international sm-n9750. i turn on oem unlock, reboot to download mode and flash TWRP and i get fail on phone it says blocked by oem lock? what am i doing wrong?
Click to expand...
Click to collapse
Sounds like you have some reading to do if it's anything like the S10. You'll likely need to flash a multidisabler and wipe data somewhere in there too.
andrewgiv said:
i have the international sm-n9750. i turn on oem unlock, reboot to download mode and flash TWRP and i get fail on phone it says blocked by oem lock? what am i doing wrong?
Click to expand...
Click to collapse
Did you unlock the bootloader? Switching oem unlock is just half of it.
Related
Team Win Recovery Project 3.0.2-0
This is for the Xiaomi Mi MIX only, do not flash on other models!
WARNING: As of Android Marshmallow, factory boot images have dm-verity enabled, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below in order to allow system modifications without the risk of a boot loop!
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.
Read more about TWRP here: https://twrp.me/about/
DOWNLOAD
You can find the device page here:
For official stock/dev firmware: http://teamw.in/devices/xiaomimimix.html
For (slightly newer) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc1-eu-lithium.img
For (the latest EU) firmware: https://build.nethunter.com/test-builds/twrp/xiaomi/twrp-3.0.2-0-rc2-eu-lithium.img
(touchscreen will not respond if not matching firmware)
You can find up to date fastboot & adb binaries here!
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
You must first unlock your device. To do this, follow the instructions on the MIUI forums. (tedious, I know)
{
"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"
}
Extract adb & fastboot to your computer.
Download TWRP for Xiaomi Mi MIX (lithium).
Reboot your device into fastboot mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Power] buttons while your device reboots.
Once you're in fastboot mode, you're ready to flash TWRP. To do this, run these commands in order:
fastboot flash recovery twrp.img
fastboot boot twrp.img
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
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.
If you want to be rooted with something else or just want a bootable system:
Download the latest dm-verity and forced encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
This will also allow you to use [Format Data] to completely disable your encryption if desired.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up. (SuperSU will reboot you a few times)
* 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 - Official release on twrp.me
v3.0.2-0-rc1 - Initial release candidate and first XDA build
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
There's absolutely none that I know of. Rejoice. You even have working hardware encryption!
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 (Official): https://github.com/TeamWin/android_device_xiaomi_lithium (android-6.0)
Device tree (Development): https://github.com/jcadduono/android_device_xiaomi_lithium (android-6.0)
Kernel: Unavailable (waiting on Xiaomi source release, using MIUI stock binary for now)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
Thank you to @wolfgart for requesting device support and reporting feedback on my initial builds.
Great Work
Now Xiaomi MI MIX is the greatest device we can have atm
@jcadduono @wolfgart Wolfgart request your help just because in Italy I've already published italian rom with my recoveryas you see from here
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=999961
http://forum.hdblog.it/index.php?/topic/55021-xiaomi-mi-mix-official/?p=1000010
But your official support is obviously better than mine. I follow you in a lot of thread so I know your great work:good::good: Very happy for this
development is starting , great work OP
agriculture said:
development is starting , great work OP
Click to expand...
Click to collapse
Best device now has best TWRP ever made before.
tnx @jcadduono
Looks like it won't be showing up on twrp.me until 3.0.3 or 3.1.0 depending on what's next. There's a few incompatibilities in the device tree and I'd prefer to wait it out till then. Ex. 3.0.2 doesn't support f2fs or ntfs on omnirom trees right now, but our current source does. If I made an official release neither would be supported.
Update: Official release made on newer TWRP build tree.
Wow, a thousand thanks.
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
mega00 said:
I flashed the recovery, but the touch screen was not working, I can't do anything in the recovery, anyone know what's wrong?
Click to expand...
Click to collapse
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
mega00 said:
Wow, a thousand thanks.
Click to expand...
Click to collapse
don't quote the entire thread opener.... edit your post and remove it, if you need to make adjustments use the edit button, don't make another post immediately after your own
jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Update: Yes, I changed to stable rom and it works.
Click to expand...
Click to collapse
mega00 said:
jcadduono said:
did you read the part about needing a different TWRP image for EU vs stock ROM? You will need to boot the ROM you want, then turn off the device completely and boot into the TWRP version that matches it. This is a kernel firmware update issue that I can't fix until Xiaomi releases sources.
I am on stock rom and using the stock rom version TWRP, the touch screen just don't work.
To be more clear, I am on dev rom 6.11.10 (MIUI8), do I have to change to stable rom V8.0.8.0.MAHCNDI (MIUI8) to make it work?
Click to expand...
Click to collapse
you have to flash CN Stable rom V8.0.8.0.MAHCNDI (MIUI8) and use original TWRP for it and if you want Cross-Flash your CN rom with International one Here too .
When you are on International rom up&running you can flash over the EU TWRP .
As explained from @jcadduono this is the only solution for the moment until XIAOMI release his Kernel stuff officially
Click to expand...
Click to collapse
Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app
cultofluna said:
Thanks to the devs for such fast development on this great phone ...
I personally coming from lg so xiaomi is completely new for me ...
I understand the usual steps unlocking bootloader..flashing twrp ...and finally root ....
I don't have the phone yet but when it comes is running the same stock rom for everybody if I'm not wrong?...
What is that with the different roms?...
And how do i know wich twrp have to install?
Thanks again and sorry for the #noob# guestions....
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
cause Stock kernel still was not relased you have to simply flash EU Rom using stock TWRP and after you done you have to change to TWRP EU to make it working again .
We are waiting official sources from Xiaomi
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
I waited about 4 hours after submitting the application, 2 weeks is a maximum estimation.
knives of ice said:
just to make sure i'm understanding this correctly - there is no way to unlock this phone on the day you get it you have to apply and wait upwards of 2 weeks to be able to unlock it?
Click to expand...
Click to collapse
you have to wait few minutes or at last 24 hours to receive sms unlock approve
:good::good:
wolfgart said:
you have to wait few minutes or at last 24 hours to receive sms unlock approve
Click to expand...
Click to collapse
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
jim380 said:
I am facing the unlock stuck at 50% issue while trying to unlock the bootloader on this phone? any ideas? Thank you.
Click to expand...
Click to collapse
you have to Log On with your MIUI account on device too and the retry to unlock
---------- Post added at 07:43 AM ---------- Previous post was at 07:42 AM ----------
knives of ice said:
does anyone know if using TWRP manager will work to install TWRP after you have unlocked?
Click to expand...
Click to collapse
it works ! I can confirm. And it works using Flashify too
Team Win Recovery Project 3.6.1
{
"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"
}
Special Notes:
DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options)
KNOX will be tripped once you flash custom binaries to your phone. Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status
Samsung Firmware OTA (aka System Updates) will no longer work once you flash custom binaries. You can flash custom ROMs if you want to keep the OS up-to-date
All apps that use KNOX like Samsung Pay, Secure Folder and maybe more will no longer work
Download:
Recovery
VBMeta
Multidisabler
Changelog:
21.10.2021
Rebased kernel source to CUH4
16.06.2021
Rebased kernel source to CUC2
03.05.2020
Rebased kernel source to BTB8
25.04.2020
Rebased kernel source to ATA4
07.12.2019
Initial Release
Guide:
If you already have a custom recovery installed:
Boot to your custom recovery
Flash the recovery image
If you are starting from scratch:
Go to Developer Settings and enable "OEM Unlock" option
Power off the device and boot in download mode
In download mode, you will see the long press and volume up option to unlock the bootloader
Unlock the bootloader. That will wipe your device so be sure you made a backup of your data
After bootloader unlock, boot up the phone and make sure it is connected to the internet or it will trigger rmm prenormal
Setup the phone without google account and others
Reboot in download mode and flash the recovery and vbmeta images
Boot to TWRP
Format data in TWRP
Flash the Multidisabler zip
Now you can reboot
Contributors
ponces, geiti94, ianmacd
Source Code: https://github.com/TeamWin/android_device_samsung_a40
Kernel Source Code: https://github.com/ponces/android_kernel_samsung_universal7904
Reserved
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
bishsop said:
I'm really tempted to flash this TWRP and root my A40. Though I know Android 10 has been announced (at least in my region) for April 2020. Should I wait until then? My main concern is, if i flash it now, how easy will it be to upgrade to Android 10 then?
The only real thing I use root privileges for is to remove bloatware completely and edit the hosts file, so I can wait a few months. Also what about dm-verity? Are there any problems there?
Click to expand...
Click to collapse
The choice of waiting is only yours.
In my case I need this as I'm using a custom Treble ROM and not Samsung's firmware.
The ease to upgrade to Android 10 relies only on the your expertise on how to flash the original firmware using ODIN.
At the time of the upgrade you need to use ODIN to flash an original firmware from Android 9 to be able to fully restore the original behavior and flash Android 10.
As far as I'm concerned, DM-Verity is related with both DT and DTBO partitions and those partitions are not even touched during this process.
The ones that are changed are BOOT, RECOVERY and VBMETA to disable a few security procedures from Samsung to be able to flash and boot custom binaries.
Because of this, take in consideration the "Special Notes" section in the first post.
Nevertheless, if the need of changing the hosts file is to block ads, you can reach the same goal by using the "Private DNS" feature introduced in Android 9 as explained here.
costa11 said:
My question and can I use this recovery on ITV-A405FNXXU2ASK2-20191218161204?
Click to expand...
Click to collapse
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
ponces said:
As you can see in the first post, this TWRP version is for the firmware A405FNXXU2ASJ1 (October's update).
I am still waiting for Samsung to drop A405FNXXU2ASK2 (December's update) sources here to update TWRP.
I'll keep you posted when the sources drop and work on TWRP update begins.
Click to expand...
Click to collapse
So I tried to install this recovery on the ASK2 firmware and it worked, there is only one problem when it goes down the brightness does not return anymore remains low! Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
thank you again for your job
i just updated my rom to the SK2 (downloaded the rom, flashed it with Odin)
then installed you twrp (the SJ1 is OK)
then flashed with magisk manager the boot.img to Root the Rom
and then flashed the param.bin with a better boot logo
thank you so much for your job !!
costa11 said:
Then another thing I rooted with Magisk is it's not working, come up with an error and then I'll try to take a screenshot!
Click to expand...
Click to collapse
Magisk-Root is working for me.
I did this:
[*]Backup of ASJ1 with TWRP
[*]Complete odin flash of ASK1
[*]TWRP - ASJ1 - Version
[*]direct reboot into TWRP
[*]Format Data
[*]Flash Multidisabler
[*]Full Boot
[*]Install Magisk.APK from sd-card
[*]Reboot into TWRP
[*]Flash Magisk
[*]Full boot to check of root access => ok
[*]Reboot into TWRP
[*]Restore of ASJ1-Data
Everything working!
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
cioce said:
Thanks for the recovery, is working fine with latest ITV (Italian no brand) firmware, to have root is only simple necessary to flash latest Magisk ZIP via twrp (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
Click to expand...
Click to collapse
Can confirm it works with ATA4 (region DBT). Same procedure my post above. With restoring Data as last step there isn't anything lost as well... :good:
Be sure to enable usb debugging after flash of new firmware. Otherwise TWRP flash would fail...
:good:
Leak.dll said:
i have a big problem about twrp on my phone
I have followed this thread
But when i flash twrp (i have uncheck "reboot" on odin of course) i can't get access to the recovery mode, when i do power button + volume up it doesn't do nothing and show this :
...
(I have already unlock my boot loader)
I think its DM VERITY who block the access to recovery mode but i can't disable this, cause i can't get access to twrp :/
Thanks for any answers c:
Click to expand...
Click to collapse
I had some similar problem.
It was a wrong TWRP, I had to try 3 different ones until it finally worked (the one for AJ1 worked for me).
If you are in a bootloop you still can press Volume UP + DOWN and at the same time put the USB cable in when booting. This should set your phone into the download mode and you can flash TWRP or OS again.
Has anyone tried this TWRP build with ATB1 February patch version? It has increased BL version (2->3) so it is not possible to roll back to any older FW...
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
ruffyrisco said:
Magisk-Root is working for me.
I did this:
Backup of ASJ1 with TWRP
...
Click to expand...
Click to collapse
what TWRP is this and how did you manage to install it before being rooted?
toshibashi said:
what TWRP is this and how did you manage to install it before being rooted?
Click to expand...
Click to collapse
I used the modified TWRP from post #1: https://androidfilehost.com/?fid=4349826312261685733
ruffyrisco said:
From my information ATB1 is still the same security patch level as ATA4.
General question: How can I judge the BL version of the firmware?
Click to expand...
Click to collapse
Well, my info comes from samfw.com/firmware/SM-A405FN/TMZ, not sure how do they extract it.
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
(sorry about URL formatting, as a XDA newbie, I am no allowed to post URLs)
xorly said:
both ATB1 - samfw.com/firmware/SM-A405FN/TMZ/A405FNXXS3ATB1 and ATA4 - samfw.com/firmware/SM-A405FN/XEZ/A405FNXXU3ATA4 seems like BL (or some OTP bits, I am noob with android internals) bumped from 2 to 3.
Click to expand...
Click to collapse
As I mentioned earlier ATA4 firmware works fine with TRWP.
But I'm not sure if ATA4 has BL 3.
Does the digit 10 in the firmware number represents the BL?
ruffyrisco said:
But I'm not sure if ATA4 has BL 3.
Click to expand...
Click to collapse
Then reboot into Download mode (you have to do it manually, not via ADB command) and look into top left corner. On ATB1, one of last lines says
Code:
AP SWREV B:3 K:3 S:3
I assume that some fo those numbers (B?) is OTP number set by BL version.
ruffyrisco said:
Does the digit 10 in the firmware number represents the BL?
Click to expand...
Click to collapse
I am not sure which *10* do you mean. It looks like version prefix is bootloader version, number 3 in A405FNXXS3ATB1 or number 2 in A405FNXXU2ASK2. It is the only number which seems to corellate with BL version.
Also, now I can confirm that that this TWRP build (based on A405FNXXU2ASJ1) works with ATB1 firmware! (february sec. patch) Successfuly tested with Phhussons Android 10 GSI quack v213.
{
"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"
}
PixelExperience for Asus Max M1
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 10
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight(back)
Camcorder
Bluetooth
FMRadio
Fingerprint reader
Lights
Sound / vibration
Facelock
Known issues
MSM8917 variants
Telegram Group
Link
DON'T FLASH GAPPS, ALREADY INCLUDED
Download from Pixel Experience website
Translation
Help with project translation
Stay tuned
Our Telegram channel
Our blog
Build author/Device Maintainer: Saalim
Device Source code: https://github.com/PixelExperience-Devices
Source code: https://github.com/PixelExperience
ROM Developer: jhenrique09
XDA:DevDB Information
pixel-experience, ROM for the Asus ZenFone Max M1
Contributors
saalimsam
Source Code: https://github.com/pixelexperience-devices/device_asus_X00P
ROM OS Version: Android 11
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie firmware.
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-04-15
Created 2020-04-09
Last Updated 2020-10-12
Nice work ?
Any guides on how to unlock the bootloader and install TWRP?
Thanks in advance.
althafvly said:
Nice work
Click to expand...
Click to collapse
I am sure you will achieve the same with the Moto x play. You are the best!
manishurfmannu said:
Any guides on how to unlock the bootloader and install TWRP?
Thanks in advance.
Click to expand...
Click to collapse
download this apk and follow instructions to unlock bootloader
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE620KL/AsusLauncher_5.0.1.70_190801_generic.apk
you need to install twrp via fastboot . And download image from here.
https://twrp.me/asus/asuszenfonemaxm1.html
iamsaalim said:
download this apk and follow instructions to unlock bootloader
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE620KL/AsusLauncher_5.0.1.70_190801_generic.apk
you need to install twrp via fastboot . And download image from here.
https://twrp.me/asus/asuszenfonemaxm1.html
Click to expand...
Click to collapse
But the apk link is just launcher. I tierd installing it on the device but installation fails with the error "app not installed"
iamsaalim said:
download this apk and follow instructions to unlock bootloader
https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZE620KL/AsusLauncher_5.0.1.70_190801_generic.apk
you need to install twrp via fastboot . And download image from here.
https://twrp.me/asus/asuszenfonemaxm1.html
Click to expand...
Click to collapse
I had successfully unlocked the bootloader and installed TWRP. After flashing the latest build the device is encrypted and asks for a password every time I reboot the device & when I open the TWRP it also asks for a password to decrypt. So is there any way to remove the encryption?
manishurfmannu said:
I had successfully unlocked the bootloader and installed TWRP. After flashing the latest build the device is encrypted and asks for a password every time I reboot the device & when I open the TWRP it also asks for a password to decrypt. So is there any way to remove the encryption?
Click to expand...
Click to collapse
You can use your screen lock to decrypt the data, if it still doesn't work, format the data partition and flash magisk before first boot.
manishurfmannu said:
I had successfully unlocked the bootloader and installed TWRP. After flashing the latest build the device is encrypted and asks for a password every time I reboot the device & when I open the TWRP it also asks for a password to decrypt. So is there any way to remove the encryption?
Click to expand...
Click to collapse
Format data or use unofficial twrp
Which version of pixel experience should I install
10 or 10 plus?
Help me
saurabhw said:
Which version of pixel experience should I install
10 or 10 plus?
Help me
Click to expand...
Click to collapse
Is there ten plus??
raza231198 said:
Is there ten plus?
Click to expand...
Click to collapse
Yup there is ten plus, you can check on official website
saurabhw said:
Yup there is ten plus, you can check on official website
Click to expand...
Click to collapse
:/ Ask saalim he didn't give for testing ?
saurabhw said:
Yup there is ten plus, you can check on official website
Click to expand...
Click to collapse
There's no Plus version for this device go and check website yourself first.
I will try this as soon as possible: has the wifi reception, by any chance, been improved compared to stock rom? IRRC back in the days there was the "radio" part of the software that could be modded.
What camera app does it use? the stock Asus cam, gcam, or the aosp cam?
I got a new X00PD (ZB555) and I wanted to try putting this rom on it out of the box. I have done:
1) Unlocked bootloader via Asus apk
2) Booted into fastboot and flashed unofficial TWRP
3) Rebooted into TWRP.
4) Flashed twrp in twrp (I wasn't sure if this was needed or not)
5) Rebooted into recovery
6) Wiped dalvik, system, cache, data
7) Flashed Pixel Experience. TWRP says it was successful.
Here is where I have a problem. On reboot its a boot loop.
I've tried flashing this rom now 4 times, keeps giving me a boot loop. I just booted into fastboot and reflashed TWRP and then tried to flash the rom from there, still boot loop.
I have questions:
1) Did I do things right?
2) Could the message on TWRP's site have something to do with this "This device uses dm-verity! This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel."? I never got a request to allow system modification.
3) Yikes, what do I do now?
reao8890 said:
I got a new X00PD (ZB555) and I wanted to try putting this rom on it out of the box. I have done:
1) Unlocked bootloader via Asus apk
2) Booted into fastboot and flashed unofficial TWRP
3) Rebooted into TWRP.
4) Flashed twrp in twrp (I wasn't sure if this was needed or not)
5) Rebooted into recovery
6) Wiped dalvik, system, cache, data
7) Flashed Pixel Experience. TWRP says it was successful.
Here is where I have a problem. On reboot its a boot loop.
I've tried flashing this rom now 4 times, keeps giving me a boot loop. I just booted into fastboot and reflashed TWRP and then tried to flash the rom from there, still boot loop.
I have questions:
1) Did I do things right?
2) Could the message on TWRP's site have something to do with this "This device uses dm-verity! This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel."? I never got a request to allow system modification.
3) Yikes, what do I do now?
Click to expand...
Click to collapse
Have you msn8917 or msm8937 variant
raza231198 said:
Have you msn8917 or msm8937 variant
Click to expand...
Click to collapse
Uh oh, did not consider checking for that. Using 'getprop' in TWRP's terminal (had to search for this command), it says
[ro.board.platform]: [msm8937]
then it also says
[ro.boot.platformtype]: [msm8917]
Does that help or is that more confusing? Any other things I can do in fastboot or TWRP to produce better information?
Thank you so much for helping!
Edit: The exact model number of this phone is: ZB555KL-4G151TW but I can't find reference to this exact model number with websearches.
Edit2: On your Lingeage OS page it says to flash FIRMWARE-ASUS_X00P-WW-16.00.1906.411-user.zip. I never did this, should I do this for this rom too? Is it safe to flash a stock rom after putting on TWRP (I was about to try your ROM but wasn't sure if I could flash this stock firmware))? Thanks again!
raza231198 said:
Have you msn8917 or msm8937 variant
Click to expand...
Click to collapse
Ok I am like 85% sure this is msn8917. Does anyone know if this ROM works with this CPU?
TWRP , OrangeFox and Skyhawk for Samsung A12/M12 Exyons850
* 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
Click to expand...
Click to collapse
{
"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"
}
Custom Recovery
NOTE
##### NO RECOVERIES FOR U3 #####
check the baseband
A127FXXU2AUJ5
Bugs
MTP
Encryption
To Fix Encryption flash Multi disabler and Formact data
Installation
Unlock bootloader
Root with magisk
Flash .tar using odin
Downloads
TWRP
SHRP
Orange Fox
Multi disabler
Device Tree
Telegram :- @a127f_res
Thanks @physwizz for testing
Great Work
Instruction are here
[ROOT] [TWRP] [KERNEL] [GSI] for SM-A127f (a12s)
Root Method https://forum.xda-developers.com/t/root-for-all-exynos-850-devices.4367799/ Twrp and Kernel https://forum.xda-developers.com/t/custom-kernel-and-recoveries-for-m127f.4361841/ Latest twrp...
forum.xda-developers.com
Can m127f use my a127f Kernel?
physwizz said:
Can m127f use my a127f Kernel?
Click to expand...
Click to collapse
yes both have same chipset
(Sri Lanka) said:
yes both have same chipset
Click to expand...
Click to collapse
Nice
Is TWRP dependent in any way of Android version?
If so next question obviously would be:
For what Android version this TWRP belongs?
More detailed step-by-step instruction would be good to have, too.
Thank you in advance.
F308 said:
Is TWRP dependent in any way of Android version?
If so next question obviously would be:
For what Android version this TWRP belongs?
More detailed step-by-step instruction would be good to have, too.
Thank you in advance.
Click to expand...
Click to collapse
M12 7f or A127f
F308 said:
Is TWRP dependent in any way of Android version?
If so next question obviously would be:
For what Android version this TWRP belongs?
More detailed step-by-step instruction would be good to have, too.
Thank you in advance.
Click to expand...
Click to collapse
root the phone whith magisk
and intsatll the recovery.tar using odin and flash mulidisabler and formact data.
only for exyons850 not for mtk or qualcomm
F308 said:
Is TWRP dependent in any way of Android version?
If so next question obviously would be:
For what Android version this TWRP belongs?
More detailed step-by-step instruction would be good to have, too.
Thank you in advance.
Click to expand...
Click to collapse
Root and TWRP
1. Download firmware
2. Extract ap file.
3. Patch with magisk
4. Flash with Odin
5. Download recovery.img (you may need to Unzip the tar file.
6. Install TWRP app
7. Choose Install TWRP
8. Choose file to flash.(don't select device)
9. Select recovery.img.
Done
Thank you both.
F308 said:
Thank you both.
Click to expand...
Click to collapse
More detailed information in post #2
The updated recoveries from November 17 do not work on SM-127F/DSN: endless reboot loop again. The previous versions from November 13 worked fine. What's the matter with all the incompatibilities?
uluruman said:
The updated recoveries from November 17 do not work on SM-127F/DSN: endless reboot loop again. The previous versions from November 13 worked fine. What's the matter with all the incompatibilities?
Click to expand...
Click to collapse
1. Do you still have the previous ones?
2. Are you having any trouble with my kernel?
3. Should I build a kernel specifically for a127f/DSN
physwizz said:
1. Do you still have the previous ones?
2. Are you having any trouble with my kernel?
3. Should I build a kernel specifically for a127f/DSN
Click to expand...
Click to collapse
1. Yes. Luckily I still had them in the trash. They do work.
2. Will check this out, but first I have to install something like OrangeFox without breaking the OS loading process. Which requires Magisk patching of the whole AP, I suppose. Therefore I have to reassemble the AP with my new super.img. Anyways I'll report the final results.
3. Don't know yet. If I'll succeed with the step 2 will try your latest kernel (physwizz a12s kernel version 4).
By the way, multidisabler-samsung-3.1 does not work for me, causes a freeze on the last logo screen (with the red warning text), I guess that's when the kernel tries to boot.
uluruman said:
The updated recoveries from November 17 do not work on SM-127F/DSN: endless reboot loop again. The previous versions from November 13 worked fine. What's the matter with all the incompatibilities?
Click to expand...
Click to collapse
According to you old recoveries work for you. new recoveries not working. am i right. endless bootloop means, when you rebooted to system it will stuck in boot animation or when you try to boot in to recovery it will looping in samsung logo ?
(Sri Lanka) said:
According to you old recoveries work for you. new recoveries not working. am i right. endless bootloop means, when you rebooted to system it will stuck in boot animation or when you try to boot in to recovery it will looping in samsung logo ?
Click to expand...
Click to collapse
Correct, the old ones are working. The loop is a loop, not freezing. Yes, I'm getting to the logo (with the red warning text), then rather quickly a reboot, and all over again.
uluruman said:
Correct, the old ones are working. The loop is a loop, not freezing. Yes, I'm getting to the logo (with the red warning text), then rather quickly a reboot, and all over again.
Click to expand...
Click to collapse
can you send a picture of red warnigs, are you in telegram?
(Sri Lanka) said:
can you send a picture of red warnigs, are you in telegram?
Click to expand...
Click to collapse
They are unrelated. This is just a generic warning that the phone software has been replaced.
P.S.: No, I do not use Telegram. Any communication tool that requires personal information for registration (e.g. phone number) is against my vision of freedom of information.
uluruman said:
They are unrelated. This is just a generic warning that the phone software has been replaced.
P.S.: No, I do not use Telegram. Any communication tool that requires personal information for registration (e.g. phone number) is against my vision of freedom of information.
Click to expand...
Click to collapse
uluruman said:
They are unrelated. This is just a generic warning that the phone software has been replaced.
P.S.: No, I do not use Telegram. Any communication tool that requires personal information for registration (e.g. phone number) is against my vision of freedom of information.
Click to expand...
Click to collapse
what is the baseband version
(Sri Lanka) said:
what is the baseband version
Click to expand...
Click to collapse
A127FXXU3AUJ5. If that is the baseband version, I'm not quite sure.
{
"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.7.0 For Galaxy A42 5G
Disclaimer
Code:
*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.
Features:
Android 12 support
Decryption support
What's not working:
You tell me.
Downloads:
A42 5G: Download
Changelogs:
2023/01/24
Updated to TWRP 3.7.0 with A12.1 trees.
Fixed decryption.
Click to expand...
Click to collapse
2022/07/27 (Re-uploaded)
Fixed OTG.
Fixed Vibration.
Support NTFS.
Use LZMA to compress image.
Click to expand...
Click to collapse
2022/07/20
Fixed MTP.
Fixed Temperature display
Updated Kernel
Click to expand...
Click to collapse
How to install
Make sure your bootloader is already unlocked and OEM unlock is enabled, otherwise the installation will fail.
Download and install Samsung Drivers
Download the latest *.tar for your phone
Download Odin, from example from https://downloads.corsicanu.ro/samsung/
If not done before, flash disabled VBMeta with Odin in AP or CP slot (originally posted here).
Turn off your phone, connect it to PC and reboot to download mode by holding down Volume up, Volume down and power button at the same time.
Open Odin and check if your device is detected, then untick "Autoreboot" in its settings.
Put the tar file you downloaded into the AP tab
Click start and wait for the installation to finish, Odin will show PASS
Now hold down Power button and Volume down for about 10 seconds to force reboot the device
Immediately after the screen goes black release the keys and hold down Volume up and Power button at the same time until you enter TWRP (You may need to release the keys after about 20-30secs due to the "unlocked bootloader" warning)
If you properly followed all the steps you should now see the TWRP menu.
I HIGHLY recommend to flash multidisabler and services disabler right after you enter TWRP to disable forced encryption and stock recovery restoration.
If you're scared of doing something wrong, you can also follow the steps in this video
Donations
DONATE To Me
Sources:
A42 5G: https://github.com/TARKZiM/twrp_android_device_samsung_a42xq
Kernel: https://github.com/TARKZiM/android_kernel_samsung_sm7225
Credits:
TeamWin
@Velosh for the original TWRP trees
@Simon1511 for A52 device trees.
@corsicanu for updating multidisabler for A12 and providing download links for Odin, USB drivers, etc
Everyone else involved
Screenshots
I'm currently working on LineageOS 19 for this device, stay tuned.
tarkzim said:
I'm currently working on LineageOS 19 for this device, stay tuned.
Click to expand...
Click to collapse
GOOD NEWS
LineageOS 19 booted and running on A42 5G, check out here : THREAD
New build released
Fixed MTP.
Fixed Temperature display
Updated Kernel
New build released
Fixed OTG.
Fixed Vibration.
Support NTFS.
Use LZMA to compress image.
Why is my phone stuck on file analysis while flashing twrp? I tried flashing vbmeta disabler on both AP and CP slot
awesomellama3 said:
Why is my phone stuck on file analysis while flashing twrp? I tried flashing vbmeta disabler on both AP and CP slot
Click to expand...
Click to collapse
The .tar file of latest twrp build is corrupted, I just uploaded a new one.
Please try to download it again.
Oh thank you! I thought something was wrong with my phone, haha... atleast if anyone bought this phone for modding doesn't have this issue anymore.
I'm a bit of a paranoid person myself, and I was wondering if my phone is compatible with this. In your LOS ROM for the A42 5G, you specified it needs to be an a42xq, however my phone is specified as an a42xqeea, and not just a42xq. I paid a lot of money for this phone, but I really want to install a custom recovery, so a response would be appreciated.
Vuraniute said:
I'm a bit of a paranoid person myself, and I was wondering if my phone is compatible with this. In your LOS ROM for the A42 5G, you specified it needs to be an a42xq, however my phone is specified as an a42xqeea, and not just a42xq. I paid a lot of money for this phone, but I really want to install a custom recovery, so a response would be appreciated.
Click to expand...
Click to collapse
If you are able to unlock the bootloader, and prepared stock firmware before flashing, I will suggest you to try this.
tarkzim said:
If you are able to unlock the bootloader, and prepared stock firmware before flashing, I will suggest you to try this.
Click to expand...
Click to collapse
Bootloader is unlockable, just checked. The device is still running on stock firmware, I don't get what you mean by "prepared stock firmware before flashing", is there a way to backup the firmware before installing TWRP?
Vuraniute said:
Bootloader is unlockable, just checked. The device is still running on stock firmware, I don't get what you mean by "prepared stock firmware before flashing", is there a way to backup the firmware before installing TWRP?
Click to expand...
Click to collapse
There are some firmware download websites for samsung devices, you can find them and download the firmware for your device model.
tarkzim said:
There are some firmware download websites for samsung devices, you can find them and download the firmware for your device model.
Click to expand...
Click to collapse
Hello again, I was preparing to donwload everything and install TWRP today, until I noticed that this was intended for an SM-A426U, I have an SM-A426B, are you sure this will not brick my recovery in any way?
Vuraniute said:
Hello again, I was preparing to donwload everything and install TWRP today, until I noticed that this was intended for an SM-A426U, I have an SM-A426B, are you sure this will not brick my recovery in any way?
Click to expand...
Click to collapse
My device is exactly the SM-A426B and well tested.
As I said, if you have stock firmware files, you could restore everything if you want, including recovery partition.
So it won't brick your device.
tarkzim said:
My device is exactly the SM-A426B and well tested.
As I said, if you have stock firmware files, you could restore everything if you want, including recovery partition.
So it won't brick your device.
Click to expand...
Click to collapse
Thanks, downloading firmware and odin right now. I will report the results when done.
Hello I am glad that I found this ! I did the whole procedure and probably I have done something wrong in the last step . It boots into the stock recovery and not twrp ? I missed something ?
New build released
Updated to TWRP 3.7.0 with A12.1 trees.
Fixed decryption.
Does it support Android 13?
gud device can play many games in very high grafic