Hi all new here,
Just got my OnePlus One and updated to cyanaogen 12, while simply using the phone it crashed forcing me to reboot the device, after this the phone would not turn on (asssuming it was hard bricked), luckily following some guides on this forum I was able to get it back up and running again.
I reflashed 12 after and exactly the same thing has happened this time, unfortunately I am unable to unbrick it using the ColorOS method like before, the phone just remains dead and I cannot get it into fast boot mode to rectify the problem.
I am out of luck already? OnePlus seem absolutely useless over support and just plain rude.
EDIT:
I am now able to get into fastboot, but still cannot see it on screen, but fastboot is appearing in device manager as windows ADB, what can I do from here?
Related
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.
Hi there,
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please help me to bring back my phone! This is literally driving me nuts, and I haven't so far found a solution that works! I would be happy to clarify and elaborate upon any point of information.
Thanks,
Sami
iamsami13 said:
Hi there,
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please help me to bring back my phone! This is literally driving me nuts, and I haven't so far found a solution that works! I would be happy to clarify and elaborate upon any point of information.
Thanks,
Sami
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Looks like you made your way to the right spot. Cool!
Hope it helps.
Hello.
First of all, i'm sorry if this question have been asked before. Believe me, i've tried searching even through Google's 2nd page but still no luck in finding answer.
I had a OPO 64GB version. It was working fine until i decided to do ROM update. My previous working ROM is "CM13-20160812-somethingsomething-SNAPSHOT.zip". It is rooted with Xposed installed
I tried to update it using TWRP. the update is "CM13-20161216-somethingsomething-SNAPSHOT.zip". It got stuck at "Patching system image unconditianally"(probably wrong spelling there) for more than one hour. So, i decided to force reboot it and it is now stuck at boot logo(not bootanimation)
Thing is, i cant get it into fastboot, nor recovery. it just stuck there and i've tried to Power Cycle but still no result. I tried to plug it into my computer and it does detect it in "Device Manager" under "Portable Devices" with name "A0001".
I wonder if it soft brick or hard brick. I'm asking brilliant mind in here, if there's a way to restore it. I just revived it from broken screen since 2016(talk about bad luck) and i don't want to completely replace as the device is still in good condition.
Also, if there's no other choice then i had no other way than to follow this guide here, which completely unbrick my phone(also losing me 30+ apps)
http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/
or
http://forum.xda-developers.com/oneplus-one/help/guide-unbrick-oneplus-one-t3013732
Nevermind. i got it to work by installing QPST driver. for some reason it enable adb at boot logo(yes at boot logo). got into recovery and recover my system partition(which is broken).
I ask the mod to delete this thread. Thank you
Recently all of a sudden my phone(Realme X2) got stuck in bootloop. It happened all by itself, phone got drained out and I connected it to the charger after 15mins and in no time it was in bootloop.
Now I'm trying to access the fastboot but I'm unable to unlock it as my phone is stuck in this bootloop.
I tried using adb commands but its not reading, and in my device manager the port section driver also keep on looping. I tried to access the stock recovery which is really of no use.I tried all the ways out by my side none is working.
Any idea how I can flash my device and get it back to usable?
Hint: Add Realme X2 to this thread's title thus mainly owners of such phone get addressed.
will do
Hi guys,
Hope someone can give me some light about diagnosing flash memo device hardware damage.
I have an OnePlus 6 A6003 that entered for sudden in CrashDump Mode. It stopped to run the OS, although the bootloader mode still worked.
Guided by some tutorials I tried to unlock trough fastboot and adb in CMD panel without success in unlocking the device.
After that, I started trying Msm Downloading tool to flash a Oxygen firmware and make it brand new. I couldn't.
The process stopped somehow in the middle of downloading to system_a. I lost hope big time here and went to SMT flashing. The tutorial advised that i could lose IMEI if i did not backed up my EFS. I didn't, but i figured i could use some downloaded backup and change my IMEI back to original, as I have the original box and data of the phone. I did it and the process of flashing the device stopped the same spot it did before.
From there I repeated the process in loop until finally I got it done. Once the original oxygen firmware was succefully flashed I was happy, till i discovered the phone still doesn't turn on. it always blurs the initial logo screen after some seconds and freezes.
At this point I think there is some hardware problem at the flashdrive device. Anyone have any idea if this still can be a software problem or can assure me how i could definitly diagnose it?
I 'd be thankful with any help.