Develop Bugs

partially bricked

I can get my Zenfone 2 up to the fastboot screen, but no further.
Under PC device manager is shows "Android-Phone" as the device, but no drivers loaded.
I've tried a few different drivers, but even though they seem to install OK, "Android-Phone" (in device manager) still won't show as having a driver.
Some threads say I have to enable Android Debugging, but how to do that when the ONLY screen I can get on the phone is fastboot??
Help???
Boowho??

You can try this.
1. Uninstall all drivers for phone you installed on PC, then reboot.
2. Disable antivirus on PC then install standard Intel android device usb drivers. You can download them from Asus website. Then reboot again.
3. Connect phone to PC in fastboot mode.
4. In the device manager you should see "Asus android device" under which "Asus android bootloader interface".
5. Check connectivity in minimal adb & fastboot software (you can get it from XDA) by command "fastboot devices" without quotes. It should answer "some number<space>fastboot".
If all is ok then you can flash raw stock firmware in fastboot mode & update it to latest version OR unlock bootloader, flash TWRP & install custom rom.

Thank you Sanesh. I got all the img/bin files successful now. However, the ZF2 has this issue when you select recovery from bootloader screen it gives dead android. You can then (extra step) hold power and VOl + and get into stock recovery. This is a flaw in the original firmware, I think.
BUT, this extra step is causing TWRP not to be entered. Stock recovery is OK, but not TWRP.
I had to recover the phone using the SOC drivers; before that TWRP worked perfectly.
Thanks

Have you unlocked bootloader ? Unlock bootloader first then flash twrp using giovix92 method. Then reboot to recovery.

Thanks. Turned out I was using a twrp image that is only for marshmallow. I still use lollipop. Every thing is now back to where it was before I had to recover the thing using the SOC method.
Lesson learned. un-root before trying to upgrade to MM.

I bricked my new Mi Mix 2 - not the computer does not recognize it

Hi,
I used the XiaoMiTool to flash my Mi Mix 2 from Chinese ROM to global. Around 90% of the flash process, the progress bar on the phone did not changed for 2 hours (!!!). I rebooted the phone and now it is with Mi logo as you can see from the img https://imgur.com/a/O9BZ8
I can enter fastboot and recovery mode, but now my computer does not recognize the device anymore (so I can re-flash it) - I get "unknown USB device" in the device manager. I installed Qualcomm driver, but still the same.
Please help!
please notice that I'm not too technical, therefore would appreciate detailed answers if possible.
Thanks ahead!

try the different computer and different USB TYPE-C cable to check if it helps. as long as you can enter fastboot /recovery mode.

I uninstalled the USB driver, reboot and now the computer recognizes the device, but I have a new problem:
https://imgur.com/a/IetkC
From the command line i got this:
https://imgur.com/a/65Dtn
How to proceed?

moralshixch said:
I uninstalled the USB driver, reboot and now the computer recognizes the device, but I have a new problem:
https://imgur.com/a/IetkC
From the command line i got this:
https://imgur.com/a/65Dtn
How to proceed?
Click to expand...
Click to collapse
Judging from the first picture, the bootloader isn't unlocked. "Erase boot failed" results most likely from a locked bootloader. Go unlock your bootloader, if you haven't done so already. The MiFlash stuff should work after that. Also, with an unlocked bootloader you might as well flash TWRP, boot into it and format data, and use its MTP capability to transfer a custom ROM onto the device and then flash it. Hope that this can help, good luck :good:

GrenadeofTacos said:
Judging from the first picture, the bootloader isn't unlocked. "Erase boot failed" results most likely from a locked bootloader. Go unlock your bootloader, if you haven't done so already. The MiFlash stuff should work after that. Also, with an unlocked bootloader you might as well flash TWRP, boot into it and format data, and use its MTP capability to transfer a custom ROM onto the device and then flash it. Hope that this can help, good luck :good:
Click to expand...
Click to collapse
Miflash will work with locked bootloader no problem.
2nd image shows its the wrong image...

problem with fastboot twrp flashing

my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.

Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
try upgrade your android sdk on your pc

