my x peformance can't access flashmode - Sony Xperia X Performance Questions & Answers

Please Help :'(
my phone briked after flashing but failed, can't access flash mode, recorvery mode.... Only can access fastboot mode
if i press down volume + plug USB only blink green LED. i try to flash kernel but (remote : command not allowed)
last time i try to Unlockbootloader and same (remote : commend not allowed) :'(
my device is SOV33
Please HELP :'(
Sorry for my english

Please check service info if your phone allowing you to unlock bootloader. If your device comes from a Japanese carrier like AU(your device's code name is SOV33) I won't be surprise if it said 'bootloader unlock allowed = no'. In that case, there is no way to unlock your bootloader without risks so far.

Related

Can't unlock relocked bootloader

Everytime i try to re-unlock my bootloader (official and flashtool way) i get this annoying error i can't figure out how to solve:
FAILED (remote: Command did not succeed)
finished. total time: 0.036s
Any help?
Thanks in advance.
evilruck said:
Everytime i try to re-unlock my bootloader (official and flashtool way) i get this annoying error i can't figure out how to solve:
FAILED (remote: Command did not succeed)
finished. total time: 0.036s
Any help?
Thanks in advance.
Click to expand...
Click to collapse
Are you using the correct code? Check your IMEI and request a new code
St.Jimmy90 said:
Are you using the correct code? Check your IMEI and request a new code
Click to expand...
Click to collapse
I double checked the IMEI and requested a new code, which happened to be the same one I requested the first time.
evilruck said:
Everytime i try to re-unlock my bootloader (official and flashtool way) i get this annoying error i can't figure out how to solve:
FAILED (remote: Command did not succeed)
finished. total time: 0.036s
Any help?
Thanks in advance.
Click to expand...
Click to collapse
Try with this:
"Windows:
Run fastboot in command prompt as an Administrator.
Make sure the output of fastboot devices returns your device serial number or you will never get past this error message.
If you have verified that you are running fastboot as Administrator and are still receiving <waiting for device>, there may be an issue with the drivers not being installed.
With the phone in fastboot mode and plugged in via USB cable:
-Open the Devices and Printers menu of the Control Panel.
-Verify that your phone is showing up as a device. Typically it will show up under the Unspecified section.
-If the phone is showing up with a yellow exclamation point, then the drivers will need to be manually installed.
-The Android SDK includes USB drivers under <path to SDK>\sdk\extras\google\usb_driver
-If the phone does not show up at all, reboot the phone into fastboot mode while the USB cable is still plugged in. If still no luck, try changing USB cables or ports on your computer. Do NOT use a USB hub."
Also make sure that you don't have another device connected or anything like Bluestacks running.
Sent from my C6603 using Tapatalk
You got a outdated fastboot version, try downloaded the latest fastboot version that might help.
And you can also try if above doesn't work: fastboot -i 0x0fce instead of fastboot

help about my p9

can anyone help me. my p9 stuck on Your Device Has been unlocked and can't be trusted.
cant go in twrp and won't power off only i can do is going in fastboot. but every time flash on fastboot it always failed (remote unknown command)
my phone status when fastboot is PHONE Unlocked FRP Lock. help me pls... thanks and sorry for my bad english
how to re-lock bootloader and unlock sir? and the problem is every time i flash stock recovery in fastboot FAILED (remote: command not allowed)
it always getting FAILED (remote: command not allowed)

Huawei P9 stuck In bootloop

what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
lucmaas99 said:
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
Click to expand...
Click to collapse
Every two or three days people report here they bricked phones by forcing update or Factory reset (or relocking Bootloader) from custom or rooted phones (or by having TWRP) - one must first go back to the original stock firmware he had, before upgrading/resetting/relocking...
And this thread will also not help to somebody else -
since 'somebody' will not read (before bricking the phone) ;(
---
Do you still have TWRP - use HWOTA to flash stock
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
If you have no TWRP but Fastboot is showing Bootloader unlocked, you should be able to flash TWRP.
If Fastboot is showing Bootloader locked but FRP unlocked, you should be able to unlock Bootloader.
But if there is no more TWRP and Fastboot is showing FRP and Bootloader locked - maybe DC Phoenix can help you
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
lucmaas99 said:
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
Click to expand...
Click to collapse
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
lucmaas99 said:
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
Click to expand...
Click to collapse
I cannot flash anything because I cannnot enable USB debugging in developers options
zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
What can I do I can access phone but cannot unlock bootloader because cannot use remote commands and I can not get into any recovery menu I am out of idea's
lucmaas99 said:
I cannot flash anything because I cannnot enable USB debugging in developers options
Click to expand...
Click to collapse
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
zgfg said:
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
Click to expand...
Click to collapse
Modelnumber: EVA-L19
Build: NRD90M test-keys
I think I should not supposed to have test-keys doesnt seem correct?
So I got my phone to boot but everytime I want to do something in recovery or something else It wont boot anymore and than I need to make the battery run out of juice. are there anyfix without needing root recovery or fastboot.
ADB wont work because usb debugging wont turn on (tried many things), Fastboot kinda works but gives the error (remote command not allowed)
Cannot get into any Recovery I can boot to OS

[HELP] Asus rog phone 2 Bricked

I messed up trying to root my phone but i found a way to fix by flashing to a newer firmware and the phone worked!
I tried to root again but this time i didnt enable developer option/usb debugging and now im stuck at bootloader screen
i cant enter recovery mode and i cant start the device.
im getting Slot _a is unbootable error message
i tried fastboot set_active _b but still getting same error..
fastboot flashing unlock doesnt work anymore because i dont have usb debugging ON
fastboot oem unlock -- getting this message
...
FAILED (remote: unknown command)
finished. total time: 0.004s
fastboot oem device-info ----------- (bootloader) Device unlocked: false
am i completely screwed?
sorry for the bad english
edit: im on version 1908,25 Global
EDIT: solved by this guide https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042 THANK YOU SO MUCH

How can I Relock Bootloader

Hello Everyone
How can I Relock Bootloader in my Asus rog phone 3 I unlocked bay mistake in asus unlocked tool so please tel me how can i relock bootloader
Thanks
Best Regards
fastboot oem asus-lock
When I try to relock my ROG Phone with this command or use any other fastboot command, I get:
FAILED (remote: 'Command not supported in default implementation')
can someone explain how to set up the Tool correctly? I cannot find any guide on it...
Hectorim said:
When I try to relock my ROG Phone with this command or use any other fastboot command, I get:
FAILED (remote: 'Command not supported in default implementation')
can someone explain how to set up the Tool correctly? I cannot find any guide on it...
Click to expand...
Click to collapse
go onto usb debugging and switch protocol
If you do this in Fastboot mode through recovery mode, it won't work. YOu need to be in direct Fastboot mode

Categories

Resources