Develop Bugs

HTC One E9 plus - dotview

Hello Dears,
kindly help me as my phone after hard reset stuck on dot view mode automaticly and i can't exit it or even setup my phone like gmail or lang ,
after five seconds after make har resest dot view mode apper and i can't exit it ,
{
"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"
}
Best Regards ,

Redo the hard reset and try again. Also, I suspect that your screen is frozen (watch for changes in dot view mode, like time and battery percentage). It might also be that your tactile screen isn't working anymore and requires a change.

sharvyngunga said:
Redo the hard reset and try again. Also, I suspect that your screen is frozen (watch for changes in dot view mode, like time and battery percentage). It might also be that your tactile screen isn't working anymore and requires a change.
Click to expand...
Click to collapse
Thanks Dear for your replay ,
but the screen is not freezed as i can check my call history and time and battary status ,
also i made har reset and change all frim as i made new flash but problem still exist ,
Regards

Can you share a video of the boot process?
I'll try my best to help you, but I can't guarantee success.

sharvyngunga said:
Can you share a video of the boot process?
I'll try my best to help you, but I can't guarantee success.
Click to expand...
Click to collapse
Thanks Dear ,
i don't have another phone , but i will try to get new one ,
Thanks

Sorry, this is completely unrelated from the current topic but I reallly need help..I tried to flash a rom on my HTC but thr preloader got corrupted xo my phone go hard bricked. Pluging the phone into a computer just shows a red led and the computer shows nothing in device manager.
I tried uninstalling the MTK Preload VCOM driver and reinstalling it but that still didn't work.
Even pressing volume keys while connecting still gave nothing.
I also tried disconnecting the battery and reconnecting the phone to the computer but still nothing.
If there is anyone, please help me.....
I need to unbrick my phone................... I am begging, please help me.

When my E9 got hard bricked, I sent it to a repair shop. They took a long time, but they brought it back to life.
Now, I had a hard brick issue with a Lenovo P1M Vibe (also a MTK device). I solved it using SP TOOL and the proper files. I don't know why the app suddenly decided to detect my phone after dozens of tries. But, during my research, I found interesting articles:
How to get a PC detect and MTK device after flashing wrong ROM/Firmware (Test Point method)
Download the latest & updated stock rom firmware of popular phones like samsung, tecno, itel, infinix, etc with flashing & upgrade tools & instruction
www.romkingz.net
As for the software part of the solution:
[Guide/Info] [How To] Unbrick your Bricked MTK Devices (Dead Brick)
This thread is about how to recover the MTK Android phone, if it has gone Bricked (soft/hard/dead/etc) THIS IS FOR INFORMATION ONLY. Q. How Phone gets Bricked? Ans : Basically, phone get bricked during the installation of Android OS (flashing)...
forum.xda-developers.com
You will need additional files for your phone during this process. You can find them online.

Can't find my device in fastboot mode

Hi, i want to unlock the bootloader of my old Redmi note 5, but there's a problem, when I go into fastboot mode, the Xiaomi's software can't find it, even using ADB the device is impossible to find. If I turn it on normally i can find it. Why it happens?

Hey u may give this a try as based on my understanding Xiomi devices will require u to install mi flashtool on PC as it has driver installation option. Remember some times you are required to disable driver signature verification.

I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.

plusminus_ said:
I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.
Click to expand...
Click to collapse
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
{
"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"
}

Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
Weird.
Maybe try a different cable?

Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
U might be using an Amd based system. Usb 2.0 hub is ur solution

Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.

drnightshadow said:
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.
Click to expand...
Click to collapse
Can you tell me about this usb 3 reg patch?
Actually i am outstation and don't have my usb hub and i want to do faatboot commands

Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me

Banty448 said:
Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me
Click to expand...
Click to collapse
Read the thread and don't be troll. You didn't even read post before you post it your own. Ignorance is a bliss.
Good luck and stay safe.

MiFlash issue > Blocked at Mi Account sign in window

