Develop Bugs

[Q] htc one x bricked. not charging. not booting. only bootloader

usual story.
got an htc one x. flashed unlocked all going well. installed a bad rom (did not make a back up)
froze at splash screen. only late last night i found disaster recovery, so i put it to download and shut off the phone. boot back up this evening and tried to install recovery re-lock bootloader, clear cashe etc but. i got a low battery warning when trying to flash.
i didn't have the latest clockwork mod for charging installed; and battery is too low to flash to it.
this is where things get different. i used the boot loader to power down. i plugged it in to the wall to charge and i got this strange flashing red led(not orange) after about an hour it went solid red. had it charging from the wall socket for well over 4 hours now with the solid red led.
then all of a sudden the led starts to flash red again. so i disconnect the phone and try to boot.... nothing happens. try bootloader mode(power + vol.dwn) nothing.
i had to hold the two buttons then plug in the wall charger. then it went into bootloader. problem is it says relocked AND security warning....... and still after all that time charging. i still get low battery warning @ flash.
so i tried to turn off the device again using the power down option. two things happen here. 1)if the charger is in the screen goes black and instantly restarts to fastboot usb menu. 2)if it isnt in it will turn off and wont turn back on (splash screen or bootloader) until the charger is back in.
so what ive done as of now is plug it in to charge over night and hope this thread can shed some light.
additional info:
ruu version: 'RUU_ENDEAVOR_U_ICS_40_hTC_Asia_WWE_1.28.707.10_Radio_1.1204.103.14_release_257076_signed.exe
os version: 1.28.707.10
clockwork mod version: 5.8.2.7
plz any help would be invaluable
EDIT: just turned on phone about ten minutes after i plugged it back in to the charger (held power button alone) splash screen is back (yay!!) but still battery low when trying to flash in
fastboot usb. ima try in the morning after a full night to the charger. fingers crossed

http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!

kasalamite said:
http://forum.xda-developers.com/showthread.php?t=1598336
no need to spam xda with two threads !!!
Click to expand...
Click to collapse
srry posted last night but would not show the thread... so i figured i couldn't so i tried to post in an existing thread. now i dont know how to delete that other one...

