bricked, can't get to bootloader or recovery, adb doesn't see phone either - HTC One S

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?

Related

[Q] Help Nexus S Totally Bricked!

Please help if you can, would really appreciate, dont know how to unbick my totally F$$$$### Nexus S Phone.
Even in recovery/fastboot mode on my Nexus S (Vol up+power), I cannot get my system to recognize the device....in fact, even in Windows, I am not able to get the system to recognize my device in Recovery mode/Fastboot mode....the only way it will recognize the device is if it is turned on the normal way, and hangs on the "Google unlocked icon" screen.
Some background info:
My power button recently stopped working...I thought it had to do with the fact that I updated NexusTools (was running a CyberGR rom...cant remember the name...had V4 Ultimate in it (downloaded from Rom Manager)).
So what I did was download/install (from the same developer) their hybrid ics rom....that did not brick it...but it also did not fix the power button...so after not liking the new rom, and the fact that it didnt fix my power button, I reflashed to the original rom I had installed (wiped everything, including doing a factory reset), and it just hung on "Google unlocked icon"
Now my phone does the following:
- First of all, the only way to power the device up is to plug it in (it automatically turns on and tries to boot without me pressing the non-functional power button)
- If I let it try to boot, it infinity hangs on the Google unlocked icon screen
- If I boot into recovery (by holding vol up button and plugging the phone into a power source), it hangs on the recovery screen...meaning the power button, as well as the volume buttons, as well as any buttons are non responsive.
- If I boot into recovery, the device doesnt even register on my system....
What am I doing wrong? What can I do to try and fix this?
I would truly appreciate if anyone reading this has some insights for me.
THANKS!!
Knightsage said:
Please help if you can, would really appreciate, dont know how to unbick my totally F$$$$### Nexus S Phone.
Even in recovery/fastboot mode on my Nexus S (Vol up+power), I cannot get my system to recognize the device....in fact, even in Windows, I am not able to get the system to recognize my device in Recovery mode/Fastboot mode....the only way it will recognize the device is if it is turned on the normal way, and hangs on the "Google unlocked icon" screen.
Some background info:
My power button recently stopped working...I thought it had to do with the fact that I updated NexusTools (was running a CyberGR rom...cant remember the name...had V4 Ultimate in it (downloaded from Rom Manager)).
So what I did was download/install (from the same developer) their hybrid ics rom....that did not brick it...but it also did not fix the power button...so after not liking the new rom, and the fact that it didnt fix my power button, I reflashed to the original rom I had installed (wiped everything, including doing a factory reset), and it just hung on "Google unlocked icon"
Now my phone does the following:
- First of all, the only way to power the device up is to plug it in (it automatically turns on and tries to boot without me pressing the non-functional power button)
- If I let it try to boot, it infinity hangs on the Google unlocked icon screen
- If I boot into recovery (by holding vol up button and plugging the phone into a power source), it hangs on the recovery screen...meaning the power button, as well as the volume buttons, as well as any buttons are non responsive.
- If I boot into recovery, the device doesnt even register on my system....
What am I doing wrong? What can I do to try and fix this?
I would truly appreciate if anyone reading this has some insights for me.
THANKS!!
Click to expand...
Click to collapse
yes, sounds like a dead power button(i have one myself).
try going back into your recovery, do a full data wipe(factory reset), then reflash the rom(and gapps). if still nothing, redownload the rom and try again. in your recovery, there is an usb option. use it to transfer your newly downloaded rom from your computer to phone.
Once I am in recovery mode it "freezes" though...as in not even the volume buttons work...they worked fine before, and even work to get into recovery mode...but once there they no longer work...nor does connecting the device in recovery mode to my laptop....so im kind of at a loss, as I cant even use Fastboot/adb to wipe/push anything on the Nexus S through my laptop
Knightsage said:
Once I am in recovery mode it "freezes" though...as in not even the volume buttons work...they worked fine before, and even work to get into recovery mode...but once there they no longer work...nor does connecting the device in recovery mode to my laptop....so im kind of at a loss, as I cant even use Fastboot/adb to wipe/push anything on the Nexus S through my laptop
Click to expand...
Click to collapse
im guessing that your using cwm recovery?
give your phone a few smacks on the back near the power button, your phone thinks its being pressed in.
yes, it definitely thinks it is being pressed in...thats for sure...and makes sense...ill try that haha!
Yes latest CWM Recovery...5.0.2 or something like that...just updated that before phone died...
Weird...so i "smacked" the phone a bit...when I do it in recovery mode, it reboots the phone into recovery....so it definitely thinks its being pressed down constantly...but I have found no way to make it "un-pressed"...only briefly by smacking it...
Knightsage said:
yes, it definitely thinks it is being pressed in...thats for sure...and makes sense...ill try that haha!
Yes latest CWM Recovery...5.0.2 or something like that...just updated that before phone died...
Click to expand...
Click to collapse
in twrp recovery, theres an option to not use the power button to select(thats what im using), is there a similar option in the newer cwm recovery? tr\y pressing the soft buttons). also, see if sticking a fingernail in between the power button helps, to pull out the button a bit.
After continuingto smack it...as well as "pulling" on the power button, I am not able to use volume buttons and power buttons within recovery...flashing a new rom now...will let you know if that fixes it...otherwise I will try unbickable in ubuntu again and see if that fixes it thanks for the pro-tip of smacking it, haha!

