Develop Bugs

Play store long delay to download

Hi,
My problem is simple, when I try to download anything on the play store, there is a very long loading (see attached screenshot) before the download start (some hours), the problem is not coming from my connection, I already contacted Google Play support and tried everything (data/cache deleting for Play store, Play Services and even the device, Google account suppression, dirty flash my firmware, root/unroot etc...) and nothing is working, I already had this problem before and after a full wipe it was gone but I don't really want to wipe everything again... Before to apply this radical method I ask the help of anyone who have maybe another solution.
Infos : - Device : OnePlus 3 A3003
- Firmware : Last Open BETA 28 (Oreo 8.0)
- Root : Yes with Magisk 14.5
- Kernel : Derp Kernel (but problem still here with stock kernel)
Thanks !

I finally wiped everything but the problem came back...

Have you cleared cache for the Google Play store, Services framework and Google Play services? You must do all 3 of them to ensure any change is effective.
Does it only have issues on a certain network/wifi ? Is this the only device that you have, if you have another device is that affected too on the same networks. Most issues on this front could be ISP/DNS related.

cbarai said:
Have you cleared cache for the Google Play store, Services framework and Google Play services? You must do all 3 of them to ensure any change is effective.
Does it only have issues on a certain network/wifi ? Is this the only device that you have, if you have another device is that affected too on the same networks. Most issues on this front could be ISP/DNS related.
Click to expand...
Click to collapse
Of course I already did it several times, it's not Network related I already tried with another WIFI and mobile data and other phones are working great.

cbarai said:
Have you cleared cache for the Google Play store, Services framework and Google Play services? You must do all 3 of them to ensure any change is effective.
Does it only have issues on a certain network/wifi ? Is this the only device that you have, if you have another device is that affected too on the same networks. Most issues on this front could be ISP/DNS related.
Click to expand...
Click to collapse
Oh It worked by wiping Google services Framework too ! Even Google customer service didn't said me to try this
Thanks !

I spoken too early... The delay problem came back few minutes after wiped everything

Same problem on huawei p10+. Anyone been able to resolve this? Hard reset not worked.

Bryandu13 said:
Hi,
My problem is simple, when I try to download anything on the play store, there is a very long loading (see attached screenshot) before the download start (some hours), the problem is not coming from my connection, I already contacted Google Play support and tried everything (data/cache deleting for Play store, Play Services and even the device, Google account suppression, dirty flash my firmware, root/unroot etc...) and nothing is working, I already had this problem before and after a full wipe it was gone but I don't really want to wipe everything again... Before to apply this radical method I ask the help of anyone who have maybe another solution.
Infos : - Device : OnePlus 3 A3003
- Firmware : Last Open BETA 28 (Oreo 8.0)
- Root : Yes with Magisk 14.5
- Kernel : Derp Kernel (but problem still here with stock kernel)
Thanks !
Click to expand...
Click to collapse
Je suis français et j'ai le même soucis
J'ai beau chercher tant que je veux, aucune solution....
I have the impression that it is a problem just French.... I look everywhere I find no solution

lexa06600 said:
Je suis français et j'ai le même soucis
J'ai beau chercher tant que je veux, aucune solution....
I have the impression that it is a problem just French.... I look everywhere I find no solution
Click to expand...
Click to collapse
Ouais c'est très étrange. La seule solution que j'ai trouvé c'était de partir sur une ROM Custom et pendant 2-3 mois aucun problème, ensuite je suis revenu sur OxygenOS dernière beta pour tester le Kernel EAS et le problème est revenu en 2 jours.
Heureusement maintenant ces problèmes sont derrière moi vu que j'ai acheté un Mi Mix 2S.
Bonne chance à toi^^ (seule solution --> ROM Custom).

Et bien justement non, moi mon problème se fait même avec les roms custom, et comme tu dis il faut attendre quelques mois avant que ça se remette
---------- Post added at 04:45 PM ---------- Previous post was at 04:38 PM ----------

