Long story short, My one plus one has been sitting in storage for over a year now. My current phone needs to be RMAed for irrelevant reasons, so I decided to pull my OPO out of storage. When I went to boot the device, I described I could only boot to TWRP. I managed to upgrade to twrp 3.1. I upgraded hoping that it would fix my boot issues. It did not. I tried flashing a copy of CM 11 I had on the device, nothing. I flashed a copy of lineage OS, and it still wont boot to anything but TWRP. It wont boot into the bootloader either. Any thoughts on what my be happening or how to fix this?
Edit: it does show up in ADB, and i'm almost positive its rooted... its been a while, so i'm not 100% sure.
flash stock images (?)
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
i hope it help
Azhar_Fahry said:
flash stock images (?)
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
i hope it help
Click to expand...
Click to collapse
However, heres the issue. I can't access the bootloader. It refuses to boot into it. It just goes back to boot into TWRP. Thoughts?
flamespinner said:
However, heres the issue. I can't access the bootloader. It refuses to boot into it. It just goes back to boot into TWRP. Thoughts?
Click to expand...
Click to collapse
It's common issue now-a-days on OPO,probably because it's getting old now,see my reply on this thread,
https://forum.xda-developers.com/oneplus-one/help/oneplus-one-stuck-recovery-t3594030
It worked for the OP of that thread so it should work for you too,lemme know if it works for you.
flamespinner said:
However, heres the issue. I can't access the bootloader. It refuses to boot into it. It just goes back to boot into TWRP. Thoughts?
Click to expand...
Click to collapse
i think there's an option to boot into bootloader from twrp
Related
Hey guys,
I screwed something up flashing the latest twrp and now my internal partition only shows as 993 mb and I can't get past twrp. I tried moving a new twrp onto the sd card and flashing it using the 0P6BIMG.zip method and it flashed fine but same issue. If I try to restore my backup it gets like 1% in and fails.
Is there a way to just RUU everything back to normal? Sorry this is the first time I've done this to my M8.
Thanks!
teddykgb715 said:
Hey guys,
I screwed something up flashing the latest twrp and now my internal partition only shows as 993 mb and I can't get past twrp. I tried moving a new twrp onto the sd card and flashing it using the 0P6BIMG.zip method and it flashed fine but same issue. If I try to restore my backup it gets like 1% in and fails.
Is there a way to just RUU everything back to normal? Sorry this is the first time I've done this to my M8.
Thanks!
Click to expand...
Click to collapse
Hold POWER + VOLUME UP AND!! DOWN (should take around 10 seconds.. and in TWRP you will see the screen turn off so as soon as that happens follow what I say next)
hold until the screen turns off, as soon as that happens let go of everything BUT VOLUME DOWN -- see if this gets you into Fastboot...
teddykgb715 said:
Hey guys,
I screwed something up flashing the latest twrp and now my internal partition only shows as 993 mb and I can't get past twrp. I tried moving a new twrp onto the sd card and flashing it using the 0P6BIMG.zip method and it flashed fine but same issue. If I try to restore my backup it gets like 1% in and fails.
Is there a way to just RUU everything back to normal? Sorry this is the first time I've done this to my M8.
Thanks!
Click to expand...
Click to collapse
What happen is you flashed twrp to your system partition. What u need to do is boot to bootloader an enter the real recovery thru boot loader. Then you should be able to restore or flash a ROM. Make sure you go to bootloader then recovery so you r in the correct one. Try that an let me know.
Tigerstown said:
What happen is you flashed twrp to your system partition. What u need to do is boot to bootloader an enter the real recovery thru boot loader. Then you should be able to restore or flash a ROM. Make sure you go to bootloader then recovery so you r in the correct one. Try that an let me know.
Click to expand...
Click to collapse
Not there yet. Restore said successful but it still booted to twrp. Flashed a different rom and it booted up but then froze and now I'm doing that over again. The restores complete successfully but won't boot. My backup may be bad though so I'll flash again and report back.
teddykgb715 said:
Not there yet. Restore said successful but it still booted to twrp. Flashed a different rom and it booted up but then froze and now I'm doing that over again. The restores complete successfully but won't boot. My backup may be bad though so I'll flash again and report back.
Click to expand...
Click to collapse
And I'm back! Thank you!
teddykgb715 said:
And I'm back! Thank you!
Click to expand...
Click to collapse
No problem. Glad to help.
Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?
fastboot reboot-bootloader ; just after recovery flash.
Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon
i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.
TobiS137 said:
i cant really explain what i was doing but i was trying to root the phone and after rooting it i tried to fix an issue with twrp crashing. it ended up with me stuck in a bootloop that i cant get out of. i have basicly no experience in the stuff so i am in desperate need of help. you can reply to the forum or msg me on an a platform like discord (TobiS137#2131) preferably discord tho. thanks in advance! i really want it fixed asap so if you can help then please be quick. please reply under the thread if you have msg me on discord. i really need help.
Click to expand...
Click to collapse
Enter fastboot, flash official twrp.Flash magisk in twrp.
vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
can you help me further? as i said i am a huge newbie and i only understood a little of that. is there any other ways you can contact me?
vrda08 said:
Enter fastboot, flash official twrp.Flash magisk in twrp.
Click to expand...
Click to collapse
Can you explain what exactly were you doing ?!
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
I'm new to this while A/B partition. I went through all the steps and my phone is rooted, with Magisk and TWRP. All seems to be fine. My question is this. When I boot to the recovery (TWRP) and choose the reboot option it defaults to Current Slot: Partition B. If I reboot to partition B it goes back to TWRP. I have to select Partition A to get the device to boot to the system.
Is this normal? Do I need to set it up in a different way?
samteeee said:
Can you explain what exactly were you doing ?!
Click to expand...
Click to collapse
i was trying to root the phone (wich i did) and then the twrp app that was on my phone after i had tried to install it using the img. it then turned into an ap that told me to update it in google play
after that was done i tried to flash it but everytime i tried it just crashed. a little time later after trying some more times i found that i started it in the bootloader and it ended up with me stuck in a bootloop. again i might not have explained enough. i am huge noob so i really need help.
ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\ . Does it change anything that i use twrp enchilada or does that not matter?
ooshkamils said:
Just hold the power button for 60 seconds or so, it should reboot normally. Did you flash twrp or just do fastboot boot twrp?
Click to expand...
Click to collapse
i think i did fastboot boot twrp. still not sure tho :\
discord
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.
TobiS137 said:
i think i did fastboot boot twrp. still not sure tho :\
Click to expand...
Click to collapse
To keep TWRP as the phones recovery, you'd first need to do as you did "Fastboot boot twrp" but that command will only allow you to boot into TWRP through your pc or whatever you ran that command on. After you've entered that temporary recovery, you'll need the TWRP installer .zip file, and flash that inside of that temporary TWRP. Then you can reboot into recovery on your phone again since it has been installed to one of the partitions.
TobiS137 said:
ignore the "discord" title. i dont think the phone has an OS right now. when i turn it on it goes directly to twrp. if i reboot the system it just goes back to twrp recovery. i think i need a way to install an OS (preferably OxygenOS if that is even possible). i realised that you guys properbly won't msg on discord. you dont have to. you can use the forums . i just really want help to get my phone back up and running. it is a OnePlus 6 btw if that is important.
Click to expand...
Click to collapse
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about
phone open again
my phone is back up and running again. i changed the partitian slot from A( the broken one with no OS) to B(the unchanged one) and it is now working again. if anyone is having the same problem the try to change to the second slot. it happend in twrp enchilada 3.2.2-0 if it is important. thank you all for your support.
I may be mistaken but I believe all you need to do is flash magisk to get up and running again
hallo dare said:
You have to flash magisk after flashing twrp or else you are going to get this bootloop you are talking about
Click to expand...
Click to collapse
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.
RusherDude said:
Why? You should be able to just flash the TWRP installer into TWRP and so its flashed into both boot_a and boot_b. It should boot ok to system from there, Magisk is just another mod to the boot partitions, like a custom kernel, etc. It should not be necessary at all, why you guys keep sayin Magisk is necessary for anything? it isn't.
Click to expand...
Click to collapse
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.
iElvis said:
Because you do. The OP6 will not boot with custom recovery unless it's rooted. I believe this is because the recovery and boot partitions are merged on this device. You're welcome to bootloop all day if you don't believe us.
Click to expand...
Click to collapse
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...
RusherDude said:
Asking "why?" is not to not believe you, and the personal bootloop all day attack is out of the matter. TWRP is flashed on the ramdisk and should boot stock, unless something derped, if it doesn't boot I honeslty don't understand why, what is the exact reason? TWRP installer doesn't overwrite the boot, just patches it to have a mini recovery on it. It should boot...
Click to expand...
Click to collapse
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.
iElvis said:
I don't know for sure either, beyond what I said above. But everyone who has reported not flashing magisk has bootlooped.
If I sounded snippy, it was only because your post above was appearing to deny the reality of what is a very well-known issue with this phone.
Click to expand...
Click to collapse
I am not denying anything! just surprised because on TWRP website they clearly state that no post-twrp-flashing step is needed:
https://twrp.me/oneplus/oneplus6.html
The OnePlus 6 uses the newer AB partition scheme first introduced on the Pixel 1. As such there is no recovery partition. Instead, the recovery is part of the boot image. You will temporarily boot TWRP to perform and later perform a more permanent TWRP installation. First download the TWRP zip file directly on your device. If you don't download the zip file to your device first for any reason, you will need to adb push the zip to the device because MTP is not currently working on the OnePlus 6 in TWRP. If you are unable to use adb, you can also use a USB stick with an OTG cable, if you have those handy. Power off the device. Hold volume up to get into fastboot mode. Run this command on your computer: fastboot boot twrp-3.2.1-0-enchilada.img
In TWRP, tap on Install and browse to the zip and install it (the zip will probably be in /sdcard/Downloads). TWRP will now be installed to both slots. TWRP is now installed and you can reboot and use your device as normal.
MTP is disabled because it causes a kernel panic sometimes with the stock kernel.
Click to expand...
Click to collapse
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?
RusherDude said:
Maybe the issue here is that the unofficial TWRP that everyone used NEEDS magisk while the official doesn't?
Click to expand...
Click to collapse
I think most people have moved to the official version. If it doesn't need magisk to avoid a bootloop, that's news to me. Not saying it's not the case, but I haven't seen any mention of it.
Hi.
So this was pretty stupid of me. I was trying to flash LiquidRemix onto my OP6, but I forgot to wipe the system partition. Flashed the rom, then blu_spark twrp, and rebooted into recovery to flash gapps and all. Got a black screen with a static LED. Didn't think that was a big issue cause this has happened before with normal TWRP on OB6 or OB7. Tried hard resetting to see if I could get into system, same result. Tried fastboot flashing 9.0.2, no help. And finally tried flashing OB9 via fastboot, and also no help.
I've reverted back to my tiny S6 and have sent repair request to OP. I haven't gotten anything back yet, so I thought in the mean time, I'd look for help on XDA and try to fix it before having the chance to send it in.
Any help/advice would be greatly appreciated.
Cheers
// EDIT
Figured out how to fix it. Used the MSMDownloadTool to unbrick my device. Worked wonders. Thanks to r/oneplus Discord
I did something like that I had to format data after I flashed the stock rom
mightyblazer said:
I did something like that I had to format data after I flashed the stock rom
Click to expand...
Click to collapse
How did you get to format? I really can't get into the OS or recovery at all
I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again
mightyblazer said:
I was actually able to boot into TWRP maybe you can get into fastboot? And try flashing TWRP again
Click to expand...
Click to collapse
I'm able to get into fastboot, but even if I fastboot boot [insert twrp file name here], it'd still result in the blank screen and static LED
Hmm I don't know then sorry
Try
fastboot flash boot twrp.zip
Then
fastboot reboot
You will need to use full stock rom first before doing anything else though.
I was in the same boat as you the other day. I flashed different versions of twrp until i managed to boot one because some twrp isn't compatible with pie.
Lol I never wipe system...
Might sound like a "hard-bricking" issue since you cant boot into the OS nor recovery. There 's a hard brick recovery guide, but it'll put you down to oreo OOS: https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
As long as you can boot into fastboot, you can follow the guide's process with no problem.
Need advise if I still revive this somehow?
can I interact with the phone only on bootloader screen and flash factory image?
I am open for other suggestion as well that will revive and improve the device
this device has mic issue and sometimes the speaker is not working.
but instead of salvage part I am hoping , it can revive just for youtube and email device
(I was using it as such until it stuck on google logo one day)
thank you
Sorry bub your motherboard is shot and your pixel is a paper weight just like mine. I thought I got lucky and my OG Pixel would be a lucky one that would escape the faulty pixel motherboard plague. She died a few weeks ago just like yours. Even bought a big stack of 10 Tech21 cases for it since they were cheap last year. Welp we didn't win the silicone lottery
This is a known issue with Pixels. What really sucks is I changed the battery on it a few months before the settlement. Didnt find out about the settlement till a month after it closed as well. Worked out in Google's favor with the window being only open for an extremely short period of time.
no hack tool to make it any use ?. I still can get too bootloader
but it is locked bootloader
If i had know I unlock bootloader at least I can try to re image or try different recovery
but if like you said the motherboard then it is paperweight
maybe i can sell the screen
valent|n0 said:
no hack tool to make it any use ?. I still can get too bootloader
but it is locked bootloader
If i had know I unlock bootloader at least I can try to re image or try different recovery
but if like you said the motherboard then it is paperweight
maybe i can sell the screen
Click to expand...
Click to collapse
and battery and camera and even sd card slot
you may like flashing in EMERGENCY DOWNLOAD MODE before dissecting it
Mine is unlocked and can boot to bootloader no problem as well. Can flash it maybe 70% of the time no problem. Other times it just freezes when it starts to flash . Have fun with that screen if you do decide to part her out, not too fun to remove I hear.
jjgvv said:
you may like flashing in EMERGENCY DOWNLOAD MODE before dissecting it
Click to expand...
Click to collapse
Sorry what do you mean about the emergency download mode?
Octopus756 said:
Sorry what do you mean about the emergency download mode?
Click to expand...
Click to collapse
Just search 'Google Pixel EDL' and cannot help you anything more.
jjgvv said:
Just search 'Google Pixel EDL' and cannot help you anything more.
Click to expand...
Click to collapse
But it doesn't seem to work on a Google pixel 1
I'm having a bootloop issue as well. Everytime I flash factory images phone bootloops
Rootmaster906 said:
I'm having a bootloop issue as well. Everytime I flash factory images phone bootloops
Click to expand...
Click to collapse
Hello flash custom firmware
Octopus756 said:
Hello flash custom firmware
Click to expand...
Click to collapse
I have tried. I had tried flashing all kinds of firmware. I've even flash custom recovery and upon installing a ROM it randomly reboots. Something is wrong with the recovery partition
Rootmaster906 said:
I have tried. I had tried flashing all kinds of firmware. I've even flash custom recovery and upon installing a ROM it randomly reboots. Something is wrong with the recovery partition
Click to expand...
Click to collapse
Go to another slot
Octopus756 said:
Go to another slot
Click to expand...
Click to collapse
I have. I have set actives on both slots, flashed them both. Still bootloops.
I have fast boot format data ,fastboot format system fastboot format vendor and then flashed the stock firmware. Boom, still boot loops
for some odd reason the slots do not want to work well with the recoveries that I am working. Even stock recovery does the same thing
Rootmaster906 said:
for some odd reason the slots do not want to work well with the recoveries that I am working. Even stock recovery does the same thing
Click to expand...
Click to collapse
What do you mean Tell us more about how they work?
Octopus756 said:
What do you mean Tell us more about how they work?
Click to expand...
Click to collapse
what i am saying is, no matter what i flash, stock factory images, otas...i keep getting bootloops. even when i fastboot boot twrp, it will not bootloop, but no sooner i try to flash a rom ( that is if twrp doesnt freeze, then do the bootloop issue), it will try to boot and then bootloop. at one time i was able to adb sideload lineage 17.1 and it worked fine for a day, then bam..random reboot then into a bootloop
Rootmaster906 said:
what i am saying is, no matter what i flash, stock factory images, otas...i keep getting bootloops. even when i fastboot boot twrp, it will not bootloop, but no sooner i try to flash a rom ( that is if twrp doesnt freeze, then do the bootloop issue), it will try to boot and then bootloop. at one time i was able to adb sideload lineage 17.1 and it worked fine for a day, then bam..random reboot then into a bootloop
Click to expand...
Click to collapse
Maybe try installing a custom kernel?
Octopus756 said:
Maybe try installing a custom kernel?
Click to expand...
Click to collapse
All is well?
Rootmaster906 said:
what i am saying is, no matter what i flash, stock factory images, otas...i keep getting bootloops. even when i fastboot boot twrp, it will not bootloop, but no sooner i try to flash a rom ( that is if twrp doesnt freeze, then do the bootloop issue), it will try to boot and then bootloop. at one time i was able to adb sideload lineage 17.1 and it worked fine for a day, then bam..random reboot then into a bootloop
Click to expand...
Click to collapse
Her?