Develop Bugs

some guidance, direction or links please...

i want to to be safe. i have a tmobile variant and i would like to flash a stock unlocked and/or international rom or developer edition rom. i am guessing this will work but i will have to use gpe or tmobile radios. i haven't seen a clear path to this and i wish it was as easy as fastbooting or just flashing the proper stock nandroid. i am confused, between all the FUU's RUU's, different firmwares etc etc. is there a guide i overlooked to do this?
btw, i've converted to gpe but i went back for various reasons. the gpe just didn't have all the proper drivers to make it the premium phone the m8 is and be stock android, because i much preferred stock but sense is not too bad. helluva lot better than touchwiz. i am just concerned and don't want to brick. i had problems going back to sense. flashing my nandroid after the RUU just failed and failed. i thought i was gonna have to change underwear and get kleenex. ended up flashing my nandroid without md5 check and have had no problems since. i am aware of the CID situation and understand that. i assume i can do this with all 1's or a EU or unlocked cid. i think i understand the MID thing but would appreciate it if somebody clarified it for me. i assume that whatever i end up flashing i need to change my MID to the appropriate MID or change it in android-info.txt or is there where i'm wrong?
anyways, hoping somebody would give some magical link to a thread i overlooked. i am backing up my latest nandroid to my laptop right now and when that is done i am going all the way stock to tmobile version. hopefully in the next hour or so i'll get my answer or direction to the appropriate thread and can just convert to dev or unlocked edition. tmobile variant just has way too much bloat and things i changed like a dozen files for carrier iq block. changing to htc edition firmware will minimize the things i need to do when it's time to ota. anyways, if you made it this far thanks. and even more thanks if you're that person that gets me going in the right direction. i am almost proficient at adb/fastboot so i don't need to be handheld on that.

nevermind. went off without a hitch. was worried because previous restores from nandroids didn't go so well. i'm flashed and tmobile splash didn't show so i am pretty sure i am eu now.

HTC One M9 replace ROM

Hey,
I can't seem to find something here that confirms or denies my thoughts, so thought I'd post.
I bought a M9 from eglobal central, but it came with a Chinese ROM. I've been able to fumble through and get it into English, but, certain things aren't quite right on it, so I wanted to swap it to a UK / European ROM. I was wondering how I would go about it? Also, what's the requirements for Carrier IDs etc?
I've seen some other posts out there about swapping ROMs, I'm assuming I'll have to S-OFF, but, after that, do I need root to swap a stock ROM for a stock ROM?
I don't want to go too far with this phone and getting it all setup if I'm going to have to wipe the thing to get it to do what I want it to do....
Thanks,
Berny

