Database Develop

Soft BRICKED A2 (bootloop)

I have bricked my A2 today. I first unlocked the bootloader then insatlled GCAM.
everything was fine, but i tried to install XPOSED (sdk 27) from Magisk module, then rebooted from magisk. My set is stuck at android one animation.
I downloaded official firmware of A2 and tried to flash via mi flash tool, always gets an error of "FLASH_DEVCFG_A ERROR" . Then i tried by clicking on "flash_all_except_data.bat" file, cmd just opened and closed very soon, Same thing happended with "flash_all_lock.bat" ,again cmd just opened and closed.
Still my phone is stuck at Android one animation, and i cant flash or boot my set.
EDIT :: USED. /FASTBOOT -W TO UNBRICK PHONE

Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4

minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
should i flash only those images? because i have some more image files than the llist, kindly check the screen shot

minnuss said:
Just follow this instructions on the link bellow.
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Click to expand...
Click to collapse
Now stuck at devcfg
PS C:\Users\KSN\Desktop\platform-tools> fastboot flash devcfg_b C:\Users\KSN\Desktop\images_V9.6.10.0.ODIMIFE_8.1\images\devcfg.img
target reported max download size of 536870912 bytes
sending 'devcfg_b' (47 KB)...
OKAY [ 0.005s]
writing 'devcfg_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.007s
bluetooth_a , bluetooth_b was flashed successfully

try fastboot flashing unlock_critical

munchy_cool said:
try fastboot flashing unlock_critical
Click to expand...
Click to collapse
This appears everytime . :/
{
"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"
}

Syed Shahriar said:
This appears everytime . :/View attachment 4581400
Click to expand...
Click to collapse
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot

munchy_cool said:
xposed would have not messed with those partitions. did you flash system partition yet?
if not just flash system, vendor and boot
once you have flashed those, do fastboot -w (will loose all data).
and then reboot
fastboot reboot
Click to expand...
Click to collapse
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please

Syed Shahriar said:
i just flashed bluetooth_a, bluetooth_b, and then went to devcf_a, failed , and did nothing else.
and what will be the command to flash system, vendor and boot ? kindly give me an example please
Click to expand...
Click to collapse
GOT THESE ERROR::
PS C:\adb> fastboot flash system_a C:\adb\images\system.img
error: cannot load 'C:\adb\images\system.img'
my system iso is there in that location
but successfuly done fastboot flash vendor_b C:\adb\images\vendor.img
and fastboot flash vendor_a C:\adb\images\vendor.img

What are you even doing with all those commands
You need to download latest ADB, that is the first that you need to do, and second, copy all of the images from stock rom to your adb folder, it will be easier for commands to work.
And then start your cmd.exe with administrative privileges (right click on cmd in search bar of windows start, and "run as administrator").
Then move yourself from directory to your adb directory with commands from DOS, like "cd.." for going back from directory, and "cd nameofdir" to go into directory.
So move yourself in adb directory, then type the commands from the upper link to flash those .img one by one.
Oh yes, one other thing, you need to check if you see your mobile device in fastboot, did you install correct drivers.
When you are in adb folder, in cmd type fastboot devices, and you should see your mobile connected, if not, then you can type all you want, the phone is not recognized with pc connection.

Right, so... follow this guide to make sure you've unlocked your bootloader successfully. After you've finished, also add in the command "fastboot flashing unlock_critical". I'm not sure why it didn't work for you in the first place - but I know for a fact it works, because I did it to my own A2.
Make sure you've installed adb/drivers as attached by that link above. Why? 'Cause that's what I did, so I know it should work.
Then go here, extract the files to the same folder as platform-tools (the adb and fastboot tools folder), and run flash-all.bat.

Hey bro i do it too, tô solve, just do a fastboot unlock_critical
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585

I had the same issue, no OS installed.
Adb Sideload and OTG didn't worl no matter what I tried.
I followed this thread, and it worked properly without errors, not even one.
It took me 5 minutes to recover my dead MiA2 device to a smooth original/official ROM built.
Locled OEM, rebooted the device and everything is working perfectlt.
Thank you all for the info.

HELP: Bricked P20 Pro - "Getting package info failed"

Hey guys,
Since yesterday I was trying to fix this issue but i could not make it.
Before bricking my P20 Pro, i have installed the Android Pie 9 "CLT-L29C432E5R1P7B108" and it was working very well.
Then i tried to install the root via Magisk and I flashed the TWRP but all failed. I was able to boot into the TWRP but later on just stopped. Now I am have screen of Error ," Attention..." similar to this
{
"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"
}
.
I am able only to access to the bootloader , the fastboot commands are working and I flashed many TWRP images successfully (eg. fastboot flash recovery_ramdisk twrp_clt_0.1.img) but without the ability to boot on TWRP.
Phone Unlocked
FRP Unlock
Note: erecovery is working but i am getting this error "Getting package info failed".
My Model : CLT-L29C432
Please help..
I have placed down here some more info from fastboot which may could help,,
*****************
PS C:\adb> fastboot oem get-product-model
(bootloader) CLT-L29
OKAY [ 0.004s]
Finished. Total time: 0.005s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
Finished. Total time: 0.004s
PS C:\adb> fastboot oem get-build-number
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
OKAY [ 0.004s]
Finished. Total time: 0.004s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: 'FAIL:need all image flashed!')
Finished. Total time: 0.020s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :CLT-L29 9.0.0.108(C432E5R1P7log)
OKAY [ 0.005s]
Finished. Total time: 0.006s
PS C:\adb>
*******************

