Stuck on error boot screen. - OnePlus 7 Pro Questions & Answers

I'm stuck on the screen where it shows up that boot loader is unlocked etc etc, visit the link and press power button to pause, which does nothing.
I can get it to reboot after holding down volume+power key for 10 sec, but it reboots it to the same screen, Windows doesn't detect the device via USB and I'm lost and haven't found any solutions yet, help is appreciated.
Edit: nvm, got it to TWRP again, but I don't get it to root properly after flashing magisk, rebooting only gets me back to trwp every time...
Using stock in the meantime, scared af.

Related

[Q] Triumph stuck at moto logo, cant get into clockworkmod

Ok so today my triumph stopped responding so i restarted it (took out the battery). then rebooted. upon reboot phone shuts down and now will hang at the motorola logo for about 10 min before boots but will shut back down due to the battery being dead(but had full charge when this started). Dont know what happened. So i try to get into clockworkmod to flash backup. cant get into it. the only thing i can do is get to the recovery.img file(pressing power+volume down). Other than that nothing.
also tried to boot with power pluged in. it stayed on but would not respond to any touches or button press except the lock button.
I have cwm 5.0.2.6 installed and tickerguy's cm7.
never had this problem till today. Any help would be appreciated.
a new development has occurred. now when i try to access recovery, the phone will just vibrate without stopping.
and i believe its stuck in a boot loop but without recovery i dont know anyway to exit the loop.
Are you able to get into download mode (power off then simultaneously press power button & vol- (should show polling))
Sent from my Triumph using xda premium
Yes i am able to get to download mode
Well after some tinkering (replacing the recovery image, assuming something corrupted it) i can now get to recovery, still takes 10 min to load it though. But i am unable to do anything in recovery because i have to press the menu button to confirm selection but the buttons wont respond. Some help would be appreciated.

[Q] Help with Phone Stuck Booting

I'm usually pretty good at following instructions but I have a problem. I am rooted with TWRP, stock kernel. I successfully applied the 4.4.1 update and used the phone for awhile no probs. Tried re-applying the 4 way reboot menu mod that I'd used successfully on 4.4.0. TWRP says flash was successful. I rebooted and am stuck at the spinning google colored circles. I cant get into recovery mode by holding the volume up/down and power buttons. The phone vibrates briefly when I hold all three but the logo keeps spinning. Pressing power button only does the same. Tried connecting to PC but mac says can't read device and to reboot it. ?help?
Update - Got her to reboot with volume down/pwer, into TWRP, and restored from backup, Back up and running...

Unusual bootloop - can't access recovery OR fastboot but loops on "optimzing apps"

Unusual bootloop - can't access recovery OR fastboot but loops on "optimzing apps"
I had my US version OpO 64GB working with CM12 for quite a while, rooted and bootloader unlocked with TWRP (possibly 2.8.6) installed, then some months ago I tried upgrading to CM12.1 through CM updater. This failed miserably - The phone started bootlooping on "Optimizing apps n of N" - as soon as it finished optimizing apps, the phone would reboot and start optimizing again. Booting to safe-mode (Power + VolUpDown) also fails in the same way (though optimizing fewer apps).
I tried rebooting to recovery mode holding Power + VolDown but it just gives a quick buzz (vibration motor) at the "1+" screen and reboots. The same thing happens when I try to boot to fastboot mode with Power + VolUp. So I'm completely stuck. All the guides show being able to boot either to fastboot or recovery (soft-brick) or else the screen being completely black/unresponsive (hard-brick). My phone is neither of these!
I got frustrated enough that I've let it sit on the shelf for the past 6 months, but now I'd like to fix this. All help appreciated.
---danq989
Did you try clearing the cache and doing a factory reset ?
SpectreFang said:
Did you try clearing the cache and doing a factory reset ?
Click to expand...
Click to collapse
That's impossible for me to do since I can't get to launcher or recovery.
No acess to recovery?? Then better take it to service center... Atleast can u boot to fastboot mode or adb accesible then use oneplus one toolkits
---------- Post added at 11:34 AM ---------- Previous post was at 11:31 AM ----------
Install oneplus tool kit, while optimising apps it gets dectected by pc, just make it reboot mode & do reset.... Dnt worry this can be fixed, if all these seems messy then take it to service center
danq989 said:
I had my US version OpO 64GB working with CM12 for quite a while, rooted and bootloader unlocked with TWRP (possibly 2.8.6) installed, then some months ago I tried upgrading to CM12.1 through CM updater. This failed miserably - The phone started bootlooping on "Optimizing apps n of N" - as soon as it finished optimizing apps, the phone would reboot and start optimizing again. Booting to safe-mode (Power + VolUpDown) also fails in the same way (though optimizing fewer apps).
I tried rebooting to recovery mode holding Power + VolDown but it just gives a quick buzz (vibration motor) at the "1+" screen and reboots. The same thing happens when I try to boot to fastboot mode with Power + VolUp. So I'm completely stuck. All the guides show being able to boot either to fastboot or recovery (soft-brick) or else the screen being completely black/unresponsive (hard-brick). My phone is neither of these!
I got frustrated enough that I've let it sit on the shelf for the past 6 months, but now I'd like to fix this. All help appreciated.
---danq989
Click to expand...
Click to collapse
while things are loading, have u tried to hold vol up + power for 10 seconds or until the screen turns off and then hold vol down + power button until the oneplus logo?
Bradl79 said:
while things are loading, have u tried to hold vol up + power for 10 seconds or until the screen turns off and then hold vol down + power button until the oneplus logo?
Click to expand...
Click to collapse
Yes, just tried it. Same thing as described in my original post. When I hold power+volup the screen goes blank. I switch to power+voldown until the 1+ logo. At that point:
1. If I continue to hold the power+voldown key through the 1+ logo, the screen goes blank briefly, the phone vibrates once and reboots. If I continue to hold the power+voldown key, the vibrate&reboot cycle continues indefinitely
2. If I let go of either the power button, the voldown button, or both at or before the 1+ logo, the phone boots normally and goes to "Android is starting... Optimizing app n of 119). When the optimization finishes, the phone instantly reboots.
It's like the phone recovery is gone or inaccessible. Could this have to do with the phone tampering setting? As I said, I had this phone rooted and bootloader unlocked, working fine with CM12 for some time before trying an in-place upgrade to 12.1. That's when things went south.
---danq989

Moto G7 Power XT1955-5: Stuck in BootLoop at "Unlocked and Can't Be Trusted"

Moto G7 Power XT1955-5: Stuck in BootLoop at "Unlocked and Can't Be Trusted"
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
bryangrant4 said:
I made several attempts to install twrp-3.4.0-0-ocean to this new Moto G7 Power. I was able to Unlock the Bootloader, and even had TWRP running twice., but after it was rebooted it would never go back to TRWP, it would reboot to the Stock ROM. Then, runnng adb reboot bootloader would bring me back to the stock bootloader page.
Each time it boots, it has displayed the "Your Device Has Been Unlocked and Can't Be Trusted." page, and then would eventually boot. Annoying, but ok. It is what it is.
However, this last attempt to reboot from the stock bootloader has created an endless bootloop to that "Cant Be Trusted" page.
No combos of holding down the down volume for 3 seconds with the power key.. or holding down the power key for 15 or 20 seconds.. nothing works. All it does it turn the screen off for a couple of seconds and then goes back to the "Can't Be Trusted" warning page.
Well.. turns out it does work, it's just finnicky. This video showed me how to do it.. https://www.youtube.com/watch?v=fA0DHvbIlWY
Holding down the Down Volume and Power for several seconds until the screen goes black, release the buttons, then waiting a moment will allow the bootloader to appear.
1- Should I replace the stock rom? If so, how? I can't boot far enough along to run adb push.. and TWRP will not run.
What I cant do now is factory restore the device. Where can I get a stock rom, or any suggestions? I am pretty sure that's what I get for trying to use the xt1955_5.img file from Minimal+adb_fastboot_platform-tools_r29.0.6_2020 on unofficialtwrp.com's how to page, right?
Thanks in advance..
Click to expand...
Click to collapse
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Glad you're out of boot loop.
Recovered from bootloop and "dead" bootloader screen! Tips to recovery
I was able to Rescue the device from periodic BootLoops and a dead end Bootloader screen.
I referenced the information on this thread in the XDA forums, specifically the “Motorala Unbricking Tools” section.
I then tried the "LMSA: Lenovo's Motorola Smart Assistant" thread to find the link to the Lenovo / Motorola download page.
The Rescue software is a bit clunky. Powerful, but clunky.
There are also some cool tools such as Clipboard Copy Text between Device and PC, a Gif Maker, a Ringtone Maker, and a SCREEN RECORDER!!
Back on Track with the Rescue:
-Linux or Mac versions are NOT available; Windoze only.
-You will need at least 2gb of ram in your virtual Windoze7 machine to run it or it will not run in a useful manner.
- Parallels16/Windoze7-64bit worked fine.
-WINE based installs will NOT work.
To run, you will need to enable USB Debugging, although there are two other ways to connect the phone I did not also try. There even appears to be a way to rescue even a truly bricked dead device.
To Rescue your device:
Download, Install, and Run Rescue and Smart Assistant.
The Rescue process will NOT relock your bootloader.
Select the Rescue tab, then select Rescue Now. If you need to backup the device, try the Backup button right next to the Rescue Now button.
The application has some bugs, shortcomings.. here's some heads up to reduce Stress caused by those bugs..
The software will ask you to select the phone you own. The slider dialogue UI is badly done, so you will go back and forth a dozen times before learning how to navigate the menu. It might auto-recognize, but it did not on mine. Good luck!
Next, download the ROM.. the progress bar does not reflect what is actually going on. Once the 2bg down is 100% complete, it will sit there for a LONG TIME doing nothing. Dont kill the app and restart. It's actually busy unpacking the .zip Rom file into a directory tree on your harddrive. Just go eat some lunch, and come back.
Then, a similar issue occurs when you install the ROM. The progress bar is pretty much done, it just sits there doing nothing.. Let it go for a long time.. it's actually doing it's job, and the progress bar is just badly done.
If you are going to use the backup.. TURN OFF YOUR POWERSAVING stuff on both ends. If it is interupted by Power Saving/Sleep mode, the software will start at the beginning. The backup process takes hours, not minutes, so this is not a good result.
Once backed up, if you are moving to a new phone, there is a couple of ways to do that. I am going to perform these functions today or tomorrow, and will update with the results of those efforts.

Can't enter recovery mode anymore (TWRP)

Hi, I don't know what is happening, but I've been having issues with my phone. I was trying to enter recovery and pressed the button combination for fastboot instead. After that, I tried to get out of fastboot, but it kept going back to fastboot. I noticed holding up for a couple of seconds would boot me into my OS. When I try to enter recovery, the screen goes black and it restarts the phone. It will just keep going in a loop if I hold the buttons. My phone was rooted with magisk and I uninstalled to see if that would help, but it didn't.
I installed an update(I use lineage OS) out of curiosity to see if it would boot to recovery. It booted to fastboot, but after restarting and holding the recovery button combo it booted to twrp and installed the update, then restarted. Now my stupid mistake made my phone unusable. Everything is the same, except Lineage is stuck at the boot screen now. Sometimes it restarts to fastboot, but other times it stays there for possibly infinity.
I don't know what to do. All help is appreciated?
TL;DR Fixed, I think my volume down button was stuck.
Nevermind, I flashed with miflash and still had the problem, then for some reason it worked, but only once. I removed my phone from the case and found that it was booting to os. It is still kind of hard to enter the recovery. I think hitting volume up was cancelling the volume down which was stuck, or something. Now I'm pissed cause I wasted so much time on nothing

Categories

Resources