Hey all,
I have just run into an issue, I was installing CWM and all seemed well, but then when I had tried to boot into recovery by holding down the buttons.
However, when it would say recovery booting it would flash turn off and reboot.
I figured it was just an issue with how I was trying to get into the recovery so I used ADB to Reboot into recovery, and that went fine but now I am in a boot loop of the phone trying to get into recovery but when it isnt seeing CWM for some reason it just reboots and continues the cycle.
I would appreciate if anyone has any insight as to how I can fix this or lets hope its not this but if Im screwed at this point.
Thanks in advance,
nEmo
Gahh... This is really getting to me, I've tried everything I can think of.
No one out there has any ideas?
I know Im not being very patient but its the only phone I have access to right now
It almost seems like there is either no OS on it (I hadn't wiped anything at this point) so this is the least likely,
or there was something wrong with the version of CWM that I was trying to use.
I think why I can't connect anything or do anything like that is because it keeps trying to look for the recovery
but because CWM isn't properly there it just keeps looking for it and just keeps on going in that loop.
would love to hear from anyone.
Thanks again.
i
nemofunk said:
Hey all,
I have just run into an issue, I was installing CWM and all seemed well, but then when I had tried to boot into recovery by holding down the buttons.
However, when it would say recovery booting it would flash turn off and reboot.
I figured it was just an issue with how I was trying to get into the recovery so I used ADB to Reboot into recovery, and that went fine but now I am in a boot loop of the phone trying to get into recovery but when it isnt seeing CWM for some reason it just reboots and continues the cycle.
I would appreciate if anyone has any insight as to how I can fix this or lets hope its not this but if Im screwed at this point.
Thanks in advance,
nEmo
Click to expand...
Click to collapse
there is also temporary state for recovery and that might be the cause of this
so try to reflash recovery through adb
:good:
Geeks Empire said:
there is also temporary state for recovery and that might be the cause of this
so try to reflash recovery through adb
:good:
Click to expand...
Click to collapse
Thanks for the reply, I would love to do that but the part that it actually gets stuck at is before any of the OS is loaded,
What happens is when there is power to it (ie battery or when plugged into a wall socket) it will try to boot as if I had held
down the vol +, Power and home and get the "recovery booting" text, from here the screen turns off and vibrates, a second or two later it reboots and repeats.
I might try to get a video of it tomorrow.
Thanks again,
nEmo
nemofunk said:
Thanks for the reply, I would love to do that but the part that it actually gets stuck at is before any of the OS is loaded,
What happens is when there is power to it (ie battery or when plugged into a wall socket) it will try to boot as if I had held
down the vol +, Power and home and get the "recovery booting" text, from here the screen turns off and vibrates, a second or two later it reboots and repeats.
I might try to get a video of it tomorrow.
Thanks again,
nEmo
Click to expand...
Click to collapse
U don't need to load OS to do this just boot to Fastboot and use adb interface
If it was useful please hit thanks
Sent from my D6503
A Million Thanks!
Thank you my good Sir!!!
Did just the trick, for some reason I totally overlooked Fastboot.
Always helps to have someone to bounce ideas off of, or someone that knows what they are doing ! HAHA
Thanks again!
nEmo
Hi, running into the same problem here
nemofunk said:
Thank you my good Sir!!!
Did just the trick, for some reason I totally overlooked Fastboot.
Always helps to have someone to bounce ideas off of, or someone that knows what they are doing ! HAHA
Thanks again!
nEmo
Click to expand...
Click to collapse
Hello, so as the title mentioned, I am in something of a similar predicament. Odin Mode is stuck, and it won't recognize any recovery on the phone. How do you boot into fastboot? Could you describe what you did? Thank you in advance.
Odin mode and recovery mode are two different things. You can't get into download mode where you see the android with the shovel?
Related
I am new to the android world, I have a vibrant that I rooted using the update.zip method. Then I went to apply the LAG FIX using the same method from the RyanZA thread. Now all I get is a boot sound and a black screen along with the buttons on the bottom glowing. I have no Idea where to even begin to recover this. I have a mac, any suggestions would be helpful. Thank you in advance!
Fathom0195 said:
I am new to the android world, I have a vibrant that I rooted using the update.zip method. Then I went to apply the LAG FIX using the same method from the RyanZA thread. Now all I get is a boot sound and a black screen along with the buttons on the bottom glowing. I have no Idea where to even begin to recover this. I have a mac, any suggestions would be helpful. Thank you in advance!
Click to expand...
Click to collapse
That's a boot loop. In your case, being new and all, it might be better to re-install the ROM and try again. You might need to give it a while as well, I don't know the details of the zip you used, but it might be copying large amounts of data, which will look like a stall in the boot process.
Get ADB and open a terminal window and do "adb logcat" it should let you know where you are stuck in the boot. Post the log and someone here should be able to help you.
Also, get boot camp and/or Virtualbox going so you can use Odin, which requires Windows. If you mess something up, you can use Odin to get back to a stock setup. Sucks that it requires Windows, but that's just how it is for now.
Oppps mis-read this phone is complete black no noise just heat
Moved your thread to general section.
Had the same problem when I tried to install that FixLag update.zip. Lucky for me, I did an Anroid Backup before I attempt it.
Hold down Vol+ & Vol- and power it up, do a Wipe.. when its done, restart your phone. When its booting up, its gonna act the same without the Tmobile Flash and still missing the Samsung Galaxy S logo. Just wait for your phone to VIBRATE. Then your phone should be working. I dont know what happen in that update.zip but it deleted the Graphic at the beginning when you first boot up your phone. After that I went back and did a Recovery and got everything back too normal.
kiddiosky said:
Had the same problem when I tried to install that FixLag update.zip. Lucky for me, I did an Anroid Backup before I attempt it.
Hold down Vol+ & Vol- and power it up, do a Wipe.. when its done, restart your phone. When its booting up, its gonna act the same without the Tmobile Flash and still missing the Samsung Galaxy S logo. Just wait for your phone to VIBRATE. Then your phone should be working. I dont know what happen in that update.zip but it deleted the Graphic at the beginning when you first boot up your phone. After that I went back and did a Recovery and got everything back too normal.
Click to expand...
Click to collapse
It worked!! Thank you so much! I am back up and running. No boot screens, however funtional and root maintained. Is there a way to recover the boot screens?
I was just searching through the forums for the answer to the last post in this thread - "is there a way to reinstall the boot animation? Well, is there? Mind, I DO NOT want the horrible tmo portion, just the S.
Thought?
Droidicus said:
I was just searching through the forums for the answer to the last post in this thread - "is there a way to reinstall the boot animation? Well, is there? Mind, I DO NOT want the horrible tmo portion, just the S.
Thought?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7663822&postcount=38
I just did this to my phone like the ones stated above..... Blank screen then vibrate and im in the Android OS and it changed the Audio but still no graphics....... Kinda disapointing but until someone finds hwo to actually finx this I'm stuck.
My phone is stuck in a boot loop after it automatically installed an OTA update when on a custom ROM. at first recovery worked, tried installing a custom rom from fresh with the sideload in CWM, then after reboot recovery does not boot, just LG logo and restarts again. Any ideas?
Need it fixed badly no phone for 5 days now.
LightInDark said:
My phone is stuck in a boot loop after it automatically installed an OTA update when on a custom ROM. at first recovery worked, tried installing a custom rom from fresh with the sideload in CWM, then after reboot recovery does not boot, just LG logo and restarts again. Any ideas?
Need it fixed badly no phone for 5 days now.
Click to expand...
Click to collapse
I just did this today, and also am out of a phone for now, apparently I lost the software, and in the process of trying to get out of the ota i blocked twrp. Anyway, does yours just go on the lg logo and have the pulsing led? Thats what mine does and I think I can get into download mode which may help. But it wont show up when I plug it in . Good luck to you, if I figure something out ill post it here.
Oxiit said:
I just did this today, and also am out of a phone for now, apparently I lost the software, and in the process of trying to get out of the ota i blocked twrp. Anyway, does yours just go on the lg logo and have the pulsing led? Thats what mine does and I think I can get into download mode which may help. But it wont show up when I plug it in . Good luck to you, if I figure something out ill post it here.
Click to expand...
Click to collapse
No LED but it just loops on the LG logo over and over, no access to download at all, tried all combinations but if i hold in power+vol buttons it eventually just gives flashing red LED until i let go of the power then it starts boot looping again.
LightInDark said:
No LED but it just loops on the LG logo over and over, no access to download at all, tried all combinations but if i hold in power+vol buttons it eventually just gives flashing red LED until i let go of the power then it starts boot looping again.
Click to expand...
Click to collapse
The red led is what i get when I try to go into download mode too. Just holding down the down and up takes me to that and it keeps going until i press another button. Thats odd you have no led though.
Is this just unfixable? I really need my phone back.
Its the same thing that happened to me the other day. Theres a way to fix hopefully, try this thread http://forum.xda-developers.com/showthread.php?t=2582142&page=3
My posts are at the end and mine is totally unrecoverable at the moment so off to Verizon for me. There are others in my shoes too but I would try that thread first to see if you can recover. If you do go thru ubuntu and only get " /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 "
your pretty much hosed from what I gather. No one has all the files to recover from where I'm at. See my posts on page 13 and 14.
Hopefully someone can figure this out but I cant wait for it to happen. Good luck
Camoxjeep said:
Its the same thing that happened to me the other day. Theres a way to fix hopefully, try this thread http://forum.xda-developers.com/showthread.php?t=2582142&page=3
My posts are at the end and mine is totally unrecoverable at the moment so off to Verizon for me. There are others in my shoes too but I would try that thread first to see if you can recover. If you do go thru ubuntu and only get " /dev/sda /dev/sda1 /dev/sda2 /dev/sda5 "
your pretty much hosed from what I gather. No one has all the files to recover from where I'm at. See my posts on page 13 and 14.
Hopefully someone can figure this out but I cant wait for it to happen. Good luck
Click to expand...
Click to collapse
No doesn't work, that fix requires the phone to get PAST the LG initial turn on logo, but it only comes on for 10 seconds then reboots again, not enough time for USB to enable on the phone itself so PC can't even detect it.
Just LG for 10 seconds, off, then LG for 10 seconds and does it over and over.
Anyone else with an idea?
I'd rather not send it away because don't want to get in trouble for having recovery and custom ROM on the phone.
Did you figure out the solution?
I'm stuck in bootloop too, can't connect to the phone to use adb anymore after i tried to install trwp. Download mode isn't seen by my computer...
my galaxy s4 is always boot looping into Samsung galaxy s4 screen. only the download mode screen appears but it reboots again after 5 seconds and keeps on rebooting . any help ?
Do you run with stock or custom recovery? Have you tried to (re-)flash a custom recovery (CWM highly recommended)?
slytidar said:
my galaxy s4 is always boot looping into Samsung galaxy s4 screen. only the download mode screen appears but it reboots again after 5 seconds and keeps on rebooting . any help ?
Click to expand...
Click to collapse
I had this problem once. I had to clear all user data,cache,dalvik and intall everything again
Chalao said:
Do you run with stock or custom recovery? Have you tried to (re-)flash a custom recovery (CWM highly recommended)?
Click to expand...
Click to collapse
thanks for the replay
i flashed a custom recovery. this happened later on. but now that the download mode is rebooting it slef and recovery isnt coming, i dont think i can flash a recovery..
MarceloSiciliano said:
I had this problem once. I had to clear all user data,cache,dalvik and intall everything again
Click to expand...
Click to collapse
cannto do it :/
slytidar said:
thanks for the replay
i flashed a custom recovery. this happened later on. but now that the download mode is rebooting it slef and recovery isnt coming, i dont think i can flash a recovery..
Click to expand...
Click to collapse
Hm, if I understand you correctly, you can boot into download mode but it just lasts a couple of seconds before it reboots on its own, right? You cannot boot into recovery as the screen simply stays black. Can you boot successfully into /system or does it bootloop as well?
Sounds like a hardbrick to me, the only thing I can think of before sending your phone in for repair is to pull out the battery for 1 hour or so, reinsert it and boot directly into download mode and see if it stays there. If it does, flash a custom recovery using Odin and check whether you can boot into it afterwards.
Chalao said:
Hm, if I understand you correctly, you can boot into download mode but it just lasts a couple of seconds before it reboots on its own, right? You cannot boot into recovery as the screen simply stays black. Can you boot successfully into /system or does it bootloop as well?
Sounds like a hardbrick to me, the only thing I can think of before sending your phone in for repair is to pull out the battery for 1 hour or so, reinsert it and boot directly into download mode and see if it stays there. If it does, flash a custom recovery using Odin and check whether you can boot into it afterwards.
Click to expand...
Click to collapse
well i cannot boot into download mode long enough to flash a recovery and i cant boot into system either .. maybe a hardware problem ?
slytidar said:
well i cannot boot into download mode long enough to flash a recovery and i cant boot into system either .. maybe a hardware problem ?
Click to expand...
Click to collapse
Looks like it, did you try pulling out the battery for 1 hour and follow the steps as suggested above?
Chalao said:
Looks like it, did you try pulling out the battery for 1 hour and follow the steps as suggested above?
Click to expand...
Click to collapse
now trying
I'm having the same problem here
dead phone, can't boot into recovery, automatically restarts seconds after going into download mode, it doesn't even charge, battery logo comes out aaaand restart, and it keep going
any help?
Im also having the same problem as of this last night.
cannot boot into recovery.
boots to download mode first screen but when I attempt to press volume up to accept, it reboots.
as soon as i put the battery in it cycles through the samsung logo.
tried removing memory card but didnt help.
tried keeping battery out overnight, nothing.
last thing i changed was flashing --> http://forum.xda-developers.com/showthread.php?t=2201860. did this about 2 days ago.
not sure if that has anything to do with it?
Ares1000101 said:
Im also having the same problem as of this last night.
cannot boot into recovery.
boots to download mode first screen but when I attempt to press volume up to accept, it reboots.
as soon as i put the battery in it cycles through the samsung logo.
tried removing memory card but didnt help.
tried keeping battery out overnight, nothing.
last thing i changed was flashing --> http://forum.xda-developers.com/showthread.php?t=2201860. did this about 2 days ago.
not sure if that has anything to do with it?
Click to expand...
Click to collapse
I think it has nothing to do with it
I'm, I was actually, on stock everything, rom, kernel and recovery
30 68336826
OK so I left my phone without a battery in it for the afternoon, just got back home and gave it a try.
It booted. No idea why or what actually went wrong.
Lets hope it doesn't happen again!
OK, So the point that the phone just start booting just the moment the battery is inserted got me thinking
IS IT THE POWER SWITCH?
and indeed it's, the power switch is stuck on, although I can feel the click when I push, still, seems like something is wrong with it
so I tried to suck it out, hit the phone softly few times while the power switch is facing the ground
inserted the battery, aaaand, it didn't start booting, pressed the power softly, and horaaaaay, it's working
Had the same issue and indeed I knocked the power button several times and it worked very well. Thank you! You saved my day
black heart said:
I'm having the same problem here
dead phone, can't boot into recovery, automatically restarts seconds after going into download mode, it doesn't even charge, battery logo comes out aaaand restart, and it keep going
any help?
Click to expand...
Click to collapse
same problem please help!
vaibhav2296 said:
same problem please help!
Click to expand...
Click to collapse
I have similar problem... and identified its power button.
How i identified is as phone switched on i hold menu button and volume down button together and
it booted in download mode, for download mode you have to keep pressing power button, volume
down button and menu button but it went without pressing power button.. so i assume that its power
button.
Try it... hope will identify your problem
same Problem
Hello!
I have the same problem, and disassemble the cell and saw that the button will operate properly .
Someone has managed to get out of this problem?
thanks a lot... i was facing same problem... i hit ma phn near power switch...again n again... it worked... love u xda
whoa, I just got this problem recently, because some of bezel around my phone has cracked, then I try to glue it roughly.
at the other hand, I tried to install new kernel. I tought that kernel make my phone bricked. then I found this thread. so I open my case. and found my glue sticked to the power button, remove it and. voilaaaa~
thank you XDA. you never cease to amaze me. lol
My Nexus 10 has been acting up recently...the battery seemed to be draining A LOT quicker then it normally would.....the tablet would just shutdown in the middle of doing something. Fast forward a week or two, now when I turn it on it vibrates for a second, shows the "GOOGLE" logo and starts the boot animation for 4.4, vibrates and repeats the same. I manually formatted and flashed 4.4 (fastboot flash boot ...etc...) and still am getting the same issues...Any suggestions on what to try next?
Flash the newest factory image automatically via fastboot.
Sent from my Galaxy Nexus using XDA Free mobile app
Just did that to no avail....same issue as before...Anything else to try?
It almost seems like it is not charging but I would assume I could still get it to boot up while connected to the charger....correct?
Update....I flashed CWM and sideloaded gapps and a ROM...and tried that...still the result..."GOOGLE" logo comes up and then a vibration...then it goes back to "charging" (the white battery with the lightning bolt through it)
Nobody has anything? Damn...lol
cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
Sounds like it may be a hardware issue, since flashing the factory image didn't even help. I would say trying flashing the factory image using the flash-all method, and wiping data/factory reset right after. Couldn't hurt.
cirenj said:
Nobody has anything? Damn...lol
Click to expand...
Click to collapse
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude
texascwby1836 said:
You said you installed cwm -- I assume you mean the recovery rom... If I'm wrong ignore the rest.
I too have had this issue and it was not hardware. To fix this I booted into cwm (the recovery rom I use on my N10) and reinstalled a stock factory boot rom. Just for those that don't know to boot into the recovery rom, power off the tablet, then press and hold the power, volume up AND volume down simultaneously --- finally, use the volume button to scroll to the recovery menu.
uDude
Click to expand...
Click to collapse
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....
cirenj said:
I have tried that as well...I am thinking it is a hardware issue as previously stated....amazing...spend $500 for a piece of hardware only to have it die a little over 12 months later....talk about pissed off....
Click to expand...
Click to collapse
No shoot me a PM ..
Lets see if we can get you up and running again ..
If we do we can post what we did back here from all XDA users ..
Thx Josh
I am having the same exact issues. I too force flashed stock 4.4.4 and it still does not boot up. Any ideas on how to remedy this would be greatly appreciated.
Thank you!
Hoping to hear something as well...but doesn't look good...
Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk
I can access adb on my laptop...and I used the "fastboot format" and "fastboot flash"
How would I check the logcat file?
http://forum.xda-developers.com/showthread.php?t=2274119
beekay201 said:
Can you access adb? To check logcat while it's booting (and possibly find out why it's bootlooping)?
What did you use to format the partitions?
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
I am unable to get my Nexus to show up in command prompt when I run "adb devices". Not sure what to do.
Any ideas? I've tried reflashing stock images and still have the same problems..
michaelearth said:
Any ideas? I've tried reflashing stock images and still have the same problems..
Click to expand...
Click to collapse
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112
demkantor said:
Can you give more details about your issue? If its still about not connecting PC and tablet see this guide for help
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
The problem is that my tablet will reboot constantly and it shows my battery being fully drained even after charging it overnight. I'm able to force flash stock images to my tablet and this has not fixed the issue. So at the moment my nexus 10 is an expensive paperweight.
What happens when booted to bootloader or recovery? Does it act normal or loop?
demkantor said:
What happens when booted to bootloader or recovery? Does it act normal or loop?
Click to expand...
Click to collapse
When I boot into the bootloader it acts normal.
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
redbay1 said:
Hey all, completely new to this forum and my Oneplus Two that I've had for a little over two weeks.
I recently got a OTA update for Oxygen 2.2.0 but I can't seem to install it. Everytime I download it and click the "install" option, the phone reboots (probably to go to recovery) but after a very brief splash screen and a vibration, it vibrates again and displays the standard boot splash screen, boots into the OS and offers me to download the update again.
I've done a little troubleshooting in the past two-three days and from what I understand, the phone doesn't seem to be able to boot into recovery or fastboot. I've enabled the advanced options in the "reboot" menu and when selecting "recovery" the phone reboots and does the same behavior described above. I tried powering off the phone and booting with the volume up button pressed (while pressing power) and the phone boots and displays a "Fastboot Mode" splash screen but it seems to hang there forever until I actually shut it off again and power it back on. Also, I've tried booting it into recovery from ADB, connected to my PC and I get the same behavior: brief splash screen with a vibrate and then the phone seems to reboot again normally.
I haven't tampered with the phone yet, it is brand new out of the box, not rooted and nothing other than simply installing a few games, Nova Launcher, changing the wallpaper and using it as you would normally use your phone.
Anyone has an idea how I could actually get the Recovery functioning on this phone?
Best regards and thanks in advance for any help!
Click to expand...
Click to collapse
That is the norm for fastboot, it doesn't go past that screen.
It may not make a difference, did you try to boot to recovery via Power+Volume Down buttons?
Greetings Khaos64,
Yes, I've tried booting with Vol-Down+Power but the phone does not start.
With volume-up+power, I get the Fastboot splash screen but the phone does not respond to any input.
I tried selecting "bootloader" from the reboot menu but I get the same thing: Reboots and after a second, the phone reboots again normaly and into OxygenOS.
Is there a way to verify if the bootloader or recovery is corrupt and maybe reflash the stock recovery onto the phone?
Thanks for your input!
You may just want to go straight to oneplus support since everything is stock and only 2 weeks they should be able to get you updated or replace it.
If you'd like to be more hands on... maybe something below can help.
So your phone isn't recognized/no commands acceptred from your computer when booted to fastboot?
Such as unlocking your bootloader and booting into twrp... "fastboot boot yourfilename.img" or maybe flashing it.
Make sure OEM unlocking is selected in Developer options.
If you can't do that then this may not work but is worth a shot.
http://forum.xda-developers.com/showpost.php?p=62973446&postcount=2
These may also be something to look into:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
I did try to contact Oneplus for support but I am not the one who purchased the phone. Long story short, it was a gift from my girlfriend that she bought off of someone. The phone was new in box and was a warranty replacement. I would have to contact the seller and go trough him for support unfortunately.
Thanks for the different suggestions!, I will fiddle around with it this afternoon while the kids are having their mid-day nap and I'll get back with the results
Thanks again for the help, it's greatly appreciated!
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Congratulations hope you enjoy the phone
Sent from my ONE A2005 using Tapatalk
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
Glad one was able to help you do it. :good:
redbay1 said:
Hello,
I eventually started fiddling around with fasboot and tried unlocking the bootloader. This sent the phone into a bootloop where it would try to boot into recovery and reboot right away.
I found an article on how to restore the phone to Oxygen 2.1.1. It would wipe user data but I did it anyway and it actually did restore the phone and now I have a worling recovery.
Here is a link to the guide I used:
http://forum.xda-developers.com/oneplus-2/general/guide-unbrick-recover-oneplus-2-to-t3269543
Thanks again for the help in solving my issue
Click to expand...
Click to collapse
HI there,
I am having the exact same issue with my oneplus 2. Unfortunately i know almost nothing regarding these android thingy. I know it has been almost 2 years, would you mind guide me through the steps? I would appreciate it so much.
Thanks.