Unable to get out of the bootloader - HTC One SV

Hi guys,
so im having an issue where im unable to exit the bootloader. i will try and provide as much info as possible.
* selecting recovery takes me back to the bootloader after it restarts itself, When i do manage to restart the phone the HTC splash screen reads ,
" HTC one stuck on "this build is for development purposes only. Do not distribute outside of HTC without HTC's written permission. Failure to comply may lead to legal action"
* whilst the bootloader is open , if i connect the phone to my computer, my computer makes the 'usb connected' sound, but shows no device to explore & the bootloader with acknowledge its connected to USB.
* The ONLY way the phone will turn on is if I remove the batter for 1 minute. put the battery in and then plug in a charger - the phone will start up by itself automatically
the bootloader reads
*tampered*
*locked*
*security warning*
K!_UL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.18.40A.00.05
OpenDSP-v13.2.0268.0620
eMMC-boot
Mar 14 2013 , 22:10:43:-1
I think i may have flashed the device years ago, likely using a method that doesn't require the phone to be unlocked. I remember the screen broke on this device years back, but it would still boot up and i could touch type my password etc - i just had limited visibility of the screen. I was last able to do this about 8 months ago. A week ago i decided to dig the phone, when the phone turned on i noticed it wouldnt respond to touches, so thought it was stuck on a charging screen or something. Then I changed the screen and discovered it was stuck in bootloader
Any ideas? If I can do anything without completely deleting the personal data that would be good, if I have to lose it thats fine - the phone is the only backup phone i have atm since my main device broke
thanks

Related

[Q] Phone not switching on

Hi,every time my phone switches off and I try and switch it back on it just goes straight to the fastboot screen. Pressing the reboot just brings me back here. Doing a factory reset does exactly the same thing, and does not reset. It has been doing it for a while now, and if i reboot enough times it eventually reboots normally, and functions fine until I run out of battery or something, then it takes ages to get it up and running again.
I haven't unlocked it in any way, it's completely stock. Htc are trying o get me to install an update, but as soon as it starts to install it switches off, and goes straight to the fastboot screen.
It's driving me mad, and is obviously just outside the warranty period.
Any help or advice on what to try would be much appreciated.
Cheers, Tom
I had the same problem a year ago but was still on warranty then, so I sent it in. When they returned it to me, there was no sign of them having opened up the phone so I guess it can be fixed software-side, but I'm not sure. You could probably try flashing a fitting RUU in fastboot and see if that fixes your problem (I guess that was what HTC has done when my device showed a similar behavior). Just be sure you're on the right version, as KitKat e.g. has a new partition layout and this could lead to problems with your phone not booting up properly.
Is your phone unbranded? What version are you currently on (Android, hboot)?

Is this a hard-brick?

I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben
Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Assistance with (partial)Bootloop and Locked Bootloader.

Hey there forums.
I've been an active browser of XDA but never really created an account but I've done so to have assistance with a particular situation with my device.
So the other week, i had spent 150 dollars on a Sony Xperia XA F3115 from Vodafone, Australia and it turns out that the bootloader was locked because of Vodafone and i wasn't going to pay 50 dollars to unlock it. I alternated and browsed the internet (Mostly XDA but other sources aswell) to figure out if there were any methods of bypassing this, whether it be easy or not - I was willing to try anything that seemed like it had a chance to work, without a 100% failure rate. Reading responses to particular methods, i was drawn into one method of just reflashing the stock firmware onto the device and then rooting, flashing and doing everything from there (as the device was no longer locked by Vodafone at that point).
I have completed this task as of this morning, and the device booted successfully. As soon as i unlocked my device, i had received the general android setup window but half way through, i got spammed with "Name has stopped responding" countless times to the point where the phone was literally unusable, it would just pop up again right after closing it - So i decided to restart the device. This was probably a big mistake, it booted fine but it said "Android is updating" and had the whole "Applications updating 100 out of 255" stuff happening. Then it booted to the lock screen, which i had previously setup before i flashed the device which didn't really surprise me too much.
Then it rebooted. Now every single time i boot the device, it reboots to the "Optimizing apps blah out of blah" and then will reboot upon the notification bar popping up, but no lock screen. I decided that my best cause of action was to download another firmware and try that one instead, but I'm unable to boot my device into bootloader mode as it's impossible to happen. I turn off my device, plug it in and hold the volume down button but it refuses to work anymore.
Now that the situation has been explained, I'd really like your help to see if i can have this resolved. I'm baffled as to why Vodafone even locked it to begin with, since the phone was prepaid and had nothing to do with any sort of plans - nor was it even available as a plan. I don't have the money to buy a new phone, and they have already denied me a refund. I need this phone for work and the mistakes i made were stupid - Please, i need assistance. You're all hopefully more tech savvy than i am in the field of mobile phones.

