No Fastboot, no Recovery, no Edl, - Xiaomi Redmi Note 3 Questions & Answers

Tengo un Xiaomi redmi note 3 pro que en el flasheo estaba en un 30% y me sale error espacio insuficiente, después de eso el miflash no me reconoce el dispositivo, ya no puedo entrar al fastboot ni al recovery ni al edl, tampoco enciende se queda con la pantalla negra y el led rojo parpadeando por un rato, le he desconectado la batería y el cable USB para ver si enciende con los dos botones de volumen mas el cable USB y no hace nada, no es asunto de controladores porque lo he instalado muchas veces a parte de que lo hice en varias computadoras y al probarlo con otros teléfonos si los ve pero este no, a ver si alguien me guía en esto.....
Mod edit - English translation added below:
I have a Xiaomi redmi note 3 Pro that flashing was 30% and I get error insufficient space, after that the miflash not recognize my device, I can not enter the fastboot or the recovery or the EDL, no lights are left with a black screen and the red lED flashes for a while, I've disconnected the battery and USB cable for lights with both volume buttons plus the USB cable and does nothing, is not a matter of drivers because I have often installed besides I did on several computers and test it with other phones if you see them but this is not, to see if anyone guide me on this .....
Enviado desde mi Mi-4c mediante Tapatalk

Only english pls. Your topic Will Be removed if not
Enviado desde mi Redmi Note 3 mediante Tapatalk

This is not the right section, it's dev not support.
Look like an hard-brick :
http://en.miui.com/thread-245347-1-1.html

I have a Xiaomi redmi note 3 Pro that flashing was 30% and I get error insufficient space, after that the miflash not recognize my device, I can not enter the fastboot or the recovery or the EDL, no lights are left with a black screen and the red lED flashes for a while, I've disconnected the battery and USB cable for lights with both volume buttons plus the USB cable and does nothing, is not a matter of drivers because I have often installed besides I did on several computers and test it with other phones if you see them but this is not, to see if anyone guide me on this .....
Enviado desde mi Mi-4c mediante Tapatalk

This is the same theme but in English
Enviado desde mi Mi-4c mediante Tapatalk

only english first
Now the problem is with mi flash tool you use
Use mi flash tool beta here is link
http://en.miui.com/thread-281979-1-1.html
And fasboot edl for reboot to edl from fastboot
http://forum.xda-developers.com/android/software-hacking/guide-how-to-reboot-to-edl-fastboot-t3394292
Either now your mobile fully discharge or may have battery
To reboot from edl to fastboot hold and press volume - and power button for 30 to 60 seconds it will reboot to fastboot mode and this use fastboot edl to boot in edl mode and flash the rom with new mi flash tool beta
As you said black screen and red led is blinking you are in edl mode use above methode to reboot and if not blinking recharge you phone i.e connect to charger to charge you battry because mobile battery is 0℅
Any help plz comments below

Already I have made this and several tutorials more and still with the same problem, have had that connect them two pin so miflash it recognize but at the time of flashing me gives always the same error: is has reached the end of the file. (0x80070026: Receiving hello packet.) And in Miflash vetoes me says: can not read from port COM 10
Enviado desde mi Mi-4c mediante Tapatalk

bravo07 said:
Already I have made this and several tutorials more and still with the same problem, have had that connect them two pin so miflash it recognize but at the time of flashing me gives always the same error: is has reached the end of the file. (0x80070026: Receiving hello packet.) And in Miflash vetoes me says: can not read from port COM 10
Enviado desde mi Mi-4c mediante Tapatalk
Click to expand...
Click to collapse
Sounds like you don't have the correct drivers.
Sent from my Redmi Note 3 using Tapatalk

Use testpoint methode
Sent from my Redmi Note 3 using Tapatalk

I have reinstalled the drivers and nothing
Enviado desde mi Mi-4c mediante Tapatalk

Exactly as is works in testpoint because if is with the keys of volume +-not me responds in nothing
Enviado desde mi Mi-4c mediante Tapatalk

what rom do you flash? (que rom flasheaste?)

Try to disable driver signature enforcement
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
Or if bootloader is unlocked install twrp and install full rom zip

About month ago i have same error. You need 64 bit windows (tested windows7 64 bit), conect your phone ONLY on rear usb port.
Sent from my Redmi Note 3 using Tapatalk