I have the same issue! Mine gets the package, but fails after 1% when it starts the recovery process.
TWRP doesn't have MTP or ADB Sideload support. So I can't push anything to TWRP.
Funkyhuawei eRecovery doesn't work either.
At this point. I'm just waiting for a TWRP update with MTP support.
p.s I seen that the unofficial twrp version supports MTP. I can push files. But that version will NOT mount system. (So its useless)

Anutter226 said:
I have the same issue! Mine gets the package, but fails after 1% when it starts the recovery process.
TWRP doesn't have MTP or ADB Sideload support. So I can't push anything to TWRP.
Funkyhuawei eRecovery doesn't work either.
At this point. I'm just waiting for a TWRP update with MTP support.
p.s I seen that the unofficial twrp version supports MTP. I can push files. But that version will NOT mount system. (So its useless)
Click to expand...
Click to collapse
ATt least your TWRP is working, .. even it is useless.. looking forward for solution..

alfrqan said:
Hey guys,
Since yesterday I was trying to fix this issue but i could not make it.
Before bricking my P20 Pro, i have installed the Android Pie 9 "CLT-L29C432E5R1P7B108" and it was working very well.
Then i tried to install the root via Magisk and I flashed the TWRP but all failed. I was able to boot into the TWRP but later on just stopped. Now I am have screen of Error ," Attention..." similar to this .
I am able only to access to the bootloader , the fastboot commands are working and I flashed many TWRP images successfully (eg. fastboot flash recovery_ramdisk twrp_clt_0.1.img) but without the ability to boot on TWRP.
Phone Unlocked
FRP Unlock
Note: erecovery is working but i am getting this error "Getting package info failed".
Please help..
Click to expand...
Click to collapse
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.

You should never tried rooting pie. It's written everywhere that emui9 is not rootable yet.
For the fix, I would try to flash stock rom via HuRu.
Wipe everything first... /system, /data, /caches

After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)

I think it was because if your modded ram disk. Android pie isn't rootable on huawei phones rn

KennyDumah said:
I think it was because if your modded ram disk. Android pie isn't rootable on huawei phones rn
Click to expand...
Click to collapse
So you should just flash stock boot.img to be able to boot to os again....

Anutter226 said:
After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)
Click to expand...
Click to collapse
I am going to try this. I hope it will work.
Can I know which rom that you have downloaded?
and which commands you have used to flash that .imgs.

side_flip15 said:
You should never tried rooting pie. It's written everywhere that emui9 is not rootable yet.
For the fix, I would try to flash stock rom via HuRu.
Wipe everything first... /system, /data, /caches
Click to expand...
Click to collapse
TWRP is not working and I can not push any file in SD Card. Only fastboot is working..

dladz said:
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.
Click to expand...
Click to collapse
Sounds interesting. will give it a try.

side_flip15 said:
So you should just flash stock boot.img to be able to boot to os again....
Click to expand...
Click to collapse
I download several update.zips and up pack them and so far i could not find this file in :boot.img:

dladz said:
When you've flagged twrp have you disconnected the cable? Remove it before you try to boot to twrp.
Had the same issue myself.
Never seen that before though.
Click to expand...
Click to collapse
can i know which TWRP you have used here?

YellowSnowman23 said:
After 3 days, I finally fixed mine.
(Requires unlocked bootloader)
I downloaded the update.zip for my region/version here *MAKE SURE TO CHOSE THE CORRECT REGION*
Used the Huawei update unpack-er to unpack the UPDATE.APP (You can download that here)
Flashed as many of the .img's as possible
At the end I did fastboot erase -w
The phone fails to boot the first time, eRecovery will prompt to format data/factory reset. I did that, it auto rebooted like normal.
SUCCESS!
(A lot of the .img's will say command not allowed. Ignore it an move on flashing the rest)
Click to expand...
Click to collapse
I have tried this without success. I used to flash imgs by "fastboot flash system xxx.img"

alfrqan said:
TWRP is not working and I can not push any file in SD Card. Only fastboot is working..
Click to expand...
Click to collapse
Unofficial twrp should work. If you have problem with encryption you should format data in twrp.

side_flip15 said:
Unofficial twrp should work. If you have problem with encryption you should format data in twrp.
Click to expand...
Click to collapse
I tried a lot of them.. but still not able to boot into TWRP

alfrqan said:
I am going to try this. I hope it will work.
Can I know which rom that you have downloaded?
and which commands you have used to flash that .imgs.
Click to expand...
Click to collapse
As for rom. I used official Huawei firmware.
Download the correct update.zip for your device.
Unzip it
Put the UPDATE.APP in the Huawei update extractor Make sure in the extractor tool, you go to settings and UNCHECK "Verify header checksum"
Code:
(Ex. system)
fastboot flash system [I]LOCATION_OF_SYSTEM.IMG[/I]
(Ex. recovery_ramdisk)
fastboot flash recovery_ramdisk [I]LOCATION OF RECOVERY_RAMDISK.IMG[/I]

alfrqan said:
can i know which TWRP you have used here?
Click to expand...
Click to collapse
Always unofficial, it's the most functional

Update>>
I have visited Huawei service center in Madrid and they said "there is no way to repair it, you have to change the motherboard". This is ridicules and I dont believe that.

YellowSnowman23 said:
As for rom. I used official Huawei firmware.
Download the correct update.zip for your device.
Unzip it
Put the UPDATE.APP in the Huawei update extractor Make sure in the extractor tool, you go to settings and UNCHECK "Verify header checksum"
Code:
(Ex. system)
fastboot flash system [I]LOCATION_OF_SYSTEM.IMG[/I]
(Ex. recovery_ramdisk)
fastboot flash recovery_ramdisk [I]LOCATION OF RECOVERY_RAMDISK.IMG[/I]
Click to expand...
Click to collapse
hey,
I have downloaded and extracted many official and found the following files unzip file (update.zip):
for system: SYSTEM.img
command: fastboot flash system SYSTEM.img
Result: error: cannot load 'SYSTEM.img'
For RECOVERY_RAMDISK: RAMDISK.img
command:
Result:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16384 KB)...
OKAY [ 0.369s]
writing 'recovery_ramdisk'...
OKAY [ 0.140s]
finished. total time: 0.509s
conc. still not booting only fastboot commands,,,,,,

