Database Info

Think I messed something up

Not even sure where to start. I've had my One S (TMO) for about 2 weeks now. I immediately followed all the guides to unlock my bootloader, install custom recovery and install custom ROMs. Was running Viper OneS for a while and then switched over to TrickDroid (both 7.0.0 TMOUS and 8.1.0). All of the ROMs seemed to give me some odd issues.
With Viper OneS (after patching my services.jar) I was able to install SManager and run the V6 supercharger script, but after reboot, I was no longer able to get into the ringtone and notification sounds options on the device. When I went to either screen they were just blank and I couldnt choose music from any location on the phone.
With TrickDroid 7.0.0 TMOUS, I was able to patch services.jar and run the supercharger script without any issues at all. However, after a few days of usage, I noticed that calls were no longer forwarding the voicemail number I setup using an MMI code. From there I went to TrickDroid 8.1.0 but even after patching my services.jar, my supercharger settings would not stick after reboot.
Here's where I think something went wrong. I wanted to go back to stock but rooted. Since there were no 2.35 RUUs available for download anywhere, I decided I would download the 1.84 RUU and then get the OTA update. I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems. Unlocked the bootloader and installed TRWP 2.2.2 so that I could flash supersu and root the phone and noticed that the phone was not acting right. From TWRP, its almost impossible to get the phone to reboot. When I choose to reboot, the screen goes blank, flashes once or twice and the notification light keeps turning from orange to green and then back again. I have to hold power down for about 10 seconds, then hold volume and press power to get into bootloader just to turn the phone on.
Decided to try going back to a custom ROM and noticed something else that is strange. I wanted to flash TrickDroid 7.0.0. and during the flashing, it hung on flashing the kernel for like 5 minutes when it usually takes just a second. I then flashed the fusion v2.1 kernel and it hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds. After the flashing was done, I booted up the ROM and when I went into settings, the new kernel was not installed. I flashed it again in recovery and booted back to the ROM and still the stock kernel was showing.
Could I have somehow really screwed up my phone throughout this whole process? Is something corrupted on the NAND that is causing issues with rebooting recovery and flashing things?

[email protected] said:
I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems.
hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds.
Click to expand...
Click to collapse
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.

dc211 said:
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.
Click to expand...
Click to collapse
Thanks for the info! Glad to know I didnt mess anything up .

One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
EDIT: Wow.... i feel really dumb now. All posts I found while searching included the extra "recovery" in the commany. I just ran fastboot boot recovery.img and all is well.

[email protected] said:
One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
Click to expand...
Click to collapse
.
I doubt that the actual recovery img is named recovery.img. If I am correct that is your problem. You would be trying to boot a recovery img that doesn't exist. It should be:
fastboot boot recovery [name of recovery file].img
Example:
fastboot boot recovery cwm_5.8.3.1_ville_recovery.img or something to that effect (not sure what the actually file name is)

if you are not sure on exact name as behold mentioned, just right click on the file (.img) wherever you have it on pc, check properties, and it will tell you exact name. at that point i just copy and paste it to command window--

[Q] Bricked phone?

Hey everyone,
So I had a TWRP with stock 4.04 on my HTC One X ATT
I downloaded one of the 4.1.1 Stock ROMS posted today and tried to flash it in recovery. It said success and I rebooted.
This one http://forum.xda-developers.com/showthread.php?t=2181399
It rebooted into a black screen and it's been stuck there since. Occasionally theres a white bar that flashes at the top.
If I hold down power + volume down, the capacitative buttons just flash several times and that's it.
Adb doesn't see my phone.
However, when I plug it in my PC recognizes it. It doesn't show it in my computer, but hardware manager shows "HTC One X"
I'm concerned it's permanently bricked.
Any advice?

what hboot are you on?
if it is higher then 1.09 you Need too s-off or Flash boot.img with fastboot
here is some help for adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=1754018

Ghostrider said:
what hboot are you on?
if it is higher then 1.09 you Need too s-off or Flash boot.img with fastboot
here is some help for adb and fastboot:
http://forum.xda-developers.com/showthread.php?t=1754018
Click to expand...
Click to collapse
I have HBOOT 1.14.0002
How should I go about doing that?
I downloaded everything and I'm ready to go but I'm not sure of what's next

you need to unzip your Rom, in there is in file called boot.img
put the boot.img in the same Folder as adb and fastboot
then put the phone in bootloader and put in the usb
open cmd on your pc and go to the ADB Fastboot Folder
now put in this:
fastboot flash boot boot.img
if it's done reboot your phone.
the procedure is almost the same as flashing the recovery.

Works like a charm, thank you !

you're welcome

[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] Help flashing a rom

I've been trying to flash CM10.1 to my htc one x.
my phone is unlocked, s-off, supercid, rooted, everything..
I put the cm10.zip on my sdcard.
I wiped my phone (cache,delvik,system [not sure if i should wipe more than this? idk... this was all i saw on a few threads])
I flash the cm10.zip to my phone.
I extracted the boot.img from cm10.zip to my adb/fastboot folder
I reboot into bootloader and attempt to fastboot flash the boot.img to my phone ** (I think this is where the problem is but idk..)
I reboot my phone and i'm stuck at the cm10 loading screen.
Help?
I think my problem might be when I'm trying to fastboot the boot.img on my phone... When I attempt to see adb devices (while I'm in bootloader) I get none... I would always have to load into android before adb would recognize my device then boot into bootloader and do anything (it always worked in the past so i never really cared..) but with a custom rom I'm unable to boot into android so idk any suggestions? would this be the problem? it says it successfully flashes it but i'm having doubts... as it shows no connected devices. can I flash the boot.img to my phone before i flash the rom?

obg8 said:
I've been trying to flash CM10.1 to my htc one x.
my phone is unlocked, s-off, supercid, rooted, everything..
I put the cm10.zip on my sdcard.
I wiped my phone (cache,delvik,system [not sure if i should wipe more than this? idk... this was all i saw on a few threads])
I flash the cm10.zip to my phone.
I extracted the boot.img from cm10.zip to my adb/fastboot folder
I reboot into bootloader and attempt to fastboot flash the boot.img to my phone ** (I think this is where the problem is but idk..)
I reboot my phone and i'm stuck at the cm10 loading screen.
Help?
I think my problem might be when I'm trying to fastboot the boot.img on my phone... When I attempt to see adb devices (while I'm in bootloader) I get none... I would always have to load into android before adb would recognize my device then boot into bootloader and do anything (it always worked in the past so i never really cared..) but with a custom rom I'm unable to boot into android so idk any suggestions? would this be the problem? it says it successfully flashes it but i'm having doubts... as it shows no connected devices. can I flash the boot.img to my phone before i flash the rom?
Click to expand...
Click to collapse
If you are s-off you shouldn't need to flash the kernel seperately.. However use "fastboot devices" instead of "adb devices". When you are connected to a computer via USB it should indicate that on the bootloader.
Before I was s-off I'd flash the rom then return to the bootloader directly and flash the kernel before attempting to boot for the first time.

The post above mine is correct. If you are s-off you don't have to flash the boot.img. Going by what you posted it doesn't look like you wiped your data in recovery, which is something you have to wipe when flashing a new ROM. That's probably why it didn't boot properly. Try again doing a full wipe/factory reset from recovery.
Sent from my One X using Tapatalk 2

[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