Hello all,
I have a Pixel1.
I was going to flash it and open the bootloader before. Everything prepared and plugged into the PC.
Via "fastboot reboot bootloader" I wanted to put the device into the bootloader to unlock it afterwards.
However, the device now does nothing.
Neither Power+Volume down does anything.
If I connect the device to the PC, the device is shown in the device manager as QUSB bulk.
Can anyone help me?
Letty said:
Hello all,
I have a Pixel1.
I was going to flash it and open the bootloader before. Everything prepared and plugged into the PC.
Via "fastboot reboot bootloader" I wanted to put the device into the bootloader to unlock it afterwards.
However, the device now does nothing.
Neither Power+Volume down does anything.
If I connect the device to the PC, the device is shown in the device manager as QUSB bulk.
Can anyone help me?
Click to expand...
Click to collapse
It's in emergency download mode (edl mode)
It may boot normally after battery dies.
If not you would need a blankflash for sailfish
I don't think there is one available for your device.
Edit: or mmcblk0.img for sailfish
Related
Hi guys,
i have a tricky problem.
I bought a used nexus S, without any hope to recover it.
This is the state at the moment (after installed SDK and drivers).
I think the device is in his standard state (all locked up, never rooted, stock rom)
It boot up and ask for a password to encrypt device (works : volume and emergency call).
If i connect usb, he tries to mount USB storage but he dosen't success.
I connect to pc and pc see an Android ADB device in the devices list.
BUT if i lauch 'adb devices' i dont see anything.
I start it in bootloader mode (Vol Up + Power) ... it starts.
BUT Vol Up and Vol down didn't work. I can only press power and return again in bootloader. (volume work if i normally boot)
In bootloader state i tried 'fastboot devices' and i didn't see any device.
So the state is :
Bootloader i think "broken" (volumes dosen't work and fastboot dosen't see device)
Debug usb disabled (adb don't see my device)
Device encrypted
Any idea ?
I think is a nice problem to let your brain works on :laugh::laugh:
Thanks in advice.
Daniele
Hey guys, there is anybody out there ?
I dont think that no one could try to solve this problem.
Thanks
Do you have the drivers installed onto your PC? You will need to get the adb drivers and fastboot drivers. Download Samsung Kies and that will take care of your ADB drivers. Click here: http://www.mediafire.com/download/5a7gou9droidi53/drivers.rar for your fastboot drivers. Hope this helps.
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
sirhaplo said:
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
Click to expand...
Click to collapse
I'd suggest just booting Linux and doing whatever you need to do in there.
The kernel already supports communicating with the Nexus S, no need to mess with drivers like on Windows.
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
xMTOOLO said:
My device is a One Plus One. I've installed an ADB driver from here: adbdriver (some site I've searched up on google) (Is this even safe? I've never seen anyone use this link before or maybe it's new. It's not a virus is it?)
So once I've installed it, I've typed all commands such as adb while my device is turned on but then when it gets to where I have to press my powerbutton+volume down and then go into the recovery screen, I see "Cyanogen Recovery" or whatever but that's what it says. Suddenly on my computer, the ADB device disappears altogether and I cannot see my One Plus One storage anymore (it's connected and even If I unconnect and reconnect it's still the same). I believe I've unlocked my phone already before so is this why? I just want to make sure and type fastboot oem device-info but when I type that nothing comes up. I've been trying to solve this and I don't know what to do anymore... Is it because I've already unlocked my device (but even I'm not sure if it's still unlocked and that's why I'm trying to confirm it by typing "fastboot oem device-info" which doesn't even work. Help please!
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the expert help you need, I'm going to move this thread to your specific device Q&A forum.
Good luck!
You need to boot into bootloader by pressing volume up + power.
Then you can use "fastboot devices" to see if your OPO is being recognised.
"fastboot oem device-info" only works when you boot to bootloader
ADB is not fastboot btw.
http://www.androidcentral.com/android-z-what-fastboot
ADB does only work when your phone is booted to the Android system and USB-Debugging is enabled
http://www.androidcentral.com/what-adb
Power + Vol Down pressed together gets you access to the F1's limited recovery mode.
Power + Vol up does not get you into the bootloader.
When you connect the phone to your PC it automatically loads its USB drivers to the PC with your consent.
ADB can see the phone once the USB drivers are installed and the phone is connected via USB cable.
ADB DEVICES provides the serial number of your phone.
ADB REBOOT RECOVERY gets you into the recovery mode mentioned above.
ADB REBOOT BOOTLOADER simply reboots the phone.
FASTBOOT can't see anything.
FASTBOOT DEVICES doesn't yield serial number.
Other FASTBOOT commands sit "waiting for device".
So FASTBOOT just does nothing useful. A google search shows that this behavior is known and people think that using different drivers overcome the problem, but I tried a number of driver solutions with no success. I just think that they've closed the Oppo F1 up rather tightly.
-----
ETA: Just heard elsewhere from a semi-official source that FASTBOOT has been disabled on the F1.
I just saw this "Decision by Oppo: No Bootloader/Fastboot access for Oppo Phones starting 2016" from here > http://forum.xda-developers.com/r7-plus/help/decision-oppo-bootloader-fastboot-t3348114
If this is true, the F1f will be our last oppo. It's not a big issue for the F1f as it's my wife's phone but I will avoid locked phones on principle now. Even Huawei are making it hard to unlock bootloader so my Mate 7 could be our last Huawei.
Guys anybody tell how to flash 'magictricks' zip to unlock boot loader and to flash twrp recovery safely...
I'm week in commanding adb devices and fastboot so I need steps,help will be thankful.
Sent from my F1f using XDA-Developers mobile app
friends. I want to flash myphone (flash tool) windows 7 but do not see it. even I reinstalled windows 7, but did not see. last driver installed on the MTK what to do - I do not understand
agreed. another computer, another cable, another driver (for flash tool)
Hello everybody,
My phone had some weird glitches, factory reset didn't work, and the capacative buttons didn't work anymore, and I had to restart the play store to install the apk after it downloaded the app. I made a new User, the buttons worked again and I could normally install apps. But it was a temporary fix, and as I couldn't factory reset I decided to unlock my bootloader because that resets your phone. So what I did is:
1. I installed all the proper drivers
2. I opened an commandprompt in the adb folder
3. I typed adb devices, it said unauthorized, I authorized it on my phone, and it said that it was authorized after that.
4. I typed adb reboot bootloader
5. I waited untill it went into fastboot mode and typed fastboot oem unlock (I had the function to unlock the bootloader enabled in developer options).
My phone rebooted after this, now it only shows the OnePlus logo and powered by android, it doesn't boot further. I can't return the phone as I bought it second hand. When I connect the phone to the laptop that I used for it (The usb cable was connected directly to the motherboard, incase that matters and it was an original 4 pin samsung cable), it recognizes it as an Android device, so I think it's a soft brick.
How to fix this? Thanks in advance.
-Oczosinkoo
Hi !
You can try this tutorial
https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Good luck !
Hi All
I have ROG 5s tencent edition. it was modified by seller to global. I have been using it for more than 1 year now. Last night something happened and it went off. I tried turn it on but it kept bootlooping at logo. It is not detetedable by computer because bootloader was locked by seller before selling. I had no idea about that at that time.
MY device is now in bootloop. I can open bootloader but it won't take me to recovery mode. Fastboot commands are also not working . Phone not found by computer in any state. Can any one provide me with some pointers on how an i flash firware,
Recoery is not opening. When I select it from bootloader it keeps bootlooping
Fastboot is not seen by computer. Tried many cables, both ports.
If anyone can guide me that be a huge favor as this is my daily driver
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Andrologic said:
Your device should be dected in bootloader mode even if it has been locked. Connect via the side port with a good data cable and check drivers on Windows.
Once you have verified you have access to send Fatboot commands to the device in Bootloader mode, you can simply do a RAW flash to any working version and then upgrade normally to the firmware version you want. You don't need unlocked bootloader to flash this way.
Click to expand...
Click to collapse
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
dksoni411 said:
I have tried but it is not detected as anything. Not even unknown device. I have installed qualcomm drivers. What other drivers are there? Could u tell?
Click to expand...
Click to collapse
If there isn't a hardware issue with the device, you should be able to.
Try to delete the driver and re-install it. Use the official Android USB driver from the SDK as opposed to Qualcomm drivers from random places on the net. Plug it in from the side port and try to turn it on while connected. Have Device Manager in Windows open and notice changes. Read out what it is recognized as. If absolutely nothing, then it's the cable, Windows or the device may really have a motherboard defect.
I believe it's more likely motherboard. Is there any fix for it?