FIXED
well never mind the fact that i loaded a plethora of info onto this post and nothing.
but besides that i got it working. in the disaster recovery tut it only lists using the ruu through a flash... never stating that you can just run the file directly and not go in %temp% and get the rom.zip(excepting for the recovery_signed.img). simply find your version of the ruu that you need, flash back to the stock recovery image (within the rom.zip) relock bootloader place device in fastboot and run from pc.
the only hard part is getting it to charge... dont know how mines took charge but i pluged it into the sockets @ my school (long story read this thread: http://forum.xda-developers.com/showpost.php?p=26156147&postcount=20).
when i pluged it in the light went solid red instantly no blinking. after about an hour of charge i pressed the power button and it went to the splash screen (still was on a older CWM which doesn't support charging) left it at the splash screen for the remainder of the class (about another hour) unplugged entered bootloader.
@ this point i had no security warning under relocked. but i used the power down option, took it home and tried to unlock/flash to the latest version of CWM so i could charge. it worked without a hinge.
anyone know why it took charge on an older CWM?
note i got the phone back up and running and the first thing i did was make a nandroid back up

hi i dont have an answer to your question but i have a question to your answer am curently suffering the same problem i can flash the stock cwm because of low battery, and i know when in boot mode it doesnt charge so i rebooted the phone it took me to the htc logo and its displaying a solid red light does this mean its charging or what (the boot loader is re-locked so i can flash stock cwm but cant due to low charge)

Noob badly. But I think it should be charging. Could b wrong. Leave it there for a couple of hours and try again. Mayb fixed. Give it time and try again.
Sent from my HTC One X using XDA

Same thing is happening to my phone. and its bootloader is locked and cannot be unlocked because of the charging. its usb debugging wasnt turned on either before it went down.

Please help anyone?
Guys I have Htc One X. I rooted it then I thought to install a custom rom (resurrection remix) and gapps. so when I was in the CWM recovery I installed the mod while it was installing it said error no file contents but it installed successfully anyway. after that I installed Gapps but it got an error and said Installation aborted. I then started panicking and I tried to restore the backup but nothing happened, then I re-locked the bootloader with battery below 30% then I used the batch file to charge it then I unlocked it again. Now I want to download a stock rom I tried 2 one was a newer version than what my phone actually is and the other one was a lower version than what my phone actually is. I then tried alooooooooooot to search for the appropriate one for my phone but I didn't find it so I thought to continue with installing custom rom anyway but the problem is that I need to get the new mod zip file and new gapps zip file into my phones sdcard but I can't do that/I don't know how. My phone isn't recognized by my pc ( I can't browse it's files) and I tried using adb in command prompt which is very complicated for me however I searched on the internet and tried to do the same but then it says "adb server is out of date killing" then I found one adbFix.exe that said that the adb in HTC sync manager folder is causing a conflict but then the Fix file said that its ok and no problems are there. Now I need to put custom rom and gapps zip files to my phone's sdcard but I can't. Please I would be very grateful to anyone who would help me and guide me and If I'm posting in the wrong forum or thread then please forgive me for this is my first time I made an account on XDA and my first ever comment/

Please help me help him... Thx ____

I sold my old incredible to a kid. It sat for about 7months due to me upgrading to new phone. It had CM7 on it running fine when sold it. When he went to activate it, problems problems problems. I took it back him and told him I would fix it before paying me. I'm having troubles.
- No working recovery. can't get it to boot properly. I had the "5 vibrates of death" couple times.
- I'm trying a couple ruu's but when finished it will get to the lock screen, look normal, then reboot to lock screen then after a couple times will 5 vibrates then black screen.
1. I've tried [HOW-TO] Fix 5 vibrate and black screen (http://forum.xda-developers.com/showthread.php?t=1110865) I can seem to do the sdcard fix but not sure how to complete the usb fix or if that will even help me along. I can't "run terminal in anroid" because I can't get the Rom to boot up. All I can do is fastboot.... Compouter recognizes device.
2. I've tried multiple RUU's including PvilleComp's at http://pvillecomp.com/?page_id=22
3. I'm using hboot .92 and radio is 2.15.10.07.07 s-off
I realize problems like these have been asked before, I've looked through them, uesd the search button, etc.... But I'm still really stuck and would like to fix this before reimbursing kid money.
Thanks

red3razor said:
I sold my old incredible to a kid. It sat for about 7months due to me upgrading to new phone. It had CM7 on it running fine when sold it. When he went to activate it, problems problems problems. I took it back him and told him I would fix it before paying me. I'm having troubles.
- No working recovery. can't get it to boot properly. I had the "5 vibrates of death" couple times.
- I'm trying a couple ruu's but when finished it will get to the lock screen, look normal, then reboot to lock screen then after a couple times will 5 vibrates then black screen.
1. I've tried [HOW-TO] Fix 5 vibrate and black screen (http://forum.xda-developers.com/showthread.php?t=1110865) I can seem to do the sdcard fix but not sure how to complete the usb fix or if that will even help me along. I can't "run terminal in anroid" because I can't get the Rom to boot up. All I can do is fastboot.... Compouter recognizes device.
2. I've tried multiple RUU's including PvilleComp's at http://pvillecomp.com/?page_id=22
3. I'm using hboot .92 and radio is 2.15.10.07.07 s-off
I realize problems like these have been asked before, I've looked through them, uesd the search button, etc.... But I'm still really stuck and would like to fix this before reimbursing kid money.
Thanks
Click to expand...
Click to collapse
Have you tried reflashing cwm recovery thru hboot? Then wipe everything and flash a rom.

Yes I did try this. Got CMW re-installed, and when I tried to select any option in recovery just goes to picture of hat and hangs there. I press power button and goes back to CMW main menu.
I also tried a fix from your post:
cmlusco said:
Not sure where you got those instructions or files from, but there not for the incredible.
Heres what you do.
Download this file http://dinc.does-it.net/Stock_Images/4.06.605.3/PB31IMG.zip, and put it on the root of your sdcard in no folders.
Pull the battery, reinsert, and press vol down +power for 5 secs then wait for 5 mins not touching anything.
Press vol up and then wait for 20 minutes touching nothing. The phone will reboot once during the process, this is normal just let it be.
Press vol up, the phone should reboot and come up being able to see things and boot to the os normally.
Click to expand...
Click to collapse
This is where I've gotten the furthest. Got thru HTC quietly brilliant. Droid animation (red computerized looking stuff), "Droid" sound, then got to lock screen. Sit there for 5sec or so then would reboot, do the same thing over again and get to lock screen. Reboot again, then usually "5 vibes of death"

The kid does not have a phone other than this one I'm trying to fix, and they would really like it fixed and in their hands by Friday.
I just tried re-installing CMW again, and just hangs on white HTC screen, doesn't even make it to CMW menu. This is kicking my butt.

Fruitcake? Back to stock? That worked on my phone once..not sure if it was sim or not
Sent from my MB860 using Tapatalk 2

He would like back to stock. S-off or S-on. Root or no root. Just working properly.

red3razor said:
Yes I did try this. Got CMW re-installed, and when I tried to select any option in recovery just goes to picture of hat and hangs there. I press power button and goes back to CMW main menu.
I also tried a fix from your post:
This is where I've gotten the furthest. Got thru HTC quietly brilliant. Droid animation (red computerized looking stuff), "Droid" sound, then got to lock screen. Sit there for 5sec or so then would reboot, do the same thing over again and get to lock screen. Reboot again, then usually "5 vibes of death"
Click to expand...
Click to collapse
What button are you using to select things in recovery? Pressinh power on the main menu brings up the orange hat, press the trackball to select items power to go back.

I have to admit I was using the power button (used to my Rezound) but now I cannot even get CMW to work. Flashed it with the .zip in hboot/bootloader. Tried both restart and not restart after running recovery update. Both ways, phone will just hang at white HTC screen and not enter CMW anymore. Sometimes screen goes black then back to white screen or just stays on white screen indefinitely.

Could a bad battery be causing this? I'm trying 2 different ones. I'm not sure if either are bad, just trying to troubleshoot. Is there a way to check battery health on a non-bootable phone?
Any other suggestions to try? Thanks everyone for your help. I'm giving this phone just a few more hours of me fussing with before it gets retired.

UPDATE:
after battery sitting on charger all day while at work (10hrs or so), tried to boot up phone. went well. got to OS right away. I let it sit for 1/2hr to see if it would reboot or not. it stayed alive. i tested making a phone call: OK. I browsed the the XDA website for less than 1 minute, it then rebooted on me. white HTC screen then black. white HTC. then black. white HTC then rebooted fine. couple seconds later shuts off again. this time the same white HTC then black 3 times same as before. then instead of rebooting, got the 5 vibes of death.
the phone while working also asked me to update to lastest android 4.08.605.2
i'm not sure which RUU i ran to get this far, but must have been an earlier.
so i guess now i will attempt the 5 vibes fix, that's if i can get the phone booted for long enough to install terminal emulator from market and follow the steps.
any ideas guys? thanks in advance.

i did the sd card fix and attempted 5 vibes fix: http://pvillecomp.com/?page_id=33
pulled the battery. put it back in. powered on the phone. once the first white "HTC Droid Incredible" screen came up, I plugged phone into PC. instead of one audible ding from computer saying device connected, i recieved 3 very quick dings from PC and phone shuts off. no charging light indicator. if i single press power button, unresponsive still.
now i unplug device from PC, remove battery, put battery back in, hoping for it to reboot normally. instead i get white HTC then black. white HTC then black screen with no boot up.

I believe so far I've tried the GB RUU from PvilleComp and the RUU provided by cmlusco in my post #3.
I guess now I'll try the Froyo RUU from PvilleComp's site: http://pvillecomp.com/?page_id=22

It could be your battery, but usually the phone will just turn off not reboot. 4.08.605.2 does not have a PB31IMG.zip so you have to use an ruu exe, but that requires you to be able to boot. You could try the froyo PB31IMG and hope it works. My only other sugestion would be to try and upgrade your hboot to the new 1.02, and then use the htcdev site to unlock it. Then fastboot flash cwm recovery and hope you can access it.

i upgraded the hboot. unlocked via htc site. reinstalled CMW and was working fine. flashed ota stock GB. same problems still. i left him long enough without a phone, so the fixer project is ended.
thank you all for your help, greatly appreciated

red3razor said:
i upgraded the hboot. unlocked via htc site. reinstalled CMW and was working fine. flashed ota stock GB. same problems still. i left him long enough without a phone, so the fixer project is ended.
thank you all for your help, greatly appreciated
Click to expand...
Click to collapse
No problem. Sounds like it may be a hardware issue.

Soft Brick from bad cable?

So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.

Lohboh said:
So earlier today I plugged in my charger into the phone, and it gave me an error messaging saying something about the cable being damaged, and System UI crashed. I unplugged it and made a mental note to buy another charger.
The device was having some issues with SystemUI properly rebooting, so I restarted the phone and got caught into a boot loop.
The device will not go past the HTC splash screen, just rebooting every few seconds.
It doesn't reboot when I go into the white screen bootloader, nor does ADB or fastboot oem detect it.
If I select download or recovery mode, one of two things happens:
1) It displays the monochromatic HTC logo for a few seconds and then reboots back into the normal bootloop.
2) It stays in the monochromatic HTC logo without doing anything else.
ADB does not work in any state, nor does trying to flash an RUU.
I've tried sticking an RUU with an SD Card and going into download mode, but nothing happens.
The device was running Leedroid at the time.
The bootloader is unlocked, and it is S-ON. It is a T-Mobile device with the Marshmallow Firmware installed.
I would very much appreciate help for this as I've been searching for solutions the entire afternoon.
I don't quite understand how a faulty cable would cause a bootloop but not completely fry the device.
Thanks.
Click to expand...
Click to collapse
So you can't even get to download mode by holding power+vol down for several seconds?

