Related
So im stuck with my nexus with no OS... after flashing pure shamu it booted to just a password box... I input my password and it said i had corrupt data. I hit reset... wiped phone... all files GONE... Now what do i do. I cant mount to put recovery on.... I cant do anyting with this phoen right now... anyone had this happen... If so what steps to remedy?
Sounds like you need to try and fastboot the original google files, nuke and repave....
flash the stock img then start again
Flashing stock as we speak... was hoping another optino.... but after years of doing this I kinda know better... live and learn
hell
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
asphalte7 said:
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
Click to expand...
Click to collapse
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Evolution_Freak said:
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
asphalte7 said:
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
Click to expand...
Click to collapse
Should be able to boot twrp now.
but i have to unlock first ... my device is locked
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
you cant unlock it without booting up and enabling allow oem unlocking in the developer options
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
If you can boot to TWRP recovery, then you can ADB push a ROM to recovery and boot it.
Edit: Sorry, I missed the fact that TWRP had been deleted too.
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Evolution_Freak said:
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Click to expand...
Click to collapse
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
Or, if you are still in fastboot, issue this command > fastboot reboot recovery
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
asphalte7 said:
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
Click to expand...
Click to collapse
Then I'm afraid you may be stuck. A RMA may be in your future if no one else can offer a solution.
simms22 said:
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
Click to expand...
Click to collapse
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
asphalte7 said:
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
Click to expand...
Click to collapse
flashing twrp..
fastboot flash recovery recoveryname.img
and flashing a factory img is done while the phone is in its bootloader. there are instruction how here on xda. but to be honest, i dont know if that will work. where did you buy your n6 from btw?
Hello All,
I have following issue and hope that - if possible - someone can help me. I also would like to mention that I am not an
Android expert but did read a lot of articles here in the forum to find out - or better - to get an idea how things are working.
My Z3C had a water damage. Now I only get fastboot mode. Display is broken and does not show anything. I installed Android-SDK
to get ADB and Fastboot. I installed also drivers.
When I connect the device while pushing the "volume down" button the device manager show me a somc flash device with the "volume up" button I see an Android ADB Interface device. However ADB is not working (no device found) only Fastboot does.
I flashed the "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" with Flashtool via fastboot in the hope that I can somehow access
to "sdcard" by blindly navigating to "mount storage" but nothing seem to work.
On my linux device I see that the usb device is recognized but that it is not an mtp device.
Before I continue to spent hours without really knowing what I am doing I thought that if there is a solution I would find it here.
So if there is any way to get access to my files / pics on the device I would be really glad if someone can let me know how or
at least bring me to the right direction.
Thanks a lot in advance!
Is your bootloader unlocked?
clouds5 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Thanks for your reply clouds5.
I followed the process to unlock the bootloader (got code from sony side and unlocked via fastboot with
"fastboot.exe -i 0x0fce oem unlock 0xKEY").
In Flashtool, when I click on the "BLU" Icon I get a window with with my IMEI and my Unlock Code and a
Relock Button. So I assume that the bootloader is unlocked.
If there is another way to verify please let me know and I will do.
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Galbasib said:
I flashed "Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img" from doomlord.xperia-files.com/download.php?dlid=WjNjX0Rvb01Mb1JEX0FkdlN0a0tlcm5lbF92MDFfRlctMTA1 with
fastboot flash boot Z3c_DooMLoRD_AdvStkKernel_v01_FW-105.img
in the hope that it is possible but after rebooting it immediately goes into fastboot again. As I do not have
a screen I can not see anything - so I can not really confirm if it works or not - and in windows I do not see
anything either..
Click to expand...
Click to collapse
hmm you better send it to repair.
evildog1 said:
hmm you better send it to repair.
Click to expand...
Click to collapse
That's unfortunately not an option as I had to disassemble the device
evildog1 said:
no you cannot access files via fastboot only. but isn't it possible to flash custom recovery img file and boot into recovery and access files?
Click to expand...
Click to collapse
Should sdcard appear automatically when booting into recovery or are there any specific steps I would need to complete?
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
PsyClip-R said:
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
Click to expand...
Click to collapse
Well, fastboot don't want to work neither so that answer didn't help at all
Tenderenden said:
How can I fix this?
Click to expand...
Click to collapse
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
doppelhelix said:
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
Click to expand...
Click to collapse
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot? Because I think that flashing stock ROM will erase any personal data, but I really need to get it.
Tenderenden said:
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot?
Click to expand...
Click to collapse
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Okay, I got it. Now, have you got any suggestions how to get contacts and (hopefully) SMS back?
Tenderenden said:
how to get contacts and (hopefully) SMS back?
Click to expand...
Click to collapse
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
Click to expand...
Click to collapse
Does this work with locked bootloader? That would be really messed up.
Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
Click to expand...
Click to collapse
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
doppelhelix said:
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
Click to expand...
Click to collapse
Unfortunately in this case contacts weren't synchronised.
LuK1337 said:
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
Click to expand...
Click to collapse
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Tenderenden said:
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
Unfortunately in this case contacts weren't synchronised.
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Click to expand...
Click to collapse
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
LuK1337 said:
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
Click to expand...
Click to collapse
I will try it as fast as I can. Thanks
I want to flash custom recovery in my phone but it shows
remote: command not allowed
In bootloader, it shows that it is unlocked.
i get the same error when I type
fastboot oem devices-info
remote: command not allowed
I tried
fastboot oem unlock XXXXXXX(huawei code)
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock
it shows
remote command not allowed
The recovery is still Huawei e-recovery, it asked me to download the update but it always failed when it comes to download package.
What should I do now?
hjaxuan said:
I want to flash custom recovery in my phone but it shows
remote: command not allowed
In bootloader, it shows that it is unlocked.
i get the same error when I type
fastboot oem devices-info
remote: command not allowed
I tried
fastboot oem unlock XXXXXXX(huawei code)
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock
it shows
remote command not allowed
The recovery is still Huawei e-recovery, it asked me to download the update but it always failed when it comes to download package.
What should I do now?
Click to expand...
Click to collapse
Connect to pc, issue unlock command, then
Fastboot flash recovery xxxxx.img
Where xxxxx is the name of custom recovery file. Take a picture of the error, if any and share here
muradulislam said:
Connect to pc, issue unlock command, then
Fastboot flash recovery xxxxx.img
Where xxxxx is the name of custom recovery file. Take a picture of the error, if any and share here
Click to expand...
Click to collapse
as i said, it shows that the phone already unlocked.
I able to flash the recovery successfully but when i tried to boot my recovery
it will show
remote command not allowed
hjaxuan said:
as i said, it shows that the phone already unlocked.
I able to flash the recovery successfully but when i tried to boot my recovery
it will show
remote command not allowed
Click to expand...
Click to collapse
To boot your recovery, disconnect from pc, press and hold power, vol up until a reboot, let go of power but keep the other pressed for about 5,6 sec more.
muradulislam said:
To boot your recovery, disconnect from pc, press and hold power, vol up until a reboot, let go of power but keep the other pressed for about 5,6 sec more.
Click to expand...
Click to collapse
Even though I had flash the recovery, when i enter recovery mode using this method, it is still showing huawei e recovery
hjaxuan said:
Even though I had flash the recovery, when i enter recovery mode using this method, it is still showing huawei e recovery
Click to expand...
Click to collapse
Did you disconnect it from PC before pressing and holding power, Vol up?
Just making sure...
muradulislam said:
Did you disconnect it from PC before pressing and holding power, Vol up?
Just making sure...
Click to expand...
Click to collapse
Yes and it show the fastboot
It shows that Phone Unlocked in red colour and FRP unlocked
hjaxuan said:
Yes and it show the fastboot
It shows that Phone Unlocked in red colour and FRP unlocked
Click to expand...
Click to collapse
And power + vol down also boots to fastboot mode?
If this is the case then I am of no help to you at all. Another user is facing the same problem and no solution there till now.
hjaxuan said:
Yes and it show the fastboot
It shows that Phone Unlocked in red colour and FRP unlocked
Click to expand...
Click to collapse
Phone off, disconnect cable to PC, vol+ and power - enter to recovery
DRUGER said:
Phone off, disconnect cable to PC, vol+ and power - enter to recovery
Click to expand...
Click to collapse
Yes I managed to enter huawei e recovery, the problem is i wan to flash the recovery but it show
remote command not allowed
hjaxuan said:
Yes I managed to enter huawei e recovery, the problem is i wan to flash the recovery but it show
remote command not allowed
Click to expand...
Click to collapse
Try to unlock bootloader again using
Fastboot OEM unlock xxxxxxxxxxxxxxxx
And then try flashing twrp again using
Fastboot flash recovery2 xxxxxx.img
muradulislam said:
Try to unlock bootloader again using
Fastboot OEM unlock xxxxxxxxxxxxxxxx
And then try flashing twrp again using
Fastboot flash recovery2 xxxxxx.img
Click to expand...
Click to collapse
I tried
fastboot oem unlock XXXXXXX
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock XXXXXX
it shows
remote command not allowed
hjaxuan said:
I tried
fastboot oem unlock XXXXXXX
and it shows my phone already unlocked
and I tried
fastboot oem relock XXXXXXX
it shows
remote root type is risk
and I tried
fastboot oem lock XXXXXX
it shows
remote command not allowed
Click to expand...
Click to collapse
Just try
Fastboot OEM unlock xxxxxx
Followed by
Fastboot flash recovery xxxxxx.img
Many users reported that this worked. Don't do anything in between.
hjaxuan said:
Yes I managed to enter huawei e recovery, the problem is i wan to flash the recovery but it show
remote command not allowed
Click to expand...
Click to collapse
build number your firmware???
druger said:
build number your firmware???
Click to expand...
Click to collapse
nem-l22c636b140
hjaxuan said:
nem-l22c636b140
Click to expand...
Click to collapse
You may put screenshot comand line whith comand flashboot
Also try this TWRP https://drive.google.com/file/d/0B1Ez6wAY1mj6c0xxaTBUWmZVN1k/view?usp=sharing (Chinese)
Huawei E-Recovery is a secondary recovery. Try adb reboot recovery.
Sent from my honor 5X using XDA Labs
DRUGER said:
build number your firmware???
Click to expand...
Click to collapse
U don't have proper drivers installed.
Hi all ! I had exactly the same issue... The problem was solved by using the TWRP-CN image pointed by Druger ! (thank you mate) Any other attempt resulted into a fail. Twrp is of course in chinese language but follow this, and your life will be a bed of roses : youtube.com/watch?v=KOhR92EKD7A
Hope this will help
Note : Chinese NEM-AL10 2gigs ram model.
Huawei honor 5c
Can somebody help me my huawei (5c) i tried to install twrp on phone and it say command is not allowed. Im unlocked bootloader, i writed adb reboot bootloader, adb fastboot flash recovery xxxx.img and then it says command not allowed. Ps my file name is twrp and i try twrp.img on flashing
Hey guys, i have MI A2 cellphone, and after auto update programmed to three hours the smartphone show "AndroidONE" logo and then shutdown, i tried "Fastboot oem unlock", but it is my output:
PHP:
C:\Users\Lucas Daniel>fastboot oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.000s
. I'm desperate, I do not know what to try anymore, I believe I do not have unlock OEM activated, someone can help me?
Sorry for bad english, i'm from brazilian.
@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.
sas.mar said:
@LukeSkyPTBR
It's a well-known issue. One update was revoked as soon as Xiaomi has found out about phones bricking once it's installed. There's no way you can fix it by yourself except if you have ordered your phone from China (and so no warranty you have) and have experience in disassembling phones. There's a thing called test-point, do some research if you are self-assured in that area. Otherwise let your authorized service center make everything for you. It is a warranty case, either way.
Click to expand...
Click to collapse
Thanks, looks that, unfortunately, my unique solution is test-point for activate EBL Mode... I will leave the topic open for the case of i get other solutions... after 3 days, if not get, i will close and the unique solution will really test-point.
Try rebooting it a couple of times and see if it boots. Or plug it to a charger and try booting it once it starts to charge successfully. If all fails, flashing via EDL might be your only option.
Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).
Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?
Tianhe said:
Isnt Fastboot OEM Unlock command deprecated ? Shouldn't you use the unlock / unlock critical command ?
Click to expand...
Click to collapse
What is it command?
Aerobatic said:
Try rebooting more than couple of time. Phone is supposed to switch to the other slot of A/B where original ROM (before update) resides. When it finally boots, get developer rights, switch on ADB Debugging and OEM unlock, thus next time update soft-bricks your phone you'll be able to unlock (or even better unlock immediately after successful boot not to loose your data in future).
Click to expand...
Click to collapse
How can I do it? I leave the phone in the charger for a long time? Or do you need the power button for a long time?
I tried to press the power button for 2 minutes and nothing happened.
When i leave the smartphone on the charge, after 50 minutes, show for me 100% percent, so, i pressed power button and the screen stayed lock in "AndroidONE", nothing happened, until try again press power button.
The problem original comebacked to me
LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
I tried, the same ploblem happenned... don't work, unfortunely... :/
LukeSkyPTBR said:
What is it command?
Click to expand...
Click to collapse
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)
Phil_Smith said:
fastboot flashing unlock
fastboot flashing unlock_critical
Can't you just enter fastboot mode by holding power and vol- keys with phone connected to a PC?
(Or power and vol+, can't remember)
Click to expand...
Click to collapse
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.
LukeSkyPTBR said:
I can enter fastboot mode, but this is not enough to do run commands up. I would need unlock bootloader(OEM).
Click to expand...
Click to collapse
Do as tabun1994 said.
This will hopefully get the system up again.
The commands I wrote would unlock the bootloader. What else could I have meant?
If you succeeded with tabun's method, then you probably would only need to enable "USB debugging" and "OEM unlocking" in the ROM's developer options (which you'll enable by hitting "build number" in settings like 10 times or so).
Then you would connect the device and accept the 'trust this device' warning.
After booting to fastboot now, the commands I wrote should work and unlock the bootloader (if you even want that when your system is running again).
tabun1994 said:
If you can enter fastboot then you can go to EDL mode by typing 'fastboot reboot edl' and then use QPST to flash the latest stock rom.
Click to expand...
Click to collapse
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl
The test point method is actually easy , you have to dissasemble the display , easy procedure , remove the battery and short the two test points with tweezerz or something ,and in the meantime you plug the usb cable into the computer. It should install the Qusb_Hub drivers , and with miFlash you should be able to reflash the firmware . I bought a phone that was in this state and fixed it using these steps.
No more solutions, I will do the test point method, thanks to everyone who tried to help otherwise.
LukeSkyPTBR said:
This command needs OEM Unlock :/
this is my output: fastboot: usage: unknown reboot target edl
Click to expand...
Click to collapse
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!
LukeSkyPTBR said:
Okays, thanks for this solution, i will get the smartphone tomorrow, if the technical assistance not resolved my problem, i will try. Thanks very much!
Click to expand...
Click to collapse
I execute bat archive but nothing happens in Mi A2 .-
tabun1994 said:
No it doesn't, i have tried this method on locked bootloader, go to this link - https://forum.xda-developers.com/an...e-how-to-reboot-to-edl-fastboot-t3394292/amp/
And download the fastboot_edl.7z , your phone will be in edl mode, I think you don't have the proper platform files which has caused the problem.
Click to expand...
Click to collapse
What is your smartphone?