Hi guys hoping you can help.
I had phone connected in fastboot and wrongly issued the following command while trying to load CWM:
c:\fastboot boot recovery-clockwork-touch-6.0.4.8-m7.img
downloading 'boot.img'...
OKAY [ 1.143s]
booting...
OKAY [ 0.005s]
finished. total time: 1.160s
I overwrote something here in the wrong place..
Phone is currently connected to PC in fastboot.
I then tried:
C:\fastboot reboot
rebooting...
finished. total time: 5.003s
But phone did not reboot and just stuck on fastboot.
side toggle buttons also don't work now..
Can you help please ?
EDIT: All sorted now, just followed thread here http://forum.xda-developers.com/showthread.php?t=2617016 and all is good in the world again..
Related
Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:
stygianblizzard said:
Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:
Click to expand...
Click to collapse
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....
gee2012 said:
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....
Click to expand...
Click to collapse
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.
stygianblizzard said:
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
TWRP cannot flash the stock images. Only flash able zips. The modified zips linked by @gee2012 should work
gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
Just few mins got img downloaded. That was bloody awesome. I dont know how to thank you :laugh::laugh::laugh::good:
Superb
Its working again!!!!!
Hello,
after unlooking bootloader of my Sony X Z3c (D5803), I tried to fastboot flash boot "Z_DooMLoRD_CF-Auto-Root-ported_FW-350.img" But got the message:
target didn't report max-download-size
sending 'boot' (7166 KB)...
OKAY [ 0.235s]
writing 'boot'...
OKAY [ 0.476s]
finished. total time: 0.726s
No error while fastboot reboot:
rebooting...
finished. total time: 0.000s
BUT the phone did not reboot. By pressing "power" and "Vol down" phone vibrated once, "Sony Xperia" appears and that's it. No soft or hard reset works.
Thanks for your help
Tony
Hello, I was on Android Marshmellow 6.0.1 + SU and I made with TWRP a full backup (+TA.img). I wiped:
+Dalwik
+Cache
+Data
+System
+Internal Storage
-Micro SDcard
Then booting into the TRWP 3.1.0.1 revovery did not work anymore (only Sony logo) and I thought I have to flash TWRP again. I used cmd administrator with this commands:
C:\adb>fastboot.exe -i 0x0fce oem unlock 0xxxx640DA639C0xxx
...
OKAY [ 3.281s]
finished. total time: 3.281s
C:\adb>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (13092 KB)...
OKAY [ 0.547s]
writing 'recovery'...
OKAY [ 0.875s]
finished. total time: 1.422s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.000s
I hold the volume down button and i was able to come into TWRP menu. Problem: I forgot to save my Lineage files on Micro SDcard, so flashing was not possible for me and I made it off (Volup + Power) After copieng with the pc the needed flash files to micro sdcard I tried again booting to TWRP recovery but does still not work. Then I tried some more commands:
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\adb>fastboot reboot
rebooting...
finished. total time: -0.000s
C:\adb>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.063s]
finished. total time: 0.484s
C:\adb>fastboot reboot
< waiting for any device >
rebooting...
finished. total time: -0.000s
C:\adb>adb ls -h
* daemon not running; starting now at tcp:5037
* daemon started successfully
adb: error: failed to get feature set: no devices/emulators found
C:\adb>adb shell
error: no devices/emulators found
C:\adb>adb devices
List of devices attached
C:\adb>fastboot devices
YT9119CPJT fastboot
C:\adb>
I´m still in a bootloop and i can not see that my smartphone is charging the battery. At last it saw only 50% in TRWP
and I don´t realy know what I have to do now. Need HELP :crying:
P.S.: I am on Windows 10 home (64 bit) and flashtool-0.9.25.0 told me all drivers was succefuly installed (with Win10 Disable Driver Signature Enforcement) and I used twrp-3.0.2-1-z3c.img
Edit: After some research, I read the battery can not charging, because it's in bootloader mode and i have to flash the stock rom back. I did it succesfully with flashtool
I am trying to unlock the bootloader and flash TWRP for the first time. I followed the steps from here: https://wiki.lineageos.org/devices/s2/install
I turned on the unlock option in settings and unlocked via fastboot, rebooted it manually (it didn't reboot), and then tried to flash:
Code:
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
$ ./adb reboot bootloader
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.779s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.836s]
Writing 'recovery' OKAY [ 0.231s]
Finished. Total time: 1.071s
$ ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
However, I got into the stock recovery page instead of TWRP. You can see above that the flash failed before I rebooted, but succeeded after that. Interesting observations:
- The above webpage indicates that the device should reset when I reboot, but it didn't, which means the unlock didn't work.
- When I went back to bootloader, the first attempt to flash failed, but when I ran another unlock it worked though apparently it did nothing.
Am I missing a step? I am using fastboot version 29.0.6-6198805 on Mac OS Mojave 10.14.6.
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
kalehrl said:
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
Click to expand...
Click to collapse
Thank you! That got me into TWRP with a dialog titled "Unmodified System Partition" with a slider to allow modifications. I am googling to see what this dialogue is about and how to get TWRP to permanently get installed.
That's normal. Just enable modifications and that's it.
kalehrl said:
That's normal. Just enable modifications and that's it.
Click to expand...
Click to collapse
OK, I don't remember seeing it before (I haven't flashed in at least a couple of years). I ran `adb reboot recovery` and it did go back into TWRP, so I am assuming that it did get persisted. For some reason "Never show this screen..." option didn't work, which is fine, but does it indicate that something is still readonly?
I don't think so.
You're good to proceed.
I was able to sideload the ROM and opengapps nano and it is booting up for the first time. I skipped the optional step to install root (AddonSU), I guess I can do it later too if I feel the need to get root. Thanks a lot for your quick help.
No problem.
If you want to root it, do it with Magisk.
Nowadays, LineageOS team recommend it.
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Flash fastboot ROM
Setting current slot to 'a' OKAY [ 12.421s]
Finished. Total time: 12.517s
Rebooting OKAY [ 0.098s]
Finished. Total time: 3.115s
Rebooting, then back to FASTBOOT
Solved!!
I got help from Xiaomi support
Helen17 said:
fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 4.615s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Device Error)
finished. total time: 4.615s
Stuck in FASTBOOT ...
Click to expand...
Click to collapse
i had the exact same problem, but someone on the site has solved the problem and repaired my phone on distance but against fee, if you want i can send you the link for him.
Helen17 said:
Solved!!
I got help from Xiaomi support
Click to expand...
Click to collapse
how to solved?