Related
Is it possible to have a phone that can't enter recovery mode?
My phone is rooted and I can enter recovery mode through Rom Manager but I can't get there by holding volume+- and power. I'm afraid some day I might mess up my phone and be unable to fix it because I can't enter recovery or download mode.
Am I just doing it wrong, or are there phones that cant?
I'm still within 30 days of my phone purchase, should I exchange it?
Same here. I can't get the phone to boot into recovery to update packages to install root. Any suggestions would be appreicated. I just exchanged my phone for a second time for a media player crashing issue, I called AT&T and they told me to bring it in for exchange. I can't get the new one to boot into recovery.
Mine only seems to work if I plug in a usb cable while holding the buttons though I'm sure I just haven't found the right timing the usb cable seems to help for some reason. And no I'm not getting confused with download mode.
Sent from my SAMSUNG-SGH-I897 using XDA App
Rhiannon224 said:
Same here. I can't get the phone to boot into recovery to update packages to install root. Any suggestions would be appreicated.
Click to expand...
Click to collapse
I was able to root using the one click root method, the one that's stickied in the development forum. It doesn't require you to manually boot into recovery mode.
Rhiannon224 said:
Same here. I can't get the phone to boot into recovery to update packages to install root. Any suggestions would be appreicated. I just exchanged my phone for a second time for a media player crashing issue, I called AT&T and they told me to bring it in for exchange. I can't get the new one to boot into recovery.
Click to expand...
Click to collapse
Hmm I guess I should exchange my phone. What should I say? "I can't get my phone to boot into recovery mode, I need a different one please." lol
jbblue1 said:
I was able to root using the one click root method, the one that's stickied in the development forum. It doesn't require you to manually boot into recovery mode.
Click to expand...
Click to collapse
I downloaded the oneclick however it is a .rare file and I can not extract the data with my pc for some reason. This is not my first time rooting a Captivate either so I have the tools and drivers. I just can't get into recovery mode and I am frustrated because without root I can not access my backup of Titanium or ClockworkMod.
I also am having problems getting into recovery.. Just got my phone today... I've tried about 30 times, and it absolutely will not go into recovery mode.
Works every time for me if i power off. Hold down volume up and down and power. Wait for the att screen to go off and as soon as it comes back on the second time let go of the power button and continue holding both volume button down until you see recovery booting. It works the same with a usb cable plugged in for download mode.
have you tried to get into recovery via adb , i always found that way a lot easier then pressing those buttons, pressing the buttons always hurt my fingers too much anyways.
From terminal in tool in the android sdk directory, you can do adb reboot recovery
smokestack76 said:
Works every time for me if i power off. Hold down volume up and down and power. Wait for the att screen to go off and as soon as it comes back on the second time let go of the power button and continue holding both volume button down until you see recovery booting. It works the same with a usb cable plugged in for download mode.
Click to expand...
Click to collapse
i had the exact same issue of mine not working.. somewhere i had read it was to only hold down the UP arrow, not both up and down. I Just did exactly as you said and it worked perfect.
I am on my 3rd Captivate and it appears that the last two won't go into recovery mode using the button combo at all. My first Captivate did with ease, go figure.
smokestack76 said:
Works every time for me if i power off. Hold down volume up and down and power. Wait for the att screen to go off and as soon as it comes back on the second time let go of the power button and continue holding both volume button down until you see recovery booting. It works the same with a usb cable plugged in for download mode.
Click to expand...
Click to collapse
Thanks I did it as you stated and it worked on the first try. Thanks a lot, you just saved me from agonizing over making changes to my phone in fear of not being able to get to the recovery screen.
If people are still having problem is suggest
1 turn off phone
2 count to 30
3 pull battery
4 putt in battery
5 hold both +,- vol buttons and the power
6 let go of power button when you see the att screen
Note: if that doesn't work than in step 5 hold the - vol and the power only or try to hold the + vol and power only.
Hope that helps even though it was said in the thread b4. Im just trying to make it clear
I've tried vol +&- with power.
vol - with power
vol + with power
I've tried letting off power at the at&t screen. I've tried one click root.
Nothing is working.
Edit: Lol, win 7 needs x64 drivers then I got it done through sdk. Still no hardware recovery boot though.
any chance this would work for our phones? Samsung Galaxy S Vibrant (GT-I9000) Software Upgrades for Handsets with Original Production Software
.by Samsung Mobile Canada on Thursday, September 16, 2010 at 4:14pm.A software upgrade is now available for Bell Mobility Galaxy S Vibrant handsets, provided the device has original production software (JG9). The latest version of Kies has been tested and will resolve the three-button recovery issue
I've read on a forum once(can't remember where) that there are different models of the at&t captivate, some ship without the ability to use the buttons to boot into recovery/download. It also said that if you call at&t and tell them you want a phone that boots into recovery they'll send you one.
I told them that this was one of the principal reasons that I won't be keeping my Captivate. I returned mine today (the second one i have had, and after a Nexus One and EVO as well).
Ok i had the same problem i broke the screen on my captivate went to at&t
did a upgrade went to root it and could not get into recovery after reading all the
post and calling samsung (what a wast of time) i took the back cover off my broken phone looking for numbers what i found was a batch # under the sn#
my old phone had 1007# my new phone had a 1008# went back to at&t we looked
at all the captivates until we found a 1007# poped in a battery and went right in
to recovery i'm thinking mabe the new batch# had something different but it worked for me thought i would share
The ota update fixes this issue.
C3P0LOL said:
The ota update fixes this issue.
Click to expand...
Click to collapse
Which update? The JH7 one? I can't boot into recovery either. I'm running JH7 on an AT&T Captivate unlocked and using it on Rogers in Canada, with "1008" on the back of the phone. Maybe they DID remove recovery mode since the "1007" phones?
EDIT: 3-button combo fixed using C3P0LOL's fix.
As it says on the title, I have just rooted went fine then I just installed ClockworkMod Recovery for the LG Optimus 2X went to go in to recovery powering on and holding the Vol down button and a scrren comes up saying
S/W UPGRADE
PLEASE WAIT WHILE UPGRADING....
then nothing happens tried it a couple of time with no joy, having to remove battery to restart, and also it wiped my phone back to stock all my apps etc gone wifi setting etc but the root/superuser is still there
Any idea people????
That is the baseband upgrade screen. You should HOLD power and volume down button!
If that doesn't work are you sure CWM is installed correctly?
weebeast said:
That is the baseband upgrade screen. You should HOLD power and volume down button!
If that doesn't work are you sure CWM is installed correctly?
Click to expand...
Click to collapse
It comes up in a command prompt and lists the things its doing and after a min it just goes off, there is no confirmation thats it's been done.
Kickasskev said:
As it says on the title, I have just rooted went fine then I just installed ClockworkMod Recovery for the LG Optimus 2X went to go in to recovery powering on and holding the Vol down button and a scrren comes up saying
S/W UPGRADE
PLEASE WAIT WHILE UPGRADING....
then nothing happens tried it a couple of time with no joy, having to remove battery to restart, and also it wiped my phone back to stock all my apps etc gone wifi setting etc but the root/superuser is still there
Any idea people????
Click to expand...
Click to collapse
I had this exact same problem as well. It led me to be very confused for a good half hour lol. Simple answer is we weren't booting into recovery properly.
1. Turn the phone off.
2. Hold the volume down button and do not let go.
3. Hold the power button and do not let go.
4. Wait and wait and wait.
5. Should see a small piece of text saying "Android" come up after about 10 seconds-ish.
6. As soon as you see this text let go of the power and volume down buttons.
7. You should now be in recovery.
Hope this helped
Edit: Also I don't think the .bat file used to install CWM recovery gives any confirmation after it's done.
xAdaM-- said:
I had this exact same problem as well. It led me to be very confused for a good half hour lol. Simple answer is we weren't booting into recovery properly.
1. Turn the phone off.
2. Hold the volume down button and do not let go.
3. Hold the power button and do not let go.
4. Wait and wait and wait.
5. Should see a small piece of text saying "Android" come up after about 10 seconds-ish.
6. As soon as you see this text let go of the power and volume down buttons.
7. You should now be in recovery.
Hope this helped
Edit: Also I don't think the .bat file used to install CWM recovery gives any confirmation after it's done.
Click to expand...
Click to collapse
Yeah well i ran the CWM again a couple of times then tried again and it worked great thanks every 1
I just think im impatient as going into CWM on the desire a little bit quicker
Once again THANKS
Had the same problem at first too.
Desire is not as "slow" as the 2X when booting to recovery.
Got myself a factory reset the first time I tried...
Yup exactly, the O2X seems to take much longer than other phones to boot into recovery. I used to have a HTC Hero and it literally took a press of two buttons and then wait a few seconds. Strange...
Hopefully you all don't sigh or roll your eyes at my questions, I came from iOS 2 weeks ago and the Android learning curve is pretty damn steep!
Many guides I read says to enter recovery mode by turning the phone off, then holding volume down and power buttons until the screen flashes and you should enter right into recovery, especially guides to flash a rom. I installed TWRP last week and the way I enter it is hit restart with phone powered on and as the phone begins to restart hold volume down only, then I enter it.
When I hold power and volume down when the phone is shut off, I get the HTC boot image as the phone is rebooting and then a message saying something along the lines of the phone will reboot and it counts down 3,2,1 then the phone reboots a second time and not into recovery. Plus my wallpaper gets removed. I rebooted but the wallpaper was still removed.
Two questions; Is this some sort of faulty installation of my recovery? Which way should I boot into recovery when about to wipe and flash a rom? Thanks a million!
twrp quicker reboot...
AcerRacer said:
Hopefully you all don't sigh or roll your eyes at my questions, I came from iOS 2 weeks ago and the Android learning curve is pretty damn steep!
Many guides I read says to enter recovery mode by turning the phone off, then holding volume down and power buttons until the screen flashes and you should enter right into recovery, especially guides to flash a rom. I installed TWRP last week and the way I enter it is hit restart with phone powered on and as the phone begins to restart hold volume down only, then I enter it.
When I hold power and volume down when the phone is shut off, I get the HTC boot image as the phone is rebooting and then a message saying something along the lines of the phone will reboot and it counts down 3,2,1 then the phone reboots a second time and not into recovery. Plus my wallpaper gets removed. I rebooted but the wallpaper was still removed.
Two questions; Is this some sort of faulty installation of my recovery? Which way should I boot into recovery when about to wipe and flash a rom? Thanks a million!
Click to expand...
Click to collapse
way i do it is i unlock the screen hold power down to get the power options screen then i select reboot i wait for the screen to go blank then i hold the power and volume down it will load into bootloader then i just hit whatever boot loader has the recovery on it (twrp 2.5... had a problem wouldnt do system boot just take me back to recovery so i had to do to bootloader then restart from there) then you will hit recovery i would do a factory wipe but dont have it delete anything else just do a normal factory wipe and maybe delete cache and your problem should be fixed unless there is an issue with your rom you are using then if it bugs you that much find a different one.
another not when the system reboots i think you can just hit volume down dont have to hold power also but im so aggrivated with my current issue i just hold power also to make sure it goes thew.
AcerRacer said:
Hopefully you all don't sigh or roll your eyes at my questions, I came from iOS 2 weeks ago and the Android learning curve is pretty damn steep!
Many guides I read says to enter recovery mode by turning the phone off, then holding volume down and power buttons until the screen flashes and you should enter right into recovery, especially guides to flash a rom. I installed TWRP last week and the way I enter it is hit restart with phone powered on and as the phone begins to restart hold volume down only, then I enter it.
When I hold power and volume down when the phone is shut off, I get the HTC boot image as the phone is rebooting and then a message saying something along the lines of the phone will reboot and it counts down 3,2,1 then the phone reboots a second time and not into recovery. Plus my wallpaper gets removed. I rebooted but the wallpaper was still removed.
Two questions; Is this some sort of faulty installation of my recovery? Which way should I boot into recovery when about to wipe and flash a rom? Thanks a million!
Click to expand...
Click to collapse
*Update*
Ok so after trying again to enter bootloader from power off holding volume down and power button, the same thing happened where I got the 3 second countdown but I continued to hold the buttons and I correctly entered into bootloader. So my question then stands, when flashing a new rom does it matter which method I use? (Reboot, volume down or Power on, volume down/power)
Thanks
Sent from my HTC One using xda app-developers app
So, my volume up key stoped working from one day to the next. Didn't slam the phone on the floor or anything, it just stoped working. I already tried it on recovery mode, no luck so i'm asuming it's not software related.
Anyone faced this issue at some point? I did the eb40 battery mod a month ago, didn't notice anything unusual since then.
Thanks guys for any help.
Anyone?
I'm worried i might need to enter recovery or bootloader using keys instead of software reboot at some point, and won't be able to since my keys don't work.
I mean you could open the phone and check the connection for the button and the contacts. Does it feel loose? Maybe the button is upside down ( which shouldn't matter but you never know). Get back to us!
Sent from my MB886 using Tapatalk
And if is broken then flash phils advance recovery and you will never need it again. Lol
TecknoFreak said:
And if is broken then flash phils advance recovery and you will never need it again. Lol
Click to expand...
Click to collapse
Wait what? I have the same problem (volume up key is broken) and I'm constantly paranoid about bootloops since fastboot reboot recovery doesn't work. I have Philz recovery as well. Is there some feature I'm not aware of?
Papahyooie said:
Wait what? I have the same problem (volume up key is broken) and I'm constantly paranoid about bootloops since fastboot reboot recovery doesn't work. I have Philz recovery as well. Is there some feature I'm not aware of?
Click to expand...
Click to collapse
The touch recovery does not require the use of volume or power button. Same with Touch CWM.
audit13 said:
The touch recovery does not require the use of volume or power button. Same with Touch CWM.
Click to expand...
Click to collapse
Oh. Well of course you don't need the volume key to navigate the menu in a touch recovery. That's not the problem. The problem is getting *into* recovery without the volume up key. The only way to do so is if you have a functioning ROM, so if you're in a bootloop, you have to FXZ back to stock from fastboot, reroot, and install a reboot to recovery app. Then commence doing whatever it was you needed to do in recovery (assuming flashing a custom rom again and hope you don't get a bootloop)
Papahyooie said:
Oh. Well of course you don't need the volume key to navigate the menu in a touch recovery. That's not the problem. The problem is getting *into* recovery without the volume up key. The only way to do so is if you have a functioning ROM, so if you're in a bootloop, you have to FXZ back to stock from fastboot, reroot, and install a reboot to recovery app. Then commence doing whatever it was you needed to do in recovery (assuming flashing a custom rom again and hope you don't get a bootloop)
Click to expand...
Click to collapse
I understand now. Yes, it's tough to access fastboot or recovery mode without volume keys working.
Not at all there are ways to get around this. Install xposed framework with an advance power option and install it. Or go to play store and look for an app name i believe quick reboot
audit13 said:
I understand now. Yes, it's tough to access fastboot or recovery mode without volume keys working.
Click to expand...
Click to collapse
Indeed. I've wasted several development hours just getting back to a workable system when I end up with a bootloop. Makes testing very frustrating.Volume down key still works (it seems people only ever have problems with the volume up button) so can still get into fastboot. It would all be good if the "fastboot reboot recovery" command worked on this phone, but it's blocked.
EDIT: @Technofreak, once again that won't work if you're in a bootloop.
Papahyooie said:
Indeed. I've wasted several development hours just getting back to a workable system when I end up with a bootloop. Makes testing very frustrating.Volume down key still works (it seems people only ever have problems with the volume up button) so can still get into fastboot. It would all be good if the "fastboot reboot recovery" command worked on this phone, but it's blocked.
EDIT: @Technofreak, once again that won't work if you're in a bootloop.
Click to expand...
Click to collapse
Yes, and fastboot only works while in download mode, which you can't access while on a bootloop.
mmm... is there any way to make the device boot into download mode by default? That would be maximum safety.
Btw, did your vol up key broke by itself? did you do the battery mod? Thanks for your input.
jaweinre said:
Yes, and fastboot only works while in download mode, which you can't access while on a bootloop.
mmm... is there any way to make the device boot into download mode by default? That would be maximum safety.
Btw, did your vol up key broke by itself? did you do the battery mod? Thanks for your input.
Click to expand...
Click to collapse
You mean download mode as in the menu where you can choose recovery or fastboot? You can't get to that without the volume up button at all. You should be able to still enter fastboot, even from a bootloop. Just hold down the power and vol down button until it vibrates, then let go. Then hit power button once more, and you should be in download mode. But that still won't get you into recovery, so you still have to FXZ back to stock from there and redo everything. There IS a way (sort of) to get it to boot to fastboot every time. Just flash an FXZ and unplug it while it's flashing system.img. Then manually flash a system.img. That should trigger the sticky bits deal where it boots into fastboot every time... but I really don't know what that will accomplish, because every time you reboot your phone you'll have to plug it into a computer and use "fastboot reboot." There isn't a reboot to recovery command in fastboot, and there is no option within fastboot itself to reboot, so you'd have to plug it into the computer and use fastboot reboot.
I wish there was a software option to always ALWAYS boot into recovery from a cold boot. That way you could always get back to recovery no matter what. FXZ is surely a last resort, but you can always restore a backup from recovery.
Yes, I have an EB40 battery mod. But the volume button didn't stop working until a couple of months after doing that. It was seemingly random. Just stopped working one day. I can't way whether it's related or not.
Papahyooie said:
Yes, I have an EB40 battery mod. But the volume button didn't stop working until a couple of months after doing that. It was seemingly random. Just stopped working one day. I can't way whether it's related or not.
Click to expand...
Click to collapse
Mine did the same, broke down randomly after the EB40 mod. Can't check the frickin button since the black t5 screws got worn out (****ty quality).
What about fastboot update? isn't that suposed to flash zip files, as in cm zips?
EDIT: Been trying the vol down + power for a while, it behaves as normal power button, can't get to bootloader.
jaweinre said:
Mine did the same, broke down randomly after the EB40 mod. Can't check the frickin button since the black t5 screws got worn out (****ty quality).
What about fastboot update? isn't that suposed to flash zip files, as in cm zips?
EDIT: Been trying the vol down + power for a while, it behaves as normal power button, can't get to bootloader.
Click to expand...
Click to collapse
I have never been able to get fastboot update to work. I believe it is restricted on this phone just like fastboot reboot recovery is. Don't quote me on that as I've never seen anyone outright say that is the case, it just has never worked for me.
If it makes you feel better,don't bother trying to get the scews out. I have taken mine all the way down to the motherboard to see if there was anything obviously wrong with the volume button. Mine seems to have nothing physically wrong with it. The button (the bare button on the mobo, not the plastic piece) pushes well and even gives a nice tactile click when you push it down with the tip of a screwdriver or soemthing pointy. Hell, I've even booted it up with the case off, bare motherboard, while holding down the button with said screwdriver and it still won't work. It's got to be something like a trace burned or cracked on the motherboard, but with all the componants and shields around it I can't tell. It looks normal, and no different than the volume down button.
That sucks that you can't use the vol down and power button to get to fastboot. I just tried it myself to make sure I said it right and it worked fine. Maybe your volume down button doesnt work either??? You have to be very VERY careful if you cant get into fastboot. Don't get into a bootloop, because I don't know if there is any other way to recover at all. The only way I would know would be to short the circuit on the mobo to force the mobo to recognize a volume button press, and nobody wants to mess with that crap. Don't do any mods that are too exotic lol.
Vol down key is ok. Do you press both buttons while phone is off? For how long? This is weird.
jaweinre said:
Vol down key is ok. Do you press both buttons while phone is off? For how long? This is weird.
Click to expand...
Click to collapse
Well, I believe the correct way to do it is to hold all three buttons down at one time, but for me just holding down the power and volume down button works. If the phone is on, just hold those two buttons down until it vibrates a couple times. At that point let go of the power button. Then press the power button again, and it should boot into fastboot mode.
If the phone is off, I would assume just hold down the power button and volume down buttons. Then let go of the power button while still holding down the volume button and it should boot to fastboot mode.
Papahyooie said:
If the phone is off, I would assume just hold down the power button and volume down buttons. Then let go of the power button while still holding down the volume button and it should boot to fastboot mode.
Click to expand...
Click to collapse
worked. thanks.
jaweinre said:
worked. thanks.
Click to expand...
Click to collapse
Good good. That will at least allow you to FXZ if all else fails. Just don't flash anything unless you have the time to FXZ back and do the whole process over, because in the event of a bootloop, AFAIK that is your only choice.
But we can always go to the recovery mode using the command prompt.
Connect the mobile to computer and use adb fastboot commands.
swapnil0545 said:
But we can always go to the recovery mode using the command prompt.
Connect the mobile to computer and use adb fastboot commands.
Click to expand...
Click to collapse
Once again, fastboot reboot recovery does not work on the Atrix HD. Let me qualify that, because there may be some people that it does work for, but the majority of us, the command is locked. In most cases, that is an invalid point, because we cannot get to recovery using fastboot.
My OP3T power button has stopped working. I am going to replace the phone with OnePlus Nord. As the release is nearly 1 week away I have been trying to live with this phone for some time. I keep the phone powered up all the time. But yesterday night I suddenly lost 50% of the battery over night down to 0. So the phone switched off.
Trying to power up the phone I looked up some options online. One of the ways was to plug it in to the charger and use the volume key. As my bootloader is unlocked the volume key took me to the options menu. There I can see all the options - Power Off, Restart, Recovery etc. I can't select any option because the power button is broken. And I can't go back to the main power menu as well.
how do I come out of that menu?
how do I power on the phone?
vicky_ag said:
My OP3T power button has stopped working. I am going to replace the phone with OnePlus Nord. As the release is nearly 1 week away I have been trying to live with this phone for some time. I keep the phone powered up all the time. But yesterday night I suddenly lost 50% of the battery over night down to 0. So the phone switched off.
Trying to power up the phone I looked up some options online. One of the ways was to plug it in to the charger and use the volume key. As my bootloader is unlocked the volume key took me to the options menu. There I can see all the options - Power Off, Restart, Recovery etc. I can't select any option because the power button is broken. And I can't go back to the main power menu as well.
how do I come out of that menu?
how do I power on the phone?
Click to expand...
Click to collapse
Without the power button you're screwed
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Without the power button you're screwed
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I left the phone as it is and once the power discharged I could experiment again. And I have tried these things. Writing them down in case people need help:
1. using this method:
https://www.techjunkie.com/how-to-turn-on-and-off-oneplus-3-with-broken-power-button/
But then using the volume down button doesn't do anything for me. The phone boots up and waits on the first screen - which says bootloader is unlocked. And then it goes to the second screen - which says drm-verity error message. And then it goes to the Oneplus Logo and gets stuck. Trying to use the volume down to cancel doesn't work. When I connect the phone to my pc, it gives me error - "usb has malfunctioned". I tried using a friend's Ubuntu just in case of issues with Windows 10. Ubuntu doesn't recognize the phone at all. So that is a no-go.
2. Same method as above instead using the volume up button. The phone doesn't boot up at all and neither it is recognized by the computer.
3. Call up Oneplus support center for button replacement. If you are in Bangalore, India you are out of luck. OP has stopped supplying OP3T parts for over a year now.
I thought there might be a way to get into fastboot mode using just volume keys and then I could do "fastboot reboot". It looks like I am wrong.
vicky_ag said:
I left the phone as it is and once the power discharged I could experiment again. And I have tried these things. Writing them down in case people need help:
1. using this method:
https://www.techjunkie.com/how-to-turn-on-and-off-oneplus-3-with-broken-power-button/
But then using the volume down button doesn't do anything for me. The phone boots up and waits on the first screen - which says bootloader is unlocked. And then it goes to the second screen - which says drm-verity error message. And then it goes to the Oneplus Logo and gets stuck. Trying to use the volume down to cancel doesn't work. When I connect the phone to my pc, it gives me error - "usb has malfunctioned". I tried using a friend's Ubuntu just in case of issues with Windows 10. Ubuntu doesn't recognize the phone at all. So that is a no-go.
2. Same method as above instead using the volume up button. The phone doesn't boot up at all and neither it is recognized by the computer.
3. Call up Oneplus support center for button replacement. If you are in Bangalore, India you are out of luck. OP has stopped supplying OP3T parts for over a year now.
I thought there might be a way to get into fastboot mode using just volume keys and then I could do "fastboot reboot". It looks like I am wrong.
Click to expand...
Click to collapse
Nice find!
Thanks for sharing this info.
So I decided to test the method and found:
- it works just as well with plugging into a computer as into a charger.
- you can take your finger of the volume-down button as soon as you feel the phone buzz and the phone boots into recovery
- if you keep the button pressed until you see the dm-verity screen (on unlocked bootloader) nothing happens until you take your finger off and then it'll reboot into recovery
- it does not work using volume-up, in other words it won't boot into fastboot. In fact trying to do this seems to prevent the volume-down method from working. Having tested volume-up I couldn't get volume-down to work until I had actually booted up (using power button) and then powered off.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Nice find!
Thanks for sharing this info.
So I decided to test the method and found:
- it works just as well with plugging into a computer as into a charger.
- you can take your finger of the volume-down button as soon as you feel the phone buzz and the phone boots into recovery
- if you keep the button pressed until you see the dm-verity screen (on unlocked bootloader) nothing happens until you take your finger off and then it'll reboot into recovery
- it does not work using volume-up, in other words it won't boot into fastboot. In fact trying to do this seems to prevent the volume-down method from working. Having tested volume-up I couldn't get volume-down to work until I had actually booted up (using power button) and then powered off.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Thank you for testing that. I am confused though. On booting up I get two screens followed by the Oneplus logo. The first screen says "phone has been unlocked" and second is the drm-verity screen. Do you see only the drm-verity screen?
When I use the volume down button I get stuck on the Oneplus logo. The phone doesn't boot into recovery. Does that happen when you experimented with the volume up button? I mean if you use volume up first and then tried volume down does it get stuck on the logo?
vicky_ag said:
Thank you for testing that. I am confused though. On booting up I get two screens followed by the Oneplus logo. The first screen says "phone has been unlocked" and second is the drm-verity screen. Do you see only the drm-verity screen?
When I use the volume down button I get stuck on the Oneplus logo. The phone doesn't boot into recovery. Does that happen when you experimented with the volume up button? I mean if you use volume up first and then tried volume down does it get stuck on the logo?
Click to expand...
Click to collapse
This is the first screen I get (picture) after volume down, then I end up in TWRP (I'm not using stock recovery). Also, I'm running a custom rom.
I never get any response if I use volume up.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
This is the first screen I get (picture) after volume down, then I end up in TWRP (I'm not using stock recovery). Also, I'm running a custom rom.
I never get any response if I use volume up.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I got the power button fixed from unofficial shop. And the first thing I did was to test the volume button to recovery process. I'm on TWRP but the official OOS Rom. And it still doesn't work. I am stuck on the Oneplus Logo. Next I tried rebooting directly to TWRP using the Reboot app:
https://play.google.com/store/apps/details?id=com.stephansmolek.reboot&hl=en_IN
And while it takes me to TWRP I am stuck on the TWRP logo screen. On searching I found this thread:
https://forum.xda-developers.com/oneplus-3t/help/twrp-stuck-splash-screen-t3541037
So, the process works only if the phone can get past the TWRP splash screen.
If not, the phone will get stuck on the OnePlus logo and the only choice is to get it repaired. And repairing will happen at unofficial shops because Oneplus has stopped shipping OP3T parts.
vicky_ag said:
I got the power button fixed from unofficial shop. And the first thing I did was to test the volume button to recovery process. I'm on TWRP but the official OOS Rom. And it still doesn't work. I am stuck on the Oneplus Logo. Next I tried rebooting directly to TWRP using the Reboot app:
https://play.google.com/store/apps/details?id=com.stephansmolek.reboot&hl=en_IN
And while it takes me to TWRP I am stuck on the TWRP logo screen. On searching I found this thread:
https://forum.xda-developers.com/oneplus-3t/help/twrp-stuck-splash-screen-t3541037
So, the process works only if the phone can get past the TWRP splash screen.
If not, the phone will get stuck on the OnePlus logo and the only choice is to get it repaired. And repairing will happen at unofficial shops because Oneplus has stopped shipping OP3T parts.
Click to expand...
Click to collapse
Glad you managed to get the button repaired.
Fyi, I've never had issues with TWRP and f2fs formatted data partition. In fact, that's what I have currently.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Glad you managed to get the button repaired.
Fyi, I've never had issues with TWRP and f2fs formatted data partition. In fact, that's what I have currently.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
I tried re-installing TWRP and found this:
https://twrp.me/oneplus/oneplusthree.html
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
Maybe, the stock kernel is the issue? I am on [email protected] A custom rom might have another kernel? And the process works on stock recovery on stock kernel?
vicky_ag said:
I tried re-installing TWRP and found this:
https://twrp.me/oneplus/oneplusthree.html
Maybe, the stock kernel is the issue? I am on [email protected] A custom rom might have another kernel? And the process works on stock recovery on stock kernel?
Click to expand...
Click to collapse
You could use the patched kernel from here https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
Alternatively, if you install Magisk it will automatically patch the kernel.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
Magisk it will automatically patch the kernel.
Click to expand...
Click to collapse
Just for accuracy: magisk doesn't patch the kernel (would be a bit tough to supply binary positions for each and every single kernel - yes, they differ from build to build - but some files in the boot partition. Droping the tripped verity bit is done by magisk after booting the kernel (that's why magisk will fail on that as soon as the safetynet api starts to use hardware backed checks for bl status - hopefully we can work around that with patched kernel sources).