Hi
I have been helping a friend repair their phone after it got water damaged
THe battery has been replaced and the phone boots and can go into Android
I have since Unlocked the bootloader
Installed TWRP
Rooted it
Installed a Cusom Rom
And installed a Custom Kernel with no issue.
So In my eyes this Phone is 100% working
The Problem i am stuck with is that whenever the phone is turned on it goes straight into the Bootloader screen and the Option bit on the top (Start, Recovery, Reboot BootLoader and Power off)
Constantly scrolls through each option as though the volume key is being pressed
if i press the power button as each option appears the phone will boot into the option i have chosen
While in Android all the buttons work correctly.
Vol up and Down and the power either going to sleep or bringing up the power menu.
Any ideas would be a great help
Probably HW related, but not sure
Sirklip said:
Hi
I have been helping a friend repair their phone after it got water damaged
THe battery has been replaced and the phone boots and can go into Android
I have since Unlocked the bootloader
Installed TWRP
Rooted it
Installed a Cusom Rom
And installed a Custom Kernel with no issue.
So In my eyes this Phone is 100% working
The Problem i am stuck with is that whenever the phone is turned on it goes straight into the Bootloader screen and the Option bit on the top (Start, Recovery, Reboot BootLoader and Power off)
Constantly scrolls through each option as though the volume key is being pressed
if i press the power button as each option appears the phone will boot into the option i have chosen
While in Android all the buttons work correctly.
Vol up and Down and the power either going to sleep or bringing up the power menu.
Any ideas would be a great help
Click to expand...
Click to collapse
after 3 years did u find any solution. exactly same issue happen today :crying:
Try updating to the latest bootloader. But I assume the buttons get stuck sometimes. Try smacking the buttons s a couple of times. Hope that works.
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?
Hey All
Need some help. I accidentally messed up my volume buttons on an HTC M8 and had to use adb to boot into recovery. After booting into recovery, I completely wiped my phone (customer ROM) using team win v2.7.0.0 with the intention of installing an official ROM. (Totally forgot I would need the Volume buttons).
Restarted my phone which seems to be stuck on the white HTC logo boot screen (understandable as I have no ROM on it now).
However, How do I get to turn it off firstly. I have held the Power button for over 2 minutes which seems not to solve the problem. Secondly is there a way I can boot into recovery without Volume buttons when the phone goes off eventually.
adb needs to detect the kernel for it to send instructions from what it seems as it keeps giving the response my device is offline on the white screen.
Is there a way of using adb to boot the device into recovery when the phone is off. Any help or suggestions you may have would be gladly appreciated.
I wanted to install Global Developer ROM for my Redmi 3s Prime which I downloaded from their website. So I started with installing TWRP custom recovery and completed successfully. After this I installed my developer ROM and after success TWRP tool asked me whether to root the phone or not, to which I said YES.
After this blank screen appeared for very long time and nothing happened. So, I long pressed the power button and now my phone is not booting up at all.
I tried the following things but none of them are working.
Fastboot mode by pressing VOLUME DOWN + POWER buttons.
Recovery mode by pressing VOLUME UP + POWER Buttons
Also tried by pressing all three buttons.
I also ran these commands adb devices and fastboot devices, cannot see my device.
And even the battery charging indicator is also not showing up.
Is there any tool or something which can help me to fix this problem?
Any help is appreciated.
chat_faraz said:
I wanted to install Global Developer ROM for my Redmi 3s Prime which I downloaded from their website. So I started with installing TWRP custom recovery and completed successfully. After this I installed my developer ROM and after success TWRP tool asked me whether to root the phone or not, to which I said YES.
After this blank screen appeared for very long time and nothing happened. So, I long pressed the power button and now my phone is not booting up at all.
I tried the following things but none of them are working.
Fastboot mode by pressing VOLUME DOWN + POWER buttons.
Recovery mode by pressing VOLUME UP + POWER Buttons
Also tried by pressing all three buttons.
I also ran these commands adb devices and fastboot devices, cannot see my device.
And even the battery charging indicator is also not showing up.
Is there any tool or something which can help me to fix this problem?
Any help is appreciated.
Click to expand...
Click to collapse
Was the ROM built for your specific model number of Redmi 3s Prime? If it was for a different model number then that's what bricked your device, it probably didn't have anything to do with the message asking you if you wanted to root the device.
If the device does not charge and shows no LED while connected, does not boot to any of its modes, does not connect to PC and makes no tone when connecting it and does not show anything in device manager on PC then your device is hard bricked. You need to replace the motherboard or send the device to a repair shop that offers a JTAG service.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Ok Guys So I Shouldn't Have Done This But I Used Fastboot To Flash Recovery And I think I Did It Wrong. It Said "ok" And Finished And I Rebooted Phone It Resetted And Then Stuck On The Orange State Bootloader Message. I Do The Recovery Mode And Goes Black And Nothing Is Responsive For a While, Sometimes Longer Than Others. This Happens If I Start Phone Normal Or Try Fastboot Or Download.
Because Of My Mistake I Cannot Connect To Pc Software And Im Not Sure Of What I Can Do. I Feel Like Im Not Going To Like The Answer For This But I Got To Take The Blame For This.
Btw i Have A Samsung galaxy Note 20 Ultra Sm-N986u
I think your phone is hard bricked
so you can't get fastboot using volume up+power or via adb?
rescue from manufacturer site pos or just device not being recognised?
It isn't hard bricked it's just way of Samsung trying to make life of simple people more difficult, people who paid for Samsung phones lots of money.
To sort that screen issues what you can surely do is,
Simply press volup + voldown buttons at the same time, no matter if you're on that orange screen or whatever just press those those two buttons at the same time and keep pressing them while you connect your phone to pc. you will boot into download mode. Then flash stock firmware for your phone. After stock of flashed Reboot and start your phone, go to developer options see if oem unlock option is there if it is then oem unlock it if it is not then go back to settings manually change date to year ago, then go to updates disable auto update, connect to WiFi, and press on update several times untill window shows up saying no updates, then go to developer options you should see oem unlock, unlock it.
Then boot into download mode and make sure you have working copy of recovery.
And make sure you follow instructions of whoever recovery you installed on how to boot into recovery. I have S20 plus and too had troubles with it, and the only working recovery for my phone is twrp customised. To boot into it after flashing recovery from odin auto reboot disabled I pressed voldown and power, USB cable connected, then after screen goes off I changed from voldown to volup while kept pressing power button and cable connected. Orange screen with warning showed up for 5 sec I kept pressing and it bottled to twrp and then I was able to install custom rom beyond rom and while installing in aroma I was able ti choose option to remove orange screen.
That's it.
I ran into the same error. I mistakenly loaded twrp's recovery into userdata instead of ap section. The phone was stuck at the orange screen and nothing was happening whatever i pressed. I waited till the battery to dry out and with 0% battery, i directly connected to pc and was able to get into download mode. Then i flashed stock and everything is now back to normal.
Carl Johnson (Cj) said:
I think your phone is hard bricked
Click to expand...
Click to collapse
Absolutely not