OPO Keeps rebooting all of a sudden! - ONE Q&A, Help & Troubleshooting

Hi Guys,
I seem to be having an issue with my OPO constantly rebooting. I decided to flash OxygenOS and after about a day i went back to Mahdi. Now all of a sudden, my phone keep rebooting on its own. It turns on and i can do whatever i want with it but as soon as i turn the screen off, it reboots....any idea as to why this is happening?
Thank you
UPDATE:
deleted the OS of the device, now i am stuck at the bootlogo. i can get into fastboot mode but not sure where to go from there

arty93 said:
Hi Guys,
I seem to be having an issue with my OPO constantly rebooting. I decided to flash OxygenOS and after about a day i went back to Mahdi. Now all of a sudden, my phone keep rebooting on its own. It turns on and i can do whatever i want with it but as soon as i turn the screen off, it reboots....any idea as to why this is happening?
Thank you
UPDATE:
deleted the OS of the device, now i am stuck at the bootlogo. i can get into fastboot mode but not sure where to go from there
Click to expand...
Click to collapse
Did you wipe properly before going back to Mahdi? If you can get into TWRP just copy a ROM across and flash it. Or flash the stock images via fastboot.
Transmitted via Bacon

Related

[Q] Bootloop and everything lost

Here goes: I was a happy OPO user using the latest crDroid ROM and AK kernel, when suddenly my phone entered the sleep of death. I turned it off and back on, and since then it is in an eternal boot loop, never going beyond the Oneplus logo.
I am able to get into fastboot mode as well as recovery mode (I am using Philz Recovery), however, here is where it gets weird. I was hoping to just flash another ROM from the recovery and fix the problem, but all my files and folders on the SD card are gone, almost as if the chip died.
I also tried flashing a different ROM using ADB, to no avail. ADB shows "OK" but nothing sticks. All I can successfully flash are the boot logo and the recovery. The phone never gets beyond the logo before it reboots.
Does anyone have an idea what else I could try? I feel like sending it back for a replacement, but I am afraid that this will take forever.
Do you have a OTG USB stick ? Maybe you can flash from there.
I was able to get my phone to boot using this:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
All data is gone though. But at least I don't have a brick any more.

[Q] Help needed with bricked 1+1

Hey guys, I tried something on my phone and everything went to hell.
The following scenario took place:
Last night, I flashed this ROM and it worked just fine. I played around with it a bit and then wanted to go back to my daleski75 version of Lollipop.
I wiped the phone through TWRP and restored my backup and it booted into it just fine.
The thing I noticed immediately was that the bootlogo was the ColorOS version. And then when I was using my phone, the only way to wake the screen up, was to plug in the charger.
So I decided to fastboot flash CM11S.
I entered -fastboot flash boot boot.img and my phone automatically rebooted and then it just went blank.
A black screen, but I get vibration when I try to shut it off or go into fastboot.
I don't see it in Device manager though.
Any help at all would be greatly appreciated.
Posessor said:
Hey guys, I tried something on my phone and everything went to hell.
The following scenario took place:
Last night, I flashed this ROM and it worked just fine. I played around with it a bit and then wanted to go back to my daleski75 version of Lollipop.
I wiped the phone through TWRP and restored my backup and it booted into it just fine.
The thing I noticed immediately was that the bootlogo was the ColorOS version. And then when I was using my phone, the only way to wake the screen up, was to plug in the charger.
So I decided to fastboot flash CM11S.
I entered -fastboot flash boot boot.img and my phone automatically rebooted and then it just went blank.
A black screen, but I get vibration when I try to shut it off or go into fastboot.
I don't see it in Device manager though.
Any help at all would be greatly appreciated.
Click to expand...
Click to collapse
Do you have the chinese or the international version?
Have you ever had Color OS Installed?
Make sure that your battery is not empty and try again. If you can't boot into fastboot or recovery you have to contact the Oneplus Support to repair your device.

LG G3 stuck in bootloop, even after flashing stock ROM

Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
Sadly that is because of a hardware issue. Been happening. A lot lately.
hyelton said:
Sadly that is because of a hardware issue. Been happening. A lot lately.
Click to expand...
Click to collapse
Alright, that's what I had read. Just seemed like a software issue so I was hoping for the best. I went ahead and ordered a new device. Im guessing a full motherboard replacement would be required to fix the device?
Recurring Issue
Hello,
The same problem happened to me a few days ago so this is trully a recurring issue.
I also tried to fix my rom by reinstalling it, then tried to install multiple new rom, and finally flashed the original stock rom. I also am stuck on the bootloop issue.
I'm going to contact LG to see if they can do anything to repaire it but my hope are very low.
I'll try to update this message if I find a solution.
Mine just started bootlooping and no wifi and today it just died. Battery pulls didnt work either no power at all. Probably going to switch to the V30 when its released.
Sent from my One using Tapatalk
ccraw said:
Device is a LG G3 D850, rooted, TWRP installed, stock ROM on 5.0.1
Here's the story: Yesterday I was browsing normally when the device froze up, then shut off. Wouldn't power on with the power button. I had to pull the battery and then it turned on. When the device booted back up, it was running very sluggish. Immediately noticed that the WiFi was constantly trying to turn on with no success (When entering the WiFi menu it only said "WiFi turning on"). Bluetooth would not turn on either. The battery was draining rapidly, about 20% in 30 minutes with no use. GSam Battery Monitor reported that Kernel (OS) had used 95% of the battery. I tried rebooting the phone with no success. Booted into recovery and cleared cache, no success. Couldn't find anything online besides people saying to try a different ROM/Stock rom or that they were told it was a failed motherboard. I tolerated using the phone into the night, but the battery was constantly draining and the phone temperature reported ~98 degrees even without use. The WiFi and Bluetooth never started working. Today, a few hours into the day, the phone shut off again. This time it started boot looping, going from the LG splash screen then the spinning AT&T screen, it would then hang and reboot (constantly boot looping). Battery pulls didnt help. Once or twice, the phone actually booted into the OS. After a minute it would start bootlooping again. I then booted into recovery and performed a factory reset. After the factory reset, the phone still bootlooped. I then booted into recovery and recovered to a previous nandroid backup. The phone booted up afterwards, with the WiFi actually working. After 5 minutes, the WiFi stopped working again and the phone proceeded to start bootlooping. My next attempt was to flash back to Stock ROM, using this method: http://forum.xda-developers.com/att-lg-g3/general/unroot-return-to-factory-stock-att-lg-g3-t2820827. The flash worked successfully, booting into the OS on the setup screen, but instantly started bootlooping again... The bootloop is a little different now, going from LG splash screen > Green android with blue spinning circle in his stomach > AT&T splash screen > then rebooting. I cant even get into TWRP now (When trying to boot into recovery and clicking yes on the default factory reset screen, it just reboots instead of going into TWRP) Im out of options, should I give up and buy a new device, or does somebody have any other suggestions?
Click to expand...
Click to collapse
It's probably to late but theres another method returning to stock KitKat dont know the link off hand in development forums. Sucks you couldnt try no adb methods. Still have the Phone want to sell it i need a cheap screen ?

