Closed Xmaster111 closed 4 years ago
Is it default custome ROM ? Can you provide the log ?
yes, stock rom, Sir.
Try Android 10 firmware.
Try Android 10 firmware.
I believe that there is no firmware with Android 10 for Mi 9T Global http://c.mi.com/oc/miuidownload/detail?device=1700361 I'm wrong?
Try Android 10 firmware.
I believe that there is no firmware with Android 10 for Mi 9T Global http://c.mi.com/oc/miuidownload/detail?device=1700361 I'm wrong?
Didn't we talking about Samsung SM-A307FN on firmware A307FNXXU2ATB1?
Make magisk patched firmware and rename recovery.img to boot.img and compressed it with 7-zip to tar and flash if it's not work with u text me on my phone no to find a solution on telegram +962787575320
Try Android 10 firmware.
I believe that there is no firmware with Android 10 for Mi 9T Global http://c.mi.com/oc/miuidownload/detail?device=1700361 I'm wrong?
Didn't we talking about Samsung SM-A307FN on firmware A307FNXXU2ATB1?
A307FNXXU2ATB1 has Android 9 A307FNXXU2BTD1 has Android 10 (27-04-2020)
Now I format the phone, I flash the new firmware (A307FNXXU2BTD1) that has Android 10, then I try again to root with Magisk and see what happens. Before trying other solutions. Do you all agree?
P.S. I was not aware of the new firmware for the A30s, thanks for the tip, thank you
Try Android 10 firmware.
I believe that there is no firmware with Android 10 for Mi 9T Global http://c.mi.com/oc/miuidownload/detail?device=1700361 I'm wrong?
Didn't we talking about Samsung SM-A307FN on firmware A307FNXXU2ATB1?
A307FNXXU2ATB1 has Android 9 A307FNXXU2BTD1 has Android 10 (27-04-2020)
Now I format the phone, I flash the new firmware (A307FNXXU2BTD1) that has Android 10, then I try again to root with Magisk and see what happens. Before trying other solutions. Do you all agree?
P.S. I was not aware of the new firmware for the A30s, thanks for the tip, thank you
Yes, upgrade to A307FNXXU2BTD1 will fix this issue.
Ok, the connection problem is fixed just like you said, but there is another problem: if I use the root to uninstall apps included in the firmware, the phone enters the bootloop on Download... and no way to load Android
That is unrelated to Magisk. You should be aware that devices are more and more unforgiving when you directly modify read-only partitions (that includes system). Tons of root apps that "remove system apps" is outdated and will brick your device, as you personally experienced
Data: A30s, SM-A307FN, A307FNXXU2BTD1 (Android 10) Magisk 20.4 (20400) Magisk Manager 7.5.1 (267)
Flash boot.ini via ODIN (Boot.ini) on stock firmware (A307FNXXU2ATB1_A307FNOEM2ASL3_ITV) boot.zip
Original boot.ini from Firmware.zip
• Does not recognize the sim-card • I cannot access the "Mobile networks" settings • I noticed a general slowdown of the phone (as if it were overloaded with processes or with full memory)
What information can I provide to help me focus on the problem?
--------- beginning of main --------- beginning of system 05-01 21:34:50.272 3862 3862 I Magisk : Magisk 20.4(20400) daemon started 05-01 21:34:50.272 3862 3862 I Magisk : * Device API level: 28 05-01 21:34:50.302 3862 3863 I Magisk : * post-fs-data mode running 05-01 21:34:50.304 3862 3863 I Magisk : Initializing Magisk environment 05-01 21:34:50.322 3862 3863 I Magisk : Mounting mirrors 05-01 21:34:50.323 3862 3863 I Magisk : mount: /sbin/.magisk/mirror/product 05-01 21:34:50.323 3862 3863 I Magisk : mount: /sbin/.magisk/mirror/vendor 05-01 21:34:50.323 3862 3863 I Magisk : mount: /sbin/.magisk/mirror/data 05-01 21:34:50.323 3862 3863 I Magisk : link: /sbin/.magisk/mirror/system 05-01 21:34:50.326 3862 3863 I Magisk : Setting up internal busybox 05-01 21:34:50.344 3862 3863 I Magisk : Running post-fs-data.d scripts 05-01 21:34:50.347 3862 3863 I Magisk : Running module post-fs-data scripts 05-01 21:34:50.347 3862 3863 I Magisk : Loading modules 05-01 21:34:50.357 3862 3870 I Magisk : Starting MagiskHide 05-01 21:34:50.357 3862 3870 I Magisk : hide_policy: Hiding sensitive props 05-01 21:34:50.358 3862 3870 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable] 05-01 21:34:50.363 3862 3870 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable] 05-01 23:34:51.416 3862 4018 I Magisk : late_start service mode running 05-01 23:34:51.416 3862 4018 I Magisk : Running service.d scripts 05-01 23:34:51.432 3862 4018 I Magisk : Running module service scripts 05-01 23:35:08.115 3862 5451 I Magisk : boot_complete triggered 05-01 23:35:50.265 3862 3870 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[9450] UID=[10036] 05-01 23:36:36.603 3862 3870 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[12360] UID=[10036] --------- beginning of crash 05-01 23:38:02.396 3862 3870 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[17086] UID=[10036]
thanks for the help in the previous discussion, I was able to advance to the boot as a result of your help