English please
@lexa06600 and @Bryandu13
Please use English so that others too understand (XDA Policy).

tnsmani said:
@lexa06600 and @Bryandu13
Please use English so that others too understand (XDA Policy).
Click to expand...
Click to collapse
Nobody answered for 5 months, and the only guy who answer speak French, I think I can answer to him in French

Bryandu13 said:
Nobody answered for 5 months, and the only guy who answer speak French, I think I can answer to him in French
Click to expand...
Click to collapse
Forum Rules
"4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature)."
My post was not to find fault with you but to point out that others also should benefit. When the other member chose to atleast give a translation as per Forum Rules, you did not and continue to justify your action.

Question OEM Unlock greyed out

Hey at all users of this low priced, anyway nice speced and nearly Stock android 11 providing phone! (And all others of you, too)
I noticed, that in developer options the OEM Unlock option is greyed out.
Cause this phone is very new on the market the information I could get online is really rare.
At the Motorola forum there were a few posts asking for this and one user got at least the answer to wait a week or so and let the device communicate online, so maybe there is a chance to get the OEM unlock available this way.
I asked myself what apps, in that case could realize this? I have disabled nearly all of that Motorola specific stuff (not much at all / good work in my opinion), so I can not really be sure if one of these should have been enabled for making OEM Unlock possible..
Now my question to all Moto G20 users out there, at best those who did not disable any preinstalled app, could you please enable developer options and look if OEM Unlock is still greyed out after a week (or more) of normal usage?
More than that I would really appreciate some more activity here at XDA.
Rooting this device or maybe being able to flash calyx or lineage os on it would be so damn great!!
I am using this as my daily driver for now, so I am not really able to go the dark path alone, at least until there is no backup device available for me. (My beloved SGS5 klte died the hard way)
So maybe we, the Moto G20 users could get together here and make more, or at least anything possible on this device.
First step is the OEM unlock.
Greetings from Germany,
yours ajox
{
"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"
}

ajox said:
Hey at all users of this low priced, anyway nice speced and nearly Stock android 11 providing phone! (And all others of you, too)
I noticed, that in developer options the OEM Unlock option is greyed out.
Cause this phone is very new on the market the information I could get online is really rare.
At the Motorola forum there were a few posts asking for this and one user got at least the answer to wait a week or so and let the device communicate online, so maybe there is a chance to get the OEM unlock available this way.
I asked myself what apps, in that case could realize this? I have disabled nearly all of that Motorola specific stuff (not much at all / good work in my opinion), so I can not really be sure if one of these should have been enabled for making OEM Unlock possible..
Now my question to all Moto G20 users out there, at best those who did not disable any preinstalled app, could you please enable developer options and look if OEM Unlock is still greyed out after a week (or more) of normal usage?
More than that I would really appreciate some more activity here at XDA.
Rooting this device or maybe being able to flash calyx or lineage os on it would be so damn great!!
I am using this as my daily driver for now, so I am not really able to go the dark path alone, at least until there is no backup device available for me. (My beloved SGS5 klte died the hard way)
So maybe we, the Moto G20 users could get together here and make more, or at least anything possible on this device.
First step is the OEM unlock.
Greetings from Germany,
yours ajox
View attachment 5410895
Click to expand...
Click to collapse
Did you connect it to the internet?