Cannot boot into recovery!

Hey guys! I just got a One X from AT&T bought on eBay, although I live in Europe.
I managed to unlock the bootloader by changing the CID to 1111111 etc. (how many 1's?) and it worked fine.
I then ran installed ClockworkMod Touch Recovery for the HTC One X through terminal and it was a success.
I rebooted by holding down the power and volume down, and attempted to boot into recovery. I got a white screen with the HTC logo, and red text underneath saying something like "do not use this without HTCs permission" or something of the sort. The phone then turned off.
NOW I'm trying to boot again into the bootloader (I think that's what it's called, but by turning it off and holding the volume down and power key) and it just doesn't work. I've tried a million times, with different variations of holding down the keys. What happens is the light on the touch keys at the bottom flashes a bunch of times, then it boots normally. Everything works on the phone otherwise.
I tried to do it via fastboot/terminal by issuing the command ./fastboot-mac reboot-bootloader but it just says "waiting for device..." even though it's connected.
Anyone had this problem and found a solution?
Recovery
Clockwork recovery is not supported on the evita. Download goo manager and you should be able TWRP from that. And then you can reboot into TWRP.
I think you flashed CWM for the international (Tegra3 quad core) One X. Install TWRP as previous poster recommended.
There is no version of CWM Touch Recovery that is supported for the AT&T One X. You flashed the international version. Fortunately, you can flash TWRP right over it inside Goo Manager.
Be thankful you didn't flash it inside ROM Manager or you could have bricked your phone. I've seen people do it in the past.
ansedve season
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?
in fastboot run this command "fastboot erase cache", then boot into recovery.
DvineLord said:
in fastboot run this command "fastboot erase cache", then boot into recovery.
Click to expand...
Click to collapse
Don't be too concerned with the blah blah in red writing about development version etc. on the boot screen - you get that boot screen when you unlock the bootloader.
mollysue said:
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?
Click to expand...
Click to collapse
What did you do in recovery? Did you flash anything? Does the phone not boot up now?
Thanks guys for all your help. I guess know I technically know what to do to fix things, thanks to you. The only problem that after probably over 100 failed attempts I cannot boot into recovery. I tried all variations of holding the power and volume down button while restarting, rebooting, turning on/off or up/down sideways but it just boots normally every time.
This means I can't use fastboot etc. I guess unlocking the bootloader and voiding the warranty was for nothing
If you know another way to reboot into bootloader other than the hardware buttons method let me know!
Believe it or not, I think you are just performing the button presses incorrectly, if you can't access the bootloader. Bootloader is probably still intact, otherwise the phone would not be working at all.
1) In Settings>Power, make sure "fast boot" is not checked.
2) Then power the phone off fully, but holding the power button until the power menu comes up, and select "Power off". Wait a minute for the phone to power off completely.
3) Hold down the volume down rocker. DO NOT release it until I tell you to later.
4) Press the power button for 3 seconds, then release. DO NOT release the volume down rocker.
5) Once the white bootloader screen shows up, release the volume down rocker.
Alternately, you can do this:
a) With the phone powered on, hold the power button until the capacitive buttons flash (about 5 seconds).
b) The moment the screen goes black, hold down the volume down rocker, (again, DO NOT release it until the bootloader screen comes up) but release the power button.
The timing for this method is a little trickier, if you press the volume down rocker too late, it will boot normally (or safe mode), and too soon, and it just reduces the ringer volume and the phone stays on. But as long as you press and hold volume down the moment the screen goes black, it will work.
---------- Post added at 10:13 AM ---------- Previous post was at 10:11 AM ----------
But also, I would still not recommend trying to boot into recovery until you have installed the TWRP recovery as mentioned previously on this thread, if you have not done so already. There is no CWM Touch Recovery for this phone, so I'm pretty certain you installed in improper recovery on the phone, and recovery will not function at all.
Alternatively, you can go into Goo Manager and select the "Reboot Recovery" option, which should get you into TWRP
Or from command prompt "adb reboot bootloader" so long as you open your prompt from your adb application folder.
Or alternatively skip the middle man: "adb reboot recovery"
I really think your problem lies with your button pressing -- follow instructions on the previous post and you should be home free.
Well I actually eventually managed it! I think the volume button was a bit stuck because it still takes a few tries to boot into bootloader, but eventually I managed it and am in the TWRP menu right now!
I did a little victory dance when it happened. Thanks again!

Pixel Stuck in Bootloop, ADB Unauthorized, Bootloader Unlocked

Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
NZedPred said:
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
Click to expand...
Click to collapse
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely shut off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
mycalculations said:
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely **** off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
Click to expand...
Click to collapse
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
NZedPred said:
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
Click to expand...
Click to collapse
Thank You!!! It didn't work in the bootloop, so I had to let the phone drain its battery and shut itself off, then I was able to enter the bootloader and reinstall lineage. Thanks so much!
mycalculations said:
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Click to expand...
Click to collapse
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
LANDTESTER said:
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
Click to expand...
Click to collapse
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
Oh so after that i can get to bootloader .....hmm let me try thanks bro
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
My bootloader is unlocked but phone not detected on pc only black screen nothing else.... Red light flashes whenever connect to charger

