Hi,
I bought my OnePlus One (64 GB Sandstone Black) in September 2014. Since I got the phone, everything was running very quickly & smoothly. I did not have any problems with it, so I was very pleased with my brand new phone.
I did not tamper at all with my OnePlus One phone and every time there was a new OTA update, I updated it with the latest version. Currently my OPO has the latest Cyanogen OS 12 OTA updates (CM12S).
Last Friday I used my phone and everything was running very good, as usual. I shut down my phone and went to bed. The next day, on Saturday morning when I turned on the phone, it started showing the OnePlus One logo (with the text "powered by android"). Then CYANOGEN logo appeared on the screen and nothing happened. I waited near my phone for half an hour and nothing happened, it kept showing the CYANOGEN logo. It's like a cycle that never ends. So now I am facing a huge problem with my OPO: every time I press the power button, my OnePlus One gets stuck while booting, showing only the CYANOGEN logo. :crying:
Please see picture "OPO stuck on booting - shows only CYANOGEN logo.JPG".
As I said before, I did not tampered with my OPO, I did not flash it, I did not installed any ROM, I did not installed a custom recovery. Also, I did not drop my phone, so it is in good hardware condition. Every time there were new updates, I updated it with the latest OTA updates. I did not have any issues after the updates, so I don't understand why now it gets stuck on booting (especially since before this problem appeared, everything was working great, as usual).
I read through the forums, the internet and tried to find several solutions, without wiping my data. Any solution that I found did not work and I could not fix this problem (OPO stuck on booting, while showing the CYANOGEN logo). After two days in which I could not use my phone, I removed my SIM from the OPO and now I am using a normal phone (only for calls and SMS).
After my OPO gets stuck while booting, showing only the CYANOGEN logo, I connect it to my laptop using the USB cable (the same one used for charging), but I cannot access my files. Before this huge problem appeared, I could easily connect my OPO to my laptop. Please see pictures: "Connecting my OPO via USB - Installing device driver software - Step 1.JPG" and "Connecting my OPO via USB - Installing device driver software - Step 2 - Failed.JPG". I updated the drivers, but it did not work.
Ever since I got my phone, I have never unlocked the bootloader or rooted or anything of that sort.
I have never even touched any fastboot/adb commands since I got the OPO, until now, when I have this major problem with it.
After reading the forums, I started my OPO in Fastboot Mode and used 2 commands with fastboot.exe (Please see picture named "OPO Fastboot Mode.JPG")
Results below:
******************************
F:\OnePlus One tools>fastboot.exe devices
b01c5f88 fastboot
F:\OnePlus One tools>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
******************************
I do not understand why "Device tampered: true", since I have never unlocked the bootloader or rooted or flashed or anything of that sort ever since I got my OPO. I did not tamper my OPO, so "Device tampered" should have been false.
I also tried to use ADB, but it does not work. Please see below:
******************************
F:\OnePlus One tools>adb devices
List of devices attached <--- THIS LIST IS EMPTY, IT DOES NOT SHOW MY DEVICE, SO ADB DOES NOT WORK AT ALL
******************************
I want to save my media files (pictures, recordings, clips, audio files), my documents and messages.
For other suggestions found on the forums, I did not use at all, because I do not want to erase all data of the phone.
My OPO can boot into recovery mode (Please see picture named "OPO Cyanogen Recovery.JPG"), so I can see the Cyanogen Recovery menu, but I do not want to wipe all my data and do a factory reset. I want to first save my data and afterwards I can erase all data and reset my OPO.
Problem: my OPO gets stuck while booting, showing only the CYANOGEN logo. I wait and wait and nothing happens (today I waited for two hours, the logo is still there and the phone does not start).
I want to:
1) Save to my computer my files (media files, documents) and messages (SMS and chat messages, like viber and so on)
2) Solve this boot logo issue (OPO stuck on booting, while showing only the CYANOGEN logo)
Any help regarding this problem is enormously appreciated.
Thanks in advance,
Bogdan
Well that sucks. You could try to install TWRP through fastboot and use it to mount the phone as a USB storage device, I think that could work.
---------- Post added at 02:56 PM ---------- Previous post was at 02:55 PM ----------
Wait no, since your bootlocker is locked it's pointless.
bogdan_p said:
Hi,
I bought my OnePlus One (64 GB Sandstone Black) in September 2014. Since I got the phone, everything was running very quickly & smoothly. I did not have any problems with it, so I was very pleased with my brand new phone.
I did not tamper at all with my OnePlus One phone and every time there was a new OTA update, I updated it with the latest version. Currently my OPO has the latest Cyanogen OS 12 OTA updates (CM12S).
Last Friday I used my phone and everything was running very good, as usual. I shut down my phone and went to bed. The next day, on Saturday morning when I turned on the phone, it started showing the OnePlus One logo (with the text "powered by android"). Then CYANOGEN logo appeared on the screen and nothing happened. I waited near my phone for half an hour and nothing happened, it kept showing the CYANOGEN logo. It's like a cycle that never ends. So now I am facing a huge problem with my OPO: every time I press the power button, my OnePlus One gets stuck while booting, showing only the CYANOGEN logo. :crying:
Please see picture "OPO stuck on booting - shows only CYANOGEN logo.JPG".
As I said before, I did not tampered with my OPO, I did not flash it, I did not installed any ROM, I did not installed a custom recovery. Also, I did not drop my phone, so it is in good hardware condition. Every time there were new updates, I updated it with the latest OTA updates. I did not have any issues after the updates, so I don't understand why now it gets stuck on booting (especially since before this problem appeared, everything was working great, as usual).
I read through the forums, the internet and tried to find several solutions, without wiping my data. Any solution that I found did not work and I could not fix this problem (OPO stuck on booting, while showing the CYANOGEN logo). After two days in which I could not use my phone, I removed my SIM from the OPO and now I am using a normal phone (only for calls and SMS).
After my OPO gets stuck while booting, showing only the CYANOGEN logo, I connect it to my laptop using the USB cable (the same one used for charging), but I cannot access my files. Before this huge problem appeared, I could easily connect my OPO to my laptop. Please see pictures: "Connecting my OPO via USB - Installing device driver software - Step 1.JPG" and "Connecting my OPO via USB - Installing device driver software - Step 2 - Failed.JPG". I updated the drivers, but it did not work.
Ever since I got my phone, I have never unlocked the bootloader or rooted or anything of that sort.
I have never even touched any fastboot/adb commands since I got the OPO, until now, when I have this major problem with it.
After reading the forums, I started my OPO in Fastboot Mode and used 2 commands with fastboot.exe (Please see picture named "OPO Fastboot Mode.JPG")
Results below:
******************************
F:\OnePlus One tools>fastboot.exe devices
b01c5f88 fastboot
F:\OnePlus One tools>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
******************************
I do not understand why "Device tampered: true", since I have never unlocked the bootloader or rooted or flashed or anything of that sort ever since I got my OPO. I did not tamper my OPO, so "Device tampered" should have been false.
I also tried to use ADB, but it does not work. Please see below:
******************************
F:\OnePlus One tools>adb devices
List of devices attached <--- THIS LIST IS EMPTY, IT DOES NOT SHOW MY DEVICE, SO ADB DOES NOT WORK AT ALL
******************************
I want to save my media files (pictures, recordings, clips, audio files), my documents and messages.
For other suggestions found on the forums, I did not use at all, because I do not want to erase all data of the phone.
My OPO can boot into recovery mode (Please see picture named "OPO Cyanogen Recovery.JPG"), so I can see the Cyanogen Recovery menu, but I do not want to wipe all my data and do a factory reset. I want to first save my data and afterwards I can erase all data and reset my OPO.
Problem: my OPO gets stuck while booting, showing only the CYANOGEN logo. I wait and wait and nothing happens (today I waited for two hours, the logo is still there and the phone does not start).
I want to:
1) Save to my computer my files (media files, documents) and messages (SMS and chat messages, like viber and so on)
2) Solve this boot logo issue (OPO stuck on booting, while showing only the CYANOGEN logo)
Any help regarding this problem is enormously appreciated.
Thanks in advance,
Bogdan
Click to expand...
Click to collapse
So your ota s update is in storage
Go to recovery
Install update
Navigate to 0/android /data/com.cyngn.fota/cache folder
There live your update and reflash the last update
Pm becarefull do not install wrong file and downgrade
Check the name or post it here for help
geowolf1000 said:
So your ota s update is in storage
Go to recovery
Install update
Navigate to 0/android /data/com.cyngn.fota/cache folder
There live your update and reflash the last update
Pm becarefull do not install wrong file and downgrade
Check the name or post it here for help
Click to expand...
Click to collapse
In the Cyanogen Recovery Menu I clicked on Apply Update, the Choose from internal storage
In the 0/android /data/com.cyngn.fota/cache folder I found this file: cm-12.0-YNG1TAS17L-bacon-signed.zip
What should I do next? Doing this will help me fix the booting cycle issue? Or it will help to save my data?
In adition to this, I posted the same problem on a OnePlus forum.
https://forums.oneplus.net/threads/cm12s-is-stuck-on-booting-shows-only-cyanogen-logo.316950/
On this thread, the proposed solution made by a user (biltoad Level: Gingerbread) will somehow help to save my data? Then I can do a factory reset.
Please find below his suggestion. What do you think?
*****
alright i've got a working solution
download color os from here:
https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
and extract
and then follow the instruction here to set it up (dont flash yet):
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
the download cyanogen fastboot zip here
https://cyngn.com/support
extract the cyanogen fastboot zip to your extracted color os folder(replace everything)
download twrp from here : https://twrp.me/devices/oneplusone.html
copy twrp to the color folder and replace recovery.img
delete these :
8974_msimage.mbn
userdata.img
userdata_64G.img
after that you should start flashing
the download tool will stop and show red text(ignore that)
after that hold the power button for about 10 secs
hold vol down+power to boot to twrp, and start saving your data
edit : Tested
oh yeah, after you install twrp, flash this to unlock your bl http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
bogdan_p said:
In the Cyanogen Recovery Menu I clicked on Apply Update, the Choose from internal storage
In the 0/android /data/com.cyngn.fota/cache folder I found this file: cm-12.0-YNG1TAS17L-bacon-signed.zip
What should I do next? Doing this will help me fix the booting cycle issue? Or it will help to save my data?
In adition to this, I posted the same problem on a OnePlus forum.
https://forums.oneplus.net/threads/cm12s-is-stuck-on-booting-shows-only-cyanogen-logo.316950/
On this thread, the proposed solution made by a user (biltoad Level: Gingerbread) will somehow help to save my data? Then I can do a factory reset.
Please find below his suggestion. What do you think?
*****
alright i've got a working solution
download color os from here:
https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
and extract
and then follow the instruction here to set it up (dont flash yet):
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
the download cyanogen fastboot zip here
https://cyngn.com/support
extract the cyanogen fastboot zip to your extracted color os folder(replace everything)
download twrp from here : https://twrp.me/devices/oneplusone.html
copy twrp to the color folder and replace recovery.img
delete these :
8974_msimage.mbn
userdata.img
userdata_64G.img
after that you should start flashing
the download tool will stop and show red text(ignore that)
after that hold the power button for about 10 secs
hold vol down+power to boot to twrp, and start saving your data
edit : Tested
oh yeah, after you install twrp, flash this to unlock your bl http://forum.xda-developers.com/showpost.php?p=54251992&postcount=1
Click to expand...
Click to collapse
Will help you with bootloop if is rom issue
Flash ota first is cyanogen 5.0.2
Your data is safe
The other suggestion from oneplus is little risky
You should after take backup to connect with pc and tranfer your backup to pc if you factory reset or unlock bootloader
You will need proper drivers for that
Check how enable twrp mtp storage for pc
Follow the steps one by one before try it .
Good luck
I have looked at multiple guides on this and other sites, googled and tried stuff and I cannot resolve this problem. Hopefully I am posting in the right place.
I took the jump and unlocked the bootloader on my Moto G first generation, XT1034 successfully. I flashed TWRP 2.8.60.xt1034.zip with adb and this was successful. Then I flashed Super SU 4.6 Update and that was successful. I got into trouble I guess when I tried to flash Cyanogenmod 12.1 nightly. I used TWRP to flash via install. The flash had an error, which unfortunately I didn't write down. I believe it was something to do with a partition. However, it looked like the flash failed. At this point and for hours I have been trying to fix the "Warning Bootloader Unlocked Loop I am stuck in.
I have been able to get into the phone and flash via adb commands. I've tried several commands suggest to fix this that I have found in forums. I have tried flashing several recoveries including an older TWRP per the method in this thread, a clockworkmod - and the original 2.8.6.0.xt1034. When I get into the phone bootloader which is available, I have not been able to access any options in recovery. Pushing the power button on recovery leads to a blank screen sometimes followed by a recovery starting or a Motorola Logo starting up and a couple times a recovery. TWRP has started a couple times, but never gets past the intro screen, where it locks up. clockworkmod (clockworkmod-6.0.4.7-falcon.img started once after flashing through adb and gave me flash options. I tried to sideload, didn't understand, went back and the recovery locked up. These recoveries no longer load at all.
Through all of this the "Warning Bootloader Unlocked" logo screen comes up after plugging into the computer (Windows 8.1).
Example, I open the phone bootloader by waiting for the phone screen to go from the "Warning Bootloader Unlocked" screen to blank - it cycles from logo to blank. If I'm quick the phone and hard boot the phone will boot into bootloader. I connect to the laptop through USB. When I toggle to recovery and hit the power button the screen goes blank, the Motorola Logo pops up, goes blank and then the "Warning Bootloader Unlocked" appears. The Laptop then seems to connect and disconnect as the Warning screen comes on and turns off.
The factory selection just goes to a blank screen.
I would really appreciate some advice on how to get the phone back to a state in which I can work with it and try again. It is very difficult wading through all of the information out there. I've learned a lot through this issue, but can't take it any further.
Thanks, Jeff
Solved - Stuck in "Warning Bootloader Is Unlocked" Loop
This resolution took many hours to figure out, but I finally got there with this guide - http://forum.xda-developers.com/showthread.php?t=2542219, this thread - http://forum.xda-developers.com/showthread.php?p=54855457#post54855457 and this thread - http://forum.xda-developers.com/gen...e-firmware-t3042687/post59139823#post59139823.
I tried RSD Lite on different computers and USB cables I could not get the device recognized. So I ended up with the MfastbootV2 method to reload stock firmware, which I found on the firmware thread above - this was big, as my phone is with Wind Mobile in Canada and the link is the right one. The only thing I picked up from a different website was to use a computer with USB 2 ports. This is what I did, but I don't know one way or the other if USB 2 was needed. .
Can't thank you hard working guys enough for the time you take to put these threads together. I'm back up and running. As a bonus, after a big clean up in the process, my phone is running fast again.
Thanks everyone.
Hi guys, I’ve had a problem with my nexus 5 and was wondering if you guys could give some insight into what I can do to fix it (hopefully it’s not a hardware issue)
Note that I have no warranty on this phone; it’s 2 years old.
First of all, my phone is stuck in some kind of bootloop – it either restarts on the google logo or loading screen – and on the loading screen it freezes for a few seconds and then restarts. I did not do anything overtly suspicious with my phone or update it before it started having this problem.
I can boot into bootloader no problem. The phone does not restart while I’m in the bootloader. I know I can stop the bootloop (aka shut my phone down) by shutting it down with the option in the bootloader.
However, I can not boot into recovery mode – whenever I choose that option the phone tries to reboot and then gives a “no command” error and then reboots after about 5 seconds – no amount of spamming power button+volume up/down does anything for me. Then it gets stuck back in the bootloop.
So I tried flashing my phone. (all my stuff was backed up anyways) Here’s what’s happened:
When unlocking bootloader, (“fastboot oem unlock” and then “fastboot reboot”) after rebooting it gets stuck in a bootloop and if I manually go back to bootloader it remains locked. In other words, if I unlock and then reset the bootloader, it goes back to locked. So I get a lot of FAILED: (remote: not supported in locked device) when programs try to flash multiple images in a row. Update: I’ve also tried “fastboot oem unlock” and then “fastboot reboot-bootloader” successfully but the lock state always changes back to locked.
When flashing any of the images when unlocked, I always get a “FAILED (remote:flash write failure) error.
When I try fastboot boot recovery.img I get the same error that I do when I try to recover from the fastboot screen.
Note that I cannot enable USB debugging because I get stuck in a bootloop.
1. What should I do from here?
2. Any other forums I can check for help?
Others:
I’m pretty sure I was on version 6.1, but I have no way of checking now.
I’m using windows 7 64bit
The guides I’ve been using are:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 and WugFresh’s nexus root toolkit, specifically http://www.wugfresh.com/forums/thread/common-solutions/
TLDR: bootloop and can't enable USB debugging, can't keep the lock state unlocked, or keep getting "FAILED (remote:flash write failure)" Error
If the bootloader relocks itself when rebooted, the memory chip is damaged which means you'll need a new motherboard.
Same here need help
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.
Hello, I've been using this phone for more than a few years now. Reflashed the system a few times over the years and was currently on Ivan_Meler's amazing LineageOS 18.
I saw that a bug on his 19.1 version I was experiencing was potentially fixed, so I started preparing to switch to that.
First order of business was going to recovery and doing a full backup, I had gone into recovery not too long ago.
Except I got boot looped instantly.
The current situation is:
- Model is SM-G930F
- The device is rooted
- Device will not stay turned off, if I force turn off with volume down + power it reboots instead
- Device is able to get into download mode and it seems to work normally
- Device will always boot to recovery, except when I ask to boot to download mode by volume down + power + home (not sure if there is a button combination for specifically booting to system, lmk If there is)
Things I already tried:
- Letting the battery run out completely to hopefully clear some cache -> Device tries to boot to recovery as soon as I plug the charger in
- Using ADB during the stuck splash screen -> Device eventually gets recognized by windows but it throws the generic "Your USB device malfunctioned" error, ADB doesn`t recognize it.
- Rebooting by launching a harmless command in Heimdell -> Device reboots but nothing else changes, still stuck.
- Letting battery run out at different stages, like in the stuck teamwin splashscreen, in the warning message before download mode and in download mode -> nothing changes
Additional information from the moment I tried to get to recovery and got stuck:
- I fat fingered "reboot" instead of turning off the phone, so I just held down volume up + home to get into recovery (I had already done this successfully before).
- My phone has USB debugging turned on
- My phone was plugged to my PC in USB Tethering mode when I tried to get to recovery
- My phone was set to use USB Tethering mode by default when plugged via USB, because I use that function a lot.
- My PC had the ADB server running, but was not actively running anything on device at the time.
I remember having been stuck in this same situation before and being able to recover it without losing data. But I have no recollection of how I did it.
If there was a way to make my phone stop trying to reboot and just turn off, im sure that
I would be able to boot into system, because i dont see how anything could've gotten messed up there since the phone rebooted normally and wasn`t reflashed or anythng
I really didn't want to have to wipe it, since my last full backup was a few months ago.
Do you guys have any suggestions? I was thinking of trying to flash back the exact same TWRP version through Odin, without flashing anything else. And seeing if that fixes it since the version is shown in the teamwin loading screen, would that be safe?
Hi, any progress ? I'm in the very similar situation, but flashing the same TWRP with Odin didn't help and I'm still stuck on TWRP logo. And adb doesn't see the device (neither when I'm in download mode nor when I'm on TWRP logo)
Is the device softbricked?
Try Frp HiJacker
All Samsung Frp HiJacker by Hagard (2017)
All Samsung FRP HiJacker 2017 latest updated tool.This tool 100% working and tested. FRP HiJacker V1.0 Features: * Remove Samsung FRP 2017 in Download Mode (No More Combination Files and No more tricks) * Softbrick fixer *Phone...
forum.xda-developers.com
Had similar problems myself