ajox said:
¡Hola a todos los usuarios de este teléfono de bajo precio, de todos modos, con buena velocidad y casi en stock! (Y todos los demás de ustedes también)
Noté que en las opciones de desarrollador, la opción de desbloqueo OEM está atenuada.
Debido a que este teléfono es muy nuevo en el mercado, la información que puedo obtener en línea es realmente rara.
En el foro de Motorola hubo algunas publicaciones que preguntaban por esto y un usuario obtuvo al menos la respuesta de esperar una semana más o menos y dejar que el dispositivo se comunique en línea, por lo que tal vez exista la posibilidad de que el desbloqueo OEM esté disponible de esta manera.
Me pregunté qué aplicaciones, en ese caso, podrían darse cuenta de esto. He deshabilitado casi todas esas cosas específicas de Motorola (no mucho / buen trabajo en mi opinión), por lo que no puedo estar realmente seguro de si uno de estos debería haber sido habilitado para hacer posible el Desbloqueo OEM.
Ahora, mi pregunta para todos los usuarios de Moto G20, en el mejor de los casos, aquellos que no deshabilitaron ninguna aplicación preinstalada, ¿podrían habilitar las opciones de desarrollador y ver si el Desbloqueo OEM sigue en gris después de una semana (o más) de uso normal?
Más que eso, realmente agradecería algo más de actividad aquí en XDA.
¡Rootear este dispositivo o tal vez poder flashear el cáliz o el sistema operativo del linaje en él sería genial!
Estoy usando esto como mi controlador diario por ahora, por lo que realmente no puedo ir solo por el camino oscuro, al menos hasta que no haya un dispositivo de respaldo disponible para mí. (Mi amado SGS5 klte murió por las malas)
Entonces, tal vez nosotros, los usuarios de Moto G20, podríamos reunirnos aquí y hacer más, o al menos cualquier cosa posible en este dispositivo.
El primer paso es el desbloqueo OEM.
Saludos desde Alemania,
tuyo ajox
View attachment 5410895
Click to expand...
Click to collapse
Same here i hope we'll grew in number an maybe we could activate the oem unlock. I found this but not work for me https://mytechgyangadgets.com/how-t...ac646cbae347febc951700b1759bca89#comment-1156. Tell me if u get it
Greetings from Argentine

sd_shadow said:
Did you connect it to the internet?
Click to expand...
Click to collapse
Sure. Both, WiFi and Mobile Data are and were connected. No good life without that.
Testwise I have now reenabled Moto Feedback and Device support stuff and more than that I created a Lenovo ID and registered my device. But anyway OEM Unlock still greyed out.
anoldman57 said:
Same here i hope we'll grew in number an maybe we could activate the oem unlock. I found this but not work for me https://mytechgyangadgets.com/how-t...ac646cbae347febc951700b1759bca89#comment-1156. Tell me if u get it
Greetings from Argentine
Click to expand...
Click to collapse
Nice to see some more Moto G20 users. Will give that a look later and tell you.
*Update*
This looks interesting. When I am at home later, I will definitely fire up fastboot and look for it.

Short update..
After a while i managed to get into fastboot mode, Volume Down + Power did not work for any reason, Assistant Button + Volume Down + Power did instead:
(sorry for the poor quality)
Device was than recognized but ran into problems anyway:

Greetings!
I just purchased the motorola moto g20 xt2128-1 (unlocked) from "A to Z" and I ran into these exact issues. This is what worked for me:
FASTBOOT: VOL UP + POWER
The OEM UNLOCKING option was also grayed out in my Developer Settings. After getting into FASTBOOT MODE (the exact screen in your SHORT UPDATE) on my PC, COMMAND PROMPT (admin):
fastboot devices (to verify)
fastboot flashing unlock
This worked for me. In the upper left corner on phone, I had to confirm that I wanted to unlock. WARNING!!! ALL USER DATA WILL ERASE!!! It took about 3 minutes.
The option is still grayed out in my Developer Settings, but it now says BOOTLOADER IS ALREADY UNLOCKED
I hope this helps you!

Chris776 said:
Greetings!
I just purchased the motorola moto g20 xt2128-1 (unlocked) from "A to Z" and I ran into these exact issues. This is what worked for me:
FASTBOOT: VOL UP + POWER
The OEM UNLOCKING option was also grayed out in my Developer Settings. After getting into FASTBOOT MODE (the exact screen in your SHORT UPDATE) on my PC, COMMAND PROMPT (admin):
fastboot devices (to verify)
fastboot flashing unlock
This worked for me. In the upper left corner on phone, I had to confirm that I wanted to unlock. WARNING!!! ALL USER DATA WILL ERASE!!! It took about 3 minutes.
The option is still grayed out in my Developer Settings, but it now says BOOTLOADER IS ALREADY UNLOCKED
I hope this helps you!
Click to expand...
Click to collapse
This really works. Did you install some recovery and some gsi?

