I tried booting into recovery today, and my R7 Plus just boots normally. It gives the vibrate indication, and then the OPPO logo flashes on for a split second... but then it gives up booting into recovery, the screen goes black again, and the phone boots normally.
If I hold down volume [-] and power, it keeps flashing the Oppo logo and then black screening every second until I let go of the buttons. It seems to me like it keeps trying to boot into recovery and then something goes wrong. After I let go of the buttons, it boots normally.
Booting to recovery through Flashify didn't work; it gave the same Oppo logo-flash before turning back and booting normally.
For some more background, after rooting my phone, I did some deleting of .com files and other Oppo-associated apps/files; I'm not a fan of ColorOS and any Oppo bloatware, so I probably deleted some pretty important stuff. Actually, I'm pretty sure I deleted something important along the way.
I would like to do a clean install to get all of the key firmware modules/files back, I can't do that without access to recovery. I tried unrooting and installing an official update, but that failed since I can't access recovery. What's more, I can't re-root because, again, recovery isn't available; Oppo Tools isn't working.
If I do a factory reset, does that restore all of the ColorOS data, including restoring deleted OS files, or does it just delete my user data and I still won't be able to boot into recovery? Is there a way to flash a stock ROM without recovery mode being available?
sendraww said:
I tried booting into recovery today, and my R7 Plus just boots normally. It gives the vibrate indication, and then the OPPO logo flashes on for a split second... but then it gives up booting into recovery, the screen goes black again, and the phone boots normally.
If I hold down volume [-] and power, it keeps flashing the Oppo logo and then black screening every second until I let go of the buttons. It seems to me like it keeps trying to boot into recovery and then something goes wrong. After I let go of the buttons, it boots normally.
Booting to recovery through Flashify didn't work; it gave the same Oppo logo-flash before turning back and booting normally.
For some more background, after rooting my phone, I did some deleting of .com files and other Oppo-associated apps/files; I'm not a fan of ColorOS and any Oppo bloatware, so I probably deleted some pretty important stuff. Actually, I'm pretty sure I deleted something important along the way.
I would like to do a clean install to get all of the key firmware modules/files back, I can't do that without access to recovery. I tried unrooting and installing an official update, but that failed since I can't access recovery. What's more, I can't re-root because, again, recovery isn't available; Oppo Tools isn't working.
If I do a factory reset, does that restore all of the ColorOS data, including restoring deleted OS files, or does it just delete my user data and I still won't be able to boot into recovery? Is there a way to flash a stock ROM without recovery mode being available?
Click to expand...
Click to collapse
Hi there, i know its been a long time. But i wanna know, have you solved your problem? If yes, could you please share how to fix it. Because im in the same situation right now.
Thank you.
Related
I scoured the forums, but have not been able to find out what I can do to solve my problem. So here it is.
I rooted my phone (to play around with some settings, what have you) and flashed TWRP recovery onto it. I got an error msg when booting up, so I decided to push an original recovery back onto the phone, because it wouldn't go to TWRP. I followed a guide (which I can't find now) to push back a stock version of recovery and it failed. My phone would boot normally just fine, but when I tried to go to recovery it would loop.
The OTA update came today, and dumbass me pressed continue (not thinking) and now I am stuck in a boot loop, and cannot get out of it.
Cannot get into recovery.
Cannot get into download mode.
Got any ideas?
Thanks
Same Problem
I have pretty much the same problem. Please help!
well without recovery/download mode working or the phone being in fastboot mode there really isn't much that can be done, you can always try to claim on warranty
boot loop
So, let me get this straight. If it failed when you tried to install the stock recovery, then you still have the TWRP recovery right?
I ran into a boot loop problem earlier when I tried upgrading TWRP. I just couldn't access my recovery so here is what I tried:
Code:
Turn your phone off.
Press volume down and power button until the LG logo comes on screen
Let go of both buttons
Hold the volume down and power buttons again until you see the "hard reset screen"
Press power once and then power again to confirm. The screen says it will reset your device but it will not as long as you have a custom recovery installed.
Your custom recovery should appear on screen.
Try the steps above and see if you can get into a recovery. Once you do maybe try resetting. Hope that helps.
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
RightHanded said:
Hello.
Today my oneplus one was suddenly stuck in bootloop. This happened in the middle of the day when I rebooted my phone. My phone was running the latest update that came OTA (stock lollipop). Whenever I boot my phone it starts loading and suddenly a Chrome (browser) window appears for 1 second and tries to load a website. Afterwards my lock screen pop ups for 1 seconds and it starts to reboot. During the lockscreen I tried to unlock my phone as soon as possible, but it just reboots. (Any ideas about this weird problem?)
I CAN boot it in recovery mode by holding volume-down button and power button.
I CAN boot it in fastboot mode by holding volume-up button and power button.
Perhaps a factory reset will do the trick, but I don't have a backup of my files (because this happened so suddenly without me trying to flash/customize my phone). My first priority is recovering my files, because most solutions will end up in me losing every file. Unfortunately I've found little possibility to do this during the bootloop problem. I've tried to flash TWRP because it could make backups of my phone. I tried it through ADB/Fastboot, but it failed because my device is not unlocked (I can't go to settings and put my phone in developer mode and debugging mode). So I've read somewhere that unlocking my phone (bootloader?) through ADB will wipe my phone, which is exactly what I don't want.
Also I've tried this: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
But It also failed because my device was not unlocked.
Did I miss some steps somewhere or did I read something wrong?
Hopefully anybody has an idea to either fix the bootloop without losing my data, or finding a way to recover my files before wiping the phone.
Thank you.
Click to expand...
Click to collapse
Unfortunately you might be stuck in a catch-22 situation here. In order to access the files you'd need to unlock the bootloader, but in doing so you'd lose those files. Without usb debugging already enabled I can't see a way out of this.
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
EDIT: Managed to fix it eventually through: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061 (part 2) writing the command in TWRP.
Phone finally boots normally again.
RightHanded said:
Decided to unlock the bootloader through ADB. (bye bye data)
After I've unlocked it, I've tried installing TWRP.
Some minor problems occured but I can finally boot into TWRP through volume-down button + power button.
I've decided to download the stock ROM i've found on the OPO forums.
Couldn't acces my phone through normal methods, so I had to use ADB to push the files into my phone.
Installing the file through TWRP, wiped cache/dalvik and installed super user before rebooting.
After rebooting my phone is stuck on the boot screen now. (This also happened before I installed TWRP on my phone)
I've also tried this method: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Also no succes. I'm stuck in the bootscreen where it says 'cyanogen'.
Any other way to fix this problem?
Click to expand...
Click to collapse
Exactly what did you flash? Full filename please. No errors occurred?
Heisenberg said:
Exactly what did you flash? Full filename please. No errors occurred?
Click to expand...
Click to collapse
Hopefully the stock cyanogen OS.
First I've tried to flash cyanogenmod 12 through TWRP (file is found here: https://forums.oneplus.net/threads/cm12s-yng1tas17l-installation-guide-review-change-log.304615/)
Afterwards I was still stuck in bootscreen, so I've looked for another solution.
Which made me find this guide: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
After flashing this file (probably the same thing) the problem still remained.
Eventually after multiple wipes/factory resets (which did not solve the problem) I've entered the command in TWRP and after reboot it finally worked again.
So I basically flashed my phone twice, once through TWRPS and the other through the batch file (perhaps ADB?).
Also no errors occured which stopped the flashing and commands. Did have to reinstall TWRP and reboot instantly in it by holding the volume down button multiple times. This doesnt happen anymore though.
Only had to install google apps for CM12 (gapps), for which I used TWRP in recovery mode.
Currently reinstalling most apps on my phone and no problems yet.
Hi there, having just the old casual phone crisis. I was running cyanogenmod 12.1 for awhile and decided to finally upgrade to a nougat 7.1 build.
I tried using this one https://forum.xda-developers.com/google-nexus-5/development/rom-dark-rom-t3492150 using adb sideload as I had tried a earlier one and the gapps messed up so I wasn't able to put twrp back on the phone. The rom said it had installed successfully but I wasn't able to sideload gapps, I kept getting an error status 255. I went ahead and just tried to load the rom without gapps and see if I could install it slowly through APKs. I managed to get past the initial android load and the services started up, and it got in an endless crash loop because the phone service wouldn't start. So I went to try and flash another rom and was going to delete the cache. When I went to delete the cache the phone hung for about an hour so I tried to just reset it into recovery mode again.
Now when I hold the power button and volume down key to into fastboot mode I can. I have access to the initial screen with the four options, but when I try to start recovery mode or start the phone my screen goes black, and it'll flash the dead android symbol with the error saying unable to mount cache, it only flashes it for like half a second then goes black and repeats every 10-15 seconds.
I tried holding power down, doing volume up, and letting go to do a hard factory reset but it does nothing. I also can't seem to access the adb sideloading anymore, I'm very scared that it's hard bricked, is there anything I can do at all to fix this.
Flash a new version of the recovery via fastboot. Then do a full wipe. After that install the ROM only! Reboot recovery (not system but recovery) then reflash the ROM (no wipe) and add everything else. Hope this helps you out.
The phone may not boot the ROM without wiping data if installing a 7.1 ROM over a 5.1.1 ROM.
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Yippee38 said:
I unlocked the bootloader on my phone, then flashed twrp. I rebooted to twrp and installed boot.img, TWRPWorkingInstaller.zip, TWRP-BLUE-FIX.zip, and Root.zip. Rebooting worked fine, but I saw that there was a newer twrp (twrp-3.2.1-3-wOOSkernel.img, so I tried installing it from twrp. The problem is that I installed it to the system image partition. After that, everything got wonky, unsurprisingly. Now, if I try to boot to twrp, it loads and I get to the first menu, but I cannot interact with it at all. Then the screen goes black and the led lights up blue. It doesn't respond to anything except shutting it down. I can hold the power button down to power off, but it reboots instead to a black screen with the blue LED. I can also boot into the bootloader. I can reflash twrp. When I restart to recovery then, I get the screen asking if I want to keep the system files locked or swipe to unlock it. The device seems to work fine for about 5 seconds from the time I get to the first twrp menu, then it doesn't respond. About 5-8 seconds later, the screen goes black and the blue led comes on. I also cannot power-off the device. If I try, it reboots.
Is there anything I can do to recover from this? I've got the stock recovery files (OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0e704ca3.zip), but I can't copy them to the device because it won't boot to the OS.
Click to expand...
Click to collapse
Do you have a TWRP backup from when your phone worked on an external drive?
Can you access fastboot? Just use the fastboot ROM files to reflash the OS. Or if that doesn't work try the unbrick tool.
Yeah. I can use fastboot. However, I wasn't able to get to ROM to flash. I'm not sure if I'm using the correct parameters in the command. I googled, but all I came up with was flashing custom ROMs. Where can I find the unbrick tool?
NM. Found the unbrick tool. I may try it. I'll let you know how it works.
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Yippee38 said:
Thanks for your help @NateDev!. The Unbrick Tool helped me fix it.
Click to expand...
Click to collapse
Glad you got it solved
My relatives have gotten this watch gifted to them a while back but it was in chinese so to get it to English I had to unlock bootloader and flash the room. But while doing so I by mistake flashed twrp instead of booting into it on the Recovery Partition right after unlocking bootloader and after rebooting, it was stuck in a horrible bootloop. Why is it horrible?
So the problem is, it keeps booting into twrp, fails to mount data cache and everything, shuts down and reboots again, shows a warning that it can't detect an operating system and continues to boot into the same twrp recovery and so on. When I try to boot into bootloader, it says to go to g.co/ABH and read instructions to proceed, but after holding down the button to continue to boot, it goes back to the same bootloop.
I cannot boot it into bootloader or get it into fastboot, I can't do anything in twrp and I can't boot into os (cause of course, there is none). Does anyone know how I can fix this? I've been struggling for 4 hours with this today. I'm really scared that I've completely bricked it and can't restore it .
I can see it in adb devices while it's in twrp and twrp is freaking out then shutting down, but I can't even side load a rom to even install something I can boot into.
Link me a thread if there is one where this problem gets fixed or help me please. Thank you!