HTC U11 : Your phone is encrypted message

Hi,
For some weird reason when i turned my HTC U11 on this time they show this message before start up:
Your phone is encrypted.
To ecrypt your phone, enter your lock spattern.
30 attempts reamin before device data is deleted.
No matter how many times i enter the right pattern it wouldn't accept it. I has just set the lock screen a couple of minutes before the phone got turned off. So when I check my phone on the linked google account it still says no lock pattern detected.
Now I am down to only 3 attempts and I do not want to lose my device data! Please help!!
Even USB Connection not working
I tried connecting the phone to my PC as well, but the device doesnt show up. Probably because the phone is not completely turned on yet ( i cant access anything on my phone

Recovering data through USB

Today my phone felt down totally flat. The screen hits the floor directly.
It carries a protector above the screen, and apparently it is the only part that broke down
The screen seems to be in perfect status.
But the problem is screen is not working. None light is shown, and no reaction is performed.
If I touch the power button during 20s, the phone vibrates and it seems to be restarted.
When I connect the charger, the led works fine. Although no sound is played.
I would like to repair the phone, but at least (and this is important) I need to download all the data to the PC.
Question: is there any way to access to the data in the phone without having the screen available?
PHONE: MI9
OS: MIUI12.5
Yolco said:
Today my phone felt down totally flat. The screen hits the floor directly.
It carries a protector above the screen, and apparently it is the only part that broke down
The screen seems to be in perfect status.
But the problem is screen is not working. None light is shown, and no reaction is performed.
If I touch the power button during 20s, the phone vibrates and it seems to be restarted.
When I connect the charger, the led works fine. Although no sound is played.
I would like to repair the phone, but at least (and this is important) I need to download all the data to the PC.
Question: is there any way to access to the data in the phone without having the screen available?
PHONE: MI9
OS: MIUI12.5
Click to expand...
Click to collapse
If you did not USB debugging enabled in system settings before the screen broke, you will not be able retrieve your data. Now that your screen is broken, there is no way for you to enable USB debugging in order to retrieve your data.
Your options are:
1) repair the screen so you can retrieve your data.
2) forget about your data and get a new device.
Live and learn. I keep USB debugging enabled on all my devices for this very reason.
I found that I can retrieved my data thanks to custom recovery. I had a bit of lucky because with adb, data can be retrieved trhough custom recovery.
Usually, I have USB debugging activated but this time it was not activated as from last ROM update it is deactivated by default.
Now, I will deassembly the phone just to understand which is the root cause as touch sensor is working fine. So I need to understand if the problem comes from the screen or in the worst-case from connectors or PCB. In this last case I would need to get a new device, and I would like to keep this one for a few more time, even when there is no more OS update.
Yolco said:
I found that I can retrieved my data thanks to custom recovery. I had a bit of lucky because with adb, data can be retrieved trhough custom recovery.
Usually, I have USB debugging activated but this time it was not activated as from last ROM update it is deactivated by default.
Now, I will deassembly the phone just to understand which is the root cause as touch sensor is working fine. So I need to understand if the problem comes from the screen or in the worst-case from connectors or PCB. In this last case I would need to get a new device, and I would like to keep this one for a few more time, even when there is no more OS update.
Click to expand...
Click to collapse
I was going to suggest that but wasn't sure you would actually be able to install it or even if a custom recovery existed for your device since you didn't post what model you have. Also, if you had needed to unlock your bootloader to flash a custom recovery, unlocking the bootloader would have wiped your data.
Yes, you were lucky, most users in this condition are screwed out of recovering their data.

Categories

Resources