custom recovery flash successful, but not working

Hi
I'm on a MI 8 global version with the latest miui (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global_515bcbba58). I unlocked the phone, did a clean install (flash_all) and now i try to get twrp to work. So i went back to fastboot mode, run the commands:
Code:
fastboot flash recovery twrp-3.3.1-1-dipper.img
Sending 'recovery' (42044 KB) OKAY [ 1.166s]
Writing 'recovery' OKAY [ 0.121s]
Finished. Total time: 1.292s
fastboot boot twrp-3.3.1-1-dipper.img
Sending 'boot.img' (42044 KB) OKAY [ 1.134s]
Booting OKAY [ 0.064s]
Finished. Total time: 1.234s
and then... nothing. It reboots to android... next try flashing and manual reboot by holding power + volume up in fastboot mode until it vibrates and the mi logo is shown. Two seconds later the screen goes black, the device (seems to) reboot and android again.
Next try was a different image (using the lineage custom recovery)... same result. And if i try to boot to recovery when the device was off with power + volume up the original recovery is shown....
I'm out of ideas.

to-bu said:
Hi
I'm on a MI 8 global version with the latest miui (dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global_515bcbba58). I unlocked the phone, did a clean install (flash_all) and now i try to get twrp to work. So i went back to fastboot mode, run the commands:
Code:
fastboot flash recovery twrp-3.3.1-1-dipper.img
Sending 'recovery' (42044 KB) OKAY [ 1.166s]
Writing 'recovery' OKAY [ 0.121s]
Finished. Total time: 1.292s
fastboot boot twrp-3.3.1-1-dipper.img
Sending 'boot.img' (42044 KB) OKAY [ 1.134s]
Booting OKAY [ 0.064s]
Finished. Total time: 1.234s
and then... nothing. It reboots to android... next try flashing and manual reboot by holding power + volume up in fastboot mode until it vibrates and the mi logo is shown. Two seconds later the screen goes black, the device (seems to) reboot and android again.
Next try was a different image (using the lineage custom recovery)... same result. And if i try to boot to recovery when the device was off with power + volume up the original recovery is shown....
I'm out of ideas.
Click to expand...
Click to collapse
Obviously, you did something wrong.
Try renaming the recovery that you downloaded to "recovery" with no quotation marks
Place the file in the platform tools directory
For example: C:\Android\platform-tools\
Then use these commands.
fastboot flash recovery recovery.img
fastboot boot recovery.img
The commands above will flash the recovery.image to the recovery partition, then reboot then phone to recovery, you will then need to flash root.
If that doesn't work just use the Tool all in One

It seems that i "holding it wrong" but in fact it doesn't work eather.
I'm original on linux but to ensure that it's working i switched to the windows system:
* downloaded and installed "Tool all in One"
* choose correct device
* ensure device allows ADB Access to PC
* ensure unlock status in tool
* use "Recovery Flasher and Rooter"
* selected "TWRP 3.3.1 mauronofrio XMI8" with "Automatic TWRP MD5 Check" and "And boot it" options
* flashed... and nothing again....
So i downloaded the and unpacked "dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global" to C:\ and used the "Flash Factory Images" to reset the device to a clean state (again.) After the flash and the automatic reboot of the device i went manual Fastboot mode and repeat "Recovery Flasher and Device Router"... with the same result....
So definitly something is wrong

to-bu said:
It seems that i "holding it wrong" but in fact it doesn't work eather.
I'm original on linux but to ensure that it's working i switched to the windows system:
* downloaded and installed "Tool all in One"
* choose correct device
* ensure device allows ADB Access to PC
* ensure unlock status in tool
* use "Recovery Flasher and Rooter"
* selected "TWRP 3.3.1 mauronofrio XMI8" with "Automatic TWRP MD5 Check" and "And boot it" options
* flashed... and nothing again....
So i downloaded the and unpacked "dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global" to C:\ and used the "Flash Factory Images" to reset the device to a clean state (again.) After the flash and the automatic reboot of the device i went manual Fastboot mode and repeat "Recovery Flasher and Device Router"... with the same result....
So definitely something is wrong
Click to expand...
Click to collapse
Are you sure that you have developer options setup? ADB debugging is enabled?
If you plan on staying on the stock rom that you are currently using you may need to flash DM verity. personally I prefer to use Orange Fox because it has DM verity built in.
once you are finally successful flash TWRP you might consider switching it. But be warned the layout takes some getting used to.
The latest Orange Fox is here: https://files.orangefox.tech/OrangeFox-Beta/dipper/OrangeFox-R10.1_002-Beta-dipper.zip
Worst case scenario; If you are located in the US, I can do it for you. ( just send me a PM if you want me to do it)
I have provided this service for a lot of people, you pay shipping and buy me a beer. This will take no more than 10 minutes.
If that is not an option:
A lot of people have trouble flashing TWRP, so dont get discouraged. After flashing recovery you must immediately boot to recovery and flash root then choose reboot to recovery. You may see check boxes asking to install TWRP manager, choose yes and reboot to TWRP.
A Lot of times when things fail it is due to some silly such as forgetting to rename the file to twrp or recovery when your adb command looks like this: 1. fastboot flash recovery recovery.img or 2. fastboot flash recovery twrp.img my guess that this is your issue or its developer options not setup correctly. Again : ADB debugging must be enabled?
If your phone doesn't reboot in TWRP it may be overwritten by the ROM's recovery.
Unplug Your phone then Manually boot it into recovery
PS: Welcome to XDA, good manners when someone takes their time helping is to give thanks by clicking the thanks button. Don't say thanks click the button. See the signature. good luck.

