[Q] Bricked?? - AT&T, Rogers HTC One X, Telstra One XL

OK. I have the ATT htc one x. I was attempting to install Cyanogenmod 9. I unlocked the bootloader. Rooted the phone. I loaded twrp. This is where things get fuzzy. For some reason I was not able to load the .zip file of cyanogen. Then when I restarted the device it went into a kind of loop. Twrp was gone and I could and can go into the boot loader but the os is gone and it just shuts down if I attempt to go into recovery or reboot. Also, to make things worse, the phone is no longer being recognized by my computer with adb. Is my phone bricked or is there something I can do to set things right?!?!?!?!

did you install the twrp with working usb mount?

No. I installed it using goomanager. I wasn't able to install twrp or CWM using usb mount.

Is fastboot usb working in the bootloader (It will say fastboot usb in the bootloader screen while your device is plugged in)? You may have to ruu if both recovery and the os is not loading, but you'll have to relock your oem bootloader first using fastboot if possible. Otherwise I wouldn't know of any other fix without recovery working, unless someone on here knows of another way. This has happened to me once and I had to just ruu and start everything over again.

No fastboot usb is not working is there any way I can restore the ability to access it?
I have nothing left on it anymore so restoring is no problem if I can get access to my device.
[solved]
just downloaded drivers and moved them to htc driver folder in program files for anyone who was wondering.

glad to hear. was actually just about to ask whether you had the drivers installed correctly. Hope everything works out from there.

Related

Ploblem with bootloader

Hi guys, i have a question:
wiht FW 4.2.1 if i reboot on bootloader screen, and in the top left of the screen, you will see a sign that says: Key drive not found .... why?
could you help me?
stevtec86 said:
Hi guys, i have a question:
wiht FW 4.2.1 if i reboot on bootloader screen, and in the top left of the screen, you will see a sign that says: Key drive not found .... why?
could you help me?
Click to expand...
Click to collapse
Same here & a few other people I have asked also have this.
Not sure but I think everyone on 4.2.1 bootloader now has this "Key driver not found...Booting os..." message in the top left corner of bootloader.
I don't know what it means though.
Not only do I have this, but no computer I have will fastboot anything to the tablet it just sits there after I do the flash command to flash twrp for as long as I let it sit and never completes.. Also by trying to boot into recovery I get the fallen down android with the red !.
It will boot into Android just fine, I just now have no recovery. The device is unlocked because it tells me it is unlocked when I boot it, but I can't flashboot anything and it has that key driver not found thing on it also. Not sure why my recovery isn't there since the only thing I have ever done to it was unlock using the V8 tool since I am on 4.2.1 and then try to flash the right 2.4.4.0 patched version of TWRP. If it isn't seeing my device I can't see how it would have wiped my recovery.
Seen several people with my issue and have even asked a question but so far no one has responded.
Edit: I still have that error on the bootloader but I finally got TWRP to flash after going to a 3rd computer and using a USB 3.0 port. Don't know the significance of the 3.0 port but it worked so I am not asking questions.
slickdaddy96 said:
Not only do I have this, but no computer I have will fastboot anything to the tablet it just sits there after I do the flash command to flash twrp for as long as I let it sit and never completes.. Also by trying to boot into recovery I get the fallen down android with the red !.
It will boot into Android just fine, I just now have no recovery. The device is unlocked because it tells me it is unlocked when I boot it, but I can't flashboot anything and it has that key driver not found thing on it also. Not sure why my recovery isn't there since the only thing I have ever done to it was unlock using the V8 tool since I am on 4.2.1 and then try to flash the right 2.4.4.0 patched version of TWRP. If it isn't seeing my device I can't see how it would have wiped my recovery.
Seen several people with my issue and have even asked a question but so far no one has responded.
Edit: I still have that error on the bootloader but I finally got TWRP to flash after going to a 3rd computer and using a USB 3.0 port. Don't know the significance of the 3.0 port but it worked so I am not asking questions.
Click to expand...
Click to collapse
Adndroid with a red ! means you have the stock recovery. Not sure why you can't use fastboot. I'd check all your drivers on your PC first as that is the most like cause. Start by uninstalling and reinstalling the Android SDK.
sbdags said:
Adndroid with a red ! means you have the stock recovery. Not sure why you can't use fastboot. I'd check all your drivers on your PC first as that is the most like cause. Start by uninstalling and reinstalling the Android SDK.
Click to expand...
Click to collapse
I got it to work. Weirdly It took 3 different computers before I got fastboot to recognize the tablet and allow me to flash the recovery. I was worried, but if you say the red ! means I still had a recovery then obviously it was just a communication issue with my device. The problem is now that only one of my three computers likes to communicate via fastboot and all three had the appropriate USB drivers installed. I am going to have to blame it on Windows most likely overriding and installing a wrong driver possibly.
I got TWRP and root. Debating on which ROM to flash now CROMi or Energy.
I still get that key driver missing at the top in the bootloader menu but obviously it isn't hurting anything and fastboot still works.

