Database Develop

[Resolved] Moto X randomly bricked itself

So, I imported and gifted this device to my GF and will describe what happened as she did. She was downloading a torrent and suddenly the screen just went black. After holding the power button for awhile, the phone came back on but, would get stuck on the boot logo(welcome message) screen and in a boot loop. I know that it is a SIM unlocked Moto X(XT 1053?)
So far, I've tried getting into the bootloader and am able to. The only problem is when I get to the recovery, I don't see the little dead Android dude. The phone ends up dying. Now I have it charging and I'm on the bootloader screen, but I still can't get into recovery. I just get a blank screen when I try.
It will be hard, time consuming and maybe a little expensive RMAing the device, as I'd probably have to send it back to the US for the warranty.
I'm thinking maybe I just try and unlock the bootloader and see if the subsequent factory reset helps. But I don't know if this will work.
I have tried fastboot erase cache but it didn't help.
I think somehow my recovery is gone. I've tried flashing a recovery.img but it errors out. (failed to hab check for recovery)
Any ideas?

Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.

KidJoe said:
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
Click to expand...
Click to collapse
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:

deejaylobo said:
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
Click to expand...
Click to collapse
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it

KidJoe said:
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
Click to expand...
Click to collapse
I only found one person with a similar issue, and you're right, he did end up getting a replacement. That's just not an option for me. It's too much of a pain sending it back to the US.
Yeah, I think I will reflash a ROM. Can you point me towards figuring out which is the correct ROM? My System Version is 212.44.21.ghost_row.Retail.en.US. So, I just grab the corresponding SBF, yeah? I flashed the logo with mfastboot, so I'm okay with that. EDIT: No worries. Foudn the right file. Sorted. Everything seems to be working fine. Thanks!
The face thing, is just to prank her. I previously had a custom message set up for her through the Moto Maker. I think she'll be rebooting her phone more often now.

oem locked NO O.S wug fresh restore fail! NEED A GURU TO TELL ME ITS FIXABLE

My nexus 6 is in a mess.
Ive briefly read everywhere about fixing it so far no luck. Is there any way any fix /solution possible
It started when i Wiped data and formated data thus wiping out the whole os inside twrp when it was working "by mistake".
So i remained oem unlocked . I used wug fresh toolkit to reflash 5.0, I suspected the process had finished but it didnt work the first time it just sat on google splash sreen and idiot me clicked on oem lock right after.
Now i cant oem unlock to run any commands or even the toolkit. I read about a hardbrick fix solution using rsd lite and qhsusb drivers basically lg version of qualcomm flashing. Would this work for my instance? What are my choices? WHAT I Dont understand is if there is no O.S why would it even ask for oem unlock knowing there isnt even a operating system on board since it was wiped after twrp reboot

androidddaaron said:
My nexus 6 is in a mess.
Ive briefly read everywhere about fixing it so far no luck. Is there any way any fix /solution possible
It started when i Wiped data and formated data thus wiping out the whole os inside twrp when it was working "by mistake".
So i remained oem unlocked . I used wug fresh toolkit to reflash 5.0, I suspected the process had finished but it didnt work the first time it just sat on google splash sreen and idiot me clicked on oem lock right after.
Now i cant oem unlock to run any commands or even the toolkit. I read about a hardbrick fix solution using rsd lite and qhsusb drivers basically lg version of qualcomm flashing. Would this work for my instance? What are my choices? WHAT I Dont understand is if there is no O.S why would it even ask for oem unlock knowing there isnt even a operating system on board since it was wiped after twrp reboot
Click to expand...
Click to collapse
No, you cannot use that fix, as it is specifically for a hard brick, non bootable device. When you relocked your bootloader, you sealed your fate. Your only option is to RMA at this point. Sorry.

Evolution_Tech said:
No, you cannot use that fix, as it is specifically for a hard brick, non bootable device. When you relocked your bootloader, you sealed your fate. Your only option is to RMA at this point. Sorry.
Click to expand...
Click to collapse
Hi! Sorry for my English. I use Google Translate. I have noticed a hundred you know well the device Nexus 6. My problem - OEM locked, stock recovery, Status code 2.
Do you think it possible to hope for a solution to this problem in software?I mean, is it possible that it will release software to solve this problem?

ArmanioKZ said:
Hi! Sorry for my English. I use Google Translate. I have noticed a hundred you know well the device Nexus 6. My problem - OEM locked, stock recovery, Status code 2.
Do you think it possible to hope for a solution to this problem in software?I mean, is it possible that it will release software to solve this problem?
Click to expand...
Click to collapse
No. You need to make a request to Motorola for repair (RMA).

