After attempting to S-Off the phone yesterday afternoon and failing (it is unlocked), I'm now stuck at the infamous JPbear screen with the green arrow. I've read pretty much every post I can find on recovering from it and still cannot get the phone to boot correctly.
I flashed the boot img for the rom I was running, I created my own PH98 file with the boot image and AmonRa, I've tried to flash a complete rooted Global stock rom, as well as attempting a full flash of the rom I was running. The PH files seem to process correctly but when done I get a messaging it is parsing the file but nothing happens afterwards. On reboot I get the white HTC screen then straight to the black JPBear screen. The phone also does not recognize that it is plugged into my laptop or a wall charger, there are no LED's lit. Without the USB I cannot relock the phone so I cannot flash back to a stock RUU. Fastboot\Min-ADB\Controlbear all fail as the phone is not recognized.
Are there any other things I can try before I give up. I'm not sure if the S-Off attempt may have damaged the USB or not but it definitely does not respond. I do have the extended warranty on the phone but returning it would be a last resort.
I apologize for asking the same questions as many others but I have not been able to find an answer despite searching for most of the night.
controlbear - r
Straight from the troubleshooting page: http://unlimited.io/jbtroubleshooting.htm
shrike1978 said:
controlbear - r
Does not work. I've read the troubleshooting page and tried everything I could find before posting. Controlbear returns an error it cannot find the phone and prompts me to install the drivers and reboot. Fastboot and mini-adb return similar results (phone is not detected).
Thanks for the input.
Click to expand...
Click to collapse
Did you try placing a rom on your sdcard and flashing it in recovery, or just simply placing a signed PH98IMG.zip on your sdcard (meaning the official update)?
brando56894 said:
Did you try placing a rom on your sdcard and flashing it in recovery, or just simply placing a signed PH98IMG.zip on your sdcard (meaning the official update)?
Click to expand...
Click to collapse
I did try a ROM but have no access to recovery. When I select it fro the hboot menu, the screen flashes for a second and then goes back to hboot. I cannot load the stock RUU because the bootloader is unlocked and I have read there is no way to relock it without working USB.
Thanks for the suggestions, I appreciate the imput.
control bear makes a back up before doing the wire trick. just restore the back up?
synisterwolf said:
control bear makes a back up before doing the wire trick. just restore the back up?
Click to expand...
Click to collapse
I tried that but no go. The main issue comes down to not getting the phone recognized by the laptop. The USB port on the phone does not recognize when it is plugged in (either to a PC or the wall charger). Controlbear or other utilities cannot find the phone so I cannot execute any commands. I've been searching for a strictly SD based solution but I am SOL.
Thanks though.
gskuse said:
I tried that but no go. The main issue comes down to not getting the phone recognized by the laptop. The USB port on the phone does not recognize when it is plugged in (either to a PC or the wall charger). Controlbear or other utilities cannot find the phone so I cannot execute any commands. I've been searching for a strictly SD based solution but I am SOL.
Thanks though.
Click to expand...
Click to collapse
Can you see hboot at all?
Sent from my iPhone...
synisterwolf said:
Can you see hboot at all?
Sent from my iPhone...
Click to expand...
Click to collapse
I can boot to hboot by using power and volume keys, but I have no recovery when I select that choice. If I choose Fastboot, it will try to load a PH image if present but when it completes it says "parsing file" and then goes back to the hboot menu.
gskuse said:
I can boot to hboot by using power and volume keys, but I have no recovery when I select that choice. If I choose Fastboot, it will try to load a PH image if present but when it completes it says "parsing file" and then goes back to the hboot menu.
Click to expand...
Click to collapse
if you can get to hboot then you should ruu. it will get your phone back to working order. just make sure you oem lock before doing it if you are s-on
synisterwolf said:
if you can get to hboot then you should ruu. it will get your phone back to working order. just make sure you oem lock before doing it if you are s-on
Click to expand...
Click to collapse
I cannot relock the bootloader without access to to the phone. The laptop does not see the phone when connected to it. I cannot run the relock tool. I think the port actually died. No LED when plugged in to a wall charger or laptop USB cable. I have not been able to locate a way to relock the bootloader using the SD card.
Thanks again.
gskuse said:
I cannot relock the bootloader without access to to the phone. The laptop does not see the phone when connected to it. I cannot run the relock tool. I think the port actually died. No LED when plugged in to a wall charger or laptop USB cable. I have not been able to locate a way to relock the bootloader using the SD card.
Thanks again.
Click to expand...
Click to collapse
idk how to help then. Im sorry. can you charge the phone in any way? if not then i would let it die and send it in as a warranty replacement.
synisterwolf said:
idk how to help then. Im sorry. can you charge the phone in any way? if not then i would let it die and send it in as a warranty replacement.
Click to expand...
Click to collapse
Nah no way to charge the battery. I have a VZW store near me and will take it there for a swap.
I really appreciate your help though.:good:
The only way to recover with the control bear program is to place all the files in its own folder and then CD to that folder and run from there.I had to recover my phone once. Took me a few minutes to wrap my mind around it. Just keep reading until it makes sense.
Related
So, I have CyanogenMod 7.0.3 Stable flashed in my Legend, and it's been working just fine. Until couple days ago when I made some theme changes through Theme Chooser and flashed some theme add-ons. Now the phone is acting just stupidly. It's in a bootloop (sometimes loops in HTC bootscreen, sometimes in the CyanogenMod bootscreen), usb connectivity doesn't work (fastboot usb works, adb/mass storage etc. doesn't). I have tried to wipe the phone and flash that rom/recovery again through fastboot, but fastboot says "remote: not allowed" or something like that. Bootloader works, fastboot works, even recovery works but it's no use 'cause adb driver doesn't recognize the phone.
Please guys, help me. What should I do to get my phone running again? (working CyanogenMod or even a stock without root, I don't care, I just want this thing up and running again)
EDIT: And the weird thing is, that couple times I was able to boot the phone normally using recovery by just sticking the usb cable into the phone. And also, couple times I was able to boot it normally by just using fastboot reboot (I was able to get to the HTC Setup screen and then it would crash and show just black screen with notification bar)
It's possible the you're USB bricked. A quick search of "USB unbrick" should bring the required thread to light (search in development)
TheGrammarFreak said:
It's possible the you're USB bricked. A quick search of "USB unbrick" should bring the required thread to light (search in development)
Click to expand...
Click to collapse
Yeah, I have thought of that! Only problem is that how am I supposed to get the required files (flash_image and .img) to SD card without a way to manage SD card? Can I flash the image using fastboot?
I can't do it inside the phone 'cause I'm in a bootloop and can't boot the phone.
EDIT: Is there a chance to do a wipe and flash a new rom using only fastboot or something?
In theory you can flash without recovery, but only if you're S-OFF. You'll need the ROM in .img format too.
I used a microSD to SDCard reader to transfer the files., they're fairly cheap in high street stores. Or borrow a friends Android phone
TheGrammarFreak said:
In theory you can flash without recovery, but only if you're S-OFF. You'll need the ROM in .img format too.
I used a microSD to SDCard reader to transfer the files., they're fairly cheap in high street stores. Or borrow a friends Android phone
Click to expand...
Click to collapse
Well, am I able to flash those files once they are in the SD card? I mean with S-ON cause I don't have S-OFF?
Or is my phone a complete brick? =( Cause I'm pretty much all out of ideas..
Once you've got the files needed for a USB unbrick on your SD card you'll be fine
if you have recovery access did you try to make apply update from SD card in order to pass in cwm recovery.
if you got a USB brick you can use a multifonction printer to mount your SD on your computer.
So in a nutshell, my problems are:
- My Legend is in a bootloop
- Apparently my phone is USB bricked cause only fastboot works
- I don't have a recovery, when I go manually into recovery (recovery -> POWER + VOL UP) it goes into stock recovery
- And also my phone is S-ON
Could you guys point me into the right direction with this, I really want my phone back working. What should I do?
When you get to the stock recovery, navigate to ans select "flash update.zip from SDcard" That should get you to ClockworkMOD. Once there you'll need to use ADB to push the files required for the USB unbrick procedure to the SDcard (adb push [files-on-pc] /sdcard/) You should no be able to perform the the USB unbrick.
You may need your phone plugged into a PC for it to boot
TheGrammarFreak said:
When you get to the stock recovery, navigate to ans select "flash update.zip from SDcard" That should get you to ClockworkMOD. Once there you'll need to use ADB to push the files required for the USB unbrick procedure to the SDcard (adb push [files-on-pc] /sdcard/) You should no be able to perform the the USB unbrick.
You may need your phone plugged into a PC for it to boot
Click to expand...
Click to collapse
But I'm getting this blue recovery screen with only four options instead of the original green one including option to flash zip. So wtf has happened?
EDIT: In the blue recovery screen it says Can't open cache/recovery/command. And when I choose "apply sdcard:update.zip" it says "signature verification failed" and it aborts the installation.
Fakeflash.
TheGrammarFreak said:
Fakeflash.
Click to expand...
Click to collapse
So I am able to flash roms only using this menu? Am I correct? Just do a wipe and apply update.zip?
Why does it say "verification failed" then?
EDIT: Oh I see, I have to download fake-flash update.zip and apply update.zip takes me to the clockwork recovery? When I put the update.zip to the SD card and apply it, then it should go on with out any "verification failed" errors?
TheGrammarFreak said:
Fakeflash.
Click to expand...
Click to collapse
My main priority is just to get the phone to run normally again, I can worry about the USB Unbrick later. So I just want to do a full wipe and flash Cyanogenmod again. Am I able to do all that is required to run the phone again normally with fakeflash?
Thanks in advance TheGrammarFreak, I really appreciate your help!
The phone won't run normally until you do a USB unbrick.
One of the things that happens with this USB brick is that a flag for advanced debugging gets set. It's a very deep setting, and the setting is read ad the HBOOT level. If this flag is set to on (like it is in a USB brick) the phone will not boot unless it's plugged into a computer. Remember that
In order to get your phone back I believe you will need to plug your phone into the PC and turn it on. It should boot, if not you will need to get to recovery and wipe/reflash (you'll need to do this while plugged into a PC too). Once you have a running system/you're in recovery you can use ADB to push the files needed for a USB unbrick to your SD card.
Assuming you got that far, you should be in a prime position to follow the USB unbrick procedure.
I'm going away tomorrow for a week, and I will not be online at all. If you need more help you will need to get someone else in. That said, I believe that with the information in this thread, the USB unbrick thread, the fakeflash thread and Google you have enough information and help top fix your phone
TheGrammarFreak said:
The phone won't run normally until you do a USB unbrick.
One of the things that happens with this USB brick is that a flag for advanced debugging gets set. It's a very deep setting, and the setting is read ad the HBOOT level. If this flag is set to on (like it is in a USB brick) the phone will not boot unless it's plugged into a computer. Remember that
In order to get your phone back I believe you will need to plug your phone into the PC and turn it on. It should boot, if not you will need to get to recovery and wipe/reflash (you'll need to do this while plugged into a PC too). Once you have a running system/you're in recovery you can use ADB to push the files needed for a USB unbrick to your SD card.
Assuming you got that far, you should be in a prime position to follow the USB unbrick procedure.
I'm going away tomorrow for a week, and I will not be online at all. If you need more help you will need to get someone else in. That said, I believe that with the information in this thread, the USB unbrick thread, the fakeflash thread and Google you have enough information and help top fix your phone
Click to expand...
Click to collapse
Legend is up and running again! Thank you so much TheGrammarFreak!
Same problem here, but slightly different. He doesn't recognize my SD card (tried different ones) anymore ... out of the blue ... so how can I unbrick ??
http://forum.xda-developers.com/showthread.php?t=751265
follow this guide, helped me a lot.
you'll need root access.
//Header information
***UNLOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
eMMC-boot
Hey guys, I recently acquired an EVO 3D in a trade deal and even though I don't want it (I plan on selling it but the cash deal + EVO 3D was worthy), I ended up being hellbent on rooting it last night. Success. Great, I threw Cyanogenmod7 on there and realized I'll have to undo the root/ROM to sell it later. I used what I believe is referred to as the REVOLUTIONARY method (using HTCDev.com, some terminal commands on my Mac, etc.)
Anyhow, didn't think it would be hard to undo what I did and I guess I was wrong. Let me tell you what I've tried so far.
I've tried using the PG86IMG.zip flash and nothing. No option (VOL UP or VOL DOWN) to even TRY installing it. Just quickly flashes the green text "No Image!" under each category (it goes too fast for me to read it) and I'm back at the boot menu. I've tried using different copies of the PG86IMG.zip with the same results (latest site acquired from: Goo-inside me, or something like that).
I've also tried using the RUU*.exe method on a Windows 7 machine. I've installed the drivers, everything checks out just fine until it actually tried to update the ROM. What happens here is that the phone reboots (as expected) and though the splash screen is different (black background with silver/gray hTc logo, semi-reflected) from the usual splash screen (white background with hTc in green), nothing happens. The software on the Windows 7 machine says "Waiting for bootloader" - which never shows up. Then it quickly gives me an error stating that the USB cable between the PC and the phone needs to be checked. Of course, there's no disconnect anywhere in the cables.
Please help! I planned on selling this device but if it's stuck in Cyanogenmod7, especially with no Google apps (couldn't get Gapps*.zip to work but whatever, not really concerned about that right now), there's no way I could sell this thing. I'm fairly knowledgeable in the basics of these matters as I have a rooted EVO 4G as well.
Anyone wanna buy an EVO 3D? HAHA
you could always flash a stock rooted rom .
You've gotta relock through adb before running the RUU.exe; then it'll work.
Hit the thanks if I helped
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
zer0xity said:
Here's another problem: I can't get back into Clockwork Mod Recovery (so I don't know how to flash another ROM on there). If I hold VOL DOWN while powering up, it starts automatically loading PG86IMG.zip. Then I get the options FASTBOOT, RECOVERY, FACTORY RESET, SIM LOCK, and IMAGE CRC.
Trying to enter recovery reboots to the splash screen and it gets stuck there.
How would I lock it using ADB?
Click to expand...
Click to collapse
It's because of the pg86img.zip you can delete/move it away from the root of your sd card and get back into recovery... but you shouldn't need to, follow these steps:
1) Turn off phone
2) Hold power+vol down
3) Choose fastboot
4) Plug into your PC if you're not already
5) When you see FASTBOOT USB on the phone screen go back to your command prompt where you have your adb.exe, fastboot.exe, etc.
6) Type: " fastboot oem lock "
7) Aaaand you're done w/ the relocking go crazy and run your RUU.exe, don't reboot the phone or anything just run your RUU while your phone's still in HBOOT.
Edit: Oh, the adb I was talking about would kind of make everything easier; in command prompt: adb reboot bootloader AND THEN fastboot oem lock
Two steps, mhm.
I'm on it! Standby...
Okay, the adb stuff - can I do that from terminal in Mac? I tried doing it while in the appropriate folder where all that adb stuff is and I typed: adb reboot bootloader (ERROR: command not found), then I tried just: reboot bootloader (not permitted). I did try: ./fastboot-mac oem lock (successful. header now says *** RELOCKED ***).
Tried the RUU*.exe stuff on the Windows machine while in that state and again an alleged problem with the USB connection...
Sounds like we're close?
BAM! Got it. You put me on the right track with that last post. RUU still wouldn't do the reversion even though I had some drivers installed on Windows so I had to find some other drivers (some HTC3*.exe file, 13MB) and ended up running those for it to recognize the phone.
+1 to you, sir. Thank you so much!
Glad it all turned out well.
I need some help.
I'm trying to recover a friend's Evo 3d. He tried to flash a different ROM on it, and messed it up.
I'm on Windows 7 32bit. The phone is the Sprint EVO 3D (CDMA). HBOOT is 1.50.0000 S-ON
The device is not bootlooping. I get a blank screen after the HTC logo. I don't have access to USB debugging. I can get into recovery to try to flash a different image but to no avail - I get the same screen every time. I decided to get it back to stock but I can't relock it. ADB doesn't recognize the device and the device is very much in the device manager (proper drivers and all). I would love any advice.
Thank you.
my fix method
pixel4e said:
I need some help.
I'm trying to recover a friend's Evo 3d. He tried to flash a different ROM on it, and messed it up.
I'm on Windows 7 32bit. The phone is the Sprint EVO 3D (CDMA). HBOOT is 1.50.0000 S-ON
The device is not bootlooping. I get a blank screen after the HTC logo. I don't have access to USB debugging. I can get into recovery to try to flash a different image but to no avail - I get the same screen every time. I decided to get it back to stock but I can't relock it. ADB doesn't recognize the device and the device is very much in the device manager (proper drivers and all). I would love any advice.
Thank you.
Click to expand...
Click to collapse
You can boot into fastboot by holding vol-down and power from off. Then plug in USB and run fastboot(in the same folder as adb i think) with these args
Code:
boot PATH_TO_RECOVERY.IMG
and then flash a ROM. LightsOut is a good ROM. Hope I help.
Download the RUU and get into fastboot USB. and run it. That'll reset your firmware and radios and everything.
IF it has 1.50 s-on than it's still on Gingerbread, You need to update your radios and firmware, With the 2.89 RUU
Then it'll be on ICS, and you can unlock the bootloader
Then get s-off, You shouldn't be flashing anything with s-on lol.
(You can, but get s-off it's 1 more hour of work once you get it booting)
I must have been using a faulty cable or USB port, I tried it the next day with my girlfriend's Samsung cable and "fastboot oem lock" worked immediately. Ran RUU like a champ and it is alive and working now.
pixel4e said:
I must have been using a faulty cable or USB port, I tried it the next day with my girlfriend's Samsung cable and "fastboot oem lock" worked immediately. Ran RUU like a champ and it is alive and working now.
Click to expand...
Click to collapse
good deal
Here is the quick rundown. I have a stock rom, rooted, att one. It has been sitting a couple of weeks. The battery was dead so I charge it up with the phone off. It does fine. The next day, I turn it on. I do a full wipe on it as the plan is to give it to my wife. We go through the set up, everything is normal, blah blah blah. Now it comes to charge the phone. We plug it in to the standard charger. It won't charge. No light, nothing under power in settings. I plug my One into the charger and it is fine. So we go to a computer next. The computer doesn't see it is plugged in. No sound, nothing in device manager nothing. I plug mine in and it is fine. So now I go to recovery and try to wipe the cache and usual stuff. Still nothing. From here I can and download the stock RUU seeing as I can't even get a file on there to flash through recovery, I figure I'll start over. I go through the ruu with 46% battery and it stops on an unknown error. Fastboot connects through USB no problem. From here I try to erase all the partitions and they all say FAILED (remote: not allowed).
What are my options at this point?
Are you flashing the RUU with the exe in windows? If so have you tried flashing from RUU mode with the /fastboot oem rebootRUU?
Yes. It stays on the black HTC screen with no changes on it. That is when I get the unknown error.
Would getting a system.img and a boot.img file maybe do the trick? I can't seem to find one for this phone. The One X pops up in all of the searches.
To be more specific, it is error 155 which according to the manual, that means that I am trying to flash the wrong size rom to the wrong device. I am using RUU_M7_UL_JB_50_Cingular.exe on a PN07120 device. It still had the stock rom, only the bootloader was unlocked and it was rooted.
Here's a rom.zip RUU that you can flash it from fastboot RUU mode. It will replace your system and boot. Its take from the same RUU_M7_UL_JB_50_Cingular_1.26.502.12.exe file
The commands when in fastboot usb mode are:
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
---------- Post added at 07:23 AM ---------- Previous post was at 07:13 AM ----------
Sorry, here's the link https://mega.co.nz/#!yNQlFJKb!aTXDHQRG0mcv3htWOHjnYxpExjB5dT7HdkuNxCtSVyo
Unless soff'd you didnt mention relocking the bootloader before flashing the ruu.
whitehooptie said:
Here is the quick rundown. I have a stock rom, rooted, att one. It has been sitting a couple of weeks. The battery was dead so I charge it up with the phone off. It does fine. The next day, I turn it on. I do a full wipe on it as the plan is to give it to my wife. We go through the set up, everything is normal, blah blah blah. Now it comes to charge the phone. We plug it in to the standard charger. It won't charge. No light, nothing under power in settings. I plug my One into the charger and it is fine. So we go to a computer next. The computer doesn't see it is plugged in. No sound, nothing in device manager nothing. I plug mine in and it is fine. So now I go to recovery and try to wipe the cache and usual stuff. Still nothing. From here I can and download the stock RUU seeing as I can't even get a file on there to flash through recovery, I figure I'll start over. I go through the ruu with 46% battery and it stops on an unknown error. Fastboot connects through USB no problem. From here I try to erase all the partitions and they all say FAILED (remote: not allowed).
What are my options at this point?
Click to expand...
Click to collapse
I'm a dumbass. I didn't relock the bootloader and I'd be willing to get that is where my problem stems from. I'll have to get back home later and give that a shot, but I'd be willing to bet that is my issue.
More than likely the issue...
this worked but what about "relocked"
Is there an way to get it to say "locked" now that we're unrooted? I saw moonshine but that takes root and the gives s-off. Any other way?
redknite said:
Is there an way to get it to say "locked" now that we're unrooted? I saw moonshine but that takes root and the gives s-off. Any other way?
Click to expand...
Click to collapse
Use revone...
Sent from my HTC One using xda premium
Yup. That was it. Now that it is locked, it is a-ok and on the stock rom. But now I have another problem. It is the original problem of not charging or being recognized while the phone is loaded up. I'll post a new thread.
whitehooptie said:
Yup. That was it. Now that it is locked, it is a-ok and on the stock rom. But now I have another problem. It is the original problem of not charging or being recognized while the phone is loaded up. I'll post a new thread.
Click to expand...
Click to collapse
I had a similar issue with my nexus 7 tablet. It wouldn't charge after letting the battery drain all the way till it shut off. The computer would still recognize when it was connected but still wouldn't charge. It turned out to be the battery. Don't know if this relates to ur issue but its a possibly...
Sent from my HTC One using xda premium
Alright so my issue is I flashed an ics rom on my evo LTE but accidentally with the wrong firmware. When the update was just about done, the screen went black. No charge light when plugged into a charger and the device will not power on, or do anything(tried button combinations). However when I plug it into my computer,device manager sees my phone as “My HTC”. So it seems to have a connection but it doesn’t do anything to the phone. Fix possibly?
Sorry for asking such a basic question guys. New to the forums but definitely not new to flashing roms. This problem just confuses me to death.
Can you supply as much info as possible.
QUOTE=bigdaddy619;45718286]Can you supply as much info as possible.[/QUOTE]
Yes I can my friend. Of course, I got S-OFF with moonshine. Never had a problem there. Rooted also with moonshine as well. Flashed a lot of different jelly bean roms (CM, Meanbean) to see which one best suited me. Well after awhile I decided to give one of the ics roms a shot but the firmware version on my evo was for jelly bean only, not ice cream sandwich. Just as the flash of the ics rom was about finished, the screen went black. (Battery was above 50%). I tried every button combination, but nothing worked. Tried connecting it to a charger and the orange charge light wouldn't even come on. I even left it on the charger overnight, but no dice. So the phone is totally unresponsive to everything. One thing I did notice however is that when I tried connecting the phone to the computer, my computer makes the connection noise when it finds a
Usb device. Checked my device manager on windows and my phone shows up as "My HTC". So it seems as my computer has some type of connection to the phone. With that being said, would there be some way to use some unbricking software or any other way to unbrick my phone? (From what I see, I think the bootloader may be corrupted)
Since you can hear USB connection, I wonder if running fastboot devices from CMD would yield any results. Though I suspect you'd probably have to be booted to fastboot USB to see.
Sent from my EVO using XDA Premium 4 mobile app
scottspa74 said:
Since you can hear USB connection, I wonder if running fastboot devices from CMD would yield any results. Though I suspect you'd probably have to be booted to fastboot USB to see.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would you know of what commands may work for my device? Cmd is new to me, or well at least when it comes to sending commands to phones lol.
Click the link in my sig. There is a guide for setting up ADB as well as commands in it.
FinZ28 said:
Click the link in my sig. There is a guide for setting up ADB as well as commands in it.
Click to expand...
Click to collapse
Thank you much sir. Here's what I found out. When I type the command "adb devices", nothing shows up. When I type in "fastboot devices" here is what it says:C:\Users\lisa\Desktop>fastboot devices
C:\Users\lisa\Desktop>fastboot devices
t♥☻ fastboot
guessing that's not a serial number, as it should be, but it recognizes my device as a fastboot device. Is there any hope of fixing this paperweight?
ADB commands only work when the phone is booted to the ROM, whereas Fastboot commands only work in the bootloader when connected via Fastboot USB mode.
Can you get to the bootloader at all?
FinZ28 said:
ADB commands only work when the phone is booted to the ROM, whereas Fastboot commands only work in the bootloader when connected via Fastboot USB mode.
Can you get to the bootloader at all?
Click to expand...
Click to collapse
The only way I can get to the bootloader is by using the command prompt. Otherwise, my phone remains inoperable.
What happens when you select the recovery option in the bootloader?
Meaning that fastboot shows my device is connected but I cant access it on my phone.
rwhittaker13 said:
Meaning that fastboot shows my device is connected but I cant access it on my phone.
Click to expand...
Click to collapse
Ah.
HTC bricked
I have the same problem with my lte. I wanted to boot into recovery mode and that was the end of my phone. I can't turn it back on, but when i connect it to my computer it makes the connection sound and thats it, my phone is still dark.
stasikbest said:
I have the same problem with my lte. I wanted to boot into recovery mode and that was the end of my phone. I can't turn it back on, but when i connect it to my computer it makes the connection sound and thats it, my phone is still dark.
Click to expand...
Click to collapse
What did you do prior to booting into recovery? Also, when you plug your phone into your computer, what does your device show up as?
Sent from my HTC EVO 4G LTE
Bricked Phone Stuck in Fastboot
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
juanrocklin said:
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
Click to expand...
Click to collapse
Use Fastboot to fastboot flash a recovery to your phone
Sent from my SPH-L710 using Tapatalk 2
juanrocklin said:
My phone is bricked and I can only get to fastboot usb. I also lost TWRP, trying to run RUU for radio. Current radio is 1.12.11.1210 and looks like there is not a full RUU for this. SD Card also bad, so couldn't get my Backup. Is there a way that I can sideload or push TWRP to the phone? I want to re-flash a custom ROM in hopes that this will fix issue. I have flashed CM 10 in past, so I figure all I need to do is put CM on sd card and then I can flash from there.
Click to expand...
Click to collapse
That's not a brick. Do as instructed above and install TWRP via fastboot.
Sent from my HTC EVO 4G LTE
Thanks
FinZ28 said:
That's not a brick. Do as instructed above and install TWRP via fastboot.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Bammm! Worked like a charm. Back in business. Thanks much!