Develop Bugs

[Q] Supersonic SuperBorked

Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...​
2) Anyone know how to turn S-(back)ON in my current situation?​
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )

First...... Wrong subforum. Try Q and A.
Second, in all your rom flashing, did you maybe forget to wipe, and re-wipe before your rom install?

Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.

Happened to me when trying to root my brothers Evo. (Already had mine rooted). I thought the phone was bricked because there was no recovery installed and all that worked was hboot. I tried several different versions of PC36IMG.zip until 1 finally worked.
Cheers

Yes! try updating with PCM36IMG.zip ROm that should help you out, ex "Sprint lovers". Good luck.

sidiasus said:
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Click to expand...
Click to collapse
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.

Mikedick said:
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Click to expand...
Click to collapse
No problem, I tried to write in a more humorous style than the other "HALP" threads, and my ability to clearly relate the important details suffered. Thanks for the good wishes!
Etiquette question: I've duplicated this thread in Q & A, should I just delete this one?
Also, thanks to all for the lightning fast responses, trying more PC36IMG'ses.

Nah, just let it die.

Found like you're radio fried, it's a well known defect on some evos and incredibles. Try to put it in the fridge while turned off and afterward it may run for long enough to turn s-on.
Sent from my PC36100 using XDA App

Crap, can this be done?

Just got this phone and I love it but the seller on ebay had it rooted and had one of the roms from here on it. They said they would put it all back to stock for me. I like to start with a clean slate if you know what I mean. Well, it is back on gingerbread but root is still there and a whole bunch of other stuff (apps, roms, titanium backup) etc etc in folders on the internal storage. My question is can I safely get this phone back to being stock just like it was from the factory, without the risk of bricking it? I know how to use Odin for the Epic 4G and all. I knew there were some problems with the touch and some phones getting bricked. I have no clue what they may have done to the phone so I am a bit concerned to do anything to it till I hear from someone who has done this (gone completely back to stock) Also, is there a tutorial somewhere?? Thanks guys for your help with this.
Oh here is some more info if it helps looks like I am on Android version 2.3.6, EL29, kernel 2.6.35.7 there is some other info if you need it please let me know I do see a Caulklin's folder in there in the internal storage so most likely they did have that rom on there at one time. There is also a ACS folder in there but when I try to open any of the folders in there I get an error that there is no program that can perform this action. Grrrrrr

Hi.
When messing with Gingerbread, especially stock, bricks are pretty hard to come by nowadays.
Here is what I suggest:
http://forum.xda-developers.com/showthread.php?t=1433101
(from what you said, you probably understand this already)
Just run the EL29 OC. You'll be good to go.
In terms of the internal storage, just delete it all or run a format. You won't get yourself in trouble that way, it's just the internal storage.
If you're concerned about the data wipe brick, that is only on ICS. So since you're on GB, it is not a problem (and totally unrelated to clearing internal storage.)
Post back if you have any questions or anythin'.

If you are on gingerbread then there is no danger of the EEMC superbug(As far as I've heard/read). As for reseting I don't have a link to a tutorial off the top of my head, however the process is pretty simple. Start searching through the development forums for the stock odin files and then flash them. I can try to find you a tutorial/links tonight but I don't really have time right now...besides the search function works the same way for you as it would for me! Feel free to ask if you need anything else!
Hahaha MochaCharok beat me to it!

Thanks guys. The phone at one time was on an ICS rom and yes I can search for it. I just wanted to make sure before I did, that this could be done. So, I will see about finding the tutorial and how to go about getting the phone all back to factory like. I know I am so anal this way, but I really do like to start with a clean slate before I do anything to any phone. thanks again guys I will holler if I run into any problems. LOVE this phone though.
thewadegeek said:
If you are on gingerbread then there is no danger of the EEMC superbug(As far as I've heard/read). As for reseting I don't have a link to a tutorial off the top of my head, however the process is pretty simple. Start searching through the development forums for the stock odin files and then flash them. I can try to find you a tutorial/links tonight but I don't really have time right now...besides the search function works the same way for you as it would for me! Feel free to ask if you need anything else!
Hahaha MochaCharok beat me to it!
Click to expand...
Click to collapse

When you activated the phone on your account it should've wiped everything they had on the phone prior and reset it to stock. At least that's what happened when I activated a phone I'd bought from an XDA member. So I started with a clean slate automatically.

It didn't for whatever reason. I had to go in and edit the MIN and MDN manually to get it to activate so maybe that is why. That thing was a HUGE pain to do too. It would not take and kept resetting. Had to try it like 5 times.
Esoteric68 said:
When you activated the phone on your account it should've wiped everything they had on the phone prior and reset it to stock. At least that's what happened when I activated a phone I'd bought from an XDA member. So I started with a clean slate automatically.
Click to expand...
Click to collapse

If you are stuck with what to do next then take it to a Sprint store and let them wipe it for you.

Good info
As I'm going to try this and hopefully get the missus off her Opt S and onto an E4GT this week this was good timing to cover the process.
Here's what I am planning to do:
1) Flash EL29 + Root
2) Factory Reset from Recovery (which should clear NVRAM if I understand correctly)
3) Call MVNO and have them set up phone
4) Allow hands-free activation to hopefully fill in the blanks
If this works as I hope then I shouldn't have to tinker manually with the NVRAM data.... if not then I have my phone to base most of that off of. And of course it depends if the carrier will let me set the phone up - in the past they haven't been warm to using a different phone unless you purchased it directly from them.
All this just to sit tight until we can get the GS3 probably next year.. yeesh.