Tarima said:
So you can't even get to download mode by holding power+vol down for several seconds?
Click to expand...
Click to collapse
No, it just brings up the same issue of it getting stuck on the monochrome HTC logo.

no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?

ffuser1 said:
no idea as i've never had this happen, but when i've had issues in the past i'd let the battery drain completely, then charge it a little, then try booting to download mode. maybe you could try that? did you have twrp or any custom recovery installed?
Click to expand...
Click to collapse
I've tried that, and I have the latest TWRP.

Razer phone stuck on boot screen after attempted root

I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.

Hi
to get to another mode you need to have the phone connected to a PC or Mac, so plug it into the usb and power off, once it is off hold volume down, this should make it go into download mode from there follow this link ( https://forum.xda-developers.com/razer-phone/help/razer-phone-os-t3772424 ) and you should get back to stock and you can retry to root from scratch or leave your phone as stock
Hope this helps

adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
If you got it to download mode but cannot communicate with the phone check your fastboot and drivers. You need Google USB drivers and the absolute latest fastboot. There are other posts here that can help you find the right stuff

adroit14 said:
I followed this guide:https://forum.xda-developers.com/razer-phone/how-to/twrp-magisk-fullproof-guide-razers-wifi-t3756137 to root my razer phone. This was the first time I tried, so I used the steps all the way at the bottom. After rebooting around step 7, it has stayed on the logo for around 3 hours now. It's not detected by ADB, so I cant flash anything or reboot it, and the buttons are not responding. I've tried holding the power button with volume down, and other combinations but it just doesn't work. I'm wondering, is there any solution for this? Or do I just need to wait for the battery to die? Thanks in advance for any responses.
Click to expand...
Click to collapse
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.

incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me

tabletalker7 said:
Mine was stuck like that months ago. I let it run the battery dry, charged it full, and followed the instructions from Razer to flash stock files. It worked for me
Click to expand...
Click to collapse
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/

incinandseril said:
That was my next thing.
Seems mine ran out of juice earlier.
It's automatically kicking to that screen once plugged in.
Completely dead, the charging light blinks red for a minute to get it on, then jumps to the logo screen, charging light turns off.
Kind of thinking mine is toast :-/
Click to expand...
Click to collapse
Hi follow the link from my comment above and give yours a try, don't think yours is toast just think it's in a boot loop cycle
My comment is second one down

incinandseril said:
I assume your phone looks just like mine at the moment.
Happened to mine after running the ODP flash_all.
What's odd is I had run it multiple times because trying the different GSIs and going back to nougat once.
The last time I ran it, it resulted in this.
I've tried multiple computers and cables to no avail.
Click to expand...
Click to collapse
I´ve got this Screenproblem with the Oreo Update with sideload, it flash but then only this Screen, i found my mistake.
My solution was to do an critical unlock for Bootloader, than install 7.1 and than sideload 8.1 OTA, now it works very fine and much smother than before

[EDIT] After letting the battery run dry again last night, plugging my phone back into my laptop booted into download mode, again with the same display as below. Fastboot again recognised the device & after doing some searching, I'd seen another suggestion somewhere else I hadn't yet tried, which was forcing the phone to partition a (to be honest I couldn't even remember which partition I'd left it in from the attempted root)
The command is "fastboot set_active a && fastboot reboot"
I did this as soon as I was able to, rather than leaving it charging (this may be unrelated, but worth considering if you're still stuck)
after this, I got to the Razer logo screen lock (instead of the blank screen lock below), I was then able to follow Razer's instructions - which are linked in one of the comments on the link from the 2nd post here (hope that makes sense)
Now I'm happy to report everything is working, back to factory
I hope this can help someone else [EDIT]
I'm unfortunately in the same position, did you have any luck flashing back to factory?
I also tried following the guide from the 2nd link, these were the steps I took:
(I can confirm my bootloader is unlocked & critical also unlocked)
1. allowed battery to run dry
2. plugged into laptop whilst holding volume -
3. phone now in download mode with battery charge symbol on screen, I left it some time to charge but noticed it got stuck as per the screenshot (for approx. 6 hours)
4. device not recognised by adb, but recognised by fastboot
5. phone not accepting any fastboot commands, when attempting 'flash_all.bat' just hangs on the first line (flash partition:0 gpt_both0.bin), I have to close command line & reopen to try anything else, however whatever I try I get the same result, so basically the only responses I'm getting from fastboot are that it is aware of the device and confirms the bootloader incl. critical is unlocked
My next thought was the perhaps the phone attempted to boot once it reached the picture charge level and therefore locked in the same way it had initially on the razer logo. Should I attempt flashing the factory image immediately once the phone enters download mode, rather than allowing it to continue charging until it's flashed? Any ideas would be greatly appreciated!
Cheers

Been a while since anybody posted, I know... but did anyone who had this problem end up figuring it out? I am in the same situation and am freaking out a little bit, I JUST got this phone...

Just try this and should solve your problems
https://s3.amazonaws.com/cheryl-factory-images/cheryl-p-release-7083-user-full.zip

Another M9 bootloop

Hi everyone, had the phone for few years, one day it died and never booted again. Nothing was flashed at the time, my son was using it and I read that some phones, if they got hot enough playing games, the nand will get erased and the phone is borked.
All I get is the white HTC screen.
If I hold the volume + and - I will get to the screen attached.
If I select download mode, the phone will reboot and a black HTC screen will appear, but then the phone will reboot after 1-2 seconds, back to the white HTC screen.
Same with bootloader mode.
I have downloaded 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.zip and copied it to a 32GB sd card, and tries to get it to flash via download mode using the process above, but nothing happens and the phone reboots within 1-2 seconds.
Is there any way I can revive this phone? or just throw it in the trash?
Thanks!

shpitz461 said:
Hi everyone, had the phone for few years, one day it died and never booted again. Nothing was flashed at the time, my son was using it and I read that some phones, if they got hot enough playing games, the nand will get erased and the phone is borked.
All I get is the white HTC screen.
If I hold the volume + and - I will get to the screen attached.
If I select download mode, the phone will reboot and a black HTC screen will appear, but then the phone will reboot after 1-2 seconds, back to the white HTC screen.
Same with bootloader mode.
I have downloaded 0PJAIMG_HIMA_UL_N70_SENSE80_ATT_MR_NA_Gen_Unlock_4.30.617.2.zip and copied it to a 32GB sd card, and tries to get it to flash via download mode using the process above, but nothing happens and the phone reboots within 1-2 seconds.
Is there any way I can revive this phone? or just throw it in the trash?
Thanks!
Click to expand...
Click to collapse
Don't trash it yet!
Do you have a custom recovery?
If not you can "RAM" boot TWRP. While in the bootloader screen do this:
Code:
./fastboot.exe boot twrp-3.0.2-0-hima.img
Then with MTP enabled you should at least be able to look at your files (assuming not HOT deleted like you mentioned).
There's something called "RUU" we can try next, it's a (HTC) way to bring your phone back to stock. But try to save your files first!

Thanks, I will give it a try.
I don't care about any data on the phone, just trying to make it function again.
I let the battery drain over-night, I'll see if I can do anything with it.
Thanks for your input!

Note it doesn't look like the RUU files are hosted on HTC anymore.
Here's the full filenames I have downloaded and used in the past.
- RUU_HIMA_UL_M60_SENSE70_TMUS_MR_TMOUS_3.39.531.7.exe
- RUU_HIMA_UL_N70_SENSE80_TMUS_MR_TMOUS_4.27.531.6
A quick google should let you find them but a little frustrating to not get it direct from HTC (security risk anyone?).

I was messing with it last night, after I let it completely drain it won't charge anymore. If i connect it to a charger, or to a pc, it will turn on for 1-2 seconds, then turn back off, and do the same again and again.
Thanks for your help but looks like I can't do anything to it at this point. Not sure if the battery can be charges externally.