Hi i follow some tutorials from youtube teaching how root my rom stock, flash a custom recovery and install cm12.1.
i used the FreeGee.apk to install the TWRP recovery. A was going to flash the cm12.1(for the e975, yes in a lot of tutorials it works ) but it fails, get a error i dont know why.
I try to wipe cache and dalvik cache like the tutorial, but unfornally i wipe all sdcard.
So, a dont have the stock rom, dont have the zip to flash a new rom.
I cant mount the mtp in this TWRP 2.6.1 recovery that free gee installs.
I cant use fastboot too, I type fastboot device and none.
I try a lot of drivers and windows 10 and 7. nothing.
can a good soul help me?
obs.: idk if it is normal, but in the bootloader screen it shows device -mako, variant - mako 32gb
Do you have a Error with the cm-12.1 zip in recovery?... It is happening to me too...
I had to flash cm12-20140416 zip file...
Remember Factory Reset, Cche and dalvik format
After flashing the Syberia 9.0 rom into my mix 2, my phone stuck in the fastboot mode. Every time I tried to reboot my phone, my phone will go right into the fastboot mode. I could get into the TWRP, and I perform the 'wipe' serval times.
This is what happens on my phone:
wipe the system---- flash the rom ------ reboot ----- fastboot mode
I don't know what happens with my phone. Pls help me guys:crying:
Could I try to use the official miui fastboot update via the mi flash?
Try installing again with "Clean Flash". Wipe System, Cache/Dalvik and format Data (don't wipe data).
Backup your data first, because your data will destroy.
I believe you should already have the ROM, Firmware and Gapps into internal storage.
Now boot to recovery.
Wipe Data (if u are decrypted, format data)
But be aware that formatting Data means that you have to again copy everything back to internal storage using adb. So my advice is to just wipe and see if that works out.
Install Firmware, ROM and Gapps zip.
Order of installation should be same.
Reboot - 1st boot may take some time.
So here's what I did to cause my phone to get stuck on the logo screen:
1. Unlocked my phone using the Mi Unlock
2. Used ADB to install twrp-3.3.1-0-nitrogen
3. I couldn't mount my Data or SD Card folders due to encryption, so someone told me to use TWRP to format data, which I did. It didn't boot up after that.
I've tried the following fixes:
1. TWRP > Advanced Wipe > Cache / Data / Internal Storage / System
2. TWRP > Install > MIUI 11 V11.0.2.0.PEDCNXM
3. TWRP > Install > MIUI 11 V11.0.3.0.PEDCNXM
4. TWRP > Install > Magisk-v20.4
No luck, still stuck on boot. Anyone kind enough to please help?
I had the same problem when I backed up the global rom with OrangeFox and restarted the system without installing anything.
The following procedure worked for me.
User the latest version of TWRP 3.3.1 do not use OrangeFox
1. First you must remove the encryption, Wipe> Format Data, confirm by typing "yes"
2. Advanced Wipe and clean Dalvik, Cache, Data, System and Vendor.
3. Then proceed with the installation.
In my case I installed xiaomi.eu_multi_MIMAX3_V11.0.2.0.QEDCNXM_v11-10
Hope this helps!
irinho said:
I had the same problem when I backed up the global rom with OrangeFox and restarted the system without installing anything.
The following procedure worked for me.
User the latest version of TWRP 3.3.1 do not use OrangeFox
1. First you must remove the encryption, Wipe> Format Data, confirm by typing "yes"
2. Advanced Wipe and clean Dalvik, Cache, Data, System and Vendor.
3. Then proceed with the installation.
In my case I installed xiaomi.eu_multi_MIMAX3_V11.0.2.0.QEDCNXM_v11-10
Hope this helps!
Click to expand...
Click to collapse
Thanks a lot for the reply!
I somehow managed to get it working with OrangeFox, so I'm going to try it for awhile till it breaks. But I can't seem to pass the SafetyNet Check in Magisk, so I might have to your tips eventually.
What I did was:
1. Use the MI Flash tool + 11.03 CN Fastboot ROM to get out of the boot loop.
2. Loaded OrangeFox-R10.1-stable-nitrogen and Magisk-v20.4 on an SD Card
3. ADB + Fastboot to install twrp-3.3.1-0-nitrogen, then installed OrangeFox
4. Using OrangeFox, installed Magisk-v20.4
Hadron001 said:
Thanks a lot for the reply!
I somehow managed to get it working with OrangeFox, so I'm going to try it for awhile till it breaks. But I can't seem to pass the SafetyNet Check in Magisk, so I might have to your tips eventually.
What I did was:
1. Use the MI Flash tool + 11.03 CN Fastboot ROM to get out of the boot loop.
2. Loaded OrangeFox-R10.1-stable-nitrogen and Magisk-v20.4 on an SD Card
3. ADB + Fastboot to install twrp-3.3.1-0-nitrogen, then installed OrangeFox
4. Using OrangeFox, installed Magisk-v20.4
Click to expand...
Click to collapse
I have not yet rooted with magisk on xiaomi.eu so I have no way of giving an opinion on what may have gone wrong in your case.
But did you install the most current magisk from magisk.me and clear the cache?
maybe this video can help you. shows a Brazilian installing orangefox and rooting with magisk in the global rom and everything works, Magisk passes the SafetyNet test. https://youtu.be/O5bq1HMFREI?t=328
Hi everyone
yesterday i receveived the android 10 update OTA for my redmi note 8 global and i updated it
i ve been using OrangeFox recovery since months and everything worked fine until yesterday
i can no more upload files to phone using recovery it shows 0 MB space i reinstalled ginkgo_global_images_V12.0.3.0.QCOMIXM_20201226.0000.00_10.0_global using fastboot then installed again twrp but after every reboot no more custom recovery only MI recovery 3.0 i have to install it everytime now and anyway in twrp or orangefox i can do anything there are strange files names it just seems it can t decrypt data to work properly ( i have no password set btw ) i formated data and same thing
Anyone can help please
be sure that ur phone is unlocked and enable USB debug
here are talking about an issue about installing a custom recovery or an issue in phone storage
I use fox too but I flashed the TWRP 1st using TOOL ALL IN ONE installed it without any issue then flashed fox from a flashable zip
for the memory issue I had it too it started with no being able to copy files that are 4Go or more to the internal memory so I flashed a the stock rom again and the memory become 0 and not accessible
but in my case fox was working so I went to wipe tab and wiped everything after ejecting the memory card in the reboot it said the system was destroyed I flashed the rom again and the issue was resolved
but before u do that make sure the phone is unlocked if not u wont be able to flash anything
Requirements: miui 12.0.3 china stable fastboot rom.
Orangefox recovery;
Custom rom of your choice;
Example xiaomi .eu 12.0.3 stable
Device: gingko(redmi note 8)
Note: make sure your bootloader is unlocked;
Backup your data before doing anything.
This guide is working and tested .
*If anything goes wrong i will not be responsible*
*Its your choice*
Make sure to check clean all button on mi flash tool.
(Do not check clean all and lock)
Flash miui 12.0.3 stable china fastboot rom using mi flash tool in fastboot mode;
After rom flashed complete the setup;
,boot phone in fastboot and flash twrp
Next boot to twrp ,allow modification.
Next move orange fox recovery to phone storage while connected on pc .
Flash orange fox ,
now your phone will boot
Into orangefox
Move custom rom of ur choice to phone storage while connected on pc.
Next
,wipe delvik
, system ,
data
cache,
vendor.
Flash any custom rom of your choice .
If phone reboots to orangefox itself just got to wipe and choose format data and type yes;
The after wiping done,
Reboot
complete the setup
Download magisk 21.3 stable
Move to phone storage
Reboot to orangefox recovery
Flash magisk ;
Reboot
Install magisk manager if manager is not showing,
Now your will be rooted
,your done.
Ive already flashed a few phones, but this is the first time that Ive got CMD error "FAILED (remote: (recovery_a) No such partition)". So I booted twrp.img, falshed ArrowOS and TWRP from within TWRP and it said something about Slot A and B, which I dont understand ... some guide also said to Format Data, which I did, and then I just could boot into TWRP in Slot A, and no OS on Slot B, which rebooted me into Slot A. I couldnt find any info about this and I dont know what to do. Anybody knows how to properly flash TWRP and custom ROMs please ?
Start fresh by flashing stock MIUI rom through fastboot and proceed from there
1 Boot once into MIUI and reboot into fastboot
2 fastboot boot twrp.img (from platform tools folder)
3 Flash custom rom like ArrowsOS with inject twrp option checked
4 Reboot recovery
5 Format Data by typing "yes"
6 Reboot to system
7 Done
Follow the TWRP install instructions by fastboot boot TWRP.img
advanced, install TWRP
It should then reboot and TWRP will be installed
Then proceed as above by flashing a ROM e.g ArrowOS with TWRP inject.
Then reboot TWRP and wipe data
Use "fastboot boot TWRP.img" to temporarily boot TWRP.
You can install TWRP by using "Install to Ramdisk" inside TWRP and selecting TWRP.img
Cvenda said:
Ive already flashed a few phones, but this is the first time that Ive got CMD error "FAILED (remote: (recovery_a) No such partition)". So I booted twrp.img, falshed ArrowOS and TWRP from within TWRP and it said something about Slot A and B, which I dont understand ... some guide also said to Format Data, which I did, and then I just could boot into TWRP in Slot A, and no OS on Slot B, which rebooted me into Slot A. I couldnt find any info about this and I dont know what to do. Anybody knows how to properly flash TWRP and custom ROMs please ?
Click to expand...
Click to collapse
Did you manage to fix it? I got into the same problem, I could only fix it downloading the most updated version of adb/fastboot. I don't remember where I downloaded it, but it was what solved this problem for me.
pedrowood said:
Did you manage to fix it? I got into the same problem, I could only fix it downloading the most updated version of adb/fastboot. I don't remember where I downloaded it, but it was what solved this problem for me.
Click to expand...
Click to collapse
well Iam still confused about that Slot A/B thing, but since Ive probably bricked my phone, I flashed the fastboot ROM through MiFlasher and I havent tried flashing TWRP or custom ROM since, there are some things I really like about MIUI so Iam gonna see which ROM Iam gonna choose in the future
Cvenda said:
well Iam still confused about that Slot A/B thing, but since Ive probably bricked my phone, I flashed the fastboot ROM through MiFlasher and I havent tried flashing TWRP or custom ROM since, there are some things I really like about MIUI so Iam gonna see which ROM Iam gonna choose in the future
Click to expand...
Click to collapse
Slot A and B refer to Project Treble, where there are 2 separate partitions. 1 for OEM like Samsung and other for core Android OS. That way Google can update the OS partition with security updates without having to wait for Samsung to implement those security update into their version of Android, as was the case before Galaxy S9. Needless to say, this way security updates get pushed out way faster, because there is no need to wait an entire year (I'm looking at you Samsung) for OEM to finally implement it. Hope this clears things up for you.
Milan-XDA said:
Slot A and B refer to Project Treble, where there are 2 separate partitions. 1 for OEM like Samsung and other for core Android OS. That way Google can update the OS partition with security updates without having to wait for Samsung to implement those security update into their version of Android, as was the case before Galaxy S9. Needless to say, this way security updates get pushed out way faster, because there is no need to wait an entire year (I'm looking at you Samsung) for OEM to finally implement it. Hope this clears things up for you.
Click to expand...
Click to collapse
reason for slots
Robert314 said:
Follow the TWRP install instructions by fastboot boot TWRP.img
advanced, install TWRP
It should then reboot and TWRP will be installed
Then proceed as above by flashing a ROM e.g ArrowOS with TWRP inject.
Then reboot TWRP and wipe data
Click to expand...
Click to collapse
there is a slight problem with this ... I cannot upload any file to the phone, because I have wiped Data, so there is no folder that I can access from the PC, so I can only sideload .zip files, and most of the .zip files just doesnt work for some reason, only ArrowOS, but not the PixelExtended, nor CrDroid ... I cannot even sideload TWRP.img to install it into ramdisk
EDIT: after sideloading ArrowOS and booting TWRP using "fastboot boot twrp.img", I can access internal storage, so I uploaded twrp.img into /sdcard/Download folder, installed it into ramdisk, rebooted to Recovery and now successfully flashing CrDroid ROM that I uploaded to /sdcard/Download
Cvenda said:
there is a slight problem with this ... I cannot upload any file to the phone, because I have wiped Data, so there is no folder that I can access from the PC, so I can only sideload .zip files, and most of the .zip files just doesnt work for some reason, only ArrowOS, but not the PixelExtended, nor CrDroid ... I cannot even sideload TWRP.img to install it into ramdisk
Click to expand...
Click to collapse
You can adb transfer files in TWRP. You could also use a USB stick connected via OTG cable
Robert314 said:
You can adb transfer files in TWRP. You could also use a USB stick connected via OTG cable
Click to expand...
Click to collapse
its behaving so randomly ... I often get error kInstallDeviceOpenError, even tho I successfully installed that ROM at least one time ... I dont know which slot (A/B) to use and when ... now I have ArrowOS in slot A and CrDroid ins lot B, and I cannot flash anything from booted TWRP.img ... Iam gonna try to install TWRP into ramdisk again from USB OTG
Cvenda said:
its behaving so randomly ... I often get error kInstallDeviceOpenError, even tho I successfully installed that ROM at least one time ... I dont know which slot (A/B) to use and when ... now I have ArrowOS in slot A and CrDroid ins lot B, and I cannot flash anything from booted TWRP.img ... Iam gonna try to install TWRP into ramdisk again from USB OTG
Click to expand...
Click to collapse
In order to wipe the super partition (both A/B and data) flash Xiaomi.eu and then wipe data
Robert314 said:
In order to wipe the super partition (both A/B and data) flash Xiaomi.eu and then wipe data
Click to expand...
Click to collapse
how exactly should I proceed ? flash fastboot stock ROM with MiFlasher, boot into bootloader, boot twrp.img, wipe data, and then what ? which slot do I choose ? should I install TWRP into ramdisk, reboot into recovery and then flash custom ROM ?
Cvenda said:
how exactly should I proceed ? flash fastboot stock ROM with MiFlasher, boot into bootloader, boot twrp.img, wipe data, and then what ? which slot do I choose ? should I install TWRP into ramdisk, reboot into recovery and then flash custom ROM ?
Click to expand...
Click to collapse
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Clean Install of Xiaomi.eu ROM:
Flash Stock ROM with Mi Flash
Boot System once (to create /data)
Boot TWRP from Nebrassy or @Vasishoth
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
dreamytom said:
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Clean Install of Xiaomi.eu ROM:
Flash Stock ROM with Mi Flash
Boot System once (to create /data)
Boot TWRP from Nebrassy or @Vasishoth
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
Click to expand...
Click to collapse
in case of flashing custom ROM, are the steps same ? just instead of Xiaomi.eu ROM I flash PE, or CrDroid ? and should I format data and dalvik also or wipe data (that option where I need to type YES) ? Ive found official guide for flashing CrDroid, but Iam stuck st booting animation for 30 minutes
Cvenda said:
in case of flashing custom ROM, are the steps same ? just instead of Xiaomi.eu ROM I flash PE, or CrDroid ? and should I format data and dalvik also or wipe data (that option where I need to type YES) ? Ive found official guide for flashing CrDroid, but Iam stuck st booting animation for 30 minutes
Click to expand...
Click to collapse
Go into TWRP and press wipe then format data (type yes).
regedit12345 said:
Go into TWRP and press wipe then format data (type yes).
Click to expand...
Click to collapse
I have stock rom in slot A (bootable and working) and custom rom in slot B (stuck at booting animation), and I should format data while being in slot A right ?
Cvenda said:
I have stock rom in slot A (bootable and working) and custom rom in slot B (stuck at booting animation), and I should format data while being in slot A right ?
Click to expand...
Click to collapse
Doesn't matter. Just select format data > yes > reboot to system
regedit12345 said:
Doesn't matter. Just select format data > yes > reboot to system
Click to expand...
Click to collapse
sooo what seemes to work for me now is, that I formated data, then flashed PE ROM from OTG and booted into it without any problems