Hi,
tsongming said:
Are you sure that you have developer options setup? ADB debugging is enabled?
Click to expand...
Click to collapse
Yes, I am. This is not the first time i switched to lineage /cyanogen mod. I already customized a Nexus 4 (mako), Motorola Moto G (falcon), Samsung Galaxy S4 (jfltexx), Samsung Galaxy Tab S2 (gts210vewifi)
and LG V20 (h990ds). So I'm not new to this.
tsongming said:
If you plan on staying on the stock rom that you are currently using you may need to flash DM verity. personally I prefer to use Orange Fox because it has DM verity built in.
once you are finally successful flash TWRP you might consider switching it. But be warned the layout takes some getting used to.
Click to expand...
Click to collapse
I see this in this subsection and i marked it already, since you suggest it i will try it as soon the flashing is working.
tsongming said:
Worst case scenario; If you are located in the US, I can do it for you. ( just send me a PM if you want me to do it)
I have provided this service for a lot of people, you pay shipping and buy me a beer. This will take no more than 10 minutes.
Click to expand...
Click to collapse
Sorry, Germany
tsongming said:
A Lot of times when things fail it is due to some silly such as forgetting to rename the file to twrp or recovery when your adb command looks like this: 1. fastboot flash recovery recovery.img or 2. fastboot flash recovery twrp.img my guess that this is your issue or its developer options not setup correctly. Again : ADB debugging must be enabled?
Click to expand...
Click to collapse
I don't see the point why the image must have a name with only characters, but i renamed the image to twrp.img and tried:
In Android with developer options enabled (and pc allowed):
Code:
adb reboot fastboot
Now i'm in fastboot and using my zsh on linux, im on my home directory located the twrp.img:
Code:
~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.279s]
Writing 'recovery' OKAY [ 0.118s]
Finished. Total time: 1.402s
Now the command to upload and boot to the same image:
Code:
~ fastboot boot twrp.img
Sending 'boot.img' (42044 KB) OKAY [ 1.236s]
Booting OKAY [ 0.067s]
Finished. Total time: 1.341s
On device: bank screen (about 5 sec) > mi logo with unlocked symbol/text (about 3 sec) > mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.
Second try manual:
Code:
adb reboot fastboot
Flashing...
Code:
~ fastboot flash recovery twrp.img
Sending 'recovery' (42044 KB) OKAY [ 1.248s]
Writing 'recovery' OKAY [ 0.107s]
Finished. Total time: 1.360s
Unplug the phone, pressing now together VOLUME-UP and POWER until device going black and mi logo showing and devices vibrates. => mi logo with android symbol/text/animation (again about 3 sec) => I'm back on android.

Similar issue
I have the exact same issue. Did you manage to find a solution?

dojabato said:
I have the exact same issue. Did you manage to find a solution?
Click to expand...
Click to collapse
Sorry for the REALLY LATE REPLY. But no..... nothing worked... currently i also don't try either.

I found the solution
to-bu said:
Sorry for the REALLY LATE REPLY. But no..... nothing worked... currently i also don't try either.
Click to expand...
Click to collapse
Hello,
I was in the same case like you, to resolve this issue you must install this TWRP : TWRP-3.3.1-1031-XIAOMI8-Q+Version-CN
Sorry I'm new and can't post links...
I installed with the TOOL ALL IN ON => Erase all data => recovery flasher (check only automatic TWRP...) => POWER+Volume down => POWER+Volume up very quickly => Enjoy it !

ASUS MemoPad 7 ME176CX unable to flash stock ROM via TWRP