[Q] stuck in boot loop / pc not recognizing phone with adb

Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
brickdummy said:
Hi,
I tried to install a ROM but it got stuck on the white screen with the HTC logo. I tried to do factory reset but it gets stuck again. I don't have clockwork recovery, and I rooted my phone using adb and ace recovery, which is not on my phone. I only temporarily used it to flash my rom, stupid I know. :-/ When I connect my phone to the PC it is not being recognized. I tried putting the PD98IMG.zip file on my sd card but it just says that it the image is incorrect. Is there anything I can do? Is this fixable?
Click to expand...
Click to collapse
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
shadowboxx said:
I just went through some similar stuff. What type of computer are you using? PC/Mac? Are you using the original cable? What troubleshooting steps for connectivity have you done? Different cable? USB port?
Can you access the bootloader screen when you pull the battery and reboot while holding the volume button down and holding the power button? By accident, I found that the phone and PC will communicate with each other when "Fastboot" is selected on the bootloader screen (you should hear a connection chime and it should change to "Fastboot USB") except I could only get fastboot commands to work. The good news is that should be enough to flash a boot or whatever else you need to get back in business.
Click to expand...
Click to collapse
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
brickdummy said:
Hi, Thanks for the reply.I am using windows 7. I downloaded the drivers for HTC, and I am using a data cable and the USB port in the back of my computer, nearest the mother board. I do see "Fastboot USB" on the phone but when i type in the command prompt "adb devices" I get nothing.
Click to expand...
Click to collapse
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
bananagranola said:
Flash a recovery.img from fastboot. What is an ace recovery? Read my signature for the HTC logo problem.
Click to expand...
Click to collapse
when i flashboot the recovery.img file it goes to the red triangle.
brickdummy said:
Hi I actually saw your post earlier thank you. I will work on this. I found it in a tutorial when I rooted my phone with HTC dev, ace_recovery_ext_4.img. I'll post where i found it later.
Click to expand...
Click to collapse
Hi the program is actually called 4EXT Recovery Touch. I finally was able to open it through fastboot....Now all thats left is to find the right zip file to put my phone back to stock.
shadowboxx said:
That's great you're getting the fastboot usb message! As long as you're not using a hub or some other usb extender, any functioning usb port on the pc will do. Again, I learned this by accident (ie the hard way) and found that in this mode, only fastboot commands will work, not adb. (on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Great test for connection: fastboot devices (if you get anything else except a serial # with fastboot after it, then close the cmd window, unplug, and pull battery/reboot to bootloader), fastboot reboot-bootloader. Once it reboots back into the bootloader screen, make sure you press the power button while fastboot is selected and you should again hear the chime and see fastboot usb come up. This is your phone saying it's ready to accept your fastboot commands.
Do let us know how it works.
Click to expand...
Click to collapse
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
shadowboxx said:
(on a side note, and others should correct me here, adb and fastboot work together when the phone is rebooted normally or in recovery but not in the bootloader screen)
Click to expand...
Click to collapse
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
brickdummy said:
Hi, this did work, thank you. Would you happen to know how i can load the stock software on my phone? I had it rooted before im not sure if its still rooted. I also managed to get the 4ext recovery on my phone too.
Click to expand...
Click to collapse
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
As for your post in your other thread, read my signature.
bananagranola said:
As far as I know, fastboot only works when your phone is in fastboot mode. ADB works in recovery or system.
Flash a rooted stock ROM from recovery. Whether you have root is in your system partition. Whether your bootloader is unlocked is in your bootloader. Whether you have a custom recovery is in your recovery partition. Three separate things.
Click to expand...
Click to collapse
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
brickdummy said:
I'm sorry, I have no idea what I am doing. Can you show me the steps? When I try installing a stock rom zip file in my recovery from my sd card it aborts.
Click to expand...
Click to collapse
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
bananagranola said:
I'm guessing that you're trying to flash a PD98IMG.zip or a RUU. You need an actual stock rooted ROM, probably from here on the forum. Or just flash Android Revolution HD, an optimized rooted stock ROM, also from here on the forum in the development section. For more specific steps read the Ace Think Tank linked in my signature.
Click to expand...
Click to collapse
Ok, one more thing. I have S-ON. does that matter?
----
It did not, lol anyway it worked. Thank you everyone for you help. I really appreciate it.
-----
For those wondering I found the stock rooted rom here http://http://forum.xda-developers.com/showthread.php?t=996368
http://forum.xda-developers.com/showthread.php?p=26617631
Instructions to flash the rom
http://http://forum.xda-developers.com/showthread.php?t=2168500
brickdummy said:
Ok, one more thing. I have S-ON. does that matter?
Click to expand...
Click to collapse
Yes. You need to read the part in my signature about being stuck in the splash screen.
bananagranola said:
Yes. You need to read the part in my signature about being stuck in the splash screen.
Click to expand...
Click to collapse
ok, got it. Thank you again
Dear friends,
I have this problem: I got a brand new TCL S720 and the Google Play did not work, being a known rom issue. So, before doing anything, I've managed to make a backup of it's original rom with MTK Droid tools whichI supose it did it well. Then I've tried to install a CWM recovery to try a custom rom for it. The CWM recovery seemed to install succesfully but I didn't manage to install the new rom. If I remember well, it stucked on boot logo. Then tried to revert at it's original stock recovery, managed to have the phone back as it was in initial state, but doing more tries, It remained stucked on boot logo. The problem is that my computer doesn't recognise it anymore, when I connect it to USB it tries to install MTP usb driver but even before the driver was installed well, now it refuse to install, like the driver is not good or the proper driver doesn't exist. So the only thing I can do is to boot on stock recovery but even I tried to copy the original rom update.zip on external SD and to flash the phone using install update from sd card in recovery mode, It doesn't find the external sd card. So I'm stuck here, the computer doesn't detect the phone to try flashing it with SP flash tool or MTK Droid tool, and I also can't flash it from sd card. Have you any idea how to make it work again?
Thanks in advance.

