The phone crashed suddenly while being used normally yesterday. Tried rebooting and it stays stuck in boot-logo or post boot-animation.
Rebooted into OnePlus recovery and did a wipe. It took a while, and it rebooted. Post reboot it started auto-wiping. Waited for 15 minutes - it was stuck on "wiping" before I reboot it manually, only for it to auto-wipe again on restart.
Then I went the MSM route, which happened successfully. Only this time, when the phone rebooted after MSM, it began auto-wiping again. I left the phone for an hour, it still said "wiping", which I had to cancel. Then the whole process starts again. The only difference after MSM process was the "Wiping" was written in Chinese.
What should I do to escape the auto-wipe loop.
Edit: To add, I did try the "fastboot oem unlock" but it says the phone state is locked, which is visible on the fastboot screen as well against Device State. So how do I unlock it when I can't even boot into the OS.
Reflash your phone using an older MSM version, like hydrogen 5.1.3
https://yun.daxiaamu.com/OnePlus_Roms_3/%E4%B8%80%E5%8A%A06/%E7%BA%BF%E5%88%B7%E6%95%91%E7%A0%96%E5%8C%85%EF%BC%88%E6%B0%A25.13%EF%BC%89/OnePlus6_enchilada_22_H.07_180513.zip?preview
This is a Chinese version, but it works on my phone.
Related
Battery was getting tired, so I ordered a replacement -- and installed it yesterday afternoon..
The phone worked normally -- until this morning.
I noticed a notification from my text app that it couldn't connect and that I should check my settings.
I went to settings and began by refreshing the PRL. During that process the phone froze and then went dead.
Totally dead.
So, I opened it up again to check the battery terminal connection -- and I believe it WAS loose -- so I reconnected it and checked it. Phone goes on!
But it only goes to the splash screen and then repeats. No boot animation.
It will go to the bootloader, but not boot the system nor recovery from there.
Using the fastboot commands, I re-flashed bootloader, radio, boot, system, (From 5.1 stock image) TWRP recovery and erased the cache.
Still stuck at the Google splash screen.
Anyone care to point me in a better direction?
Must be expiration time for Nexus 5 batteries from the initial run. I had to replace mine today as well. Try reflashing the cache and not erasing it after. I made that mistake a month or so ago and kept bootlooping.
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
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!
heyo - I have a G930w8 Samsung S7 (Exynos.) I don't know what CSC the phone has. It was just sold new-in-box on Ebay as an unlocked Canadian Samsung S7. I'm using it in the US.
I've had it for a while. While attempting to update today, the phone, well... didn't update. It was stuck updating for a day. Could not get into recovery menu, but Odin/downloading mode worked.
I used Odin to flash this stock firmware: sammobile. com/samsung/galaxy-s7/firmware/SM-G930W8/XAC/download/G930W8VLS6CSH1/288555/ to the phone, using the CSC file (not HOME_CSC.) It worked. I did not flash the userdata and didn't use PIT as neither are included in the sammobile package. I didn't use re-partition, because whenever I try that, Odin (3.13.1) fails to flash with "Can't open the specified file, line 1892"
So, post-flashing, the phone boots to a "Erasing" screen, then to an "installing system updates..." screen, stops at 32%, then goes back to "Erasing". After a while on "Erasing", the Android logo freezes. I left it in this state for 30 minutes and nothing happened - I now plan to leave it there overnight, but in the meantime:
- if I force restart the phone, once it reboots it tries "Erasing" for a moment, then goes into a permanent "No Command" boot loop.
- If I re-flash the firmware, it goes back to the previously described "Erasing > Installing System Updates 32% > Erasing > Frozen logo on Erasing" state.
- If I go to the recovery menu, the phone usually randomly freezes or reboots. A couple times I successfully selected the factory reset option, at which point the phone would print "formatting /data...". It remained in this state for 30 minutes with no change, so I am not sure if it's freezing or actually doing something. I intend to also try leaving this overnight.
Can anyone help me get this phone functioning again? I am not sure what's going wrong here, if I have installed the wrong firmware, if I have installed the wrong CSC, do I need to use a PIT file, etc.
Edit: The phone is working again. For posterity, here is what I did:
- left it overnight at the "erasing" screen. It was still there when I woke up.
- went into recovery, tried a factory reset. It almost instantly went through. Rebooted the phone from recovery menu.
- phone now did "Erasing" for a moment, then, reboot > glowing samsung logo > setup screen > rebooted (with no prompting) into bootloop while I was setting up
- re-flashed the firmware, removed SD card
- now it does "Installing updates > 32% > erasing" except it doesn't freeze on erasing this time, it completes "Erasing" and reboots
- phone now boots normally
- encountered a crash/boot into bootloop after setting up the phone, but re-flashing (this time with HOME_CSC) fixed it
And I'm currently in the phone, able to use it... hopefully no more bootloops. What a cluster****.
Edit 2: I kept getting unprompted reboots into boot loops after 5-10 minutes of using the phone (after flashing.) Re-flashing with HOME_CSC would un-bootloop it, but I decided to let it boot loop for 30 minutes to see what would happen. It eventually stopped boot looping and stayed on the Samsung logo, not booting into recovery or anything. I turned off the phone (power + volumedown) and started it up and it booted just fine. Phone now doesn't appear to be bootlooping randomly.
Edit to the edit of the edit - actual solution: The phone still randomly rebooted every now and then, although no bootloop. I ended up installing TWRP through Odin and hard-wiping the phone ("Format Data".) A normal wipe did not work. I then finally re-flashed the stock ROM and now the phone has been working perfectly for hours.
Here's to hoping future Android updates don't prompt two days of attempts to un**** the phone!
The short story is that I used the MSM Tool to try reset my OP7 Pro completely back to stock. I have the US/Global variant (GM1917). The image I used is the guacamole_21_P.31_201105 (found on this thread under GM21AA tools -> Android 10 -> OOS 10.3.7: https://forum.xda-developers.com/t/...0-gm21ba-collection-of-unbrick-tools.3956595/)
The MSM tool completed its work with no errors and the phone rebooted after it completed. On the first reboot it spun on the red dot and white circles screen for a few seconds before rebooting itself again. On the second reboot it stayed on that spinning dot screen for 15+ minutes, after which time I powered the phone off. I can get into fastboot/recovery. My understanding was using the MSM tool should basically completely reset back to the factory image, am I doing something wrong? Is there anything else I can do at this point or is the phone just hosed?
Longer history
The phone was originally unrooted, stock, locked bootloader, etc. No changes done by me. The phone started having a few random reboots yesterday (and some games I were playing started throwing random security violations or just outright closing themselves). This morning the phone itself started rebooting every minute or two. This had also happened back in October and only after about 4 or 5 factory resets did it finally stabilize itself. Instead of going the same route again I did some search around searching around. I decided I'd try to replace the kernel with arter97's (https://forum.xda-developers.com/t/r64-arter97-kernel-for-oneplus-7-series.3952578/) since it seemed like the OS itself was randomly crapping out. I unlocked the bootloader, installed TWRP (twrp-3.5.0_9-0-guacamole.img) and Magisk (latest version) first in the same recovery session with no reboots in between. I rebooted and was having a bootloop issue at that point, but figured I'd proceed with the kernel update as well to see if that resolved it. When that also didn't help I decided I'd try to go the MSM route.