Dear Xda members, I need help with my OnePlus 2... Just got it few days ago. Great phone ! and as an android user, generally the first thing I'd do with my phone was to root it...
basically here's what I've done...
1. unlocked bootloader
2. flash TWRP
3. clean flash OOS 3.0 Beta from TWRP
4. flash CM 13 by Grarak from TWRP
5. flash Gapps Arm64-6.0-micro from TWRP
6. flash SU from TWRP
things were going fine, everything works normally, until I go into bootloader mode.
Suddenly my device goes into a boot loop...
I realised maybe there were something wrong with my recovery (TWRP).
so I tried to flash it again, but it says that my device were locked, therfore I can't flash img file from my PC...
I tried to type unlock Oem, but when I check oem device info, it says device tampered : true, unlock device : false.
I searched for a while and find a temporary solution, by typing "fastboot continue" from command prompt in PC,
I was able to skip the boot loop straight to the boot-animation and was able to enter Cyanogen.
but if I turn off and on my phone, again it enters boot loop...
so basically here's my phone condition...
1. stuck at boot loop
2. no recovery
3. locked bootloader
4. Cyanogen & Su working fine
Please anyone, help... and Thx...
I've used this guide to good success twice now, good luck let's hope you're up and running in no time.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
WHOA !!! IT WORKED !!! Thx alot BRO !!! You saved my day !!! THX XDA !!!
Related
I Have a big issue and need your help
I was OOS3 and do all the correct steps to get modified TWRP to setup custom rom and succeeded on this they I decide to back agaon to OOS3 as it`s more sable
So I download OOS3 and flash it from my Modified Recovery and works fine
Than I decide to enter the recovery just to clear the cash for agood performance and here .. the issue started ...
when I click reboot to recovery , the mobile stopped @ 1+ LOGO So I remmember that this modified recovery is not working with oos3
so I get the steps for unloacking the boatloader again to flash the recovery compatible with OOS3
and HERE .. I see my device when I type
fastboot devices ,,,
but once I type "fastboot oem unlock" it`s show my ok and device rebooted in the same 1+ LOGO
SO I now Stuck in this logo
Cannot enter the recovery Or even the OOS3 just can enter the fastboat mode
Please I need your help how can I manage this
I think your thread will get moved to the General section. But in the meantime try this it worked for me
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Sent from my ONE A2005 using XDA-Developers mobile app
Use the search button before posting.. There atleast 4 threads with the solution.
Wrong section
the command you're looking for is not the unlock one but this one: fastboot flash recovery "twrp-2.8.x.x-xxx.img" just replace "twrp-2.8.x.x-xxx.img" with the name of the recovery .img you have in the same folder as fastboot.
Ahmed Shawky said:
I Have a big issue and need your help
I was OOS3 and do all the correct steps to get modified TWRP to setup custom rom and succeeded on this they I decide to back agaon to OOS3 as it`s more sable
So I download OOS3 and flash it from my Modified Recovery and works fine
Than I decide to enter the recovery just to clear the cash for agood performance and here .. the issue started ...
when I click reboot to recovery , the mobile stopped @ 1+ LOGO So I remmember that this modified recovery is not working with oos3
so I get the steps for unloacking the boatloader again to flash the recovery compatible with OOS3
and HERE .. I see my device when I type
fastboot devices ,,,
but once I type "fastboot oem unlock" it`s show my ok and device rebooted in the same 1+ LOGO
SO I now Stuck in this logo
Cannot enter the recovery Or even the OOS3 just can enter the fastboat mode
Please I need your help how can I manage this
Click to expand...
Click to collapse
First read the Forum Rules on posting, moved here out of the Development Section....
fastfreddy101 said:
the command you're looking for is not the unlock one but this one: fastboot flash recovery "twrp-2.8.x.x-xxx.img" just replace "twrp-2.8.x.x-xxx.img" with the name of the recovery .img you have in the same folder as fastboot.
Click to expand...
Click to collapse
How Can I do this and I even can not unlock the boatloader ?
should still be unlocked - put phone in fastboot mode, check for it via: fastboot devices. If its there then just flash the recovery with: fastboot flash recovery "twrp-2.8.x.x-xxx.img" then reboot into recovery. should work
fastfreddy101 said:
should still be unlocked - put phone in fastboot mode, check for it via: fastboot devices. If its there then just flash the recovery with: fastboot flash recovery "twrp-2.8.x.x-xxx.img" then reboot into recovery. should work
Click to expand...
Click to collapse
I can`t unlock the phone
Thanks for your reply
My situation now that I`m stuck in boot loop and I can`t enter any think , only the fastboat mode and I can not unlock my device
every time I tried to Unlock it , till me Fail to unlock
I follow this steps with no change
http://www.technobuzz.net/unbrick-oneplus-2/
In this video also with no hope
https://www.youtube.com/watch?v=R4SVSovw4Jo
Ahmed Shawky said:
Thanks for your reply
My situation now that I`m stuck in boot loop and I can`t enter any think , only the fastboat mode and I can not unlock my device
every time I tried to Unlock it , till me Fail to unlock
I follow this steps with no change
http://www.technobuzz.net/unbrick-oneplus-2/
In this video also with no hope
https://www.youtube.com/watch?v=R4SVSovw4Jo
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 to get back your old twrp and then follow the instructions from here https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/ carefully (use the tread for users already have twrp)
When did you lock the phone again after unlocking it?
Assuming the phone shows up when running "fastboot devices" try running this "fastboot -i 0x2a70 oem unlock-go" - worked for me
Hello, my OP2 currently works fine on H²OS but my system is telling me that it can be fixed to the latest version (OnePlus2Hydrogen_14.Y.01_007_1606020602 - 1016Mb) but when I try to install it, my phone reboot after 20% of the installation and gets stuck into a bootloop. I also cannot flash another rom as I cannot boot into recovery mode (Fastboot mode works fine).
Is there any way to "unlock" the recovery ? and get back to OxygenOS ?
I have tried the MSM ToolBox to fully reset my phone but it looks like it doesn't work with my device..
Do you guys have any ideas how to solve my problems ?
Ps:I can give you more specific information about my device if you need.
Thank you ! :angel:
HippoOP2 said:
Hello, my OP2 currently works fine on H²OS but my system is telling me that it can be fixed to the latest version (OnePlus2Hydrogen_14.Y.01_007_1606020602 - 1016Mb) but when I try to install it, my phone reboot after 20% of the installation and gets stuck into a bootloop. I also cannot flash another rom as I cannot boot into recovery mode (Fastboot mode works fine).
Is there any way to "unlock" the recovery ? and get back to OxygenOS ?
I have tried the MSM ToolBox to fully reset my phone but it looks like it doesn't work with my device..
Do you guys have any ideas how to solve my problems ?
Ps:I can give you more specific information about my device if you need.
Thank you ! :angel:
Click to expand...
Click to collapse
Unlock command: fastboot oem unlock
Flash recovery through fastboot,
Recover flash command: fastboot flash recovery recovery.img
Reboot in recover, Command: fastboot boot recovery.img
Thank you, it worked perfectly ! :highfive:
Hello guys, my phone one plus 5 has stopped working when I wanted to change to a ROM called (Resurrection Remix) which does not give any problem according to the users of the forum. I have another version of (Resurrection Remix) in my ONE PLUS TWO and without any problem. The topic is the following I have done all the steps as they are indicated but at the time of restarting the phone when the installation is finished, a load loop has started and never ends. I've been searching the internet all day to unbricke the phone but it's impossible, I try to install different ROMs and I still get nothing.
Sorry for my bad English, my language is Spanish
Link video YOUTUBE : https :// w w w. youtube .com/watch?v=0prJgT2erSU Delete the spaces of the link, being a new user does not let me post links
I had this same problem, and can almost promise this will unbrick it. Unfortunately this will put your phone back to how you had it when you first unboxed it, but it will work again.
1. Download the official OOS 4.5.5 zip
2. Wipe cache/dalvik/system/data in TWRP and flash the stock zip.
3. Within TWRP, flash the stock OP recovery image. You do this the same way as a zip, but click images in the bottom right while browsing for the file. Choose recovery as the partition of course.
4. Go to TWRP power options and boot to Bootloader/fastboot
5. Hook up to your PC and run the command to lock your bootloader "fastboot oem lock" (this will wipe your device and encrypt it again. I believe at this point the stock recovery will come up, do another factory reset to be safe.
6. Start your phone, at this point it should load up like new and all you have to do is unlock bootloader again and flash TWRP through fastboot so you can root again.
I don't have an answer for why ResurrectionRemix bricked your phone, but it did for me too. I followed the decrypt instructions to the T, but the same thing happened and I spent an entire Saturday trying to get my phone running again. I would guess that ResurrectionRemix is not to blame, and any other Lineage based ROM would end in the same result.
Good luck.
ArkAngel06 said:
I had this same problem, and can almost promise this will unbrick it. Unfortunately this will put your phone back to how you had it when you first unboxed it, but it will work again.
1. Download the official OOS 4.5.5 zip[/URL]
2. Wipe cache/dalvik/system/data in TWRP and flash the stock zip.
3. Within TWRP, flash the stock OP recovery image.[/URL] You do this the same way as a zip, but click images in the bottom right while browsing for the file. Choose recovery as the partition of course.
4. Go to TWRP power options and boot to Bootloader/fastboot
5. Hook up to your PC and run the command to lock your bootloader "fastboot oem lock" (this will wipe your device and encrypt it again. I believe at this point the stock recovery will come up, do another factory reset to be safe.
6. Start your phone, at this point it should load up like new and all you have to do is unlock bootloader again and flash TWRP through fastboot so you can root again.
I don't have an answer for why ResurrectionRemix bricked your phone, but it did for me too. I followed the decrypt instructions to the T, but the same thing happened and I spent an entire Saturday trying to get my phone running again. I would guess that ResurrectionRemix is not to blame, and any other Lineage based ROM would end in the same result.
Good luck.
Click to expand...
Click to collapse
WOW Many thanks, my friend, finally my phone has revived. Again thank you very much has served me very much.:good:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
[email protected] said:
Hi, hope you can help solve the problem that happened with my Moto E4 "woods". Installing TWRP recovery (TWRP-3.2.1.-0_woods_UNOFFICIAL.img) went smoothly via ADB fastboot flash recovery etc. The phone rebooted however in "Orange State- your device has been unlocked and can't be trusted". Having searched the internet the solution seemed to be to prevent the phone from installing it's own recovery again by getting it to reboot via ADB with the command "fastboot boot ....recovery.img (the name of the TWRP image). It does so succesfully by first downloading "boot.img" and then the same thing happened as before, it boots into the unlocked orange state warning. The phone still has the stock rom on it and will boot into that normally once I've removed the battery and put it back in. But I have no recovery at all now, not the stock recovery either. Pressing volume down and power gets me into adb connection, and volume up into the warning. Any solutions? Anyone else had the same problem? Thanks!
Click to expand...
Click to collapse
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
madbat99 said:
When you're in bootloader, keep pressing volume button until it says recovery. Then tap power. If you already fastboot flashed recovery, no need to fastboot boot recovery recovery.img. just boot to bootloader and tap volume until you see recovery, then tap power.
Click to expand...
Click to collapse
Thanks for your reply and thinking with me, but like I wrote, all there is left is the option to use ADB. Pressing volume up and power no longer gets me into a choice menu, only a black screen with small white letters telling me to attach a cable.
No tapping whatsoever will change that. Volume up gets the orange state message again. So....
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
KevMetal said:
You need to flash the old recovery first ....from one of my threads ..follow full guide by flash no dm-verity ..THEN install new recovery via old twrp recovery ...the "NEW" recovery has errors so be warned :good:that will work
Go look in one of my guides for woods for old files
Click to expand...
Click to collapse
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
[email protected] said:
Thank you for taking the time to help out! Today I somehow got lucky after I reflashed it again, after having spent the morning deciphering the Chinese recovery which occasionally appeared. Rebooting into recovery inside TWRP held it stable. I manage to flash one custom rom, Dot Os, the Lineage OS for Moto E4 Woods got a TWRP message the zip wasn't correct (though I trust it was) and my backup made by TWRP did not restore. Is this what you mean by the errors? Very lucky to have a working Dot Os, and maybe I'll wait until an official TWRP is available now. Since I lost it again by forgetting to flash SuperSu again at the install of the custom rom....
Will look through your posts to find the guide with the files to have them at the ready Happy New Year's Eve!
Click to expand...
Click to collapse
Don't forget to join us on telegram
We have a lot going on and if we chat via one central chat development , bug fixing and general help happens fast .
https://t.me/joinchat/G3XDFEO7AR4fGdyBRfwVOw
http://telegra.ph/woods-development-01-07
twrp for 1762 ?
I can't seem to find TWRP-3.2.1.-0_woods_UNOFFICIAL.img annywhere on the internet
I found this but i don't realy trust that site.
https://romprovider.com/2017/12/twrp-3-2-0-moto-e4-xt1762-woods/
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
A little progress, I was unable to unlock_critical but its still hanging here
https://imgur.com/a/IdZum
jAm-0 said:
I think I messed up my PH-1 something royally.
All I was trying to do is unlock my bootloader and load Magisk.
To preface this, my PH-1 seemed to act a little wonky from the get-go. I bought it 3rd person from a guy on craigslist so anything warranty involved I think I'm out of luck.
The phone would take a while to power on, it took something like 10secs on the power button just to turn it on. And if I set it to reboot , it boots into the bootloader. Also, I was never able to access the recovery (even using power + up). It always felt like I had to hold the buttons for way to long to get to its destination; e.g. up and power to get into fastboot.
Ok where I'm at now. In can occasionally get into fastboot mostly after it bootlooping a few times. It won't get past the Essential logo if I try to boot it up.
PS I was able to unlock the bootloader.
Steps I took to remedy this:
> erase all user data in fastboot
> hold power + u + d to hard power off
> follow this guide https://forum.xda-developers.com/essential-phone/how-to/guide-rooting-essential-ph-1-magisk-t3701976
> attempt to install stock system image via flash-all
>a ton other
Here are the results of that.
https://imgur.com/a/iVwwS
Help me guys please. :crying:
Click to expand...
Click to collapse
read through this and follow the steps should be good to go.
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
This is also very helpful
https://mata.readthedocs.io/en/latest/
That's the exact process I was going through, and it finally booted up.
The issue I was having was a bad usb connection which wouldn't allow me to unlock_critical.
SOLVED. Still no Magisk, we'll worry about that another time. 5hrs of troubleshooting is enough for one night.
https://imgur.com/a/ZiBzp
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
jAm-0 said:
SO close to getting Magisk to install, any reason the refuses to flash the boot partition? I used the stock boot.img and had Magisk patch it before I flashed
Click to expand...
Click to collapse
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
wolfu11 said:
You have to flash magisk in twrp recovery NOT bootloader mode.
It's right in the OP from the rooting guide you followed:
Do not set up a password if you are on 8.1 twrp doesn't work.
You need to read through that rooting guide and make sure you know what you're doing before you try.
This phone is easy to hard brick and there is no solution to recover from that.
OREO 8.0/8.1
REQUIREMENTS:
An unlocked bootloader.
A working ADB/Fastboot environment on your computer. Knowledge on how ADB and Fastboot works is also preferred.
The stock boot image for whatever build you're running/trying to root.
The latest TWRP build for our device.
If on 8.1, remove your pin/pattern/passcode until the root process is done.
1. Download both the stock boot image for whatever build you're running and the Magisk or SuperSU zip. Transfer both files to your device's internal storage.
2. Reboot your phone into the bootloader, then open up your command prompt or terminal and flash the latest TWRP build for the device using:
Code:
fastboot flash boot twrp.img
3. Once TWRP has finished flashing, reboot into your recovery. When prompted, enter your pattern/passcode/password to decrypt your data in order to gain access to your internal storage.
4. Once you're in TWRP, install the stock boot image and then the Magisk/SuperSU zip.
5. Whenever Magisk/SuperSU finishes installing, simply reboot your device! You should now be rooted.
*NOTE: TWRP will NOT remain installed on your device.
Click to expand...
Click to collapse
I realize all that, the issue is I cannot access any sort of recovery because I think my bootloader is defective.
For example from a cold restart if I press the power button for say 3 -5 seconds it wont boot, just boot to the Essential logo and loop. To get the phone to boot I have to hold the power down for 15-20 seconds while it bootloops a couple times then it'll boot.
Is there a possible way to reflash the bootloader software if it is defective? It's unlocked btw
There is a way to install magisk via fastboot with a patched_boot img which I'm working on. Cant seem to find the right boot img to patch for 8.1
PS Is it possible to flash .zips through fastboot? e.g. custom roms etc
Was finally able to get into recovery, so all is well. Thanks for the help yall
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
gimpy1 said:
OP, what was your process to successfully get into recovery and fix your problems?
It may help others sometime?
Click to expand...
Click to collapse
It's really hard to say, my phone has a serious problem with it. sometimes I cant get it to boot, it will boot into the bootloader over and over and over. I've managed to get Lineage 15.1 on if for a bit until I tried to get back into the recovery which sent it manic.
I just got lucky I was able to get into TWRP and flash lineage.
my first issue not being able to flash the stock image via fastboot because I didn't unlock_critical which can sometimes fail when the usb connection is bad.
Currently flashing stock again if my phone will boot up. I'm not sure whats wrong with my bootloader but its causing a ton of havoc
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
Same boat for me - just keep rebooting to show Powered by Android Screen and then reboot again and again. Was able to see my device using fastboot devices command but all attempts to access recory just repeat the bootloop entry. I would happily check the OEM UNLOCK option in dev settings but can't even get it to book to any OS to make that option happen. Still shows bootloader locked on bootloader screen - any help someone can suggest?
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.
katastyle971 said:
My essential phone stuck in boot logo,bootloader work but recovery doesn´t work
Bootloader locked.
Oem unlocking disable.
Usb debugging disable.
How to flash stock recovery or twrp on bootloader locked ? please
Thank you!
Click to expand...
Click to collapse
I am in the same boat. I tried to re-install the OS, but because my USB debugging was not enabled, Fastboot worked but ADB would not and since I basically wiped the recovery area, my phone will only boot into Fastboot but will not allow any loading of recovery. I would pay for someone to help. This is so hard to figure out. I have contacted Essential but since my phone is over 12 months old, the warranty has expired.
Help please. It seems like such a waste to have a bricked phone.