Related
TWRP Recovery 3.2.3-0 For Xiaomi Mi A2 (daisy) by TWRPBuilder
Code:
#include
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/
Welcome, all Mi A2 users, This is Lastest TWRP Recovery For your device By TWRPBuilder Team
CHANGELOG for 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
DownloadsXiaomi Mi A2 Recovery img
Sources:
Code:
[CENTER][URL="https://github.com/TwrpBuilder/android_device_xiaomi_daisy"][COLOR="bule"]Device tree[/COLOR][/URL]
[URL="https://github.com/TeamWin/Team-Win-Recovery-Project"][COLOR="bule"]TeamWin Github
[/COLOR][/URL][/CENTER]
How to install:
You must have fastboot installed on your pc and then:
Code:
adb reboot bootloader
fastboot boot recovery.img
Then flash img from the recovery
Notes:
You have to format data and disable force encryption in order to access data partition:
- Format data
- Flash Magisk DFE or DisableForceEncryption zip, attached below.
Don't Forget to Hit Thanks :good:
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
XDA:DevDB Information
[RECOVERY][UNOFFICIAL] TWRP for Xiaomi Mi A2 Lite (daisy) by TWRPBuilder, Tool/Utility for the Xiaomi Mi A2 Lite
Contributors
TwrpBuilder, yshalsager
Source Code: https://github.com/TwrpBuilder/android_device_xiaomi_daisy
Version Information
Status: Stable
Current Stable Version: 2
Stable Release Date: 2018-08-09
Created 2018-08-09
Last Updated 2018-08-18
Disable Force Encryption
Flash one of these files
Screenshots
Attached below
i install it and not boot on twrp, please fix it bro
Will i lost anything after formatting data?
krzygaj said:
Will i lost anything after formatting data?
Click to expand...
Click to collapse
Yes, you will lose all your data (music, video, documents, app, etc.).
BubuXP said:
Yes, you will lose all your data (music, video, documents, app, etc.).
Click to expand...
Click to collapse
Bubu, Seguendo la guida si riesce ad installare la recovery modificata correttamente?
Ho letto che, visto la nuova politica Google delle partizioni A e B, non funziona più fare semplicemente flash recovery blablabla.img
michaelsan1337 said:
Bubu, Seguendo la guida si riesce ad installare la recovery modificata correttamente?
Ho letto che, visto la nuova politica Google delle partizioni A e B, non funziona più fare semplicemente flash recovery blablabla.img
Click to expand...
Click to collapse
Non ho provato ancora questa TWRP, però so che è come dici, cioè non c'è più la partizione di recovery nei nuovi telefoni A/B quindi la custom recovery può essere avviata solo da PC tramite fastboot, non sarà più possibile lasciarla installata sul telefono pronta all'uso.
I didn't test this TWRP on my Mi A2 Lite, but you cannot install a custom recovery anymore on new phones with A/B partitioning scheme, because there isn't a recovery partition anymore. The only way to use a custom recovery is via fastboot with a PC.
EDIT: looking at the TWRP threads for Mi A1 (very similar device), it's possible to install TWRP by adding it to the boot partition (more or less how Magisk is installed).
BubuXP said:
Non ho provato ancora questa TWRP, però so che è come dici, cioè non c'è più la partizione di recovery nei nuovi telefoni A/B quindi la custom recovery può essere avviata solo da PC tramite fastboot, non sar
Click to expand...
Click to collapse
Doesn't boot.
doesn't boot into recovery.img
when i enter:
fastboot boot recovery.img (tried it with TWRP-3.2.3-TwrpBuilder-daisy-20180809.img)
just the normal android starts and not the twrp recovery
cmd history:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot TWRP-3.2.3-TwrpBui
lder-daisy-20180809.img
downloading 'boot.img'...
OKAY [ 0.930s]
booting...
OKAY [ 0.595s]
finished. total time: 1.531s
C:\Program Files (x86)\Minimal ADB and Fastboot>
fizze17 said:
when i enter:
fastboot boot recovery.img (tried it with TWRP-3.2.3-TwrpBuilder-daisy-20180809.img)
just the normal android starts and not the twrp recovery
(…)
Click to expand...
Click to collapse
Can confirm this. Doesn't work.
I don't want to disparage any hard working dev's efforts, but does anyone actually check these things?
We get a "stable" version and install instructions. But if it's impossible to boot through fastboot, it's impossible to test. So how can it be stable?
And if there's no recovery partition, it's impossible to install. So why do we get install instructions?
Is there any evidence that someone was able to disable forced encryption? I couldn't through a modified boot.img.
Curunir said:
Can confirm this. Doesn't work.
I don't want to disparage any hard working dev's efforts, but does anyone actually check these things?
We get a "stable" version and install instructions. But if it's impossible to boot through fastboot, it's impossible to test. So how can it be stable?
And if there's no recovery partition, it's impossible to install. So why do we get install instructions?
Is there any evidence that someone was able to disable forced encryption? I couldn't through a modified boot.img.
Click to expand...
Click to collapse
I was wrong in the previous posts, actually it seems that TWRP could be installed in the boot partition, by modifying it (just like Magisk does).
I checked the info in the Mi A1 forum, as the device is very similar to ours.
But if the TWRP doesn't boot via fastboot, it means it doesn't work. Probably OP compiled the code automatically, without testing it against the device.
EDIT 1: in fact, as they say on their presentation post:
We do not guarantee all images will work as expected. It might even not boot.
Click to expand...
Click to collapse
EDIT 2: finally I tested this, and the result is the same as the other users: it's not booting.
But instead it succeeded to remove Magisk somehow. It's because the phone has booted with the TWRP boot image, not with the Magisk boot.img saved in the phone. In fact, rebooting the phone brings back Magisk.
BubuXP said:
EDIT 2: finally I tested this, and the result is the same as the other users: it's not booting.
But instead it succeeded to remove Magisk somehow. It's because the phone has booted with the TWRP boot image, not with the Magisk boot.img saved in the phone. In fact, rebooting the phone brings back Magisk.
Click to expand...
Click to collapse
I can confirm this. Sme behavior for me. Somehow,it also removed the password to boot Android. My phone still show as encrypted but is not asking the password anymore to boot, which is weird.
BubuXP said:
I was wrong in the previous posts, actually it seems that TWRP could be installed in the boot partition, by modifying it (just like Magisk does).
I checked the info in the Mi A1 forum, as the device is very similar to ours.
But if the TWRP doesn't boot via fastboot, it means it doesn't work. Probably OP compiled the code automatically, without testing it against the device.
EDIT 1: in fact, as they say on their presentation post:
EDIT 2: finally I tested this, and the result is the same as the other users: it's not booting.
But instead it succeeded to remove Magisk somehow. It's because the phone has booted with the TWRP boot image, not with the Magisk boot.img saved in the phone. In fact, rebooting the phone brings back Magisk.
Click to expand...
Click to collapse
As I don't have the device, all testing is the Requester responsibility.
I didn't publish it before testing, he tested and reporting It's working
Anyway, I'll look into it within a few days.
yshalsager said:
As I don't have the device, all testing is the Requester responsibility.
I didn't publish it before testing, he tested and reporting It's working
Anyway, I'll look into it within a few days.
Click to expand...
Click to collapse
Thanks for clarifying. I hope it's possible to fix it!
Are there any news about a twrp that works?
alonsosjumper said:
Are there any news about a twrp that works?
Click to expand...
Click to collapse
Curunir said:
Thanks for clarifying. I hope it's possible to fix it!
Click to expand...
Click to collapse
Here's a working version!
Everything is fixed except data decryption
https://github.com/TwrpBuilder/android_device_xiaomi_daisy/releases
Thanks @Mashudi97 for testing
whats the meaning of custom recovery on this phone while there are no custom rom? just curious
machine1104 said:
whats the meaning of custom recovery on this phone while there are no custom rom? just curious
Click to expand...
Click to collapse
You can root with magisk, flash Project treble GSIs and backup your device
So I tried out the Xiaomi.eu rom, and it bugs me, that now my Poco F3 is called Redmi K40. For example when I connect the phone to my pc it shows up as Redmi K40. I know its not a big deal, but it bugs me Is there a way to change it? I know you can change the device name, but it will only change like the bluetooth name of it. I want the whole phone to be called Poco F3.
REBRANDING IS VERY RISKY
The chance of a bricked device is large.
You don't need to rebrand to do what you want (you just need to modify the build.prop file):
root your device (unlock bootloader, flash TWRP and then flash magisk). Then you can use a build.prop editor and edit ro.prop.device or something similar
Okay, thanks for the advice! I will try it out.
Robert314 said:
REBRANDING IS VERY RISKY
The chance of a bricked device is large.
You don't need to rebrand to do what you want (you just need to modify the build.prop file):
root your device (unlock bootloader, flash TWRP and then flash magisk). Then you can use a build.prop editor and edit ro.prop.device or something similar
Click to expand...
Click to collapse
Which lines do i need to change so it looks like S21 ultra ?
I developed a magisk module that just install and the device name is changed to POCO F3. I also developed a module that does the same but also has a Mi 10T Pro pach that unlocks superior graphics in games.
Sorry for my bad english.
(Desenvolvi um módulo do magisk que basta instalar que o nome do dispositivo é alterado para POCO F3. Também desenvolvi um módulo que faz o mesmo mas também tem junto um pach do Mi 10T Pro que desbloqueia gráficos superiores em jogos.)
Install Termux from PlayStore and open it
Type su and press enter
make root permissions to Termux
Type props and press enter
Enter option: 1 and press enter
Exactly type a valid device fingerprint into the command line and press enter the fingerprint according to your model
also read this
[GUIDE][POCO F2 Pro] How to pass SafetyNet on Android 11 and Magisk
1. Install the latest weekly or global firmware in twrp. (without magisk) 2. reboot. 3. complete the first setup. 4. reboot to recovery. 5. install latest magisk canary (now the latest stable version is v20.4, but need higher) 6. reboot. 7. enable magiskhide and hide magisk manager. 8. install...
xiaomi.eu
Premise: I performed all the operations by raspberry (I have driver problems on windows).
Today I decided to install the official twrp for my mi 11 lite 5g (renoire); and then install the MiuiMix android 12 rom in fastboot.
I download the img file from the official site, put it on a key, connect the fastboot phone to my raspberry (after giving it usb debugging permissions) and launch the command:
"fastboot devices" from the terminal.
"fastboot random number" ... ok phone recognized.
"fastboot flash recovery /home/meda/usb/twrp.img" ...
the recovery flash starts.
"Sending recovery OKAY"
"Writing recovery FAILED (remote '(recovery_a) No such partition')"
"fastboot: error: Command Failed"
Do you know what happened? and how can I solve?
C0DEX0 said:
Premise: I performed all the operations by raspberry (I have driver problems on windows).
Today I decided to install the official twrp for my mi 11 lite 5g (renoire); and then install the MiuiMix android 12 rom in fastboot.
I download the img file from the official site, put it on a key, connect the fastboot phone to my raspberry (after giving it usb debugging permissions) and launch the command:
"fastboot devices" from the terminal.
"fastboot random number" ... ok phone recognized.
"fastboot flash recovery /home/meda/usb/twrp.img" ...
the recovery flash starts.
"Sending recovery OKAY"
"Writing recovery FAILED (remote '(recovery_a) No such partition')"
"fastboot: error: Command Failed"
Do you know what happened? and how can I solve?
Click to expand...
Click to collapse
dude your wrong woth your command fastboot boot ****.img because mi 11x has a/b partitions you need to first boot it and then install via recovery ramdisk
TeckySairam said:
amico, hai sbagliato con il tuo comando fastboot boot ****.img perché mi 11x ha partizioni a/b devi prima avviarlo e poi installarlo tramite recovery ramdisk
Click to expand...
Click to collapse
moddo i miei telefono da 4 anni ma non ho mai sentito parlare di questa cosa, potresti spiegarti meglio gentilmente?
Okay so, I followed this guide step by step and everything worked until:
Once I sent the command "fastboot boot twrp.img", and navigated to the twrp to get to the zip file that is needed to not have the recovery, I noticed that there is no trace of the internal memory (where I had just downloaded the aforementioned file ).
I thought "okay the download on a usb stick with usb-c connection and the meat from the" NO. HE DOESN'T EVEN SEE THE KEY.
I don't know how to do it, I can't get the twrp the phone memory can't see me
C0DEX0 said:
Okay so, I followed this guide step by step and everything worked until:
Once I sent the command "fastboot boot twrp.img", and navigated to the twrp to get to the zip file that is needed to not have the recovery, I noticed that there is no trace of the internal memory (where I had just downloaded the aforementioned file ).
I thought "okay the download on a usb stick with usb-c connection and the meat from the" NO. HE DOESN'T EVEN SEE THE KEY.
I don't know how to do it, I can't get the twrp the phone memory can't see me
Click to expand...
Click to collapse
Hi, first you are on the wrong section, the correct one for your phone model is this:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Where maybe you will find the answer to your question.
I can advise you to follow the instructions that you find on the official twrp website to the letter:
Xiaomi Mi 11 lite 5G
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
RollDload said:
Ciao, prima sei nella sezione sbagliata, quella corretta per il tuo modello di telefono è questa:
[RECOVERY] [11] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Dove forse troverai la risposta alla tua domanda.
Posso consigliarti di seguire alla lettera le indicazioni che trovi sul sito ufficiale di twrp:
Xiaomi Mi 11 lite 5G
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
Click to expand...
Click to collapse
hello thanks for your answer, I followed the guide you had left me (the official twrp and it worked) (amazing how I did not see it alone). But although I managed to install the recovery correctly, I still have the problem that does not show me the files of the phone (eg download folder, DCMI etc...). Even by connecting a usb. does not detect it, keeps showing me 0Mb on each partition
C0DEX0 said:
hello thanks for your answer, I followed the guide you had left me (the official twrp and it worked) (amazing how I did not see it alone). But although I managed to install the recovery correctly, I still have the problem that does not show me the files of the phone (eg download folder, DCMI etc...). Even by connecting a usb. does not detect it, keeps showing me 0Mb on each partition
Click to expand...
Click to collapse
Very good!
What rom did you flash? Android 11 or 12?
It could solve, on android 11, complete the initial configuration after flashing the rom with data format. Also try disabling pin \ password \ fingerprint as a screen lock. Or check the mtp driver in the raspberry.
With Android 12 as far as I know this is normal because decryption does not work yet, and it is not fully supported.
RollDload said:
Molto bene!
Che rom hai flashato? Android 11 o 12?
Potrebbe risolvere, su Android 11, completare la configurazione iniziale dopo aver flashato la rom con il formato dei dati. Prova anche a disabilitare pin \ password \ fingerprint come blocco schermo. Oppure controlla il driver mtp nel lampone.
Con Android 12, per quanto ne so, è normale perché la decrittazione non funziona ancora e non è completamente supportata.
Click to expand...
Click to collapse
here's why... I installed the MiuiMix, fastboot version android 12. Is it known about how much it will affect before they resolve? will one month be enough?
C0DEX0 said:
ecco perché... ho installato il MiuiMix, versione fastboot Android 12. Si sa quanto influenzerà prima che si risolvano? basterà un mese?
Click to expand...
Click to collapse
Hopefully soon! But having two different phones, I don't know, I haven't researched the model you have mi 11 lite, I have poco F3, so they have two different development paths. I recommend that you deepen your research on the section dedicated to your phone, here.
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
reserved
Arobase40 said:
Ok, I feel happy for you you succeeded to root your phone with your camera working and you pass the SafetyNet test by activating Zygist with safetynet-fix v2.2.1, but what have you done differently from my guide as you as you just got updated information from my thread ?
You passed SafetyNet test and so what next ???
Have you got Samsung Secure Folder, Samsung Health or Samsung Pay working or such other protected Samsung apps ???
Are you getting Xprivacylua or AfWall+ (may be this one but not sure) working ???
Firefds kit [R] is not yet update to be compatible with Android 12, so it only partially works...
On my Galaxy Note 9, I didn't pass SafetyNet test, but Samsung Secure Folder, Google pay, Samsung Health are fully working... ^^
Samsung Pay is working but only with a Samsung Watch...
With another configuration I passed SafetyNet test but all above apps aren't working at all !!! ^^
I don't mind you created another thread and another guide on how to root the A528B but what is the interest if you don't explain how you improved mine and what new features you got ???
Click to expand...
Click to collapse
A. I didn't read your guide since your guide openly says it doesn't work with camera
B. I needed camera so I created my own guide where the camera works and it is here for everyone to read
testestestest said:
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
Click to expand...
Click to collapse
Ok, I confirm this works!! Way to go sir. Thanks so much and I encourage everyone to do this method. WooHoo
Arobase40 said:
Ok but does it changes anything since my post #218 of my own guide ?
Click to expand...
Click to collapse
not that i can tell
Arobase40 said:
UPDATED : How to root Galaxy A52S 5G (SM-A528B)
This is a highly updated tutorial on how to root the Galaxy A52S 5G (SM-A528B) phone based on new version of Magisk and from feedbacks I received from users after the release of the first guide version ! ;) This guide should work with other...
forum.xda-developers.com
As I was myself trying to use Zygist with SafetyNet 2.2.1 version even though I didn't mention it explicitely as Safetynet 2.2.1 is only working with Zygist ?
"Ok, nice try mate but Zygisk-LSPosed is even worse !!!
It broke FoxMagiskModuleManager when Zygisk-LSPosed has very poor modules list. It broke AfWall+ and it partially broke Firefds kit and no progress at all with Samsung apps !!!"
Does this still apply ?
Click to expand...
Click to collapse
yes as far as lsposed goes, never used the fox app or afwall so can't say. no gravity box for android 12 yet
Arobase40 said:
So that means that since my post #218 no one with failed camera has installed SafetyNet Fix 2.2.1 with Zygist and no one has checked if that has an impact on the camera, and thus no report to me ??? lol
I just remind you that my camera has always been working so I couldn't expected any changes on this aspect... ^^
Finally, if my guide offered "limited root", this one offers even more limited one as with the exception of AdAway what this root stands for if you can't at least protect your privacy ???
Click to expand...
Click to collapse
you are lucky enough to be in a region that allows the camera to function while boot loader is unlocked
One thing I've noticed, after a restart the camera fails until closing it and killing the app in recent apps, then it works.
testestestest said:
Guys, I DID IT !!!!
Working Samsung A52s (SM-A528B/DS) with Unlocked Bootloader, Rooted (Magisk), Passing SafetyNet and WORKING CAMERA (yaaay).
Problem is that I have no idea how I did it, because it was 3 days of flashing, patching, reinstalling and phone bricking too (unfortunately).
I am attaching a screenshot I did with the phone while writing this post in Word. Someone wanted screenshots in split screen as a proof so.. boom, here ya go.
I have a lot of pictures that I made in last 3 days, so I will try to write some more detailed instructions soon. But now at least try this:
This should work for anyone, even people without working camera after unlocking bootloader
1. Download latest Firmware and Odin from samfw.com (don’t know why but these was only one that worked for me, bricked my phone earlier with different fw)
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
4. Unlock bootloader (first in developer settings, then in the download mode)
5. Reboot
6. Go to Download mode (You should see OEM: OFF (U))
7. Flash with Odin all the Firmware files you downloaded, but to AP put the patched file
8. Reboot
9. Go to magisk, do what he wants, reboot, in settings activate seamless host, activate Zygisk, reboot, download and install module kdrag0n’s safetynet-fix v2.2.1 (https://github.com/kdrag0n/safetynet-fix/releases)
10. reboot
11. yaaay
UPDATE: Ok, It seems that the Camera software will fail after reboot once. When you close it and open it again, it works.
CONFIRMED: I had to reflash after trying some TWRP and now I can confirm that patching the "safetynet-fix v2.2.1" will allow you to use the camera after one run. The Samsung Cam App will fail on the first run, so when you kill it in the app switcher and run again, it works in a normal way (switching cameras, front/back and everyhing).
Click to expand...
Click to collapse
thank you very much )))) I will try this weekend!
Guys, can anybody explain to me , why Samsung is apparently making it so hard for the customers to root their devices? Is it a problem with Samsung or with Magisk, or both?
Not being able to root via Magisk is a real dealbreaker to this otherwise well-specced phone (at least it is to me!).
Going to try this method with Android 11 using Magisk 24.3 and safety net 2.2.1 which I hope will allow the camera to work also.
Edit: It works with android 11.
Arobase40 said:
Why wouldn't it work with Android 11 as it is not related ???
You mean you downgraded to Android 11 and got stuck with a very old security patch just to get GravityBox and probably with Firefds Kit [R] working ??? lol
Click to expand...
Click to collapse
Yes, yes and yes. LOL and better battery life too
I've had no bootloops when changing things FireFDS and I'm glad to have a working gravity box... I'll report battery after a few days.
testestestest said:
Guys, I DID IT !!!!
Click to expand...
Click to collapse
Hi, I'm new here and I bought the A528B, I don't speak English and I use google translate... maybe this is asking too much but a step by step video would be too much to ask? having to translate it costs me a lot trying to follow the guide...
I don't understand how I have to do to be able to root it and have the camera working
bobfrantic said:
Ok, confirmo que esto funciona!! Bien hecho señor. Muchas gracias y animo a todos a hacer Desbloquee el gestor de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)
Click to expand...
Click to collapse
testestestest said:
Chicos, LO HICE!!!!
Samsung A52s (SM-A528B/DS) en funcionamiento con cargador de arranque desbloqueado, rooteado (Magisk), pasando SafetyNet y CÁMARA DE TRABAJO (yaaay).
El problema es que no tengo idea de cómo lo hice, porque fueron 3 días de flashear, parchear, reinstalar y bloquear el teléfono también (desafortunadamente).
Adjunto una captura de pantalla que hice con el teléfono mientras escribía esta publicación en Word. Alguien quería capturas de pantalla en pantalla dividida como prueba, así que... boom, aquí tienes.
Tengo muchas fotos que hice en los últimos 3 días, así que intentaré escribir algunas instrucciones más detalladas pronto. Pero ahora al menos prueba esto:
Esto debería funcionar para cualquier persona, incluso para las personas que no tendrán una cámara en funcionamiento después de desbloquear el gestor de arranque.
1. Descargue el último firmware y Odin de samfw.com (no sé por qué, pero estos fueron solo uno que se cubrieron para mí, bloquearon mi teléfono antes con un firmware diferente)
2. Descomprima el firmware descargado y copie AP a un teléfono con Magisk 24.1
3. Use la aplicación Magisk para parchear el archivo AP y descárguelo nuevamente a la PC
4. Desbloquee el cargador de arranque (primero en la configuración del desarrollador, luego en el modo de descarga)
5. Reiniciar
6. Vaya al modo de descarga (debería ver OEM: APAGADO (U))
7. Flashee con Odin todos los archivos de Firmware que descargó, pero a AP puso el archivo parcheado
8. Reiniciar
9. Vaya a magisk, haga lo que quiera, reinicie, en la configuración active el host integrado, active Zygisk, reinicie, descargue e instale el módulo kdrag0n's safetynet-fix v2.2.1 ( https://github.com/kdrag0n/safetynet -fix/ lanzamientos )
10. reiniciar
11. siiii
ACTUALIZACIÓN: Ok, parece que el software de la cámara fallará después de reiniciar una vez. Cuando lo cierras y lo abres de nuevo, funciona.
CONFIRMADO: Tuve que volver a flashear después de probar TWRP y ahora puedo confirmar que parchear "safetynet-fix v2.2.1" te permitirá usar la cámara después de una ejecución. La aplicación Samsung Cam fallará en la primera ejecución, por lo que cuando la elimine en el conmutador de aplicaciones y vuelva a ejecutarla, funcionará de manera normal (cambiando de cámara, frontal/trasera y todo).
Click to expand...
Click to collapse
EL DESBLOQUEO DE ARRANQUE ES ANTES O DESPUES DE PARCHEAR EL AP
Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.
ch3mn3y said:
Do I really need to patch whole AP?
Tried with only boot, vbmeta, vendor and dtbo, but bootloop was the only result.
Click to expand...
Click to collapse
Well then, there you go. You got bootloop for not following the instructions
Did i understand right?
2. Unpack downloaded firmware and copy AP to a phone with Magisk 24.1
3. Use Magisk app to patch the AP file and download it back to PC
Click to expand...
Click to collapse
These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?
luffy786 said:
Did i understand right?
These steps are requiring a mobile with Magisk installed on it to patch the AP?
If yes, is there any other option, if i have only a A52s 5G ?
Click to expand...
Click to collapse
You can install the Magisk app without being rooted. It's an app like any other app, you simply won't have root access. So install it on your A52s 5G and patch your files with it.
Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?
BlueChris said:
Guys can someone remind me what i need to do to make smartview working? I need to hide something from root?
Click to expand...
Click to collapse
Well, I added these 2 lines:
wlan.wfd.hdcp=disable
wifi.interface=wlan0
On the following files:
product/etc/build.prop
system/build.prop
system/system_ext/etc/build.prop
vendor/build.prop
vendor/default.prop
I'm pretty sure not all of them are needed but I'm too lazy to figure out which prop file really needs it lmao if I had to take a guess I'd say either vendor build.prop or default.prop, who knows.
Hello XDA community!
My Motorola Moto g60 phone is bricked i.e. flashing is locked in fastboot mode and I cannot install a new ROM without entering into EDL mode.
Does anyone know how to enter EDL mode for Moto g60?
KayaNN said:
Hello XDA community!
My Motorola Moto g60 phone is bricked i.e. flashing is locked in fastboot mode and I cannot install a new ROM without entering into EDL mode.
Does anyone know how to enter EDL mode for Moto g60?
Click to expand...
Click to collapse
Unfortunately, there's no way for that. Did you find a solution though? My phone is in the exact same condition.
ankurpandeyvns said:
Unfortunately, there's no way for that. Did you find a solution though? My phone is in the exact same condition.
Click to expand...
Click to collapse
posted in this thread - https://forum.xda-developers.com/t/no-operating-system-found-brick.4422035/post-87036557
The technician has yet to buy the JTAG boot tool
KayaNN said:
posted in this thread - https://forum.xda-developers.com/t/no-operating-system-found-brick.4422035/post-87036557
The technician has yet to buy the JTAG boot tool
Click to expand...
Click to collapse
I found a shop here in bangalore named next level repair. These guys have all the tools but they still cannot recover the phone. Motherboard replacement is the only solution they have right now.
A method can be adopted, you can test it if the device is soft brick/hard bricked,(as your device requirements) then there is no harm in taking this remedy, collect information about it from the internet, I am telling you the way which is like this:-
Download:-
Qualcomm QDLoader HS-USB 9008 Driver for x64 or 32
Motorola device manager
Motorola USB driver
ADB driver
Stock firmware
Optional:- Blankflash file for honip according to your build no. [[ if device does not turn on fastboot or recovery mode in any mode just read as black dead screen.When the device is not detected by anyone, try to get the test point detected by sort and use blank flash only when needed.After that, if needed, after blank flash, device will open in boot loader mode or fastbood mode. The Boot Loader Mode menu will appear on device. ]]
Info:- Make sure that your device is getting deducted in the computer or not.
Find the test point in the motherboard of the device and try to shorten it, this information is available on the internet, Google about it that, where is test point in mother board. This method is quite a tricky, again saying tricky, sometimes the test point is supported along with attaching it to the USB device, sometimes it has been seen that even after attaching the USB, you can get the test point shot. It may not be a problem if this method is not successful in a couple of times. Try it PC will detect EDL mode.
When your device is not detected and PC detects your mobile after shorting the test point, It means EDL mode is working. After that you will be able to turn it on by flashing the stock firmware.
RajivShastri king said:
A method can be adopted, you can test it if the device is soft brick/hard bricked,(as your device requirements) then there is no harm in taking this remedy, collect information about it from the internet, I am telling you the way which is like this:-
Download:-
Qualcomm QDLoader HS-USB 9008 Driver for x64 or 32
Motorola device manager
Motorola USB driver
ADB driver
Stock firmware
Optional:- Blankflash file for honip according to your build no. [[ if device does not turn on fastboot or recovery mode in any mode just read as black dead screen.When the device is not detected by anyone, try to get the test point detected by sort and use blank flash only when needed.After that, if needed, after blank flash, device will open in boot loader mode or fastbood mode. The Boot Loader Mode menu will appear on device. ]]
Info:- Make sure that your device is getting deducted in the computer or not.
Find the test point in the motherboard of the device and try to shorten it, this information is available on the internet, Google about it that, where is test point in mother board. This method is quite a tricky, again saying tricky, sometimes the test point is supported along with attaching it to the USB device, sometimes it has been seen that even after attaching the USB, you can get the test point shot. It may not be a problem if this method is not successful in a couple of times. Try it PC will detect EDL mode.
When your device is not detected and PC detects your mobile after shorting the test point, It means EDL mode is working. After that you will be able to turn it on by flashing the stock firmware.
Click to expand...
Click to collapse
Thanks for the reply.
The technician could not find a test point on the motherboard.. We haven't found a way to force Motog60 into EDL mode yet.
ankurpandeyvns said:
I found a shop here in bangalore named next level repair. These guys have all the tools but they still cannot recover the phone. Motherboard replacement is the only solution they have right now.
Click to expand...
Click to collapse
Replacing motherboard was what the authentic Lenovo dealers had given to me as the only solution. That would cost about 3/4th the phone's original price.
I still have hopes that the technician I know might be able to perform a boot repair using the JTag boot tool that I had mentioned in the earlier posts. I'll post here immediately when its done, along with the complete step by step solution.
Maybe this video can be of some use to you because this video matches 80% of your problem, even if it did not work, then it will definitely increase your knowledge.
Try to see if something from here could help. Unless you already tried that. In which case, I don't know what else to recommend you.
Also, if you have TWRP installed, that seems to have an option to boot into EDL.
However, I'm curious how did you get in this scenario to begin with.
arsradu said:
Try to see if something from here could help. Unless you already tried that. In which case, I don't know what else to recommend you.
Also, if you have TWRP installed, that seems to have an option to boot into EDL.
However, I'm curious how did you get in this scenario to begin with.
Click to expand...
Click to collapse
I also very curious to know about result, but he must has to search about edl point. I was also stuck in this kind of problem once, But the theoretical method was all in vain. All the technicians were useless. But at last my phone booted up but I didn't even understand how it booted up. only a miracle. After getting frustrated all over the place, I used to try again and again whenever I got time, even if it was 5 minutes, I would try to flash by taking test point shots and on the 7th or 8th day my device booted in bootloader mode.
But in this case the main role will be that of Qualcomm QDLoader HS-USB 9008 Driver. This driver is designed to working + bring interface to EDL mode. After installing this driver, many times users think that the driver is installed but, it is not actually installed and is not working inside, so it is necessary to install the driver properly and needs verify. I have posted these all in his conversation section (regarding installation) pdf. This pdf also discusses some commands that forcefully brings in EDL mode. But I don't think that command will work because I don't know if their mobile has USB debugging on or not. According to me and from my knowledge/understanding this is the way to get them back in boot>>
Find edl point/test point>>short & same time attatch usb cable> pc shows device>mobile screen greets in fastboot mode, than quick flash fastboot rom with double click on .bat file
If no recovery/No bootloader mode/only dead black screen than blank flash with same version.
Things to remember before flashing ROM:-
Info:- If one have the locked bootloader then one can only install the firmware with a version equal to or higher than the version that is already on the device. In that case If one have the bootloader locked, if one wants to install a previous version or a downgrade, it is necessary to unlock the bootloader because if one try to install a previous version with the bootloader locked, there is a high chance of bricking.
www.youtube.com/watch?v=DtRZkCyp9do
Motog60/40 edl point
RajivShastri king said:
Motog60/40 edl point
Click to expand...
Click to collapse
Thanks a lot for this - I'll show this to the technician and see if it works
KayaNN said:
Thanks a lot for this - I'll show this to the technician and see if it works
Click to expand...
Click to collapse
You are welcome!!! I'm glad that, I could be of some use to you.
RajivShastri king said:
Motog60/40 edl point
Click to expand...
Click to collapse
Thanks Sir, I also have same issue and opened my G60 but above images does not match with G60 model I purchased from flipkart India. Anyone can help me to find EDL points on G60 model
asdrhyme said:
Thanks Sir, I also have same issue and opened my G60 but above images does not match with G60 model I purchased from flipkart India. Anyone can help me to find EDL points on G60 model
Click to expand...
Click to collapse
I'm not sure EDL will work with a locked bootloader.
asdrhyme said:
Thanks Sir, I also have same issue and opened my G60 but above images does not match with G60 model I purchased from flipkart India. Anyone can help me to find EDL points on G60 model
Click to expand...
Click to collapse
There's no solution to it that you can do in home. I got my device fixed at Next Level Repair in Bangalore. They replaced the UFS chip on my phone. That's the only solution
RajivShastri king said:
Motog60/40 punto edl
Click to expand...
Click to collapse
Buenas tardes,
RajivShastri king said:
A method can be adopted, you can test it if the device is soft brick/hard bricked,(as your device requirements) then there is no harm in taking this remedy, collect information about it from the internet, I am telling you the way which is like this:-
Download:-
Qualcomm QDLoader HS-USB 9008 Driver for x64 or 32
Motorola device manager
Motorola USB driver
ADB driver
Stock firmware
Optional:- Blankflash file for honip according to your build no. [[ if device does not turn on fastboot or recovery mode in any mode just read as black dead screen.When the device is not detected by anyone, try to get the test point detected by sort and use blank flash only when needed.After that, if needed, after blank flash, device will open in boot loader mode or fastbood mode. The Boot Loader Mode menu will appear on device. ]]
Info:- Make sure that your device is getting deducted in the computer or not.
Find the test point in the motherboard of the device and try to shorten it, this information is available on the internet, Google about it that, where is test point in mother board. This method is quite a tricky, again saying tricky, sometimes the test point is supported along with attaching it to the USB device, sometimes it has been seen that even after attaching the USB, you can get the test point shot. It may not be a problem if this method is not successful in a couple of times. Try it PC will detect EDL mode.
When your device is not detected and PC detects your mobile after shorting the test point, It means EDL mode is working. After that you will be able to turn it on by flashing the stock firmware.
Click to expand...
Click to collapse
-Escrito en español
Buenas tardes, yo también tengo el problema de tener el teléfono "brikeado", mire el post completo y observe que encontro los punto "EDL" del Motorola G60"XT2135-1. Mañana voy a realizar el procedimiento solo necesito configurar correctamente mi "QUALCOMM" para no tener inconvenientes , me podría pasar por este medio la dirección web para descargar los "PDF" para empezar a preparar mi computadora.
-Translated into english by google translator
Good afternoon, I also have the problem of having the phone "bricked", look at the entire post and see that I found the "EDL" point of the Motorola G60 "XT2135-1. Tomorrow I am going to carry out the procedure, I just need to configure my "QUALCOMM" correctly "In order not to have inconveniences, you could send me the web address to download the "PDF" to start preparing my computer.
RajivShastri king said:
I also very curious to know about result, but he must has to search about edl point. I was also stuck in this kind of problem once, But the theoretical method was all in vain. All the technicians were useless. But at last my phone booted up but I didn't even understand how it booted up. only a miracle. After getting frustrated all over the place, I used to try again and again whenever I got time, even if it was 5 minutes, I would try to flash by taking test point shots and on the 7th or 8th day my device booted in bootloader mode.
Pero en este caso el papel principal será el de Qualcomm QDLoader HS-USB 9008 Driver. Este controlador está diseñado para trabajar + llevar la interfaz al modo EDL. Después de instalar este controlador, muchas veces los usuarios piensan que el controlador está instalado, pero en realidad no está instalado y no funciona internamente, por lo que es necesario instalar el controlador correctamente y debe verificarse. He publicado todo esto en su sección de conversación (sobre la instalación) pdf. Este pdf también analiza algunos comandos que activan con fuerza el modo EDL. Pero no creo que ese comando funcione porque no sé si su móvil tiene la depuración USB activada o no. Según yo y según mi conocimiento/comprensión, esta es la forma de recuperarlos>>
Encuentre el punto edl / punto de prueba>> cable USB de conexión corta y al mismo tiempo> la PC muestra el dispositivo> la pantalla móvil saluda en modo fastboot, luego flashea rápidamente la rom fastboot con doble clic en el archivo .bat
Si no hay recuperación/No hay modo de cargador de arranque/solo pantalla negra muerta que flash en blanco con la misma versión.
Cosas para recordar antes de flashear la ROM: -
Información: - Si uno tiene el cargador de arranque bloqueado, solo puede instalar el firmware con una versión igual o superior a la versión que ya está en el dispositivo. En ese caso, si tiene el gestor de arranque bloqueado, si quiere instalar una versión anterior o una versión anterior, es necesario desbloquear el gestor de arranque porque si intenta instalar una versión anterior con el gestor de arranque bloqueado, existe una alta probabilidad de bloqueo. .
www.youtube.com/watch?v=DtRZkCyp9do
Click to expand...
Click to collapse
works. but without QFIL files edl mode won't make uch difference here.
Thank you for the information. In future it would be easy to identify edl points from schematics and it consists of UART and USB Boot inputs as test points.