Related
Hi all,
I have problem, cant install twrp recovery via minimal adb&fastboot commands. Getting error
.Phone unlocked. Adb devices command showing device connected, i can use fastboot reboot bootloader, and that all. Other commands geting failed.
I tryed many times and olders twrp files, but same problem. Plz guys help me fix it.
Unlock bootloader even if its unlocked.
Flashing command : fastboot flash recovery recovery.img
gm007 said:
Unlock bootloader even if its unlocked.
Flashing command : fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Look what i get after trying unlock bootloader again, and second when try install twrp recovery.img.
Why don't you use srk tools to unlock and install the recovery.
gm007 said:
Why don't you use srk tools to unlock and install the recovery.
Click to expand...
Click to collapse
Becouse i get same problem like with minaml adb&fastboot program. Its sames cmd commands what diffrent ?
r4ason said:
Becouse i get same problem like with minaml adb&fastboot program. Its sames cmd commands what diffrent ?
Click to expand...
Click to collapse
Relock bootloader and unlock again.
What did you do to your phone.
gm007 said:
Relock bootloader and unlock again.
What did you do to your phone.
Click to expand...
Click to collapse
Already tryed. Nothing, same error. Since in phone was NXT-L29C432B320 firmware. I searched in internet its able to update to nougat. L29C432B521(beta).
I used dload method and phone get bricked. After that tryed rollback software to all older versions.And nothing, dload dont helped.
Next i writed to huawei custumservise and they gives me bootloader unlock code. I used it and succsesfull unlocked phone.
Next step was twrp revovery.img installed succsesfully.And worked fine.
Searched international custom rom for my device.And installed via twrp recovery without errors or faild. But in twrp meniu bellow i saw "os not installed"
After that phone restarted 2 times, and wont boot system. That twrp recovery disapier from phone. And until now im stuck here to find any soliution.
Yesturday i was tryed even dc unlocker pheonix program for 15€ and its not helped..
What you did with dc unlocker ,did you flash a rom?
gm007 said:
What you did with dc unlocker ,did you flash a rom?
Click to expand...
Click to collapse
With pheonix i tryed to install stock rom. Like in instruction by program.
Program installed ios, but phone wont restarted and booted to system. Nothing hapened.
r4ason said:
With pheonix i tryed to install stock rom. Like in instruction by program.
Program installed ios, but phone wont restarted and booted to system. Nothing hapened.
Click to expand...
Click to collapse
I used this https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
r4ason said:
With pheonix i tryed to install stock rom. Like in instruction by program.
Program installed ios, but phone wont restarted and booted to system. Nothing hapened.
Click to expand...
Click to collapse
Step 2
After performing steps in guide your phone should boot up
Then you need to repeat flashing, but now in upgrade mode
This step is necessary to fix incorrect internal storage size after flashing in fastboot
Did you use a official firmware or a firmware from dc unlocker?
gm007 said:
Did you use a official firmware or a firmware from dc unlocker?
Click to expand...
Click to collapse
Yes i used official firmware.
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:
Do you have the Verizon model?
samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03
spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.
The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?
I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?
What if fastboot boot twrpname.img
It's really weird anyway...
enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...
if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.
I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!
Hi everyone, I have the mha-l29 and successfully updated to the latest Oreo for the US version. I then unlocked the bootloader, flashed TWRP, flash Superuser and everything was working fine. I then got an error message while doing a backup in TWRP and foolishly edited a file which caused the system to not boot. I then Flashed the hwoa7 instead of 8 to fix it and now my phone is bricked. The only thing I can do is get into fastboot. Everything else throws an error. Is ee a func no: 11 error. Please see attached pictures. Please let me know how I can fix it. I've already tried reflashing the ramdisk as well as TWRP bet I can't boot into TWRP.
Thanks so much
C:\>fastboot oem lock-state info
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ 0.008s]
finished. total time: 0.012s
Do you mean you flashed RECOVERY_nocheck from Nougat to Recovery of Oreo?
If so you should only need to flash recovery_ramdisk.
I guess you could extract ramdisk, recovery_ramdisk and kernel and flash to the partitions of the same name.
See what error it gives after you flash back stock recovery_ramdisk
Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
saw this to late , TWRP caused this i had the same thing earlier and reinstalled different TWRP
seti007 said:
Thank you for your help ante. I ended up fixing it by using DC unlocker. That Basically got me to where I could boot into erecovery. It also allowed me to use ADB to flash TWRP. From there I just flashed the entire hwota8 package. I'm back up and running thankfully. Once again, I really appreciate you and people like you who help others on this forum.
Click to expand...
Click to collapse
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?
I was able to flash the entire update package using DC Unlocker. That should have gotten me up fully but it did not. Before using DC unlocker, I was not able to even boot into TW RP or erecovery. I was able to get into fastboot but could not install anything. I did not get any errors in ADB and installations were successful but I could not boot into TWRP. After using DC Unlocker, I went back into fastboot and used ADP to install TW RP. I was then able to boot into TW RP. So the difference that DC unlocker made was that it allowed me to use ADB to successfully install TWRP.
I had the very same issue previously with another device. It was running an old version of TWRP. Regardless of what I flashed, it would give errors, etc.
However, using ADB, I flashed the very latest recovery and voila! Flashed a rom successfully as well as other apps without any issues.
It's always best to use the latest possible recovery to avoid issues with flashing.
Glad you solved your problem
Wirmpolter said:
DC-Unlockr allowed you to use adb to flash twrp? How were you able to do that exactly?
Click to expand...
Click to collapse
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA
marktheripper said:
Good sir, can you link me to a working twrp? I tried several twrps, but i cant seem to boot into recovery. TIA
Click to expand...
Click to collapse
Were you running Android Nougat or Oreo? I've just used the TWRP's found here on the xda forums. However, I didn't use TWRP nor dc-unlockr to fix my issue. Have you tried the hardware button combo of volume up And power to boot into it?
Oreo. I tried using the twrps available, but i cant seem to boot into twrp. It goes directly to error mode. Im using the power + vol up btw.
Hi guys,
so after I got my xiaomi with a global ROM and wanted to update and that is when I accidentally relocked the bootloader. The version of ROM was invalid apparently and wouldn't let me boot and now I'm stuck in fastboot mode.
My problem is as follows:
-can't enter recovery, stuck at fastboot no matter how many times I try and reboot
-adb not working since I didn't enable it
-bootloader locked (miflash says so and it can't unlock it since I didn't check 'oem unlock enable' and I cannot boot ROM so I can't enable it)
-fastboot flashing says 'not allowed in lock state'
-edl mode not available
I've seen tutorials where people opened their phones to force the phone into edl mode via the testing points but is that the only way`?
Any suggestions on how I could unbrick it?
Much appreciated
yes, it is the only way.
koniv90 said:
Hi guys,
Any suggestions on how I could unbrick it?
Much appreciated
Click to expand...
Click to collapse
you can use this tool to flash the phone on fastboot mode
Xiaomi King Tool - Home.
xiaomikingtool.com
its cost you only 5 credit
Can you flash files by fastboot? if so, flash the global rom images one by one, then reboot
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
I need help please my phone redmi k50 gaming is no recovery and . bootloader is locked
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
This what I'm facing
Dims_Camper said:
yes, it is the only way.
Click to expand...
Click to collapse
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
kskksks said:
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
Click to expand...
Click to collapse
Nope, only very old devices.
NOSS8 said:
Nope, only very old devices.
Click to expand...
Click to collapse
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
kskksks said:
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
Click to expand...
Click to collapse
Have you tried to flash stock rom?
I mean, if you have Chinese rom before, just flash with latest Chinese rom.
Ghanaba said:
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
Click to expand...
Click to collapse
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
jholfran3 said:
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
Click to expand...
Click to collapse
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
flashing is possible with modified firehose programmer (no auth factory loader) or with authorized xiaomi account. both solutions are paid service and cannot advertised here.
please -as always- read the thread you posted in. I can see useful information shared already. wait for other replies.
letsgofly said:
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
Click to expand...
Click to collapse
Hi, try to flash the .img files from the fastboot stock rom whit cdm in fastboot, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
example:
fastboot flash boot boot.img
fastboot flash cust cust.img
etc.
jholfran3 said:
Hi, try to flash the .img files from the fastboot stock rom, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
Click to expand...
Click to collapse
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
NOSS8 said:
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
Click to expand...
Click to collapse
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
jholfran3 said:
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
Click to expand...
Click to collapse
To install a recovery, the bootloader must be unlocked.
Solution: I hardbricked my device because of my dumbness. This device is not veux... It s viva. Be cautious my friends...
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies
turbotales said:
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies
Click to expand...
Click to collapse
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
NOSS8 said:
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
Click to expand...
Click to collapse
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?
turbotales said:
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?
Click to expand...
Click to collapse
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).
NOSS8 said:
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).
Click to expand...
Click to collapse
Tried doing this.. now it s hard bricked.
turbotales said:
Tried doing this.. now it s hard bricked.
Click to expand...
Click to collapse
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?
NOSS8 said:
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?
Click to expand...
Click to collapse
I tried flashing with Miflash didnt work,
Tried flashing with linux and said it is done, but now device does not open in any way. What should I do?
These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.
NOSS8 said:
These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.
Click to expand...
Click to collapse
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?
turbotales said:
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?
Click to expand...
Click to collapse
If you tried with Miflash post the log otherwise try and post the log.
Solved, I'm dumber than I thought. This phone is not veux. It's viva. If I were to re-check it I d not be in this position... Let this be a lesson to me. Going to have to take it to the service now.