Chris776's solution worked for me too, thanks! I didn't managed to get twrp on it yet, and I tried getting root through patching the boot file to no avail.
EDIT: I'm starting to feel maybe Chris766's solution doesn't work? The option is still greyed out although it says the bootloader is unlocked, however when trying to flash twrp or a modified boot image I always get the same error via fastboot:​writing 'boot'...
FAILED (remote: Write img fail!)
If anyone has any idea...

Radiobuzz said:
Chris776's solution worked for me too, thanks! I didn't managed to get twrp on it yet, and I tried getting root through patching the boot file to no avail.​​EDIT: I'm starting to feel maybe Chris766's solution doesn't work? The option is still greyed out although it says the bootloader is unlocked, however when trying to flash twrp or a modified boot image I always get the same error via fastboot:​writing 'boot'...
FAILED (remote: Write img fail!)
If anyone has any idea...
Click to expand...
Click to collapse
For moto device if the the bootloader is unlock, the OEM unlocking option in Dev options should be greyed.
That's normal

sd_shadow said:
For moto device if the the bootloader is unlock, the OEM unlocking option in Dev options should be greyed.
That's normal
Click to expand...
Click to collapse
Then would you know why I get that error with fastboot?

Radiobuzz said:
Then would you know why I get that error with fastboot?
Click to expand...
Click to collapse
Many people get that error with an unlocked bootloader.
what does this say?
Code:
fastboot getvar securestate

sd_shadow said:
Many people get that error with an unlocked bootloader.
what does this say?
Code:
fastboot getvar securestate
Click to expand...
Click to collapse
Literally nothing lol:
securestate:
finished. total time: 0.000s

Radiobuzz said:
Literally nothing lol:
securestate:
finished. total time: 0.000s
Click to expand...
Click to collapse
Ok, securestate should still be on the Phone's screen while in fastboot mode.
Maybe listed like one of these, but moto keeps changing the phrase.
It will be right under the battery state
Code:
Device is locked
OEM_locked
flashing_unlocked
Device is unlocked

sd_shadow said:
Ok, securestate should still be on the Phone's screen while in fastboot mode.
Maybe listed like one of these, but moto keeps changing the phrase.
It will be right under the battery state
Code:
Device is locked
OEM_locked
flashing_unlocked
Device is unlocked
View attachment 5427523
Click to expand...
Click to collapse
Ok this is what I get while the phone is booting and on fastboot:
https://imgur.com/a/u6IMWox

Radiobuzz said:
Ok this is what I get while the phone is booting and on fastboot:
https://imgur.com/a/u6IMWox
Click to expand...
Click to collapse
Thanks for the screenshots.
The first screenshot is while booting?
The second is fastbootd not fastboot(bootloader)
the bootloader is what I meant
Anyways, it does appear to be oem unlocked

sd_shadow said:
Thanks for the screenshots.
The first screenshot is while booting?
The second is fastbootd not fastboot(bootloader)
the bootloader is what I meant
Anyways, it does appear to be oem unlocked
Click to expand...
Click to collapse
Yes the first one is while the phone is booting up, it appears every time. The bootloader screen is all white and all it says is "Fastboot" and then a track ID, which are letters and numbers, nothing more. Do you have any idea why it doesn't allow me to flash anything on it?

Radiobuzz said:
Yes the first one is while the phone is booting up, it appears every time. The bootloader screen is all white and all it says is "Fastboot" and then a track ID, which are letters and numbers, nothing more. Do you have any idea why it doesn't allow me to flash anything on it?
Click to expand...
Click to collapse
I believe you should be flashing the patched boot.img in the bootloader mode
edit: if that fails use fastbootd

