Develop Bugs

[GUIDE]Asus Fonepad 7 FE375CG ( K019 ) Downgrade

Hey My Friends This is my First Guide in This Forum
I Wanted to downgrade to Kitkat So i Take along trip
Disclaimer:
* Warranty is void.
* I don’t guarantee that this will work.
* It maybe cause bad effects to your tablet.
* You are responsible for any damages or other issues that may arise directly or indirectly because of this.
* Very important: All your data and programs will be lost!
* All Files are in the last of the topic
Requirements
* Install Asus Drivers ( included in downloads section )
* install IntelDnXUSBDriverSetup
i got errors during downgrade testing like
# Stuck on ASUS Logo
# Stuck on USB Logo
# No Power on
If u Have any just reply the problem i'll tell u solution
Steps i Did to Downgrade is simply Deleted The Current rom and All Software for asus and re install it again
Let's Start
1 - Go To Fastboot Mode
Turn off Your Tablet
Press ( Power + Volume up )
When Tablet Vibrate leave power button , keep pressing volume up
When asus logo appears leave all buttons
** You Now in Fastboot Mode **
/* if you can't get to fastboot mode bcz it's deleted or damaged Leave Reply i will post solution */
2 - Make Session For CWM
Download IntelAndroid-FBRL-07-24-2015.7z
Open ( launcher.bat ) File
Connect Your Tablet to computer ( in fastboot mode )
Just Type ACCEPT And Press Enter
{
"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"
}
Type 5 And Press Enter
Now Type T3
Wait untill it finished
3 - Disable Verification
Now u must be in CWM Mode
Choose install ZIP
Choose toggle signature verification
( Make Sure it's disabled )
Now Reboot
4 - Remove Current Software
Load your Tablet in fastboot mode
Download and unzip Downgrade_K019_NEW.zip
Connect your Tablet to PC
Run Downgrade-3.cmd
Type Y And press Enter
Wait till finish
** Now Your Tablet won't turn on or it'll stuck on usb logo Don't worry **
Plug it in the computer And Keep Going
5 - install ASUS Software
open Downgrade_K019_NEW
Run Downgrade-2.cmd
if it's not working just try Downgrade.cmd*/
Wait till finish and mobile restart it will stuck on asus logo You can remove mobile now
5 - install Android Official Rom
Download The rom you want to install from asus Site
copy it to SD Card
Rename it to ( mofd_sdupdate )
Enter Fastboot Mode ( You will see it's changed )
choose recovery
Now You will see android installing updates
Just Wait and Congratulations
/**** Downloads ****/
https://www.mediafire.com/folder/52b6q9pa4c4cc/K019_-_FE375CG
:corm All Rights Reversed elza3ym =>( Mohamed Shehata )

Hi i do , but Stuck on ASUS Logo
---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------
Hi , please hel me ,Stuck on USB Logo

sarinna said:
Hi i do , but Stuck on ASUS Logo
---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------
Hi , please hel me ,Stuck on USB Logo
Click to expand...
Click to collapse
Hey My Friend
Sorry for being late
First Solution :
1 - Plug it into the pc
2 - Run Downgrade-2.cmd (if it's not working just try Downgrade.cmd)
3 - Wait till finish and mobile restart it will stuck on asus logo You can remove mobile now
4 - Follow the ( 5 - install Android Official Rom ) From the post
2nd Solution :
Follow this video
https://www.youtube.com/watch?v=9FsdnIrnQYA
But Here's the files You will use
FW DnX => dnx_fwr.bin
IFWI => ifwi_76.57_factory.bin
Os Image => droidboot.img.POS.bin
Untill u see the droidboot page loads Now
Now Resume The Steps
Download the files
https://www.mediafire.com/?54kyud40cqu6kad

Thanks? but do not worked for me ?I think bootloader is lock? do you any way for unlocking bootloader? i need raw image firmware ? thanks

please help me, xsfstk-dldr-solo.exe force close, but 2 weeks ago i can run it and root ko019, but now that force close, help me please

T3 step not working for me.auto exit.what is the solution.?
Yes. I do it. Successfully. Thank you very much.

On step 3 after I typed T3 and press enter, all writings failed n I didn't get to enter CWM mode. What could be the reason, am I missing something?

It cant go to CWM windows after T3, What can I do?

Hi, this is Kristein. I am working constantly to provide information regarding various issues of entertainment channels like YouTube. Recently I have written a blog on issue of YouTube Not Working On Android Devices. This writing contains in-depth to rectify this issue from its roots.
thequeryhub.com/youtube-not-working-fix-it/

ASUS K019 how to add CWM mode
ASUS K019 how to add CWM mode ?My English is not good.Thanks.

Steps 4 and 5 don't work
Hi. Steps 4 and 5 don't work and this error shows up:
'findstr' is not recognized as an internal or external command,
operable program or batch file.
'findstr' is not recognized as an internal or external command,
operable program or batch file.
#####################################################################
!!! ERROR !!! IFWI NOT EXIST, EXIT!
#####################################################################
Press any key to continue . . .
Click to expand...
Click to collapse
What should I do?

Can anyone help? mine doesn't even detected by the pc. As soon as i connect the usb cable or the battery it turns on and vibrates twice. The usb logo shows and stays until i disconnect both the cable and the battery. Key combinations won't seem to have any effect. All drivers correctly installed... can anyone help? Is there a testpoint i can force the usb?

Ultra Keto X Burn Formula should enable your body to remain in ketosis longer. What's more, it's likewise expected to enable you to get into ketosis. Like we stated, remaining in this fat-burning zone is indispensable in the event that you need to lose genuine weight. Furthermore, ketosis can make you feel fiery, centered, and increasingly positive. You just may discover you LOVE being in ketosis. Snap any picture to get the top of the line ketosis pill online at the present time!
wellness4supplement.com/ultra-keto-x-burn

Rollback EMUI from 10 to 9 to bypass FRP

Hi all,
Got a mobile that we dont know the previous Gmail account this was registered with. Therefore, I need to bypass the FRP to recover the mobile and use it for testing purposes. Accidentally, I upgraded it to EMUI 10 and after fixing several softbricks, I have no clue how to downgrade it to EMUI 9.
Goals:
Rollback EMUI 10 to 9 on Huawei 20x C185
Abuse flaws on EMUI 9 to bypass FRP
Do all via Linux tools (preferably console)
Firmware
EVR-L29 C185 EMUI 10
https://mega.nz/#F!zRUGFKyZ!je09cCOdJRPePDvykLwJCQ
http://www.mediafire.com/file/m7l6xlqe4se0u7s/dload.zip/file
Fail attempts
Enter upgrade mode and dload a previous C185 EMUI 9.0.x or EMUI 9.1.x (via OTG cable + microSD card). This always produces the same error: Software upgraded failed!
Try to change country to have chances to flash different firmware.
Logs:
Code:
> fastboot oem get-build-number
...
(bootloader) :EVR-L29 10.0.0.180(C185E6R3P3)
OKAY [ 0.011s]
finished. total time: 0.011s
> fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.019s
Any idea?

Try Hisuite

sunrider07 said:
Try Hisuite
Click to expand...
Click to collapse
hey @sunrider07,
apparently you need to enable HDB options to use HiSuite, right? Tested HiSuite on Linux emulated via Wine. I was able to use the Huawei tool but I couldn't hook up the mobile to the app. Have you used HiSuite to downgrade the bootloader? If so, it is really needed to have adb connection? Remember my phone is protected via FRP.
This is the way to enable HDB (Huawei ADB dev options):
4. Go to device setting and enable USB Debugging. You can follow our guide on how to enable USB Debugging on Huawei phones.
5. Connect HiSuite to your mobile.
6. HiSuite will automatically shows a system update on your device.
Click to expand...
Click to collapse
Being blocked by FRP, HDB switch cannot be enabled so i am not sure if HiSuite can be used
{
"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"
}

My phone is fully stock and unmodified.
And yes, HDB must be enabled for the app to connect.
I was able to downgrade my phone just two days ago and everything works as expected

sunrider07 said:
My phone is fully stock and unmodified.
And yes, HDB must be enabled for the app to connect.
I was able to downgrade my phone just two days ago and everything works as expected
Click to expand...
Click to collapse
Thanks for your answer. Unfortunately, I do need to find another way to perform a downgrade on the bootloader and base image to EMU 9.0 where there are public and known vulnerabilities to overcome FRP. Otherwise, I will need to wait until a FRP bypass is public, or reverse engineering the HiSuite software to find some fastboot commands to see if I can leverage any of these. It seems I am stuck with it.

Apparently I found this video from 5 days ago: https://www.youtube.com/watch?v=USvi-1O2Y6o
Anyone knows well the mode USB upgrade?

--

mac231us said:
I saw that too. I too need to downgrade but cannot as usb is not connecting. I can connect to one of the Hisuite versions through wlan option but it cannot be used to change the system (only through usb). Cannot do system recovery (says take it to service center)
Yes video shows if you go into usb mode through recovery (which I can) you can use the MRT tool to flash the rom. I plan to look into it. Otherwise I might just take it to a service center in an upcoming overseas trip (still almost 2 months away)
Click to expand...
Click to collapse
Do you know where to download this MRT tool? It seems like super unprofessional tool without github repo.
mac231us said:
Separately in my case-The device is not recognized when connecting through usb to the computer (usb ports, cable, windows version, drivers etc all tried-the device type and name is not recognized. OTG usb works but that is only for backups, backup restore and dload method to upgrade-which cannot be used to downgrade to 9.1 or 9.0 from 10.0) Fastboot commands are severely limited in 10 as my device country vendor is unknown. The device works fine otherwise (calls, mms, apps, internet, themes) Device cannot be registered at Huawei as unknown device though I can register in themes. With dload I can switch back and forth between 10.0.0.180 and 183 or even a lower 10 but not to 9 series.
Click to expand...
Click to collapse
Dont own a Windows10 laptop to use HiSuite, looking for one to see if I can connect it via WiFi. Did you mention you can use all these calls, mms, apps, internet, themes? In this case, we have different issue.
Can you run this command?
Code:
$ fastboot getvar vendorcountry
vendorcountry: hw/meafnaf
finished. total time: 0.019s
mac231us said:
Surprised there is no way to fastboot erase and install firmware-I heard you need a service rom to completely redo the phone.
Click to expand...
Click to collapse
The MRT tool must use a fastboot command too. We can always reverse this tool to extract the command. Do you have the tool?

In this video there are downloading links:
MRT sw

--

anyone able to bypass the frp?

Clear-simple method install W10 on <4gb ROM

I get it done with more than 1Gb of free storage !
-I have lumia 530 Dual SIM (1019) previous build was 8.1 I don't recall OS version but it was the latest, so yeah I searched for more information and I found this thread https://forum.xda-developers.com/win...date-t3527340/ of this glorious man @hikari_calyx
-I tired to install W10 even the method says that not supported for 4gb devices, and it was really a fail because following his steps ended up with fail to update due to low storage, then I tried to delete anything I could, but again it fails for just 140mb or so... an idea pops up in my head which updating after a hard reset so the OEM apps won't get installed, and
here are the steps
1- go to the link provided for @hikari_calyx and follow the steps (make sure to download the .cab files) until it fails to update.
2- perform a hard reset to your phone (power off, press vol - and power button together after the vibrate release ur finger from power button and keep pressing vol - then in order : vol - vol + power button vol - )
and don't pass the language selection screen just keep it there.
3- Now go and update it like you just did before hard reset, it will take a lot of time just plug it to a power source and keep it cold, maybe more than 1 hour.
4-hurry it boot up you might face a problem in "Almost done.." screen, so the solution is : lock the screen and turn it on again, once u slide the lock screen up and before the app reloads keep pressing the "win" button it will open "one handed mode" then bring down the notification center and press anything (maybe win button I don't recall) until it goes to home screen (not 100% sure what I have done it was so random lol)
Congratulations u have W10 with a lot of storage.

STALKER18 said:
I get it done with more than 1Gb of free storage !
-I have lumia 530 Dual SIM (1019) previous build was 8.1 I don't recall OS version but it was the latest, so yeah I searched for more information and I found this thread https://forum.xda-developers.com/win...date-t3527340/ of this glorious man @hikari_calyx
-I tired to install W10 even the method says that not supported for 4gb devices, and it was really a fail because following his steps ended up with fail to update due to low storage, then I tried to delete anything I could, but again it fails for just 140mb or so... an idea pops up in my head which updating after a hard reset so the OEM apps won't get installed, and
here are the steps
1- go to the link provided for @hikari_calyx and follow the steps (make sure to download the .cab files) until it fails to update.
2- perform a hard reset to your phone (power off, press vol - and power button together after the vibrate release ur finger from power button and keep pressing vol - then in order : vol - vol + power button vol - )
and don't pass the language selection screen just keep it there.
3- Now go and update it like you just did before hard reset, it will take a lot of time just plug it to a power source and keep it cold, maybe more than 1 hour.
4-hurry it boot up you might face a problem in "Almost done.." screen, so the solution is : lock the screen and turn it on again, once u slide the lock screen up and before the app reloads keep pressing the "win" button it will open "one handed mode" then bring down the notification center and press anything (maybe win button I don't recall) until it goes to home screen (not 100% sure what I have done it was so random lol)
Congratulations u have W10 with a lot of storage.
Click to expand...
Click to collapse
That seems tricky ,I LL try that for I have a lumia 530 and there isn t another way to get W10 on it. I didn t read the Hikari thread yet but which .cab files did you download? Lumia 535 one? Thank you

Arny80 said:
That seems tricky ,I LL try that for I have a lumia 530 and there isn t another way to get W10 on it. I didn t read the Hikari thread yet but which .cab files did you download? Lumia 535 one? Thank you
Click to expand...
Click to collapse
oh. sorry for that, didn't use xda for a long time now.
i just let the program works by it self. if I recall. sorry again xd

While at least now it does copy the files to the device, I can't get past this. Do you know how to fix this, or alternatively, give me the backup files (EFIESP, MainOS and Data) for WPInternals? I'd probably prefer a solution to fix the update software over your firmware dumps though.
PS: I'm also using a Lumia 530.
Update: if you're getting the error attached below and trying to do this on Windows 10, I found a solution. What you want to do is to make a Windows 7 VM which is not updated, or to Jan-2016 at maximum and follow the steps of the OP. The error below here is a syncing error, which is probably because of the amazing Windows 10 driver support . Also, if stuff in the W10m OS isn't working properly, you could try a factory reset first
{
"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"
}

Realme UI 2.0 update issue

Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.

soham93 said:
Hello everyone. Hope you all are doing well.
I had updated my Realme 6 Pro from Android 10, version RMX2061_11.A.49 to the Android 11 update i.e. Realme UI 2.0, version RMX2061_11.C.15. The thing is, after optimizing apps during the first boot, the phone is stuck at the lock screen and the touchscreen is not responding.
Video of the issue is here: Realme 6 pro UI 2.0 issue
Kindly do help on what to do next. Doing a reset is the last step I want to undertake, since I forgot to take a backup.. Will flashing the Realme UI 2.0 update via stock recovery help? Any help and suggestions would be much appreciated.
Thank you.
Click to expand...
Click to collapse

Hello soham,
I have the exactly same problem since the yesterday update with my Realme X2 Pro.
If you find a solution please let me know
...at the moment i have no idea.

yeah bro same with mine,
but we have another choice,
drain the battery and let the mobile turn off
after that go to the recovery mode and wipe your data.
or else we need to update the software in the recovery mode which is not arrived yet.

Press the power off and volume up button for about 7 sec and it should power off. when u turn it on press the power off and volume down button for 10 sec and you will boot to recovery mode. After that, u will have to format your data which will cause ur data to be removed.

I dont think there is any other way to fix this. Unless you have your data back up in the cloud. Maybe you can also take out the storage card from your phone which is difficult and then back up your data from a pc or something.

I thought of flashing the ROM, but it was not available anywhere. So I ended up performing a factory reset to boot the phone. There seems to be no other solution for this.

I have no backup..so i wait for the next update..
Wipe data doesnt work for me and i do not format the device.

I have the exact same issue. This problem generally applies to all Realme devices upgraded to Realme UI 2.0. The root cause is the disabling of com.coloros.weather.service package, usually done during debloating through adb. Further analysis I have done is explained on my thread.
Quick fixes you have now:
If you have adb enabled and ticked "Always allow from this computer" on the prompt below when your phone is still working, you can connect your phone in the blinking state and issue the following command: adb shell cmd pm enable com.coloros.weather.service. Then, reboot your phone. It will work normally on Realme UI 2.0.
{
"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"
}
Click to expand...
Click to collapse
[DATA LOSS] Download this ozip and put it on an SD card. A used SD card works fine as long as it isn't encrypted and has enough free space. Make sure the file name matches your device model. Enter realme UI Recovery (on Realme 7, you press VolumeDown + Power, which might differ for each device) and choose 'Install from Storage'. Enter your device password, select 'SD Card', and pick the ozip you have downloaded. The phone will wipe itself, and you end up with a working phone on Realme UI 1.0.
[DATA LOSS] If your phone is still on warranty period, go to any Realme Service Centre, and use the following statement; the service centre will either replace your phone free of charge or if they don't have any replacements in stock, put you on a waitlist and calls you back once the replacement device is available.
I am updating my device to Realme UI 2.0 when suddenly the device turns off and reboot itself. Now, this device won't allow me to unlock it.
Click to expand...
Click to collapse
Other possible, longer-term solutions are:
Wait for Realme to realize this problem and issue an OTA update. The fix is easy on their side; just add a simple one line on the after-flash script of the next OTA/ozip to enable the weather services package:
Code:
pm enable com.coloros.weather.service
The command pm enable would do nothing if a package is already enabled. However, Realme might not realise this problem. Even if they recognise it, Realme might think it is not their own problem (debloating = user's fault?). If they release this fix, we can just boot into recovery and install it. Realme has support for OTA updates on their recovery. Just enter the device password and then the WiFi password.
I have tried exploring the Realme forums, albeit not directly filing a bug report. I found many, many users experiencing a similar issue as ourselves. Most of it was responded to by Realme representatives in this fashion: "enter recovery mode by pressing this and this, and then choose to wipe data. This will reset your phone to its working state." This is not acceptable for me since a functioning phone is lower on my priority than keeping my data (albeit in limbo).
Suppose your device has MediaTek SoC, and you have not set up any password/PIN/pattern on your device. In that case, you could possibly extract the userdata partition, exploiting the Boot ROM (BROM) exploit by Dinolek and k4y0z with the SP Flash Tool. You first need to find a specific scatter file for your device; however, if none is available, you could generate one from a preloader dump using a tool named Wwr MTK.
If you have set up a password, then this would be infeasible, apparently, since not only the device password is needed to decrypt it, but also some salt stored on the SoC itself; hence this thread highly suggests swapping SoC and eMMC to another working exact same phone (cannibalize another phone).
However, even after you swapped the SoC to a new phone and write your userdata partition on it, you faced a new dilemma:
previously on the old phone, you have a non-working software config, but the decryption key to the userdata is the same as the decryption key to the other partitions
now on the new phone, you have a working software config. The decryption key is available on SoC, but the other partitions are unreadable to the bootloader. They are either unencrypted or encrypted with a different key.
I have not been able to solve the above dilemma.
Hence, my current objective is to nag Realme and invite others to also nag them to implement that simple one line on their OTA update.

any updates? today i update realme 6 to realme ui 2.0 it broke my phone... because of this weather crap usb debugging not working for me...

I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.

vigneshrajarr said:
I too ran into this issue just now. Thanks @said1219 for your suggestion. A single change in my case. I haven't disabled the app, I have uninstalled it. So I ran
adb shell cmd package install-existing com.coloros.weather.service
This fixed the issue. This didn't require restart.
I use Realme C3. After this update again there is a new update of 280MB released on Dec 9, 2021, specifies system optimization.
It doesn't make any issue after this.
Click to expand...
Click to collapse
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on

Quasar.Illumia said:
I have a question, how did you reinstall the weathersystem even if your phone is flickering? Did you do it on power on or in recovery mode? That is an adb fastboot right?? Does your phone prompt you and asks to "file transfer" and "charging only"? Because that's the only last thing I have to do, let my pc run adb fastboot to turn it on
Click to expand...
Click to collapse
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.

I thought it wasn't working when I entered adb shell yesterday. Thank you UwU it is working now
said1219 said:
You let the phone complete boot and enter the flicker-state. Then run "adb devices" as per your photo in my thread.
The following step can be done either on normal boot, fastboot, or recovery mode:
If no device is found, it is likely that USB debugging is disabled on your device.
If your device is found, but it says 'unauthorized', it means that you didn't tick "Always allow connections from this device" or a long time has lapsed since you've connected your PC's ADB to your phone.
If your device is found and it says 'device' on the right of the serial number, you're good to go.
Except for the last scenario, you're possibly getting back to square one.
The following step must be done after the phone completed normal boot, recognized your PC, and enter the flicker-state:
If you disabled the weather package, run
Code:
adb shell cmd pm enable com.coloros.weather.service
If you uninstalled the weather package, run
Code:
adb shell cmd package install-existing com.coloros.weather.service
Your phone will immediately stop flickering and you can enter your password normally. And, as per my reply in my thread, "Allow charging only" could prevent you from accessing ADB.
Click to expand...
Click to collapse

Well then, another year has gone by
No changes so far? I noticed new Realme UI updates have been launched in the meantime. Has anyone tried them out yet on the blocked phones?
As you've recommended @said1219 , I've kept my battery in good condition and still hope that this problem can get solved in the future...
However, since this issue started, by principle I've refused to buy any new Realme product...

Question Hard bricked Mi Pad 5, while installing windows 11

Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)

mdve123 said:
Hi, is there any alternatives to rescue my device? i can not enter to fastboot, nor to recovery.
In miflash i have no active connection. Is there any solution, or did i just make it dead?
only shows mi logo (powered by android)
My theory is that my EFI bootloader was written in memory, therefore my bootloader is gone after restarting windows.
(interestingly there is no bootloader unlocked indication, as before.)
Click to expand...
Click to collapse
Sorry to hear that, please share your steps to disaster to let others know how to avoid this.
I assume that you used default Windows installer that broke your ufs gpt, instead of the installer you should have been used dism.
At this stage only a service may help you, they will put the device in edl mode and flash a stock firmware.

I think the only way to bring it back to life is to get it into EDL mode and force flash stock rom.

but to get to EDL first have to get to fastboot, i dont think it will work, also tried...

mdve123 said:
but to get to EDL first have to get to fastboot, i dont think it will work, also tried...
Click to expand...
Click to collapse
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.

serdeliuk said:
That is one way to get EDL, the other one is with a special USB plug if your device permit this, or open the back case and short two special test points on motherboard before power up to enter the EDL.
After you have your device in EDL mode you will need a tool to flash a stock image but as well you will be required to use a special program to authenticate, known as firehose, that kind of program should be signed by Xiaomi, this is why you need to go to an "authorized" service, which paid the signing authorization to Xiaomi.
Click to expand...
Click to collapse
Very useful info thank you! Just ordered a deepflash cable, hopefully i will find a workaround to flash in EDL.
If not, i'll try to get it done under warranty. I do not want to risk a keylog or a scam.

I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked

RoyPH9903 said:
I bricked my tablet in the same way, only I can enter fastboot mode, by mistake when flashing a rom I did not change the option to lock the bootloader, now my pad 5 only turns on in fastboot mode, I don't have access to anything else , it does not let me flash with xiaomiflash because it says that it cannot proceed with the bootloader locked
Click to expand...
Click to collapse
You should download the latest MIUI Stable Fastboot update corresponding to your region (global, eeaor other) from this thread https://forum.xda-developers.com/t/miui-updates-tracker-xiaomi-pad-5-nabu.4328591/ , decompress the tgz file with 7zip or another software, and then, with your device in fastbboot mode, execute the flash_all.bat file within the folder you extracted. This should work even with a locked bootloader.
Good luck

I get this error
{
"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"
}

RoyPH9903 said:
I get this error
View attachment 5883229
Click to expand...
Click to collapse
Well, maybe I was wrong and you need an unlocked bootloader for this method to work. You could try to unlock it again with MiUnlock https://en.miui.com/unlock/download_en.html . Otherwise, I am out of idea.

I tried it and it didn't work, it tells me that I have to enable my miui account.

RoyPH9903 said:
I tried it and it didn't work, it tells me that I have to enable my miui account.
View attachment 5883255
Click to expand...
Click to collapse
Well, then I'm out of ideas. Maybe you should see what the seller's support can do.