[Q] Xperia Go: backup with broken screen. - Sony Xperia P, U, Sola, Go

Hi,
I broke the screen of my Xperia Go completely. My problem is that I have some very important pictures on my phone, which I would like to back up.
Unfortunately I did not activate usb-debugging before, so pulling the files with adb will not work.
I managed to unlock the bootloader over command-line and booting the phone into fastboot mode.
I read somewhere that you can boot a recovery image(with adb enabled) in fastboot mode and connect to your device this way.
Unfortunately this did not work out for me. After I load clockworkmod recovery into the bootloader I'm not able to connect via adb.
The output is:
Code:
./fastboot boot ~/Downloads/recovery-clockwork-6.0.4.5-u8951-R3.img
downloading 'boot.img'...
(bootloader) USB download speed was 17900kB/s
OKAY [ 0.467s]
booting...
(bootloader) Download buffer format: boot IMG
OKAY [ 0.022s]
finished. total time: 0.489s
After this
Code:
./adb devices
returns an empty list. I also tried
Code:
./fastboot reboot
and
Code:
./fastboot reboot-bootloader
after that, but both commands get stuck.
Any ideas what I am doing wrong?

are you positive that the screen doesnt work at all? you could try to navigate the menus "blind" and enable debugging?

Related

Stuck in fastboot/hboot ; no adb; no RUU

Hello, i tried to update the OS manually on my Desire 610, unfortuneatly i guess i soft-bricked it. I can not get out of Fastboot/Hboot menu. Is there any way to get a working OS on it? Or it is trash now?
Some info:
1. TAMPERED UNLOCKED
2. Fastboot devices : good ; adb devices: not found (tried with original cable, every usb slot, millions of drivers)
Code:
C:\Users\Erik\Desktop\fastboot>fastboot devices
HC46NWS01827 fastboot
C:\Users\Erik\Desktop\fastboot>adb devices
List of devices attached
3. I have no TWRP or CWM. Yes i tried to get twrp via fastboot, but it is doing the same.
Code:
C:\Users\Erik\Desktop\fastbo
target reported max download
sending 'recovery' (11588 KB
OKAY [ 1.342s]
writing 'recovery'...
OKAY [ 0.628s]
finished. total time: 1.977s
4. Tried 2 different RUU, but at 1% it throws back an error.
Can some1 help me?
flash stock recovery with fastboot and use recovery to format. I was having the same issue with my 610.

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

half-bricked fastboot not working properly

a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.

How to boot into TWRP from a bootloop Nokia 6.1 Plus

I was installing a new custom ROM on my X6 and I forgot to change the slot after installing it. I proceeded to rebooting and my device was stuck in a bootloop. I struggled to power off the device but I couldn't. So after hours of trying to get into the bootloader, I found a solution.
You will need your USB cable, a `trwp.img` and a machine with `adb` and `fastboot`.
Connect the phone to the machine and execute the command below before the phone boots for the next round.
```
$ fastboot boot twrp-boot.img
```
You should get something like this:
```
< waiting for any device >
downloading 'boot.img'...
OKAY [ 1.444s]
booting...
OKAY [ 5.148s]
finished. total time: 6.592s
```
Fastboot will attach itself to the device before reaching the AndroidOne logo and boot the TWRP image.
That's it.

Question Honor 50 Lite stuck on looping logo screen

Hello I am trying to boot my phone to recovery mode to do a factory reset since it keeps restarting and it does not passes the Logo screen, it is stuck on a looping state. I tried to access the recovery mode usign the volume buttons but is not working, it keeps restarting. I did not enable debugging usb since I never knew I was going to need it. Any help will be greatly appreciated.
lol easy.
if your has problem, can you boot your phone into fastboot, don't request usb debbuging.
install this file and unzip it on your pc. https://dl.google.com/android/repository/platform-tools-latest-windows.zip
now open this folder and open cmd window inside it.
and run this command "fastboot continue" for continue normal booting.
if you need to reset your phone, can you use this command "fastboot -w"
Thanks,
I've tried that but is says command not allow.
C:\adb\platform-tools>fastboot continue
Resuming boot FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
Then I tried fastboot reboot to fastboot and it gave me this
C:\Users\Aiven>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
it goes back to the looping stage again.

Categories

Resources