If you are having a weird bootloop where the phone just reboots after few seconds of booting like shown here (https://www.youtube.com/watch?v=3YcWsWYQVGQ) then you're in the right place, here's how you can fix the issue.
Before proceeding make sure you know your risks as I am not responsible for bricked devices, dead SD cards, thermonuclear war and anything really.
Steps:
1) Download Mi Flash Tool and install it. (For the drivers, skip it if you have installed the drivers already)
2) Download and Install minimal ADB and Fastboot Tool, persist.img and temporary twrp.img links will be below.
3) Copy the persist.img to your internal storage.
4) Copy the recoveryxx.img to same folder where you've saved the minimal ADB/Fastboot tool.
4) Goto the minimal adb fastboot tool folder where you had put the recoveryxx.img
5) Open cmdhere.exe
6) Put your phone in fastboot mode (Volume - and Power)
7) Type the following commands:
- fastboot devices (you should something like this:
Fastboot dsad5454sfs, If not, re-install the the fastboot drivers correctly. )
- fastboot oem unlock (This is just for unlocking the bootloader you can just skip it if you have unlocked bootloader.)
- fastboot boot recoveryxx.img *(basically the filename of the image file.)
Now you will boot to the temporary twrp and once you're there follow these steps:
8) Open Terminal in TWRP Custom Recovery (go to “Advanced” > “Terminal”).
9) Type the following command:
- dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
10) Go to reboot and select system and that's it!
Voila!
Minimal ADB and Fastboot tool: https://forum.xda-developers.com/sho....php?t=2317790
Mi Flash Tool: http://c.mi.com/thread-235054-1-1.html
TWRP Recovery: https://forum.xda-developers.com/mi-a1/development/recovery-twrp-3-1-1-0-touch-recovery-t3688472 , download the recovery3/2x.img according the android version your on.
Persist(Using this persist.img file is a must) : https://xiaomifirmware.com/download-link/?dlm-dp-dl=7270
Couldn't flash, Error: This image isn't allowed download.
tajamulbaba said:
Couldn't flash, Error: This image isn't allowed download.
Click to expand...
Click to collapse
Have you unlocked the bootloader? If you have and it's showing that error then download the august fastboot ROM and use that persist.img.
Edwin Hamal said:
Have you unlocked the bootloader? If you have and it's showing that error then download the august fastboot ROM and use that persist.img.
Click to expand...
Click to collapse
Yes I've unlocked bootloader, August ROM is nowhere available.
tajamulbaba said:
Yes I've unlocked bootloader, August ROM is nowhere available.
Click to expand...
Click to collapse
Available here (first result of Google search for "mi a1 firmware").
_mysiak_ said:
Available here (first result of Google search for "mi a1 firmware").
Click to expand...
Click to collapse
Thanks for the link, I downloaded and extracted the persist.img, it still shows the error.
tajamulbaba said:
Thanks for the link, I downloaded and extracted the persist.img, it still shows the error.
Click to expand...
Click to collapse
Try other builds then, that occurs if the size of persist.img is different than what your partition allows. For most the August one should work.
Does this break SafetyNet?
No!
ltf_195 said:
Does this break SafetyNet?
Click to expand...
Click to collapse
Nooo. What even makes you think it does?
Could you update the persist file? mine stuck on oreo..
So basically is it working on any nougat build?
awandroid89 said:
Could you update the persist file? mine stuck on oreo..
So basically is it working on any nougat build?
Click to expand...
Click to collapse
I've updated the guide the new one works no matter what.
Edwin Hamal said:
I've updated the guide the new one works no matter what.
Click to expand...
Click to collapse
Hi..successful to flash the file on august firmware but problem still happen. Do you know why?
TWRP
tajamulbaba said:
Couldn't flash, Error: This image isn't allowed download.
Click to expand...
Click to collapse
Use the twrp method as in this thread:
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restrore-persist-partition-t3765643
Had the same problem, used twrp
CoolPlushBear said:
Use the twrp method as in this thread:
https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restrore-persist-partition-t3765643
Had the same problem, used twrp
Click to expand...
Click to collapse
I've updated my method too.
could you explain why does this happens?
Help me.
IMEI= 0
How to fix it?
Step 7.1 adb devices
Step 7.2 adb push persist.img /sdcard
Worked in my case.
Thanks
---------- Post added at 03:12 AM ---------- Previous post was at 03:10 AM ----------
Now i need to fix my IMEI
...
this can not find file on twrp terminal how i can flash it
Can I re-lock bootloader?
Hi,
Flashing the persist.img seems to have resolved the issue for me also, once I have completed the steps in the guide can I re-lock the bootloader?
I assume as we didn't flash TWRP and only booted into it temporarily should be fine?
Thanks
Related
Hello,
I have MIX 3 Chinese version, unlocked bootloader, flashed latest global. Fine
For security purposes, tried to lock bootloader with fastboot - I knew it may be risky- now the device is in Mi recovery 3, refused to reboot even after erase data.
How to bring it back to life.
Thanks
Use the XiaoMiTool V2.
Google it
Can you enter fastboot mode?, If yes use mi flash and flash original chinese rom.
GVN.Gallus said:
Can you enter fastboot mode?, If yes use mi flash and flash original chinese rom.
Click to expand...
Click to collapse
Yes I can enter fastboot. Even I check bootloader status now locked.
Could you refer a link where all the process is explained? I am not conversant with mi flash.
visit https://www.xiaomitool.com/V2/ and good luck
Nakbleu said:
Yes I can enter fastboot. Even I check bootloader status now locked.
Could you refer a link where all the process is explained? I am not conversant with mi flash.
Click to expand...
Click to collapse
Follow instruction here, make sure to download lastest Miflash and correct rom, for fastboot rom use mifirm.net
grandman1701 said:
visit https://www.xiaomitool.com/V2/ and good luck
Click to expand...
Click to collapse
XiaoMiTool V2 won't be able to unbrick your device in the cases "This MIUI Version can't be installed on this device" error
Nakbleu said:
Yes I can enter fastboot. Even I check bootloader status now locked.
Could you refer a link where all the process is explained? I am not conversant with mi flash.
Click to expand...
Click to collapse
Fastboot is fairly simple. Download the latest Chinese from from miui.com, unzip it, connect your device in fastboot mode, and run the flash_all.bat file. It will take a while and the command prompt window will close when it is finished and your device will reboot.
jcsww said:
Fastboot is fairly simple. Download the latest Chinese from from miui.com, unzip it, connect your device in fastboot mode, and run the flash_all.bat file. It will take a while and the command prompt window will close when it is finished and your device will reboot.
Click to expand...
Click to collapse
I am downloading the ROM.
Please can provide step by step instructions?
My understanding is to:
1. copy the rom in minimal fastboot directory
2. unzip all files in that same directory (or should I create new one?)
3. Execute the command below:
fastboot flash_all.bat
By the way, can I use fastboot with locked bootloader?
Thanks again
Nakbleu said:
I am downloading the ROM.
Please can provide step by step instructions?
My understanding is to:
1. copy the rom in minimal fastboot directory
2. unzip all files in that same directory (or should I create new one?)
3. Execute the command below:
fastboot flash_all.bat
By the way, can I use fastboot with locked bootloader?
Thanks again
Click to expand...
Click to collapse
If you have ADB installed system wide, then it doesn't matter where you unzip the full image to. The best way to have ADB installed system wide is through this method.
You don't need to type anything. Just open the folder the ROM was decompressed in, right click the flash_all.bat, and run it as administrator with your device connected in fastboot mode. It will literally do everything else.
jcsww said:
If you have ADB installed system wide, then it doesn't matter where you unzip the full image to. The best way to have ADB installed system wide is through this method.
You don't need to type anything. Just open the folder the ROM was decompressed in, right click the flash_all.bat, and run it as administrator with your device connected in fastboot mode. It will literally do everything else.
Click to expand...
Click to collapse
I unzip the rom using 7zip, but couldn't find flash_all.bat file!
Nakbleu said:
I unzip the rom using 7zip, but couldn't find flash_all.bat file!
Click to expand...
Click to collapse
Did you install ADB 1.4.3 from the thread linked to? Do you have your device connected to a USB 3 port or USB 2 port? Are you using the cable that came with your device to flash it? Were you booted into the bootloader when trying to flash?
Edit: Read that post wrong. You need to download the fastboot version. You can't flash the TWRP image using fastboot.
jcsww said:
Did you install ADB 1.4.3 from the thread linked to? Do you have your device connected to a USB 3 port or USB 2 port? Are you using the cable that came with your device to flash it? Were you booted into the bootloader when trying to flash?
Edit: Read that post wrong. You need to download the fastboot version. You can't flash the TWRP image using fastboot.
Click to expand...
Click to collapse
Yes I did all that.
I am getting error: Erase is not allowed in lock state.
Any workaround please?
re-unlock the device. it's locked right now.
erbsenmatsch said:
re-unlock the device. it's locked right now.
Click to expand...
Click to collapse
Won't be possible with the Mi unlock software as the phones been wiped - no account, no OEM allowed ticked etc.
in that case, your only hope is: sending it back to china
where did you buy it?
erbsenmatsch said:
in that case, your only hope is: sending it back to china
where did you buy it?
Click to expand...
Click to collapse
In UK. Gray import. I really don't understand why a manufacturer should let this be possible. Why not just make it unlockable with global rom? This will avoid such unwanted situation for everybody. Pissed off by Xiaomi
Hey guys,
VIDEO TUTORIAL:
https://youtu.be/ylBSZk7EqcA o
Someone written a better tutorial or you can follow my video tutorial
https://docs.google.com/document/d/1fdeO9jmm8ewwRX_G0MaGHsVfIVtxgh0yRK0-Yypcl_E/edit?usp=drivesdk
Credits:
@loonycgb2 for the bootloader tutorial
@jsergan[/MENTION] for the root tutorial
@Zackptg5p and whoever helped him for this DM Verity and forceencrypt disabler
Where "21ULMD Kdz file"
I can't found it on web
Ahmed Ismael said:
Where "21ULMD Kdz file"
I can't found it on web
Click to expand...
Click to collapse
https://lg-firmwares.com/downloads-file/20303/G710ULM21d_00_NAO_US_OP_0711
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
Before I flash it I wanted to ask if you notice any performance difference between 11g (oreo) and 21d. Is it just as fast?
ninjamirage said:
https://lg-firmwares.com/downloads-file/20303/G710ULM21d_00_NAO_US_OP_0711
---------- Post added at 07:17 PM ---------- Previous post was at 07:16 PM ----------
Before I flash it I wanted to ask if you notice any performance difference between 11g (oreo) and 21d. Is it just as fast?
Click to expand...
Click to collapse
I Cross-Flash G710ULM20 GFI
Performance increases
I cross-flashed G710pm to G710ulm20e USA. Thanks OP and lge.fun
I only have to ask if you should let magisk manager download and install the updated zip (20.1). I decided not to because it may break the rooted boot image.
ninjamirage said:
I cross-flashed G710pm to G710ulm20e USA. Thanks OP and lge.fun
I only have to ask if you should let magisk manager download and install the updated zip (20.1). I decided not to because it may break the rooted boot image.
Click to expand...
Click to collapse
Nah it works you can update it via twrp or direct install it.
Awesomeslayerg said:
Nah it works you can update it via twrp or direct install it.
Click to expand...
Click to collapse
Thanks. I don't think I need fastboot yet. I am not sure how to erase the LAF partition.
ninjamirage said:
I cross-flashed G710pm to G710ulm20e USA. Thanks OP and lge.fun
I only have to ask if you should let magisk manager download and install the updated zip (20.1). I decided not to because it may break the rooted boot image.
Click to expand...
Click to collapse
ninjamirage said:
Thanks. I don't think I need fastboot yet. I am not sure how to erase the LAF partition.
Click to expand...
Click to collapse
To zero it out use adb shell or the termrnial app then su
The do:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
To get into download mode:
Theres two ways#
1. Get into fastboot mode and set current slot to b
Code:
fastboot --set-active=b
then reboot and hold the up button while its connectrc to your pc and you should be able to get into download mode
2. Boot into twrp, then tap reboot in the menu and on the bottom it should say slot a or b and select b. Then reboot. Dont worry about not being able to mount.
Awesomeslayerg said:
To zero it out use adb shell or the termrnial app then su
The do:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
To get into download mode:
Theres two ways#
1. Get into fastboot mode and set current slot to b
Code:
fastboot --set-active=b
then reboot and hold the up button while its connectrc to your pc and you should be able to get into download mode
2. Boot into twrp, then tap reboot in the menu and on the bottom it should say slot a or b and select b. Then reboot. Dont worry about not being able to mount.
Click to expand...
Click to collapse
Is that for installing a custom rom?
Then do you need to do this?
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.img
ninjamirage said:
Is that for installing a custom rom?
Then do you need to do this?
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.img
Click to expand...
Click to collapse
Yes
This tutorial is trash, I'm tried everything but my device keep getting bricked and bootloop, pls delete it!
CyborgSG said:
This tutorial is trash, I'm tried everything but my device keep getting bricked and bootloop, pls delete it!
Click to expand...
Click to collapse
One person got it to work. I
Can you show the full details of your method, as I'm tried patch both img and it's work, but when I boot to download mode and connect to PC and open LGUp, it's always show unknown model, try flash the img it in fastboot many time, it's always happen like that
CyborgSG said:
This tutorial is trash, I'm tried everything but my device keep getting bricked and bootloop, pls delete it!
Click to expand...
Click to collapse
CyborgSG said:
Can you show the full details of your method, as I'm tried patch both img and it's work, but when I boot to download mode and connect to PC and open LGUp, it's always show unknown model
Click to expand...
Click to collapse
First don't call a tutorial trash cause you didn't do it properly and you didn't even detail the problem properly. . Second, make sure you're still on 11g firmware or go back to 11g firmware via download mode of you're not and then flash the abl partition from the unlocked bootloader tutorial if you havent used that abl. Then fastboot flash rooted 11g boot_a and boot_b file then reboot to firmware and make sure it boots all the way up and restart your PC then try going into download mode again if it works go into fastboot flash the 21ulmd booted rooted image both a and b then immediately restart to download mod
I'm on g710ulm11g and I'm rooted, updated the magisk to 20.1, now do I have to boot to fastboot and boot the twrp20ulmrooted img to boot_a and boot_b and then boot to download mode?
CyborgSG said:
I'm on g710ulm11g and I'm rooted, updated the magisk to 20.1, now do I have to boot to fastboot and boot the twrp20ulmrooted img to boot_a and boot_b and then boot to download mode?
Click to expand...
Click to collapse
Noo. Fastboot flash 21ulmrooted to both a and b then reboot to download mode.
question: I am rooted with magisk and on ULM21d. I have extracted the image file and renamed it "twrp21ulmdroot.img" and put this file on my internal storage /sdcard. When I run the command dd if=/sdcard/twrp21ulmdroot.img of=/dev/block/bootdevice/by-name/boot_a in adb shell (as root #) it keeps giving me a response of dd: /sdcard/twrp21ulmdroot.img: No such file or directory. The file is actually there. Any ideas?
way2aware said:
question: I am rooted with magisk and on ULM21d. I have extracted the image file and renamed it "twrp21ulmdroot.img" and put this file on my internal storage /sdcard. When I run the command dd if=/sdcard/twrp21ulmdroot.img of=/dev/block/bootdevice/by-name/boot_a in adb shell (as root #) it keeps giving me a response of dd: /sdcard/twrp21ulmdroot.img: No such file or directory. The file is actually there. Any ideas?
Click to expand...
Click to collapse
Are you sure you didn't name it twrp21ulmd.img.img? Or reboot the device.. Make sure it's where the Download, pictures etc.. folders are.
Awesomeslayerg said:
Noo. Fastboot flash 21ulmrooted to both a and b then reboot to download mode.
Click to expand...
Click to collapse
When I'm try to boot the twrp20ulmrooted to boot a and boot b, bcoz I want to root on g710ulm20e, then in command it's show up: cannot boot a boot.img *and* ramdisk, so what exactly command I have to use in adb and fastboot?
Awesomeslayerg said:
Are you sure you didn't name it twrp21ulmd.img.img? Or reboot the device.. Make sure it's where the Download, pictures etc.. folders are.
Click to expand...
Click to collapse
sir, your tutorial worked perfectly for me- I now for the first time since owning this phone have a custom recovery. Thank you for your help :good:
Edit: my problem earlier was that the image file was not installing to my internal storage in the right place for whatever reason... /sdcard was not available when searching my int storage. So I dropped the file into 'Download', then used Advanced tools pro file manager to grab it and paste it into the parent directory. At that point the shell commands worked
- Make sure usb debugging is enabled in your developer options menu, your bootloader is unlocked and your critical partitions are unlocked. For instructions, visit https://developer.razer.com/razer-phone-dev-tools/general-instructions/?_ga=2.111753092.1097369801.1578321896-2010083175.1573219083?_ga=2.111753092.1097369801.1578321896-2010083175.1573219083
- Download and extract platform-tools to your desktop (for adb and fastboot functions) here http://https://developer.android.com/studio/releases/platform-tools
- Download the current release on Razers website here http://https://s3.amazonaws.com/cheryl-factory-images/cheryl-p-release-7083-user-full.zip or for a list of releases https://developer.razer.com/razer-phone-dev-tools/factory-images/. Unzip, and copy the boot.img to your phones internal storage.
-Download and install Magisk Manager on your device. https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
-open Magisk Manager, and select install, and when prompted, select "select and patch a file". Choose the boot.img you put in your internal storage.
-Once patching is finished (the patched image will be in the same location as the original image), move the patched boot.img from your phone to your platform-tools folder (will be labeled "magisk_patched.img").
-right-click within the platform-tools folder and select "open powershell window here" or "open cmd prompt here".
-IF USING CMD:
Code:
adb reboot bootloader
-IF USING POWERSHELL:
Code:
./adb reboot bootloader
. Your device should restart and boot into the bootloader.
-next, flash the patched boot image to BOTH slots,
-IF USING CMD:
Code:
fastboot flash boot_a magisk_patched.img
and then
Code:
fastboot flash boot_b magisk_patched.img
-IF USING POWERSHELL:
Code:
./fastboot flash boot_a magisk_patched.img
and then
Code:
./fastboot flash boot_b magisk_patched.img
-Finally, restart your device and verify Magisk is installed via the Magisk Manager app, and that WiFi is working.
NOTE Keep the original boot.img because it can be flashed the same way to revert to stock.
Thanks for this, I had been waiting on a method to root the latest update and this looks like it. Will try it when I get a chance.
Working 100%, thanks again.
Sent from my Phone using Tapatalk
patient81 said:
Working 100%, thanks again.
Sent from my Phone using Tapatalk
Click to expand...
Click to collapse
You're welcome!
After I try flashing <waiting for any device> shows up and nothing happens help
plankton57 said:
After I try flashing <waiting for any device> shows up and nothing happens help
Click to expand...
Click to collapse
I PMed you, in case you still need help.
bdizthebiz said:
I PMed you, in case you still need help.
Click to expand...
Click to collapse
i faced the same issue send help
bdizthebiz said:
I PMed you, in case you still need help.
Click to expand...
Click to collapse
Im having the same issue, stuck on <waiting for any device> in powershell. is there a fix for this?
Anytime tried relocking bootloader after this method?
@bdizthebiz Can you explain what´s the trick please?
Edit: Nevermind. I´ve solved it changing usb driver to Android Bootloader Interface.
Lonewolf007ljp said:
Anytime tried relocking bootloader after this method?
Click to expand...
Click to collapse
no reason to relock your bootloader unless you're getting rid of your phone. Just keep it unlocked.
crombull said:
@bdizthebiz Can you explain what´s the trick please?
Edit: Nevermind. I´ve solved it changing usb driver to Android Bootloader Interface.
Click to expand...
Click to collapse
how to change to android bootloader interface?
---------- Post added at 07:48 AM ---------- Previous post was at 07:29 AM ----------
After I try flashing <waiting for any device> shows up and nothing happens. I tried so many methods and couple hours. please help
Fastboot issue
If you're having issues interacting with your device while its in fastboot, it could be because the appropriate drivers aren't installed. Please refer to this link;
https://s3.amazonaws.com/cheryl-factory-images/How_to_Install_Android_Fastboot_Drivers_on_Windows.pdf
error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot_a Magisk_patched.img
error: cannot load 'Magisk_patched.img': No such file or directory
kevinc999 said:
how to change to android bootloader interface?
---------- Post added at 07:48 AM ---------- Previous post was at 07:29 AM ----------
After I try flashing <waiting for any device> shows up and nothing happens. I tried so many methods and couple hours. please help
Click to expand...
Click to collapse
I changed the properties of the android device in device manager as bdizthebiz user said.
crombull said:
I changed the properties of the android device in device manager as bdizthebiz user said.
Click to expand...
Click to collapse
did that already. still same results
Sorry. I cannot help you. Perhaps using another PC...
Hi, thanks for your guide but before I attempt I am on the November 2019 Security Patch (Android 9), does this matter or do you not know? Sorry if it's a silly question.
this method work for oreo or not?
Hi
I can't flash my redmi note 7 pro.
Bootloader is unlocked: I did the procedure, there is the unlocked logo at boot, and Dev options says "OEM unlock: device already unlocked".
I tried the Pixel Experience way, I ran the command "fastboot flash recovery" under Windows (opens a shell window that immediately closes) and under Linux (nothing happens), and I also tried the Xiaomi flash tool which ends up with a "cannot find the file flash all bat".
Would someone have any idea?
Thanks!!
pata2000 said:
Hi
I can't flash my redmi note 7 pro.
Bootloader is unlocked: I did the procedure, there is the unlocked logo at boot, and Dev options says "OEM unlock: device already unlocked".
I tried the Pixel Experience way, I ran the command "fastboot flash recovery" under Windows (opens a shell window that immediately closes) and under Linux (nothing happens), and I also tried the Xiaomi flash tool which ends up with a "cannot find the file flash all bat".
Would someone have any idea?
Thanks!!
Click to expand...
Click to collapse
Hello,
download platform-tools (ADB) zip and extract it.
download fastboot rom and extract it.
1) copy all the files from "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in" (Total 12 items) folder into extracted platform tools folder.
2) boot device in Fastboot mode and connect it to pc.
3) now open cmd and check if device is detected by pc.
(use following command -> fastboot devices)
4) now close cmd.
5) now go to platform tools folder and double click on "flash_all.bat" file.
6) it will flash ur device with MIUI. DONE.
rasik107 said:
Hello,
download platform-tools (ADB) zip and extract it.
download fastboot rom and extract it.
1) copy all the files from "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in" (Total 12 items) folder into extracted platform tools folder.
2) boot device in Fastboot mode and connect it to pc.
3) now open cmd and check if device is detected by pc.
(use following command -> fastboot devices)
4) now close cmd.
5) now go to platform tools folder and double click on "flash_all.bat" file.
6) it will flash ur device with MIUI. DONE.
Click to expand...
Click to collapse
Thanks a lot for your reply. I'll try that as soon as I have some time.
Just another question:
I am running MIUI Global 11.0.4.0 | Stable (PFGMIXM) at the moment. Which is not the same as you indicated (I believe yours is Indian version dated 22 Oct 2019).
This page does not include any Global rom: https://xiaomifirmwareupdater.com/archive/firmware/violet/
And the Global ROM available on MIUI website under the RN7Pro page (https://c.mi.com//miuidownload/detail?device=1700360) is noted "lavender" and not "violet" - and I do not want to risk installing the wrong firmware, I've read a few topics and it does not ends well.
So bottom line: which one should I work with?
thanks again!
pata2000 said:
Thanks a lot for your reply. I'll try that as soon as I have some time.
Just another question:
I am running MIUI Global 11.0.4.0 | Stable (PFGMIXM) at the moment. Which is not the same as you indicated (I believe yours is Indian version dated 22 Oct 2019).
This page does not include any Global rom: https://xiaomifirmwareupdater.com/archive/firmware/violet/
And the Global ROM available on MIUI website under the RN7Pro page (https://c.mi.com//miuidownload/detail?device=1700360) is noted "lavender" and not "violet" - and I do not want to risk installing the wrong firmware, I've read a few topics and it does not ends well.
So bottom line: which one should I work with?
thanks again!
Click to expand...
Click to collapse
No need to flash Firmware.
just download fastboot rom of your region and u r good to go.
rasik107 said:
No need to flash Firmware.
just download fastboot rom of your region and u r good to go.
Click to expand...
Click to collapse
OK, I've found 2 options:
This one here on XDA:
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
(dowloading the "Fastboot ROM V11.0.6.0")
But it is 11.0.6.0 while my phone is under 11.0.4.0: is this a problem?
This other one:
Note 7 Europe V11.0.4.0.PFGEUXM at: https://www.leakite.com/xiaomi-redmi-note-7-pro-firmware-fastboot-recovery-rom/
It's not exactly the same code (PFGEUXM instead of PFGMIXM), I don't know if it makes any difference?
Sorry for keeping asking question, but I'd better be safe since I am very new to this kind of things...
and thanks a lot for your help and patience.
pata2000 said:
OK, I've found 2 options:
This one here on XDA:
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
(dowloading the "Fastboot ROM V11.0.6.0")
But it is 11.0.6.0 while my phone is under 11.0.4.0: is this a problem?
This other one:
Note 7 Europe V11.0.4.0.PFGEUXM at: https://www.leakite.com/xiaomi-redmi-note-7-pro-firmware-fastboot-recovery-rom/
It's not exactly the same code (PFGEUXM instead of PFGMIXM), I don't know if it makes any difference?
Sorry for keeping asking question, but I'd better be safe since I am very new to this kind of things...
and thanks a lot for your help and patience.
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
this one looks fine.
but make sure it is a fastboot file (.tgz) :good:
rasik107 said:
https://forum.xda-developers.com/redmi-note-7-pro/how-to/miui-11-public-beta-violet-t3973921
this one looks fine.
but make sure it is a fastboot file (.tgz) :good:
Click to expand...
Click to collapse
HI again
it still won't flash no matter what.
I'll deal with it
the reason I wanted to flash was essentially to remove all non necessarry stuff, which I did by following the "remove bloatware" thread.
thanks anyway
pata2000 said:
HI again
it still won't flash no matter what.
I'll deal with it
the reason I wanted to flash was essentially to remove all non necessarry stuff, which I did by following the "remove bloatware" thread.
thanks anyway
Click to expand...
Click to collapse
flash aosp recovery, then adb sideload PE rom
Srikanth0721 said:
flash aosp recovery, then adb sideload PE rom
Click to expand...
Click to collapse
Thanks!
Based on PE instructions (https://telegra.ph/Flashing-PE-for-the-first-time-using-the-AOSP-Recovery--Or-updating-12-06) and if I understand properly:
- I download the firmware and Aosp recovery
- I enter in fastboot and connect the phone to PC, then I type fastboot flash recovery.img (in folder Download+Recovery)
- Then reboot into the new recovery
- Then Tap the power + vol up(2 times vol up) together once or twice and the AOSP recovery menu will pop up
- I then type adb sideload NameofthePErom.zip
- Then: Use the volume keys to select Factory Reset and confirm. ( If you want to format data if not just ignore this part )
- Reboot!
Am I correct?
I'll give it a try even though I don't understand why flashing aosp would work when flashing other stuff didn't... But who knows!
Will let you guys know anyway.
pata2000 said:
Thanks!
Based on PE instructions (https://telegra.ph/Flashing-PE-for-the-first-time-using-the-AOSP-Recovery--Or-updating-12-06) and if I understand properly:
- I download the firmware and Aosp recovery
- I enter in fastboot and connect the phone to PC, then I type fastboot flash recovery.img (in folder Download+Recovery)
- Then reboot into the new recovery
- Then Tap the power + vol up(2 times vol up) together once or twice and the AOSP recovery menu will pop up
- I then type adb sideload NameofthePErom.zip
- Then: Use the volume keys to select Factory Reset and confirm. ( If you want to format data if not just ignore this part )
- Reboot!
Am I correct?
I'll give it a try even though I don't understand why flashing aosp would work when flashing other stuff didn't... But who knows!
Will let you guys know anyway.
Click to expand...
Click to collapse
Also check the recovery in the extracted folder, I got a twrp recovery so I guess I have facee issues with flashme.bat (immediate close).
If u face that issue, download aosp recovery separately or from their telegram channel and flash using fastboot cmd and do the rest..
Srikanth0721 said:
Also check the recovery in the extracted folder, I got a twrp recovery so I guess I have facee issues with flashme.bat (immediate close).
If u face that issue, download aosp recovery separately or from their telegram channel and flash using fastboot cmd and do the rest..
Click to expand...
Click to collapse
well it would not work either. that is not a problem though, I'll survive with the MIUI rom!
thanks
Hi everyone urgently need help root instructions for the xcover 5. there is a possibility it runs with android 11. thank you in advance
akin03 said:
Hi everyone urgently need help root instructions for the xcover 5. there is a possibility it runs with android 11. thank you in advance
Click to expand...
Click to collapse
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Tab E said:
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Click to expand...
Click to collapse
thanks for the instruction. what do I have to type in adb mode. Is there a program where I can use the adb mode.
akin03 said:
thanks for the instruction. what do I have to type in adb mode. Is there a program where I can use the adb mode.
Click to expand...
Click to collapse
There is no program. You have to download adb and fastboot tools
Once your phone is in fastboot mode and you have opened command prompt in adb fastboot folder in you pc type
fastboot oem unlock (this unlocks the bootloader)
fastboot flash boot boot.img (this flashed the magisk patched or rooted boot.img to your devices boot partition
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Patch Stock Boot Image via Magisk and Flash it using Fastboot
This tutorial contains explanation on how to Patch Stock Boot Image file of your device and subsequently flash it via Magisk.
www.droidwin.com
Tab E said:
There is no program. You have to download adb and fastboot tools
Once your phone is in fastboot mode and you have opened command prompt in adb fastboot folder in you pc type
fastboot oem unlock (this unlocks the bootloader)
fastboot flash boot boot.img (this flashed the magisk patched or rooted boot.img to your devices boot partition
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
Patch Stock Boot Image via Magisk and Flash it using Fastboot
This tutorial contains explanation on how to Patch Stock Boot Image file of your device and subsequently flash it via Magisk.
www.droidwin.com
Click to expand...
Click to collapse
Thanks for the instructions. Did it as described. However, I'm stuck in fastboot mode when sending. Is there a guide or a way to flash the patched file via odin?
akin03 said:
Thanks for the instructions. Did it as described. However, I'm stuck in fastboot mode when sending. Is there a guide or a way to flash the patched file via odin?
Click to expand...
Click to collapse
Yes. Compress the file to '.tar' and flash it
Tab E said:
Yes. Compress the file to '.tar' and flash it
Click to expand...
Click to collapse
Ok just the patched file? And do I have to pay attention to something?? Flashing via AP or BL?
akin03 said:
Ok just the patched file? And do I have to pay attention to something?? Flashing via AP or BL?
Click to expand...
Click to collapse
Ap
Tab E said:
Ap
Click to expand...
Click to collapse
Hi does not get errors on odin. Do I just need to flash the patched file or other files.
Request for help.. Have flashed the whole ap file about magisk after a guide now I have bootloop and the device restarts after 3 min. I don't get the device rooted
Hi. Is n'one who can help me...! It's important...?!
akin03 said:
Hi. Is n'one who can help me...! It's important.
Click to expand...
Click to collapse
Hi, if you send me the exact ROM of your device I can create a Root-AP file (boot.tar) for you which you flash through Odin (AP). Note that after flashing the Root file your phone will be factory reseted.
akin03 said:
Hi. Is n'one who can help me...! It's important...?!
Click to expand...
Click to collapse
Or you can follow this guide, it is the exact same process of rooting newer samsung devices.
How to root Samsung Galaxy X Cover 4s Enterprise Edition (SM-G398F)
Hey there, is there a way to root a Samsung Galaxy X Cover 4s (SM-G398F)? The phone is from June 2019 and runs Android 9.0. I haven't found anything on the forum. Here's a link to the Samsung website...
forum.xda-developers.com
I tried to patch the updated AP (boot loop)
I tried to flash the stock AP and then only the updated boot.img (boot loop)
I also tried flashing a patched recovery.img (HASH_MISMATCH error)
Maybe Magisk has some issues with that phone.
Did anyone have success in rooting the G525F?
hatl said:
I tried to patch the updated AP (boot loop)
I tried to flash the stock AP and then only the updated boot.img (boot loop)
I also tried flashing a patched recovery.img (HASH_MISMATCH error)
Maybe Magisk has some issues with that phone.
Did anyone have success in rooting the G525F?
Click to expand...
Click to collapse
How to Root via Magisk Patch:
1) Download and open the stock ROM
2) Extract the boot.img.lz4 and convert it to boot.img with a program like lz4_win64
3) Convert the boot.img to boot.tar with 7zip or winRAR
4) Copy boot.tar to your mobile phone and patch it with Magisk, so you will get magisk-patched.tar
5) Rename the patched magisk-patched.tar to boot.tar
6) Flash it with Odin in AP mode and you are rooted!
Only this method worked for me, if you try it differently it may not work! (Xcover4s)
Should work on all Samsung phones with Android 9 or higher.
I did this with the latest ATO firmware: https://samfw.com/firmware/SM-G525F/ATO
and ended up in a boot loop.
Maybe it's an issue with the latest Android 11 version - or the Xcover 5
I have the same issue . Stuck on boot screen after flashing. Works fine after I re-flash original boot or do a complete re-flash with original firmware. I can successfully root my s9 so am not a complete noob. My region is NEE
One more weird thing is that i cant seem to get it in recovery after the rooted boot flash. Any ideas for checking relevant logs?
There is a extra file in the boot.img called vmbeta compared to the s9 boot.img. Is it possible that this is the issue or am i completely wrong?
How to create a custom signed vbmeta.img for Unisoc using AVBtool
If you're into rooting and flashing custom recoveries then Android Verified Boot (AVB) or dmverity is something you should be aware of. We'd dropped a blog post on why dmverity could be causing your p
forum.hovatek.com
[CLOSED] What is "vbmeta.img" ?
What is "vbmeta.img" and why it is needed? How it works? Does anybody knows?
forum.xda-developers.com
ive tried like evverything but get stuck on a message sayying my phone isnt running on offical firmwire or something like that. But now i have another problem. When in fastboot adb cant find my device. If my phone is just on and im not in fastboot adb finds it. Why is that happening?
Tab E said:
Download the boot.img of your device. Transfer it to your phone. Install the magisk manager app. Click on install. Click on select file to patch. Locate your boot.img and click on it. The output file will be in internal storage/downloads. Copy this to you adb fastboot folder. Rename it to boot.img
Open command prompt in the adb window. Enable oem unlocking on phone , reboot to fastboot mode Unlock your phones boot loader, with fastboot oem unlock and then fastboot flash boot boot.img
https://github.com/topjohnwu/Magisk/releases/download/manager-v8.0.7/MagiskManager-v8.0.7.apk
Click to expand...
Click to collapse
When my phone is in fastboot mode it cant find it.. WHen its on adb devices finds it but not when in fastboot mode.
A search for "root xcover 5" brings up plenty of ways to achieve this, but most of those sites are click bait, with identical instructions for any device you can think of. Other people are more helpful, like those who replied above, but I would like to know if anyone has ACTUALLY ROOTED A XCOVER 5 SUCCESSFULLY. And yes, if so, I'd like to know how it was done.