So I just purchased a used Oneplus One off of Swappa (seller claimed phone had been used for 1 week, minimal damage, etc.) and upon receiving it and trying to boot it, I was greeted with a bootlook where the phone never makes it past the boot animation (the oneplus logo with android at the bottom). I figured the easy solution was to simply sideload a stock image of the latest software. However, when I put the phone into fastboot, it would not be detected by either adb or fastboot. I know the phone is rooted and unlocked, but because I cannot turn it on, I cannot tinker with any USB-related dev settings. I have reinstalled android sdk, adb, fastboot, and the google usb driver, all to no avail. Even tried all of this on a second Windows laptop. Is there something I'm missing or is there some fix to have this phone detected while in fastboot? The phone is the Cymd edition with stock recovery. Thank you.
Related
I have a Moto G (from Republic Wireless) and started having the Boot loop problem.
When I try to go for fastboot, then volume up to select recovery, the motorola logo appears, but no android logo after. Then the boot loop starts again. Anyone help me please?
Did you flash an older android version?
Same same but different
I have the same issue. Although I actually get as far as to getting to the lock screen and unlock that and then I get about 3 seconds then I get the 'Powering Off' message and the phone turns itself off.
I have enough time to go in and put it in debug mode but the phone never recognises the computer once in bootloader, I think it most likely have something to do with the driver for 'Fastboot falcon s' not working. Can't install a new one or in any way make my phone communicate with my computer. Have all the latest Moto device manager stuff installed too. I also think I have the wrong firmware installed (US and not AUS version) along with a heavily corrupted (or even completely missing) recovery image.
Have tried flashing a new recovery image but I keep getting either a blank response from 'adb devices' or 'fastboot devices' and whenever I try and issue a command that would hopefully result in anything other than the **** I am currently stuck in I get a 'waiting for device'.
All this because I tried to go from Unlocked Bootloader and CM11 (that wouldn't let me use mobile data or kept crashing on me, like 24/7) to stock Android and Relock the Bootloader.
I am pretty much losing my **** here, just happy it was only a $250 device though.
Does anyone have anything on this?
oh well, giving up on this. Contacted Republic Wireless and and they're sending me a replacement.
Good evening ,
Yesterday I did a very stupid thing, I was trying to update my phone to 5.0 Lollipop, I found a way to do it with flashify but instead of taking the custom rom image I chose the stock rom downloaded from ASUS website, since then the phone won't go past the ASUS logo, I can only get into recovery mode, can't get into fastboot. I tried deleting the cache and then factory reset, to no avail, phone turns on, ASUS logo appears and then the screen goes black, then blank and that forever.
I tried to user fastboot with the phone plugged in recovery mode, ADB recognizes it, device manager sees it (both Android ADB and USB Composite Device), no exclamation mark, latest drivers installed, both from Intel and Google but it doesn't show up when running the cmd fastboot devices, nothing worked, I don't what else to do, hope someone can help me.
Asus Padfone Infinity Lite, 32GB TW version, can't remember the number though
Thanks for reading!!
Hi all,
I have a Nexus 5 that I bought second hand. It powers up but is stuck in a bootloop. The Google Logo appears and it starts to load but it does not progress. I can get in to boot loader and I have tried to do a factory reset but it it still stays in the boot loop. I have tried to install the new factory software using the Nexus Root Toolkit but nothing. The Phone is also locked and I cant unlock the phone so the Nexus Root Toolkit wont allow me to try to flash the stock image? I am at the end of my knowledge base as I have tried almost all the normal methods to unbrick and fix the boot loop. The Phone can access the boot loader. When I try to unlock the phone using the Nexus Root Toolkit, it unlocks it but does not write the data and it becomes unresponsive! I have no idea if USB developer is on in settings as I have never got in to the Android operating system as I cant get past the bootloop.
Your help and suggestions would be most helpful as I am now at an end of my abilities until I am further educated about how to resolve the issue.
Res
I haven't tried this myself (no need), but since you seem to have nothing to lose give it a go. It's official Google, and comes with instructions.
https://developers.google.com/android/nexus/ota#instructions
Does the fastboot oem unlock command work?
Do you have all the correct usb and adb drivers installed??
First off, I suggest doing some reading up on adb and fastboot. Then manually flash factory images first and try to boot the phone completely.
The links @dahawthorne will help a lot.
Then try the command that @audit13 mentioned.
Hey guys, I've got a Kyocera Brigadier and I decided to change the runtime from Dalvik to ART. Now the phone is stuck on loadscreen and I don't know how to fix it. The phone is rooted using the KingRoot app, but I don't know if that would help in any way.
Please help me guys!
Similar Issue
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Ornias Abezethibou said:
I am have a very similar issue, I also rooted my Brigadier with Kingroot and all went well. However, I attempted to flash the Xposed Framework onto it using Flashify. After doing such it got stuck in a bootloop, I was able to fix that problem by booting into fastboot mode and using fastboot to push stock firmware back onto my device. However now I have an even bigger problem where my phone boots up to the Powered by Android screen and then to the Kyocera screen, however instead of continuing to boot to the Verizon Wireless screen and then into the phone, it gets stuck at a black screen. I have tried waiting for hours and nothing at all happens, also I can no longer seem to boot into fastboot mode or in other words the Powered by Android screen with the little 1 in the top left corner of the screen. Fastboot nor ADB recognizes the device when plugged into my computer, as neither list anything when ran. Please help, I don't want to have to pay and end up sending my phone into Verizon to be unbricked.
Click to expand...
Click to collapse
I have the same problem. I bought a new a Brigadier that was on 4.4.2. I rooted with Kingroot ran update and now my phone will not boot past Kyocera screen. It goes black with the back light on. Did factory wipe and still nothing. I am shocked that KK has killed yet another phone of mine. I very much dislike KK ROM. What did you find out?
Hello everyone,
I have a European H870 and unlocked the bootloader, used ADB/FASTBOOT to install TWRP but could never get to start in recovery because of a warning screen that shows up because it is unlocked.
Couldn't get into recovery from both ADB or by utilizing the keypress method. Vol-down+power --> logo --> release power for 1 sec then back on it. I even tried with other variants of that but could never get into recovery or DL mode. What's the point of unlocking the bootloader if you can't do anything afterwards because of a stoopid warning screen?
I never had that issue with my Samsung Mini S3. But with the LG's that I have, since the bootloaders were locked, the phones display this warning screen upon powering up. I can't be the only one with this issue unless I was doing it wrong. But I wasn't. So...anyway.
So with my G5 H850 I got around this problem by using FASTBOOT FLASH RECOVERY TWRP*.IMG and then FASTBOOT REBOOT before using ADB REBOOT RECOVERY during the boot process to get into recovery before the phone had fully booted.
So I tried the same with the G6 H870, of which I also cannot get into DL mode or recovery because of this screen. The only difference was that there is something different about how the H870 loads the system so that I could not run ADB commands until the phone was already 100% booted and thus rendering my recovery flash useless.
I ended up doing something that caused my phone to always boot into fastboot so I downloaded what I thought at the time was the correct boot.img and flashed it. And now I'm at the current situation where the phone boots past the warning screen and into the logo screen but then stops for a few minutes before rebooting. This process endlessly repeating. It is obvious to me that the boot.img was incorrect.
So what I have done so far is loading all Qualcomm drivers, LG drivers, QFIL and QPST (drivers being installed or uninstalled for each instance that requires them). The problem now is that the phone shows up on a COM port but is is unrecognized to all the different software and thus can I not communicate or flash anything to it.
A couple of unbricking procedures that I tried are:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
https://androidmtk.com/use-qpst-flash-tool
There were more but I cleared my browser's memory.
So, do I need to invest in an Octoplus device to get past this or is there another way?
Thank you.