Nazukii said:
my device came with unlocked bootloader, so I tried to flash twrp but every time i type "fastboot flash recovery C:\adb\twrp-3.2.1-3-whyred.img" and hit enter, the device seems to disconnect from pc and there is "press any key to reboot" in fastboot on my phone.
How can I solve this issue?`
Phone gets detected by adb/fastboot tool so its not a driver problem. I tried different cables and usb ports aswell.
Firmware is latest global stable.
Click to expand...
Click to collapse
Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful

i am trying to flash twrp there is no folder called adb i have installed the 15 second adb and all so i have got this minimal adb flashboot and i tried with that and got this ---- FAILED (remote: Flashing is not allowed in Lock State). i have granted all usb and oem unlocking. please help with this

Phone shows unlocked during the boot?
I had the same Problem,after a Factory Reset works for me.
I am on Miglobe-Rom Miui10 8.6.28.
Minimal ADB is enough.
Or use this from Attachment.
Unpack with Win.zip and copy Twrp in this Folder.
Conect the Phone with your Pc ,boot into Bootloader and click "cmd-here.exe"
Use this Command
fastboot flash recovery twrp-3.2.1-3-whyred.img

@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J

gamebenchjake said:
@Nazukii - Quick question - any chance you could try running GameBench on your device, and see if our background service dies when the device is disconnected from the PC? I don't have a Note 5 Pro to test, and I've got some user complaints. Any assistance would be awesome!
J
Click to expand...
Click to collapse
Have you fixed your app to run on Magisk-SU ?

otonieru said:
Have you fixed your app to run on Magisk-SU ?
Click to expand...
Click to collapse
Hey Otonieru,
Not yet, but I've got one of the engineers working on it - hopefully it'll be up in the next 30 days or so

Same problem here after updating my gcam was not working was enabling hall again but it is not booting into twrp

Redmi Note 5 pro
So my Bootloader is locked,
My phone stuck in MI recovery idk how.
I cant install MIUI via fastboot. Im stuck ..
Can anyone please help me here not sure how to proceed further.

If you have made sure that you have all the drivers installed and still have not solved, you need to use an Intel-based PC / notebook and use a usb 2.0.

”Well if you already had adb in your pc, rename the twrp file to recovery, you don't have to move the twrp from download folder, open download folder press shift and right click then select open cmd here, on cmd type "adb device" to see if your device connected, then after that type this "fastboot flash recovery recovery.img" press enter than after that type "fastboot boot recovery.img" TEAMWIN logo should appear on your device and then you can unplug your device. Hope this useful”
i did that but it is showing failed（too many links）and "press any key to reboot" showing on my phone's fastboot screen

Fastboot boot recovery.img flashing problem on Redmi note 5 pro
My bootloader is unlocked and my oem as well as usb deb is on. After i connect my phone in fastboot mode to my pc. The cmd shows fastboot devices but when it comes to fastboot boot recovery.img flashing device get disconnected. Plzzzzzz let me know a solution for this. A solution for this will be highly appreciateable.

Flashing using MI Flash got stuck

Hello,
I'm using Redmi Note 5 pro. Recently my device went on boot loop. Whenever I tried to restart, it was showing MI Logo for long time, nothing happens. I'm not able to enter into recovery mode as well (Vol Up + Power). But I can go to Fastboot mode (Vol down + power key).
Mine is not bootloader unlocked and I dont think I have enabled OEM Unlocking from the settings.
I tried downloading the ROM from below URL (Rom for Fastboot flash) -> whyred_global_images_V11.0.3.0.PEIMIXM_20191108.0000.00_9.0_global
http://c.mi.com/in/miuidownload/detail?guide=2
http://update.miui.com/updates/v1/fullromdownload.php?d=whyred_global&b=F&r=global&n=
When I check, whether the fastboot devices is showing mine or not, I can see my device listed
In another forum, I can across this, before flashing using MiFlash, they asked to download the Edl.cmd file from the below link and run it. I did that as well.
https://forum.xda-developers.com/an.../guide-how-to-reboot-to-edl-fastboot-t3394292
After that, when I select the downloaded ROM, and try to flash it with MiFlash (v2019.12.6.0), it keep showing the below line. but its not getting errored out. progress bar keeps going till the end but it stays with the below status. Attached the screenshot as well.
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *whyred" || echo Missmatching image and device
Any help with will be much helpful! Thanks in advance!

I think flashing via fastboot on unlocked bootloader is not possible

Hi, you mean locked bootloader is not possible?
If yes, is there a way to fix the phone?
Thanks in advance!

karthik623521 said:
Hi, you mean locked bootloader is not possible?
If yes, is there a way to fix the phone?
Thanks in advance!
Click to expand...
Click to collapse
The way i see is Edl flash mode (wait for a proper answer)

I accidentally locked my chinese whyred while flashing global rom using miflash.
The only thing that worked for me was EDL flash chinese rom using QFIL following the tutorial here: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I had to use chinese rom for 360 hours until I could unlock the bootloader again.
You need to flash the rom version that matches your device origin (global, china, india, russia, etc..)

tsarig said:
I accidentally locked my chinese whyred while flashing global rom using miflash.
The only thing that worked for me was EDL flash chinese rom using QFIL following the tutorial here: https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
I had to use chinese rom for 360 hours until I could unlock the bootloader again.
You need to flash the rom version that matches your device origin (global, china, india, russia, etc..)
Click to expand...
Click to collapse
Hello, Thanks for letting me know about this method. I tried this but I'm not able to find my devices showing in Device Manager as "qualcomm hs-usb qdloader 9008" (I'm trying with fastboot mode as am not able to go to Recovery mode)
I tried installing the Qualcomm QDLoader 9008 driver using the method shown in the below link
https://www.99mediasector.com/install-qualcomm-hs-usb-qdloader-9008-install/
1. tried direct installation of exe - didn't work)
2. there was manual method which asked me to reboot in edl mode using the command fastboot oem edl - but this shows error saying FAILED (remote: 'Device is already locked!')
//attached screenshot for reference
Thanks!

karthik623521 said:
Hello, Thanks for letting me know about this method. I tried this but I'm not able to find my devices showing in Device Manager as "qualcomm hs-usb qdloader 9008" (I'm trying with fastboot mode as am not able to go to Recovery mode)
I tried installing the Qualcomm QDLoader 9008 driver using the method shown in the below link
https://www.99mediasector.com/install-qualcomm-hs-usb-qdloader-9008-install/
1. tried direct installation of exe - didn't work)
2. there was manual method which asked me to reboot in edl mode using the command fastboot oem edl - but this shows error saying FAILED (remote: 'Device is already locked!')
//attached screenshot for reference
Thanks!
Click to expand...
Click to collapse
You're in fastboot. not EDL mode.
EDL Testpoint - https://youtu.be/dYVR5BgNwG0
Connect the usb cable to both phone and pc, disconnect the battery flex cable, short the two EDL testpoint, and connect the battery flex cable. it will take some practice.
Also, there is a limited time in EDL mode to start flashing, if you too late you will have to repeat again.
Use this tutorial https://youtu.be/ikGsxf_s-zw

It seems shorting pins and edl flashing is the only way for reviving ur phone pal
Good luck

Recovering data on a DEAD Redmi Note 8 PRO

Hello,
I hope this is the right section for this post.
I've been using a Note 8 Pro with zero issues until one week ago when I accidentally dropped the phone in the water.
After a few seconds submerged the display turned off and I felt an intense heat coming from the zone of the battery.
Having no chance to recover the phone (tried with Isopropyl Alcohol too) I decided to open it and manually dry/clean each component, having seen the situation inside gave me the phone is dead but I still want to recover some pictures/data from it.
Before opening the open Minitool was not detecting any device on my Windows Laptop, after cleaning each component Minitool is instead detecting the phone via USB, but I still can't extract any data because the "Usb debugging" option is not tuned on (and no the device is not rooted).
Is there any option to extract data from the phone? There's a way to turn on USB Debugging via ADB on a non-rooted phone?
Thanks,
Andrea.

how about trying your luck with a service ? most of the time they do have access to special programs, which have a better functionality than adb.

Thanks for the hint, but I am not happy with the idea of someone playing with my data

1. Try reboot phone to recovery
2. Connect it to your computer (download Platform-tools)
3. In the folder with Platform-tools open cmd
4. In cmd - adb shell
5. cd storage/emulated/0
6. ls
7. Now, using the commands, drag files from your phone to your PC

Thanks for your hint.
No luck so far, I think because the phone is not in recovery mode.
I can hear the phone starting up several times (hear the jingle) so I think it's in a reboot loop and I don't know how to boot it into recovery mode wo a working display (tried with power/volume up combination with no luck).
From the windows taskbar I can see that the phone is recognized for a few seconds before it restarts.
EDIT: trying to switch the phone on with the combination "power/volume down" brings to a kind of stable state and I can now see the phone in the windows taskbar recognized as a generic "android device". Still no luck when trying to access the phone as there's no device in windows and no device obtained through "adb devices" command.
EDIT1: I think that the phone is in "FASTBOOT" mode. If I type "fastboot devices" I can see it detected but still can't access it.

Any idea? Should I give up?

If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info

Yes it's popping up and down when it's booted in recovery mode whilst is stably connected when in fastboot mode but in this case I can't access the internal memory of the device.
I didn't get the purpose of logging the devices connecting to the USB as I can see the device connected for a while and correctly recognized as Redmi Note 8 pro but as it keeps popping out windows have no time to show it's folder.
As for the code you wrote: i will try asap but already tried with "fastboot devices" and I get the phone correctly listed but still can't access its memory as told.

Renate said:
If it's popping up and down you need something to keep track.
You can try my UsbLog.exe (in the sig), it just sits there and shows what devices appear (if they have a driver) and disappear.
Try these to see if anything is working:
Code:
C:\>fastboot devices
C:\>fastboot getvar all
C:\>fastboot oem device-info
Click to expand...
Click to collapse
After rebooting the phone in fastboot mode I can see it recognized as a generic android device from windows (still can't access the storage folder of the device).
fastboot devices----> I get the device listed with a series of numbers/letters
fastboot getvar all---> I get a list of information on token/token version/partition type and size/baseband/bootloader etc.
fastboot oem device-info----> FAILED (remote: unknown command)
So I think it's clear that the device is in Fastboot mode and instead is in a boot loop when started in revocery mode.
Is there a way to extract data from fastboot mode?
Thanks,
Andrea.

If you put a custom recovery on it in the first place you can try reflashing recovery from fastboot.
Fastboot doesn't allow you to read anything.
oem device-info is obviously an oem command that might not be on any device.
You've got a Mediatek processor. That has some low level equivalent to Qualcomm EDL, but I have no experience with that.
If you can get there you can download the user data partition, but it's probably encrypted. Also no experience with that.
The easiest is if you can get the system to mount/decrypt the partition.
You've tried the normal system too?
Is this A/B? Have you tried changing slots?
How much time does it stay up in recovery? Do you have ADB? Maybe try:
Code:
# stop recovery
Does that prevent it from looping?

So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?

Sephiroth79 said:
So I should try to flash a custom recovery like TWRP for example?
What you mean with "normal system too"?
Changing slots you mean changing usb port?
It stays in recovery less than one second so I can't give any command via ADB.
EDIT: cant' flash any custom recovery because the bootloader is locked.
If I Try to unlock the bootloader via MiUnlock I get a warning saying that all data will be erased.
Any idea on how to unlock the bootloader wo wiping all the data?
Click to expand...
Click to collapse
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons

MysticNoOb said:
There is a mediatek bootloader unlocked you just have to boot in Brom mode and it'll unlock it please follow this
PS: press all buttons
Click to expand...
Click to collapse
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?

You really want to boot the normal system because that's the best way to get decrypted data.
I realized that you don't have ADB enabled there.
You should look at B. Kerler's https://github.com/bkerler/mtkclient/
If you can pull the boot image off your device then I might be able to fix it so that you have ADB.
You'd have to flash it back in fastboot or mtkclient.
You can also pull a copy of userdata off the device with mtkclient.
As far as booting into recovery, there's a way.
Here's how, if you don't have A/B (that is you flashed TWRP into recovery and not recovery_a or recovery_b)
then you can fastboot flash a special file into the misc partition and it wil boot into recovery next reboot.
To return things to normal you have to flash the empty file to the misc partition.
Code:
C:\>fastboot flash misc misc-rec.img
C:\>fastboot reboot
Only do this if you don't have partitions that end in _a or _b

I really don't know if I have partitions A and B as you mentioned and I think there's no way to check actually.
I confirm I don't have "USB Debugging" active on the phone.
So if I understand correctly I should do the following:
- Flash misc-reg.img via Fastboot
- Boot into recovery just rebooting the system after flashing the above file;
- use MTKclient to dump userdata or boot image to enable ADB on (I will need help with mtkclient I suppose).
Is it correct?
EDIT: flashed TWRP first and misc-rec then rebooted via Fastboot/Reboot but nothing happens.

Sephiroth79 said:
My bootloader is unlocked!
Thank you very much.
Now I am going to try to flash a custom recovery mode via fastboot in order to access the internal memory of the phone.
EDIT: I've just flashed twrp-3.6.2_9-0-begonia.img but still can't boot into recovery mode.
Any hint on how to extract data from the system now?
Click to expand...
Click to collapse
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.

Kirasu2080 said:
TWRP cant boot because you used wrong one. Search again in that unlock bootloader channel and use suitable one.
Click to expand...
Click to collapse
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?

Sephiroth79 said:
Hmmm, I am almost sure that the TWRP I've flashed was listed under Redmi Note 8 pro page. Can you please indicate more precisely where should I sera
EDIT: I think I've downloaded and flashed the correct TWRP file.
@Renate can you please detail your method so I can try to extract data from the phone?
Click to expand...
Click to collapse
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.

Kirasu2080 said:
1/Yeah it's official. You "flashed correct TWRP." Downgrade to Miui Android 9 (_9 in it's name) to boot into that TWRP and lose your data.
2/In unlock bootloader video above, search other video in his channel playlist and find TWRP video suitable for your Miui version.
Click to expand...
Click to collapse
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?

Sephiroth79 said:
Can't find the right video, can you kindly send me a link (I am on the latest Miui version and I am in Europe)?
In all the videos I've seen on his page he is using the device to install TWRP etc.
I think I just need the correct TWRP version for my MIUI release and then I'll flash TWRP and misc-reg.img. Is it right?
Click to expand...
Click to collapse
Use brp 3.5.2 v3.1 or V3.6 to decrypt Miui 12.5