Hi, i like to know the prevention for Moto g5.so I can't able to brick my device again. thanks in advance
Don't flash recoveries, kernels or ROMs that are not suitable for your phone. However, in some cases mentioned above, phone will start. This is also related to other Android phones, not just Moto G5. An exception is if your device support Treble (Moto G5 does since today). Then, you can flash any ROM WITH TREBLE SUPPORT AND PARTITIONING CORESPONDING TO YOUR DEVICE - A ONLY or A/B.
Don't even try to flash stock firmware with older security patch than you have currently installed - everything except gpt and/or bootloader will flash because of preflash validations. Corrupted or missing gpt/bootloader will end up in hardbricked device.
Even, there's already a tutorial for fixing hardbricked G5 (by booting off from sdcard), it may, but also may not work for you. Always be careful of what you are flashing to avoid situations that are difficult to fix.
Andrej_SK said:
Don't flash recoveries, kernels or ROMs that are not suitable for your phone. However, in some cases mentioned above, phone will start. This is also related to other Android phones, not just Moto G5. An exception is if your device support Treble (Moto G5 does since today). Then, you can flash any ROM WITH TREBLE SUPPORT AND PARTITIONING CORESPONDING TO YOUR DEVICE - A ONLY or A/B.
Don't even try to flash stock firmware with older security patch than you have currently installed - everything except gpt and/or bootloader will flash because of preflash validations. Corrupted or missing gpt/bootloader will end up in hardbricked device.
Even, there's already a tutorial for fixing hardbricked G5 (by booting off from sdcard), it may, but also may not work for you. Always be careful of what you are flashing to avoid situations that are difficult to fix.
Click to expand...
Click to collapse
Thans for replying. If I flash the device without using gpt/or bootloader codes (in case of using old firmware).then my device will not get bricked.is it right.
riyan65 said:
Thans for replying. If I flash the device without using gpt/or bootloader codes (in case of using old firmware).then my device will not get bricked.is it right.
Click to expand...
Click to collapse
It won't get hard bricked because you are not changing the boot partitions or bootloader so you will be able to access fastboot
Your phone may not boot (for example if a kernel requires a certain bootloader version) but it won't be hard bricked
TheFixItMan said:
Your phone may not boot (for example if a kernel requires a certain bootloader version) but it won't be hard bricked
Click to expand...
Click to collapse
Or for example if ROM needs certain kernel... still remember how much I was scared when I've softbricked my old Xperia X8 for the first time.
Andrej_SK said:
Or for example if ROM needs certain kernel... still remember how much I was scared when I've softbricked my old Xperia X8 for the first time.
Click to expand...
Click to collapse
Thanks for help.
My piece of advice:
DON'T ATTEMPT TO DOWNGRADE USING FASTBOOT.
More specifically: don't flash gpt/bootloader files with fastboot. When you flash an older bootloader through Fastboot or RSD Lite, you end up with a brick and you will need a blankflash file or an image dump on a Micro SD card.
Just backup everything you can and be very cautious of what you flash, better safe than sorry.
Hi, I'm begging you all for help.
Please, even if you don't know the answer, share any sort of advice.
I'm not a newbie (25+ years story of Unix/Reversing), but I know nothing about radio.
Here's a list of symptoms:
1) Sometimes the WIFI MAC Address comes up as 02:00:00:00:00:00 and IMEI isn't available, then they both magically come up (without rebooting, after the SIM Is read - see n. 2)
2) It keeps powering ON & OFF the SIM and switching between Connected , No Signal , Emergency. Sometimes taking the SIM out & back in helps. Selecting the Preferred Network Type from the modem debug screen keeps it connected for long periods.
3) It won't search for alternative networks to Register Manually
3) IMS Registration is showing as Not Registered always, even while it's connected: Voice + Data (?!?)
4) From the Debug Info only 1 cell appears as SRV = R+N and has a CELL ID, so it seems it connects only to 1 cell at a time.
I can't post screenshots as I lost my old username here, so I signed-up again.
Nothing works, it was a new phone. I wanna die.
Thank you all for your help.
Thanks.
I have problems with modem and camera wgen updating ta android 9.
I would recomend you to rollback to 10.2.1.0
I would use this method
1. Backup your media files to your computer
2. Unlock bootloader
3. Download fastboot china version of 10.2.1.0 and Flash it with mi flash (choose wipe but dont lock!)
4. Flash orange fox twrp with fastboot
5 wipe all partitions exvept internal storage with orangefox
6. Download 10.2.1.0 from xiaomi.eu and flash it with orangefox
Tell me is you want direct links to all files that you need.
If you still have problems after downgrading I can prove my persist and modem files
Good luck
eliaztheone said:
I would recomend you to rollback to 10.2.1.0
Click to expand...
Click to collapse
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)
DoYouWantFriesWithThat said:
@eliaztheone thank you for your reply and your offer about the files, I'll take it if necessary.
Just one question: won't that trigger Anti-Rollback ?
(I don't need to stay on MIUI: do I have other options?)
Click to expand...
Click to collapse
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...
eliaztheone said:
Your anti rollback is already triggered on 4. Thats the arb value on 10.2 too. As long as you dont flash older miui 9 firmware you should be ok...
Click to expand...
Click to collapse
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone
DoYouWantFriesWithThat said:
The roll-back went well but the phone is still unstable.
I'm not sure why: did the Persist get corrupted? Or the EFS partition? I have some backups but I'm not sure what to do.
Can you provide the files that you mentioned, or maybe some pointers?
What could be wrong with the phone?
Thanks a lot @eliaztheone
Click to expand...
Click to collapse
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?
eliaztheone said:
I can give you my efs and persist backup if you want? Then you can use partitions backup and restorev from playstore.
You need to be rooted with magisk to restore
Are you on the xiaomi.eu version of 10.2.1.0 and is it the 8.1 version or 9.0?
Click to expand...
Click to collapse
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump
DoYouWantFriesWithThat said:
I am on Xiaomi.eu 10.2 with Android 9 now, as you suggested. Rooted & with Magisk.
I have backups of my old PERSIST from the China 9.x ROM. Should I flash that (or do I risk bricking) ?
I was reading on persist.img and I don't understand one thing: if it's different for every phone, why there's a persist.img in every Fastboot ROM ?
EDIT: I flashed my old Persists (tried various ones), and the problem.....persists! :') lol
So I'm back to my most recent Persist and still in need for help.
PS: if it helps for a diagnosis, any time the modem resets the SIM it dumps a lot of logs in /ramdump
Click to expand...
Click to collapse
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I tried it following this guide to restore the Persist partition (https://forum.xda-developers.com/xi...guide-restoring-persist-partition-to-t3906424 - via Fastboot, not EDL) , and right after flashing the SIM was working fine on 4G/LTE and the phone didn't present any problems.
Then I opened up Google-Maps and gave it permission to read the GPS and it went crazy: not reading the SIM anymore, rebooting, etc. And turning GPS off now won't help. So I guess the problem is with the Modem and the fact that it connects to only 1 Cell - no idea why.
@eliaztheone
eliaztheone said:
Sorry I was not clear with my guide.. You needed to flash the android 8.1 version of 10.2.1.0 . I guess that wont help either but maybe so try it..
Try it and if it does not work. I will make backup of my persist and efs and modem and send them to you and after that u need to change to your imei numbers with qualcom app..
Click to expand...
Click to collapse
I am on 10.2.1.0 - Android 8.1 now. In addition to what you suggested I restored the persist.img via Fastboot (not EDL) following this guide on XDA .
Right after flashing the phone didn't present any problems (SIM/4G was working without hiccups). As I opened up Google-Maps and gave it permission to read the GPS it went crazy: not reading the SIM anymore, rebooting, etc. Turning GPS off now won't help, it constantly reboots - I have to use Airplane Mode.
So I guess the problem is still in the Modem. Maybe it's the fact that it connects to only 1 Cell, apparently.
@eliaztheone if you can provide the files I'll try one last time. Thank you.
I will upload them tonight hopefully. You need to be on 10.2.1.0 oreo xiaomi.eu version.
You also need to be rooted with magisk so you can restore them with partition backup and restore
---------- Post added at 07:33 PM ---------- Previous post was at 07:28 PM ----------
Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img
Take your time, thank you.
While inspecting the ramdump I noticed the following:
[ 21.864464] [c:1] [p:<003975, android.vending>] Fatal error on the modem.
[ 21.864522] [c:1] [p:<003975, android.vending>] modem subsystem failure reason: rflm_diag_error.cc:361:[email protected]_qlnk.cpp:1090 [9,3] RF stuck in QLINK start s.
[ 21.864530] [c:1] [p:<003975, android.vending>] subsys-restart: subsystem_restart_dev(): Restart sequence requested for modem, restart_level = RELATED.
There's many SELinux odd log entries too, not sure if that's normal. When I disabled SELinux from the terminal the 4G immediately picked up...totally weird
eliaztheone said:
[/COLOR]Did you try to flash modem_fix_ysl.zip? It resets the modem.img and modemst1.img and modemst2.img
Click to expand...
Click to collapse
I'll try to flash it, thank you.
I am on 10.2.1.0 oreo xiaomi.eu. Do you think it makes sense to try a custom ROM ?
Thank you.
EDIT:
- I flashed modem_fix_ysl.zip but it didn't have any effect.
- I find the ramdumps from the china ROM much cleaner and errorless than the Xiaomi.eu ROM, just saying
I have sent you a pm
Have you guys found a solution? I have the exactly same problem on Mi Max 3 4/64Gb version. I'm on MIUI Global Stable 10.3.5.0. I was on China stable and had issues,so i flashed Global Stable fastboot rom using Mi Flash Tool(flash all option),and It doesn't solve the problem.I have unlocked bootloader,and no previous system backup.
Also i tried flashing NON-HLOS.bin file from Global Stable fastboot ROM using command : fastboot flash modem NON-HLOS.bin
Also i tried something that worked on my old redmi 4,after NON-HLOS.bin flash,executed fastboot commands :
fastboot erase modemst1 and modemst2,but no luck because of "partition is write protected" error.
Have you found what's the cause of this problem?Is it hardware?Is it corrupted modem files?Will custom rom solve it? Please, any help,any suggestion will be appreciated. I'll try everything to fix it. Thank you in advance.
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Thank you man, I'll try everything you said tommorow. The device hardware is awesome,and i really want to support xiaomi,only if they had solution for this problem. Also i think keeping ARB on unlocked bootloader is a bad decision,it really makes this whole process harder.
I'm hoping you get you phone fixed and looking forward to see how this will end.
Thanks for helping me man.
(Sorry for bad English)
---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------
Maybe someone's QCN file can help us?
DoYouWantFriesWithThat said:
@ghost baby
I tried the following:
- reflashing Global ROM
- flashing Xiaomi.eu ROM as per instructions of of Eliaztheone
- restoring a backup of old China ROM
- reflashing China ROM
- analyzing the ramdumps (memory dumps & system/radio-modem logs)
- EDL flashing (with `fastboot oem edl` - not with the deep-flash cable)
All the reflashes included overwriting the EFS (modemst1/2) & PERSIST partitions, automatically (in bulk) or manually, taken from various sources including those that Eliaztheone kindly sent to me. The EDL flashing didn't work because I had no authorization on my Xiaomi account (I've tried all combinations of SDR programmers & old versions of MiFlash - none works) so I've then tried to get a remote authorization, also without success: the guy from UNBRICK.RU told me that Xiaomi revoked all authorizations lately to push out of business the remote-auth-flashers.
From my understanding of the ramdumps the problem seems to be an internal modem fault. Since ARB wasn't triggered when I rolled back to China ROM, I suspect that the fault is a hardware (or very low-level SW) software in the radio modem, and so it can be maybe fixed only by EDL flashing.
That's why I resorted to finding a local authorized service center this week. But I have to see how much money they ask me: if they ask too much I might as well buy a new OPPO or REALME phone, which are cheap & open (at least more than ****ty Xiaomi). If the service center pisses me off you'll see the result in the news.
Support the right to repair movement.
I hope this helps.
Click to expand...
Click to collapse
Maybe someone's QCN file can help us?[/QUOTE]
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.
@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.
DoYouWantFriesWithThat said:
@Wmateria can you give me the contact of this person who gave you the remote Auth ?
I just phoned Xiaomi and they told me that Xiaomi's warranty is only valid at national level (read: each european country collects phones sold on its territory, and sends them to specific labs).
The QCN won't help cause we can't access EDL anyway even via QFIL.
If anyone has a contact for remote Auth, I'd appreciate if he/she could share it.
Thanks.
Click to expand...
Click to collapse
I found some article that shows how to flash QCN file form DIAG mode,and how to enter that mode. I'll try and keep you updated.
Wmateria said:
Maybe someone's QCN file can help us?
Click to expand...
Click to collapse
All authorizations has been locked down for a while now, learned that the hard way during in the early days of ARB4 and i tried to flash a stable rom with a lower ARB number and my phone bricked. IThen i found someone to flash a beta rom by remote with authroization; costed me 15 USD. EDL flash was the only way if you still have fastboot. I worked with the service guy because he also wants to figure out the problem also. After bricking my device 4 times, I got the right recovery to use and then TWRP Recovery worked for the 4GB version. I got the 6GB version also and the people who sold me the phone had already unlocked the bootloader, I had to double check to see using command prompt. The i flashed the Recovery i was given to by a user on the AOSiP thread, thinks its Page 7, its a TWRP CN Recovery.. and it worked in both devices.[/QUOTE]
Did EDL flash solved the problem?
Hello,
The Xiaomi 9 SE Global Unlocked of my girlfriend was restarting a lot (restart loop) and I tried to flash a ROM but I accidentaly flashed and locked the mobile on a "MIUI version that can´t be installed on this device" (grus_global_images_V12.0.2.0.QFBMIXM_20200910.0000.00_10.0_global)
The problem is the phone was wiped and I cant unlock the phone now. What to do? I can´t flash another ROM or unlock it and I just have access to Recovery Mode and Fastboot mode.
Please any help would be greatly appreciated.
It´s 4 am where I live and I´ll go to bed... But Will read here as soon as I´m awake. Thanks a lot in advance.
Let me continue my story... I still need help.
I contacted an authorized and he helped me to EDL a flashed version and I reinstalled the MIUI 12.0.2 Global stable on the phone.
But the phone is still TURNING OFF BY ITSELF (this was the reason because I tried flashing it on the first place). I don´t know the cause but it does not seems to be a faulty battery. I heard the phone has Anti RollBack protection. Is it right?
So I need help on how to procced. I would like to RollBack it to MIUI 11 where I didn´t had this problems...
Unfortunately you can NEVER go back once you flash a ROM on Xiaomi devices. However that doesn't prevent you from flashing custom ROMs.
Though you still need to be careful, because once flashed there is no going back.
I recommend testing the ROM on an emulator before flashing it. Here is how.
Also don't forget to check for your rollback protection index and the ROM's index before flashing.
Follow this post and scroll down to "How to find rollback index of images".
XDHx86 said:
Unfortunately you can NEVER go back once you flash a ROM on Xiaomi devices. However that doesn't prevent you from flashing custom ROMs.
Though you still need to be careful, because once flashed there is no going back.
I recommend testing the ROM on an emulator before flashing it. Here is how.
Also don't forget to check for your rollback protection index and the ROM's index before flashing.
Follow this post and scroll down to "How to find rollback index of images".
Click to expand...
Click to collapse
what do you mean never? you can flash miui with miflash
giorgarasgr said:
what do you mean never? you can flash miui with miflash
Click to expand...
Click to collapse
You can read more about xiaomi anti-rollback here.
I understand I can convert to EU.... However, I don't wish to do that. I just want to root my stock TMOBILE ROM.
My sim is unlocked and I have the unlock.bin from OnePlus for my phone. For anyone who has rooted TMOBILE stock ROM, which boot.img did you patch? I've read that AA boot image can work, but no firsthand accounts confirming this.
Ideally, I'd like to use my own boot.img but I can't find a tutorial or guide anywhere advising how to obtain my boot.img without root.
Thanks!
use AA boot img, but recommend unlocking Bootloader and backing up your tmo modem a/b imgs
How to guide
[TMO] 9 PRO MODEM RETENTION/DATA FIX
----- With the release of OOS13, the modem issue no longer exist. Thank you all for the support & help with this unfortunate issue, we had to endure.... ----- EXPLICITLY FOR TMOBILE 9 PRO (I'm not responsible for your failure to read or...
forum.xda-developers.com
Use partitions backup (app) to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..
galaxyuser88 said:
Use partition magic to backup the existing TMO Firmware first and copy your files to a pc before you do anything. As with any flashing you run the risk of wiping your info and stored files..
Click to expand...
Click to collapse
What is partition magic? An app? Software?
Pain-N-Panic said:
What is partition magic? An app? Software?
Click to expand...
Click to collapse
Sorry meant to say partitions backup. Which is an app.
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out
Pain-N-Panic said:
Thank you... unfortunately partition backup requires root. So I can't back anything up until I unlock and root....which using the AA boot image to root kinda freaks me out
Click to expand...
Click to collapse
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..
galaxyuser88 said:
It is understandable to be freaked out,. But if you follow the direction letter for letter then you should be fine.
Also good rule of thumb is make sure you have all the drivers and software loaded on your pc, then make sure your pc and phone can talk in adb and fastboot before you start to flash your phone.
I have rooted my stock tmo rom with aa and all good. Of course I went even further and installed the EU version on my tmo bought 9Pro..
Click to expand...
Click to collapse
Yep, confirmed, 9pro and my computer can talk. The whole MSM thing is what is worrying me. In the MSM tool, it says it is the TMO -EU MSM. So, once it does it's thing and flashes it all, it should wipe the phone, it would be on the EU rom?
From there, I would need to follow the steps, unlock BL, flash modems, and then download oxygen updater to be able to locally download updates and install?
Hi.
I am new to Custom Roms and therefore have absolutely inadequate experience, so I would be very happy to receive help.
(It's a Poco F3 [Alioth]+Bootloader is Unlocked)
Currently neither an operating system nor TWRP is "installed".
I have already tried to load the .img from TWRP onto the mobile phone while it is in the state where I entered the command fastboot boot twrp-3.6.0_11-0-alioth.img in the Platform Tools (cmd) (i.e. in Twrp only it is not installed?) And you can activate MTP under "Mount" (file transfer?). Only that doesn't work (mobile phone is only displayed on the PC when I want to drag files to it, it loads forever. (Mobile phone also has no SD card slot.
But how am I supposed to install TWRP without getting the file on the phone and with it Magisk and a Custom Rom?
Help is very much appreciated.
Lg
(my english is not the Yellow from the Egg = GTranslate)
First, install the stock rom, everything is explained in detail in the guide I sent, then you can install the rom you want.
How to flash a stock rom [alioth]
Hello everyone. The purpose of this guide is to illustrate two methods to flash the stock rom on F3, both with the use of xiaomi flash tool (which for convenience I will call "miflash") and with cmd. Warnings! Before starting I would like to...
forum.xda-developers.com
dogan6459 said:
First, install the stock rom, everything is explained in detail in the guide I sent, then you can install the rom you want.
How to flash a stock rom [alioth]
Hello everyone. The purpose of this guide is to illustrate two methods to flash the stock rom on F3, both with the use of xiaomi flash tool (which for convenience I will call "miflash") and with cmd. Warnings! Before starting I would like to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much i try it