Unbricking HTC U12+

Hey guys - I hope you're doing well.
I recently got an HTC U12+, but wanted to try using a custom ROM due to all of the bloatware . Unfortunately I think I've ended up bricking my device. Here are some things I've since tried:
- Restoring to the backup I made beforehand in TWRP - restore works without any errors, but then just hangs at the boot screen
- Method 1 from this thread (https://forum.xda-developers.com/u12-plus/how-to/collection-htcu-u12-ruu-firmware-t3794664) - TWRP always says the zip files are corrupted for some reason
- Method 3 from that same thread - this actually worked before, but I tried installing a custom ROM again, somehow messed up again, and now this method no longer works as it just hangs at the "HTC" boot screen for eternity
- Both methods in this thread (https://www.theandroidsoul.com/how-to-install-htc-firmware-ruu-and-zip/) - the first one leads to a "failed remote 99 ru unknown fail terrible mishap" error, and for some reason my PC doesn't see my phone when I try the second despite being able to see it in file manager
- Probably many other methods that I've now forgotten
I know this is a whole lot of information, but I'm in desperate need of some help. I typically like to troubleshoot things myself, but I've been trying to fix this for quite some time now and could definitely use another set of (much more experienced) eyes. I greatly appreciate any help you guys can provide.
Thanks.
Flash RUU with SD card method
Download RUU from here(important:check your CID): https://docs.google.com/spreadsheets/d/1wIRrVQawd5rD-t9VKPQ-SdRK20RcJVZhwD7lhmPIK8w/edit#gid=0
1. rename RUU to 2Q55IMG.zip
2. copy zip in the root of your sd card. - external card / not internal - it will not work
3. reboot to download mode,
4. your device will pick up the zip file and flash it.
5.follow on screen instructions and enjoy your RUU(this method erase all your data)
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
EDIT: So I was finally able to get into download mode by waiting until the phone done its 6 minute reboot and then holding power down until it vibrated once, then held volume up until it vibrated again, then let go of the power button, I was then able to choose recovery, download etc.
So I managed to get the file 2Q55IMG.zip to install, it said it installed 100% okay. The phone rebooted and now I'm stuck again just at the white HTC logo and Power by Android down the bottom of the screen.
This time the phone is not automatically rebooting itself and no key combinations will make it reboot. I've tried holding them all in certain combinations for periods of time, the phone will not reboot or turn off.
EDIT 2: So maybe I didn't wait long enough after installing the 2Q55IMG.zip file, I finally got the phone to reboot and now I've got a working phone again. happy days :laugh:
whowhatwhen said:
I'm having an issue with my u12+ where it just continually reboots to a message saying "The boot loader is unlocked and the software integrity cannot be guaranteed. Any data stored on the device maybe available to attackers, do not store sensitive data on this device" and then it shows the white HTC logo that says Powered by Android down the bottom of the screen, it stays like that for about 5 minutes and then reboots and does the same thing over again.
Holding the power down button does nothing, it will not turn off the phone. Holding power and volume down does nothing either. The phone just does this every 6 minutes and reboots and cycle and that's it.
I've tried putting the file 2Q55IMG_IMAGINE_DUGL_O80_SENSE10GP_hTC_Asia_TW_1.53.709.1_Radio_sdm845-000201b-1807311356_release_531499_signed_2_4.zip (renamed to 2Q55IMG.zip) on the root of a 8gb Fat32 formatted SD card, but I just can't get into recovery or download mode.
I've tried holding down all 3 side buttons for minutes, or just the power button, or combination of buttons, they all do nothing to the phone. (it's as tho they are disabled, but sometimes holding a combination of the 3 will make the phone vibrate a little bit, but in no particular time or order)
When the phone is in either state (locked bootloader message or white HTC logo) my Windows 10 PC sees the phone plugged in as a "USB Input Device", not an Android Phone or Android Device. So using ADB or Fastboot commands do not work to it. I've tried to force the driver to the HTC driver but that does not work.
I also tried using the RUU_IMAGINE_UHL_O80_SENSE10GP_NA_Gen_Unlock_1.30.617.2.exe file, but once again it doesn't detect my phone.
Any help would be kindly appreciated.
Cheers!
Click to expand...
Click to collapse
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
fabrizio b92 said:
with the phone off, turn it on,when you feel first vibration
quick release power key and keep push volume down.
Smartphone should boot in bootloader mode.
can you get into this mode with this guide?
Click to expand...
Click to collapse
Cheer mates, issue sorted. I just updated my comment in my post.
Not sure if I'm game enough again now to try and put LeeDrOiD and Magisk on it.

I Flashed My Note 20 Ultra With Recovery.img And Now Its Stuck On Orange State "Bootloader Unlocked" Warning Message!

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

Categories

Resources