Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mrtr33 said:
Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
View attachment 5264033
Click to expand...
Click to collapse
hey does your device have an working os ?
mrtr33 said:
Hello,
I am not sure if I am right here, because I have a Xiaomi Redmi Note 9 Pro Global, but here is no place for this model.
Besides that I have a small, I guess it is a big problem, with my Phone.
I tried to install the clean version of MiUI with the XiamiTool V2 ... but the whole Story started one week ago:
About one week ago I tried to reinstall my Phone with the XiamiTool V2. Everything looked good, it found my model and even told me that it can download the custom rom automatically. But I had the 7 day lock. So I waited.
Yesterday I tried it again. But the tool was not shown the custom rom anymore. It didn't even find the correct TWRP.
After a bit research I found the codename joyeuse for my phone. I downloaded the TWRP and custom rom for it, gave it to the tool and it worked.
But then ... my phone booted only into TWRP. The tool did not recognize my phone.
After a bit of google I find the Xiaomi Flash Tool. But the tool tells me that my device and rom version are missmatching. Now I am stuck and don't know what to do.
/Edit:
I just checked online which phone I have:
View attachment 5264033
Click to expand...
Click to collapse
if your device has a working os ... enable usb debugging and oem unlock .... boot into fastboot ... connect to pc .... use adb to flash new twrp which is supported
Benjamin0702 said:
hey does your device have an working os ?
Click to expand...
Click to collapse
Benjamin0702 said:
if your device has a working os ... enable usb debugging and oem unlock .... boot into fastboot ... connect to pc .... use adb to flash new twrp which is supported
Click to expand...
Click to collapse
Like I said, I am stuck in TWRP. I can't boot anything and I guess I don't have any os anymore.
Are you frozen in a black screen?
Now I was able to bring back my phone to the original ROM. The flash_all.sh works for me great.
But how do I install the clean xiaomi.eu version?
I tried this video, but it still keeps rebooting into TWRP.
mrtr33 said:
Now I was able to bring back my phone to the original ROM. The flash_all.sh works for me great.
But how do I install the clean xiaomi.eu version?
I tried this video, but it still keeps rebooting into TWRP.
Click to expand...
Click to collapse
You need to erase the "misc" partition.
VD171 said:
You need to erase the "misc" partition.
Click to expand...
Click to collapse
Which one is the "misc" partition? This is the only thing I can erase.
Also I have this error when I do any action in the first line of my terminal output:
E: unable to update logical partition: /system_ext
mrtr33 said:
View attachment 5264227
Which one is the "misc" partition? This is the only thing I can erase.
Also I have this error when I do any action in the first line of my terminal output:
E: unable to update logical partition: /system_ext
Click to expand...
Click to collapse
Read here: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
VD171 said:
Read here: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Click to expand...
Click to collapse
Now I get the following error when trying to install the xiaomi.eu ROM form SD Card:
Code:
E: unable to update logical partition: /system_ext
E: unable to decrypt FBE device
After installating and rebooting I am back at TWRP again.
Related
I AM NOT RESPONSIBLE FOR BRICKED DEVICES, DEAD SD CARDS,
THERMONUCLEAR WAR.YOU ARE CHOOSING TO MAKE THESE MODIFICATIONS, AND IF
YOU POINT THE FINGER AT ME FOR MESSING UP YOUR DEVICE, I WILL LAUGH AT YOU. HARD. A LOT.
THIS GUIDE WILL HELP YOU TO ERASE PARTITION TABLE AND RESTORE STOCK PARTITION TABLE OF REDMI 2.
IF YOU MESSED UP WITH YOUR PHONE PARTITION TABLE, OR SOMETHING ELSE.
THIS WILL REWRITE THE WHOLE PARTITION TABLE FOR YOUR PHONE RATHER SIMPLY FLASHING THE PARTITIONS.
REQUIRMENTS:
1.) REDMI 2 (ANY VARIANT) CHARGED ABOVE 75%.
2.) A WINDOWS PC.
3.) MI FLASH TOOL AND GET IT INSTALLED. ---> http://en.miui.com/thread-339517-1-1.html
ALTERNATE MI FLASH TOOL IF YOUR DEVICE IS NOT DETECTED AFTER RUNNING .BAT FILE--> https://1drv.ms/u/s!AjRyVY8i_bd1nURHfzNelaEUosue
4.) MI FASTBOOT ROM DOWNLOAD AND EXTRACT IT. ---> http://en.miui.com/forum.php?mod=viewthread&tid=439829
(I RECOMMEND 1 GB VARIANTS OWNER TO DOWNLOAD REDMI 2 PRIME FASTBOOT ROM.)
5.) ERASE_PARTITION_TABLE.zip FROM ATTACHMENTS.
PROCEDURE:
1.) DOWNLOAD AND EXTRACT ERASE_PARTITION_TABLE.zip
2.) CONNECT YOUR DEVICE TO PC IN FASTBOOT MODE.
3.) RUN .BAT FILE FROM ERASE_PARTITION_TABLE.zip
4.) A DIALOG FROM WINDOWS WILL APPEAR TO FORMAT DRIVE. JUST CLICK CANCEL.
5.)YOU PHONE SCREEN WILL BE BLACK. DONT PULL OUT USB CABLE.
6.)RUN MI FLASH TOOL AND FLASH DOWNLOADED REDMI 2 PRIME FASTBOOT ROM USING FLASH_ALL.BAT
7.) AFTER 5-10 MINS YOUR PHONE WILL BOOT INTO MIUI ROM.
8.) TO USE CUSTOM ROM FLASH APPROPRIATE CUSTOM RECCOVERY AND ROM.
HOPE THIS FIXES ALL ISSEUES RELATED TO MODEL NUMBER CHANGE,VO-LTE, etc,etc,etc.
Simply reserved.
It hard bricked my phone, not showing in miflash and can't go into recovery or fastboot mode. Only showing as Local Disk G in pc
Bhargab Deka said:
It hard bricked my phone, not showing in miflash and can't go into recovery or fastboot mode. Only showing as Local Disk G in pc
Click to expand...
Click to collapse
Does it show as HS Q loader something?
aashishdamrait said:
Does it show as HS Q loader something?
Click to expand...
Click to collapse
Its showing qualcomm hs usb diagnostics 9006 (com11) in device manager -ports
it happened here too, what should I do????
---------- Post added at 16:46 ---------- Previous post was at 16:17 ----------
@aashishdamrait I was scared as **** bro, my device was black and 23 disk partitions opened in the windows, but I managed to revive the device by using the other mi flash, that was scary as hell
@TecnoTailsPlays
Now, I hope phone is working fine?
aashishdamrait said:
@TecnoTailsPlays
Now, I hope phone is working fine?
Click to expand...
Click to collapse
Yep, back to normal state
@TecnoTailsPlays
Did this fixed random reboots for you?
aashishdamrait said:
@TecnoTailsPlays
Did this fixed random reboots for you?
Click to expand...
Click to collapse
Nope
ASK a senior member
I have to problem with flashing xiaomi redmi 2 prime HM2014813 as a notifcation unspecified error( 0×80004005) failed ( remote : failed to write partition)
Please help me a lord
How can it fixed flashing xiaomi redmi 2 prime hm2014813?
Sent from my SM-J500G using Tapatalk
IAM_COOL49 said:
ASK a senior member
I have to problem with flashing xiaomi redmi 2 prime HM2014813 as a notifcation unspecified error( 0×80004005) failed ( remote : failed to write partition)
Click to expand...
Click to collapse
Kindly Send the Screenshots.
do tell me about the Mi flash tool you are using , rom and and.
aashishdamrait said:
Kindly Send the Screenshots.
do tell me about the Mi flash tool you are using , rom and and.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Run "erase_partition_table.bat" again.
do verify you have selected all the files under browse category like patch.xml.
Okay i'm trying flash using erase partition a lord
I messed up with my mi3w
can I use it on my mi3w? Will it work ?
it works. thanks for the guide I have Redmi 2 Pro wt88047.
aashishdamrait said:
Run "erase_partition_table.bat" again.
do verify you have selected all the files under browse category like patch.xml.
Click to expand...
Click to collapse
Hey, I have a problem with my Redmi 2 version 2014813 and I can only access TWRP, whenever I try to flash any compatible ROM I get the errors I attached in the picture.
Also when I try to flash via fastboot it fails --> fastboot flash partition gpt_both0.bin --> FAILED to write partition
Any idea how to try to fix this? You think your scrip for the partition table can help?
Adi59 said:
Hey, I have a problem with my Redmi 2 version 2014813 and I can only access TWRP, whenever I try to flash any compatible ROM I get the errors I attached in the picture.
Also when I try to flash via fastboot it fails --> fastboot flash partition gpt_both0.bin --> FAILED to write partition
Any idea how to try to fix this? You think your scrip for the partition table can help?
Click to expand...
Click to collapse
Same here. Did you find a solution ?
oferyuval said:
Same here. Did you find a solution ?
Click to expand...
Click to collapse
I tried many different ways to flash any ROM into it without any success. I read somewhere in the miui eu forums that the redmi2 pro had a stupid software update that was not meant for one type of emmc and broke it. Someone who contacted the Chinese support got his/her phone swapped or money back.
I still have the phone in same condition hoping to manage one day to replace the emmc chip. I think that will fix the issue.
EDIT: original post:
"Bad news - Redmi 2 the series 2014813 has faulty NAND memory. After 1 to 1.5 year of operation the memory dies. First warning is "App stopped working" message. Then the phone dies and after rebooting you see just the Mi logo.
Flashing new ROM usualy fixes this problem and phone works for 1-2 months without problems. Then the fault apears again and it is end for the phone. You can enter fastboot mode, TWRP, but there is no was how to write any data to internal memory. Fastboot, TWRP nor MiFlash do not work because this is a hardware problem. The only way is replacing NAND memory, but this is extremely complicated task." source: http://en.miui.com/thread-268891-3-1.html
EDIT2: check this thread also: https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171
Hi im trying to find if there has been proper recovery made for the x704a devices and if there is actually custom roms that support the x704a . I've searched and searched and cant find much solid info. I see tons of the 704f, l, etc. but cant find anything specific or will work with the x704a for sure. I have the tablet with the stock android 71.1. rom and its a buggy mess always lagging and have to restart multiple times a day just to be able to try to use it. And its done this from day one and even after reflashing the stock rom from scratch. Trying to find options to make this thing better vs throwing it in the trash and wasting the money i paid for it. All help would be appreciated . Thanks in advance
Hi I am using a recovery that works with the x704a its hard to find I will have a look for a link or I can send you the file.
Regards Ashley
Download the onekey unlock and the twrp.
The default language is Chinese.
https://drive.google.com/open?id=1H5k46hztwj_1FeBxzfFIXqo5hy0OpJvr
So what custom roms have you guys found for these?
Sent from my HD1925 using Tapatalk
This tablet blows...x704a
I watched tons of reviews on the Lenovo tab 10. All positive reviews. So, when I found a version with 1 less gig of ram but cellular support I jumped on it as a $200 gift for my wife. Lenovo, the Amazon seller used the same exact name for the x704f and x704a.. they are not the same , this tablet blows. I ended up getting her another tablet and we are stuck with this pos. I would like to get a rooted cfw like lineage and no luck so far.
I have the same problem! My tablet is a lenovo tab x704A and only information about x704F appears, I don't know if it is the same, then try with that info, unlock the bootloader, download the twrp recovery for x704F when flashing it tells me that the procedure was a success, but the device It does not restart in twrp recovery, I did everything using the commands, I did it manually from the tab and nothing is only the original recovery (oem) as if I had not installed it, it must be because that recovery is not compatible. If you can help me!
Tegra4Me said:
This tablet blows...x704a
I watched tons of reviews on the Lenovo tab 10. All positive reviews. So, when I found a version with 1 less gig of ram but cellular support I jumped on it as a $200 gift for my wife. Lenovo, the Amazon seller used the same exact name for the x704f and x704a.. they are not the same , this tablet blows. I ended up getting her another tablet and we are stuck with this pos. I would like to get a rooted cfw like lineage and no luck so far.
Click to expand...
Click to collapse
Are you talking about Lenovo Tab4 10 x704A ? Is that the one with the ATT logo on the back, cuz I have that (one with 2gb of ram) and its rooted with magisk and has lineage OS and works great. You do need a special twrp file though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
manny71 said:
I have the same problem! My tablet is a lenovo tab x704A and only information about x704F appears, I don't know if it is the same, then try with that info, unlock the bootloader, download the twrp recovery for x704F when flashing it tells me that the procedure was a success, but the device It does not restart in twrp recovery, I did everything using the commands, I did it manually from the tab and nothing is only the original recovery (oem) as if I had not installed it, it must be because that recovery is not compatible. If you can help me!
Click to expand...
Click to collapse
I have Lenovo tab x704A its one with the ATT logo on the back right? It uses a special twrp file that only works with x704A recovery-TWRP-3.3.0-0521-LENOVO_TBX704A-CN-wzsx150.img . No other x704 variants twrps work on x704A and I have tried. Download that try to flash that to your recovery. I used this ROM https://forum.xda-developers.com/t/...neageos-16-0-for-lenovo-tab4-10-plus.3923394/
I haven't gotten to try the newer OS10 Lineage 17.
Folty57fg said:
I have Lenovo tab x704A its one with the ATT logo on the back right? It uses a special twrp file that only works with x704A recovery-TWRP-3.3.0-0521-LENOVO_TBX704A-CN-wzsx150.img . No other x704 variants twrps work on x704A and I have tried. Download that try to flash that to your recovery. I used this ROM https://forum.xda-developers.com/t/...neageos-16-0-for-lenovo-tab4-10-plus.3923394/
I haven't gotten to try the newer OS10 Lineage 17.
Click to expand...
Click to collapse
So this rom works with the x704a?
Folty57fg said:
Are you talking about Lenovo Tab4 10 x704A ? Is that the one with the ATT logo on the back, cuz I have that (one with 2gb of ram) and its rooted with magisk and has lineage OS and works great. You do need a special twrp file though.
View attachment 5187855
Click to expand...
Click to collapse
Could you help me with step by steps to install the twrp which you provided. I have the same XB704A tablet and I’m not successful in installing this twrp. I’m stuck. Kindly reply here or mail me at [email protected]
Bhaskarrv said:
Could you help me with step by steps to install the twrp which you provided. I have the same XB704A tablet and I’m not successful in installing this twrp. I’m stuck. Kindly reply here or mail me at [email protected]
Click to expand...
Click to collapse
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Don't setup, cause you will need to format your tablet later again. Shutdown tablet. Hold volume up and power button to start to bootloader
Then run
Code:
fastboot flash recovery twrp-3.2.3-0-<your-filename>.img
to flash TWRP
Select with volume buttons "Recovery Mode" and press power button
Select to write to system, otherwise you can't flash ROM
Backup at least system and boot partitions to your sdcard cause you will wipe data in next step. Choose "System Image" for the system partition backup.
Flash the recovery that I mentioned. Recovery-TWRP-3.3.0-0521-LENOVO_TBX704A-CN
The instructions I used were from this thread.
[ROM][UNOFFICIAL][9.0][TB-X704F/L] LineageOS 16.0 for Lenovo Tab4 10 Plus
/* * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * Please do some research if you have any concerns about features included in the...
forum.xda-developers.com
Use the twrp that I link, its only compatible with our tablet model. I rename it to like twrp.img then use "fastboot flash recovery twrp.img" instead of typing the whole name of the img file.
marcmann982 said:
So this rom works with the x704a?
Click to expand...
Click to collapse
sorry for late response, yes it works with x704a that what I screenshot it, you need a specific TWRP to install ROM
I tried to uninstall magisk via twrp flashing boot.img but only appeared the fastboot screen, so tried to restore stock rom but still on fastboot
Tried MiFlash, XiaoMI tool v2, MiFlash Pro with so many fastboot roms, flashed custom roms (included the aosp derivates and the latest miui eu) and still no luck, at least twrp and custom recoveries works fine
Please help, I already spent to many days trying to fix it
Edit: Tried to flash vbmeta again and now it works
uninstalling magisk is pretty hard nowadays, even when uninstalling via the app (which also flashes the uninstaller)
something is very wrong since you redirect to fastboot
did you format data?
try flashing the vbmeta at the bottom of the post
GUIDE From Zero to Hero - Basic Usage
Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. YOUR WARRANTY IS VOID IF YOU CONTINUE A noob friendly guide on how to get the most out of your phone. The Xiaomi Redmi 8 has been touted as one of the most sold...
forum.xda-developers.com
what were the results when you flashed stock using tools? have you tried fastboot instead of using the gui tools (often verry buggy)
fonzacus said:
uninstalling magisk is pretty hard nowadays, even when uninstalling via the app (which also flashes the uninstaller)
something is very wrong since you redirect to fastboot
did you format data?
try flashing the vbmeta at the bottom of the post
GUIDE From Zero to Hero - Basic Usage
Give a man a fish, feed him for a day. Teach a man to fish, feed him for life. YOUR WARRANTY IS VOID IF YOU CONTINUE A noob friendly guide on how to get the most out of your phone. The Xiaomi Redmi 8 has been touted as one of the most sold...
forum.xda-developers.com
what were the results when you flashed stock using tools? have you tried fastboot instead of using the gui tools (often verry buggy)
Click to expand...
Click to collapse
Basically i tried everything in the guide and other xiaomi guides (Except flashing via EDL), in the gui tools always show as "Success" and via fastboot all seems to be flashed correctly but still got the fastboot screen
Edit: Trying one more time with another vbmeta and instaled dotOS, Now it works
just a side note, miui >12.5.x were built to be more picky with everything in general. you mightve been blocked by miuis avb (custom vbmetas workaround this) when you were sent to fastb
hence why twrp 3.6.x includes an advanced installer option (workaround this and other brands)
as for trying to fully uninstall magisk, lots of others (including me) failed lots in the past on 23 and canary (and other forks), reinstalling again seems to fix it
thankfully you got it up and running, tho id recd something other than dot, i and others found it battery heavy for some strange reason ;P
good night in my case what happened to me is that I was cleaning the files see formatting the folders through orange fox recovery, after doing everything quietly I went to install the official rom of miui 12.5, because previously I had a custom rom of android 12 and I saw many problems with said rom anyway. I do a deep cleaning and proceed to install the official rom It gave me a very bad feeling that in the process it will restart in recovery at the end of everything, so I reinstalled the rom and instead of falling into recovery it falls into fastboot and restarts and It does not let you enter the recovery but goes directly to fastboot. The pc detects it as android and the tools only throw that code that it gives in the attached image. please a hand for this poor devil I don't want to lose such a good phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xXchizaXx said:
good night in my case what happened to me is that I was cleaning the files see formatting the folders through orange fox recovery, after doing everything quietly I went to install the official rom of miui 12.5, because previously I had a custom rom of android 12 and I saw many problems with said rom anyway. I do a deep cleaning and proceed to install the official rom It gave me a very bad feeling that in the process it will restart in recovery at the end of everything, so I reinstalled the rom and instead of falling into recovery it falls into fastboot and restarts and It does not let you enter the recovery but goes directly to fastboot. The pc detects it as android and the tools only throw that code that it gives in the attached image. please a hand for this poor devil I don't want to lose such a good phone.View attachment 5650943
Click to expand...
Click to collapse
you should make a new thread for this
so many questions
its a very delicate situation youre in. which orangefox? which miui rom? is your os really winxp? what does device manager see your phone as?
fonzacus said:
you should make a new thread for this
so many questions
its a very delicate situation youre in. which orangefox? which miui rom? is your os really winxp? what does device manager see your phone as?
Click to expand...
Click to collapse
Fortunately, you can install the Miui through the flash ROM, but unfortunately the Miui 11 version blocked me from starting up again, so I can't put any more ROMs in it.
Hi, I'm trying to root my Redmi 7A with Magisk. I have patched the recovery.img of my stock ROM (MIUI V12.5.2.0.QCMMIXM) and then flashed it with fastboot. Then I rebooted into the recovery, released the key combo and the system seems to boot properly but it block ath the MIUI splash screen.
Then I need to reboot normaly and the root is'nt installed.
I also tried with patching the vbmeta.img like said here but it's the same result.
Same result with the patched boot image
I know that all my data / settings are properly loaded (I can see my luminosity and reader mode during the MIUI splash screen)
That's all, I hope there is someone who know how to solve this.
Specs :
- Xiaomi redmi 7A
- Magisk v25.2
- MIUI verison : MIUI Global 12.5.2 stable (12.5.2.0QCMMIXM)
- stock ROM found here : xiaomifirmwareupdater.com
Thanks
Choucroute_melba said:
Hi, I'm trying to root my Redmi 7A with Magisk. I have patched the recovery.img of my stock ROM (MIUI V12.5.2.0.QCMMIXM) and then flashed it with fastboot. Then I rebooted into the recovery, released the key combo and the system seems to boot properly but it block ath the MIUI splash screen.
Then I need to reboot normaly and the root is'nt installed.
I also tried with patching the vbmeta.img like said here but it's the same result.
Same result with the patched boot image
I know that all my data / settings are properly loaded (I can see my luminosity and reader mode during the MIUI splash screen)
That's all, I hope there is someone who know how to solve this.
Specs :
- Xiaomi redmi 7A
- Magisk v25.2
- MIUI verison : MIUI Global 12.5.2 stable (12.5.2.0QCMMIXM)
- stock ROM found here : xiaomifirmwareupdater.com
Thanks
Click to expand...
Click to collapse
Firsly, here you have the general forum for your model here on XDA https://forum.xda-developers.com/c/redmi-7a.9077/
This thread has some insights for your issue https://forum.xda-developers.com/t/boot-img-patched-boot-img-files-patching-tool.4030777/page-3
As far as I remember, you need to patch only the boot image, patching other image like the recovery, won`t work, but read well that thread, you`d need to, firstly, patch the boot image with this tool https://github.com/YaAlex3/patcher-oss, and only after that, Magisk can patch the boot image, to be flashed.
Ok, I'll try this and give you an update.
Thank you
Hi again I have tried the patcher-oss but it give me the following output :
Exception: ERROR: Didn't find skip_initramfs, no need to patch.
I retried to flash this boot.img patched with magisk (with no error) and this time, idk why but MIUI don't boot and the bootloop stay on android splash screen.
The other patcher given I the thread don't work 'cause of a socket error and put the magisk.zip file don't fix it.
that's all, it's a little bit annoying so if you or someone have any idea on how to root this f****** device it would be very nice
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
su command exist.
So the root worked
android booted properly
all my data / settings are still here...
but what the hell is with MIUI ????
Choucroute_melba said:
View attachment 5703915
su command exist.
So the root worked
android booted properly
all my data / settings are still here...
but what the hell is with MIUI ????
Click to expand...
Click to collapse
Not clear, you meant, now it`s rooted but device is not booting. Don`t let your post as a guess, it`s not clear what you did. These commands are from?
When my device boot it's firt boot Android with the "powered by android" splash screen and then MIUI boot with the MIUI splash screen.
In the case of my post, android has booted successfuly (Ihave access to adb and my phone shell) and when I execute the su command, nothing happens but it does not tell me that the commands is "innacessible or not found". so I deduced the command exist and the phone is rooted (maybe there is still something missing, I don't know, but it's a different behavior from when the phone is normal).
BUT MIUI refuse to boot and block on the MIUI splash screen.
That's why i said that Android booted properly and the phone is rooted, but maybe I'm wrong
Tell me if you have any question or if you want me to test something.
Also about the patcher, do you know if there is a way to make it work ?
Thanks
Choucroute_melba said:
When my device boot it's firt boot Android with the "powered by android" splash screen and then MIUI boot with the MIUI splash screen.
In the case of my post, android has booted successfuly (Ihave access to adb and my phone shell) and when I execute the su command, nothing happens but it does not tell me that the commands is "innacessible or not found". so I deduced the command exist and the phone is rooted (maybe there is still something missing, I don't know, but it's a different behavior from when the phone is normal).
BUT MIUI refuse to boot and block on the MIUI splash screen.
That's why i said that Android booted properly and the phone is rooted, but maybe I'm wrong
Tell me if you have any question or if you want me to test something.
Also about the patcher, do you know if there is a way to make it work ?
Thanks
Click to expand...
Click to collapse
If you can really boot to Android completely then, test the root status with some root app checker, if you can't do that, then the device didn't boot properly, in a way ADB can interact with.
Unfortunately, from what I did test it in the past, the tool works with some boot versions only. By the way you have a boot collection in the first posts, you can pick up from.
Hi ! I finally managed to install a custom ROM (Arrow Os) and then the root went by himself.
Thank you for your help
Hi.
Bought this phone 4 months ago and it went into a boot loop, where it would only show the battery empty icon. Yesterday, I tried turning it on again and noticed, that it's stuck at the Redmi - Powered by Android" screen. From this screen, I can enter fastboot. See this video:
VID_20230417_194410.mp4
drive.google.com
I've read that there are a couple of options for reflashing this device:
- aks someone with the authorized Xiaomi account to reflash stock rom using the MiFlash tool (no bootloader unlock needed)
- put the device somehow into ETL mode and reflash stock rom using the MiFlash tool (no bootloader unlock needed)
I've tried contacting someone, who for #1, but they aren't willing to help, for some reason (I'm wiling to pay). For #2, I'd have to open up the device, which I'd like to avoid doing.
Would anybody know of any other options for fixing this?
Thank you in advance!
okay, which version of MIUI are you running?
first get the fastboot rom of the version your phone supports , i recommend the global version fastboot rom , because it works and its stable and u get your updates
download this fastboot rom first
Temporary file download page
miuirom.org
and I will give you the MI flash tool working version at like 6 hours after, Ill post the remaining steps after you download this , btw, you will get a .tgz file , when u download the Rom, thats the one you need
RunoTheDog said:
Hi.
Bought this phone 4 months ago and it went into a boot loop, where it would only show the battery empty icon. Yesterday, I tried turning it on again and noticed, that it's stuck at the Redmi - Powered by Android" screen. From this screen, I can enter fastboot. See this video:
VID_20230417_194410.mp4
drive.google.com
I've read that there are a couple of options for reflashing this device:
- aks someone with the authorized Xiaomi account to reflash stock rom using the MiFlash tool (no bootloader unlock needed)
- put the device somehow into ETL mode and reflash stock rom using the MiFlash tool (no bootloader unlock needed)
I've tried contacting someone, who for #1, but they aren't willing to help, for some reason (I'm wiling to pay). For #2, I'd have to open up the device, which I'd like to avoid doing.
Would anybody know of any other options for fixing this?
Thank you in advance!
Click to expand...
Click to collapse
If you can boot into fastboot, then it is already enough.
Now, I suppose your bootloader is still locked
You need to download a MIUI ROM from "EEA", from any trusted website, and remember to download the "Fastboot" ROM to flash it (my favorite is mifirm.net, it downloads faster)
Install MiFlashPro - attached at the end of the thread
Open it up, and you will be greeted with this.
Click on the "Mi Flash" tab, as it is the only one we need.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will be greeted with this window now:
After you have done downloading your ROM, extract it to any place.
If MiFlash does not recognise the directory you have extracted in, move it to C:\. Not any external drive, your main one
Now click on the "select" button box, go to your ROM directory, and simply select its folder
Boot your device into fastboot (PWR + VOL-), click on "refresh" button box and your device serial number should appear on the first line.
Now simply click "flash" and let it do its job for 10 to 15 minutes. It will reboot automatically.
If you dont succeed, please read this thread:
Thread '[GUIDE] UNBRICK YOUR HARD-BRICKED MTK' https://forum.xda-developers.com/t/guide-unbrick-your-hard-bricked-mtk.4564029/
You will require BROM and to bypass and to flash via SP Tool.
RunoTheDog said:
For #2, I'd have to open up the device, which I'd like to avoid doing.
Click to expand...
Click to collapse
You have either got confused, or being scammed
Newer MTK devices do not require the opening of the device. I suppose you have been probably confused with a Qualcomm Snapdragon based service, that does require the opening, so you can access EDL mode and flash your phone into life, or someone just put up the Redmi Note 10 5G and is a scam, also, on MTK, you do not need to pay for a authorized Mi account. On MTK, it is easily bypassable due to BROM
Thank you both.
I put ran MiFlashPro, pointed it towards the downloaded eea stock rom file and attempted to flash it, but got this error message:
So I presume this is due to locked bootloader? I'll try to follow the second link.
I actually managed to enter recovery mode and do a factory reset. Currently setting it up and plan on updating it.
RunoTheDog said:
I actually managed to enter recovery mode and do a factory reset. Currently setting it up and plan on updating it.
Click to expand...
Click to collapse
Good to hear you got sorted. I basically bricked my phone last week (only 3 weeks old ) after trying to switch from MIUI 13 Global to EEA. I managed to get it into BROM mode and used MTK Auth Bypass which allowed me to use Chimera Tools to flash the phone again as nothing else seems to work with a locked bootloader. Currently running MIUI 14 with root and magisk optimisations (blur/high end tweaks, MIUI monet etc) and loving it! Just need a way to bypass Play Integrity API for Google Wallet