Is my phone bricked beyond saving? (HTC One SV, tried to install CyanogenMod)
- Okay, this all happened because I tried to install CyanogenMod without taking into consideration the fact that I'm using the SV version, of which there does not seem to be any easy way to install CyanogenMod on.
My provider is Boost Mobile if that's important.
The first step I took was to unlock the bootloader, which was successful (I did use the HTCDev website, submit my identifier token, and it definitely worked).
The real trouble was when I tried flashing my recovery and boot .img's using the files in this link (for the HTC One S): How to Install CyanogenMod on the HTC One S ("ville") - CyanogenMod
Terrible mistake, I know. I think my phone is bricked, but I'm not 100% sure because this is the first time I've tampered with any phone on this level. The only comparable mistake was when I accidentally formatted my hard drive when I tried installing Arch on my desktop, two years ago.
Right now, my phone won't start properly. When I do a normal bootup, by simply holding down the power button, I get treated to the HTC logo followed by a blank blackish-grey screen. I have to remove the battery to exit it. I can access fastboot, but when I attempt to access recovery I get taken to a perpetual load screen with an HTC logo and "Entering recovery mode..." on top of it. I have to remove my battery at this point because it never goes beyond that screen.
The other trouble is that while I seem to be able to access my phone through a USB cable, and apparently detect it using the "fastboot devices" command, the device itself doesn't seem to show up on Windows (as C525c, like it did before). I'm not sure if this has to do with me screwing up my boot and recovery .img's or my USB drivers.
Is it possible to at least bring my phone back to its original state? I hear that there is a difference between "soft-bricking" and "hard-bricking," so I suspect my case is the former. I'd rather not spend any money on a new phone unless there literally is no other way, so I need to know how to restore it to where I can at least make calls and keep contacts.06-20-2014 10:47 PMLike 0 - wizzrahRetired AmbassadorOkay, this all happened because I tried to install CyanogenMod without taking into consideration the fact that I'm using the SV version, of which there does not seem to be any easy way to install CyanogenMod on.
My provider is Boost Mobile if that's important.
The first step I took was to unlock the bootloader, which was successful (I did use the HTCDev website, submit my identifier token, and it definitely worked).
The real trouble was when I tried flashing my recovery and boot .img's using the files in this link (for the HTC One S): How to Install CyanogenMod on the HTC One S ("ville") - CyanogenMod
Terrible mistake, I know. I think my phone is bricked, but I'm not 100% sure because this is the first time I've tampered with any phone on this level. The only comparable mistake was when I accidentally formatted my hard drive when I tried installing Arch on my desktop, two years ago.
Right now, my phone won't start properly. When I do a normal bootup, by simply holding down the power button, I get treated to the HTC logo followed by a blank blackish-grey screen. I have to remove the battery to exit it. I can access fastboot, but when I attempt to access recovery I get taken to a perpetual load screen with an HTC logo and "Entering recovery mode..." on top of it. I have to remove my battery at this point because it never goes beyond that screen.
The other trouble is that while I seem to be able to access my phone through a USB cable, and apparently detect it using the "fastboot devices" command, the device itself doesn't seem to show up on Windows (as C525c, like it did before). I'm not sure if this has to do with me screwing up my boot and recovery .img's or my USB drivers.
Is it possible to at least bring my phone back to its original state? I hear that there is a difference between "soft-bricking" and "hard-bricking," so I suspect my case is the former. I'd rather not spend any money on a new phone unless there literally is no other way, so I need to know how to restore it to where I can at least make calls and keep contacts.
Let's get started with the basics. The recovery. Do you have the recovery file? If so, we need to flash it.
Are you familiar with the bootloader menu as well as fastboot? You'll need to know these.
Access the bootloader menu (power off the phone, then hold power +vol up button).
Select fastboot from the menu.
Wait until you see "fastboot" in red text on the phone's screen.
Connect it to the PC.
See if it changes from "fastboot" to "fastboot usb"
Let me know once you get to this point.06-20-2014 11:14 PMLike 0 - Hi, this is the OP. I am certainly able to see it change from "fastboot" to "fastboot-usb." In fact, my entire afternoon was spent in a tedious cycle of removing the battery -- reinserting the battery -- rebooting to fastboot, plugging it using my USB -- try to experiment with various options (even checked the Image CRC or whatever it was called) -- get stuck on a perpetual load screen -- remove battery -- etc.
The recovery file? I'm not sure if you mean the recovery file that already comes with the phone (does something like that exist?), or the one I tried to flash in order to install CyanogenMod, or the one I took from this one thread on the XDA forums that was meant to be some sort of Jelly Bean clone (as far as I can recall, because I'm on my laptop right now, and the stuff for reference is on my desktop computer which I can't access at the moment). Sorry if my tone comes across as sarcastic, because I'm really not sure, and I'm completely serious about fixing this (tone can get lost through the written word if you're not careful).06-20-2014 11:27 PMLike 0 - bump
(I do know how to get to the point where it says fastboot usb, but I don't know what I can do next.06-21-2014 08:25 AMLike 0 - bump
In a thread on the XDA forums where I first posted this, someone recommended that I flash my recovery from a file from here:
[Recovery] TWRP Recovery 2.7.0.x (recommended for 4.2.2) - Post #2 - XDA
Original Thread: I've made a few extremely rash decisions, and I'm not sure if I can fix this. - xda-developers06-21-2014 11:20 AMLike 0 -
- Okay, I just flashed my recovery from a file in that link, and I'm finally able to boot into recovery. I'm not sure what to do next.
My options are: Install, Wipe, Backup, Restore, Mount, Settings, Advanced, Reboot.06-21-2014 11:43 AMLike 0 - Okay, here's the thing right now, when I check all the boxes and press "Mount," Windows 7 tells me that I need to "format the disk in drive E: before you can use it." I don't think I should do this because it would wipe out what I have on my phone right now. Is there any workaround?06-21-2014 12:48 PMLike 0
- wizzrahRetired AmbassadorOkay, here's the thing right now, when I check all the boxes and press "Mount," Windows 7 tells me that I need to "format the disk in drive E: before you can use it." I don't think I should do this because it would wipe out what I have on my phone right now. Is there any workaround?06-21-2014 12:52 PMLike 0
- Quick question: do I format it as NTFS or FAT32?
edit: because I recall having to format stuff to NTFS before, for it to work. That had to do with Linux though, with the formats associated with that.06-21-2014 12:54 PMLike 0 - wizzrahRetired Ambassador[Q] Is the memory of the One S FAT32 or NTFS? - xda-developers
You might want to look into this. I might have been wrong about losing data, but I'm not sure what data you would be losing.
Anyways to sum it up, NTFS allows transfer for big files above 4GB. Fat32 only allows files up to 4GB.
I believe I have my HTC One XL formatted as Fat32, so that should be sufficient.06-21-2014 01:00 PMLike 0 - Okay, after doing a quick Google search, I just formatted it to FAT32, and I'm able to see it on Windows now. I'm not sure what to do next though. Do I need to flash something again? I just want to get a working system from which I can do more later on.06-21-2014 01:01 PMLike 0
- wizzrahRetired Ambassador
Check something out from there. Or do you have something already?
Also, could you do me a favor and click "reply with quote."
It notifies me when you responded. Thanks.06-21-2014 01:06 PMLike 0 - Yep! Now you can drag in a ROM! One SV Android Development - xda-developers
Check something out from there. Or do you have something already?
Also, could you do me a favor and click "reply with quote."
It notifies me when you responded. Thanks.06-21-2014 01:10 PMLike 0 - wizzrahRetired AmbassadorI did get a couple of files from this thread already : [HTC One SV] Stock boot.img | recovery.img | radio.img - xda-developers06-21-2014 01:17 PMLike 0
-
-
- Okay, I finished saving the zip file. What do I do with it? I see on another site which instructs users to go to the Install section of their Recovery, but I'm not sure if this applies to me. I'd have to unmount my phone to get to my Install section (I think)
How to Flash a ROM to Your Android Phone06-21-2014 01:30 PMLike 0 - wizzrahRetired Ambassador
- - - Updated - - -
Okay, I finished saving the zip file. What do I do with it? I see on another site which instructs users to go to the Install section of their Recovery, but I'm not sure if this applies to me. I'd have to unmount my phone to get to my Install section (I think)
How to Flash a ROM to Your Android PhoneIt's real easy.
06-21-2014 01:32 PMLike 0 -
Edit: also, thank you . I really appreciate your help. =)06-21-2014 01:36 PMLike 0 - wizzrahRetired AmbassadorJust saw what you were talking about. I see what you mean about the loading screen. I'm trying to find a compatible ROM. Could you do me a favor and unmount, then boot into bootlaoder? Look at the very top of the screen. What does it say for the codename? K2_UL, K2_U, K2_CL, etc.06-21-2014 01:43 PMLike 0
- Some of the ROM threads have a disclaimer that I should download to hboot 2.0.0 if I have hboot 2.2.1. I guess I need to check my hboot version. Do I need to do anything before rebooting (in order to get into hboot to see what my version is)06-21-2014 01:46 PMLike 0
- Just saw what you were talking about. I see what you mean about the loading screen. I'm trying to find a compatible ROM. Could you do me a favor and unmount, then boot into bootlaoder? Look at the very top of the screen. What does it say for the codename? K2_UL, K2_U, K2_CL, etc.
I see that my HBOOT is 2.21.00006-21-2014 01:50 PMLike 0 - Just saw what you were talking about. I see what you mean about the loading screen. I'm trying to find a compatible ROM. Could you do me a favor and unmount, then boot into bootlaoder? Look at the very top of the screen. What does it say for the codename? K2_UL, K2_U, K2_CL, etc.06-21-2014 02:27 PMLike 0
- Forum
- Get Help & Give Help!
- Ask a Question
Is my phone bricked beyond saving? (HTC One SV, tried to install CyanogenMod)
« andriod system recovery
|
S3- charging problems. Recognising being plugged in but not holding any charge. »
Similar Threads
-
Unknown error code during application installed -110
By AC Question in forum Ask a QuestionReplies: 6Last Post: 12-08-2015, 05:03 AM -
Battery Life Horrible since updating to Kit Kat
By Eddster in forum Samsung Galaxy Note 10.1 (2014)Replies: 4Last Post: 06-23-2014, 03:31 PM -
Can I copy old phone app info to a new phone?
By Right_2_B3ar in forum Ask a QuestionReplies: 3Last Post: 06-21-2014, 12:42 PM -
App to auto unlock, pin enabled lock screen
By gabrielxavila in forum Samsung Galaxy S5Replies: 4Last Post: 06-21-2014, 04:16 AM -
Case issues; auto answering phone calls
By AC Question in forum Ask a QuestionReplies: 2Last Post: 06-20-2014, 11:17 PM
LINK TO POST COPIED TO CLIPBOARD