[Q] Unlocked, reflashed, app ran into problem phone restarted and bricked?

Hi there,
Im still kinda a noob with android...
but i managed to unlock my htc sensation trough the steps @HTC,
changed the recovery, tried to flash a rom.
it failed due to my phone not being S-off. so i flashed it back :/
no problem there i thought just a rooted htc.
downloaded an app to remove bloat. and all seemed fine...
I was playing Clash of Clans, and it gave a message that the Google play services stopped and the phone rebooted.
when booted the lock screen was frozen, i pulled out the battery to find out my phone is unresponsive..
When i connect to windows 8, it cant recognize my phone at all
When i connect it to a charger i dont see the charging light.
and the worse thing is.. i cant get into the recovery.
any idea's what i can try?
i checked out the [unbrick] tread but i cant seem to figure out which "Package" i need and the links on the bottom of the page dont work when i click them
Thanks in advance
-Aline
At first you have not to be S-OFF in order to flash a rom.
Your rom will get installed just fine.You just need to flash the kernel of your rom manually through fastboot using the command fastboot flash boot boot.img.
What exactly do you mean by telling "so i flashed it back"?
Did you relocked your bootloader with fastboot oem lock and you flashed an RUU?
You said you are just rooted.If my theory was right you probably unlocked your bootloader again by flashing the unlock.bin and a cwm recovery and then you had to use a (Superuser , SuperSU zip).
The first time you unlocked your device was you using the same computer with windows 8?
If yes this is a problem.Check your device manager for unrecognised devices.Can you see the device?
Check this out.You can also check this.
(You can try with win7 or a linux destribution instead.)
Are you still able to boot into bootloader (hboot) using (Power)+(Vol-) Buttons?
If you have enabled usb-debugging and a working adb shell despite you are in a bootloop you can try:
Code:
adb shell
su ------>(If you don't see # instead of $)
reboot oem-78 -------> To get in RUU mode
or
reboot bootloader -------->(To reboot into hboot)
* reboot recovery could bring you to recovery *
If you can get into hboot or RUU mode give the command fastboot getvar all and copy-paste what it prints.
I know it was possible to flash with S-on,
thats what i tried and it failed (manually flashed the boot.img resulted in a bootloop)
so i flashed back to the "stock" rom.
resulting in a "normal" rooted device
since i've replaced my recovery and got root access
it never has been oem locked again.(still isnt)
i cant get into my bootloader/ruu mode. nor start up.
when i plug it into my computer (windows 8) it makes the sound as it does when you connect a device.
but in device manager it shows nothing, not even a yellow ! as it normally would if it can recognize a device.
aline1996 said:
I know it was possible to flash with S-on,
thats what i tried and it failed (manually flashed the boot.img resulted in a bootloop)
so i flashed back to the "stock" rom.
resulting in a "normal" rooted device
since i've replaced my recovery and got root access
it never has been oem locked again.(still isnt)
i cant get into my bootloader/ruu mode. nor start up.
when i plug it into my computer (windows 8) it makes the sound as it does when you connect a device.
but in device manager it shows nothing, not even a yellow ! as it normally would if it can recognize a device.
Click to expand...
Click to collapse
As you have not access to bootloader but your device is still seems to get connected i think you can only try HTC Unbricking Project.If the brickdetect.sh is not working you can try a different linux destribution.
Gatosbil said:
As you have not access to bootloader but your device is still seems to get connected i think you can only try HTC Unbricking Project.If the brickdetect.sh is not working you can try a different linux destribution.
Click to expand...
Click to collapse
Well, i just wonder which package i need, tried the links at the bottom of the post but those are no longer valid :/
aline1996 said:
Well, i just wonder which package i need, tried the links at the bottom of the post but those are no longer valid :/
Click to expand...
Click to collapse
Oups!I downloaded those packages some days before and I didn't see the links are broken now.
You can download them from the attachments here.
For Sensation and Sensation 4G
Gatosbil said:
Oups!I downloaded those packages some days before and I didn't see the links are broken now.
You can download them from the attachments here.
For Sensation and Sensation 4G
Click to expand...
Click to collapse
Well im afraid my phone is offically dead
this is what i get when i use ./brickdetect
[email protected]:/media/sdc$ ./brickdetect.sh
Searching for bricked device...
Device can't be detected. Check connections
[email protected]:/media/sdc$
please tell me i did something wrong xD
edit:
after some digging in knoppix i did find this:
http://imgur.com/DR7T4QK

[Completed] MOTO X PLay Root gone wrong!

Alright, I wanted to root my moto x play and and i tried doinng it using this tool. http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3206881
Unlocking the boot loader worked fine and it got unlocked. After when i flashed on twrp, it prompted to me set up the device and so i did turning on usb debug mode. After i flashed on supersu and when i tired going into recovery mode twrp was not there. So i flashed on supersu first and then twrp and finally it worked. After i ran supersu and booted the device it doe not get past the boot loader warning. the device is readable in adb but i cant sideload and push anything onto /sdcard does not exist and when i side load i get error:closed. in device manager the phone shows up as mtp usb device but with a yellow triange. when i run the command adb usb the driver install fails. i really hope this is not a brick and i can recover.
sidenote= the sd card does not work so i can not flash another rom.
please help.
Found fix.
Update: not bricked. Flashed on stock ROM using a otg cable.

URGENT!! Fastboot can't be detected on PC Android 10 Boot slot TWRP

I'm sure my drivers are fine cuz i messed this up via fastboot.
so i got android 10 on my op7p. There were some magisk modules that caused a bootloop. But i cant uninstall those modules without twrp. So i decided to flash twrp into a boot slot via fastboot. then, i set the active-slot to that. but then I still don't get twrp idk why. Now, I can get into fastboot but my pc doesnt detect it, I cant boot into the system either. The only thing my pc detects is when i power the phone off and plug it in, it automatically boots into the unlocked bootloader screen and gets stuck in there. PC detectes an "unknown usb mass storage device". HELP!!!
xnegra80 said:
I'm sure my drivers are fine cuz i messed this up via fastboot.
so i got android 10 on my op7p. There were some magisk modules that caused a bootloop. But i cant uninstall those modules without twrp. So i decided to flash twrp into a boot slot via fastboot. then, i set the active-slot to that. but then I still don't get twrp idk why. Now, I can get into fastboot but my pc doesnt detect it, I cant boot into the system either. The only thing my pc detects is when i power the phone off and plug it in, it automatically boots into the unlocked bootloader screen and gets stuck in there. PC detectes an "unknown usb mass storage device". HELP!!!
Click to expand...
Click to collapse
How did you flash twrp? On A/B devices like the OP7P you can't simply fastboot flash twrp since that will cause you bootloops. To install twrp you have to fastboot boot the image and when TWRP is booted you have to flash the installer zip file. Since you are now stuck in a bootloop, you can try to recover your boot image with something like this https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345 (no guarantees on this).
Fastboot flash this image and see if you can boot again. If that does also not work I believe the best thing you could do is reset everything with the MSMDownloadTool.
Did you use this command: fastboot flash recovery filename.img?
If yes, you'll have to use MSM to restore it
THREAD CLOSED! If interested in the subject please follow this thread: https://forum.xda-developers.com/oneplus-7-pro/how-to/android-q-4th-developer-preview-t3953997
Relevant posts have been copied to that thread.

Categories

Resources