I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X
1xcalibur1 said:
I've been searching all over the place...
Could anyone point me at a guide for newbs?
Thanks!
X
Click to expand...
Click to collapse
First, you need your bootloader to be unlocked. It's pretty easy if you have that done already.
You'll need ADB and Fastboot. It can be tricky to get the right drivers. The driver used when your phone is connected in normal mode is not the same when connected in fastboot mode, in my experience anyway. You'll want the 15sec ADB driver and you'll need to update the driver when it is in fastboot mode.
Next, get the correct twrp img and put it in the ADB folder(you'll need a different one based on flashing a pie rom or a q rom). You may want to rename it so it's easier to type in fastboot.
To enter fastboot mode, hold volume up and plug in the usb cable. The LED should light up blue.
Open a command prompt and navigate to wherever you've installed ADB(mine is on C:\ so it's really easy).
Type "fastboot devices" to double check if the driver is installed and your phone is connected in fastboot mode.
------It should show something like: BH9090808E fastboot
Then type "fastboot flash recovery twrp.img" - or whatever you've named the file. It will take less than a few seconds.
Then type "fastboot reboot" and let your phone reboot.
Done
Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!
1xcalibur1 said:
Thanks a lot for the reply!
I've been experiencing the exact issues you described. I'm having issues unlocking the Bootloader. "Fastboot.exe devices" does not show anything, the phone is with a blue led on and a balck screen and when I look in Device Manager there's an "Other" Android device with an "!".
Could you please share the drivers you mentioned? Because I really went through
everything and none was accepted. Also the 15 Seconds ADB Drivers did not help.
Thanks!
Click to expand...
Click to collapse
My apologies. It's been so long since I've started from scratch, I must've gotten the drivers mixed up. The 15sec ADB is for the phone connected in normal mode.
I'm pretty sure this one is the fastboot one:
https://developer.sony.com/file/download/xperia-xz1-compact-driver/
If not, I'm sorry because that's all I have.
I nailed it eventually!
For anyone that comes across this thread,
this video will solve all your problems with adb drivers:
Related
Last night I was on my nexus before I would go to bed. I opened the franco kernel app and then noticed that r6 was available for download. I downloaded and flashed it and was about to go to sleep when I noticed the notification light that my phone was charging. I thought it was neat then tried to get some sleep, but my promised sleep did not come quick. After a good chunk of time had passed, I thought that my lack of sleep was caused by the green light that was barely noticable. I searched and searched in the app to try and find an option to disable the LED, but could not. I then decided that the best way to get rid of the light, would be to flash the older r5 kernel so I wouldn't have to see the light anymore. I hit flash and my phone rebooted and then brought me to the bootloader. I attempted to reboot but I could not. I've tried using adb and nexus root toolkit to get my device to work again, but they can't seem to find it without the correct drivers. I installed Motorola device manager, nothing. I tried to follow the instructions in the toolkit to get the correct drivers installed but I can't continue with the need to enable debugging, which I cannot do from being stuck at the bootloader.
Under bootloader logs, I have the following messages:
Invalid boot image size!
failed to validate boot image
Fastboot Reason: Fall-through from normal boot mode
Any help would be greatly appreciated.
USB debugging is an android setting. It can only be used when android is running. If you had USB debugging on, it would make absolutely no difference in recovery or bootloader so don't let that step stop you.
From the logs, it sounds like your kernel download is corrupt or didn't flash properly. I had a similar message when I flashed a partially downloaded recovery image today.
Just fastboot flash a complete boot image
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
thecupman said:
I tried that last night by launching adb and doing 'adb devices' but my device is unrecognized and I am unsure of how to go about fixing that.
Click to expand...
Click to collapse
Tried what exactly? Adb and fastboot are two different things. Adb works in android or recovery only. Fastboot works in boot loader only. Boot to boot loader and do "fastboot devices"
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
thecupman said:
Ah that was my mistake. But the fastboot devices command just returns a new line for a new command to be entered in
Click to expand...
Click to collapse
That probably means there is a blank line between them - showing that no device is found. Unlike Adb it just gives a blank line instead of "no devices".
Probably means a driver issue or cable issue. Try different USB ports / cables if you can. Check to see if there are any yellow triangles in device manager too.
I'm new to this phone so I don't know where the drivers are if you need them. If I ever find them, I'll port my nexus 5 Adb and fastboot thread over here. Unfortunately i use Linux at home so I don't really have a driver issue.
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
thecupman said:
Oh, so if I were to use Linux I wouldn't have to deal with missing drivers? I'm assuming that's the issue since no matter which port I use, 'Connect USB Data Cable' doesn't change
Click to expand...
Click to collapse
I can't say for sure. In Linux you may need to add UDEV rules. I didn't though. My bootloader is just recognised.
Please do check your device manager though.
I'm sorry i can't help more right now. I'm going to bed.
Okay, thank you! I'll reply if I encounter any other errors!
The Google driver works for all Nexus devices (except the GNex): http://developer.android.com/sdk/win-usb.html
Hello guys,
I have 3 identical phones i-mobile IQ2. They are shared among our family.
Mine (fortunately) is runnng fine. The 2 others not so. That's the reason why I want to flash a different ROM.
I have 2 Computers, One with Windows, the other Linux. Both are equipped with adb/fastboot.
What did I do?
1) enabled developer options in the settings.
2) enabled USB debugging and OEM unlock in developer options.
3) Connect the phone via USB
4) Terminal command "adb devices" shows correct serial number of the phone
5) and here it starts. After typing "adb reboot bootloader", the phone shows the white i-mobile screen which is shown when you enter fastboot mode. But....
6) "fastboot devices" results in the terminal message "waiting for any devices"
And that's it. Nothing happens. Retried with 2 phones and always the same. The funny thing is that on my identical phone, there is not a problem and typing "fastboot devices" results in a proper recognition of my phone.
So.... is there anything that I could have done wrong or that I forgot? How can I unlock my bootloader in a different way? As far as I know, adb commands are usually the last resort.
I would appreciate every help. Thanks
You need to install fastboot drivers for your device when your device is in fastboot mode as I know.
here is the right drivers for me in the whole internet: https://mega.nz/#!YcUABBpR!_8w6S5zj_Ct2eBMPr6cL1d1NhC4AZEfphOSQJRJZmjU
I had the same problem on my gm4g nd i solved installing the correct driver just like nhmanas said. Good luck.
nhmanas said:
You need to install fastboot drivers for your device when your device is in fastboot mode as I know.
here is the right drivers for me in the whole internet: https://mega.nz/#!YcUABBpR!_8w6S5zj_Ct2eBMPr6cL1d1NhC4AZEfphOSQJRJZmjU
Click to expand...
Click to collapse
Ok, I will try and get back to you again. Thanks for now.
I tried the guidelines to boot into bootloader, I'm using xz2 non premium/compact, I press vol- a while and connect USB cable to PC but I never boot into bootloader, even when I try using adb command "adb reboot bootloader" it just reboot into normal system, what can I be doing wrong?
Also I have no update, I'm still on 8.0.0,I keep checking and it says you're using latest Android version, how come?
[email protected] said:
I tried the guidelines to boot into bootloader, I'm using xz2 non premium/compact, I press vol- a while and connect USB cable to PC but I never boot into bootloader, even when I try using adb command "adb reboot bootloader" it just reboot into normal system, what can I be doing wrong?
Also I have no update, I'm still on 8.0.0,I keep checking and it says you're using latest Android version, how come?
Click to expand...
Click to collapse
Use xperifirm and newflasher to flash the newest firmware.
Both programs are available on XDA.
MartinX3 said:
Use xperifirm and newflasher to flash the newest firmware.
Both programs are available on XDA.
Click to expand...
Click to collapse
Do you Know of any tricks to boot fastboot/bootloader,I want to unlock it, the current methods not working,I get a black screen and green/blue notification light (-vol and connecting USB cable from pc to phone) when I input fastboot commands, it says "waiting for available devices" and fastboot devices says no device connected, but adb devices (when in normal boot) recognises my device
Sent from my H8216 using Tapatalk
[email protected] said:
Do you Know of any tricks to boot fastboot/bootloader,I want to unlock it, the current methods not working,I get a black screen and green/blue notification light (-vol and connecting USB cable from pc to phone) when I input fastboot commands, it says "waiting for available devices" and fastboot devices says no device connected, but adb devices (when in normal boot) recognises my device
Sent from my H8216 using Tapatalk
Click to expand...
Click to collapse
Then the fastboot driver doesn't work correctly, is not correctly installed or the wrong got installed, while the adb driver is fine
similar problem: fastboot issues
I apparently don't have standing to post my own thread, so I'm replying to this one which is similar. My apologies.
I've downloaded adb and fastboot on my win 7 machine to unlock my bootloader on the way to rooting my xz2 compact. Fastboot will not recognize the phone. Adb does recognize it, and fastboot recognizes my Moto X DE, so both utilities seem to be working fine. Additionally, using 'adb reboot bootloader' cycles through a green, red and then a faint blue led, the latter which just stays there continuously with a black screen.
I've spent quite a bit of time on this looking for a solution, so I'm turning to you all for help.
dmm108 said:
I apparently don't have standing to post my own thread, so I'm replying to this one which is similar. My apologies.
I've downloaded adb and fastboot on my win 7 machine to unlock my bootloader on the way to rooting my xz2 compact. Fastboot will not recognize the phone. Adb does recognize it, and fastboot recognizes my Moto X DE, so both utilities seem to be working fine. Additionally, using 'adb reboot bootloader' cycles through a green, red and then a faint blue led, the latter which just stays there continuously with a black screen.
I've spent quite a bit of time on this looking for a solution, so I'm turning to you all for help.
Click to expand...
Click to collapse
The bootloader is just black with blue led.
Download mode is just black with green led
Recovery is just recovery with red led
System is just system with all led Colorado or none
fastboot
MartinX3 said:
The bootloader is just black with blue led.
Download mode is just black with green led
Recovery is just recovery with red led
System is just system with all led Colorado or none
Click to expand...
Click to collapse
That's helpful, thanks. I am fastboot mode then. I am used to a menu screen of some sort. How do I get to one of those?
dmm108 said:
That's helpful, thanks. I am fastboot mode then. I am used to a menu screen of some sort. How do I get to one of those?
Click to expand...
Click to collapse
Please look into the twrp chat
Yes, my Nexus devices had bootloader menu's
fastboot
MartinX3 said:
Please look into the twrp chat
Yes, my Nexus devices had bootloader menu's
Click to expand...
Click to collapse
Sorry, if didn't communicate this well. I need to unlock the bootloader using the fastboot command, yet fastboot overtly doesn't recogize the device. (no recovery screen menu is a separate problem). so,
'fastboot oem unlock' returns
'< waiting for any device >'
even though the phone is recognized by adb and other phones are recognized by fastboot.
How do I get the phone to be recognized by fastboot is the main issue.
dmm108 said:
Sorry, if didn't communicate this well. I need to unlock the bootloader using the fastboot command, yet fastboot overtly doesn't recogize the device. (no recovery screen menu is a separate problem). so,
'fastboot oem unlock' returns
'< waiting for any device >'
even though the phone is recognized by adb and other phones are recognized by fastboot.
How do I get the phone to be recognized by fastboot is the main issue.
Click to expand...
Click to collapse
Try a Ubuntu Virtual machine with usb passthrough
Best distro for phones - Manjaro
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!