Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
OMG!
edit:
how the hell do i get those files inside with only wastboot mode ... FFS
2nd edit: @Neuer_User, I have the pulled mmcblk0p7 on the storage, is there any possible way of pushing it back into the system via fastboot?
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
Interesting. See if you can make it reproducable. That would be great!
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
I wrote some unbricking instructions and a flash script to recover bricked watches with @kiralex1995 method of entering fastboot.
Hope, it helps recover the small number of watches known to be bricked through flashing.
https://forum.xda-developers.com/sm...tches/tutorial-unbrick-huami-amazfit-t3547300
Neuer_User said:
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Click to expand...
Click to collapse
You're welcome
@kiralex1995 , Thanks a Gazillion !!!
it worked and with @Neuer_User help, the watch came back to life !!!
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
MyriaBoa said:
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
Click to expand...
Click to collapse
maybe you need to explain a little bit more detailed? is the watch running and completely booted when you connect to usb and type those adb commands or is it switched off? when you turn it on, how fast do you turn it off? i didn't get it yet. please explain a bit more.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
It is interesting. Does it work with out th.e adb kill-server and adb start-server commands? I do not see, how they could be involved...
The adb wait-for-server might be the key. So, when the watch is started, there is some USB communication on-going. I'd love to do some testing on that. Will do that for sure, when I get the development watch
I' m not near my computer, so I can't do more tests now.
As I wrote in my first post, it wasn't my intention to open fastboot, when it accindentally happened for the first time.
The kill and start commands were given, because my Windows 7 machine pretended not to see the watch in adb (only as usb), and I thought, maybe it's detected, when I turn it on while adb is waiting for device and the usb notification 'kicks in'.
But nothing happened, so I pushed the button, to turn the watch off again.
To my surprise the result was fastboot.
I repeated the same steps today on my Windows 10 computer that always detects the watch in adb and it opened fastboot again.
Could you specify for which build or version you tried this? I (unfortunately) had the update to 1.3.5 and there seems to be no way to enter fastboot. It also is not recognised as an adb device
I have a amazfit pace but he is stucked on a update screen and when I try entring in fast boot mode he doesn´t enter and goes to update again and don´t conclude that. What can I do?
Did anybody managed to get Amazfit 2 (stratos) to fastboot using this method? thx...
EDIT: Yes, I can confirm it works! However it is really kind of tricky. Embrace yourselves!
Many thanks to you guys for finding this out, you are the best!
Thanks.
kiralex1995 said:
Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
Click to expand...
Click to collapse
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Hello my device is waiting for the logo, it is not opening.
endrancer said:
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Click to expand...
Click to collapse
Hi all together,
yes I can confirm that plugging the cable is not neccessary. Went back to stock yesterday. Got into fastboot on first try.
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
E-lian said:
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
Click to expand...
Click to collapse
Hello
I've bricked my Pace and cannot enter fastboot.
When I try to enter fastboot I have the same behaviour on my Amazfit Pace. Have You managed some how to enter the fastboot without connection to the PC?
Related
some guy successfully bricked his N1 as soon as he received it about 2 months ago. When this expensive brick reached my hand, he didn't even remember what he had done... and this brick had been through many many ppl for repair, so there is no way for me to know what exactly happened during the last 2 months...
Anyway, now it:
1. light doesn't turn on when charging(not sure yet whether it is actually charing)
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
3. after single press of power button when powered off, red/green/blue/white color bar and 3 droids on the screen
so , now I cannot put it in fastboot nor recovery mode, stuck.
could there be anything I can do to rescue it?
ndep said:
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
Click to expand...
Click to collapse
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
The only way that a N1 get bricked (software wise) is by upgrading a wrong radio, and unfortunetly the only way to recover it (now) is by sending it to Google/HTC
more explanation
thanks i did try that...fastboot devices could not detect anything,coz it just freezes at that screen and could not enter any mode using power and voldown button.
what puzzlrs me most is that screens with multicolor bars, how on earth does that happen?
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
update: the light turns orange now and then when charging, and it is actually charging no matter the light is on or not. ( using my own nexus to verify that )
Did you plugged it to your PC?
I knew a guy who bought a ''flashing device'' capable of formating any chipset over USB, so he could do a clean install of the Firmware again. Perhaps you could find one of these devices over ebay
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
That's assuming he has the android sdk installed with the correct drivers. We don't know if the op has.
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
should be deleted, sorry
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
edit: isn't there an option to delete this reply? I clicked the submit button twice,sorry.
does typing fastboot devices in the cmd prompt work for your non bricked nexus?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
TFJ4 said:
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
Click to expand...
Click to collapse
power+trackball will bring it to fastboot screen, note just the fastboot screen, it just freezes there. All the buttons does not work, and connecting to PC using a USB cable does not show "FASTBOOT USB".
However, it could enter HBOOT with power+voldown, I noticed it searches for passdiag.zip , passdiag.nbh, etc. Could I use this builtin function to flash it? which file in this post should I use?
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
I tried to use the first one ( http://www.romraid.com/paul/nexusone/EPE76-update-nexusone-stock-images.zip ), rename to PASSDIAG.zip , but HBOOT is still complaining about "No Image"
Perhaps it's physically damaged!
It remembers me of my boss iphone that looked perfectly normal but couldn't get a FW installed because the power part has been damaged by water(power button couldn't work at all)
Try renaming it to passimg.zip and use hboot again.
speedyls91 said:
Try renaming it to passimg.zip and use hboot again.
Click to expand...
Click to collapse
tried PASSIMG.zip , still "No Image"...
You can send it to htc for repair but the downside would be that you would never know how to deal with this kind of problem yourself...
Continue the research and keep us posted ...
i maybe wrong but i think is it case-sensitive.....meaning PASSIMG.zip would fail but passimg.zip wouldn't.....Correct me if i'm wrong please....
Case sensitive
I'm pretty sure it is case sensitive. Used to be that way with other android and HTC devices. Can't imagine it's changed.
linux is case sensitive, for sure.
i say approach from the adb/fastboot route, using usb. first, ensure that you have all the correct drivers etc for adb use (the sdk, the usb drivers, and the device specific drivers).
try ur 'adb devices' command
if adb sees it, in normal mode, you should be okay. make sure the phone has 'usb debugging' turned on in settings
I have searched and couldn't find a fastboot thread. So here it is.
I found out fastboot is working on Linux.
Bad news is Windows seems to need another driver for fastboot.
Please help look for a windows driver or make one.
The fastboot commands all seem to work fine.
Here you guys go! Enjoy.
Code:
[SIZE=5][SIZE=3][SIZE=5][SIZE=3]adb reboot-bootloader
fastboot -i 0x1949 command_here[/SIZE][/SIZE][/SIZE][/SIZE]
Just noticed pokey9000 said this but it was overlooked.
pokey9000 said:
That's it. And you're running fastboot as "fastboot -i 0x1949 your_command_here", and you have udev set to allow permissions for that VID (or are running as root) in Linux?
Click to expand...
Click to collapse
Thank you.
Still don't believe me, look at the last picture.
I'm having issues with some commands. Please test it out and enjoy!
shimp208 said:
In the Fire TV section a fastboot cable was created by splicing two USB A to B cables together, so that the A to A ends were together which when connected from your computer to the Fire TV on bootup put the device in fastboot mode, in the process then your computer recognized (Running Windows 8 was the example given) the device and installed the proper drivers. Since the devices are similar, a potential solution would be use the cable, have the computer recognize it and install the drivers, then backup the drivers, and share them here for others to use.
Click to expand...
Click to collapse
I'm quite sure the cable isn't the issue. Also that's just it, I can't get windows to recognize it or find much info about it. The adb driver for the device isn't enough I guess. The funny thing is windows says it's working properly as 'Kindle' for a little while when you plug it in (while in bootloader) then device manager refreshes and reports 'cannot start'. I tried launching 'fastboot devices' many times but still nothing. I think it needs a software fix and not a hardware one but I have no past experience using fastboot. So... noob alert.
btw the driver windows tries to use is ms_comp_mtp(Generic driver installed=true) and adb uses the Amazon one on the fourm here.
DevNode status Value:
01802400
DN_HAS_PROBLEM
DN_DISABLEABLE
DN_NT_ENUMERATOR
DN_NT_DRIVER
Also Bus reported device description Value:
fastboot
VID=1949 & PID=000C
(0x1949 && 0x000c)
Current Driver files:
\system32\DRIVERS\UMDF\WpdMtpDr.dll
\system32\DRIVERS\winusb.sys
\system32\DRIVERS\WUDFRd.sys
\system32\WpdMtp.dll
\system32\WpdMtpUS.dll
We need someone good on this.
I have a problem
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
saphi95 said:
I have a problem
Click to expand...
Click to collapse
I would recommend taking a look at this thread here, specifically the "Fixing No Permissions Error" section which should allow you to fix the problem your encountering.
dcoig1 said:
Is flashing the stock .bin file any different than doing a factory reset?
I am bricked, have root, have adb, can get fastboot using adb reboot-bootloader in windows 8. I also have a Linux box if necessary.
Click to expand...
Click to collapse
Fastboot works with win8? Not with win7.1 If you have fastboot working with win8 please go to device manager (when your in the bootloader) click properties on the device then look for what driver it uses.
Hashcode said:
I don't think there's ever been a question of getting into fastboot mode by using the adb reboot-bootloader command.
The issue is how to enter fastboot if the device is semi-bricked.
The device has source in the original bootloader to boot into fastboot mode if both volume buttons are pressed while powering on the device. But this has since been altered and now will only work if the device is unlocked.
Click to expand...
Click to collapse
My main reason is to get fastboot working with windows. I just can't. Linux seems to work with fastboot but I can't access it via windows.
Just uninstall the kindle driver and replace it with the generic fastboot one
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
I think all that works is reboot into fastboot mode. Windows 8 says no drivers are loaded. I tried a command (can't remember what) and it just went out to lunch so... I guess windows 8 isn't working either. Only to put the device in fastboot.
there are three oem commands:
oem device-info
oem idme
oem relock
Click to expand...
Click to collapse
but it doesn't support oem unlock so there must be another way of unlocking the bootloader, when you try some of the commands the device returns "not allowed for locked hw". Does anyone know what the "hw" is ?
hw = hardware?
MaximilianOzora said:
hello all,
i've kindle fire hdx 7" , no adb, grey screen logo then shutdown and goes to black screen.
when connected using cable, it show new devices... QHSUSB_BULK and sometime unknown devices.
press hold power button and volume up only go to recovery mode, but cannot recovery the system..
always go to grey screen logo...
sorry for my bad english language...
hope all of you, understand what i mean here
i need solution for fix the problem soon. thanks
Click to expand...
Click to collapse
Read up on this bud.
Hi,
I have a bricked kindle hdx 8.9 that stops at "Kindle Fire" boot screen. I am a newbie at these things.
Just discovered that it still respond to some adb queries. Sounds like there is still hope to recover... Could it be the bootloader is messed up? Anyway to reload an image boot file to repair?
Also "fastboot reboot-bootloader" puts it into fastboot mode...with the status "ready"....and i just dont know how to proceed. Any one can help?
uhg
Facepalm
just back a little: was rooted in April but with subsequent amazon auto updates - didn't have su status. But I was able to load apps & files, installed vpns, quite a few docs,mp4 files, etc. Not really using much of the new freedom or whatever was left of it... Nothing exciting.
Was working well until one fine sunday afternoon, just 2 weeks ago when it just simply stopped after rebooting from a previous low battery charge. Was told it could be an interrupted routine update when the battery power just fell below threshold - but thot it wouldn't have erase the previous image before the new update is effective. Or it could possibly be a deleted file that is related to the booting process as I did a bit of clean up prior to the last reboot?
In the meantime, I did some adb shell/pull to explore or extract the files, photos,etc in /sdcard & other places back to my PC just in case they were not backup by the cloud. Maybe it was not bricked...but just lost a boot file or something...
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
here try
Tumbtack said:
In a bad situation, have absolutely zero ADB access as my build.prop is botched (bad permissions) and I did a factory reset in hopes of recovering. There is a "fastboot cable" on amazon that says it will reboot a hdx into fastboot mode, but I'm unsure of it's legitimacy. Help?
Click to expand...
Click to collapse
This thread.read read read http://forum.xda-developers.com/showthread.php?t=2588608
I don't quite understand. Why is a special cable required for this? What makes it any different from the standard one that comes with the device?
I don't know if this will add anything to the discussion...but I can confirm fastboot is working on Ubuntu 14.04. I am using a kindle fire HDX 7" and it detects it on devices..and most commands work. Sometimes the terminal must be closed and reopened for commands to go through..
fastboot oem unlock works..or rather it says "Okay" but I'm unable to flash anything.
Hi all!
I've been researching this for the past few days. I recently dropped my Nexus 6P and it broke the LCD display. Google voice commands still work and I was able to unlock it with a USB OTG cable, so it appears that the only thing that's broken is the display. Of course, I didn't have USB debugging, Developer Mode, or it set up as an MTP device. I've only had the phone for a couple months so it's not a big deal but I would like to get my pictures back if at all possible. I know almost 0 things about android development, but am fairly tech savvy so I'm trying, here.
I have Android Development Studio with the Google USB Driver installed. Plugging the phone in via USB shows a "Nexus 6p" device with no files on it. I've gone through some tutorials but always get stuck at the "adb device" part.
I get the following from running commands:
Code:
C:\Android\Sdk\platform-tools>adb.exe devices
List of devices attached
C:\Android\Sdk\platform-tools>fastboot devices
XXXXXXXXXXXXXX fastboot
C:\Android\Sdk\platform-tools>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.031s
I think I am able to boot my device into recovery mode, but that hasn't helped as of yet.
Would appreciate any and all advice. Thanks for taking a look. Don't worry, I immediately set up my new phone in case I'm ever in this situation again. Take it from me... set it up now
OK so fastboot is for the bootloader and adb is for either recovery or the system itself.
You also won't type .exe after it either. Boot up your phone and unlock it then type "adb devices" into the command prompt. If that doesn't work (since you mentioned USB debugging is off) try from stock recovery. I'm honestly not 100% sure this will work TWRP is the 1st thing on my phone's. I don't mess with stock, but it's worth a shot. Reboot while holding volume up and it should bring you to stock recovery. Wait a few seconds and then hold the power button and quickly press and release volume up and then let go of both buttons. Do this plugged into a PC since when you enter the bootloader you get the little noise that plays. That way you know when it actually reboots and when to try the button combos. Now run "adb devices" again and it should show "XXXXXXXXXXXXXXXXX recovery"
From there just try adb pull.
"adb pull /storage/emulated/0 c:/Users/YourUserNameHere/Downloads"
Obviously in the path above, you'd enter your own username and entirely change the path to wherever you want your data saved. The above pull command will take your entire internal storage, all files if it works.
Hey Roy,
Thanks for posting. Still no luck getting it to show up on the device list. Followed your instructions and got a connected noise for the boot screen, then unconnected noise and connected noise again when I held the power button and pushed the volume up button, then released. So I think I got it into recovery mode but still no dice. Any other ideas on things I could try?
ahalbert said:
Hey Roy,
Thanks for posting. Still no luck getting it to show up on the device list. Followed your instructions and got a connected noise for the boot screen, then unconnected noise and connected noise again when I held the power button and pushed the volume up button, then released. So I think I got it into recovery mode but still no dice. Any other ideas on things I could try?
Click to expand...
Click to collapse
Sadly if you fully booted into stock recovery and adb still isn't working, I'm not sure there's a way to enable Android debugging at this point. Maybe someone else could chime in, but I think you'd need to get your screen replaced at a local repair shop.
RoyJ said:
Sadly if you fully booted into stock recovery and adb still isn't working, I'm not sure there's a way to enable Android debugging at this point. Maybe someone else could chime in, but I think you'd need to get your screen replaced at a local repair shop.
Click to expand...
Click to collapse
That's too bad. Thank you for the advice though!
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
From your description, it seems like TWRP was not installed correctly. But don't worry, on this phone you do not have to install the recovery to use it. You can boot straight into recovery from your PC while the phone is in 'fastboot' mode. The 'fastboot' mode is what you get when you do 'adb reboot bootloader'. The screen off, blue LED is signalling that the phone is ready for fastboot commands. You can then run:
Code:
fastboot boot <recovery image file>
The phone should load and run the recovery.
Please note that adb will not see your device while it is in fastboot mode. Likewise, fastboot does not work while the phone is accessible through adb. adb support comes from the ROM, but TWRP also supports adb, so you can also use adb while in TWRP.
Rendini said:
So I looked around here and on the interwebz to find an answer to my question before I decided to state my question to you.
I just acquired the Sony Xperia X Compact (F5321; Android 7.1.1).
In order to get TWRP on it, I consulted a lot of online guides including those described here. Of which I thought this would be the most suitable:
https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914
So after:
having adb tools and fastboot incl. drivers (also tried the minimal)
developer options -- oem unlocking -- bootloader allowed to be unlocked; and developer options -- USB debugging -- debug mode when USB is connected
checking the service *#*#7378423#*#* , which shows "bootloader unlock allow : YES"
phone connected to PC
I encounter the following problem.
While the sony stock rom it comes with is running,
via adb I am able to feed the phone the following command with the respective outcome:
adb reboot fastboot (reboots into Android, with the LED lighting briefly up in red)
adb reboot recovery (reboots into Android, with the LED lighting briefly up in red)
adb reboot bootloader (boots down, but does not boot into Android; there is only a black screen and the LED is on and stays blue)
in any of those states, if I enter an adb command there is always this output as if the phone wasn't connected or recognized or off:
error: device '(null)' not found
So I am able to communicate commands to the phone when it is running. I assume this means my drivers are all in order, right?
Also. While it is off and disconnected from the PC.
I keep the power button and the volume down button pressed, the Sony Logo comes up and after that it takes turns with a black screen as long as I keep pressed.
I keep the power button and the volume up button pressed. It is followed by one short vibration, another short one, and the three in a row. And then no further reaction.
I feel pretty dumb, can anyone help me with how to enter any of the alternative boot options? Thanks in advance!
I just don't know if there is something I am not seeing or if there is plainly something wrong with the phone. Not knowing this for sure is driving me crazy. Hopefully this is something others might learn from, as well.
____________
little edit about the text format
Click to expand...
Click to collapse
Switch the phone off.
To enter fastboot mode: Hold the Volume UP and connect your phone to the USB port of your PC. The blue LED should come on and provided you have correctly installed drivers, you will be able to use fastboot commands.
To enter bootloader/flashmode: Hold Volume DOWN button and plug USB cable to your PC. Green LED should lit up and provided you have correctly installed the drivers, you will be able to use Flashtool, Emma or other software to flash firmware files.
FAILED (remote: Command not allowed)
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Rendini said:
Hey guys!
First of all, thanks for taking the time!
So, confirming how to enter bootloader/flashmode is much appreciated, since I was very much in doubt about the fact that the screen stayed off. On other devices I always had something on the screen in recovery mode and the like.
Now I know it was problem with the drivers indeed. Also appreciated, the hint that adb and fastboot work separately. While the device was recognized by adb when it was turned on, it was not in fastboot mode because of missing drivers. Finally it is being recognized and I can address the device via fastboot command.
And yet, I have the next brick wall. Any command I send via fastboot is answered by this output:
Code:
FAILED (remote: Command not allowed)
up to this point, I have not found one command that is being acknowledged and triggers another output, so I think it is a general problem. Maybe still with the drivers. Any hints would be celebrated. Anyways, in the meantime I will keep on trying until I succeed or until I get too frustrated and send it back and never try Sony devices again
not kidding XD
Click to expand...
Click to collapse
because your bootloader is not unlocked. you have set your bootloader to allow unlocking in developers options, but you need to do the actual unlock using "fastboot unlock" command. you need a unique unlock code from Sony Developers portal and keep in mind that unlocking your device irrevocably deletes DRM keys. it is advisable that you backup your DRM keys before unlocking your device.
the problem is not Sony device, but your unability to read and follow guides and get yourself informed and educated before you dive into trial and error, finaly blaming manufacturer for your own faults...
Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
owerevoke said:
Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
Click to expand...
Click to collapse
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Choose an username... said:
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Click to expand...
Click to collapse
Thanks, adb reboot solved it! Can't thank you enough!
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
svsavic said:
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
Click to expand...
Click to collapse
Same problem here.
But i do not know how to use ADB tool.
I dowloaded minimal adb fastboot tool and i have now 3 executable (adb, fastboot, MAF32) in a directory but I do not know how to use them in order to reboot my Axon 7.
I would appreciate a step by step guide, made for a very beginner.
Note also that I may not have already the device drivers on my computer.
Find cmd.exe in syistem32, run as administrator, drag adb.exe in cmd window. Write command adb reboot.
Impossible for me.
I am not even able to have the phone recognized since the drivers are not correctly installed and Zadig tools wont help.
I'm really stuck.
Would any Belgian Guys be able to help me having a computer with adb WinUSB drivers correctly installed so that we can reboot my phone with his PC with any adb tool ? Please PM me is so.
Phone is recognized as adb device (w/o driver). Just try this and write command adb reboot or reboot (i don't remember).
It is said that no devices is found.
?
Also had the same FTM problem and can confirm that power button did not work in stock Oreo.
If can't get adb reboot work, one simple way is to discharge the phone - USB type C connection is fully working in FTM mode (u can simply check that). Connect one or few (use simple usb spliter) USB devices (the best way is to connect devices, for example power bank, some bluetooth speaker, which actually suck energy etc.) to your phone in order to charge them and it will fully discharge the phone in a few hours. Then on phone turned off connect power charger, wait about 15-20 minutes to charge and turn on the phone as usual (using only power button for a few seconds).
Hello, i actually thought about this option of waiting for the battery to be discharged but did not dare to take the risk. I finally found someone that will "adb reboot" my phone tomorrow, fingers crossed.
Hi,
OK, let's hope that "adb reboot" option will succeed.
However, personally I see no risks in discharging the battery - when the phone discharges it just safely automatically turns off - no data loss, no need to reflash the ROM etc. I went through this route myself.
I think it could be another bigger risk to keep the screen on (not moving screen) for a longer time - possible burn in of screen etc. But not sure about this risk and don't want to frighten, maybe others have more knowledge on possible screen burn in issues. In my case after discharging the battery no burn in or other screen problems.
I ordered a OTG cable that should arrive tomorrow to discharge the phone if adb reboot does not work. Thank you for ur feedback.
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
billjim24 said:
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
Click to expand...
Click to collapse
that's not remotely useful to the situation
please read up before posting lmao
Mine Axon 7 did just that, couldn't turn it off in any way, also on b03 Oreo rom. So I let it discharge completely, and just did a normal power on, and it worked again.
I think that the Oreo Rom is in an awfully bad beta Rom rushed out from a sinking mobile company, that don't give a s... about their customers.
Will never buy ZTE again.
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Chinesur said:
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Click to expand...
Click to collapse
G B03 has daydream, hasn't it?
No, it doesn't have
Boot in FTM,open axon7toolkit,connect phone to laptop and follow instructions in axon7toolkit.It will reboot in edl and you can flash a firmware