Search the Community
Showing results for tags 'fastboot'.
Found 23 results
-
nokia 7 plus Fastboot doesn't recognize device but ADB does
Alfah1o1 posted a topic in Phones and Tablets
So I unlocked my bootloader successfully using techmesto's free boot loader unlock tool (Link to the guide) and i wanted to flash a twrp recovery. But when I boot into fastboot using "adb reboot bootloader" command and then try the "fastboot devices" command i get no output. But when I try "adb devices" in normal boot I get an output of my device's serial number. I also found out that some how techmesto's tool is able to recognize my device when in bootloader mode. I already tried various drivers from hmd gobal, google and universal adb drivers still no change and also tried it with different cables and different usb ports and finally tried it after a clean windows install too but no luck. so can anyone help me out of this situation as it's frustrating that I can't still do anything even after unlocking my bootloader after waiting all this time.
-
I have a Oppo Reno3 Pro CPH2036 which has an expired warranty so I decided to root it. I need to access the bootloader. I have tried some methods: - Volume up + Power Button : just boot like normal - "adb reboot bootloader" and "adb reboot-bootloader" : also boot like nomal I cannot get into bootloader/fastboot mode to unlock it with fastboot command on my computer (with my phone plug in though usb).
-
I have a new PC with an MSI motherboard andI have tried everything I've found. NVME is first (and the only thing) in the boot order. Legacy USB is disabled. Fast boot is turned on (Not the MSI Fast boot). XMP is enabled with the highest MHz my CPU works with. I do have a lot of USBs plugged in, but half are on a hub, and the boot time is basically identical with just my Keyboard, Mouse, Headset, and USB Wi-Fi adapter plugged in. This is not the original motherboard that was used when I put windows on my NVME though, that board was switched out, could that be the problem? Edit: I should state that last week it was around 20 seconds, I did all of the above, and got it to about 14 seconds, and just today it shot up to 25.
-
So I had this old redmi 4X chilling in the shelf and I wanted to use it...But with a different ROM I have enabled both USB DEBUGGING and OEM UNLOCKING option in the developers option and cross checked if its enabled before entering fastboot I lost my simcard tray...so basically I cannot use the MI UNLOCK TOOL either...... I have tried a lot of stuff from other threads in this forum for this specific phone and nothing seems to help...the same issue arises... have tried commands to enable bootloader , few people have made .bat files which they claim to install TWRP by just using it...nothing seems to help Any help would be nice -
on a Oreo Nexus 6P. No matter what I do, I get to this point and nothing shows my device as fastboot. I've tried everything I can find on the internet. Ive reinstalled drivers. I've reinstalled while at the fastboot menu (Power button+vol. down). I've tried it on two different PCs. USB 2.0 and 3.0. I've tried it in recovery mode, regular mode. I've tried all the drivers out there and driver installing tools. I've done this on a windows 10 machine and a windows server 2016 machine, same results on both. No matter what I do my device never lists in fastboot devices and because of this I can't flash anything or unlock bootloader. My device manager looks like this Im so stuck I don't know what is wrong. Can anyone provide some help? First time doing this is it a dumb mistake? It always lists when I do adb devices but never for fastboot. -
I am trying to flash TWRP recovery on my redmi 6A, but it dosn't work. I am using all the lastest driver, etc. I am using this method. Can someone tell me how to correct this.
-
I tried to install the stock rom on Mi A1 using my laptop which has only USB 3.0 and type C port. It was failing. Then i used the same files and installed the OS using my 7 years old laptop which has USB 2.0 port. I did some googling, where they were saying to install USB 3.0 driver from Intel instead Microsoft. I tried to download the driver, but none of the drivers are getting installing. Can anyone help on that? My System Config (Laptop Model : MSI GL63) CPU : i7-8750H GPU : NVIDIA GTX 1050Ti 4GB RAM : 16GB @2400Mhz
-
My spare smartphone was left turned off and charging but I come home to this and it won't turn on. Any explanation? Thanks.
-
TL;DR I have deleted everything off my phone using TWRP and now I can’t boot back into TWRP (it only automatically boots into fastboot mode). Have I done something wrong? If so, how could I fix it? Details So it’s my first time rooting an android phone and I have run into a problem. I recently bought a Xiaomi Mi 9T and went through the process to unlock and root it, because I wanted to install Lineage OS instead of using MIUI. I started following the LTT tutorial on modding the Poco F1 to look like the Pixel 3 (https://www.youtube.com/watch?v=BsHtfLh6azw&t=194s – not the Mi 9T, but I think any Xiaomi phone would have pretty much the same process), and it was going fine until you have to download and flash TWRP to the phone. I did it and it worked, and so I booted into TWRP and went to wipe the phone. The LTT video says to only wipe the “Data” portion, but I had read that when wiping a phone there’s no reason not to wipe other stuff as well, so I think I chose to wipe Data, Cache, Dalvik cache, Internal storage and System (it was a brand new phone, so I just wiped everything that made sense to start clean). Well after that I think I rebooted, but when it turned back on it booted straight into fastboot mode. I thought this was weird, but I just held the power button to turn it off (to boot into TWRP again to continue with the install of Lineage OS). Unfortunately, it booted straight back into fastboot mode, and ever since then I haven’t been able to boot into anything else (I can’t even shut it down, every time I hold the power button in it just automatically restarts into fastboot, so I just have to unplug it and wait for it to turn off itself). So I then tried re-flashing TWRP to start the whole process again and to boot back into it, but now I get this error message (see attached image). So my question is; have I done something bad by deleting all of the data and System OS at the same time? I’m worried that I’ve really messed something up by deleting all of the stuff I did, because I’ve read that it’s possible (however unlikely) to brick a phone by using TWRP incorrectly. Any help would be greatly appreciated.
-
After I activated fast boot I can’t just press delete key when starting windows to open bios, so I went through the windows recovery tab to open bios but every time I do it is just stuck on “cable not connected” on my monitor
-
I wanted to create this little post for people who try to flash the Xiaomi Mi4i FIrst thing first, if you don't own this phone, keep it that way and stay a mile away from xiaomi phones that aren't stock, damn things are filled with ridiculous amount of bloatware. (which led me to flash it, first time btw) The steps are pretty straight forward like any other ROM but keep few things straight and it'll save you hours. (I am not responsible for bricking your phone) Get your hands on this toolkit to save you the trouble - https://forum.xda-developers.com/mi-4i/development/tool-mi-toolkit-v4-root-twrp-stock-t3170607. Put your phone into USB debugging mode and fastboot (The info out there is outdated). Get your hands on Xiaomi stock ROM 6.5 or less (In my case I have version 9 and went through over an hour of bootloop figuring out what did I do wrong, all because I lazied out to install the older version). Connect your phone to your computer with device manager open and make sure it's detected properly (If not, look into it and get the right drivers or use a USB 2.0 port). Get twrp on your phone (Option 2, use the batch file made for you) remain within OS, let the toolkit boot your phone into fastboot for you (In my case doing it myself resulted the app from not detecting my phone, just like some videos stated, again outdated info). After successful TWRP installation your phone will still remain in fastboot, hold the pwr button for it to restart when it does for the split second make sure to press PWR + Vol Up to get into the new recovery mode (Another place I needed to spend over an hour figuring it out, for some reason MIUI was overwriting the new recovery mode every single time it booted (It will be fine after first successful attempt to get into new recovery mode). SAVE A BACKUP before doing anything, the option will be available within TWRP Under the wipe option do a factory reset (It will be the slider) go on installing the old MiUI rom, after installation do the factory reset again. Make sure to remain in TWRP and not setup the older MIUI that was flashed. Finally install the ROM you want to along with the Gapp files. You are set (I probably saved you hours of debugging and annoying bootloop). Gapp - ARM64, your ROM version of android and something smaller than stock. Stock or higher result in insufficient size error Root - Wasn't required
-
I am fixing a friends gaming rig, It has a problem that is beyond my understanding. IT has 2 SSD, 3 HDD. The OS is loaded on one of the SSD. Now when I disconnect all other drives it boots up in 10 - 15 seconds but when all drives are connected it takes around 2 - 3 minutes to boot up. The fastboot in bios is enabled. Motherboard : Asus Rampage 5 RAM : HyperX fury 8Gb x 2 Processor : intel i7 5th gen PSU : corssair 1200 Hx GPU : nvidia 1080 ti 11gb Cabinet : Coolermaster Striker Anti-virus : nil
-
Greetings! One of my friends would like to get some files off his OnePlus 3 with a broken screen. The screen is black and does not respond to touch. So my first thought when he came to me with it was to just plug it in a computer and run a ADB pull command and get the files off the device. Nope! Turns out the he has not turned developer settings on. This means that USB debugging is disabled. Then I thought "Maybe I could just flash a new recovery on the device and retrieve the files from that.". And again I was disappointing when I found out that of course the OEM is also locked. So no flashing TWRP on that device... So to summaries: Device works and can go in to fastboot or recovery (OnePlus stock recovery). OEM is locked and USB debugging is disabled, so no ADB commands... Fastboot commands work So now you are probably like: "Why don't you just buy a replacement screen?". Well you see I am going to do that later down the line, but I just wanted to pull the files as fast as possible. Any suggestions to what I can do at the moment?
-
Hi I wondered if anyone could shed any light on this issue I had. I'd be interested to know why it happens or if anyone else has encountered it. This is on a new build (Build details) that went very smoothly otherwise. Main suspects are the Asus ROG Strix H370-F Motherboard or the MSI - GeForce GTX 1070 8GB Gaming X Video Card I fire up VirtualBox which I use for work, and of course my VM won't boot as VT_X is off, by default I presume. So I reboot and hold down the old DEL key to get into the BIOS, except... no BIOS, just black screen. I think it's POSTed to BIOS because powering off from the front panel is instant, the diagnostic Q LEDs on the motherboard are all A-OK. Boots into Windows fine. Hmm. Inspiration strikes, so I go and reset the CMOS with a jumper pulled from my old board. Reboot and.. no BIOS screen still and also no boot into Windows. I deduce it's waiting for an F1 keypress to choose the boot device which this BIOS does on first boot, even if there's only one boot device. Try removing the GPU and booting off the mobo HDMI, still no dice. I then try the thing that I probably should have first and hooked up the monitor via DVI. Boom - BIOS screen appears. So I can now turn on VT_X. I also turn OFF the EFI "Fast Boot". I also now get BIOS screen displayed correctly over HDMI -
sfully) locked my bootloader on my OP3 running Android 6.0.1 which in turn completely wiped both the OS and the custom recovery I had installed (TWRP). I'm now stuck trying to bypass the locked bootloader as fastboot commands require OEM Unlocking to be turned onn in Developer Settings which cannot be done on account of there now being no os on the thing. Any and all help is appreciated more than you will ever know <3 -
After not having used my pc for the past year all I could think about was firing it up and starting gaming again. As expected there were many updates to be installed, but after installing the 1709 update, my pc reboots to a black screen or continuously shows a frozen post screen. After a few reboots Windows decides to undo the update and I'm back again with my desktop and everything working. After this happened a few times I decided I'd just reinstall Windows and be done with it. I make a new bootable USB drive aaand it boots to a black screen when trying to install Windows. I decide to dive into UEFI and disable the Windows 8 features ( fastboot and secure boot ) and I'm fully able to update and reinstall Windows without any black screens. Enabling fastboot and putting an old Windows 10 ISO on the USB drive also installs perfectly, until Windows forces itself to update again. So, from what I can gather, is that the Windows 10 1709 update breaks fastboot with my motherboard (MSI Z77A-G45). I'm on the latest UEFI firmware, my VBIOS is updated, I've reset CMOS. No matter what I try, I can't get fastboot to work with the latest Windows update. Does anybody have an idea what could be a solution to this problem? Or am I just doomed in running Windows 10 without fastboot from now on?
-
I just upgraded my gpu, processor, ram and motherboard. Everything is working fine yesterday and now for some reason i am now stuck at "reboot and select proper boot device.." i turned on fastboot yesterday and now my pc wont let me press any key to access bios cause my pc is booting too fast to the point that i cant use my keyboard. Im not sure what to do now, i tried searching still stuck at that message. Im using msi b150m nightelf. EDIT: i manage to get into the bios thankss. What should i configure now? Thankss
-
I own a Nexus 5 Hammerhead with the latest software updates. While I was using it normally, it suddenly turned off (without a shutting down animation) and it couldn't turn on, a lot of glitches appeared with the turning on animation. I tried to factory reset it from the phones bootloader, but it wouldn't allow me. I've also tried to manually flash and reinstall the system image, but the writing of it would always fail. Does anyone of you have a solution?
-
I have MOTO G3 XT1542 with Android 6 and it's been working extremely bad since I upgraded it from Lollipop, I want to Unlock the phone for either installing CyanogenMod or downgrading to Lollipop: First step for unlocking is enabling Developer Options and Inside Developer Options enable OEM Unlocking, well... I dont have OEM Unlocking! Well.. I've been reading "If it doesnt appear it's not necessary to enable it" Alright I Skipped step one, I requested my Unlock code and got to the last step where I have this error "Bootloader error make sure you enable OEM Unlocking in Developer Options" so..? The crazy part is that if I go to settings and I touch the Search icon and I write OEM, it appears, it finds it but after tapping me it takes me to Developer Options where it's not there... My friend has the exact same phone from the same career and he has the option. I really need to get this fixed somehow, Android 6 is really buggy i've encountered a problem today that there is no lock screen, home button won't work and notifications bar wont work (doesnt show notifications and doesnt even scroll down)
-
Hey guys, Is there any reason to have fastboot disabled in the UEFI? And how much of a difference does it make when booting? Would you recommend using it? Thanks to all of you Motherboard: Asus M5a99x evo r2.0 CPU: AMD FX-8350 (at 4 ghz because of my bad cooler...)
-
Hey guys, I accidentally wiped everything in TWRP (most importantly the 'system' partition) and somehow managed to relock the bootloader. So now I am left with a device that can only boot into fastboot mode because else it's stuck in a bootloop and that I can't flash anything onto because of the locked bootloader. Fastboot reboot(-)recovery isn't a command apparently, although I've read that it worked at some point (in an older version maybe?). When I am trying to "flash all file.zip" fastboot 'stops working', but not only on my desktop but also on my notebook. The zips (yep, tried multiple) don't seem to be damaged (Tested in WinRar) and I also tried reinstalling fastboot/adb multiple times with different setup .exes. I am running out of ideas here - I basically need something to unlock my bootloader without sending it into a bootloop when rebooting afterwards. Any ideas? Help is very much appreciated! -
I am trying to root my HTC One M8, but everytime I try the command: fastboot oem get_identifier_token, It stalls at <waiting for device> I am only at the unlock bootloader stage, I have not installed any custom recovery yet. If you could please help me with this, that would be so kind of you. (P.S: I have just installed all the new drivers and things required today, all drivers are up-to-date)
-
Help!!! please! It all started long ago, when Asus's nexus 7 tablet decided not to get along with Android 4.4, and bootlooped itself. So, off to my friend to fix it! Well, the jerkface unlocked the tablet and put cyanogenmod on it, instead of just putting lollipop or jellybean on it. So, I try to use Nexus Root Toolkit to flash stock back on the tablet, as Cyanogenmod itself was having crazy troubles, and crashed every app I had, and didnt work properly. So, I attempted to flash Android 5.0.0 onto the tablet. I thought I had set up the drivers right, and the command prompt went through fine, but the tablet just sat there, with that evil white google sign staring me in the face. The tablet is unlocked. I contacted ASUS, and they refused to help me because it's unlocked. I can't enter bootloader, yes, I have tried power and volume up. I can force shut down the tablet with power and volume down, and turn it on. That's it. It doesn't boot, and it won't enter fastboot or bootloader. Anybody... Please...