No longer able to boot into recovery mode after flashing LineageOS

Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
AMpageg2 said:
Hi all, have a rooted OPO that was running ExodusOS. I decided to try a flash of Lineage and so booted into recovery, backed everything up, flashed it. Everything seemed to go okay but after the boot logo the screen just goes black and stays that way until it gets shut back off. I went back to TWRP, loaded my backup and all seemed well as I was still able to use my old backup just as normal. Well, I tried reflashing Lineage from TWRP again and I still get the same black screen issue. This time, however, the phone will neither boot into Fastboot nor into recovery mode and just goes straight into loading Lineage. Because of this I am left with a soft brick until I can get this straightened out. I tried connecting the phone to my PC but it is not detected as a device. I only need to boot into my backup one more time so that I can back everything up, so even if it's only a temporary fix, I'm okay with that too. Any suggestions?
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Sounds like a Hardware issue? Sorry to say what your saying doesn't add up and or make sense. Fastboot should work no matter what even if you soft brick it and mess up recovery. I suggest letting the power fully drain maybe and google how to fast boot in case you are doing it wrong.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
Click to expand...
Click to collapse
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
AMpageg2 said:
I've tried that but it can't find the phone. The phone gets detected as a new device in windows as evident from the device connection sound but it also never shows up in the list of devices from My Computer.
Click to expand...
Click to collapse
I agree with what @Shinobi_warrior said.Seems like you just have a soft brick,so you should be able to boot into fastboot mode without any issues.Are you sure you're doing it the right way? Did you try draining battery completely and then booting into fastboot(yes,you don't need much battery to boot into fastboot mode)?
Well I was finally able to get the device detected by ADB, but it just shows as offline. I attempted to use the repair kit and nothing seemed to happen. I also attempted a different tool (https://forum.xda-developers.com/on.../oneplus-one-toolkit-manudroid19-gui-t2807418) and then booting into either fastboot or recovery that way, a terminal window pops up and quickly disappears, and then nothing else happens. I still see the TugaPower boot logo and it still goes to the blank black screen after this.

Every Rom I've tried is just sitting at the boot up logo.

I've tried Carbon but that one wouldn't actually boot up, just shut my screen off and would shut itself off.
AospExtended ROM, is just sitting at these bouncing dots.
Ressurection Remix, sits at the boot screen of whatever that...logo is supposed to be.
I'm at my witts end here and about to smash this piece of junk. Nothing on this phone has ever worked right since I got it. Figured I'd fix it by getting rid of their trash UI and do custom roms but apparently it can't even do THAT right.
Upgrade your device to EMUI 8. Then flash one of the Treble ROMs.
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Spykez0129 said:
I can't even get into TWRP anymore. It just keeps going into the EMUI recovery everytime I hold down all 3 buttons.
Click to expand...
Click to collapse
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
SuperSwordSmasher said:
I've found out myself of why those custom roms wont boot, because you did not clear cache and dalvik before you booted to the custom rom. You wont have to smash ur phone if you do this.
Click to expand...
Click to collapse
That's something I do automatically without thinking. That stuff was finicky back in the OG Droid days so I always do it like 3 times just to make sure.
Anything else that would cause it to get stuck at the booting up screen? I get passed the blue screen and the your device is insecure or whatever. Then it just goes into the fancy booting logo and just sits there. Never on any of the phones I've rooted over the past decade ever got stuck like this.
WOHOOO! I MADE PROGRESS!
My phone is now stuck in a never ending bootloop and can't seem to get into any recovery. Can't even shut the phone off because it just turns itself back on. Backwards progress is where it's AT!
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Spykez0129 said:
Bump, any ideas?
I went back to Motorola and bought an X4 but I'd like to get this working again so I can sell it.
Click to expand...
Click to collapse
What honor 8 model do you use? It should not be Bootlooping then, if there is no solution you can always go to stock.
You could flash twrp again, with fastboot
Boot with power + volume up to boot into twrp
Use dload method

Categories

Resources