Berny Stapleton said:
Hey,
I can't seem to find something here that confirms or denies my thoughts, so thought I'd post.
I bought a M9 from eglobal central, but it came with a Chinese ROM. I've been able to fumble through and get it into English, but, certain things aren't quite right on it, so I wanted to swap it to a UK / European ROM. I was wondering how I would go about it? Also, what's the requirements for Carrier IDs etc?
I've seen some other posts out there about swapping ROMs, I'm assuming I'll have to S-OFF, but, after that, do I need root to swap a stock ROM for a stock ROM?
I don't want to go too far with this phone and getting it all setup if I'm going to have to wipe the thing to get it to do what I want it to do....
Thanks,
Berny
Click to expand...
Click to collapse
You don't need to s-off to flash a new rom. The ROM just needs to match your current firmware, or you can see if there's a firmware update available for the ROM you're currently using.
This thread should get you started. http://forum.xda-developers.com/one-m9/general/guide-root-install-twrp-htc-one-m9-t3061133
Once you have TWRP flashed, you can flash any of the custom ROMs in the Android Development section that match your firmware. You can tell what your firmware is when you are in download mode (It's listed as OS on that page...probably 1.32.xxx.xx...the first set of x's are your SKUid, basically region/carrier, the second set is the version of the 1.32 firmware you're using). All of this should make more sense to you after you read the OP at the above link.

better reception trick

Ever since I got my m9's I have been a flashing fool! I absolutely love it. But I recently learned a trick to improve my reception so I decided I would share.
I live in a city and my reception should always be 5 bars but ever since I got my phones I was only getting 3 bars max regardless of firmware or rom. I know because I have flashed them all. I have a developers edition and an AT&T edition m9 and both phones got the same reception.
well about a month ago I just wanted to try an experiment so I took my att m9 and changed the cid and mid to match a tmoble version. I then flashed the 1.32 firmware and then ran the tmobile Ruu. As a result I then had a stock t-mobile edition m9. But for the first time I had full bars for my reception!
Naturally I then flashed twrp and put a cutom rom back on it but I had the volte and wifi calling along with full bars reception. So put I that observation in the back of my mind and carried on with my business.
Well recently the tmobile update came out and I just flashed the firmware package that sneakyghost (thanks btw for your firmware files) put up and updated the custom rom I was on. But I noticed immediately afterwards my reception returned to 2-3 bars again. I really didn't care too much but then the rom I was using started acting funny. The developer decided to mess with the cpu cores on his update and in extreme power save mode over night it would eat 10% of my battery. And that is something I can't tolerate...
So, I decided to run the 1.32 tmobile (that's my carrier) RUU on my m9 and then accept the 2.7 ota. My reception then returned to 100%. after that I reflashed twrp and super su and restored all my data.
I told my wife about the reception and she wanted me to do the same on her phone (the dev edition) and so I did and got the same results....
So moral of this long post is that if you have poor reception than flashing an ruu for your carrier just might be the trick. This in return will save battery life.
If you decide to try it let me know if it worked. Thanks
This is the link with instructions on how to change your phone from one carrier to another. clsA gives instructions to convert ATT model to developer edition. But you can change your cid to whatever you carrier is and flash accordingly.
Tmobile cid= T-MOB010
At&T and develop edition cid can be found in the link. Also make sure your mid match the firmware you flash. Tmobile mid is 0PJA12000

bigp951 said:
Ever since I got my m9's I have been a flashing fool! I absolutely love it. But I recently learned a trick to improve my reception so I decided I would share.
I live in a city and my reception should always be 5 bars but ever since I got my phones I was only getting 3 bars max regardless of firmware or rom. I know because I have flashed them all. I have a developers edition and an AT&T edition m9 and both phones got the same reception.
So moral of this long post is that if you have poor reception than flashing an ruu for your carrier just might be the trick. This in return will save battery life.
Click to expand...
Click to collapse
I noticed my reception also being worse than my Galaxy S5. In fact, when I woke up I found that my phone was roaming! I never had that issue with the S5. I found it strange. Wi-Fi signal also isn't as good as on the S5. I don't know if it's all the metal or the terrible Snapdragon 810.
I wish your method involved changing something in build.prop lol, that would be simpler and quicker. I'm on a custom ROM also, not by my own will but because I bought the phone like that, I have no idea how to go back to stock AT&T without root and to be able to accept OTAs. I am S-On right now.

Ramsey said:
I noticed my reception also being worse than my Galaxy S5. In fact, when I woke up I found that my phone was roaming! I never had that issue with the S5. I found it strange. Wi-Fi signal also isn't as good as on the S5. I don't know if it's all the metal or the terrible Snapdragon 810.
I wish your method involved changing something in build.prop lol, that would be simpler and quicker. I'm on a custom ROM also, not by my own will but because I bought the phone like that, I have no idea how to go back to stock AT&T without root and to be able to accept OTAs. I am S-On right now.
Click to expand...
Click to collapse
There are a ton of excellent guides in the forum to either change ROMs or return to stock. I think you have to be s-off though. When I want to return to stock I just run an RUU. but remember to back up everything you want to keep because the phone will be completely wiped

bigp951 said:
There are a ton of excellent guides in the forum to either change ROMs or return to stock. I think you have to be s-off though. When I want to return to stock I just run an RUU. but remember to back up everything you want to keep because the phone will be completely wiped
Click to expand...
Click to collapse
I can't find any good guide here for the M9. Weird huh? I've been here since 2008, read countless excellent guides for many phones, and let me tell you that in the past guides were clear and informative. Now all I see is people writing random text all over the place, no clear steps, and information isn't always updated. Probably younger people are writing them, no problem, but it's not helping me understand how to do it.
There's a guide that still says that HTC hasn't yet allowed the bootloader to be unlocked for the M9, and yet when you go there you realize that HTC allows us to unlock it now.
Anyways, my point is, I can't find a good guide, it's not that I'm being prideful, it's just that I have indeed searched and can't find a clear guide. I'm not sure if most assume we have to be S-off? In the past people used to mention "you have to be rooted, or unrooted, or unlocked bootloader, or S-on or S-off". Now it's not very clear so I'm confused, especially since those guides have so many links that I don't know what to download and each is 2GB. You're not the first to tell me that xda has many excellent guides without pointing me to one for the M9 haha.
I want a better reception among other things as it worries me that it was roaming out of nowhere and I'd love to go back to stock as I am not a fan of custom ROMs (except for on my 2010 Galaxy S1 lol).
I have to admit this is the most confusing phone when it comes to modding it or removing root to OTA.
I tried to run an RUU for AT&T latest Android 5.1 (when I was running stock 1.32) and it failed many times, even though I unrooted and locked bootloader. I miss the days of ODIN flashing in download mode =(.
I'm happy the ROM I'm using is stable but still.

Ramsey said:
I can't find any good guide here for the M9. Weird huh? I've been here since 2008, read countless excellent guides for many phones, and let me tell you that in the past guides were clear and informative. Now all I see is people writing random text all over the place, no clear steps, and information isn't always updated. Probably younger people are writing them, no problem, but it's not helping me understand how to do it.
There's a guide that still says that HTC hasn't yet allowed the bootloader to be unlocked for the M9, and yet when you go there you realize that HTC allows us to unlock it now.
Anyways, my point is, I can't find a good guide, it's not that I'm being prideful, it's just that I have indeed searched and can't find a clear guide. I'm not sure if most assume we have to be S-off? In the past people used to mention "you have to be rooted, or unrooted, or unlocked bootloader, or S-on or S-off". Now it's not very clear so I'm confused, especially since those guides have so many links that I don't know what to download and each is 2GB. You're not the first to tell me that xda has many excellent guides without pointing me to one for the M9 haha.
I want a better reception among other things as it worries me that it was roaming out of nowhere and I'd love to go back to stock as I am not a fan of custom ROMs (except for on my 2010 Galaxy S1 lol).
I have to admit this is the most confusing phone when it comes to modding it or removing root to OTA.
I tried to run an RUU for AT&T latest Android 5.1 (when I was running stock 1.32) and it failed many times, even though I unrooted and locked bootloader. I miss the days of ODIN flashing in download mode =(.
I'm happy the ROM I'm using is stable but still.
Click to expand...
Click to collapse
I can see where you think my guide has a lot of links, but all you need to do is determine what your phone is now and choose the correct link for your device. To figure out your current Firmware just reboot your phone to download mode and it tells your OS version right their.
now you know your version download the one your on now or a newer version and RUU back to stock, It's actually easier than Odin
Read my entire instructions to convert to developer edition and you'll see it's not all that hard.
S-off is a pretty vital step if you plan on flashing your phone much at all, and is well worth the $25 price. But it's not needed if you just want your AT&T phone back to stock. Just lock the bootloader (fastboot oem lock). and Run the RUU.exe and your done you have a stock phone.
If your worried about the modified status you'll have to pay for the s-off to remove it.

clsA said:
I can see where you think my guide has a lot of links, but all you need to do is determine what your phone is now and choose the correct link for your device. To figure out your current Firmware just reboot your phone to download mode and it tells your OS version right their.
now you know your version download the one your on now or a newer version and RUU back to stock, It's actually easier than Odin
Read my entire instructions to convert to developer edition and you'll see it's not all that hard.
S-off is a pretty vital step if you plan on flashing your phone much at all, and is well worth the $25 price. But it's not needed if you just want your AT&T phone back to stock. Just lock the bootloader (fastboot oem lock). and Run the RUU.exe and your done you have a stock phone.
If your worried about the modified status you'll have to pay for the s-off to remove it.
Click to expand...
Click to collapse
Thanks for the answer. I saw yours a week ago and I skimmed through it and since it needs S-Off, I kept it for later. I have a question for you and I'll PM you if that's fine as I don't want to take over this thread.

clsA said:
and is well worth the $25 price.
Click to expand...
Click to collapse
S-off is only $25 now? Dang I paid 50 for each phone.

Ramsey said:
I have to admit this is the most confusing phone when it comes to modding it or removing root to OTA.
Click to expand...
Click to collapse
cLSA is very knowledgeable on the m9. When I first made the swith from Samsung to HTC I didn't know jack. But in the past few months I have realized the m9 is the easiest phone to customize that I've ever owned. If cLSA can't help you (I'm sure he's a busy guy) than I'm sure I could. I'm moving and dont have internet yet (right now I'm typing from my phone) but I can always turn on my hotspot and lend a hand.
First thing I recommend doing is to make sure you're adb and fastboot are updated to the latest version. Also make sure you have ever all the right drivers installed.
I'd also recommend getting s-off. Just makes life easier knowing you can flash anything you want (including older firmware). And if a stock phone is what you want than you can turn it back on
If your adb is working then with you phone plugged in and USB debugging clicked open a command prompt (as administrator) and type adb devices. You should then look at Your phone and grant the phone adb privelages. Following that you should see your phones serial number on your pc.
If you see that adb is installed properly, if not then go back and install adb properly. Pm me if you want me to walk you through anything.

Steps for SW update while Rooted?

I have had the HTC 10 pretty much since launched and rooted on day one.
I use the phone regularly but haven't really kept up with the goings one since then.
Just wanted to know if there are steps that need to be taken before or after the "software update available" notification comes along. I've been dismissing it for now because I didn't really have time to sit down and investigate what I would need to do.
Would someone be able to point me in the right direction if there are any steps I need to take or if it even really matters, if I can just install the update without worrying.
Thanks in advance.
If anyone needs any specifics I can see about providing that too.

O-2-L said:
I have had the HTC 10 pretty much since launched and rooted on day one.
I use the phone regularly but haven't really kept up with the goings one since then.
Just wanted to know if there are steps that need to be taken before or after the "software update available" notification comes along. I've been dismissing it for now because I didn't really have time to sit down and investigate what I would need to do.
Would someone be able to point me in the right direction if there are any steps I need to take or if it even really matters, if I can just install the update without worrying.
Thanks in advance.
If anyone needs any specifics I can see about providing that too.
Click to expand...
Click to collapse
To take the full OTA you need an unmodified system (i.e. no root or other mods) and stock recovery. Lots of guides on this, like here:
http://forum.xda-developers.com/showpost.php?p=66347165&postcount=2
Go to point 7 in the above FAQ

Tarima said:
To take the full OTA you need an unmodified system (i.e. no root or other mods) and stock recovery. Lots of guides on this, like here:
http://forum.xda-developers.com/showpost.php?p=66347165&postcount=2
Go to point 7 in the above FAQ
Click to expand...
Click to collapse
Cheers man, appreciate the quick reply.

O-2-L said:
Cheers man, appreciate the quick reply.
Click to expand...
Click to collapse
No problem, the "tricky" part is to find a stock system image backup of your exact software, if you didn't do one yourself before rooting. Just search around the forum, it's probably posted somewhere.

HTC has a tool you can use that makes it super easy. Google Search "ruu HTC 10". It's model specific. They say you should lock your boot loader before running under Rom Update Utility (ruu). I've done it both ways and it worked beautifully. It really is just a few guided clicks and back to stock. Good luck. I love my 10!

Buddudstud said:
HTC has a tool you can use that makes it super easy. Google Search "ruu HTC 10". It's model specific. They say you should lock your boot loader before running under Rom Update Utility (ruu). I've done it both ways and it worked beautifully. It really is just a few guided clicks and back to stock. Good luck. I love my 10!
Click to expand...
Click to collapse
Those are leaked files from HTC. It isn't granted that one has been leaked for his particular CID/MID. Thus this information would be needed, as well as his S-ON/S-OFF state and current firmware number. In addition the RUU has to be of the firmware number he's currently using, or above, as elsewise the mentioned RUU won't work at all. ALL leaked RUUs can be found here in XDA already, only question is if one would fit his needs. If no RUU has been leaked you'd have to do the restore with an untouched system as written above. So this answer might not help in this case.
Sent from my htc_pmeuhl using XDA Labs

5m4r7ph0n36uru said:
Those are leaked files from HTC. It isn't granted that one has been leaked for his particular CID/MID. Thus this information would be needed, as well as his S-ON/S-OFF state and current firmware number. In addition the RUU has to be of the firmware number he's currently using, or above, as elsewise the mentioned RUU won't work at all. ALL leaked RUUs can be found here in XDA already, only question is if one would fit his needs. If no RUU has been leaked you'd have to do the restore with an untouched system as written above. So this answer might not help in this case.
Click to expand...
Click to collapse
Not all RUUs are leaks though and HTC does make certain of them easily accessible. For example, you can find the RUU for multiple devices, including the 10, and various carriers in the U.S here:
http://www.htc.com/us/support/rom-downloads.html

Tarima said:
Not all RUUs are leaks though and HTC does make certain of them easily accessible. For example, you can find the RUU for multiple devices, including the 10, and various carriers in the U.S here:
http://www.htc.com/us/support/rom-downloads.html
Click to expand...
Click to collapse
Right, I didn't mention this. Bit Thise US variants are the only officially posted ones, at least as far as I remember it.
Sent from my htc_pmeuhl using XDA Labs

New thread, new question. Wifi or service, not both.

Ok, same phone, AT&T HTC M9, now S-Off, TWRP 3.0.2.0, 3.38.502.41 firmware. Tried ARHD 20.0, had no service, flashed boot.img, got service but lost wifi. Tried Viperone M9 4.3, same issue. ICE, same issue. If I have Wifi, I have no service. If I flash boot.img, I get service, but lose Wifi. I'm pulling my hair out right now, as I've searched high and low and I've been looking at my PC and M9 for about 14 hours now. Anyone have any insight?

Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it. Htc's are crap when it comes to recovery so be careful.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices. They don't have an app like odin or one even half as good.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.

shivadow said:
Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it. Htc's are crap when it comes to recovery so be careful.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices. They don't have an app like odin or one even half as good.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.
Click to expand...
Click to collapse
It's a bit of a long story as to why I decided to root. It's not damaged by any means, if I flash the ROM posted here (https://forum.xda-developers.com/at...ficial-att-3-38-502-12-rom-7-01-2016-t3409354), Wifi and data both work flawlessly, despite it having a different firmware number. The whole ROM is actually decent, but lacks all the customization I want, and for some reason, headphones only work on one side. I hoped this fix would be simple, as so many people seem to run custom ROMs and I'm just over here yelling at my inanimate object

shivadow said:
Does the rom match your firmware version?
Edit: just read your other thread and replied.
The firmware versions are off so I wouldn't trust it.
I have stayed on 6.0 with root and s-off, without xposed for a very good reason!.
If I were you, as I said in your other thread, would be going back to stock at this point and hoping for the best that the damage isn't permanent.
Its too risky to mess with htc devices.
You have a beast of a phone as is. You don't need to beef it up any more than it is.
Beamed in by telepathy.
Click to expand...
Click to collapse
None of the things manlavi did, so far, was risky. The phone didn't take any damage. All he did was flashing a rom that is incompatible with his firmware like many did before him. The only difference is that HTC seems to have changed some more parts of the firmware with the latest AT&T update so that not only the boot image is incompatible. But that only makes it harder to make the rom compatible. The phone doesn't get damaged in any kind.
If he had flashed a firmware that is incompatible with his phone that would be a whole different story. However, before he opened this thread his phone wasn't S-OFF so he wouldn't have been able to do so even if he wanted.
manlavi95 said:
It's a bit of a long story as to why I decided to root. It's not damaged by any means, if I flash the ROM posted here (https://forum.xda-developers.com/at...ficial-att-3-38-502-12-rom-7-01-2016-t3409354), Wifi and data both work flawlessly, despite it having a different firmware number. The whole ROM is actually decent, but lacks all the customization I want, and for some reason, headphones only work on one side. I hoped this fix would be simple, as so many people seem to run custom ROMs and I'm just over here yelling at my inanimate object
Click to expand...
Click to collapse
The headphones might be broken. Did you check whether they work correctly with a different device?
As already said in the other thread you could convert your phone to another GSM variant of the M9. You would need to change your CID and your MID and then you could flash a RUU with a different SKU. However, you need to be aware that you'll lose every AT&T specific tweaks and functions by doing so. Instructions for converting for example to the US dev edition of the M9 are linked in the readme thread.
Alternatively you could try xposed and the sense tool box on a rooted stock rom. This way you could enable many customisations without having to change your firmware. If you choose this option you should get back to the correct stock rom for your firmware by flashing the RUU I linked in your other thread.

Flippy498 said:
None of the things manlavi did, so far, was risky. The phone didn't take any damage. All he did was flashing a rom that is incompatible with his firmware like many did before him. The only difference is that HTC seems to have changed some more parts of the firmware with the latest AT&T update so that not only the boot image is incompatible. But that only makes it harder to make the rom compatible. The phone doesn't get damaged in any kind.
If he had flashed a firmware that is incompatible with his phone that would be a whole different story. However, before he opened this thread his phone wasn't S-OFF so he wouldn't have been able to do so even if he wanted.
The headphones might be broken. Did you check whether they work correctly with a different device?
As already said in the other thread you could convert your phone to another GSM variant of the M9. You would need to change your CID and your MID and then you could flash a RUU with a different SKU. However, you need to be aware that you'll lose every AT&T specific tweaks and functions by doing so. Instructions for converting for example to the US dev edition of the M9 are linked in the readme thread.
Alternatively you could try xposed and the sense tool box on a rooted stock rom. This way you could enable many customisations without having to change your firmware. If you choose this option you should get back to the correct stock rom for your firmware by flashing the RUU I linked in your other thread.
Click to expand...
Click to collapse
I tested the headphones on another rom and my computer, they had no issues with that. I'm working on converting it to the dev edition. I've changed my CID, but I'm a little afraid that this write-up is a bit out of date, so I'm currently searching for the right RUU.

manlavi95 said:
I tested the headphones on another rom and my computer, they had no issues with that. I'm working on converting it to the dev edition. I've changed my CID, but I'm a little afraid that this write-up is a bit out of date, so I'm currently searching for the right RUU.
Click to expand...
Click to collapse
It's linked in my thread, as well. Directly behind the link to the newer version of the conversion guide. However, it doesn't matter whether you use that old 3.x RUU or a newer one. You just need to install some OTAs while being on stock rom, afterwards, if you choose to use the old one. Be aware that most of the custom roms aren't compatible, yet, with the new 4.x firmware. So only update until your device suggests you to install the 4.x OTA.

Flippy498 said:
It's linked in my thread, as well. Directly behind the link to the newer version of the conversion guide. However, it doesn't matter whether you use that old 3.x RUU or a newer one. You just need to install some OTAs while being on stock rom, afterwards, if you choose to use the old one. Be aware that most of the custom roms aren't compatible, yet, with the new 4.x firmware. So only update until your device suggests you to install the 4.x OTA.
Click to expand...
Click to collapse
Currently downloading the 3.35.617.12 RUU and the HTC Fastboot as I don't have an SD smaller than 32GB. I don't know how I've read that entire Q&A a few times over and didn't see that, so thanks as always

manlavi95 said:
Currently downloading the 3.35.617.12 RUU and the HTC Fastboot as I don't have an SD smaller than 32GB. I don't know how I've read that entire Q&A a few times over and didn't see that, so thanks as always
Click to expand...
Click to collapse
You don't need an SD card with less than 32gb if you're on firmware 3.x (and that is what you currently are). With firmware 3.x and above HTC enabled the usage of exfat formatted SD cards for RUU flashing.

Used the SD method, my phone is now running developer edition. Speaking technically once again, I should be able to use ROMs and have them work now, I imagine. Wifi and cellular both work after flashing dev edition.j

manlavi95 said:
Used the SD method, my phone is now running developer edition. Speaking technically once again, I should be able to use ROMs and have them work now, I imagine. Wifi and cellular both work after flashing dev edition.j
Click to expand...
Click to collapse
Correct.

IT WORKS. IT WOOOOOORKS. Thank you so much.