Hello, so i was using my phone last night browsing instagram, when all of a sudden it froze and restarted(happened to me from time to time), so i thought it will bootloop for a few times and it will boot up just fine. But no. It got stuck there and i could access recovery only when my phone has been off for 10 minutes, and fastboot was accessible at will. I accessed recovery a few times, and i tried:
Wiping cache and delvik cache - No luck
Let it charge into recovery to 100% overnight and try flashing in the morning
Wiping data - no luck
Re-flashing sultan rom - no luck, phone just freezes halfway into installation and restarts
Since i can only access fastboot, i tried some fastboot commands, but nothing serious(like flashing, formatting, wiping...), and cmd shows that they were successfully executed, but nothing happens with phone ("fastboot reboot" cmd)
Removing sim card - no luck (but i am desperate)
Usually when reboots happen, i can plug it in a charger, and it will power on with battery charging animation, but not these times, it just reboots at oneplus logo
On one occasion it got past the oneplus logo, and showed a small blue cyanogen circle, but it froze there as well.
I did not try sideloading, and nothing with adb, since i am not experienced in those fields
I had similar thing happen to me the night before, but it eventually turned on and i could use it whole day without reboots
Also it seems to have happened both times while battery was at around 15%
I live in a small city in Serbia where there are no professional who know these kinds of phones, so i can't take it to repair shop.
EDIT: I can enter sideload if that matters, and my pc seems to detect it, because i can hear windows chime
EDIT 2: i can no longer enter recovery, it just wont enter there anymore
Tried flashing twrp via fastboot but i get (command write failed too many links) error
I tried some repair shops they said it's the motherboard, so is it really dead, because i still have oneplus logo
Any suggestions?
MY FIX
I connected my phone to friends laptop and flashed stock cyanogen os 6.0.1, fastboot worked like charm and phone booted up just fine
Related
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
morr22066 said:
So it started out that CM 12 kept shutting down on me, the phone would occasionally just power off. I tried restoring some of my TWRP backups but they seemed to be corrupted.
So I decided to try RSD and reflash the stock firmware and go back to 4.4. I let it flash and then when I booted up I kept getting a message saying that the phone was going into cool down mode, but the phone never actually got hot. So I decided to try and reflash the stock 4.4 firmware again in RSD. This time I watched the phone screen as it went through and just after the system image (#7 of 17) I would get a message in "RED" letters that reads "sp space is not enough". It would continue to flash the rest of the images and then reboot. And it would have the same problem with saying the phone is going into cool down mode and sometimes it would shut off, but the phone never gets hot.
I thought maybe I had a bad download / firmware image so I tried several 4.4 images including one directly from Motorola but I get the same message every time I flash the stock 4.4 ROM.
*While it is plugged into the computer the phone stays on, but once I disconnect from the computer it shuts down again.
So I thought I would try flashing TWRP and CM 11 and then CM12, but the phone will boot up and then shortly after boot up it will shut down.
I have spent hours looking for a solution online and I do find that there have been multiple reports of this same problem along with photos of the phone screen message, but I have not found an explanation or a solution.
Does anyone have any idea what the problem is or how to fix it?
Click to expand...
Click to collapse
I had tried everything I could think of and it appeared that there was a partition problem. The phone continued to shut down and would only stay on while connected to the PC. If it were a PC I would reformat and re-partition the drive but I did not want to risk a permanent brick by messing with it.
So, as a last ditch effort to try and get my phone functioning again I let it download and install system updates. The phone is now working again, it has not shut down at all and there have been no warning messages about cool down mode.
BUT, I am now on "4.4.4, SU-5-24, build 23.3.24 dated 10-27-14. Since my boot loader is unlocked I flashed TWRP but it would not not accept Super SU zip so I am no longer rooted.
I finished reading up on it in the forums and realize I am pretty much screwed as far as root goes. But at this point I don't even care anymore. I just need to get the phone functioning correctly.
*So, I am still having the problem with flashing stock and getting the "red" letter message after system image boots saying "sp space not enough". So long as it is hooked up to the computer it stays on and if it is downloading or installing an update it stays on and I never get a warning about cool down mode and it does not shut off, but once I disconnect from the computer it starts all over again. The phone boots up but at random intervals it still either gets a pop up message saying that it has gone into "cool down mode" or it shuts off. It is not doing it as often as before, but it is still doing it. Does anyone have any suggestions on whats causing it or how to fix it? It sounds like a software / firmware issue but I am not sure how to fix it.
*Update. The phone is still not functioning correctly. At times it will appear to work fine for hours with frequent to heavy use at times then suddenly it will start acting up, the phone will shut down randomly and when it reboots some of my settings have changed. The temperature is usually pretty low but once in a while after a shut down I will check the temp when I'm able to reboot it and it will be high. When it shuts down like that I usually have trouble getting it to boot up again unless I plug in the factory cable, either in the PC or just the wall charge then it seems to boot up fine and I can even reboot it but once it shuts itself down it doesn't want to start again unless I use the factory cable.
It really does sound like a software / firmware / partition problem but after multiple attempts to flash the firmware with RSD I continue to get the same error message at the end of the system flash and the phone continues to have problems. Does anyone have any suggestions?
Got me an xt1080 which I'm trying to restore to stock, and in both House of Motor and RSDlite 6.2.4 at some point during the system partition flash 'so space is not enough' as well. The phone is in perpetual bootloop, unless I use a 'Factory/power' cord and starting up in fastboot (eventually). Tried both 1FF and CFC fxz files, no luck.
I was charging my phone overnight. In the morning I realized it didn't charge, I tried to turn it on and it gets stuck on the HTC screen.
I was running Viper One 3.21, I tried rebooting, entered recovery, tried to reinstal a nandroid, got stuck on the screen again.
Tried reinstalling ViperOne same problem.
Here's what I know:
Fastboot will NOT work, while I can get to fastboot, any time I reboot the phone it gets stuck.
I can't get to RUU (because it wont go past the HTC screen).
adb sideload will not work
I've let the battery drain, fully charged it; no change.
I tried wiping and doing a factory reset but it just gets stuck on the reboot, I also noticed on the File manager within TWRP that my phone was never wiped.
Any ideas?
SS823 said:
I was charging my phone overnight. In the morning I realized it didn't charge, I tried to turn it on and it gets stuck on the HTC screen.
I was running Viper One 3.21, I tried rebooting, entered recovery, tried to reinstal a nandroid, got stuck on the screen again.
Tried reinstalling ViperOne same problem.
Here's what I know:
Fastboot will NOT work, while I can get to fastboot, any time I reboot the phone it gets stuck.
I can't get to RUU (because it wont go past the HTC screen).
adb sideload will not work
I've let the battery drain, fully charged it; no change.
I tried wiping and doing a factory reset but it just gets stuck on the reboot, I also noticed on the File manager within TWRP that my phone was never wiped.
Any ideas?
Click to expand...
Click to collapse
Sorta sounds like one of the bricked ones where the entire emmc goes write protected. If you can't get fastboot or ruu mode and have no warranty left I can take a look at it for you. I'm in PA so it wouldn't take long to mail it here.
Not sure how it got bricked, it has been over a month since I flashed anything.
I am able to use adb sideload, but any file I use it says is corrupted.
Could I partition part of the drive and try to instal from there?
What part of PA are you in?
SS823 said:
Not sure how it got bricked, it has been over a month since I flashed anything.
I am able to use adb sideload, but any file I use it says is corrupted.
Could I partition part of the drive and try to instal from there?
What part of PA are you in?
Click to expand...
Click to collapse
I am down in the York/Harrisburg/Lancaster area. You don't want to partition emmc manually.
So I was on my way back from vacation yesterday, I had made a phone call a few minutes prior, and I noticed my screen wasn't coming on ....
Tried holding the power button - nothing.
Tried charging - nothing.
Tried every combo I could find on google, held them for minutes - nothing.
Let it charge for an hour or so - nothing.
Then randomly it started allowing me to get to the "Google" splash screen, then the screen would go black and become unresponsive again.
It's gotten a little better, but it is extremely random, sometimes I can get into recovery (TWRP), sometimes I can get the phone to charge, and sometimes it will do nothing at all.
After getting into recovery a few times, I noticed that my SD card was wiped (only a TWRP folder remains) and it wasn't a few minutes before that - I did not wipe it.
It will not boot, and trying to mount via USB doesn't work - it doesn't allow me to copy any files to try and re-flash the OS (stock rooted 6.0.1 with elemental x).
Tried ADB push with no luck, it says file system is read-only.
I can un-toggle System / Data etc in TWRP to unmount them, but clicking to mount them does nothing, the box remains unchecked, and trying to do other things, such as start adb sideload, results in a buttload of mount /system errors......
Battery is full (when I can get the phone to charge) and is a new OEM battery.
Tried charging, not charging, and plugged into a USB port on my PC...
I'm out of ideas here.... does this sound like the internal memory is shot? Does anyone have any ideas on how I can revive my lil' buddy???
Thanks in advance for the help!
-Austin
Update: Now it won't even boot to recovery.... I select recovery and the screen goes black...
I think your eMMC is corrupt. I don't know any way to solve this issue.
Looks like you have to get a new motherboard.
UPDATE: I have finally managed to get my phone working again! Am now currently re-downloading all my apps and transferring all my files back to my phone, running AOSPExtended (https://forum.xda-developers.com/oneplus-one/development/rom-aospextended-rom-t3732194) with OpenGApps. I'll write the steps I took to figure this mess out at the end of this post for anyone who might encounter the same problem in the future. :good:
So last night I left my phone charging overnight from 54% as I was downloading a couple of files (my internet is 1Mbps or 125KB/s). I've done this a couple of times before with no problems what so ever. But this morning I woke up and my phone was in a boot loop. I've tried everything I can think of and everything I could find on these forums, but to no luck. I am at my wits end and I have no clue what to do except to do a full factory reset, which I'd rather not do as its been a while since my last backup and I would lose a lot of precious files...
My Phone: OnePlus One 64GB Sandstone Black, purchased in August 2014.
ROM: cm-13.0-ZNH5Y-20161105-STABLE-Sultan-bacon
Recovery: TWRP+3.0.3-2-TugaPower
Firmware: bacon_firmware_update_2016_1-25_.4.0.1.c7-00011
The boot loop itself is odd, I'll describe them separately here.
-I can boot into fastboot, but not while the USB is plugged into my PC. I have to boot into fastboot, followed by plugging it into my PC. If I try to boot into fastboot while it is plugged in, the screen goes completely black and goes back into the bootloop. However, the phone shows up in Device Manager during the black screen.
- I can boot into Recovery, but the phone automatically reboots and goes back into the bootloop after a few minutes. One thing I have noticed is that if I let it reboot by itself, all the settings reset (including the confirmation to allow modifying of files when you first boot into recovery). But if I manually reboot back into recovery, the settings remain the same; atleast until it reboots automatically again.
Here, I'll list the things that I have tried to no avail:
1. Following this post - https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/, when I try to wipe Dalvik cache and cache from recovery, the phone goes right back into the bootloop
2. I tried flashing a newer version of TWRP (3.2.1-0 and 3.2.1-K2). After flashing I try to boot into recovery but the TWRP loading screen displays, and then goes right back into the bootloop. It wont even let me into the main menu.
3. I tried flashing a ROM through fastboot (via this post, https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/). The phone still remains in a bootloop.
HOWEVER, if I flash my previous recovery (TWRP+3.0.3-2-TugaPower replacing the stock cyanogen recovery from this method), my phone manages to get past the 1+ screen, and goes through my custom power on screen, and reaches the "Android is starting... Optimizing app 1 of 67." But it never gets past app 1, freezes, and then reboots. So now it's stuck in this "extended" bootloop thing.
What I want to know: is there anyway to fix my phone, or will I have to lose all my data and do a full factory reset through the ColorOS method? If anyone has any experience with this or knows a way to help, please don't hesitate!
Thank you in advance.
WHAT WORKED FOR ME:
After following the steps in this post (https://forums.oneplus.net/threads/guide-oneplus-one-flashing-fastboot-recovery.301131/) my phone was booting up, but was kicked back into a boot loop after freezing at the "Android is starting.. Optimizing app 1 of 67" screen. However, the recovery was now the default CyanogenMod recovery. I then re-flashed my previous recovery (TWRP+3.0.3-2-TugaPower) from fast boot, and it was now stable (no more auto-reboots). From there I made a backup off all my files onto my PC before proceeding. After that, I did what this post said (https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/) and wiped Cache + Dalvik cache. This allowed me to boot all the way past the "Android is starting" screen. However, the phone was still rendered unusable as there were non-stop notifications saying various apps had stopped working. I then booted back into recovery, downloaded and pushed a new ROM and GApps package on to my phone, wiped system, data, cache, dalvik cache, and installed the ROM and GApps pacakge, clearing the cache one more time before rebooting. Everything is working beautifully so far and I could not be happier! I hope this helps anyone else who encounters this problem, Cheers!
So everything went smoothly after the update but I couldnt get it to factory reset. Kept saying unable to mount. So I tried the repair option on TWRP and that wiped the OS. Now I can't get into recovery only the fastboot function. What can I do?
fastboot boot twrp.img on your PC?
Maybe you are using the wrong one, the inoffical twrp comes in Android P and Q flavour
I have also had the issue where neither started, after shutting down and waiting for a while it worked again
I had same problem totally black dead screen, nothing happens for couple of minutes, I tried all key combinations and it didn't respond. Somehow after a while (like 5 min. ) I tried vol up+down+power button, it took me to fastboot screen. Then I flashed everything back in, downside Lost All data even internal storage.