i think my phone is soft bricked. while opening recovery it stucks in oneplus logo and while booting also it stucks at oneplus logo and then restart itself
You take your time to post this thread but... you dont have time to google it? Seriously, dont mess with roms unless you have the time to search for possible solutions when you have a problem. Found it writing "oneplus 2 soft brick" in google btw
Writing a post asking for help is last solution.
^As stated above, always perform your own search for a solution to your issues.
That being said, I have posted a link below that will take you to a thread where a solution has been posted for "Soft Bricked" OnePlus 2 devices.
Solution for Soft Bricked OP2
Hope this helps and welcome to the OnePlus 2 family on XDA!
Sent from my OnePlus 2 running H2OS
piyushsoni24 said:
i think my phone is soft bricked. while opening recovery it stucks in oneplus logo and while booting also it stucks at oneplus logo and then restart itself
Click to expand...
Click to collapse
And this without unlocking or flashing some other ROM, recovery, H2OS or OOS Marshmallow build? The usual explanation for this would be if you update to the beta Marshmallow builds of the mentioned OEM ROMs and not flashing a recovery compatible with the bootloader in these ROM updates....
Related
Okay, so I flashed my phones recovery using adb with twrp, but when I went into recovery mode,
it was installing an update that would reset it to stock rom. I held the power button to stop that,
and now it's stuck in a bootloop and wont boot into recovery or bootloader. Is it hard bricked or is there still
hope? Should I just wait it out?
Any progress/solution?
If not try: [GUIDE] How to unbrick HUAWEI P8 when failed to update and ends in bootloop
GaT7 said:
Any progress/solution?
If not try: [GUIDE] How to unbrick HUAWEI P8 when failed to update and ends in bootloop
Click to expand...
Click to collapse
Yeah, forgot to say anything. After a while of constant bootlooping (like 2.5 hours) it went into the bootloader by itself so I was able to restore the stock rom. For anyone that has the same problem as me, while it was bootlooping I sent a mail to huawei about this and their anwser was to hold the Power button for 20-30 sec. I couldnt test this because it was already fixed but it might have worked.
Quick note: If anyone else tries to root the Huawei P8 with twrp 2.8.7.1 it wont work on Marshmellow. Follow this post http://forum.xda-developers.com/huawei-p8/how-to/guide-install-twrp-root-systemless-t3325161.
You can Easily Fix your Device , Just follow the Steps Carefully
Follow this link to fix your Mobile:
This Tutorial is easy to follow. Fix your device and Return to your OFFICIAL STOCK ROM
https://youtu.be/4AkSuE20_08
Links are included in video Description .
Cheers...!
I bricked my mobile few months ago and I fixed my mobile using this video , hope it will help you guys too.
Good morning everyone
I come here for I'm desperate.
I was using my Nexus 6P and it restarted and then went into bootloop in "Google" already tried to restore several times with the "Nexus Root Toolkit" but without success.
I do not know what to do I'm already terrified even though I do not have a warranty because I bought out of my country
Could someone please help me?
Sorry for the bad english if someone can help me I'm very grateful, because I do not know what to do and I do not understand much about it
Honestly if the phone went into a boot loop completely on its own and you weren't flashing anything it's probably the boot loop of death and there's nothing you can do. If you can get to the bootloader using the volume and power keys you can try flashing a full factory image--but that's only if you enabled OEM Unlocking and USB Debugging in the developers menu before the phone bootlooped. There are threads in XDA dedicated to the boot loop of death plus lots of posts like yours. It's a known problem that there is no solution to.
Tavinlol said:
Good morning everyone
I come here for I'm desperate.
I was using my Nexus 6P and it restarted and then went into bootloop in "Google" already tried to restore several times with the "Nexus Root Toolkit" but without success.
I do not know what to do I'm already terrified even though I do not have a warranty because I bought out of my country
Could someone please help me?
Sorry for the bad english if someone can help me I'm very grateful, because I do not know what to do and I do not understand much about it
Click to expand...
Click to collapse
Maybe Chinese Taobao can help you
jhs39 said:
Honestly if the phone went into a boot loop completely on its own and you weren't flashing anything it's probably the boot loop of death and there's nothing you can do. If you can get to the bootloader using the volume and power keys you can try flashing a full factory image--but that's only if you enabled OEM Unlocking and USB Debugging in the developers menu before the phone bootlooped. There are threads in XDA dedicated to the boot loop of death plus lots of posts like yours. It's a known problem that there is no solution to.
Click to expand...
Click to collapse
I can restore the software in the Nexus Root Toolkit, I can unlock and block the bootloader plus the "Google" permanace boot loop
I can install ROM's and always stays in bootloop
Tavinlol said:
I can restore the software in the Nexus Root Toolkit, I can unlock and block the bootloader plus the "Google" permanace boot loop
I can install ROM's and always stays in bootloop
Click to expand...
Click to collapse
I think your phone is now an expensive paperweight. I've read lots of ideas people have come up with for getting out of the type of boot loop you are now in but I don't remember ever reading one that actually worked. Maybe someone can help you and I'm wrong but I seriously doubt it. Good luck.
jhs39 said:
Honestly if the phone went into a boot loop completely on its own and you weren't flashing anything it's probably the boot loop of death and there's nothing you can do. If you can get to the bootloader using the volume and power keys you can try flashing a full factory image--but that's only if you enabled OEM Unlocking and USB Debugging in the developers menu before the phone bootlooped. There are threads in XDA dedicated to the boot loop of death plus lots of posts like yours. It's a known problem that there is no solution to.
Click to expand...
Click to collapse
please bro for me i have nexus 6p with bootloop i can enter in bootloader mode with volum my phone is unlocked ant i try flashin factory image with fastboot mode when i reboot the phone he take time but just android logo
do you have any idea to help me
Tavinlol said:
I can restore the software in the Nexus Root Toolkit, I can unlock and block the bootloader plus the "Google" permanace boot loop
I can install ROM's and always stays in bootloop
Click to expand...
Click to collapse
As @jhs39 already told you, your phone is likely dead. If you have access to recovery, try sideloading the latest OTA from Google site. But if you only have bootloader access and flashing stock firmware doesn't fix your issue, it's dead...
Good luck...
leroilion02 said:
please bro for me i have nexus 6p with bootloop i can enter in bootloader mode with volum my phone is unlocked ant i try flashin factory image with fastboot mode when i reboot the phone he take time but just android logo
do you have any idea to help me
Click to expand...
Click to collapse
Hey...
Check this thread:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
If your issue is similar and you only have bootloader access, it's dead...
Good luck...
I am on the same boat with my Nexus 6P bootlooping. The Nexus 6P went into bootloop during 7.1.2 update. The phone was bought from a Canadian carrier and was out of warranty by a few weeks. Both Huawei and Google refused to help and while courteous gave a lot of run around. Disappointed and helpless that a otherwise perfectly working and excellent device was turned into a expensive paper-weight and the vendors would not take responsibility
I was able to solve the problem on my device
1- I access bootloader on my device
2 - In the Nexus Toolkit I went to Advanced Utilities, fastboot format and fastboot erase.
3 - Back to start page I left it marked "Soft-Blicked / BOOTLOOP" and I used NUF26N http://prntscr.com/euczlb
4 - After completing the process the Nexus was in bootloop for 5 minutes and started normally.
I do not know if it was a divine miracle or if it was something that I did,
leroilion02 said:
please bro for me i have nexus 6p with bootloop i can enter in bootloader mode with volum my phone is unlocked ant i try flashin factory image with fastboot mode when i reboot the phone he take time but just android logo do you have any idea to help me
Click to expand...
Click to collapse
Did you mean the Google logo, or the Android startup animation? What about this? https://forum.xda-developers.com/showpost.php?p=71699404&postcount=15
Tavinlol said:
I was able to solve the problem on my device
1- I access bootloader on my device
2 - In the Nexus Toolkit I went to Advanced Utilities, fastboot format and fastboot erase.
3 - Back to start page I left it marked "Soft-Blicked / BOOTLOOP" and I used NUF26N http://prntscr.com/euczlb
4 - After completing the process the Nexus was in bootloop for 5 minutes and started normally.
I do not know if it was a divine miracle or if it was something that I did,
Click to expand...
Click to collapse
My device died again....
Tavinlol said:
My device died again....
Click to expand...
Click to collapse
Hey... Just Hoping you took the time to backup everything important on your phone...
You only have access to bootloader yet? If yes, check this thread: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
I would call Google or Huawei and try getting your device repaired/replaced. Some people have had their device replaced even being out of warranty.
Good luck..!
What does your device say in device manager when you plug it into your pc?
---------- Post added at 11:32 PM ---------- Previous post was at 11:32 PM ----------
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779
---------- Post added at 11:33 PM ---------- Previous post was at 11:32 PM ----------
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
DEVILOPS 007 said:
What does your device say in device manager when you plug it into your pc?
---------- Post added at 11:32 PM ---------- Previous post was at 11:32 PM ----------
https://forum.xda-developers.com/nexus-6p/general/qpst-qfil-answer-to-issues-t3455779
---------- Post added at 11:33 PM ---------- Previous post was at 11:32 PM ----------
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Click to expand...
Click to collapse
Bootloader service.
I'm sending my Nexus 6P for warranty as in my case i bought in another country
I'm buying a OnePlus 3t to replace it, because I can not wait
I have tried flashing both TWRP and the original recovery through Fastboot but the phone just won't boot to neither recovery. If I try to boot recovery, the phone gets stuck to the first boot screen with white oneplus logo in the middle.
Im running OxygenOS 3.1.0 on my OnePlus 2 device. The phone has encryption but I can't remove it. There is no option in settings to remove the encryption and if I try to do a factory reset through settings, the phone reboots and gets stuck the same way when I try to boot to recovery.
I can still boot to my current ROM but I wan't to get rid of it. I can't think of any way to decrypt the phone and I think this recovery issue is encryption related. The phone booted fine to both recoveries before I encrypted the phone. Is there any way to remove this retarded encryption? I want the phone completely wiped clean and start fresh. I will never encrypt my phone again...
You should try second method in this https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
It will restore the phone back to original.
Hope this helped.
Sent from my ONE A2005 using Tapatalk
[SOLVED]
I solved this issue just now by using this OnePlus 2 unbrick guide from YouTube:
For me it didn't boot straight away to the recovery like at 2:16 in the video (my phone got stuck again to the OnePlus logo screen). I had to turn off the phone first and then boot again to make it work. Case SOLVED!
4z4 said:
I solved this issue just now by using this OnePlus 2 unbrick guide from YouTube:
For me it didn't boot straight away to the recovery like at 2:16 in the video (my phone got stuck again to the OnePlus logo screen). I had to turn off the phone first and then boot again to make it work. Case SOLVED!
Click to expand...
Click to collapse
my Google Pixel XL is like that...
can you maybe help me to fix it too?
tasty_boy said:
my Google Pixel XL is like that...
can you maybe help me to fix it too?
Click to expand...
Click to collapse
I'm not familiar with Google phones but I suggest you try to find unbrick guide for your phone model if nothing else works. Good luck!
Hi Community,
I had to reset my oneplus 5 because of a annoying adware that i might have got from something n was experiencing ad pop ups even on the home screen. So i did a factory reset from setting. My phone restarted and the boot screen appeared. After one or two mins both white dots of bootlogo merged and big red logo appeared (device was about to go to setup page) but instead of going to setup screen a black screen appeared and again bootlogo started rolling... i thought its a reset process but it just on for a long time, around 20 mins. So i restarted the device by holding power button and phone restarted to the setup screen in no time.
I again did a reset and same thing happened
Can some please tell me was that normal or was a bootloop??
Please help
What?
...
PwnedBySumo said:
What?
Click to expand...
Click to collapse
Sorry that was an error occured...updated the thread with the issue. Kindly check
Someone please reply
You have a couple of options:
1.) If your bootloader is already unlocked and you're using TWRP then just download the latest 4.5.10 ROM from OPs website and flash it.
2.) If not then download the rescue image from OP, go into fastboot mode and flash it from there.
There are many guides around the internet on how to do both methods
What exactly do you want us to say?
Yeah it was a bootloop?
Just be patient next time?
its a bug and i reproduced this issue on my friends op5 too and the same thing happened.
Sarath280 said:
its a bug and i reproduced this issue on my friends op5 too and the same thing happened.
Click to expand...
Click to collapse
In that case you could report it to oneplus
nxss4 said:
In that case you could report it to oneplus
Click to expand...
Click to collapse
i have already reported this issue to them but no response.
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.
I'm having this screen too, I'm trying to gsi, but none works, only lineage 16, but it gives error and closes the system at 16, and at lineage 15 the battery is being drained very quickly
Any rom stock I try to flash via edl gets in bootloop on the penguin screen, I can do the flash via edl from a los rom with 15.1 with oki twrp, some bugs, but would like to return to stock, can anyone help us?
same issue
Hello there
I have the same issue, can you please help ?
Thank you in advance
prasnel
kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Hi XDA developers community,
Using some of the guides on this fantastic website I flashed LineageOS on my A2017G a few months ago. Now I tried reverting back to stock by flashing the B03 Oreo zip file in EDL mode (this guide).
The first reboot was already successful: I powered the phone on via the power button, then went through "can't be checked for corruption" screen, then got into the screen with Tux (Linux penguin), pressed volume up to go to recovery just to be sure, and rebooted from there into Android.
Although instead of starting the setup process Android dropped my right into the lock screen. I assumed that was because I hadn't factory reset yet and my data partition still had garbage data (that was step 18 of the guide btw). So, I powered off, from Android, and tried booting into recovery mode again to do the factory reset. However, now, after the Android corruption warning screen, the Linux Tux screen just stays there. Recovery mode doesn't appear, neither did it boot into Android. I can't even force power off by pressing the button (I pressed 80 seconds straight, no effect). No combination of volume and power buttons does anything, even pressing and holding it.
Right now I plan to let the battery drain on its own to get the device to power off. That's probably gonna take some days because the battery is completely charged. Is there some other possibility to make it go faster? Maybe heat the battery up from the outside with a hair dryer? I would rather not open the phone up and take the battery out, because I don't have a heat gun and I'm also worried I'm gonna leave scratch marks or something (the process seems quite rough).
And also, when the battery is drained, is there any recommendation on what I should do? Simply try again, going into recovery mode? Flash the EDL file again?
Thank you for reading all this, and I'd be so glad for any help.
Click to expand...
Click to collapse
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !
afef said:
My phone is like u "zte axon 7 a2017g " version oreo b03 please tell me the guide that u used to install lineage os and the tools please !!!
i just want to install unloack my bootloader , flash twrp , install lineage os so on ; please give me just the guide that u use !
Click to expand...
Click to collapse
Sorry, I don't remember
kangalioo said:
Sorry, I don't remember
Click to expand...
Click to collapse
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !
afef said:
u don't remember if the guide is for marshmallow or naugat a 2017 g or i can use guide for a2017 u !
Click to expand...
Click to collapse
what
kangalioo said:
EDIT: Thankfully I could resolve this issue on my own fairly easily. My battery drained relatively quickly, and the issue didn't repeat when I tried booting again.
Click to expand...
Click to collapse
Mine didn’t reboot at all after completely draining the battery several times. Same result, blocked on penguin screen, no way to get into a menu to flash anything ?
kangalioo said:
what
Click to expand...
Click to collapse
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !
afef said:
My phone is "zte axon 7 a2017g" version oreo b03 , i want to find guide make me unloack bootloader , flash twrp , install lineage os ; i just want for if u can remember if what can proch me i can use because the only guides exist are for a2017u or a 2017 g marshmallow or naugat
or if u can tell me if i can downgrading from oreo to marshmallow without unloack bootloader to use the guide exist for marshmallow !
Click to expand...
Click to collapse
As I said, I don't remember. I'm using a different phone altogether since half a year.
So because only a Tux logo appeared on the screen, my guess as to what happened is that while the Android Bootloader, also called "aboot" was booting the Linux kernel that Android runs off of, before the kernel could display the splash screen that appears when you power on the device, it encountered a critical error that either aborted the boot process, or caused the kernel to go into a kernel panic. Now as to why it displayed the Tux logo, it probably did that because when it crashed, it tried mapping the framebuffer to the display instead of keeping in hidden by default to show you the kernel buffer logs for you to troubleshoot the problem but instead, it shows the iconic Linux penguin that is usually hidden when the kernel boots.