I had miui global 8 and I was installing the weekly 6.9.9 I have or had the bottloader officially unlocked
Enviado desde mi Mi-4c mediante Tapatalk

I currently have 10 Windows 64 bit, but the issue is that when I connect another Xiaomi all is normal and until I flashed, but with this nothing
Enviado desde mi Mi-4c mediante Tapatalk

I can not install the TWR because not connecting not see CMD when I enter the command says waiting for device, I've left all the time in the world and does nothing
Enviado desde mi Mi-4c mediante Tapatalk

Phone must be in fastboot mode, then instal twrp alka using command :
fastboot flash recovery twrp.img
Make sure you rename twrp to twrp.img
Then after succesfully, type in command prompt:
fastboot boot twrp.img
Your device will boot into twrp, and you can clean flash it.

But what happens is that not can enter or to the Recovery or to the fastboot, is as if the phone was in mode EDL but without respond and or to connect it, it light red only lights when it connect to the pc, the administrator of devices it recognizes but none of them Miflash not and when can connect them pin in my flash only me appears in name of the port COM not of the phone and therefore not is communicates me says that no can read the port
Enviado desde mi Mi-4c mediante Tapatalk

bravo07 said:
But what happens is that not can enter or to the Recovery or to the fastboot, is as if the phone was in mode EDL but without respond and or to connect it, it light red only lights when it connect to the pc, the administrator of devices it recognizes but none of them Miflash not and when can connect them pin in my flash only me appears in name of the port COM not of the phone and therefore not is communicates me says that no can read the port
Enviado desde mi Mi-4c mediante Tapatalk
Click to expand...
Click to collapse
Try to press & hold volume.down + power for 10 second or more, it will make your device boot to fastboot mode.

Related

Question about flashing with hardspl 1.22

I am really confused.
The last time I flashed my nike was almost a year ago, and now, since hardspl 1.22 I cant remember how to flash a new rom.
So, when I used spl 1.16, how I always do is the following: establish active sync connection, execute spl 1.16 on device, and then execute RUU.
So (by that time) I installed 1.22 and flashed an official ROM (no need of spl 1.16). But now, I'm trying flashing the same ROM (the lastest one, OEM PTG), establishing active sync and just executing RUU, but in the last step my device jumps to tri color boot (with USB information) and I get in my computer error in syncronizing.
Am I doing anything wrong?
I'm using Windows 7, wondering if that's problem (altought I can use Windows Mobile Device Center very well and with no problems).
Can you please help me?
Same problem here, might be a Win7 issue.
boa tarde Tiago, tive o mesmo problema aqui.
a solução foi a seguinte: despluga do usb, desliga o aparelho e liga com o botao da camera pressionado, vai entrar na tela tricolor, aí vc pluga e executa o customRUU.
pra mim funcionou.
qq coisa tamos aí.
Abraço.
1 - unplug from usb
2 - turn off the phone
3 - hold camera button and turn on the phone (will apear the three color screen)
4 - plug the usb cable again
5 - run customRUU
thanks
I am also using windows 7 and no problem.
I think need to install 1 more driver.
When connected on bootloader mode (three color) windows will ask for a driver.
Just let it search online. When it's done, then you can flash your phone.
Sorry for my bad english

I5500 brick

