I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Paris6906 said:
I started to root my phone this morning. I did the HTVDev unlock, flashed twrp, then tried to flash viperboy's disable RW system protect. This caused my phone to just hang at the HTC screen. I let my phone die and was able to get into my bootloader and fastboot. I tried to push the rom via adb but I kept getting the error of no device connected. Then i tried to flash the stock boot.img though fastboot. This brought me back to the HTC screen but now when I plug it in to my computer it shows up for everything and it installs drivers but the HTC MTP Device fails. Now I cant send commands to reboot through fastboot or adb. Im currently waiting for it to die again to get back to twrp or the bootloader. Any advice on how to proceed?
Thanks,
Paris6906
Click to expand...
Click to collapse
Likely no need to let it die -- a hard reset (hold the power and vol down for a very long time) should bring you back to the bootloader (hopefully). It'll seem like a good long while -- keep pressing.
From there, select 'fastboot' and press the power button, then plug in to your computer (USB). That'll show USB on the fastboot line.
Then, on your computer, open a command window (presuming you're using Windows) in the SDK platform-tools directory and type:
fastboot devices
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
Then, reboot into recovery.
Your kernel (boot.img) apparently is garbage, so hopefully you can either put a ROM on USB and flash from that (OTG) or adb sideload it. All the ROMs normally have a good kernel so would flash your boot.img properly during install. Were me me, I'd flash O.M.J's stock rooted ROM just so you at least get back to some place of sanity).
If that all fails, you might have to RUU and start over.
Let us know and we'll help out.
If that gives back your device ID, you're at least at a reasonable fastboot. I'd flash a good recovery (I use PhilZ, and while it might be foreign to you (CWM style), it lets you load a ROM via OTG cable over USB if you have such a cable -- if not, hopefully sideload works for you in TWRP if you stick with that) -- just to be sure you have a good recovery.
ok. can you use adb push in fastboot? also i noticed that my captive buttons blink when i tried to turn off my phone. don't know if that means anything.
OMG it worked! Thank you so much. I uber appreciate it. Today I learned a ton about how android works and how to use adb and fastboot. While the processed about gave me a heart attack i did learn a lot. I can not believe how great of a resource xda is. The knowledge of everyone on here is incredible. I cant thank you enough.
Thanks all,
Paris6906
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
08G8V8 said:
Hoping somebody can help me figure out what is going on with my phone. Sorry for the long post, but hoping folks with custom rom and flashing experience will read on to help.
I have the Verizon Developer Edition. I have unlocked the bootloader, installed TWRP 2.7, and rooted the phone. I have never installed any custom ROMs on the phone. I had done custom ROMs on my GS3, but I just wanted this phone rooted, and maybe mess around with a few ROMs down the road.
I followed this video from RootJunky when I originally installed TWRP.
So a few weeks ago I kept getting the OTA message to upgrade to the latest kitkat. I decided to flash back to the original recovery so I could do the upgrade. I contacted RootJunky on his youtube channel and he provided a link to the stock recovery and I flashed it using the same video and his linked file.
After flashing the stock recovery, when I was in bootloader mode, I scrolled down to "recovery" and selected it. It would not go into recovery. It just stays in a bootloop. I went back and forth with RootJunky a few times trying to resolve this, but I got no response to my last few comments.
I can get the phone back into bootloader mode by holding the volume up/dwn and power buttons, if I time it correctly during the bootloop. When in bootloader mode, I can select "Normal Powerup" option and the phone will boot up and function properly. But, if I shut the phone down, I can't turn the device on with the power button, otherwise it will just bootloop. I have to get into bootloader mode, then select "Normal Powerup" to get the phone to work.
Once back in the phone, my USB debugging option is unchecked. I can recheck it, open a command prompt, and do a "adb devices" and it shows it connected. But if I do a "adb reboot bootloader" from the command prompt it will bootloop.
When I get into bootloader mode manually, when I connect it to the computer, and do a "adb devices", it doesn't show as connected, as I think the USB debugging option is getting toggled off somehow, so I can't connect or flash anything to the phone at this point.
One thing I see, in the video @ 4:50, he says you need to be at "status code 1" to flash recoveries. I am/was at status code 3. Not sure if that is why I am having this issue, or how to get this changed.
Any help would be greatly appreciated. I can use the phone just fine, but at this point, I would just like to be able to do a full restore to stock, upgrade to 4.4.4, keep the unlocked bootloader, and root the phone. No custom ROM.
THANKS!
Click to expand...
Click to collapse
First, Status code 3 is normal - that indicates an unlocked bootloader.
You should be able to use the 4.4.4 FXZ to flash back to 100% stock. Afterwards, you can flash TWRP, and re-root. Use the latest TWRP from here: http://techerrata.com/browse/twrp2/ghost
The important thing about TWRP is that immediately after flashing it, you have to "fastboot reboot-bootloader" and immediately boot into recovery - otherwise it doesn't 'stick'. We don't know why, but as long as you do it that way, you will be fine.
Here is the link for the 4.4.4 FXZ: http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
If you follow the instructions, you will be on stock, rooted 4.4.4 in less than 20 minutes.
Good Luck, and let me know if you need additional assistance :good:
Also, please remember to post your questions to Q&A - not General. Don't worry as I have already requested that the Mods move it to the appropriate sub-forum.
EDIT: The problem I see with "rootjunky"s video is that first, he advises that "Status code 1" is required to flash recovery -- this is incorrect. Status code 3 works fine for custom recovery.
Additionally, he did not "fastboot reboot-bootloader" before booting into recovery. This is necessary. I'm not sure why he left that step out....likely he already had custom recovery flashed when he made the video.
Thanks for the quick response. Sorry about posting in the wrong section. I should have known better.....
I will look at this, but probably won't do it until after work tomorrow. I will post back tomorrow, hopefully with success.
Thanks!
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
08G8V8 said:
I saw your edit to your post. I did the reboot boot loader step when I originally flashed twrp. I can't remember where I saw it, but I remember reading it and doing it.
The phone was running fine with twrp installed for a few months. The problem I am having now happened after flashing the stock recovery back onto the phone.
Do you recommend the RSD Flasher or House of Moto method to flash this FXZ?
Click to expand...
Click to collapse
Either will work fine. If you don't care about keeping your data, you can use RSD Lite (will wipe everything). If you use one of the tools in the thread I linked you to, make absolutely sure you follow the instructions -- you can't have any spaces in any folder-names. If you use RSD Lite, you just select the zip file and flash (no worries about directory structure).
Ok, I just assumed those were the methods to flash it. I will look into the RSD Lite method, as if don't mind wiping the data.
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
08G8V8 said:
I just watched a quick video on YouTube about using RSD Lite, and they state you must reboot the boot loader and do the flash in fastboot. I can't reboot into the bootloader from the command prompt, as it goes into the boot loop. I can get into fastboot manually, but when connecting to the computer it doesn't recognize it since the USB debugging option keeps getting reset on me.
Am I missing something? I don't see how I can flash this.
Click to expand...
Click to collapse
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
samwathegreat said:
So you are telling me that when you type "adb reboot bootloader" (if usb debugging is enabled) or "fastboot reboot-bootloader" (if usb debugging is not enabled) it doesn't take you to the "AP Fastboot Mode" screen?
Click to expand...
Click to collapse
Sorry, the "adb reboot bootloader" sends me into the bootloop.
I hadn't tried the "fastboot reboot bootloader" or "fastboot reboot-bootloader". Now when I try that, with USB debugging checked I just get "<waiting for device>" It does nothing.
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Travisdroidx2 said:
What about turning off the device. Then holding power button and volume down at the same time. Does it take you to the bootloader screen like it should?
Click to expand...
Click to collapse
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
08G8V8 said:
Yes, I can manually get into bootloader, but it keeps toggling my USB debugging option, so when I connect it to the computer, it doesn't see it.
Click to expand...
Click to collapse
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Once you are in the boot loader screen does "fastboot devices" recognize your device?
samwathegreat said:
It sounds to me like when you were attempting you flash your stock recovery back, you flashed it to the wrong partition. I've seen another member do this....
He accidentally typed "fastboot flash bootloader stockrecoveryfile.img"
That would cause the issues you are describing... I might have a way to fix it if you are currently still rooted and able to access adb...
Click to expand...
Click to collapse
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
samwathegreat said:
USB debugging isn't used in the bootloader, and adb isn't used for fastboot mode... I'm very confused by what you are saying...
Click to expand...
Click to collapse
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Travisdroidx2 said:
Once you are in the boot loader screen does "fastboot devices" recognize your device?
Click to expand...
Click to collapse
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
08G8V8 said:
No, I typed "fastboot flash recovery stockrecoveryfile.img"
I did just like originally when flashing TWRP, just replaced the file in the command line.
I am still rooted.
I can get into fastboot with the phone powered off, holding the volume UP/DWN and PWR. But when connected to the computer it isn't recognized.
Sorry, but I am confused as well. I am just going off what I have seen in RootJunky's videos. In this video, https://www.youtube.com/watch?v=1LkuLb8hV6Q#t=285 at 4:44, after he does the "adb reboot bootloader" he says the device is now in "bootloader mode" which is what I am talking about, but I guess is actually Fastboot Mode. This is the same mode I am talking about getting into from the device powered off holding the volume UP/DWN and PWR buttons, but going in this way doesn't get recognized by the computer.
Click to expand...
Click to collapse
OK, glad you didn't flash to bootloader. That is tricky to fix...but I've dealt with people who have done it before.
Try another PC...or re-install the drivers. Also, DO NOT use a usb 3.0 port, always use 2.0.
Bootloader = AP fastboot mode. They are one and the same. Try to get it recognized with "fastboot devices", on any PC. If you can get to that point, you can flash back to stock and recover everything. The FXZ can actually FIX a corrupted or damaged filesystem. It replaces all the relevant partitions.
Remember you do NOT use adb or usb debugging. They have nothing to do with fastboot.
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
08G8V8 said:
YES it does! Thanks. I kept trying "adb devices", and when it wasn't recognizing it, I figured it wasn't connected. I wasn't doing "fastboot devices". But, my USB debugging still was getting unchecked after getting back into the phone.
So with it recognizing my device in fastboot mode I should be able to go ahead with the RSD Lite flashing?
Click to expand...
Click to collapse
YES!!!!
It seems you were confusing adb and fastboot. As long as "fastboot devices" recognizes your device, SO WILL RSD LITE!!!
Now follow my initial instrucitons, and you will be up and running in no time...
Thanks guys! I am going to do this tomorrow, but I feel pretty good that it is going to work.
Yes, I got VERY confused, and definitely need to go study up some more. I thought I had it, but obviously not.
Will report back tomorrow.
Happy to help
Absolutely get the Dev Edition for the same price. While Safestrap is out for other Galaxy devices with locked bootloaders (not sure if the S5 got SS yet) it allows customs Roms....but not kernel changes. With a Dev edition, there may be less development, but I'm sure there will still be some development out there.
Hi all,
A few years ago (well when the devices has pretty much just come out), I ran a mod which i found on the XDA website that allowed me to root my partners Xperia T (LT30P),
Everything has been fine until recently, where I've wanted to upgrade the ROM on the phone, but this is where i'm having some major problems.!
Essentially I cant get the phone to boot into either Flash mode (green LED) or Fastboot mode (Blue LED). I've tried the volume down and then connecting the USB cable to my PC (on which the correct drivers are installed via Flashtool). and also the volume up for Fastboot. Neither work. Unsure if the phone has an unlocked bootloader or if that matters (im a Samsung man and used to working with that, so all the Xperia modding is totally new to me... :/
So far ive tried the following:
-Volume down key and plugging into USB port - Result: Phone remains switched off.
-Volume up key pressed in and then plugging into USB port. - Result: Phone remains switched off
-Enabled USB debugging and attempted to boot the phone into flash mode via ADB (Flashtool option). Phone simply reboots.
-Attempted inbuilt software update - Update downloads, but fails at 25% approx when it reboots and attempts the install.
-PC companion equally unsuccessful on my PC, as cant enable flash mode.
I'm totally at a loss at how to flash a fresh complete build (using a ftf file) to the phone without access to flash mode or fastboot mode. Anyone got any idea or know of any tools that might allow me to to completely rebuild the phone so all partitions are present and correct?
One idea i had was to flash a recovery to the phone using FlashR or alike, but cant seem to get it to work either. Flashr looks to install the twrp recovery, but when i attempt to reboot into recovery via Flashr or Rom Manager (another tool i use but not sure if useable on xperia phones?), the phone simply reboots. SOunds like a damaged or wiped partition perhaps?
Anyhoo , any ideas would be welcome guys! Too good a phone to just leave in the drawer
Cheers
Craig.
Cant you flash a boot.img (maybe from cm11 or something) with inbuilt recovery? You can use this for flashing
Ok, I've started writing this reply and lost everything near the end, started freaking out, calmed down and decided to do it again, cause I know what it's like to have a phone that's not behaving as it should. So here goes the shorter-ish version cause I really can't type everything again...
Make sure your volume buttons are working at all (I mean when the phone is booted). They work? good, procced. They don't? we can bypass that, but you, should get them fixed.
Got to this thread and download the latest build of the ROM http://forum.xda-developers.com/xperia-t-v/orig-development/rom-cyanogenmod-12-neo-s-homebuilds-t2984988
Extract the boot.img file from the zip and copy it to the root of your external micro sdcard, NOT IN A FOLDER. If you don't have an sdcard, put in on the internal storage, again, not in a folder.
Root your phone if you haven't. There are plenty of threads on that here on xda
Download an app called Terminal Emulator from the Play Store
Open the app and type su into the prompt.
Grant the app superuser/root access
The following step is the dangerous one where you can seriously break your phone forever. I'm not responsible for anything you mess up. You alone chose to do this
Run the following command in the terminal (be sure that the $ at the end of the line changed to a # (That means you're in root shell, but it's not important))
If you don't have an external sdcard type sdcard0 instead of sdcard1
Code:
dd if=/storage/sdcard1/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/Kernel
Connect the phone to a PC with fastboot drivers installed
Next execute this command and your phone should now boot into fastboot
Code:
reboot bootloader
If a blue LED lights up, you can happily continue flashing kernels and ROMs, if not report back and I'll see if I can help you
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
crstephenson said:
Cheers gents. Going to give this a shot tonight. I read last night that some builds out there where you cannot unlock the bootloader (which you can check via service menu)? Is that now bypassable?
Click to expand...
Click to collapse
No and it probably never will be. It's hardcoded on the chip. If your phone is bought with a contract binding or it's limited to a single provider, then chances are that you will never be able to unlock the bootloader and flash kernels. It could be that you not being able to get into fastboot is because it's restricted on the device itself [citation needed]. In that case you're screwed and can pretty much forget the whole custom kernel thing. Only ROMs for locked bootloaders
Hi there,
This is for EVA-L09.
How this came about:
I was relocking my bootloader when it failed(fastboot changed to locked though) however, continued onto reboot anyway. It didnt reach the EMUI lowlevel wipe stage
Device info:
EVA-L09
Nougat
C432 B391 (If I remember correctly)
FRP unlocked
bootloader ???
phone functionality:
whenever it turns on I just get huawei logo regardless of key combos
seemingly unable to fastboot
Unable to force update (Vol +&- & Power)
Unable to recovery mode
I was wondering if anyone has had a similar situation or any insight how to fix this.
Most solutions I've found require fastboot but once my device starts charging the logo appears then only restarting by holding power is available.
I expect the cause to be the issue relocking the bootloader.
thanks for any insight.
Edit/Notes: I have sucessfully unbricked this device before via the dload method however unable to. (rollback to 4.1EMUI and 6.0 then changed to C432 B168 and upgraded from there)
I do have a DC Pheonix account on standby if I ever can fastboot
LuxrayElite said:
Hi there,
This is for EVA-L09.
How this came about:
I was relocking my bootloader when it failed(fastboot changed to locked though) however, continued onto reboot anyway. It didnt reach the EMUI lowlevel wipe stage
Device info:
EVA-L09
Nougat
C432 B391 (If I remember correctly)
FRP unlocked
bootloader ???
phone functionality:
whenever it turns on I just get huawei logo regardless of key combos
seemingly unable to fastboot
Unable to force update (Vol +&- & Power)
Unable to recovery mode
I was wondering if anyone has had a similar situation or any insight how to fix this.
Most solutions I've found require fastboot but once my device starts charging the logo appears then only restarting by holding power is available.
I expect the cause to be the issue relocking the bootloader.
thanks for any insight.
Edit/Notes: I have sucessfully unbricked this device before via the dload method however unable to. (rollback to 4.1EMUI and 6.0 then changed to C432 B168 and upgraded from there)
I do have a DC Pheonix account on standby if I ever can fastboot
Click to expand...
Click to collapse
As you say, you cannot go to Fastboot even by power off, Vol- and connecting USB?
It doesn't help now but when you were relocking (btw why, but you may had your reasons for), did you have clean stock without root and TWRP (since relocking ininitates full reset)?
TG, I never used DC Phoenix but maybe you can unbrick by Method 3 (seems, it does not rely on Fastboot?):
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
sometimes people do mistake trying to boot in fastboot while are not conected to pc, connect phone and pc with usb, then try to force restart holding power more than 30 sec together with vol -. If cable are not connected, you never will boot in fastboot and find a way to test if your usb cable working properly!! i bought one non-huawei cable, it was new, but with that cable i wasnt able to boot in fastboot, duno why, so there need to be original cable for this! (maybe i bought foulty cable, duno , with non-huawi cable i can easy charge, transfer data to pc, but when tried to use adb comands, sometime it worked, sometime not, but with original cable got no problems at all)
Thank you for both of your comments. I have now successfully recovered via DC-Phoenix.
I was just getting unlucky with holding down the Vol - key it seems as I eventually got into fastboot which then allowed DC-PHOENIX to solve the problem.
The Huawei wire which I bought is third party and I have noticed connection dropping which may have caused me to not enter fastboot as it had unconnected(but not visibly). This happens during normal system boot as well when I'm trying to use MTP.
SOLVED
Hi there.
I had my couple's mobile rooted with Magisk and MIUI Global 10.3. Once wanted to update twrp and the issues began. Actually the mobile isn't rooted but with unlocked bootloader, apparently.
I list the issues down below:
1) Trying to install twrp with fastboot by CMD, pressing enter after the command the cursor just blinks and nothing happens. At first it showed "waiting for device", so I installed adb drivers and the mobile appeared in Device Manager. It run once up to "sending 'recovery'" but not farther. The mobile was connected in fastboot mode indeed as well as in usb debugging but couldn't activate oem unlock as it stated it as unlocked and the option was dimmed.
2) Tried to unlock the mobile with Miflash_unlock and the phone was recognized, but the tool checked the device up to 50% and then showed that it Couldn't verify the device.
3) Then I tried to make a backup of the user data and doing a Hard Reset from settings. It went forward up to reboot, so I did, then it entered in fastboot mode for a few seconds and it powered off. Rebooted the phone and it was up and running as if nothing happened. So I cannot make a hard reset.
4) I can't enter the recovery too. If pressing volume - and power on it enters in fastboot mode. With volume + and power on it does the same With recovery enter tools isn't possible either. It seems as it's been corrupted.
5) I've just tried to flash the Global_8.0 rom with MiFlash 2019.12.6.0 and on the progress line it says "echo Mismatching image and device" How? I'm sure its a Mi Mix 2 'chiron' Rom, so... Anyway, I start to flash and the tool seems to progress but it never ends. So I disconnect the phone, reboot, and it keeps untouched running as before, OMG
6) On top of that I can't update android by OTA, as it gets downloaded, then reboot, then enters fastboot mode and after few seconds it powers off as before, and powering it on afterwards shows that it couldn't be updated
So I don't know what to do next. However, the mobile runs apparently ok.
May someone lend me a hand, please?
Thank you.
SOLVED: The Xiaomi Mi MIX 2 is up and running with the last firmware installed. The issue was that, as I build a new PC lately, I connected the phone in fastboot mode to the front USB ports, which are 3.0 version, and you need a 2.0 USB port at most, causing errors in MiUnlock and MiFlash.