Hello everyone,
I apologize in advance for my English.
I bricked my RN5 Whyred, mi logo loop, no fastboot, enter EDL mode by test point. I see a solution by flashing stock Rom with MiFlash but I am blocked at "EDL authentication"
- A first window opens and I click "Login" (picture "Mi Flash Tool")
- A second window opens and I log in to my Mi Account (picture "Login MI account v1.0")
and the latter does not close, no redirection to the program is possible, when I close the window, MiFlash pop up " Failed login" and flashing abort...
{
"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 tested lot of solutions and lot of ROMs (MI 9/10/11), I have the same problem with MiPhoneAssistant, blocked by the Mi Account window.
So, I try to bypass authentication by using firehose patched file but not working.
I read that I was not the only one stuck on this window, do you have a solution? Maybe an older version of MiFlash? or modified to bypass authentication?
Thank you very much for your answer.
Stef

Note for Moderators :
I'm sorry, I posted in the wrong category. Please move in Questions & Answers inventory

Hi,
Did someone have a solution of the MiFlash issue ? I read a lot of posts regarding the EDL download authorization and I am a little disappointed...
Do you have a patched firehose method that works for RN5 Whyred? I have the impression that this remains the only solution.
Regards,
Stef

Stelephant said:
Hi,
Did someone have a solution of the MiFlash issue ? I read a lot of posts regarding the EDL download authorization and I am a little disappointed...
Do you have a patched firehose method that works for RN5 Whyred? I have the impression that this remains the only solution.
Regards,
Stef
Click to expand...
Click to collapse

You need to use patched firehouse in EDL mode only and patched xml for persist partition in miflash tool ... but you can combine them under EDL mode to flash your rn5 and completely remove account.
I advice you firstly to try with miflash tool with patched xml and probably wont work... need to sign in
read it how to patch xml:
Remove MI Account in any Redmi Phone
While flashing fastboot rom Just edit ur rawprogram0.xml in notepad ++ Find line of persist Add persist.img Under "" before persist Like "persist.img" And save it Then flash:cool:
forum.xda-developers.com

Stelephant said:
Hello everyone,
I apologize in advance for my English.
I bricked my RN5 Whyred, mi logo loop, no fastboot, enter EDL mode by test point. I see a solution by flashing stock Rom with MiFlash but I am blocked at "EDL authentication"
- A first window opens and I click "Login" (picture "Mi Flash Tool")
- A second window opens and I log in to my Mi Account (picture "Login MI account v1.0")
and the latter does not close, no redirection to the program is possible, when I close the window, MiFlash pop up " Failed login" and flashing abort...
View attachment 5446803View attachment 5446805
I tested lot of solutions and lot of ROMs (MI 9/10/11), I have the same problem with MiPhoneAssistant, blocked by the Mi Account window.
So, I try to bypass authentication by using firehose patched file but not working.
I read that I was not the only one stuck on this window, do you have a solution? Maybe an older version of MiFlash? or modified to bypass authentication?
Thank you very much for your answer.
Stef
Click to expand...
Click to collapse
bro me tool i am stuck in there.I have problem even unlocked device.mi flash tool take me auth account if sign in problem as your picture.redmi 7 onclite no auth file not found.

bro you can login with mi flash tool version 2021 but you can stuck in edl auth.

Stuck/bricked in EDL mode?! That's the solution!

This is 2 days long story..
A friend gave me his Poco M3 for changing rom.
Searched an alternative working way to bypass the 7 days wait to unlock bootloader.
After some tries the phone goes in permanent EDL stuck.
Lost 2 nights searching and tried EVERYTHING: Qfire, Miflash (bypassing login but error for "not associated to this account"), enegeering rom, test points, etc..
After the successfully flashed, the phone was yet in EDL mode.
No way to exit.
but, finally, found a solution.
Heres what you need:
- Qualcomm Drivers
- Fastboot ROM
- MiFlash
- Patched Firehose (for bypass login to MiFlash)
Procedure:
- Install the Qualcomm drivers
- extract the downloaded fastboot rom
- go into rom folder, then images folder, and overwright the Firehose with the patched one
- now disconnect the fingerprint sensor cable from mainboard
- open Miflash, select the folder and flash it
- after complete the flash, disconnect cable from pc, disconnect the battery, reconnect the fingerprint sensor cable and reconnect the battery
and, magically, NOW WORKS.
Follow the procedure exactly otherwise will not work and will be stuck in EDL.
Hope to save time and money to someone have my same problem.

Nope mine is stuck at flashing state... I hate this phone, I tried almost everything
But thanks anyway
{
"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'm constantly amazed how crappy all this software is.
First, there is this fixation with Com ports. That's so 1990's.
The USB interface is just a plain ol' bulk interface. Why not use that instead of some bogus virtual Com port driver?
Everything should have timeouts, there is no reason that a program should hang.
I'd almost suggest that you try my EDL client but I don't know if this flash_all is using sparse files or calculated sizes which are not things that I've implemented.

For my daughter's M3 the trick worked, but only one time.
When I switched off the phone, it returned to EDL mode.
Works only if I don't switch off the phone.
There must be a hardware fault/bug, probably triggered by the latest MIUI 12.5 update. I think that this problem will not have a definitive working solution.

flash in miflash error set patition needhelp

fastleo63 said:
For my daughter's M3 the trick worked, but only one time.
When I switched off the phone, it returned to EDL mode.
Works only if I don't switch off the phone.
There must be a hardware fault/bug, probably triggered by the latest MIUI 12.5 update. I think that this problem will not have a definitive working solution.
Click to expand...
Click to collapse
I can confirm that this happens. My Poco M3 does the same thing. I can flash it in EDL mode but after a reboot (or two) or powering it off and powering it back on, it's stuck in EDL mode once more.
This phone is dreadful and it's such a shame.
I'd love to see a proper, permanent solution to this, but I don't think it's possible.
Maks13xe said:
flash in miflash error set patition needhelp
Click to expand...
Click to collapse
There's probably not much you can do besides trying again. Make sure you are on the most recent version, I think it's 20220507
Personally, I just had to select the rom folder (after replacing the prog_firehose_ddr.elf file in the images subdirectory) and then flash.
This thread has the proper details: POCO M3 Stuck in EDL
You can get the most recent MiFlash here: Xiaomiflashtool.com - Xiaomi Flash Tool 20220507

[Q] I can't root my xiaomi redmi note 8 pro

Hi, i have a xiaomi redmi note 8 pro (64gb), with the bootloader unlocked, MIUI 12.5.7 global, debug enabled
Using Google Platform-Tools, after entering fastboot (with "adb reboot bootloader") and flashing the twrp recovery (with "fastboot flash recovery twrp.img") I cannot enter the custom recovery, whether I use the combination of button, whether you use the command "fasbtoot boot recovery/twrp.img"
I tried to change the USB port of the PC but I always get the same error: FAILED (Status read failed (Too many links))
{
"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"
}
Does anyone know how to fix this error? I don't mind having to format the phone.

Have you tried this ?
Write to device failed (no link / unknown error / too many links) - Sample Code and Directory of libraries for Android Developers - AndroidHiro.com
Write to device failed (no link / unknown error / too many links).I am trying to flash twrp to my ZTE Axon 7 but until now I just keep getting errors every time I try to flash something.Device is already wiped and bootloader unlocked.I am in fastboot mode, I also get some unknown error in...
androidhiro.com

Fytdyh said:
Have you tried this ?
Write to device failed (no link / unknown error / too many links) - Sample Code and Directory of libraries for Android Developers - AndroidHiro.com
Write to device failed (no link / unknown error / too many links).I am trying to flash twrp to my ZTE Axon 7 but until now I just keep getting errors every time I try to flash something.Device is already wiped and bootloader unlocked.I am in fastboot mode, I also get some unknown error in...
androidhiro.com
Click to expand...
Click to collapse
Soo should i use a USB hub?
Because I have already tried to use the method that modifies the registry but it didn't help

umbi027 said:
Soo should i use a USB hub?
Because I have already tried to use the method that modifies the registry but it didn't help
Click to expand...
Click to collapse
Have you tried uninstall ing your device existing drivers, shutting down and turning on you computer and reconnecting your phone again ? This can work in some cases

Fytdyh said:
Have you tried uninstall ing your device existing drivers, shutting down and turning on you computer and reconnecting your phone again ? This can work in some cases
Click to expand...
Click to collapse
I tried and it didn't work, but I tried to install a different recobery (so not the twrp) and it worked
thanks so much, for the help anyway

umbi027 said:
I tried and it didn't work, but I tried to install a different recobery (so not the twrp) and it worked
thanks so much, for the help anyway
Click to expand...
Click to collapse
What recovery have you used that works?

Lucz0xxZ said:
What recovery have you used that works?
Click to expand...
Click to collapse
I followed this tutorial:
I followed the tutorial until the custom recovery was installed and then I used the latest version of magisk downloaded from the official GitHub

umbi027 said:
I followed this tutorial:
I followed the tutorial until the custom recovery was installed and then I used the latest version of magisk downloaded from the official GitHub
Click to expand...
Click to collapse
Thanks!