Hi, my tablet was crashed when i updated firmware to one of the latest version in Lolipop.(i don't remember what was the version number of it). Started freezing bootlops, weird crashes and after some time it's stucked at UEFI bios menu. i've searched a lot of possible solutions and made some progress, but it's annoyingly persistent failing to flash ROM. Some ROMs caused freezing on installation progress bar as it's mentioned below( thread ***5.0 Brick Solution*** Asus Memo Pad 7 ME176CX) waiting 20 minutes, but couldn't get response from the device.
Can you please help me what's wrong i'm doing and do you have any solution for this ?
Followed guides:
UNBRICK ASUS MemoPad 7 ME176C/CX
Enter recovery and sideload CN ROM http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So...
forum.xda-developers.com
UNBRICK ASUS MemoPad 7 ME176C/CX
Enter recovery and sideload CN ROM http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So...
forum.xda-developers.com
***5.0 Brick Solution*** Asus Memo Pad 7 ME176CX
For the people out there who for some reason had there devices bricked when updating to lollipop. Whenever I was going to flash the WW_5.0_ME176C/X update I would get this error. "This package is for "K013" devices; this is a "K013_1"." I was...
forum.xda-developers.com
Intel Android Devices Root / Temp Recovery Session
Intel Android Devices Root / Temp Recovery Session Disclaimer: Before you proceed to the rooting instructions below, please read this disclaimer: XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You...
forum.xda-developers.com
UEFI bios
{
"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"
}
Droidboot
TWRP session, flashing update.zip
Failed but why ?

Tried to unlock bootloader on Android 5.0, seems successfully finished.
Tried to install permanent TWRP with this guide. Command is flashed ok, but when select recovery mode on Droidboot screen, it drops back to UEFI bios menu again:
[RECOVERY][2019-06-09] UNOFFICIAL TWRP 3.3.1 for ASUS MeMO Pad 7 (ME176C(X))
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
Tried to restore with TWRP backup WW 12.10.1.36 8 GB version. It's failed due to unable to mount partitions. Only Factory partition is mounted.

Tried rollback from Android 5 to 4.4 Kitkat.
Code:
OSLOADER: efilinux-userdebug.efi
sending 'osloader' (2023 KB)...
OKAY [ 0.103s]
writing 'osloader'...
OKAY [ 0.007s]
finished. total time: 0.113s
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
OKAY [ 0.001s]
finished. total time: 0.541s
Waiting for 0 seconds, press a key to continue ...
< waiting for device >
...
(bootloader) Start partitioning
OKAY [ 0.047s]
finished. total time: 0.048s
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (1 KB)...
OKAY [ 0.035s]
writing '/tmp/partition.tbl'...
OKAY [ 0.044s]
finished. total time: 0.081s
...
FAILED (remote: GPT command failed
)
finished. total time: 0.287s
"partition /tmp/partition.tbl FAILED, EXIT!"
Press any key to continue . . .

Fastboot commands:
Code:
fastboot oem start_partitioning
fastboot oem partition /system/etc/partition.tbl
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash osloader efilinux
.efi
target didn't report max-download-size
sending 'osloader' (2009 KB)...
OKAY [ 0.104s]
writing 'osloader'...
OKAY [ 0.045s]
finished. total time: 0.153s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.537s]
booting...
OKAY [ 0.002s]
finished. total time: 0.540s
C:\Program Files (x86)\Minimal ADB and Fastboot>
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.046s]
finished. total time: 0.048s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem partition /system/e
tc/partition.tbl
...
FAILED (remote: GPT command failed
)
finished. total time: 0.103s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Patch Micro SD, trying to run OS on it.

Power Y USB Hub connected. Have access to UEFI settings.

