Hey, I got my replacement phone only to find out that I can't root my OTA! Apparently the phone provided by Asurion was running 2.1 OTA as stock and the HBOOT version was 1.49? Does this mean that future versions will be running 1.49 or will it stay at 1.47, and for how long?
Same here. My New eris (not refurb) came in today with 2.1 (2.36.605.1 CL165907) with hboot 1.49 installed (PB0010000).
-------------------------------------
Sent from my EvilEris using TapaTalk
Might be a good thing or a bad thing. We might be able to get the 1.49 bootloader from these new 2.1 OTA phones and so allow us to root.
was my thought as well.
-------------------------------------
Sent from my EvilEris using TapaTalk
I wonder if they used to belong to people who couldn't wait and installed the leak, then claimed their phone broken so they could have them replaced. Refurbs that were once leak. Sound like a bad porno.
-------------------------------------
Sent via the XDA Tapatalk App
I highly doubt that, because we don't have a 2.1 OTA update for the 1.49 hboot. If they didn't have that, then there's no way Asurion could have updated the leaks. If they DID update the leaks, then how come they aren't releasing it to the public?
V3 is the leak. The only difference is the hboot.
-------------------------------------
Sent via the XDA Tapatalk App
Just an FYI that I'm rooted (currently running leak4base) and my HBOOT is 1.49.
fritzel67 said:
Just an FYI that I'm rooted (currently running leak4base) and my HBOOT is 1.49.
Click to expand...
Click to collapse
really? huh
fritzel67 said:
Just an FYI that I'm rooted (currently running leak4base) and my HBOOT is 1.49.
Click to expand...
Click to collapse
I'd like to learn more about this, PM / post here how you did it please. I haven't been keeping up with the other devs lately but last I checked thats the leak 2.1 rom's hboot version. Maybe there are some differences in your 1.49 and the leak 1.49, and we may be able to use that to our advantage, as there are ways to change the nvram that we found earlier.
Yeah 1.49 s-on bootloader out of the box won't get you root.
anyone want to trade an eris with 1.49 for one with 1.46? lol had my hopes up this morning.
homer169 said:
I wonder if they used to belong to people who couldn't wait and installed the leak, then claimed their phone broken so they could have them replaced. Refurbs that were once leak. Sound like a bad porno.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I've returned three different Eris handsets with various 2.1 leaks on them. The first one I didn't ask for, Verizon just randomly sent me a new phone, so I swapped them. I thought maybe there was a recall, but apparently they're just idiots. The other two were because the trackballs failed. I've been afraid that they would go to refurb these, see the 2.1 leak, then charge me for the replacement.
jcsugrue said:
I've returned three different Eris handsets with various 2.1 leaks on them. The first one I didn't ask for, Verizon just randomly sent me a new phone, so I swapped them. I thought maybe there was a recall, but apparently they're just idiots. The other two were because the trackballs failed. I've been afraid that they would go to refurb these, see the 2.1 leak, then charge me for the replacement.
Click to expand...
Click to collapse
I ran through 6 bb storms, all for hardware issues, and I never got hit for the leaks I had left on them.
homer169 said:
V3 is the leak. The only difference is the hboot.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
You mean v3 is the OTA? Only difference is the setup program to get the phone going (the OTA is intended to move from 1.5, the v3 leak is a complete wipe/flash).
HBOOT doesn't upgrade with OTA.
Do any of you want to see if this isn't just the 2.1 leak v3? Hope I can help. Here's all my info:
Firmware Version: 2.1
Baseband version: 2.42.00.04.12
Kernel version: 2.6.29-8a03cb9a | [email protected] #1
Build number: 2.36.605.1 CL165907 release-keys
Software number: 2.36.605.1
Browser version: WebKit 3.1
PRI Version: 2.11_002
PRL Version: 51866
ERI Version: 5
ANOTHER QUESTION: Why can't we just have the root running the HBOOT 1.49?
If there was root with hboot 1.49 that would mean that those of us on the OTA leak would get root too right?
crax0r said:
Do any of you want to see if this isn't just the 2.1 leak v3? Hope I can help. Here's all my info:
Firmware Version: 2.1
Baseband version: 2.42.00.04.12
Kernel version: 2.6.29-8a03cb9a | [email protected] #1
Build number: 2.36.605.1 CL165907 release-keys
Software number: 2.36.605.1
Browser version: WebKit 3.1
PRI Version: 2.11_002
PRL Version: 51866
ERI Version: 5
ANOTHER QUESTION: Why can't we just have the root running the HBOOT 1.49?
Click to expand...
Click to collapse
That's actually does seem to be a rather strange combination - it seems you have a locked bootloader but the OTA install.
Someone over at Androidforums posted a HTC ROM decoder ring tonight, and from all appearances, you have a mystery combination that does not appear natural.
My bet is on someone who went crazy with fastboot after the 2.1OTA, and wasn't paying attention.
Who wants to bet that techs for Asurion just FR the phone with the (2.1) stock recovery boot - that clears out phone activation as well as /data.
bftb0
erisuser said:
If there was root with hboot 1.49 that would mean that those of us on the OTA leak would get root too right?
Click to expand...
Click to collapse
There actually is a root with 1.49, provided you have 1.49 S-OFF (which is the engineering SPL). What I'm not clear on is where this came from (including how my phone went from .47/.48 to it. (I never installed a leak...just rooted 1.5 to 2.1 then ran custom ROM's...currently on leak4base)
From what I understand, 1.49 S-ON (leak users) cannot be updated with the engineering SPL because the phone sees it as the same or older and won't complete the update. And it can't be hacked, but it's digitally signed by HTC and any attempts to change it corrupt the authentication.
(I'm not 100% sure on all this so please correct any errors)
Does anyone know how I can get hboot 1.49 S-OFF?
Related
I have the leaked 2.1 v3 does that mean i rooted my phone to put it on it? Is my phone now rooted?
No. Your phone is not rooted. Leaked v3 is essentially the same as the upgrade from Verizon.
-------------------------------------
Sent via the XDA Tapatalk App
and because i have V3 im not able to Root right?
yes
Sent from my Eris using the XDA mobile application powered by Tapatalk
So NO custom ROMS for me...this sucks
Yep. You, me, and loads of others using the leaked versions. Not to worry though. the devs are working on rooting the leak for us. It may take some time so just be patient.
-------------------------------------
Sent via the XDA Tapatalk App
I'm hoping soon too, I just got a replacement with 2.1 and 1.49 hboot loaded because mine had trackball issue. The original was the same but thought I was going to get lucky with replacement. Guess I was wrong.
-------------------------------------
Sent via the XDA Tapatalk App
hang tight guys, devs are still working on root for leakers. they're looking at a couple attack vectors and will notify everyone once they've got something working
jestercing said:
I have the leaked 2.1 v3 does that mean i rooted my phone to put it on it? Is my phone now rooted?
Click to expand...
Click to collapse
What exactly is it that makes you think you have leak-V3?
Check your bootloader version (power phone up holding Vol-down+End/Power).
If it says 1.47.xxxx (S-ON), you can root
if it says 1.49.xxxx (S-OFF), you have already rooted
if it says 1.49.xxxx (S-ON), you have put a "leak" (V1, V2, or V3) on your phone and can not root.
Then, reboot and look at Settings->About phone->Software information. If you put a leak on there, you should be able to decipher which one it was by looking at this post on Androidforums.com
Note that you can not tell the difference between the OTA-2.1 and Leak-V3 from the O/S software information alone - determine that by looking at the bootloader (HBOOT) Version number and security status (S-OFF vs. S-ON).
bftb0
I have HBOOT 1.49 and I have S-OFF and I'm currently not rooted.
crax0r said:
I have HBOOT 1.49 and I have S-OFF and I'm currently not rooted.
Click to expand...
Click to collapse
There is only a single 1.49 S-OFF bootloader "in the wild" - and it is from the ROOT ROM.
That does not mean that you must have a rooted OS on top of it - you can "root" the Eris, in the sense of installing that very bootloader (1.49 S-OFF), and then back-install any OS you like on top of it (manually).
For instance, I have had stock 1.5 running on my phone for experiments, but with the root (1.49 S-OFF) bootloader sitting there as the bootloader. The "O/S" is not "rooted" - but the bootloader is there which would allow me to write anything I want to the phone. So, calling that "not rooted" is semantically accurate - if you are only talking about the OS on top.
Having said that, there is not a single chance that you have 1.49 S-OFF on your phone without it having been touched by the root-PB00IMG.zip HTC ROM at one point or another in its past. Either that or you work for HTC.
bftb0
Lucky you mine is s-on
-------------------------------------
Sent via the XDA Tapatalk App
Question,
I have 2.1 ota My HBoot is 1.46 and s=on
can this be rooted?
And why/how do I have Hboot 1.46 with 2.1 I havn't done anything but the OTA
[email protected] said:
Question,
I have 2.1 ota My HBoot is 1.46 and s=on
can this be rooted?
Click to expand...
Click to collapse
Yes.
[email protected] said:
And why/how do I have Hboot 1.46 with 2.1 I havn't done anything but the OTA
Click to expand...
Click to collapse
Your phone has the 1.46 bootloader precisely because it is an "older" phone (in relative terms), and also because it has only seen OTAs in it's operating history - the OTA process for the Eris has never replaced the bootloader. (There have been 3 OTAs now, and none of them replace the bootloader.)
Good luck with the rooting!
bftb0
Thank exactly what I needed to know.
Now off to root (screw up) my phone
Ok,
Want some input before i do this and screw something up.
I'm currently running Scott's CleanROM ICS (built off the VM leak)
I honestly have no idea what FW (stock sprint, stock VM, modified, etc) i have.
I basically want to get my phone back to bone stock, all sprint software (FW, Radio, OS, etc) and go from there
What is the easiest way to get this done? And once i do, and upgrade to the latest OTA, is there a way to root HBOOT 1.58? All i really want root for is to WiFi tether..
Suggestions appreciated.
johnnyphive said:
Ok,
Want some input before i do this and screw something up.
I'm currently running Scott's CleanROM ICS (built off the VM leak)
I honestly have no idea what FW (stock sprint, stock VM, modified, etc) i have.
I basically want to get my phone back to bone stock, all sprint software (FW, Radio, OS, etc) and go from there
What is the easiest way to get this done? And once i do, and upgrade to the latest OTA, is there a way to root HBOOT 1.58? All i really want root for is to WiFi tether..
Suggestions appreciated.
Click to expand...
Click to collapse
This belongs in Q&A brah...
AAAAAAAHHHHHH.!!!!!!! (-_____-)
Someone please ban these ppl that can't follow rules, this has to stop, dude ain't a noob, been a member since 2010
Sent from my PG86100 using Tapatalk 2
ognimnella said:
AAAAAAAHHHHHH.!!!!!!! (-_____-)
Someone please ban these ppl that can't follow rules, this has to stop, dude ain't a noob, been a member since 2010
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
This is just like the last time :'(
Sent from my PG86100
Where to start....well how about development is for well development and I know this sounds obvious but I guess this needs to be said seeing the circumstances....questions go to the Q&A section seeing as its a question and answer section....(that's what q&a stands for in case you didn't know)
Ok, so i flash "RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109_signed"
via fastboot and now i'm back to the following:
Appears locked (Bootloader no longer says "revolutionary")
S-Off
HBOOT 1.40
Radio 0.97.10.0530
Android 2.3.3
Sense 3.0
Software Number 1.13.651.7
Kernal 2.6.35.10-gcb1cf83
PRI 1.42_003
PRL 21086
As far as i know / can tell, this is all stock sprint stuff, but retain s-off, have the ability to unlock and root?
What do i need to do from this point to get the the latest stock sprint stuff
johnnyphive said:
Ok, so i flash "RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109_signed"
via fastboot and now i'm back to the following:
Appears locked (Bootloader no longer says "revolutionary")
S-Off
HBOOT 1.40
Radio 0.97.10.0530
Android 2.3.3
Sense 3.0
Software Number 1.13.651.7
Kernal 2.6.35.10-gcb1cf83
PRI 1.42_003
PRL 21086
As far as i know / can tell, this is all stock sprint stuff, but retain s-off, have the ability to unlock and root?
What do i need to do from this point to get the the latest stock sprint stuff
Click to expand...
Click to collapse
Since you ran that ruu, you should have stock gingerbread. There is an ruu out there with the latest Sprint stock stuff (ICS). If you run that one, you will be ICS stock but still s-off.
I'm running:
Rooted 1.22.651.3
LazyPanda S-OFF
Hboot: 1.12.2222
Baseband: 1.02.12.0427
PRI: 2.28_003
PRL: 25010
Haven't updated ROM because I figured I'd wait till JB hit and bugs got ironed out. I also never updated firmware because everyone was saying that you you can never go back after you update. So, my questions:
1. Can I update to newest firmware while staying on an older ROM?
2. If so, should I?
3. Is there any reason to stay with an older firmware (assuming there are no compatibility issues)?
1. Yes
2. Yes
3. No, baring any compatability issues I'm not aware of.
I'm s-on hboot 1.12 and obviously wouldn't want to upgrade my hboot. I can do radio, but I guess that's it?
Sent from my EVO using xda app-developers app
In the Android Development forum there is a thread with the firmware. You can flash the one that says "no kernel/hboot/recovery". That way it'll just update everything else. There are a bunch of files that it flashes but I can't say exactly what each is for except for the radio.
Yes I went with stock with goodies and I have no regrets
Sent from my EVO using xda premium
JPHoss said:
Yes I went with stock with goodies and I have no regrets
Sent from my EVO using xda premium
Click to expand...
Click to collapse
That makes me feel better since I just downloaded it and will be installing it shortly!
I need help inrooting my Evo, I want to go with Jelly bean update but everytime i have tried to unroot i fail and lock my phone and i try by doing the OTA (heard that works and will remove root) but i can error when flashing the file.
If anyone could please help or point in the directions of some good links on how to remove root. Im currently on stock root 1.22.651.3
I didnt really like any of the roms and would rather just go with being unrooted.
Thanks.
vmgarcia15 said:
I need help inrooting my Evo, I want to go with Jelly bean update but everytime i have tried to unroot i fail and lock my phone and i try by doing the OTA (heard that works and will remove root) but i can error when flashing the file.
If anyone could please help or point in the directions of some good links on how to remove root. Im currently on stock root 1.22.651.3
I didnt really like any of the roms and would rather just go with being unrooted.
Thanks.
Click to expand...
Click to collapse
check in the development section.. there is a few threads on how to unroot..
If your HBOOT is 2.09 your hosed with bad radios.
See here:
http://forum.xda-developers.com/showthread.php?t=2074643
tankerkevo said:
If your HBOOT is 2.09 your hosed with bad radios.
See here:
http://forum.xda-developers.com/showthread.php?t=2074643
Click to expand...
Click to collapse
how do i see what hboot i have?
okay after trying to unroot my phone i think i bricked it, it stuck on the htc load up page, and if i try to turn it off it just turns back on. i cant even get into recovery mode, any help?
Read the link above. Sounds like you ran the 3.15 RUU and didn't get the radio update like the rest is us. You are SOL.
That said, you can get back into the phone, all you gotta do is HTC unlock the phone. Just be aware that unless you have the 1.12 radios any JB Rom, stock or custom, will have unstable radios. For an almost stable experience you will need to flash an old ICS Rom.
Sent from my EVO using xda app-developers app
I just arrived from the search button, and this is the closest question I have found to what I need, but I don't quite see an answer to where I am, but I figured I would ask here rather than bother everyone with a new post.
I'm on an HTC EVO 4G LTE rooted with supersu, teamwin and all that stuff. I can't quite remember what package I got, but I did it right when the phone came out and have been happily using it rooted since. I would like to go and either make my phone capable of getting the OTA sprint jellybean update, or find a flash rom that I can install.
I haven't done anything yet. My phone is still rooted and fully functional, but I want to get all the advice before risking anything. I did try to OTA update it earlier, but the Teamwin recovery program came up on the reboot.
Model: Evo 4G LTE
Hardware Version: 0003
Software Version 1.13.651.710RD
Android Version 4.0.3
HTC Sense: 4.0
HTCExtension version : HTCExtension_403_1_GA_8
PRI Version 2.28_003
PRL Version 25010
Kernel Version: 3.0.8-01360-g3fd0422 [email protected] #1 SMP PREEMPT
Baseband Version 1.02.12.0427
Build number 1.13.651.1_R2 CL60201 release-keys
Hi everyone,
AT&T published a new OTA update.
I am unlocked, rooted and have TWRP. Is this safe?
Also, any thoughts on the purpose of this? The change log says:
What's changing?
New FOTA enhancement – support for 1GB+ file size (OMA DI Client Update).
Is this a setup for the AT&T Marshmallow update?
Thanks.
When I received the message I thought it was going to be the MM update but it turns out it's some sort of LP update. Very disappointed. I can't find release notes as well.
Android Version: 5.0.2
Software Version: 4.28.502.8
Baseband Version: [email protected]_40.56.C33074.00_F
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: Android Version: 5.0.2
Software Version: 4.28.502.8
Baseband Version: [email protected]_40.56.C33074.00_F
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: 4.28.502.8 CL511189 release-keys CL511189 release-keys
I can find stuff on 4.28.502.1 and 4.28.502.2 but not Software Version: 5.28.502.8
The only difference I saw was the radio version in the bootloader. I realized the update wasn't MM and impatience got the best of me so I went ahead and flashed a GPE MM rom.
Gotcha gotcha. I couldn't make or receive calls with the MM ROMs so returned to stock AT&T. I hope the MM update is coming.
Sent from my HTC One_M8 using XDA-Developers mobile app
matt11601 said:
Gotcha gotcha. I couldn't make or receive calls with the MM ROMs so returned to stock AT&T. I hope the MM update is coming.
Click to expand...
Click to collapse
This is almost certainly due to AT&T specific deployment of Voice over LTE (VoLTE, which ATT calls "HD Voice") not playing well with non-ATT ROMs. You can call AT&T to have HD Voice option turned off on your account. Details in my post here: http://forum.xda-developers.com/showpost.php?p=62001970&postcount=28
Another option, you can try the stock Developer's Edition MM ROM here (just need to flash the ROM, don't need the flash the firmware; and s-off would be required to do so): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
The Dev Ed is designed to work on AT&T's network, so I'm guessing it shouldn't have the same voice call issue. Although I haven't personally ran into that issue, so I can't confirm that. Plus, the Dev Ed ROM is clean of AT&T branding and bloat, so IMO much better than any stock AT&T ROM, anyway.
redpoint73 said:
This is almost certainly due to AT&T specific deployment of Voice over LTE (VoLTE, which ATT calls "HD Voice") not playing well with non-ATT ROMs. You can call AT&T to have HD Voice option turned off on your account. Details in my post here: http://forum.xda-developers.com/showpost.php?p=62001970&postcount=28
Another option, you can try the stock Developer's Edition MM ROM here (just need to flash the ROM, don't need the flash the firmware; and s-off would be required to do so): http://forum.xda-developers.com/htc-one-m8/development/rom-stock-unlocked-developer-sense-7-t3262894
The Dev Ed is designed to work on AT&T's network, so I'm guessing it shouldn't have the same voice call issue. Although I haven't personally ran into that issue, so I can't confirm that. Plus, the Dev Ed ROM is clean of AT&T branding and bloat, so IMO much better than any stock AT&T ROM, anyway.
Click to expand...
Click to collapse
Yea I remember reading that post. It was very helpful but also disappointing because I had to return to stock. I'm hoping the MM update will come soon, but if not, may try the Dev Edition.
theandies said:
When I received the message I thought it was going to be the MM update but it turns out it's some sort of LP update. Very disappointed. I can't find release notes as well.
Android Version: 5.0.2
Software Version: 4.28.502.8
Baseband Version: [email protected]_40.56.C33074.00_F
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: Android Version: 5.0.2
Software Version: 4.28.502.8
Baseband Version: [email protected]_40.56.C33074.00_F
Kernel Version: [email protected] #1 SMP PREEMPT
Build Number: 4.28.502.8 CL511189 release-keys CL511189 release-keys
I can find stuff on 4.28.502.1 and 4.28.502.2 but not Software Version: 5.28.502.8
Click to expand...
Click to collapse
Still on .2 firmware
I'm very interested in getting the baseband update. ATT HTC M8 Unlocked S-off. I tried loading the stock ROM and using the OTA update, but it went into TWRP recoery mode and then only upgraded the software version to 4.28.502.8 not the radio. I've also tried the "manual" method using the utility provided by HTC and it hangs about 14% into the upgrade (I gave it a full 30 minutes before I gave up). Any help for this novice?
4/29/16: I'm such an idiot...flashed a stock recovery, so the the manual RUU method worked...except it was the update from last August, not the one from April 7, 2016. So now all that I've accomplished is to (it would seem) unroot, and factory reset. Going to leave as is until the 24 hour wait is over and can re-try the OTA. Maybe now it will work. Still unlocked and s-off.
Does anyone know the device location of the download? If so, I can post it since I haven't updated yet.
matt11601 said:
Does anyone know the device location of the download? If so, I can post it since I haven't updated yet.
Click to expand...
Click to collapse
I have been searching high and low for where on the device the download is stored!
Ok, so i ran RUU_M8[email protected]50319A_40.45.C33065.00_F_release_446225_signed_2
Then ran the april 7 OTA update on my unlocked, rooted, s-off M8. It all seemed to go great, and then bootloop. Tried factory reset, still hangs on HTC screen after ATT "bells". At least I know from the bootloader screen the stupid radio firmware was upgraded (that was the goal) I wish I had used TWRP to save a copy of the above RUU state before I went and did the OTA. Tried booting (not flashing) TWRP to load my last working ROM prior to the RUU which was CM-12 stable release-yay it booted! But if I need to go back to stock ROM I guess I'll need to downgrade with the RUU above?
---------- Post added at 09:38 PM ---------- Previous post was at 09:33 PM ----------
PS this does NOT solve the issue of not receiving phone calls while on a custom ROM the ATT LTE network...so a huge waste of time.
charger1969 said:
But if I need to go back to stock ROM I guess I'll need to downgrade with the RUU above?
Click to expand...
Click to collapse
You can typically on downgrade by RUU if you have s-off.
redpoint73 said:
You can typically on downgrade by RUU if you have s-off.
Click to expand...
Click to collapse
Yup I'm S-off
charger1969 said:
Yup I'm S-off
Click to expand...
Click to collapse
Then yes, downgrade by RUU is probably your best bet to get back to stock (until we have a newer RUU).
So I flashed the RUU 4.28.502.1 through HBOOT. It booted up to LL but I'm not able to update my phone at all. It will take the update file approx around 28MB but when it reboots after flashing the file it gets stuck at the HTC logo after the AT&T logo. I tried to reboot and restore the phone but it doesn't go anywhere. I would have to enter HBOOT again and flash the stock RUU file again to get the phone to boot up again.
Could anyone help me into the right direction? I'm trying to get MM eventually on it.
Sent from my Nexus 6P using Tapatalk
volcalstone said:
So I flashed the RUU 4.28.502.1 through HBOOT. It booted up to LL but I'm not able to update my phone at all. It will take the update file approx around 28MB but when it reboots after flashing the file it gets stuck at the HTC logo after the AT&T logo. I tried to reboot and restore the phone but it doesn't go anywhere. I would have to enter HBOOT again and flash the stock RUU file again to get the phone to boot up again.
Could anyone help me into the right direction? I'm trying to get MM eventually on it.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Sounds like you need to flash the last working ROM you have a back up of. I had the same bootloop issue, if you read post #11
Best,
charger1969 said:
Sounds like you need to flash the last working ROM you have a back up of. I had the same bootloop issue, if you read post #11
Best,
Click to expand...
Click to collapse
Thx I'm unlocked, rooted with s-off. My concern is that by doing the bootable RUU to LL which has stock recovery, why can't I take the OTA updates?
My last rom was actually stock KK with TWRP. I modded so much files so I would at this point I have do an RUU to update. I will probably do a KK RUU with stock recovery and take the LL update OTA. I could be missing something in between, dunno.
Thx
Sent from my Nexus 6P using Tapatalk