[Q] please help a noob in need! big phone problems

Hopefully this is the right place to post. I apologize if it's not.
Last week I bought the Samsung Galaxy S2 X from Koodo Mobile. The model # is SGH-T989D and runs the newest version of ICS. 4.04 I believe.
I hadn't had any problems until recently. I was trying to root my phone when I ran into some trouble. I forgot to make a backup of my system, so when I ran into problems, I just decided to try out a couple custom roms. At some point something got messed up badly with my phone. Whenever I turn it off now the lights at the bottom of the screen stay on. Unless I hold the power for 30 seconds to a minutes it won't turn back on. The factory reset has also been a problem. I'll go to reset it, and it formats the usb storage, but doesn't restart. When the phone is on, it seems to work fine.
I finally managed to get a telus stock rom to flash and work. So I have two questions I'm hopeful someone can help me with.
1. Are there any Koodo stock roms for ICS? I've looked on tons of different sites, and it seems it's all either for T-mobile or Telus. Is that because Koodos just came out with their phone? I'm just looking for the exact version that would have been on my phone when I got it. I found one online, but it had no baseband version. If I have to return the phone or send it in for repairs, I'd like it back to stock,
2. My other question is, does the light not turning off, and the turn on problems sounds like a hardware issue? I've been trying to fix this for the last 24 hours and it's driving me nuts. Since I'm a noob I have no idea whether I should keep trying or just send it in for repairs. Does it sound like something that can be fixed? Like maybe I'm flashed a wrong kernel or am using a bad rom? I don't know, but advice would be much appreciated.
Thanks to anyone who answers.

you have various roms made for koodo..2) are you talking about the soft keys? depending on what rom you use they can be different (locationwise) ... if I'm not mistaken all --- This is my personal opinion. Jedi on koddo should be more than sufficient as to suit your daily driver needs. Dev is very helpful and keeps a very organized thread. You can also try darkside, if I'm not mistaken he had a koodo version. i own a hercules so i at give more information... for your best info, go into the thread and ask the ppl i n them for their experience. everyone's needs are different so for what might work for me might not for you Infamous is another one. Just click on the t mobile dev section and you just scroll for what you like.. Hope this help

I guess my main question is about the key lights staying on. I'm pretty sure it means its not shutting down correctly because it also won't turn on again unless I hold down the power button for 30 seconds. So could that be caused by anything I did? Like any of the flashing or customers roms I used, or should I just send it back into Koodo?

Okay download this: http://sourceforge.net/projects/darksidetools/files/SGH-T989_DARKSIDE.SUPER.WIPE_EXT4.zip/download
And then flash a rom (any one, just pick one)
That is a flash able zip (in cwm recovery) that will completely wipe off every piece of system and rom data (does NOT touch anything on your internal memory or external sd). If your hardware lights are malfunctioning due to software, this will fix it. Then, when you flash your rom, if you still have the issue with your hardware lights, it's likely a hardware issue and you should follow a guide to return to stock everything and send it in for warranty repair.
Also, this is a Koodo based rom if you're interested:
http://forum.xda-developers.com/showthread.php?t=1849748

yoft1,
I appreciate your help. I did what you said and downloaded both the darkside clean wipe and the darkside cache wipe. Flashed my rom, and the light finally started to shut off.
Except when I did a normal factory reset just from the settings menu, when it reset I still have the same problem, it goes back to keeping the lights off. Does that make any sense to you? Like could something in the darkside clean or cache wipe fix it but then a factory reset mess it up again?
Also if I wanted to make a backup of my system, what program would you recommend to do it? Thanks again.

Just run the cache wipe again. It will fix that.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Great, thanks for the help.
One other question, if I want to put my phone back to the EXACT way it was when I bought it, do I just need to flash a stock rom, or do I need to flash a kernel as well?