cam30era said:
No. You need to make a request to Motorola for repair (RMA).
Click to expand...
Click to collapse
Thanks for the answer. Unfortunately I have no such possibility(( I'll wait, can think of something.

ArmanioKZ said:
Thanks for the answer. Unfortunately I have no such possibility(( I'll wait, can think of something.
Click to expand...
Click to collapse
your only option is to fastboot format userdata and cache.

simms22 said:
your only option is to fastboot format userdata and cache.
Click to expand...
Click to collapse
it does not help, because the established stock recovery

ArmanioKZ said:
it does not help, because the established stock recovery
Click to expand...
Click to collapse
some people it does help, but they usually have twrp recovery, so youre right.

Phone Die or did I kill It?

So here's the deal. I use WUGS and don't manually do stuff.. Yes this makes me a weak individual and I bow to the people who can manually flash and their omniscient power. I bought a 64gb google version Nexus 6 about a month ago when the price dropped. I had issues with it just shutting off every once in a while, but tried rooting and romming and no matter what the rom was, about a day in it would just force shutdown... In the early days I could access TWRP and even if I restored to a stock back up, only one time did it just restore and boot up, the rest of the time it would just not boot up..... I called about an RMA and put it back to complete stock, unlocked, trying to get it working, just thought maybe it was something I did and if so, I wanted to try stock. I flashed it, a few times I even made it to the set up screen on the initial boot, but after failing it didn't matter if I navigated to stock recovery and wiped or anything. Only thing I can do is access stock recovery and bootloader and all that and try to power it on but it just says google for a few seconds then shuts down. . Last night I got worried and relocked the bootloader so I could send it back and not have Moto void me on that... Was this always just a faulty phone or is it more likely something i did? I appreciate any intelligent thougts.
Dustin

kickenwing13 said:
So here's the deal. I use WUGS and don't manually do stuff.. Yes this makes me a weak individual and I bow to the people who can manually flash and their omniscient power. I bought a 64gb google version Nexus 6 about a month ago when the price dropped. I had issues with it just shutting off every once in a while, but tried rooting and romming and no matter what the rom was, about a day in it would just force shutdown... In the early days I could access TWRP and even if I restored to a stock back up, only one time did it just restore and boot up, the rest of the time it would just not boot up..... I called about an RMA and put it back to complete stock, unlocked, trying to get it working, just thought maybe it was something I did and if so, I wanted to try stock. I flashed it, a few times I even made it to the set up screen on the initial boot, but after failing it didn't matter if I navigated to stock recovery and wiped or anything. Only thing I can do is access stock recovery and bootloader and all that and try to power it on but it just says google for a few seconds then shuts down. . Last night I got worried and relocked the bootloader so I could send it back and not have Moto void me on that... Was this always just a faulty phone or is it more likely something i did? I appreciate any intelligent thougts.
Dustin
Click to expand...
Click to collapse
There is honestly no way to tell. We would be guessing. You cannot unlock the bootloader now either, so we can't even get you to manually flash stock to test.
You can try a "fastboot format userdata" and "fastboot format cache" to see if that helps you boot, otherwise, nothing you can do.
We do recommend that you only use toolkits if you know what they are doing in the background. It really isn't difficult. In fact, I wrote a very simple thread to explain in in General > Sticky roll-up. None of this has anything to do with omniscience. Though, that particular skill would be helpful to us to answer your actual question.

Lol thanks dude. I'll try anything. I figured out how to run simple commands, but when it comes to putting the files in the correct directory I think so that it reads it... But, you're saying now that I'm locked, stock, and not loading up, I could try to do fastboot and format data and cache? Is this a more in depth wipe than just wiping in stock recovery does ? I assume now that I locked, I can't flash firmwares without voiding my warranty or? I was actually on chroma and it shutdown, so I went to stock, started typing gmail log in on initial set up and it shut down.. .So as far as I know. I'm stock... and locked..

kickenwing13 said:
Lol thanks dude. I'll try anything. I figured out how to run simple commands, but when it comes to putting the files in the correct directory I think so that it reads it... But, you're saying now that I'm locked, stock, and not loading up, I could try to do fastboot and format data and cache? Is this a more in depth wipe than just wiping in stock recovery does ? I assume now that I locked, I can't flash firmwares without voiding my warranty or? I was actually on chroma and it shutdown, so I went to stock, started typing gmail log in on initial set up and it shut down.. .So as far as I know. I'm stock... and locked..
Click to expand...
Click to collapse
Format is not a wipe. It will wipe, but unlike a wipe, it will recreate the file system. A corrupt file system can prevent boot so worth trying.
If the BL is locked and won't unlock, that's about all you can try.
Boot.to recovery just incase you have TWRP recovery still

danarama said:
Format is not a wipe. It will wipe, but unlike a wipe, it will recreate the file system. A corrupt file system can prevent boot so worth trying.
If the BL is locked and won't unlock, that's about all you can try.
Boot.to recovery just incase you have TWRP recovery still
Click to expand...
Click to collapse
tried and the process failed... I have it back to status 2 and not rooted and it died after flashing stock so I assume sending it back is okay.. my replacement is here today. I'm unlocking and rooting as we speak

I erased everything on my Nexus 6 and then tried using the flash-all.bat from image-shamu-lmy48i.zip.
It failed saying could not allocate so many bytes.
Accidentally i did lock my bootloader using fastboot oem lock.
Now cant load anything and my phone doesn't boot.
When i try fastboot oem unlock it says enable that option under developer options.
I am now with a brick Nexus 6 please help me out of this situation.

openbook said:
I erased everything on my Nexus 6 and then tried using the flash-all.bat from image-shamu-lmy48i.zip.
It failed saying could not allocate so many bytes.
Accidentally i did lock my bootloader using fastboot oem lock.
Now cant load anything and my phone doesn't boot.
When i try fastboot oem unlock it says enable that option under developer options.
I am now with a brick Nexus 6 please help me out of this situation.
Click to expand...
Click to collapse
No matter how many times this question is asked, unfortunately, the answer is still, there is no fix.
This has been happening since the nexus 6 went to 5.1 and has been documented numerous times. A bit of reading beforehand is all that is needed to avoid this situation.
RMA is the only option.

Evolution_Tech said:
No matter how many times this question is asked, unfortunately, the answer is still, there is no fix.
This has been happening since the nexus 6 went to 5.1 and has been documented numerous times. A bit of reading beforehand is all that is needed to avoid this situation.
RMA is the only option.
Click to expand...
Click to collapse
I did unlock before and rooted the phone and i was using it.
Does it mean my warranty is also void and no more support?
Is any devs working on fixing this problem?

openbook said:
I did unlock before and rooted the phone and i was using it.
Does it mean my warranty is also void and no more support?
Is any devs working on fixing this problem?
Click to expand...
Click to collapse
It's a security feature since 5.1. You cannot.unlock the bootloader without first setting "enable oem unlock". If you unlocked before 5.1, then you most likely didn't do this as it wasn't needed. So now you're locked and there is no way to unlock it.
Some devs may be looking into it, but if they are, they have been looking into it for a long time. It's extremely unlikely there will be a solution for this that doesn't come from Motorola. It could be an easy fix if Moto Wanted. They could provide a stock recovery flash able fully signed, rom.zip. This wouldn't bypass security either because you would still need your unlock code / google password to boot the device. But so far, we've heard nothing
Send it in to them. If you haven't got TWRP installed, there is nothing you can do. There's no reason for them to void warranty

stuck in boot loop android is starting optimizing apps after update

sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance

viper1402 said:
sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
Click to expand...
Click to collapse
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.

simms22 said:
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
Click to expand...
Click to collapse
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply

viper1402 said:
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
Click to expand...
Click to collapse
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.

simms22 said:
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
Click to expand...
Click to collapse
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?

viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
I'd suggest avoiding the OTA's and fastboot flash the latest factory image. LMY48I
IMHO....

viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
is it worth it? YES! if you want, you can flaah the factory image for 5.1.1 instead of taking the ota. but chances are that the ota will be fine.

viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great ?

boxa72 said:
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great
Click to expand...
Click to collapse
As stated before. Forget OTA. Unlock bootloader and fastboot flash the images manually. Do not take OTA with bootloader locked. If OTA fails have to RMA. No fix.

I had the same issue today and like PRDOG1 said I was talking to him on my forum post. As soon as you get the phone unlock that bootloader, then just do flashes through the bootloader. It is safer, and as long as that bootloader is unlocked you can go ahead and load up any image you want thats factory and you will be fine.

Well it should be fine then coz the carriers in Aussie don't lock bootloaders. I just told him to bring the phone to me n I'll re-flash a stock image for him but I thought u may have found another way as I'm more familiar with Samsung and Windows than I am with Nexus. It seems pretty common this bootloop stuff after OTA with the N6.
Sent from my SM-G920I using Tapatalk

I suspect you are confusing carrier SIM lock with bootloader lock.
Carriers do not usually do anything with bootloader lock - they may force a SIM lock to their SIM cards however.
On the Nexus 6 however, unlocking the bootloader is pretty easy (assuming you can boot to the OS and select the option to allow OEM unlock). I'd recommend leaving the bootloader unlocked and flashing twrp asap, in case of any issues later.

Altho in Australia they don't carrier lock bootloaders the software comes locked for security reasons. If he didn"t unlock prior to the OTA update it is bricked and will require RMA.

Bricked Nexus 6

Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John

if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.

droidstyle said:
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
Click to expand...
Click to collapse
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?

hadifreestyler said:
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
Click to expand...
Click to collapse
no you are bricked unfortunately. the unlock bootlader option in dev options really seems to have caused more issues then good.
I am wondering if Jtag will fix these devices?

jpl81905 said:
Suggestions?
Click to expand...
Click to collapse
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.

scryan said:
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
Click to expand...
Click to collapse
Thank you. I think.

jpl81905 said:
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
Click to expand...
Click to collapse
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM

backdown00 said:
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
Click to expand...
Click to collapse
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.

danarama said:
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
Click to expand...
Click to collapse
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.

backdown00 said:
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
Click to expand...
Click to collapse
..but even so, your method is overkill. It is really simple to boot into TWRP and look in the menu for the "Enable MTP" option. Once that is done, the phone appears in "Computer" as an MTP device, just like when you boot into android. Then, simply dragging and dropping a ROM onto that device then flashing it via recovery will get him back up and running. There is nothing simpler or quicker than this.
Sorry, I do not intend to be confrontational here.