Can I recover my phone? / How I most likely bricked my F5122. - Sony Xperia X Questions & Answers

Hi all,
it seem that I bricked my Sony Xperia X F5122.
I'll try to explain all the steps I took as detailed as possible hoping that I can recover my phone with your help somehow.
Steps:
- unlocked bootloaded following official Sony documentation (1)
- extracted TA partition
- installed Sailfish X according to official documentation (jolla.com/sailfishx-linux-instructions/)
- successfully ran Sailfish X for 1,5 years with all things functioning
- decided to reflash stock android to give phone to my daugther
- connected phone to Win10 PC in flashmode (Volume down while connecting to PC)
- started EMMA tools from Sony
- it detected the phone and presented several flashable images
- started flashing of latest image which finished successfully
- after flashing the phone boot-up failed with a message that the image is broken
- restarted phone and tried to get into flashmode again
- flashmode failed with LED blinking in a strange colors code (2)
- booted into fastboot mode (volume up while connecting to PC)
- booted TWRP (3) successfully
- flashed TA partition back to phone using abd mode available thanks to TWRP as I thought that it will enable the flashmode again
Current state:
- can set phone into fastboot mode
- all actions initiated with fastboot command are answered with "remote: Command not allowed" (4)
- tried to flash OEM using all available AOSP images from Sony (5)
- tried to unlock phone again (6)
- tried to boot TWRP image again (7) results in error "Your device has failed verification and will not work properly."
- cannot set phone into flashmode with LED blinking described above
- when booting phone the following error message is shown: "Your device has failed verification and will not work properly."
- when connecting to PC without any keys pressed, the same LED blinking is happening (2)
I assume that the commands are rejected due to enabled bootloader lock because of flashing the TA partition.
As no image I tried to run boots up due to verification error I cannot unlock the bootloader via developer settings thus not clear the TA partition again.
I also assume that I could flash the stock Xperia X image when I could enter the flashmode.
1) Does anyone of you know a way to unlock the bootloader via USB port?
2) Does anyone maybe know a boot image which succeeds verification and I could boot using fastboot mode?
(1) developer.sony.com/develop/open-devices/get-started/unlock-bootloader/how-to-unlock-bootloader/#tutorial-step-1
(2) dark red (~1 second), light red (~1 second), green (~3 seconds), yellow (< 1 second), restart with dark red
(3) twrp.me/sony/sonyxperiax.html
(4) several command outputs:
Code:
$ fastboot flash oem SW_binaries_for_Xperia_AOSP_N_MR1_3.10_v13_loire.img
target reported max download size of 536870912 bytes
sending 'oem' (164639 KB)...
OKAY [ 5.194s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 5.198s
(5) developer.sony.com/develop/open-devices/downloads/software-binaries
(6) unlock command:
Code:
fastboot oem unlock 0x<valid-unlock-code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.004s
(7) boot TWRP
Code:
fastboot boot /home/aa_ulm/Downloads/twrp-3.3.1-0-suzu.img
downloading 'boot.img'...
OKAY [ 0.704s]
booting...
FAILED (status read failed (No such device))
finished. total time: 12.245s

Related

[Q] Not able to boot past bootloader warning screen or get past TWRP splash screen

I am running a year old Moto E 1st Gen dual SIM (Indian version). Recently I installed CyanogenMod condor 12.1 nightly build (was running from June 18th). Today I tried to update it using CyanDelta. When I picked up my phone to wake it upI found it would not wake up. Since then it will not boot. It boots up to the Warning screen for unlocked bootloader and does nothing.
When I hold the power and volume button down to get the Fastboot mode screen, it refuses to enter TWRP recovery - it just gets stuck at the TeamWin splash screen.
I am using Linux. I ran fastboot -w . It claims to have wiped the cache and userdata. Then I could no longer reboot from the Fastboot mode menu - it started saying "Boot not validated." Recovery also produced the message "recovery not validated."
I tried to flash TWRP again with fastboot flash recovery <twrp image>. I got this error message at the console:
target reported max download size of 299892736 bytes
sending 'recovery' (7300 KB)...
OKAY [ 0.291s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 5.340s
The phone also displayed the "Mismatched partition size" recovery. The situation is the same - hangs at TeamWin splash screen, refuses to boot.
What do I do now?
I could try to flash the stock firmware again, but I use Linux, and I can't find the mfastboot tool for Linux anywhere (Motorola has yet to send me an invite for their developer software and all the external sites only have the Windows tool). I suspect that won't work either when I'm not able to flash a recovery.

Black screen after flushing new kernel

Hi guys
I really need your help!
Just unlocked my new z4 tablet and flushed a new kernel.
The short version, I've flushed androplus kernel v10 and rebooted the tab and completed the android wizard.
And the stupid thing is, I've forgot to activate usb debugging and rebooted the tab.
And now I have a black screen. The tablet doesn't show anything on the display.
After turn on it just vibrates shortly, but the screen is black.
The only thing I can do ist start fastboot, but since I did not enabled usb debugging I can't do anything, like reflush:
HTML:
C:\adb>fastboot flash boot boot.img
sending 'boot' (31948 KB)...
OKAY [ 1.239s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 1.256s
I'm pretty sure it is this stupid sony my xperia protection, I was so stupid to turn on "locate my device" or whatever.
(Before the fastboot oem unlock, I had to disable this thing in the android settings. If it was activated I got command not allowed from fastboot)
I have a black screen, usb debugging disabled and this stupid xperia protection is enabled, what can I do?
Please help
Thanks a lot!
Awesome, was able to fix it myself. With great help from this forum (Other older posts).
If anyone got the same problem, don't worry if fastboot doesn't work anymore.
You would be able to flush a new firmware (stock.)
1. Get latest version of flashtool
2. Download a firmware for your Device (Xperifirm)
3. Flush firmware in flashmode (Connect your device in flashmode, not fastboot)
4. Finish, your device will boot again!:laugh::laugh::laugh::laugh::

Oem unlocking via command line?

I want to flash new version of TWRP to my Jiayu S3. In order to flash a new recovery, I have to unlock the bootloader. Normally this is done in Android Settings > Developer options > OEM Unlocking. I can't do this, because my boot process hangs and I can't access the Android user interface at all. However, I have access to command line via adb shell and TWRP Terminal.
Can I unlock the boot partition using the command line? For example, can I use a command such as flash_unlock?
How to allow download for partition 'recovery' via command line?
Here is the actual error messages that I get:
Code:
[[email protected] ~]# fastboot flash recovery /home/Big/Download/twrp_20180417.img
target reported max download size of 134217728 bytes
sending 'recovery' (13198 KB)...
OKAY [ 1.002s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 1.005s
The following fails as well:
Code:
[[email protected] ~]# fastboot flashing unlock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.003s
[[email protected] ~]# fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 64.993s
So my question is, is there any command that I could enter in adb shell or TWRP Terminal Command that would allow me the flash a new recovery? Now the Android user interface for this phone does not work, but fastboot, adb and TWRP still work.
Now I have TWRP version 2.8.7.0 but in order to flash madOS Android 8.1 I should upgrade to their version of TWRP.
The usual command is fastboot oem unlock. If your phone supports this, it will wipe your phone as it unlocks the bootloader. If not, you get that error message. Not all phones support bootloader unlocking, as many ZTE owners have found out.
hello , having the same problem any soloutions ?
I would also like to know. I toggled the OEM Unlocking option thinking I was done flashing roms, but then an update happened updating my phone from android 10 to 11. Now my phone is stuck in a bootloader loop. I was able to boot OrangeFox recovery and access the terminal and I was wondering if you can navigate to that "OEM Unlocking" setting and change it to "on" somehow. My phone is the Moto G Stylus (2021) XT2115-4

[Root] Is my phone bricked ?

Hi all,
First of all, sorry for my english...
I've got a problem to root a phone.
I followed this guide :
https://forum.xda-developers.com/android/development/root-ulefone-armor-2-easy-rooting-t3780055
But I just realized, it's for ulefone Armor 2, while I try to root a Armor 2S..
I followed instructions, but I've got a problem on the point 2.
Code:
C:\Users\greg\Downloads\root\platform-tools>fastboot.exe flashing unlock
(bootloader) Start unlock flow
OKAY [ 5.301s]
Finished. Total time: 5.305s
C:\Users\greg\Downloads\root\platform-tools>fastboot.exe flash recovery recovery.img
Sending 'recovery' (15218 KB) OKAY [ 0.405s]
Writing 'recovery' OKAY [ 0.356s]
Finished. Total time: 0.777s
C:\Users\greg\Downloads\root\platform-tools>fastboot boot recovery.img
Downloading 'boot.img' OKAY [ 0.392s]
booting FAILED (remote: 'invalid ramdisk address: overlap with the download image')
Finished. Total time: 0.417s
After few test, who doesn't work at all, I've decide to reboot my phone.
Now, It's stuck on the main screen with this text :
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds.
And after 5 seconds, the screen go black for one second and return to the message.
And I can't go to recovery mode anymore. Volume+ and Power button don't do anythong but show this "Orange state" screen.
Please tell me there is a solution to unbrick this phone..
Thanks in advance
Try to relock again bootloader with command : fastboot oem lock maybe it can fix that issue but do at your own risk !!!
Thank you for your answer, but the phone is not recognized by the computer at this point.
I can not send command from the PC (adb or fastboot)
Try some key combination keys like :
hold Vol + and plug usb
hold Vol - and plug usb
hold Vol + ; Vol - and plug usb
If that doesn't work , let your battery to be completely empty 0% and repeat process . Good luck

poco f1 twrp boot loop, no twrp access

After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
kmkzboi said:
After doing a flash for new pixel experience PixelExperience_Plus_beryllium-11.0-20210823-0645-OFFICIAL, phone restarted and then no other option for access. Boots into twrp logo and stuck.
adb devices in command prompt show device and recovery.
When I do bootloader into fast boot,
fastboot devices shows
??????? fast boot
then disconnects. (after this it doesnt progress any further and disconnects from pc).
cant fastboot any files as it has error, my boot loader is unlocked and was on pixel experience 10 prior.
what are my next steps?
the teamwin recovery is 3.2.3-0
Click to expand...
Click to collapse
Use the latest Official TWRP since the one you have now is outdated and do clean install according the guide at POCO F1 Ultimate Collection & Guides. (You need to format data not just wipe) You can find everything you need there.
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
kmkzboi said:
first time i turned on phone today, i was able to to do command fastboot devices and it actually showed the device id, then when i tried to flash it stopped and then everytime i connect it wont even show fastboot devices without showing ???????? and shutting down again.
ive tried installing uninstalling the drivers and boot loader drivers, i believe its something to do with that, otherwise it has unlock symbol when it gets stuck on twrp logo, then when i put into fastboot it doesnt have unlock symbol before fastboot splash, what could it be? (im unable to flash anything without getting
1. running fastboot flash/boot/ any command really
Sending 'recovery' (1551913 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
2. running command then connecting phone already in fastboot
< waiting for any device >
FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
Click to expand...
Click to collapse
Check AMD Ryzen Fastboot Fix at the thread I posted above. If you have Intel system just install the Fastboot Drivers which is there (at the thread) and check.

Categories

Resources