Help, I've installed with rom manager the wrong version of clock recovery, then I turned off my phone and it's dead
Recovery and download mode doesn't work..!! Odin can see it if I presso volume +, then Menu smartkey (first on left) and power botton but I can't flash Roms because odin hold on setup connection... How can I solve..? if odin can see the phone there must be a solution..!
Help please..
-------------------
Ho installato da rom manager la recovery e selezionato un modello sbagliato.. Poi ho spento il cel e non c'è verso di rianimarlo
Odin lo riconosce se premo tasto volume su + tasto funzioni + tasto accensione ma non va a buon fine il flash (si blocca su configurazione connessione)..
Recovery e download mode sono ko e nemmeno la ricarica USB funziona.. Cosa posso fare..? Ho provato a comprare su ebay un USB modificato per mandarlo in download mode.. Speriamo bene...
Ma possibile che se odin lo vede non posso farci nulla..?
Se lo mando in assistenza c'e speranza non se ne accorgano e la cosa passi in garanzia..?
Sent from my i9000 using Tapatalk
ribelle85 said:
Help, I've installed with rom manager the wrong version of clock recovery, then I turned off my phone and it's dead
Recovery and download mode doesn't work..!! Odin can see it if I presso volume +, then Menu smartkey (first on left) and power botton but I can't flash Roms because odin hold on setup connection... How can I solve..? if odin can see the phone there must be a solution..!
Help please..
-------------------
Ho installato da rom manager la recovery e selezionato un modello sbagliato.. Poi ho spento il cel e non c'è verso di rianimarlo
Odin lo riconosce se premo tasto volume su + tasto funzioni + tasto accensione ma non va a buon fine il flash (si blocca su configurazione connessione)..
Recovery e download mode sono ko e nemmeno la ricarica USB funziona.. Cosa posso fare..? Ho provato a comprare su ebay un USB modificato per mandarlo in download mode.. Speriamo bene...
Ma possibile che se odin lo vede non posso farci nulla..?
Se lo mando in assistenza c'e speranza non se ne accorgano e la cosa passi in garanzia..?
Sent from my i9000 using Tapatalk
Click to expand...
Click to collapse
the right download mode, the one you have to use with Odin is obtained by pressing Vol - / OK button /the bigger one at the center) / Power
try to use it after starting Odin to see if it recognized by it. Use Odin 4.2.8 with Europa 1.0.ops and ClockworkMod-Galaxy5-v0.5.tar file, no other one: for my personal experience, others ClockworkMod recovery versions (0.6, for example) don't work.. they just freeze on recovery.img download process!!
hope this could help you solving the problem, let me know!
- - - - - - - - - - - - -
Il Download mode che va usato con Odin si ottiene premendo Vol - / Tasto OK centrale / Power
usa questa sequenza con Odin 4.2.8, Europa 1.0.ops e come recovery solo e soltanto la ClockworkMod-Galaxy5-v0.5.tar, per la mia esperienza le successive versione della recovery non vanno: si bloccano durante il processo di sownlaod del recovery.img file (ma non succede nulla di irreparabile, basta riavviare e si può usare la versione precedente senza problemi)!!
spero che questo ti possa aiutare a risolvere il tuo problema, fammi sapere..
brainvision said:
the right download mode, the one you have to use with Odin is obtained by pressing Vol - / OK button /the bigger one at the center) / Power
try to use it after starting Odin to see if it recognized by it. Use Odin 4.2.8 with Europa 1.0.ops and ClockworkMod-Galaxy5-v0.5.tar file, no other one: for my personal experience, others ClockworkMod recovery versions (0.6, for example) don't work.. they just freeze on recovery.img download process!!
hope this could help you solving the problem, let me know!
- - - - - - - - - - - - -
Il Download mode che va usato con Odin si ottiene premendo Vol - / Tasto OK centrale / Power
usa questa sequenza con Odin 4.2.8, Europa 1.0.ops e come recovery solo e soltanto la ClockworkMod-Galaxy5-v0.5.tar, per la mia esperienza le successive versione della recovery non vanno: si bloccano durante il processo di sownlaod del recovery.img file (ma non succede nulla di irreparabile, basta riavviare e si può usare la versione precedente senza problemi)!!
spero che questo ti possa aiutare a risolvere il tuo problema, fammi sapere..
Click to expand...
Click to collapse
The download mode sequence doesn't work.. The display doesn't turn on..
Only with option key odin can see the phone
Sent from my i9000 using Tapatalk
WTF..
adb recognize it? did you try
Code:
adb reboot
or
Code:
adb recovery reboot
Searching the web I found a reply to a question very near yours (a user flash trough Odin but it use APBOOT for another phone):
Immettendo un file diverso su Odin hai scalibrato le linee di flash del dispositivo e di conseguenza alcune sue funzionalitá di utilizzo. Probabilmente a causa di ció la sequenza per entrare in dowload mode non va a buon fine. Consigliabile inviarlo in assistenza per capire se il problema puó essere risolto o meno tramite un intervento mirato al tuo caso........Il flash di qualunque Rom é un'operazione delicatissima e tante possono essere le cause che contribuiscono a poter rendere inutilizzabile il prodotto in questione.
Click to expand...
Click to collapse
Finally I found that, maybe you just read it.. http://forum.xda-developers.com/showpost.php?p=18795160&postcount=4
Tks mate tomorrow I'll try and let you know
Sent from my i9000 using Tapatalk
Can You tell Us which version did You pick?
brainvision said:
WTF..
adb recognize it? did you try
Code:
adb reboot
or
Code:
adb recovery reboot
Searching the web I found a reply to a question very near yours (a user flash trough Odin but it use APBOOT for another phone):
Finally I found that, maybe you just read it.. http://forum.xda-developers.com/showpost.php?p=18795160&postcount=4
Click to expand...
Click to collapse
In the control panel I see this:
http://dl.dropbox.com/u/23080338/pannellocontrollo.JPG
but when I launch the adb devices command the system doesn't recognize the device:
http://dl.dropbox.com/u/23080338/comando.JPG
Why???
ribelle85 said:
In the control panel I see this:
http://dl.dropbox.com/u/23080338/pannellocontrollo.JPG
but when I launch the adb devices command the system doesn't recognize the device:
http://dl.dropbox.com/u/23080338/comando.JPG
Why???
Click to expand...
Click to collapse
I think you have the same identical problem I run into when i installed the Android SDK (first time I did that by the zip archive): before all that, my laptop was able to recognized and connect to the Corby without problems.. I was able to use Odin and flash both CWM both stocks rom..
My troubles started when i decided to install the Android SDK: I installed the Java JDK, first of all, then i downloaded the zip version of the Android SDK: I unzipped into a folder and started the SDK Manager letting it install the 6 or 7 default packages it required..
After that I was not able anymore to successfully flash anything with Odin! I think that the problem is the USB Google driver, indeed!!
I try to uninstall the driver by unpicking it into the SDK Manager but it's still there.. and if I try to manually uninstall it by the Control Panel, at the next reboot it installs itself again and again!!
Just to be sure I install the Android SDK into an VirtualBox emulated machine but this time I don't install the USB driver and Odin stills work!!
So, I don't know what you can do into your PC to solve that, actually.. I'm still studying the problem but I usually don't use Windows so I quite forget it.. now I can run Odin into my Slackware, so..
What I can suggest you is to try with another PC or laptop, for now..
EDIT: I forget to say: obviously the question mark into your first screenshot means that the driver doesn't work properly.
Last thing: the right driver is not the one you shot, but is called Samsung USB or something like that and you must find it among the USB devices (when the phone is connected, naturally. If you don't have it: did you install Kies or the USB Samsung drivers? But I'm sure yes)!!
brainvision said:
I think you have the same identical problem I run into when i installed the Android SDK (first time I did that by the zip archive): before all that, my laptop was able to recognized and connect to the Corby without problems.. I was able to use Odin and flash both CWM both stocks rom..
My troubles started when i decided to install the Android SDK: I installed the Java JDK, first of all, then i downloaded the zip version of the Android SDK: I unzipped into a folder and started the SDK Manager letting it install the 6 or 7 default packages it required..
After that I was not able anymore to successfully flash anything with Odin! I think that the problem is the USB Google driver, indeed!!
I try to uninstall the driver by unpicking it into the SDK Manager but it's still there.. and if I try to manually uninstall it by the Control Panel, at the next reboot it installs itself again and again!!
Just to be sure I install the Android SDK into an VirtualBox emulated machine but this time I don't install the USB driver and Odin stills work!!
So, I don't know what you can do into your PC to solve that, actually.. I'm still studying the problem but I usually don't use Windows so I quite forget it.. now I can run Odin into my Slackware, so..
What I can suggest you is to try with another PC or laptop, for now..
EDIT: I forget to say: obviously the question mark into your first screenshot means that the driver doesn't work properly.
Last thing: the right driver is not the one you shot, but is called Samsung USB or something like that and you must find it among the USB devices (when the phone is connected, naturally. If you don't have it: did you install Kies or the USB Samsung drivers? But I'm sure yes)!!
Click to expand...
Click to collapse
Yes in that pc Kies is installed.. tomorrow i'll try in another one and let you know!!! Thanks for everything
Inviato dal mio GT-I9000 usando Tapatalk
on another pc I installed kies and press the option, power and volume down botton; it's now recognised ad a modem :
http://dl.dropbox.com/u/23080338/Immagine.JPG
but when I try ADB devices it appears this:
http://dl.dropbox.com/u/23080338/Immagine (1).jpg
(it doesn't recognize an adb device...)
http://dl.dropbox.com/u/23080338/Immagine3.JPG
this are the files in adb folder (I downloaded a zip version)
http://dl.dropbox.com/u/23080338/Immagine2.JPG
what's wrong??? help
ribelle85 said:
on another pc I installed kies and press the option, power and volume down botton; it's now recognised ad a modem :
http://dl.dropbox.com/u/23080338/Immagine.JPG
but when I try ADB devices it appears this:
http://dl.dropbox.com/u/23080338/Immagine (1).jpg
(it doesn't recognize an adb device...)
http://dl.dropbox.com/u/23080338/Immagine3.JPG
this are the files in adb folder (I downloaded a zip version)
http://dl.dropbox.com/u/23080338/Immagine2.JPG
what's wrong??? help
Click to expand...
Click to collapse
did you do all that with the phone ON or in Dload mode, that is the only state of the phone you are allowed to, isn't it?
brainvision said:
did you do all that with the phone ON or in Dload mode, that is the only state of the phone you are allowed to, isn't it?
Click to expand...
Click to collapse
I can't access to download mode..! I only can press the option,on and volume up to go in a special mode..
Sent from my i9000 using Tapatalk
ribelle85 said:
I can't access to download mode..! I only can press the option,on and volume up to go in a special mode..
Sent from my i9000 using Tapatalk
Click to expand...
Click to collapse
Yes I know.. It's called Emergency DLoad mode, if I well remember..
so did you try that with the phone putted in Emergency DLoad mode??
brainvision said:
Yes I know.. It's called Emergency DLoad mode, if I well remember..
so did you try that with the phone putted in Emergency DLoad mode??
Click to expand...
Click to collapse
Yes and the result is the one of the screenshots
Inviato dal mio GT-I9000 usando Tapatalk
bootloop samsung i5500
good morning head see I have a serious problem and would like to know if I can help smooth yo I got to free my samsung i5500 with the method that I show below:
and the super decompress a folder called oneclick ADB is copied to the root directory ie C:
2 - Within SuperOneClick files windows open a console (Start> Run> cmd) and
cd wrote .. twice and then, cd adb, then enter the following
-adb shell
- su
- cd /
- mount -o remount,rw -t rootfs rootfs /
- mkdir /efs
- mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
- cat /efs/mits/perso.txt
anotamos el codigo de 8 digitos
- umount /efs
3 - Place the chip from another company and enter the lock code we had written down and ready.
actually showed me on screen release the eight digits. the question is that when you turn off the cel to place another sincard and stays lit in a boot loop that is constantly cycles on and off and not pass the screen that says SAMSUNG.
I'm trying to repair the cell with this method and after discovering that I have to keep precionada turn the MENU + HOME + POWER on screen I get "emergency Dload Mode (ARM9 mode), run the odin and detects the device performed all steps you mentioned and well but after hours in performance of odin never goes out of this line "
<1> setup connection ... ".
then it would ask if I'm missing some file or am I doing wrong. I have the Samsung i5500 cell movistar Venezuela
Hello everyone! Today I downloaded and installed in Rom manager a recovery different from my model (stupid), turned off the phone and now will not start, nor the downloading mode... is there any solution? In other forums told me that there is no solution, is this right?
Sorry, my english is too bad...
I forgot to say that does not show the symbol of the battery when charging, either the PC or power...
You found any solution...???
Samsung repaired my phone for free!!!
So happy
Inviato dal mio Nexus S usando Tapatalk
ribelle85 said:
Samsung repaired my phone for free!!!
So happy
Inviato dal mio Nexus S usando Tapatalk
Click to expand...
Click to collapse
che para******
meno male.. ora starai più attento, questo è certo!
did you find any solution????
Enviado desde mi GT-S5830L usando Tapatalk
brainvision said:
che para******
meno male.. ora starai più attento, questo è certo!
Click to expand...
Click to collapse
Sure! Comunque ho smanettato a palla sul galaxy e non ho mai brickato!!! E' stata sfortuna grazie ancora
Inviato dal mio Nexus S usando Tapatalk

[Q] cm-12.1-20150623-NIGHTLY-serranoltexx.zip Error Status 7

i have the galaxy s4 mini i9192..am trying to install CM12.1 cm-12.1-20150623-NIGHTLY-serranoltexx.zip Edition..but am getting the error status 7..please help me ...
Lo quiero
Enviado desde mi Aquaris E6 mediante Tapatalk

LM-X210APM (LG Phoenix 4 At&t) Not Booting to Fastboot from ADB Command

So recently I have been trying to root my At&t LG Phoenix 4, when I use the command "adb reboot bootloader", it just performs a normal reboot into Android. I have USB debugging enabled and I have the setting "Enable OEM unlock" enabled. My end goal is to eventually install TWRP recovery for this device and then flash Magisk. I managed to boot into it once while following this tutorial, but never ended up being able to get into it again after that. One other notable thing is that when I boot into recovery via "adb reboot recovery", the screen displays "no command" with the droid on its back. Is there any way I can reboot into Fastboot so that I can install TWRP?
Device Info:
Stock Rom
Developer Options: Enabled
Android Version: 8.1.0
Rooted: False
On the no command screen you have to press the power button to enter in recovery. You are seening no command means you are there in recovery but to come to main screen you have to do one extra step. From there you can enter to bootloader/fastboot mode.
Hit thanks if helped.:laugh:
abhinavp649 said:
On the no command screen you have to press the power button to enter in recovery. You are seening no command means you are there in recovery but to come to main screen you have to do one extra step. From there you can enter to bootloader/fastboot mode.
Hit thanks if helped.:laugh:
Click to expand...
Click to collapse
Just tried this and it did not seem to do anything. Am I missing something?
If power button is not working try the buttons you pressed to enter in the recovery (power + vol down). On no command screen press and hold the buttons for a second or 2 and release. Possibly then you'll then enter in the main screen.
If also this combination dont work try all the buttons in combination.
room LG LM X210APM
Soy nuevo por aquí, quise rootear este dispositivo y termine matándolo por instalarle otra rom diferente a este modelo, lo cual hizo que ya no prendiera ni cargara ni nada de nada : o,
agradecería si alguien tiene una room LG LM X210APM y algún método para revivir el teléfono, pronto hare mis aportes para ser parte de esta gran familia, yo también vivo de esto, solo que estoy en pañales, es decir voy empezando pero la necesidad de aprender y salir adelante me llevo hasta aqui, gracias y tengan un excelente día.
att
Abhinavp649 has it correct just not explained quite clearly.
No offerce infended abhinavp649.
When the "No Command" appears on your screen press and hold the power button FIRST then while keeping tbe power button pressed then press the volume up button.
That will instantly give you the menu.
Pikeypete.
Pikeypete said:
Abhinavp649 has it correct just not explained quite clearly.
No offerce infended abhinavp649.
When the "No Command" appears on your screen press and hold the power button FIRST then while keeping tbe power button pressed then press the volume up button.
That will instantly give you the menu.
Pikeypete.
Click to expand...
Click to collapse
Android 8 relocks the bootloader and disables fastboot. Try LG Uppercut to downgrade and try again. Hope this helps.
JHell said:
Android 8 relocks the bootloader and disables fastboot. Try LG Uppercut to downgrade and try again. Hope this helps.
Click to expand...
Click to collapse
What kdz do we use to downgrade aristo 2 says spc code don't match
Hello, dear friends. will you be able to install firmware with Redmi 4A on this device? the processor is the same, the RAM is the same. what could go wrong? who is very well versed in this matter?
I guess the root was never sucessful. I was never able to root my old one after trying just about everything. Seems I saw one time on here that if your phone is branded by a carrier (locked to a certain network) that you can never root those phones, have to get an unlocked phone. Though it seems logical to also see if there are any custom ROMS even made for that model if you are planning on installing one. Am I correct on these?

REDMI 8A handishaking fail [Sahara] Reading Hello - Failed to handshake with device PBL!

I'm trying to install a stock rom on my Redmi 8a that has the system destroyed and also the bootloader blocked. I put it in EDL mode, and when trying through mi flash it asked for login, I'm trying through QFil and Qualcomm MTK Mi but both have the same error in sahara.
handshake failed [Sahara] Reading Hello - Handshake failed with PBL device!
what should i do to fix the error?
Note: After putting the device in EDL mode, I can no longer access fastboot.
Estoy igual, trabajndo para buscar alguna solucion.
GINKGOUL said:
Estoy igual, trabajndo para buscar alguna solucion.
Click to expand...
Click to collapse
Have you tried using Qfil to restore?

Categories

Resources