Related
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.
Hi All,
Hope some will help guide me to the right way
Its My friend phone Mi3
I tried to update his phone using updater in miui, after choose update rom cancro .zip just finish sucessfull but restart like nothing happen.now Simcard not detected.
I tried to reset factory, failed it just delete some of it but data still there, so went to recovery ( in chinese just know the word emmc , so i choose to wipe data) successfully reseted .
Ok fine, i tried to root using kingroot ( success ) after that i tried to flash twrp, nothing happen, so try to enter fastboot (manual and adb)it just restart and came back to system, tried to go into recovery also the same reboot and nothing happened.
In adb mode ' adb devices ' detect 0123456789abcdef , when i check in phone imei and baseband 'unknown'
Already tried fix using adb shell but failed
miui pc suite not detecting phone
Try most driver suggested not working
Pc just detect storage only
So now
The phone
-boot normaly,
-no sim detected
-rooted by kingroot but cant flash twrp
-wifi useable (working)
-no imei (unknown)
-no fastboot ( cant go edl mode)
-recovery mode just (chinese ,test mode... And emmc deleted)
This Mi3 W
-Cannot enter or go into Fasboot manually or adb command ( so cannot miflash, flash boot or recovery img, cant edl mode)
-tried flash twrp but cannot boot to twrp recovery
So most unbricked steps need to go into fastboot in order to recover back. Is there any other way?
Please help
Im blurred rite now
Anybody?
I don't understand be a bit clear and specific
Which ROM was the phone on before flashing?
hi
1. please first try fastboot rom flashing via EDL...
for going to EDL ;
on adb ;
# reboot edl
or with a EDL cable ...
or via test point ;
photo ; https://1.bp.blogspot.com/-wKylsSuw...Xe7YbdcIsaIgCK4B/s640/mi3_9008_test_point.jpg
2. or restore qcn via qpst from here ; https://drive.google.com/open?id=0B4oUiKSTOb7oRUhPUm5kekpTOUk
So I ended up in the brick wagon, basically doing this:
- Tencent CN version converted to WW by vendor.
- Rooted / uptaded from root folder
- Changed fingerprint to WW
- Decided things got buggy here and there, did a factory reset
-> Slot _b is unbootable / Bricked
I tried flashall_AFT.cmd from both WW and CN raw firmware, both by clicking and command prompt, nothing happens (windows either disappear or stay still).
Phone does still answer to .\fastboot devices with powershell cmd.
Could somebody put me out of my misery ?
duck from space said:
So I ended up in the brick wagon, basically doing this:
- Tencent CN version converted to WW by vendor.
- Rooted / uptaded from root folder
- Changed fingerprint to WW
- Decided things got buggy here and there, did a factory reset
-> Slot _b is unbootable / Bricked
I tried flashall_AFT.cmd from both WW and CN raw firmware, both by clicking and command prompt, nothing happens (windows either disappear or stay still).
Phone does still answer to .\fastboot devices with powershell cmd.
Could somebody put me out of my misery ?
Click to expand...
Click to collapse
This happens when we root the phone.. so basically when you factory reset, phone tries to boot to recovery and doesn't work.. this is a known issue.. just get stock boot image for your versionand flash it using fastboot...
Thanks a lot !
duck from space said:
Thanks a lot !
Click to expand...
Click to collapse
Did it work OK flashing boot stock?
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
Does the cmd window pop up briefly and go again? If so, try removing or deleting the original zip from that folder, the one with the same name as the raw. Cmd gets confused /conflicts and crashes out...
Thanks for your help dude, yes that's what it does. I already done most known tricks to solve that issue to no avail. Might try on another PC now.
duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
i have same problem too.
Experienced that as well at first, flashall_aft.cmd not doing at all. But I got it work by putting the extracted raw folder to the root of my C: in my pc.
ram4ufriends said:
This happens when we root the phone.. so basically when you factory reset, phone tries to boot to recovery and doesn't work.. this is a known issue.. just get stock boot image for your versionand flash it using fastboot...
Click to expand...
Click to collapse
if we flash stock boot image, are the phone still rooted..?
ghayathok said:
if we flash stock boot image, are the phone still rooted..?
Click to expand...
Click to collapse
No, you need to update Magisk after ota or flash root boot
I can't flash the stock boot image. It says my phone is locked. I tried relocking the bootloader and it gave me the Slot_b is unbootable message as well. Any advice?
---------- Post added at 09:12 PM ---------- Previous post was at 08:36 PM ----------
Schramx4 said:
I can't flash the stock boot image. It says my phone is locked. I tried relocking the bootloader and it gave me the Slot_b is unbootable message as well. Any advice?
Click to expand...
Click to collapse
Nevermind, I figured out I could switch the boot image over to Slot_a and that worked for me.
Just flash the raw full rom with bootloader by pc
How to do
Ajmi24 said:
How to do
Click to expand...
Click to collapse
Download the RAW firmware version you want, then;
'Extract the file on your PC. Boot the phone into fastboot mode (hold volume up then press and hold power button, Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...) connect to the side port and run "flashall_AFT.cmd" wait for it to finish and the phone will restart itself (it will take a number of minutes to complete, with the cmd window open all the time. If the cmd window only flashes up and closes down, then check the rest of the notes with this step).
NOTE: you need to remove or delete the original zip from the raw folder once extracted as it confuses the Flashall_AFT.cmd with the raw rom and zip having the same name. Also, it can help to extract to the root of C drive.'
Taken from my guide;
https://forum.xda-developers.com/rog-phone-2/how-to/guide-to-check-change-fingerprint-cn-to-t4002279
duck from space said:
Yes thank you, phone is alive again.
Wish I could use the raw firmware flash method though, ADB works but flashall_AFT.cmd does nothing (not seemingly frozen while doing its job, just nothing).
Click to expand...
Click to collapse
BOA TARDE AMIGOS
ESTOU TENDO O MESMO PROBLEMA APÓS INSTALAR O TWRP
APAGO O TECIDO ROM WW ANDROID 10
REINICIALIZE O SISTEMA E APENAS LIGA E DIZ ESTAS INFORMAÇÕES (Slot _b não pode ser inicializado) VOCÊ PODE ME AJUDAR ONDE EU ENCONTRAR A IMAGEM DE BOOT, POSSO ENTRAR EM FASTBOOTON SMATPHONE MAS NO PC DE DISPOSITIVO DESCONHECIDO
Hi i recently bought the Asus ROG phone 2 Tencent edition, it came with WW rom 1908_12 but CN fingerprint. I followed the tutorial from Bobbyprats to fully convert it to global, unlocked bootloader etc. but after step 2 (the root part) when trying to boot the phone it says ''Slot A is unbootable''. I can still run the ''fastboot devices'' cmd and I can still see the fastboot menu. Now I read some other posts about this and I read that you need to flash the stock img again but since I don't have experience with flashing at all I am pretty clueless. Do I just connect the phone to my computer in fastboot mode and start adb&fastboot and use the ''fastboot flash boot bootstockww190812.img'' command? Thanks for the help.
Asparas said:
Hi i recently bought the Asus ROG phone 2 Tencent edition, it came with WW rom 1908_12 but CN fingerprint. I followed the tutorial from Bobbyprats to fully convert it to global, unlocked bootloader etc. but after step 2 (the root part) when trying to boot the phone it says ''Slot A is unbootable''. I can still run the ''fastboot devices'' cmd and I can still see the fastboot menu. Now I read some other posts about this and I read that you need to flash the stock img again but since I don't have experience with flashing at all I am pretty clueless. Do I just connect the phone to my computer in fastboot mode and start adb&fastboot and use the ''fastboot flash boot bootstockww190812.img'' command? Thanks for the help.
Click to expand...
Click to collapse
fastboot flash boot bootstockww190812.img thts all you need to do in fastboot mode And your phone will boot up .
kashif31 said:
fastboot flash boot bootstockww190812.img thts all you need to do in fastboot mode And your phone will boot up .
Click to expand...
Click to collapse
Thanks for the fast reply! will it boot by itself? ADB says it finished but i still see the fastboot menu on my phone, do i just press start? Also is it normal that it only takes 3 seconds too finish that process?
Asparas said:
Thanks for the fast reply! will it boot by itself? ADB says it finished but i still see the fastboot menu on my phone, do i just press start? Also is it normal that it only takes 3 seconds too finish that process?
Click to expand...
Click to collapse
Hey did you fix your issue? Yes you have to manually press on start on your phone
Slot a unbootable
Any ideas to fix this thank you
Slot -a unbootable
Asparas said:
Hi i recently bought the Asus ROG phone 2 Tencent edition, it came with WW rom 1908_12 but CN fingerprint. I followed the tutorial from Bobbyprats to fully convert it to global, unlocked bootloader etc. but after step 2 (the root part) when trying to boot the phone it says ''Slot A is unbootable''. I can still run the ''fastboot devices'' cmd and I can still see the fastboot menu. Now I read some other posts about this and I read that you need to flash the stock img again but since I don't have experience with flashing at all I am pretty clueless. Do I just connect the phone to my computer in fastboot mode and start adb&fastboot and use the ''fastboot flash boot bootstockww190812.img'' command? Thanks for the help.
Click to expand...
Click to collapse
I follow the same steps and got the same error but now I can fix. If any knows the solution please contact me.
i have same proplem and it sayes to me its locked
Hello Team,
I am also facing same problem. Please help any one
You have to reflash the entire RAW firmware image through fastboot. Then it will boot.
I have the same problem. I tried flashing a new boot image, but it still doesn't work. PLEASE HELP
aliferous said:
I have the same problem. I tried flashing a new boot image, but it still doesn't work. PLEASE HELP
Click to expand...
Click to collapse
Check one post above you.
I am getting a slot a is unbootable error. When I try to flash any raw images i am getting vender.img errors. see attached file.
> ROG2 Bootloader Unlocked.
> Download Stock.img of which firmware version you're on.
> switch the phone to fastboot mode
> launch adb > fastboot devices > alpha numeric should appear
> make sure stock.img is in the same folder as your adb
> fastboot flash boot stock.img
> fastboot restart
if above didn't work.
> download RAW Firmware
> Extract Content to a folder
> Switch phone to Fastboot mode
> double click Flash_all.bat
> Wait for process to finish
> Factory Wipe to boot
If Phone says LOCKED and you can't boot to system
you can unlock through EDL mode
sorry for resuming this "old topic",
after i did the thing in fastboot (my phone reboot and now it "works") is not able anymore to get LTE/4G any suggestion? i only did the fastboot thing
says galerVersion WW-17.0240.2009.49a where I find the boot.img of this rom
please help me to recover my rog 2 is with storage Slot a is unbootable
kashif31 said:
Ei, você consertou seu problema? Sim, você deve pressionar manualmente para iniciar no seu telefone
Click to expand...
Click to collapse
bom dia galera, alguem pode me ajudar a recuperar meu rog2, estou com o mesmo problema, meu ROM é ww17.0240.2009.49
como posso digitar esse comando no adb, obrigado pela força! estamos juntos !
Hello i have flash TWRP on my Redmi 9
and on my computer i have typed this command
"fastboot reboot fastboot"
for acces to the fastbootd mode
and now i have
REDMI
Powered By Android
black screen
and
Redmi
Powered By Android
and this loop
my english is very bad
bye
I have this problem too!!! could you fix it? it happened to me when I did this too
try to hard reset
I had the same problem after trying to flash the TWRP custom recovery on my Redmi 9 (lancelot).
In case that someone still needs to know, following was my solution:
I needed to flash back the stock firmware on my device with SP Flashtool. For that you of course need to download the firmware and take the scatter file of it. Then grab a custom Download Agent File and an authentication file from the web.
Also you need the MTK_bypass utility with the right payloads from the github website (Redmi 9 is MT6768, just take the master collection payload, it worked for me). You need that tool to disable the DAA und SLA protection on your Redmi 9. (Except you have access to an authorized Mi account of course, then you can just flash it with Mi Flash tool, but usually, one doesn't have that.) Follow the instruction on the web, there are detailed ways how to install the right drivers and run the bypass utility correctly.
In my case I had to format my device with the automatic flashing in SP Flashtool before the flashing worked, but that was it - my Redmi 9 is working fine again.
thank you for the input as it really cleared my head after i took a break at trying to get this thing out of a bootloop.
this does work, using sp flash tool but the device will auto detect through usb and you've gotta have the scatter file and firmware for the device. after using the brom utility don't restart the phone, you will reverse the process.
iReebu said:
I had the same problem after trying to flash the TWRP custom recovery on my Redmi 9 (lancelot).
In case that someone still needs to know, following was my solution:
I needed to flash back the stock firmware on my device with SP Flashtool. For that you of course need to download the firmware and take the scatter file of it. Then grab a custom Download Agent File and an authentication file from the web.
Also you need the MTK_bypass utility with the right payloads from the github website (Redmi 9 is MT6768, just take the master collection payload, it worked for me). You need that tool to disable the DAA und SLA protection on your Redmi 9. (Except you have access to an authorized Mi account of course, then you can just flash it with Mi Flash tool, but usually, one doesn't have that.) Follow the instruction on the web, there are detailed ways how to install the right drivers and run the bypass utility correctly.
In my case I had to format my device with the automatic flashing in SP Flashtool before the flashing worked, but that was it - my Redmi 9 is working fine again.
Click to expand...
Click to collapse
if my phone is bootloop and can't go into recovery mode either fastboot mode, can it be done ?
my phone bootloop after installing twrp and there you go bootloop until the end. can't go any mode also can't turn off the phone. any suggestion ?
daniel04222 said:
if my phone is bootloop and can't go into recovery mode either fastboot mode, can it be done ?
my phone bootloop after installing twrp and there you go bootloop until the end. can't go any mode also can't turn off the phone. any suggestion ?
Click to expand...
Click to collapse
I had the same issue, I was not able to enter neither recovery mode nor fastboot mode. But you are able to enter EDL mode, the Emergency Download Mode - in my case at least. From there I was able to unbrick the phone. I was able to enter EDL mode without opening the phone and using test points. Turning the phone on and connecting it to the computer in the same second as the screen goes on let me enter for some seconds, it was enough to let me run the tool to bypass the DAA and SLA protection of the device. Then I was able to flash back the stock firmware with SP-Flashtool. In my case I needed to format the device before the flashing worked, but then it booted back up alive.
Just be aware you probably need to install the proper drivers first to bypass DAA and SLA protection with LibUSB.
I have the same problem, help
I already tried all the methods in this post, my phone cannot access fastboot or recovery mode, and when I connect it via usb it starts immediately
iReebu said:
I had the same issue, I was not able to enter neither recovery mode nor fastboot mode. But you are able to enter EDL mode, the Emergency Download Mode - in my case at least. From there I was able to unbrick the phone. I was able to enter EDL mode without opening the phone and using test points. Turning the phone on and connecting it to the computer in the same second as the screen goes on let me enter for some seconds, it was enough to let me run the tool to bypass the DAA and SLA protection of the device. Then I was able to flash back the stock firmware with SP-Flashtool. In my case I needed to format the device before the flashing worked, but then it booted back up alive.
Just be aware you probably need to install the proper drivers first to bypass DAA and SLA protection with LibUSB.
Click to expand...
Click to collapse
Can you tell us how did you unbricked your device step - by - step? Sorry I am a newbie and do not know how to do it.
Alfredo_One said:
Tengo el mismo problema, ayuda
Ya probé todos los métodos en esta publicación, mi teléfono no puede acceder al modo de arranque rápido o de recuperación, y cuando lo conecto a través de USB, se inicia de inmediato.
Click to expand...
Click to collapse
Si hablas español podría ayudarte, te dejo mi FB
Log into Facebook
Log into Facebook to start sharing and connecting with your friends, family, and people you know.
www.facebook.com
Cualquiera que tenga ese problema en cualquiera de los dispositivos Xiaomi que hable español puede comunicarse conmigo y con gusto los ayudaré