sd_shadow said:
I believe you should be flashing the patched boot.img in the bootloader mode
edit: if that fails use fastbootd
Click to expand...
Click to collapse
Ok I just tried that with no luck. I tried the fastboot getvar is-userspace command and it came back negative so I assume I'm not using fastbootd. I still tried it though and it just never connected (it kept on "waiting for device"), then I tried again flashing it from the bootloader (white screen) but I keep getting that "write img fail" error.

Radiobuzz said:
Ok, eu tentei isso sem sorte. Tentei o comando fastboot getvar is-userspace e deu negativo, então presumo que não estou usando fastbootd. Eu ainda tentei e nunca conectou (ficou em "esperando pelo dispositivo"), então tentei novamente fazer o flash do bootloader (tela branca), mas continuo recebendo aquele erro "write img fail".
Click to expand...
Click to collapse
when installing the corrected boot.img you have to use fastboot flash boot_a boot.img

Chris776 said:
Greetings!
I just purchased the motorola moto g20 xt2128-1 (unlocked) from "A to Z" and I ran into these exact issues. This is what worked for me:
FASTBOOT: VOL UP + POWER
The OEM UNLOCKING option was also grayed out in my Developer Settings. After getting into FASTBOOT MODE (the exact screen in your SHORT UPDATE) on my PC, COMMAND PROMPT (admin):
fastboot devices (to verify)
fastboot flashing unlock
This worked for me. In the upper left corner on phone, I had to confirm that I wanted to unlock. WARNING!!! ALL USER DATA WILL ERASE!!! It took about 3 minutes.
The option is still grayed out in my Developer Settings, but it now says BOOTLOADER IS ALREADY UNLOCKED
I hope this helps you!
Click to expand...
Click to collapse
working for me thanks!!!! any root method working? magisk maybe? going for it

How To Guide How to root Samsung A52s (SM-A528B/DS) with working Camera

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.

Question Moto G60 EDL mode (How to enter?)

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.

Xiaomi Eu Miui 13 for Mi10t (Q)

Does anyone here manage to upgrade your Mi10t on Xiaomi Eu ROM (Android 11) to the latest build Eu (Miui 13/Android12)?
If yes, could you please explain on how to do it, and if there's any issue with it?
As far as I know, the latest Eu ROM for Mi10t can be done only via fastboot... Is it true?

I did update my rom to miui 13. I did it using the stable recovery.
First I check what was my version, mine was V12.5.10.0.RJDEUXM. So I start updating from this rom till the last one :
V12.5.10.0.RJDEUXM -> V12.5.11.0.RJDEUXM -> V12.5.12.0.RJDEUXM -> V13.0.2.0.SJDEUXM -> V13.0.6.0.SJDEUXM.
I use this method each time :
"Recovery updates can be installed using the official updater app inside your device settings, but keep in mind that only stable updates can be installed like this. If the update is a stable beta you might not be able to install it. After downloading the MIUI update, whether the incremental or the full one, open the updater from settings then click the 3-dots menu and choose Install from a local file, then select the downloaded MIUI zip. If you can't see this option, click on MIUI logo in the updater several times till you see a message that tells you more features have been enabled."
I tried update straight from V12.5.10.0.RJDEUXM to V13.0.6.0.SJDEUXM but it didn't work... So I did it rom by rom.
Hope it will help...
P.S.: sorry for my English.

Did you manage to do the update ?

Hi, which recovery do you have installed ?
I'm on 21.11.3, and today I have time to do a new install ...
Can I install the new eu beta ROM via twrp like always?, Must I change first something? Like recovery?
I will do a backup later
Install this recovery:
3.6.2_12-RedmiK30SUltra-Mi10T[Pro]_v3.7_A12-apollo-skkk_8c92bcf4.img
And try to install last version

Bonjour j'aimerai savoir comment tu a fait pour passe a la 12.5.12.0 rjdeuxm a la 13.0.2.0 sjdeuxm car j'ai fais comme tu a dit sur les 12.0 pas de problème mais des que je veux installer de rjdeuxm a sjdeuxm sa ne veut pas merci de m'aider

Nevermind.