Related
If we had s-off but a locked bootloader, would there be a way to unlock the bootloader without notifiying HTC through HTCdev? Or does an unlocked bootloader essentially come with s-off?
I am wondering because I would prefer not to notify HTC of the unlock unless I absolutely have to. Obviously...
I don't know the answer to you first question but, I do know that unlocked bootloader does not give you s=off.
Yes but I'm asking if s-off gives up an unlocked bootloader. Or if the only way to unlock it is to use HTCdev
Confirmed. I'll wait a while before using htcdev.
I don't think we'll know for sure, until the S-Off method is found (which may be soon?). And there are plenty here that know more than I. But S-Off should be security off for everything, and let you do whatever you want, so I don't think you need bootloader unlock on top of that.
I could be wrong but unless HTC has some sort of counter in the phone how would they know you unlocked? If we ever got s-off you would just push the stock hboot etc and no flags would be thrown. Just because you generate a token, doesn't mean you went through with unlocking the device. Again, I didn't read HTC's fine print when unlocking though.
mbh87 said:
I could be wrong but unless HTC has some sort of counter in the phone how would they know you unlocked? If we ever got s-off you would just push the stock hboot etc and no flags would be thrown. Just because you generate a token, doesn't mean you went through with unlocking the device. Again, I didn't read HTC's fine print when unlocking though.
Click to expand...
Click to collapse
Wow that's absolutely hilarious LOL I never once stopped to think with my puny brain that we could indeed generate tokens without unlocking. Haha so funny. And yes if we could hide it, it would be great, but I read that no matter what you do the boot loader will always say RELOCKED and not LOCKED. Or tampered, something of that sort.
I think we can fix that with s off. I could be completely wrong though.
Sent from my HTC One X using Tapatalk 2
From what I've been reading, any and everything can be accomplished with s-off. We can make the phone microwave food with s-off. PS they are trying some s-off methods with a members phone today. We shall see
Yep, S-Off means all partitions are writeable, and nothing is locked (except possibly SIM lock). I'm not personally clear what exploit is being used to get S-Off, but if it doesn't involve HTCDev (which my guess is that it wouldn't) than I don't see any way for HTC to track you. But all of this will hopefully be definitively answered very soon once a method is deployed . . .
seh6183 said:
If we had s-off but a locked bootloader, would there be a way to unlock the bootloader without notifiying HTC through HTCdev? Or does an unlocked bootloader essentially come with s-off?
I am wondering because I would prefer not to notify HTC of the unlock unless I absolutely have to. Obviously...
Click to expand...
Click to collapse
If you go through HTC are you supposedly giving up your warranty?
Sent from my HTC One X using Tapatalk 2
mobilehavoc said:
If you go through HTC are you supposedly giving up your warranty?
Click to expand...
Click to collapse
Yup. They tell you explicitly when you unlock the bootloader that you are voiding your warranty.
I think reports vary a bit on what HTC will actually do if you send a phone in with a hardware defect and its BL unlocked. I was reading a while ago on the International One X forum that they will still honor your warranty if you are BL unlocked and there is a hardware defect, as long as a custom ROM was not installed. But if you flashed a custom ROM they can somehow tell (even if you returned to stock) and deny your warranty. At least that was one guys experience over in the International forum.
S-OFF > Unlocked Bootloader, especially when HTCDev is involved. I've been holding off on the HTCDev unlock to see if we can get S-OFF, but now that some awesome ROMs are becoming available... I may just crack!
Billy
Stop worrying so much. Unlock it and enjoy it. No need to stress, it's not a car, it's a phone. Itll be fine. did u get the aftermarket or accidental warranty? If so, and you need it replaced, use that warranty if htc doesn't fix it. That's if they deny it and if they do they'll give you a repair cost, hopefully affordable. I would think though they would only deny it if unlocking caused the failure. If the flash goes out or dust under screen or volume rocker fails or USB port dies... They would probably fix it. No way unlocking it could cos those things to fail.
Well I'm banking on the fact that we will get s-off anyway and be able to remove the evidence of it ever being unlocked. I can just argue that I didn't actually unlock the bootloader and only generated the code. Either I honestly don't care anymore because I just got a great insurance plan that was only 58 for a year and covers EVERYTHING with only $75 deductible.
Also its funny that you say they would cover dust under the screen. I had an Inspire a while back and tried to get it repaired under warranty for dust under the screen (the battery door let a ton of dust in) and they would not cover it. I was so pissed about it and the way they handled it I swore to never buy another HTC product.
And then they released the most beautiful phone in the world.
seh6183 said:
Well I'm banking on the fact that we will get s-off anyway and be able to remove the evidence of it ever being unlocked. I can just argue that I didn't actually unlock the bootloader and only generated the code. Either I honestly don't care anymore because I just got a great insurance plan that was only 58 for a year and covers EVERYTHING with only $75 deductible.
Also its funny that you say they would cover dust under the screen. I had an Inspire a while back and tried to get it repaired under warranty for dust under the screen (the battery door let a ton of dust in) and they would not cover it. I was so pissed about it and the way they handled it I swore to never buy another HTC product.
And then they released the most beautiful phone in the world.
Click to expand...
Click to collapse
details on that insurance please? that's fantastic
gunnyman said:
details on that insurance please? that's fantastic
Click to expand...
Click to collapse
Ensquared.
Thanks signed up and canceled the overpriced att insurance.
gunnyman said:
Thanks signed up and canceled the overpriced att insurance.
Click to expand...
Click to collapse
It's the least I could do for you essentially being responsible for the 1.85 root.
Hey guys, I'm considering going with they option of rooting my HTC Sensation, but I'd like to clear something up beforehand.
At the moment Im on a pay monthly contract with my HTC Sensation and I pay monthly for insurance on the handset, before I go rooting my phone, if for some reason I need to send this phone off to my provider will my insurance be void? Or is this just the case if I haven't managed to return the phone to stock setup?
Id really like to try rooting my phone, but I dont want to have the problem of not being able to send the phone off for repairs or whatnot in the future. By repairs, obviously Im not referring to any problem that could occur during the rooting process, I mean more in the sense of hardware issues etc.
Any help is appreciated, and I apologise if this has been asked/answered before, I did do a forum search but found nothing.
Thanks.
You can S-Off your device without unlocking the bootloader over HTCdev. This way you can root and flash custom ROMs/kernels without loosing your warrenty.
If you have issues and you have to send the phone in, you can just run an RUU for you phone and S-On it again. Nobody would know that you have rooted it.
And if you want to S-Off take a look at the Hboot version! Hboot 1.2x has a different and more difficult way of S-Off'ing.
Oh right, how would I go about S-off'ing my phone? Would it still require me to go through the whole root process first off?
Thanks for your help
First we have to know your H boot version to direct you to the proper guide. To find out, pull battery, put battery back in, then at the same time press power and volume down button. Hold. Then you will see a screen pop up. Look at the information on Top of the screen. Then tell us your H Boot version. by the
Way, I also pay insurance every month on my device and I'm rooted and S off. If anything should happen I would restore back to stock and S on again. This way they would not know device was rooted. Hope this helps.
Sent from my HTC Sensation
Just did as you asked and my H boot version is 1.27.0000. That is what I was curious about, the whole insurance deal.
My main reason for considering rooting is to be able to theme my phone a bit more than what a launcher lets me, so what is recommended for this, just rooting, just S-off'ing or both?
Thanks
Gaz1521 said:
Just did as you asked and my H boot version is 1.27.0000. That is what I was curious about, the whole insurance deal.
My main reason for considering rooting is to be able to theme my phone a bit more than what a launcher lets me, so what is recommended for this, just rooting, just S-off'ing or both?
Thanks
Click to expand...
Click to collapse
Both process are reversible, once its s-off and rooted, just dont change your hboot and your good to go. I had the same concern, yet when i needed to return my phone for the warranty, they never even cared and sent me the other one without question (after i turned back the s-on of course). Follow Ganesh's guide here: https://www.google.com/url?q=http:/...ds-cse&usg=AFQjCNGNDWtlRFM7pBTIlQr-Y6Vd4nJEgw
Very easy and completely safe!
BoB!!
I suggest rooting and S off. I don't regret it for a second! I try all kinds of awesome roms and I'm able to customize to exactly how I want things! It's been a totally positive experience for me. As I mentioned in above post, I too pay the extra insurance monthly. If there we're a issue I'd return to stock. As above member mentioned he did it and didn't have any problems. I think once your rooted and s off you will be very happy. But do take the extra effort to s off because it's worth it in the long run and makes things easier for you, You will have the ability to do more with s off. Best wishes.
Sent from my HTC Sensation
Oh right, thanks you guys. I now feel more able to go ahead and root, now I just need to decide whether I think Im capable of doing it correctly.
Just had a look at that link you posted BobThaBear, it looks abit on the daunting side so Im going to have a long, hard think about it first.
Thanks for all of the help though, its very much appreciated
some time in the past week, i accidentally dropped my HTC one X and the LCD screen broke (several cracks) which obviously would require a replacement but the phone is still usable, i can still call/text, literally everything except of course the screen is cracked.
So i went to the nearest HTC service center and the screen replacement would cost $260 (converted to dollars from my local currency) PLUS $150 because im using a different ROM (MIUI to be exact) and not the stock ROM.
theyre asking me to pay an additional fee because im using a different ROM and a rooted phone, I only wanted to replace my LCD screen. the OS is still working! and they were saying some technical stuff like the board was broken and other reasons they could think of to persuade me.
now my question, is it still possible to 'unroot' my phone and bring it back to the HTC stock ROM, without a trace of being rooted previously?
this topic is also related to my other post "How to get RUU - i need it to revert back to stock ROM"
pedenski said:
some time in the past week, i accidentally dropped my HTC one X and the LCD screen broke (several cracks) which obviously would require a replacement but the phone is still usable, i can still call/text, literally everything except of course the screen is cracked.
So i went to the nearest HTC service center and the screen replacement would cost $260 (converted to dollars from my local currency) PLUS $150 because im using a different ROM (MIUI to be exact) and not the stock ROM.
theyre asking me to pay an additional fee because im using a different ROM and a rooted phone, I only wanted to replace my LCD screen. the OS is still working! and they were saying some technical stuff like the board was broken and other reasons they could think of to persuade me.
now my question, is it still possible to 'unroot' my phone and bring it back to the HTC stock ROM, without a trace of being rooted previously?
this topic is also related to my other post "How to get RUU - i need it to revert back to stock ROM"
Click to expand...
Click to collapse
It is possible, using an RUU to relock the bootloader and unroot the phone, but where the bootloader says ***TAMPERED*** and ***UNLOCKED*** now, it will change to ***RELOCKED***. AFAIK, there is no way to make the boatloader show ***LOCKED***", it will forever show ***RELOCKED***, unless you unlock it again. So basically there will always be some trace of your phone having been unlocked. Someone else pointed out that, aSsuming you've followed the most popular unlock guides, you had the use the HTC Dev site to get a file, and that since you did that, it's also on record on some server someWhere that you have unlocked your phone.
So basically, unless it's a know manufacturing defect, you are most likely screwed. Don't quote me on that though, as there are always stories of people saying the right things to the right people and getting their devices replaced where most others were not able to.
garfnodie said:
AFAIK, there is no way to make the boatloader show ***LOCKED***", it will forever show ***RELOCKED***
Click to expand...
Click to collapse
You can change the flag back to LOCKED if you S-off: http://forum.xda-developers.com/showthread.php?t=2168578
But as mentioned, HTC presumably has some record of you unlocking the bootloader via the HTCDev.com website.
Plus, there was a thread a while back on the "international" One X forum section where people were reporting that HTC was honoring the warranty for phones with unlocked bootloaders; but denying warranty service for unlocked bootloader if a custom ROM was every installed (even if the phone was returned to the stock ROM before sending in for warranty). So apparently, HTC has some way of knowing a custom ROM was ever installed, even if its no longer on the phone.
A question for the OP: have you tried going through your carrier for a repair? Some carriers (such as AT&T) seem to be much more forgiving about modding the phone, and might forego any "custom ROM" fee.
$150 extra to replace a screen because you have a custom Rom? They have no relation. Find someone else to do the repair, or just order the parts and do it yourself. Not very hard to do, order LCD+digitizer, and watch some you tube videos on the process.
Sent from the HOXL dimension of S-OFF
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
I'm guessing you were SuperCID, and S-on? If so, sorry to say you are now bricked.
Should have read this, stickied to the top of General: http://forum.xda-developers.com/showthread.php?t=2181929
Wow. The level of suck here is amazing. Thanks. Nothing that can be done at all?
Jonathan_A said:
When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing.
Click to expand...
Click to collapse
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
redpoint73 said:
Does the phone power on at all? Its not clear when you say "power it on" whether you are talking about the phone or the computer.
Any charge LED when the phone is plugged to USB or the wall charger?
Any message about QHSUSB_DLOAD drivers popup on the computer when you connect the phone by USB? If you get this, and no charge LED, you are bricked.
Click to expand...
Click to collapse
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Jonathan_A said:
I meant the phone, when I power the phone on, I hear the device connect sound through the computer. No charge LED, but I do get the QHSUSB_DLOAD in device manager. So crap . Thanks for your help (not sarcasm). Level of stupidity/annoyance that I'm feeling right now is OVER NINE THOUSAND. Can't believe I missed a sticky. Thanks a million for the informative thread there though, I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Everyone makes stupid mistakes once in a while. But yeah, that really sucks. If you have access to a Linux computer, you might try the JET tool in Development, or check the unbricking thread in General. But I don't think anyone has been able to come back from this after the 3.18 RUU or OTA + SuperCID.
Beyond that, you can try to find a repair shop that will JTAG the phone. It will cost you, but better than buying a new phone.
iElvis said:
Some people have resurrected their phones from this using the JET tool. Failing that, it's fixable via jtag, though it wil set you back about $100.
Click to expand...
Click to collapse
Well, it's still under warranty, and I'm hoping that since the bootloader was relocked and the RUU technically succeeded, they'll just send me a new one or something. Though I'll take a whack at the JET thing if I can find my Linux live CD... Thanks a ton, I'm feeling pretty dumb here and you guys have been really helpful.
Jonathan_A said:
I'll never use an RUU again, bet your bottom dollar.
Click to expand...
Click to collapse
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
redpoint73 said:
RUU is usually a safe thing to do (typically its a good tool for recovering from all sorts of issues). It really shouldn't cause a brick, and nobody is really sure why it does in this case. So really, its kind of an honest mistake. Its folks that OTA while rooted, etc. without doing any reading that I kinda wonder about.
Click to expand...
Click to collapse
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Jonathan_A said:
Ah well, thanks for making me feel less stupid I guess I meant that I'll do some checking before I RUU again, heh.
Click to expand...
Click to collapse
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
Good luck bud!
Sent from my HTC One X using xda app-developers app
Jonathan_A said:
Well, we'll see. I'm sending it back tomorrow, will update on what happens. Praying that it gets a really lazy reviewer or something, haha.
Click to expand...
Click to collapse
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
iElvis said:
HTC will give you some grief. AT&T doesn't appear to care and from what I have seen has happily replaced lots of bricked phones without being concerned about relocking.
Click to expand...
Click to collapse
Ooh, thanks. Good to know. They'll be my next try. You all have probably just saved me ~$300
Jonathan_A said:
I used the jellybean RUU from HTC after relocking my bootloader, and now it won't "turn on." When I've got it plugged into the computer and I power it off and on, I can hear the device connect/disconnect sounds, but my screen does nothing. Any help appreciated.
Click to expand...
Click to collapse
Happened to me too :c Has anyone had any luck using JET?
If the emmc partition table is still intact its feasible, but im pretty sure the ruu/ota kills it upon install. who knows why. seems to be a security "feature" since s-off seems to work fine.
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
I had a similar issue where my screen wouldn't turn on but it was still on and usable. I went to the AT&T store and got a replacement. Tell them you installed the AT&T update and then the screen stopped working. They probably won't be able to fix it but they'll give ya a new phone if you're under warranty. My phone was far from stock (rooted, bootloader unlocked, S-off, custom kernel and ROM), and they still gave me a new one. Make sure you go to an AT&T store though, I tried three different Best Buys and they were all noobs that had no idea what to do.
Edit: Didn't read post above so you can disregard this. But if you go to a store they can give you a new one on the spot instead of having to wait for one to be shipped to you.
Jonathan_A said:
Just called AT&T, they're sending me the replacement and then I send this one back in the box that the replacement came in and then the replacement is free. They said that they basically can't do anything with the dead one since it's dead, so I think all's well that ends well? Updates as events warrant, if need be. Thanks so much Redpoint73, iElvis, and exad.
Click to expand...
Click to collapse
Since the phone is bricked, there is really no way of them knowing (by checking the phone anyway) that you modded it. And as mentioned, AFAIK there has never been a reported case of AT&T denying warranty service due to the bootloader having been unlocked (and probably aren't even going to check). AT&T is much less strict then HTC, as its in AT&T self interest to keep you as a happy customer (paying that big old monthly bill), rather then fight over something like a single warranty exchange.
There have been some cases of the OTA randomly bricking devices that are fully stock (and probably possible with the RUU as well). Any time you mess with the hboot, if things get interrupted somehow, its possible to brick the phone. So for all AT&T knows, this is what happened in your case.
I'm normally not a big fan of making a warranty claim for your own negligence, and as a result of you modding the phone. But I suppose this is a bit of a gray area, since the RUU really shouldn't brick the phone solely due to SuperCID.
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
exad said:
Unfortunately HTC will be of no help as once you unlock the bootloader, even if you relock and the RUU bricks you, that's the end of your warranty.
The Carrier would usually be your best bet but they will most likely charge you to fix it
In this Case a Jtag will probably be your cheapest option. That isn't to say you shouldn't try HTC and your carrier first, just keep this in mind as it's most likely how things will go.
I'm speaking from experience of course. As I have bricked a one X the same way you did before it was known that super CID + S-ON + ruu = brick
Click to expand...
Click to collapse
Did HTC actually deny your warranty service due to a record of you having unlocked the bootloader? Just curious, because it would be the first I have heard of that actually happening.
Yes, as the warning state when you unlock the bootloader, it voids the warranty (at least in theory). But in actual practice, whether they honor the warranty or not after BL unlock seems to be much more of a gray area.
Its true that the carrier will be more lenient than HTC. But I know there was some discussion on the "international" (quad core) One X forum, where HTC was actually honoring the warranty if the bootloader was unlocked. But they were actually denying warranty service if any custom ROM had ever been installed on the device. Even if the device was returned to the stock ROM before sending in. So apparently, they have some way of knowing a custom ROM was previously installed (even if uninstalled). If the phone was bricked, I wonder if they would still be able to check this?
Of course, how HTC honors the warranty may also vary from region to region.
I first unlocked my google pixel (Verizon) bootloader, i then went on to try to root it. This went on to go into a boot loop. Me being dumb, forgot that you can just flash the stock firmware. I locked the bootloader. Now im stuck, when i try to boot it gives me the "Your device is corrupt" screen and it goes to the white battery display. I try to reinstall stock firmware and it says i need an unlocked bootloader. In order for me to unlock the bootloader i need usb debugging enabled. I can't get into the phone to enable it so im at a stuck point... I really would appreciate some help. I have extended warranty if Verizon can do anything with that.
Unfortunately, the instructions were pretty clear to not relock the bootloader unless the phone was 100% stock. From what I've seen, you are stuck. Haven't heard anyone recovering from relocking the bootloader with a bad install.
You made the decision to void your warranty when you unlocked the bootloader, so Verizon owes you nothing (extended warranty or not). That being said, they may replace it if you "played dumb" and said it happened during an update, but that poses an ethical quandary. So it's up to you how to proceed.
thanks for the reply
stranula said:
Unfortunately, the instructions were pretty clear to not relock the bootloader unless the phone was 100% stock. From what I've seen, you are stuck. Haven't heard anyone recovering from relocking the bootloader with a bad install.
You made the decision to void your warranty when you unlocked the bootloader, so Verizon owes you nothing (extended warranty or not). That being said, they may replace it if you "played dumb" and said it happened during an update, but that poses an ethical quandary. So it's up to you how to proceed.
Click to expand...
Click to collapse
Thanks a ton, yeah gonna try that "playing dumb" tactic today, was thinking the same thing... lets hope it works.
This is why providers lock bootloaders. Passing the cost to them instead of owning up to your screw up. Im sorry you bricked your device but that cost should be on you not verizon.
Sent from my Pixel using Tapatalk
jbjancuski said:
Thanks a ton, yeah gonna try that "playing dumb" tactic today, was thinking the same thing... lets hope it works.
Click to expand...
Click to collapse
For your sake, I hope it works. But, as I said, this is ethically questionable (on a personal level) and wrong on a grander level. You took responsibility when you unlocked the bootloader. If you are fortunate and Verizon gives you a new one. Either leave it stock, or read more thoroughly before making changes to your phone.
maulich said:
This is why providers lock bootloaders. Passing the cost to them instead of owning up to your screw up. Im sorry you bricked your device but that cost should be on you not verizon.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Unfortunately, this is absolutely the case. When we make the decision to do things to our phones that operators don't want us doing, we are accepting responsibility for the phone, and if we brick it we should deal with that consequence. But of course, some people aren't really prepared for this reality, and want someone else to get them out of it.
Agreed.......i have had to pay the piper before for my screw ups. Even a brand new device of my wifes that i was trying to get twrp on. Phone was less than 6 hours old and rendered a paper weight. Expensive lessons are a part of life.........The sad thing is verizon will get a ton of these returned for this very thing, and it will only force them to lock down the bootloader even better hurting the individuals who want a little freedom for a better price.
Sent from my Pixel using Tapatalk