RaiKov said:
Hi, my tablet was crashed when i updated firmware to one of the latest version in Lolipop.(i don't remember what was the version number of it). Started freezing bootlops, weird crashes and after some time it's stucked at UEFI bios menu. i've searched a lot of possible solutions and made some progress, but it's annoyingly persistent failing to flash ROM. Some ROMs caused freezing on installation progress bar as it's mentioned below( thread ***5.0 Brick Solution*** Asus Memo Pad 7 ME176CX) waiting 20 minutes, but couldn't get response from the device.
Can you please help me what's wrong i'm doing and do you have any solution for this ?
Followed guides:
UNBRICK ASUS MemoPad 7 ME176C/CX
Enter recovery and sideload CN ROM http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So...
forum.xda-developers.com
UNBRICK ASUS MemoPad 7 ME176C/CX
Enter recovery and sideload CN ROM http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So...
forum.xda-developers.com
***5.0 Brick Solution*** Asus Memo Pad 7 ME176CX
For the people out there who for some reason had there devices bricked when updating to lollipop. Whenever I was going to flash the WW_5.0_ME176C/X update I would get this error. "This package is for "K013" devices; this is a "K013_1"." I was...
forum.xda-developers.com
Intel Android Devices Root / Temp Recovery Session
Intel Android Devices Root / Temp Recovery Session Disclaimer: Before you proceed to the rooting instructions below, please read this disclaimer: XDA-DEVELOPERS.COM and I are not responsible for what you are doing to your device. You...
forum.xda-developers.com
UEFI bios
View attachment 5150261
Droidboot
View attachment 5150263
TWRP session, flashing update.zip
View attachment 5150265
Failed but why ?
Click to expand...
Click to collapse
If im not wrong its due to bad partition table, you should try to format everything first, before flashing, on after new year I can give more detailed help, I dont have access to the device at the moment.

Ruben Craveiro said:
If im not wrong its due to bad partition table, you should try to format everything first, before flashing, on after new year I can give more detailed help, I dont have access to the device at the moment.
Click to expand...
Click to collapse
Hi, i appreciate if you can help me further. Yes, the main problem is Internal memory is somehow disappeared after i tried to format all memory on WIPE menu in TWRP. Now Tablet went into read-only mode, no access to flash something. Only MicroSD storage is visible on MTP device on Windows PC. It was both visible(Internal storage and MicroSD) before formatting data in TWRP. Looks like all partitions are erased, unable to mount data due to Internal Storage(0 MB) problem. I guess i may need a full memory dump of any of working 176CX 8GB tablet to restore my tablet. Looking forward to your reply. Merry Christmas and happy holidays.
Raiko.

RaiKov said:
Hi, i appreciate if you can help me further. Yes, the main problem is Internal memory is somehow disappeared after i tried to format all memory on WIPE menu in TWRP. Now Tablet went into read-only mode, no access to flash something. Only MicroSD storage is visible on MTP device on Windows PC. It was both visible(Internal storage and MicroSD) before formatting data in TWRP. Looks like all partitions are erased, unable to mount data due to Internal Storage(0 MB) problem. I guess i may need a full memory dump of any of working 176CX 8GB tablet to restore my tablet. Looking forward to your reply. Merry Christmas and happy holidays.
Raiko.
Click to expand...
Click to collapse
The partition table looks pretty good in this screenshot:
Spoiler
The sizes seem to mostly match mine (I have the 16 GB variant though).
In general, as long as you can still access the UEFI setup or even boot (temporary?) TWRP your tablet seems in pretty good shape.
I would try flashing e.g. me176c-boot from the "FASTBOOT MODE" (Droidboot) screen (see https://forum.xda-developers.com/t/...6c-boot-for-asus-memo-pad-7-me176c-x.3780225/) and then check if it shows the boot menu if you keep "Volume Down" pressed while turning the tablet on.

lambdadroid said:
The partition table looks pretty good in this screenshot:
Spoiler
The sizes seem to mostly match mine (I have the 16 GB variant though).
In general, as long as you can still access the UEFI setup or even boot (temporary?) TWRP your tablet seems in pretty good shape.
I would try flashing e.g. me176c-boot from the "FASTBOOT MODE" (Droidboot) screen (see https://forum.xda-developers.com/t/...6c-boot-for-asus-memo-pad-7-me176c-x.3780225/) and then check if it shows the boot menu if you keep "Volume Down" pressed while turning the tablet on.
Click to expand...
Click to collapse
Hi, yes i have access to Fastboot mode and then TWRP, but not directly(first i need to flash efilinux from DNX mode Fastboot starting...#1#2#3 https://forum.xda-developers.com/t/unbrick-asus-memopad-7-me176c-cx.2970049/post-72963836) I flashed ESP.img successfully. When i press Volume down button. These options are available:
*Recovery mode
*Restart bootloader
*Normal boot
*Power off
(This is an old image for e.g., there was no error in this session.)
Code:
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash osloader efilinux-userdebug.efi
sending 'osloader' (2023 KB)...
OKAY [ 0.105s]
writing 'osloader'...
OKAY [ 0.007s]
finished. total time: 0.115s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
OKAY [ 0.002s]
finished. total time: 0.541s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.169s]
writing 'ESP'...
OKAY [ 0.616s]
finished. total time: 1.788s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>
When i select boot or recovery it directly goes into UEFI bios screen. Is there any solution to format or recover Internal Storage(0 Mb) of the tablet?

RaiKov said:
Hi, yes i have access to Fastboot mode and then TWRP, but not directly(first i need to flash efilinux from DNX mode Fastboot starting...#1#2#3 https://forum.xda-developers.com/t/unbrick-asus-memopad-7-me176c-cx.2970049/post-72963836) I flashed ESP.img successfully. When i press Volume down button. These options are available:
*Recovery mode
*Restart bootloader
*Normal boot
*Power off
Code:
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash osloader efilinux-userdebug.efi
sending 'osloader' (2023 KB)...
OKAY [ 0.105s]
writing 'osloader'...
OKAY [ 0.007s]
finished. total time: 0.115s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.536s]
booting...
OKAY [ 0.002s]
finished. total time: 0.541s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>fastboot flash ESP esp.img
target reported max download size of 536870912 bytes
sending 'ESP' (33792 KB)...
OKAY [ 1.169s]
writing 'ESP'...
OKAY [ 0.616s]
finished. total time: 1.788s
C:\Users\RaiKo\Desktop\asus recovery project\rollback\WW_ME176C_V12.10.1.17-user
debug-201505051557-rawdata>
When i select boot or recovery it directly goes into UEFI bios screen. Is there any solution to format or recover Internal Storage(0 Mb) of the tablet?
Click to expand...
Click to collapse
That does not sound like it really flashed it successfully. If you install me176c-boot, the boot menu should look like
It does kind of sound like your eMMC has magically become read-only, although I don't know how this is possible.

lambdadroid said:
That does not sound like it really flashed it successfully. If you install me176c-boot, the boot menu should look like
View attachment 5185301
It does kind of sound like your eMMC has magically become read-only, although I don't know how this is possible.
Click to expand...
Click to collapse
Exactly yes! This read-only memory mode what i'm facing now. As i said above, i didn't change too many things. When i was trying to solve "unable to mount" error, once i tried to format internal memory on TWRP wipe menu. I saw this advice in main topic, it was explaining in guide how to solve Internal Memory(0 Mb) problem with TWRP formatting, wipe, repairing partitions, change type of format from ext4 to ext2 and rechange it to ext4 etc. I'm very sure Internal memory was visible both TWRP and MTP device on Windows PC before formatting.
Maybe i need to give permissions or enter password(seen it in many Youtube tutorials for Asus Phone) to unlock Internal Memory, but i don't know how to solve this problem without running Android.
Do you have any suggestion to me, what i supposed to do?

RaiKov said:
Do you have any suggestion to me, what i supposed to do?
Click to expand...
Click to collapse
It's a very strange problem and to be honest I don't really know what to do either.
I guess in your situation I would put some Linux distribution on a USB flash drive (e.g. Arch Linux), boot it through the UEFI menu (use the "Boot Override" option). And then try to investigate from there using some proper Linux command line tools or by looking at the kernel log. But I can't give you exact steps because I don't know how the eMMC could magically become read-only or how to get it out of this mode.

lambdadroid said:
It's a very strange problem and to be honest I don't really know what to do either.
I guess in your situation I would put some Linux distribution on a USB flash drive (e.g. Arch Linux), boot it through the UEFI menu (use the "Boot Override" option). And then try to investigate from there using some proper Linux command line tools or by looking at the kernel log. But I can't give you exact steps because I don't know how the eMMC could magically become read-only or how to get it out of this mode.
Click to expand...
Click to collapse
Thanks for the answer. Not sure we are talking about similar things. I downloaded gparted live on Linux OS.(My dev specialist friend had advised me). Created a bootable disk by rufus, but if i knew it i could tell you the result.
And then do you know any person in the forum who can help me in this case? i believe this eMMC issue is weird, but not magical imho, it must have happened and affected to more users.

RaiKov said:
Thanks for the answer. Not sure we are talking about similar things. I downloaded gparted live on Linux OS.(My dev specialist friend had advised me). Created a bootable disk by rufus, but if i knew it i could tell you the result.
Click to expand...
Click to collapse
So, did you find anything interesting?
RaiKov said:
And then do you know any person in the forum who can help me in this case? i believe this eMMC issue is weird, but not magical imho, it must have happened and affected to more users.
Click to expand...
Click to collapse
I don't really know any other person who has worked on this device in the last few years so I'm afraid I don't know anyone either.

lambdadroid said:
So, did you find anything interesting?
Click to expand...
Click to collapse
No, actually i haven't tried it yet. Because i dunno how to recognise it.(not familiar with Linux) Another reason i know this is one of the last thing i can try to bring the tablet back life. I was searching other possible solutions before this step.
What do you think about if i got a full memory dump.img.gz(including all 15 partitions) of a working 176CX 8GB tablet? Would that help me in some way?

RaiKov said:
What do you think about if i got a full memory dump.img.gz(including all 15 partitions) of a working 176CX 8GB tablet? Would that help me in some way?
Click to expand...
Click to collapse
This will probably be helpful at some point, but I would recommend against randomly overwriting all partitions from some memory dump. This might do more harm than good. From what I could tell, your partition table for example seems fine.
You can try booting the following image. This is me176c-boot packaged for USB. It also contains a bootable version of my TWRP build (https://forum.xda-developers.com/t/...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/).
Flash it to an USB flash drive using Rufus.
Boot it on your tablet. A menu like I showed above should show up.
You can try the other boot options but I added a special "Recovery (USB)" one. This should boot TWRP from the USB flash drive. (Note: use ↓ to switch options, ↑ or Enter to select an option)
When the TWRP splash screen shows up you can disconnect USB.
Post the output of "dmesg" in the terminal emulator here. You can get it via adb shell (tablet connected via USB to your PC) or write to to an external SD card e.g. with "dmesg > /external_sd/dmesg.txt".
Perhaps that (dmesg = kernel log) contains something useful.

lambdadroid said:
This will probably be helpful at some point, but I would recommend against randomly overwriting all partitions from some memory dump. This might do more harm than good. From what I could tell, your partition table for example seems fine.
You can try booting the following image. This is me176c-boot packaged for USB. It also contains a bootable version of my TWRP build (https://forum.xda-developers.com/t/...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/).
Flash it to an USB flash drive using Rufus.
Boot it on your tablet. A menu like I showed above should show up.
You can try the other boot options but I added a special "Recovery (USB)" one. This should boot TWRP from the USB flash drive. (Note: use ↓ to switch options, ↑ or Enter to select an option)
When the TWRP splash screen shows up you can disconnect USB.
Post the output of "dmesg" in the terminal emulator here. You can get it via adb shell (tablet connected via USB to your PC) or write to to an external SD card e.g. with "dmesg > /external_sd/dmesg.txt".
Perhaps that (dmesg = kernel log) contains something useful.
Click to expand...
Click to collapse
Thank you for taking your time! i will try it asap.

lambdadroid said:
This will probably be helpful at some point, but I would recommend against randomly overwriting all partitions from some memory dump. This might do more harm than good. From what I could tell, your partition table for example seems fine.
You can try booting the following image. This is me176c-boot packaged for USB. It also contains a bootable version of my TWRP build (https://forum.xda-developers.com/t/...p-3-3-1-for-asus-memo-pad-7-me176c-x.3745190/).
Flash it to an USB flash drive using Rufus.
Boot it on your tablet. A menu like I showed above should show up.
You can try the other boot options but I added a special "Recovery (USB)" one. This should boot TWRP from the USB flash drive. (Note: use ↓ to switch options, ↑ or Enter to select an option)
When the TWRP splash screen shows up you can disconnect USB.
Post the output of "dmesg" in the terminal emulator here. You can get it via adb shell (tablet connected via USB to your PC) or write to to an external SD card e.g. with "dmesg > /external_sd/dmesg.txt".
Perhaps that (dmesg = kernel log) contains something useful.
Click to expand...
Click to collapse
Here's the result. i hope it will be helpful.
Also, is there a solution to charge the tablet properly? After the battery capacity goes under 50%(only i can monitor it in TWRP) and then try to connect a power source (AC charger, PC USB cable or USB HUB), Tablet screen is immediately opened in UEFI bios menu by itself. No matter of using power off button. During a cable is connected, tablet goes on again(with release of power off button). Only way i find is opening back cover of tablet and disconnecting power supply terminal of battery for a while. Tablet is charging well via AC charger while screen is completely off(No backlight.) i hope you understand it.

RaiKov said:
Here's the result. i hope it will be helpful.
Click to expand...
Click to collapse
Hmm. There are lots of I/O errors that shouldn't be there.
Code:
[ 8.008459] print_req_error: I/O error, dev mmcblk2, sector 589864
[ 8.008492] Buffer I/O error on dev mmcblk2p9, logical block 0, lost sync page write
[ 8.008641] EXT4-fs (mmcblk2p9): I/O error while writing superblock
[ 8.008692] EXT4-fs (mmcblk2p9): mount failed
[ 8.030538] print_req_error: I/O error, dev mmcblk2, sector 589864
[ 8.030571] Buffer I/O error on dev mmcblk2p9, logical block 0, lost sync page write
[ 8.030868] EXT4-fs (mmcblk2p9): I/O error while writing superblock
[ 8.030919] EXT4-fs (mmcblk2p9): mount failed
This could be caused by this "eMMC has magically become read-only" problem. But I have absolutely no idea how this could happen, it seems almost impossible.
Sadly, another possible explanation for those I/O errors would be that your eMMC is just broken.
Can you try flashing me176c-boot to the internal storage from that TWRP build? Download https://github.com/me176c-dev/me176c-boot/releases/download/0.3.0/esp-0.3.0.zip and unpack it to external SD card.
From TWRP terminal do dd if=/external_sd/esp.img of=/dev/block/by-name/ESP (make sure to type it correctly). Before rebooting, copy the dmesg again to see if there are new I/O errors. (You can post it here if you are not sure how to read it...)

How To Guide [ROM][MIUI][sweet] Xiaomi.eu ROM for Redmi Note 10 Pro

How to install Xiaomi.eu ROM for Redmi Note 10 Pro
We will release fastboot ROM versions until TWRP for sweet is released
TWRP is released, so install our ROM as usually
Steps to install xiaomi.eu ROM for first time from China ROM (All your data and files on internal storage will be deleted!)
- Update Global ROM to the latest via updater app first..
- Unlock your bootloader by Mi Unlock tool https://en.miui.com/unlock/
- Download our ROM zip file xiaomi.eu_multi_HMNote10Pro_V12.0.6.0.RKFMIXM_v12-11.zip
- If you are on Windows: Right click on downloaded zip - Settings - Unblock zip content
{
"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"
}
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via original USB cable
- Run fastboot installation script as administrator from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_first_install_with_data_format.bat
For Linux ./linux_fastboot_first_install_with_data_format.sh
For MacOS ./macos_fastboot_first_install_with_data_format.sh
- After reboot its done (first boot may take up to 15min)
Steps to install update of xiaomi.eu ROM (All your data and files on internal storage will NOT be deleted!)
- Download our ROM zip file STABLE
- Unpack downloaded zip file in the PC
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system
For Windows OS ./windows_fastboot_update_rom.bat
For Linux ./linux_fastboot_update_rom.sh
For MacOS ./macos_fastboot_update_rom.sh
Update guide on the video
- After reboot its done (first boot may take up to 10min)
Update via OTA:
Installation via OTA is currently not possible due to missing TWRP
Updater will notify you about new version and download it to your device for you
You have to copy it to your PC, unpack it and run fastboot_update_rom sctipt
Enjoy..

Do we have root/magisk with it?

Lycox said:
Do we have root/magisk with it?
Click to expand...
Click to collapse
nope.. if you need ROOT, you have to install Magisk by yourself..

Is there any way to unlock bootloader without wiping data?

saaqirajput said:
Is there any way to unlock bootloader without wiping data?
Click to expand...
Click to collapse
Unfortunately, no.
Also since we already have a custom TWRP available for Sweet, would it be possible to have a non-fastboot ROM for xiaomi.eu ?

Bloblom said:
Unfortunately, no.
Also since we already have a custom TWRP available for Sweet, would it be possible to have a non-fastboot ROM for xiaomi.eu ?
Click to expand...
Click to collapse
ok, released flashable zip for TWRP
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/xiaomi.eu_multi_HMNote10Pro_V12.0.6.0.RKFMIXM_v12-11.zip/download

ingbrzy said:
ok, released flashable zip for TWRP
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/xiaomi.eu_multi_HMNote10Pro_V12.0.6.0.RKFMIXM_v12-11.zip/download
Click to expand...
Click to collapse
Can we install the zip rom on top of the stock rom without installing fastboot version first?

sure..

ingbrzy said:
ok, released flashable zip for TWRP
https://sourceforge.net/projects/xiaomi-eu-multilang-miui-roms/files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv12/xiaomi.eu_multi_HMNote10Pro_V12.0.6.0.RKFMIXM_v12-11.zip/download
Click to expand...
Click to collapse
Thanks, it works perfectly.
Wonderful to see a working TWRP and xiaomi.eu so soon after the phone's release.

Hello,
I followe the guided, but after 30 minutes, the procedure is freezed in sending data.
I stopped and relaunched tha .bat files, but it says:
Missmatching image and device
Now the phone is in fastboot mode, what can I do?
Thanks
Edit:
I disconnected the device, rebooted in fastboot and restart the flash, but I have the following error:
Finished. Total time: 128.911s
Erasing 'metadata' OKAY [ 0.003s]
Finished. Total time: 16.693s
Erasing 'userdata' OKAY [ 0.372s]
F2FS-tools: mkfs.f2fs Ver: 1.13.0 (2019-09-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 224550872 (109643 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 556] Filling sit area at offset 0x00600000
E:\temp\xioami.eu_12.0.6.0\platform-tools-windows/make_f2fs failed: 3221225477
fastboot: error: Cannot generate image for userdata
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
Edit2:
Phone booted but it says it doesn't have the play protect certification.

So since there is already a custom TWRP available, will you stop making the fastboot ROM version? is that I'm less than 12h to unlock the bootloader and I didn't want to be installing a version and then having to delete everything and install the version by TWRP ...

yes.. there is no point of fastboot rom version when TWRP is released..

ingbrzy said:
yes.. there is no point of fastboot rom version when TWRP is released..
Click to expand...
Click to collapse
I can't find the twrp version rom please upload the rom once more thank you

ROM reuploaded..
fixed SafetyNet issue

Sourceforge mirrors didn't get created properly so I'm unable to download, please re-upload or provide a mirror.

its normal when servers are overloaded.. try again later..

Was the TWRP removed again? I will be able to unlock my bootloader this night and don't know, if I can use TWRP, which was here before and the flashable Rom or if I should stick with the fastboot Rom for now

did it all in one!!! was a bit scared..hahahaha but everything works perfect!!!

adversario71 said:
did it all in one!!! was a bit scared..hahahaha but everything works perfect!!!
Click to expand...
Click to collapse
What you did?

ZainBilq said:
What you did?
Click to expand...
Click to collapse
just normal procedure..flash twrp..wipe data..then data,dalvik,cache..flash zip rom via otg..after flash wipe data again and thats it