hello i get this error every time when i try to use fastboot, can some one help me?
c:\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
FAILED (remote: Command not allowed)
finished. total time: 0.004s
i tried many diffrent commands, each time i get this error
have install google usb driver, device manager calls all fine.
have also tried the flashtool driver, device manager calls all fine but cmd.exe (admin) and fastboot same error.
only working command is to unlock the bootloader .
so my bootloader is unlocked and fastboot driver senn to be right.
can you please help me
windows 8.1 64 bit
xperia z c6603
bootloader open
no idea?
Sent from my C6603 using XDA-Developers mobile app
bump
If no one replies, in my experience, just inbox one of the old devs from our phone. Sometimes, if their not too busy they'll give you some time. They're just dudes trying to help people have cooler phones, anyway.
In my case, I get those errors because my bootloader was locked. I've unlocked a lot of times but not with the right code. I suggest you to try unlocking the bootloader with the right IMEI (not the one on the box nor the one in Flashtool) and enabling USB debugging.
i have order the unlock code 3 times from sony, also look on the rooting status:
Bootloader unlocked: Yes
i´m using the sony emma flashtool, and this works only with unlocked bootloader, but on fastboot i cant execute comands
dont know what is wrong
steve233 said:
i have order the unlock code 3 times from sony, also look on the rooting status:
Bootloader unlocked: Yes
i´m using the sony emma flashtool, and this works only with unlocked bootloader, but on fastboot i cant execute comands
dont know what is wrong
Click to expand...
Click to collapse
In case you use linux, try this setting permissions first:
http://forum.xda-developers.com/xperia-z/help/flashing-rom-twrp-bootloader-boot-img-t3241148
Edit:
You mentioned cmd.exe, so I guess you use windows and this is not the case,
however it may be similar issue for windows, since you run cmd from admin.
In my case, on linux, without permissions, my computer could only recognize the device from superuser/admin. With permissions like in the thread above, any user could run commands to device, and finally I did the trick without superuser/admin.
so you think it is an administrator premission problem?
i have format my windows pc today and reinstall all, but same problem, fastboot and device driver is without issue in device manager.
also create new administrator account, didn´t help.
edit:
i tried some more commands and some of them worked
HTML:
> fastboot erase boot works
> fastboot erase system works
> fastboot erase userdata works
> fastboot erase cache faild
> fastboot erase recovery faild
> fastboot oem lock faild just show 3 dots and nothing happening i wait 1 hour for sure
I can see you are using Windows 10. There are problems with driver verification. Have a look in device manager and check if your device is recognized properly in fastboot mode. If drivers cannot be installed you have to boot windows with signed driver verification turned off. For this press and hold shift and klick on reboot. Then choose troubleshooting and then something like restart options. At the next boot you have to press 7 - I think. Now fastboot drivers should install correctly.
Sent from my E6653 using XDA-Developers mobile app
its windows 8.1 x64 and driver are already installed no problems on device manager, i also have open bootloader.
I am having the same problem with windows 10 64 bit.
I give up.
pls help
try to run fastboot.exe under administrator's permission (either by setting properties on fastboot.exe or by running administrative cmd).
I'm using android sdk on ubuntu, I have to add "sudo" (run as root) before fastboot command but there's no need for "adb".
I think the device (xperia z c6603) isn't supporting some commands, but (boot system userdata) erase works.
maybe some experts can give a final answear
Try enabling OEM unlocking in the developer settings on the phone first.
This!
jackflap said:
Try enabling OEM unlocking in the developer settings on the phone first.
Click to expand...
Click to collapse
Thanks, been trying to unlock the BL of my Z5. I didn't know that this has the option. Previously on my Z1C and Z3 Dual there was no such option or lock
jackflap said:
Try enabling OEM unlocking in the developer settings on the phone first.
Click to expand...
Click to collapse
Awesome, thanks for that needle in a haystack!
Worked on Xperia X F5121 US version with the UK firmware to enable fingerprint scanner.
remote: command not allowed
Honor 6X BLN-L24
I had the same issue for the longest and tried everything possible under XDA's advice. its for the first time that I was not able to find the soloution to my isuues with the phone. Desperation led me to keep on trying until I accidently found how to do a "Hard Reset" which eventually solved this issue
1) Power your phone off.
2) Press Vol Up (+) Button and while keeping it pressed push the power Button (keeping both pressed).
3) As soon as you see the honor logo (blueish color), move from Vol up (+) to Vol down (-) While Still Pressing On The Power Button.
4) Keep Pressing Vol (-) and Power Button, --> will go through "turning your device on" --> Blank Screen --> Hard Reset Menu.
5) Well everyone knows from this point onwards --> Wipe It Clean, Reboot, Just like New.
Hope this helps.
I have bricked my phone (sony logo and nothing else) and can only connect in fastboot (not even flashmode). I try to flash a kernel but shows the same error. What should i do now? (Im on wind10 64bit)
Totesz00 said:
I have bricked my phone (sony logo and nothing else) and can only connect in fastboot (not even flashmode). I try to flash a kernel but shows the same error. What should i do now? (Im on wind10 64bit)
Click to expand...
Click to collapse
same problem.....
gungsye said:
same problem.....
Click to expand...
Click to collapse
Lograste solucionar el problema, a mi me pasa lo mismo...solo reconoce mi móvil en modo Fastboot y me muestra el mismo mensaje de error. Habrá alguna forma de instalar todo por fasstboot y recuperar mi Xperia Z (c6603)?
De antemano garcías.
Related
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
unlock it using flash tool, just press unlock wait and enter the code.. done
KlamKhowder said:
Hello everyone, I'm trying to unlock my bootloader but I have hit a roadblock and cannot seem to find anything that helps.
The part where i am stuck at is that when i enter "fastboot.exe -i 0x0fce getvar version" all i get is "waiting for device" infinitely.
I know the phone is in fastboot mode because the blue light is on
It seems my pc isn't recognizing my phone when it's in fastboot mode. I can see my phone in windows device manager as "S1 boot fastboot" but when i try to update the drivers manually using the drivers provided by sony, i just get an update failed screen.
any help would be much appreciated, i'm sure it's something dumb that i did, but i just can't figure out what.
Click to expand...
Click to collapse
try using different usb cable/ different port.
Had same problem....some driver was missing
Sent from my C5503 using xda app-developers app
I've finally gotten flash tool to work, however now it gives me an error saying that my device cannot be officially unlocked,
EDIT: i'm pretty sure i've unlocked the bootloader now, as flashtool had me enter an unlock code and my device has had all of its data reset.
however my issues continue as now flashtool utterly refuses to pick up my device. I have re-installed all drivers, flashtool, etc but still nothing.
sometimes it may have conflicts when flashtool and other tools use their own instance of adb or fastboot. I think the best thing to do now is reinstalling regular drivers normally. don't forget to enable usb debugging...
this may be useful :
Code:
[I]ADB_PATH[/I]\adb kill-server
exit
create a text file, paste this code then save it as ADB - Kill.cmd
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
arman92 said:
I'm trying too root my Asus memo pad 7 (170C), I've tried EVERY method, using KingoRoot, SuperOneClick, Frameroot, motochopper. None of them worked.
So I decided to do the rooting stuff myself, first I tried on Windows 8, the fastboot driver was not recognized, I installed the PdaNet, It recognizes the device now, the problem is when I run "fastboot oem unlock" or "fastboot oem unlock0x0b05" (ASUS VendorID), it returns : "FAILED (remote: unknown OEM command)"
I enter bootloader with "adb reboot bootloader" or by pressing Volume Up and Power.
I have also tried in Ubuntu 14.04, It doesn't even recognize the device in fastboot, and yes I run fastboot as root, still no chance "fastboot devices" returns nothing, and "fastboot oem unlock" returns "Waiting for device"
I did run "usbls" command, and it was clear that the OS has recognized the tablet, but why the fastboot does not?
Here is some information of my specs: ASUS MemoPad 7 (170C) Windows 8.1 64bit AND/OR Ubuntu 14.04
Bootloader: DroidBoot Provision Os, DroidBoot Ver: WW_MeMO_Pad-11.2.3.28-20141230 IFWI Version: 64.25
PLEASE somebody save my life as I'm stuck with it for a very long time!
Click to expand...
Click to collapse
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
CYoung234 said:
Because these Asus tablets use Intel processors, I do not believe that fastboot works. You did not indicate that you had tried the RootZenFone tool in your post above. See this thread:
http://forum.xda-developers.com/memo-pad-7/help/me170cx-k01a-root-t2985421
I have rooted two of these tablets using this method, and it worked perfectly on both of them.
Click to expand...
Click to collapse
Yes I did try the RootZenFone tool, but it didn't work either.
Unfortunately I forgot to "Forget the wireless networks" (I just disabled the WiFi), and the RootZenFone failed rooting my device...
Is there any way to get it work again?
HELP ME!!
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
arman92 said:
Anybody got an idea?
Would it be helpful if I Re-Flash the Asus official ROM to my tablet and start over? If it is, how can I do that?
PLEASE somebody help me!
Click to expand...
Click to collapse
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Done! I'm Root
CYoung234 said:
Yes, you can go into bootloader mode and restore the factory rom, which will likely downgrade you to 4.3 again. Then you can do the OTA update and use the RootZenFone again. This time, remember to follow the instructions EXACTLY, and you should do fine.
Edit: I do not have the two I set up right now, but they both were visible to my desktop in fast boot mode. They responded to fast boot device. Beyond that, I never tried fastboot oem unlock. Did you try just typing fastboot to see the comand set? You might try that.
Click to expand...
Click to collapse
I've followed the instructions in this page : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466
I successfully made it flash the Asus official ROM, but every time the freaking "Unfortunately Asus Demo has stopped" showed up.
I tried 4 different ROMs, still I got the error. I tried the RootZenFone-1.4.6r.apk everytime, no chance. The rooting process was interrupted by the "Unfortunately Asus Demo has stopped"
Then I figured out that when the tablet is connected to a power source (e.g. USB charge or PC), the error come up more frequent, so I disconnected the USB cable and tried the RootZenFone again, after a fresh ROM recovery, this time it successfully finished the rooting process. Huurrraaaay!!
So for every one else that has the same issue: just disconnect the USB cable and you are good to go!
Thanks for everyone that helped.
Hi,
Last Sunday (5) my phone turns off with 25% battery and just don´t turn on.
I was with the stock Oxygen OS.
Now when i turn it on, the oneplus logo appears and the next "screen" that should be the android or any other OS loading, just don´t appear. It just go to black and turn off.
Reading the Threads here about "OP3T Bricked" they all requests to hold volume up, and connect the usb cable.
The problem is when i do it, the driver just pop up at Device Manager List, and few seconds later it disappears.
(Try it using 4 different computers (Desktop win7 , laptop win7, laptop win 10 and desktop winxp) and 2 original OP cables.)
I had read a lot of informations that you share here in forum, but no tips helps to solve this issue.
So i contact the OnePlus support, they give me some links to download 2 encrypted files that looks like the files you guys shares here (One is the driver and the other is some kind of unbrick tool called MSM).
They connect at my computer and as soon they see that my driver just pop up and disappear, they stop the process and said to me to send the device to one support center.
Probably i will do it, but first i want to guarantee that its nothing i can do here.
So I try to reach my phone throw ADB and fastboot commands.
When at the screen of Fastboot I have some information about the phone and the last line said:
DEVICE STATE - LOCKED
using the command adb devices, we don´t find anything.
using fastboot devices, my device is listed by the serial number.
Should be possible to recover it using fastboot commands ?
There is a way to analyze my phone throw fastboot commands? Something like "all hardware is ok", like the memory, battery, etc ?
Best Regards
I have encountered the same issue while I was playing around with a beta oreo rom the name of which I wouldn't not want to mention here. Got my phone bricked and it wouldn't boot to recovery. Only fastboot was accessible so what I did was just flash the blusaprk v45 recovery and after booting I was finally successful in booting my phone into recovery where I wiped system, data, cache and dalvik without internal storage and flashed a nougat rom. Thankfully I was able to revive my phone and that solved my issue.
UPDATE:
I try to use the fastboot commands, but to do it i must use "fastboot oem unlock"
And guess what?! i can´t ...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.023s
Click to expand...
Click to collapse
So a lot of answer for the people who get this fail is to use the MSM tool .....
Any tips ?
Have you read THIS thread? Try to follow exactly those instructions...
jonsat said:
Have you read THIS thread? Try to follow exactly those instructions...
Click to expand...
Click to collapse
Hi Jonsat,
Yes, i tested and as i said, i can´t do it because the driver don´t still at device manager list.
So, the problem was solved, i need to use the OnePlus Support and converge them to use the files like "my method":
The Regular method is:
1) Hold volume +
2) When holding, plug the phone at PC
3) The device should appear at device manager, so you can run tools like MSM
This method does not work for me because my device doesn't still at device manager list, it just pops up and disappears.
So to make it work i need to:
1) Turn off the phone
2) Hold power + Volume +
3) Plug the phone
4) The phone should start with fastboot menu
5) Select recovery mode
6) hold volume +
Now the driver still on device list.
Using this solution, the files that we see here in forum does not work.
Need to use the files from OnePlus Support, MSM3.08 + OnePlus3T_A56(A57, or newer) + Driver Qualcomm signed 24/04/2013.
Thanks you
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
jonsat said:
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
Click to expand...
Click to collapse
Glad to help
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?
Here we go:
1- Today i got a new phone
2- Wanted to remove the Google search bar and disable google app
3- Restart and the phone screen is very different like another version, so i decide to do a soft reboot
4- Phone stuck on auto loop
5- Try recovery mode, dont work
6- Fastboot works
7- I download new room jasmine_global_images_V10.0.12.0.PDIMIXM_20190712.0000.00_9.0_1e580ee45b
8- Download Miflash and Minimal ADB and fastboot.
9- Plug the phone in pc
10- Unlocks OEM with app
11- Opened Mi flash
12- Miflash have installed all the drivers
13- When i click on refresh the Fastboot icon(the android and the soviet cat) dissapears and the only thing i have is in one corner "press any key to shutdown"
Important data:
-i have windows 10 with usb 3.1 and 2.0
-USB debugg is locked
-By pure luck once i managed to do a full boot sequence but when it finished the layout of the screen was different, like another version and i started updating it, after a couple of updates it stuck again on bootloop.
- i have no idea what was the original version on the room but in the last point and in nº 3 it was 10.0.7.
- i have nothing that i cannot recover so i dont mind wiping out my userdata
-i have considered a test point but i dont know if it going to work
-return it to amazon its my last ressort
- i read about the issues in december and january with the bootloop but i tried everything
-i have acces to a computer with linux
-its very difficult to start the fastboot logo/menu and almost impossible the recovery mode, it almost always ends with phone booting, when i plug it onto my pc it start with the bootloop.
-sometimes when i click on refresh while the phone with the screen in black or starting up with the android one logo it changes to fastloop automatically
- also tried a hard resset and nothing changed
I have no clue what to do, should i do the test point, ask for another in amazon, spray it with holy water??
Sorry for the possible typos and all the numbers i wanted to explain myself and to put some order in my head.
Please help and Thanks in advance
Fastboot rom
Try FASTBOOT method to unbrick your mi a2,
Karthickvel1988 said:
Try FASTBOOT method to unbrick your mi a2,
Click to expand...
Click to collapse
My PC does not recognize the phone and when i click on refresh the fastboot icon goes out and i can only se "pres any key to shutdown"
SrBisectriz said:
My PC does not recognize the phone and when i click on refresh the fastboot icon goes out and i can only se "pres any key to shutdown"
Click to expand...
Click to collapse
I think you should connect your phone via USB 2.0, from my previous experience, the USB 3.0 port will give press any key to shutdown message on your phone
Sent from my Mi A2 using Tapatalk
K9998 said:
I think you should connect your phone via USB 2.0, from my previous experience, the USB 3.0 port will give press any key to shutdown message on your phone
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
Does the same
I gave up
Using the fastboot mode and the adb voids the warranty?
SrBisectriz said:
Does the same
I gave up
Using the fastboot mode and the adb voids the warranty?
Click to expand...
Click to collapse
In this case I think you haven't unlock your bootloader, or haven't unlock both OEM and critical. Following up your steps, you didn't mentioned this part.
Have you done these codes?
fastboot flashing unlock
And
fastboot flashing unlock_critical
?
Select OEM unlock in settings doesn't unlock your bootloader automatically
Sent from my Mi A2 using Tapatalk
K9998 said:
In this case I think you haven't unlock your bootloader, or haven't unlock both OEM and critical. Following up your steps, you didn't mentioned this part.
Have you done these codes?
fastboot flashing unlock
And
fastboot flashing unlock_critical
?
Select OEM unlock in settings doesn't unlock your bootloader automatically
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
I tried these and only worked once or twice
But mi Flash did not recognise the phone
SrBisectriz said:
I tried these and only worked once or twice
But mi Flash did not recognise the phone
Click to expand...
Click to collapse
Mi flash required both unlock to do the work.
Sent from my Mi A2 using Tapatalk