robois88 said:
yoft1,
I appreciate your help. I did what you said and downloaded both the darkside clean wipe and the darkside cache wipe. Flashed my rom, and the light finally started to shut off.
Except when I did a normal factory reset just from the settings menu, when it reset I still have the same problem, it goes back to keeping the lights off. Does that make any sense to you? Like could something in the darkside clean or cache wipe fix it but then a factory reset mess it up again?
Also if I wanted to make a backup of my system, what program would you recommend to do it? Thanks again.
Click to expand...
Click to collapse
If you're looking to make a backup of your entire device image, your cwm recovery will do that for you under backup. No other way to do it, you have to do it via a recovery mode.
I don't know why factory reset would be causing that problem since I never use that but it does seem odd.
robois88 said:
Great, thanks for the help.
One other question, if I want to put my phone back to the EXACT way it was when I bought it, do I just need to flash a stock rom, or do I need to flash a kernel as well?
Click to expand...
Click to collapse
To return exactly how you bought it, you need to first flash the stock ics kernel through cwm. Then flash an Odin tar file through Odin (desktop) which will restore stock rom as well as stock recovery. Unfortunately, I've looked around but could not find an Odin tar file for Koodo stock. Maybe you'll have better luck but in any case that is the process.
You seem competent and willing to learn, which doesn't happen as often as you would think. Let me know if I can help further. Good luck.

yoft1,
Many thanks again for your help. I am extremely green to this type of stuff so I feel like I've been thrown into the deep end here.
I've been looking around for the tar file and can't seem to find one either. But with the amount of people on here, there is probably someone who could upload it right? Would there be a thread or better forum for me to make a request? Or is that poor etiquette on this site?
I've just seen so many different roms, kernels, updates, etc...and I'm thinking somebody might be able to get it on here.
Ok you also said the first thing to do is to flash the kernel. Am I just lookng for any stock ics kernel? I just know I've looked through so many website and threads with different kernels, I just want to make sure I flash the correct one. Like is there a specific one per carrier, or model, or brand?
Again thanks for the help.

I would probably start a thread in the general section to see if someone can compile/upload an Odin flashable tar from Koodo stock. If that doesn't work or if no one responds after a bit, I would PM Mr X (a user on these forums). He is a dev that has uploaded stock roms for Telus and tmobile and he's also a really nice guy. He would probably know where to get one.
As for the kernel, I'm not sure if it matters but I would say with 80% certainty that there is no difference between the stock tmobile kernel and the stock Koodo kernel. On top of that, I would say with 99% certainty that it doesn't matter either way because I highly doubt they would look that closely (if there's anything to find at all) if you send it in for warranty purposes (but no promises of course) . If you get your hands on that tar file for Odin, I'm almost positive that the stock tmobile/Telus ics kernel will do it for ya.
Here is one of MrX's threads so you can PM him if the general forum doesn't work out:
http://forum.xda-developers.com/showthread.php?t=1356739

[Q] Crashing apps and loss of service?!

Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!

Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).

BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.

Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.

BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!

N5 sorta stuck in bootloop. Looking for help on backup and remedy!

Hey there guys!
So I'm having a bit of a situation with my Nexus 5. It is a first production run as I ordered it the hour it came out.
Today it started having HUGE issues. This is a few days after I downloaded Marshmallow 6.0. The device would shut down and then go into a boot loop for HOURS. Sometimes it'd start back up fine and be usable for a few minutes, but then shutting down and becoming unusable. Sometimes it'd start up and the "Optimizing Apps" screen would come up as if I had just made an Android upgrade, and it would complete after some minutes and become usable until it restarted again.
The phone "seems to be working" now OK. This thread is gonna be a bit multi-faceted, so sorry for asking so much :/ Just having a situation with my phone I want to remedy.
First, I'm looking for a good unrooted backup program I can use to backup the stuff on my phone to my computer or somewhere else. I want it in case I get the phone working again or I get a new android and want to transfer stuff over. Is it possible to move data from one backup to a new phone? Not sure. Either way, just looking for a good backup program I can use, if anyone can recommend me one.
Second, besides the obvious possibility of Marshmallow messing my phone up, a lot of people say it could have to do with a "stuck internal power button" and that "smacking the phone against a hard surface near the camera" could help. This seems mega sketchy, but at this point Im willing to do it after a backup. Does this solution have any merit or is it, as we say, "bulls***"?
Third, is there any possible way to remedy a bootloop software-side?
Thank you!

Since you are talking about downloading 6.0, and don't mention the N5X, I'm assuming you are in the wrong forum
That said:
You can run backups with adb (search for "adb backup"), without root. Just need adb debugging turned on in Android. This will also let you restore apps.
I've always used Titanium or a custom recovery myself, so I'm not familiar with the whole process.
I think you can clear the cache in the stock recovery too - might help? Fastboot & TWRP would offer more options, of course.
No idea on the stuck button theory - hopefully mods move this over so N5 veterans can you help out.

Thanks for the help!
To be perfectly honest, I didn't even know a Nexus 5X existed until now :$ Sorry for posting in the wrong forum, thought the X just stood for some production run number. My bad!