Related
I was trying to root my one for the first time. I followed someone's tutorial online, and everything was perfect at first, until I got into using TWRP for recovery. I used version 2.5. After I got into it, the touch screen is not working. I stuck in the lock screen now, not able to unlock, not able to restart, not even able to power off. After some digging, I found out that probably I should have used the version 2.6 instead in the first place. Now my question is, do I need to wait until the power drains out before I could do anything else, or if there is anything I could do to restart the phone and do this recovery process again with TWRP v2.6? Thanks.
kevin0634 said:
I was trying to root my one for the first time. I followed someone's tutorial online, and everything was perfect at first, until I got into using TWRP for recovery. I used version 2.5. After I got into it, the touch screen is not working. I stuck in the lock screen now, not able to unlock, not able to restart, not even able to power off. After some digging, I found out that probably I should have used the version 2.6 instead in the first place. Now my question is, do I need to wait until the power drains out before I could do anything else, or if there is anything I could do to restart the phone and do this recovery process again with TWRP v2.6? Thanks.
Click to expand...
Click to collapse
try doing a hard reset and flash the latest TWRP in recovery mode.
hard reset:
hold your phone under bright light ( i personally use a torchlight for this)
press power + vol down button
i had the same panic attack just few days ago
office usirmr
kevin0634 said:
I was trying to root my one for the first time. I followed someone's tutorial online, and everything was perfect at first, until I got into using TWRP for recovery. I used version 2.5. After I got into it, the touch screen is not working. I stuck in the lock screen now, not able to unlock, not able to restart, not even able to power off. After some digging, I found out that probably I should have used the version 2.6 instead in the first place. Now my question is, do I need to wait until the power drains out before I could do anything else, or if there is anything I could do to restart the phone and do this recovery process again with TWRP v2.6? Thanks.
Click to expand...
Click to collapse
It is because your phone has updated firmware with the updated touch drivers. twrp 2.5 does not support the new drivers as 2.6 doesnt support the old drivers either. Download official 2.6.3.0 img file. reboot into boot loader. If you are stuck on twrp hold power button until phone turns off "10-15" sec. Hold vol down and power to get into boot loader. click fastboot. Use your computer in terminal or command
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
obviously you have to be in the directory with the img file. Search twrp in google to get newest img file
an0ther said:
It is because your phone has updated firmware with the updated touch drivers. twrp 2.5 does not support the new drivers as 2.6 doesnt support the old drivers either. Download official 2.6.3.0 img file. reboot into boot loader. If you are stuck on twrp hold power button until phone turns off "10-15" sec. Hold vol down and power to get into boot loader. click fastboot. Use your computer in terminal or command
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
obviously you have to be in the directory with the img file. Search twrp in google to get newest img file
Click to expand...
Click to collapse
I have exactly the same problem.
But I can't hard reset the HTC ONE via volume down + power button...
Can't access the phone via USB attached cable and the common tools... :///
Do I have to wait till the battery is empty or is there a further solution?
Try opening the back cover and removing your battery and connecting again(btw its easy to remove the battery on a non removable battery mobile,unless you have a finger print scanner at the back side)...now switch on the mobile........you cant charge your mobile while it is switched off....so you have to charge your battery in the frozen twrp screen and later you have to remove and connect the battery to operate your mobile(you can charge your phone normally when it is switched on)...i tried this,works fine with my HTC 826..................
BTW if someone found a solution,,please help us to remove the frozen twrp screen....I think this would help
lol same problem, i powered off the phone, then power up it, (redmi 9 lancelot) and its in chinesse lol, hten i forgot to change the leanguege and reboot it, now waiting ;-;
Note: This is a re-post from the Verizon HTC forums (http://forum.xda-developers.com/showthread.php?t=2533042)
I just rooted and S-off my HTC via rumrunner.
No flash roms install or custom recovery installed.
I wanted to see if I still had CWM from my last root (I returned to stock via http://forum.xda-developers.com/show...highlight=s-on.
So I went into the bootloader or fastboot (I don't remember) and hit recovery. This did not send me to a CWM, but it appeared to be the stock version of recovery. The process took too long (I know impatient) so I turned it off via power button + volume down.
Now I come to you in need, my phone is constantly turning off/on only displaying the green htc text, no red text, then pausing for 8 seconds, then off again to black screen. The whole process lasts 12 seconds, and this had been going on for about 10-15 min atm.
Plugging it in, my computer does not have the time to recognize it with adb, or fastboot.
I cannot use the power button + volume down to go into bootloader, and pressing the power button does nothing.
Please help me.
So here's the update.
Screen is now black, meaning the boot up/down process has stopped.
I have tried these:
A. Hold down the volume down + power button for 20+ seconds.
B. Hold down the volume up + volume down + power button for 20+ seconds and let up on the volume up button when screen goes black.
These two methods results in a single boot up to green HTC text then black screen.
I suspect the device has lost most of its power. Tried it for a third time, the device is now unresponsive and remains at black screen.
Now I plugged the usb cable connected to the power adapter.
The device enters the aforementioned continuous boot loop.
I tried method A and B, and there are no results, the boot loop continues. Now the device returns to the low or no powered state.
Now the device is connected to the computer. The same happens as if it were connected to the power adapter.
Method A and B still do not work.
Results: holding down buttons longer do nothing for me. The device seems to have lost power, but when charged, immediately the device enters the boot loop state.
Note: when doing method A and B the trials were done when screen is on and when screen is off, still no results.
Now the screen is off and not connected to anything. The problem still persists.
geeibara said:
Note: This is a re-post from the Verizon HTC forums (http://forum.xda-developers.com/showthread.php?t=2533042)
I just rooted and S-off my HTC via rumrunner.
No flash roms install or custom recovery installed.
I wanted to see if I still had CWM from my last root (I returned to stock via http://forum.xda-developers.com/show...highlight=s-on.
So I went into the bootloader or fastboot (I don't remember) and hit recovery. This did not send me to a CWM, but it appeared to be the stock version of recovery. The process took too long (I know impatient) so I turned it off via power button + volume down.
Now I come to you in need, my phone is constantly turning off/on only displaying the green htc text, no red text, then pausing for 8 seconds, then off again to black screen. The whole process lasts 12 seconds, and this had been going on for about 10-15 min atm.
Plugging it in, my computer does not have the time to recognize it with adb, or fastboot.
I cannot use the power button + volume down to go into bootloader, and pressing the power button does nothing.
Please help me.
So here's the update.
Screen is now black, meaning the boot up/down process has stopped.
I have tried these:
A. Hold down the volume down + power button for 20+ seconds.
B. Hold down the volume up + volume down + power button for 20+ seconds and let up on the volume up button when screen goes black.
These two methods results in a single boot up to green HTC text then black screen.
I suspect the device has lost most of its power. Tried it for a third time, the device is now unresponsive and remains at black screen.
Now I plugged the usb cable connected to the power adapter.
The device enters the aforementioned continuous boot loop.
I tried method A and B, and there are no results, the boot loop continues. Now the device returns to the low or no powered state.
Now the device is connected to the computer. The same happens as if it were connected to the power adapter.
Method A and B still do not work.
Results: holding down buttons longer do nothing for me. The device seems to have lost power, but when charged, immediately the device enters the boot loop state.
Note: when doing method A and B the trials were done when screen is on and when screen is off, still no results.
Now the screen is off and not connected to anything. The problem still persists.
Click to expand...
Click to collapse
If I had to guess I would say your volume down is broken, else it would enter hboot
plug in the power and let it charge all day. then plug it to your pc and try to adb reboot bootloader or adb reboot recovery the instant you here the pc usb ingage.
once you get to the bootloader try and fastboot erase cache followed by fastboot reboot
after your phone boots you should be able to go back to bootloader and reinstall custom recovery
clsA said:
If I had to guess I would say your volume down is broken, else it would enter hboot
plug in the power and let it charge all day. then plug it to your pc and try to adb reboot bootloader or adb reboot recovery the instant you here the pc usb ingage.
once you get to the bootloader try and fastboot erase cache followed by fastboot reboot
after your phone boots you should be able to go back to bootloader and reinstall custom recovery
Click to expand...
Click to collapse
I have a few questions/concerns to this.
1. When I charge it, I can't stop the phone from the continuous boot. I'm afraid that doing this all day might hurt the phone more.
2. Currently I have been charging it via computer (still boot loop), and the computer does not recognize it at all. I think there is really not enough time because the loop duration is only a few seconds.
3. Since the phone is connected to the computer, the commands adb reboot bootloader and adb reboot recovery does not work. Error: device not found.
geeibara said:
I have a few questions/concerns to this.
1. When I charge it, I can't stop the phone from the continuous boot. I'm afraid that doing this all day might hurt the phone more.
2. Currently I have been charging it via computer (still boot loop), and the computer does not recognize it at all. I think there is really not enough time because the loop duration is only a few seconds.
3. Since the phone is connected to the computer, the commands adb reboot bootloader and adb reboot recovery does not work. Error: device not found.
Click to expand...
Click to collapse
well have you held the phone under a bright light and held just the power down for 15 seconds and let go when the phone go's off ?
clsA said:
well have you held the phone under a bright light and held just the power down for 15 seconds and let go when the phone go's off ?
Click to expand...
Click to collapse
So what is this method supposed to accomplish?
I did this and the phone stopped the continous boot. However when I tried to go to hboot it went back into the loop. I did this twice, and I'm able to stop the loop with the bright light method, but I don't know what to do from here.
Note: when plugging phone into computer, the loop starts again.
geeibara said:
So what is this method supposed to accomplish?
I did this and the phone stopped the continous boot. However when I tried to go to hboot it went back into the loop. I did this twice, and I'm able to stop the loop with the bright light method, but I don't know what to do from here.
Note: when plugging phone into computer, the loop starts again.
Click to expand...
Click to collapse
will the phone charge when in the off state / not from PC ?
clsA said:
will the phone charge when in the off state / not from PC ?
Click to expand...
Click to collapse
Plugging the phone into the adapter, the phone charges, but the boot loop occurs again.
geeibara said:
Plugging the phone into the adapter, the phone charges, but the boot loop occurs again.
Click to expand...
Click to collapse
the phone should not bootup with the power cord plugged in from an off state (are you turning the phone back on ?)
turn off phone by holding power 15 seconds under a bright light
plug phone into outlet (not PC) let charge till green light comes on (not Red)
hold volume down and power for 10 seconds ( you should be in hboot)
plug phone to PC choose fastboot hit power
your now in fastboot usb
from here you reflash recovery
fastboot erase cache and reboot recovery
if your still in bootloop I'm at a loss, and seems your hboot is corrupted I think you have to return your phone to Verizon or HTC.
clsA said:
the phone should not bootup with the power cord plugged in from an off state (are you turning the phone back on ?)
turn off phone by holding power 15 seconds under a bright light
plug phone into outlet (not PC) let charge till green light comes on (not Red)
hold volume down and power for 10 seconds ( you should be in hboot)
plug phone to PC choose fastboot hit power
your now in fastboot usb
from here you reflash recovery
fastboot erase cache and reboot recovery
if your still in bootloop I'm at a loss, and seems your hboot is corrupted I think you have to return your phone to Verizon or HTC.
Click to expand...
Click to collapse
Well I don't know if it is truly off, I'm just assuming it is.
But yes as soon as I plug the phone into the power adapter the red led flashes on, and the htc logo appears, then the loop continues.
I'll probably take it into Verizon tomorrow and update on what happens.
Update: Welp, I gave up. I'm going to get my replacement soon and I'll be turning it into Verizon. Really it's not that bad of a loss since I just wiped the phone, only thing is I lost my screen protector and carbon skin
geeibara said:
Update: Welp, I gave up. I'm going to get my replacement soon and I'll be turning it into Verizon. Really it's not that bad of a loss since I just wiped the phone, only thing is I lost my screen protector and carbon skin
Click to expand...
Click to collapse
sorry to hear that mate!!!
So first things first:
I am not a noob, I have been flashing phones for years
The phone has an UNLOCKED bootloader
I know what a bootloader/recovery are etc
So last night I upgraded my phone to 6.0.1. I then decided to root it and get a kernel on for color control. So I download one of the new kernels (Elementalx) for 6.0.1 and the systemless root that he recommended in his post. I flash both files and boot the phone, the phone bootloops twice after the password to boot screen and then it works fine. I install a few things adjust a few things (nothing pertaining to root) and then before I jump into the shower I reboot it. I look at it after a few minutes and it is sitting at the google screen with the padlock, no worries it has happened before so I reboot it only to be met with this same screen. Over and over it just halts here. I do the button trick to get into the bootloader, no dice. No button combination can get me past this screen.
I then go over to my PC and try it out and see if I am getting a Q_BULK issue (I had it happen to my Galaxy Nexus before) and the PC doesn't even acknowledge it, so now I am getting a little worried. I cannot power off the device normally, it just reboots back to here. I can manage a trick with the power cable and some quick button presses to enter the "charging" mode and from there it appears to shut down. Upon boot though it comes right back to this halt. :-/
So, does anyone have ANY experience with this before I contact Motorola? I really don't want to because I have frame swapped and don't look kindly on the process of undoing it for a replacement, but if it must be then it must be. Below is a TLR
Phone boots to Google/padlock screen
CANNOT access the bootloader/recovery through normal means
PC does not recognize it (I did prior in both fastboot and recovery so the drivers are all installed)
the phone does NOT appear to be in Q_BULK
the phone will not shut down, it just boots back to here
It "was" running ElementalX and the systemless root (both are the newest) for 6.0.1
-Current status, sitting on this screen waiting to die... but it has an almost full charge
OK, first off... YOU ARE A NEWBIE.
Turn off the phone and boot to bootloader and use that to load your custom recovery and restore your working backup.
Failing that, fastboot flash the stock image from bootloader mode.
What are you hoping to accomplish by draining your battery completely, this can only make matters worse.
@scryan you are a funny man?
you didnt say anything about trying to get into recovery.. i assume you tried getting unto your recovery?
Hold power button, up and down button all at the same time. If you are on stock recovery wipe user data and cache. See if you can boot into the bootloader afterwards. That's unusual you cannot get into stock or custom (if you have it) recovery.
So you're main problem here is that you can't get into your bootloader or recovery right now? Hmm..... that can't be good. My best guess would be to keep trying to get it into your bootloader, just keep on holding volume down and power for a long time, hopefully if you can get into either bootloader or recovery you can fastboot flash a clean stock image, or restore a nandroid backup (assuming you have one) with TWRP. My best guess though.
Briefly, your device powers on, so there's sign of life. It is either your cable, pc' usb port or the usb socket of the phone is at fault. Did you try with another usb cable at another usb port in the pc ?
Let the phone power down completely. And when it dies, connect it to a charger while briefly holding the vol down button to get into the bootloader. It might take a while since the phone doesn't have any juice but this trick might just work.
If already no warranty, so dissasembly the deive, re-attack your battery
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).
I believe i've royally screwed up and i want to know if there's anything I can do to save my phone.
I downloaded the latest BeyondROM from here after being on a previous version for about a year (not sure which one I was on):
https://forum.xda-developers.com/ga...evelopment-exynos/rom-beyondrom-v6-0-t4017921
I flashed the zip file through TWRP and only after flashing did I realize that I was on TWRP 3.3.1-11 and not 3.4.0-3, which I'm guessing is why my phone is now stuck on the boot logo when I boot it. I went back into TWRP and cleared the Dalvik & standard cache again after this but no dice.
But it gets worse. I then tried to upgrade to 3.4.0-3 by flashing it from TWRP 3.3.1-11 using the recovery partition, hoping to reflash the firmware after doing so.
After doing this and my phone rebooting, not only am I stuck on the boot screen, but now I can no longer enter recovery mode either by holding Bixby + Vol Up + Power. My phone isn't recognized by my PC or Odin now either.
Is my phone completely bricked, or is there a way to salvage this mess i've made?
Could really use some help.
Thanks guys.
If you can go to download mode, try re-flashing the stock Samsung firmware via Odin.
XTrail02 said:
If you can go to download mode, try re-flashing the stock Samsung firmware via Odin.
Click to expand...
Click to collapse
Thanks for the suggestion, however that's my primary issue. I can't get to download mode (which really should be recovery mode since I have TWRP).
Do you think it could be an issue with me rebooting to recovery mode after upgrading TWRP using TWRP itself? Maybe my phone needs to be hard powered off once to access TWRP again?
And since I have that failed ROM install, the only way to power off the phone would be to wait for the battery to drain.
Power+volume down+Brixby goes right into download mode bypassing the recovery
TheMassiveEffect said:
Power+volume down+Brixby goes right into download mode bypassing the recovery
Click to expand...
Click to collapse
My phone just keeps restarting when Power + vol down are held. Looks like draining the battery didn't help either. I'm stuck on the boot screen even when plugged in with 0% battery. When I remove the USB Cable and hold Vol down + Power, the phone seems to turn off because there's no battery, but immediately after plugging in a power cable, the phone automatically turns on by itself again.
You can try this, but best not to flash anything without charging battery first. You can charge while phone is off: