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...
Related
I seemed to have bricked my Nexus S 4g, I unlocked the bootloader, and had MIUI running on there for some time with no problems, I took the rom off and started to run with just stock android. I ran into an issue when i tried to use an application that would change the system fonts, Fontchanger, and now the phone will not even reach the nexus s loading screen but instead gets immediately stuck at the first image screen showing the Google logo. When i hold the volume up and power button i can get into the boot menu, but when i try to get into the recovery menu i just get the triangle with the exclamation mark logo. Can anyone help me out with this one?
BUMP BUMP BUMP BUMP In a similar situation, flashed the wrong rom ran the OTA and wiped out recovery & USB.
Press Power and Volume Up Button in recovery mode and you will get options to clean things up. Did the same in morning and got it when accidentally pressed.
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
Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.
t1j said:
Hello, I just unlocked bootloader, flashed custom recovery (clockwork 6.0.4.8), and gained root on my HTC One S. I then attempted to install a custom ROM, (cyanogen 12.1).
After installing and telling Clockwordmod to reboot, I believe I am in a boot loop. The white HTC screen pops up and then goes to black and stays there. When I plug my phone into my computer, I get the connection and chime, and a new device appears in Device Manager called "HTC MTP Device." When I am in fastboot mode, my phone is shown as "Android ADB Interface" in device manager, so this is different. This leads me to believe that my phone is not dead or off, it is on with a blank screen. I do not believe my computer will recognize a device that is not powered on.
I have HTC Sync Manager and I have the option for it to automatically pop up when a device is connected. It pops up, but with an error saying HTC Sync Manager could not connect to your phone.
I am able to hard-reset the phone, by holding down the Power button for several seconds. However, this just repeats the process (White HTC logo screen, then black screen). I am not able to enter bootloader or recovery by holding down Volume and Power. I have tried Volume Up + Power, Volume Down + Power, and Volume Up + Volume Down + Power.
Also adb no longer recognizes my device, so I can not interact with the phone that way either.
Currently, my only idea is to allow my phone to die so I can try booting it into recovery from power off. But if there are any other ideas that would be great.
Right before I rebooted, after installing the ROMs, I got a message saying something like "Root possibly lost, do you want to fix root." I said yes, could this be part of the issue?
I am on Windows 10.
Click to expand...
Click to collapse
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.
In the end, I just flash a different rom, specially Candy5 as found here: http://forum.xda-developers.com/htc-one-s/development/rom-t2964931 and it worked.
It's possible I accidentally flashed a rom that was incompatible with my device, not sure.
EDIT: I also switched from CWM to TWRP. Not sure if that helped.
t1j said:
Just in case anyone stumbles on this. You can boot into the bootloader by Holding down the Power Button for several seconds, the soft buttons will blink, indicated ensuing reboot, when they stop blinking, hold Volume Down until you get to the bootloader menu. The phone does not need to be powered off for this. From there, adb/fastboot will recognize your phone, and you can factory reset if needed.
However, I figured out my problem. On older HTC models, including the HTC One S, you have to manually flash the boot.img file that is included in the zip for your ROM.
But now I've made it to the cyanogenmod boot screen and am stuck there. sigh. i've been at this literally all day.
Click to expand...
Click to collapse
I have broken volume down button, what can i do? face the same problem
What does it mean by manually flash boot.img? After flashing a custom rom, do not reboot first but flash the boot.img via twrp which can be found in zip for the rom?
Edit: Resolved
I flashed a nightly release of LineageOS and it's working like before!
Software
TWRP 3.1
LineageOS 14.1
Magisk 18.1
Magisk Manager 7.0
Rooted (unsure)
Background
Google Pay recently declined contactless, so I tried re-enabling it with Magisk and changing device fingerprint, to no avail. I rebooted into recovery to install Magisk Canary, by running the magisk-uninstaller.zip. As soon as I swiped right to run it, it rebooted into the turquoise "Downloading... do not turn off target" screen (with no text in the corner). Every attempt to boot into system yielded this.
Troubleshooting Attempts
Holding volume down + power, reboots to Samsung S7 screen then quickly back to the same "Downloading..." screen
Holding volume down + power, then as soon as screen flashes black quickly holding volume up + power goes into TWRP
Cleared cache in TWRP and tried rebooting, same results
Other Information
I can still enter TWRP and see my files via USB on my computer
Even after phone is powered off and I recharge it, the screen goes back to the turquoise "Downloading..." screen. Powering on is the same..
Questions
Does anyone have suggestions as to what I can try next? Or should I create a backup while I can, then reinstall TWRP or another ROM?
Thanks!
therollingthunder said:
Software
TWRP
LineageOS
Rooted (unsure)
Background
Google Pay recently declined contactless, so I tried re-enabling it with Magisk and changing device fingerprint, to no avail. I rebooted into recovery to install Magisk Canary, by running the magisk-uninstaller.zip. As soon as I swiped right to run it, it rebooted into the turquoise "Downloading... do not turn off target" screen (with no text in the corner). Every attempt to boot into system yielded this.
Troubleshooting Attempts
Holding volume down + power, reboots to Samsung S7 screen then quickly back to the same "Downloading..." screen
Holding volume down + power, then as soon as screen flashes black quickly holding volume up + power goes into TWRP
Cleared cache in TWRP and tried rebooting, same results
Other Information
I can still enter TWRP and see my files via USB on my computer
Even after phone is powered off and I recharge it, the screen goes back to the turquoise "Downloading..." screen. Powering on is the same..
Questions
Does anyone have suggestions as to what I can try next? Or should I create a backup while I can, then reinstall TWRP or another ROM?
Thanks!
Click to expand...
Click to collapse
If the rom zip is on your sd card and you can boot into TWRP, you can flash the rom again, do not wipe anything! and all your apps files etc should be still there when the phone reboots. It's the same process as updating lineage over the existing build.
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.