Develop Bugs

Screen issue

I've got my device 2 weeks ago from T-mobile in Hungary.
So far it's been good, but I hated the Sense UI, unlocked my bootloader and installed CM10.
I've just noticed if I press the right edge of the screen I get this screen issue. I don't really know how to describe it, but it's just as if I pressed my desktop's LCD screen. The screen slightly recoulours and waves appear. I've found others with the same issue (and there seems to be another guy from T-Mobile HU): http://crave.cnet.co.uk/mobiles/htc-one-x-screen-flex-flaw-we-would-never-let-that-ship-50007596/
However I don't even have to press it hard, - normally is enough - and it's not only on the right corner, but on the edge too. Sometimes I can hear a crack. (it must be the case of the device)
So I'd like to get it fixed or replaced, but sadly as I've mentioned I've already unlocked my bootloader. Is this a problem for replacing/fixing it? Where should I take it? T-mobile or to HTC?
Thank you very much for your help and time.
P.S. Why always me? :crying: 泣く

same here.

Well, you should always look after faults with your phone before unlocking the bootloader.
Sent from my HOX running CMX by Tbalden.

Relock bootloader and return it back

Tingelholm said:
Well, you should always look after faults with your phone before unlocking the bootloader.
Sent from my HOX running CMX by Tbalden.
Click to expand...
Click to collapse
Alright, why would I start pushing around the edges of a new phone? Thanks for your constructive response.
By the way the I checked the htcdev site again, it sais
Unlocking your device allows you to install custom Operating Systems (“OS”) onto your device. Custom OS’s are not tested as thoroughly as your original OS, and unlocking your device may void all or parts of your warranty.
Click to expand...
Click to collapse
>may void.
English grammar: may means something is possible, but it is not certain. So this could be interpreted as you're only responsible for the software, and this is a build issue.
So T-mobile (carrier) or HTC?
this is going to be my last htc device, the original SGS was leaps and bounds better, even with its cheap plastic back, but sadly I've lost it. You didn't even have to unlock the bootloader.
P.S. Sorry for my English
EDIT
DoeBoi said:
Relock bootloader and return it back
Click to expand...
Click to collapse
No point, if one relocks the bootloader the fact that someone has opened it before can be seen.

Wait if I take it to the carrier they'd send to it htc to repair it right?

Im at T-Mobile Hungary, too, and if you send it back to them, they send it to HTC, and after that it doesnt matter if its repaired or not, you'll even have to pay for returning your damaged phone...my hungarian is better than my english

Well, obviously if you would just have waited a couple of weeks before unlocking your bootloader you would obviously have noticed the screen? Thank you for your constructive response.
Sent from my HOX running CMX by Tbalden.

Silgrond said:
No point, if one relocks the bootloader the fact that someone has opened it before can be seen.
Click to expand...
Click to collapse
True, but the only way to RUU it back to stock is with a ***LOCKED*** or ***RELOCKED*** HBOOT.

TripleD_HOX said:
Im at T-Mobile Hungary, too, and if you send it back to them, they send it to HTC, and after that it doesnt matter if its repaired or not, you'll even have to pay for returning your damaged phone...my hungarian is better than my english
Click to expand...
Click to collapse
Thanks for your response. But obviously its not my fault. They shouldn't charge me for anything. I still have my T-Mobile warranty.
Rusty! said:
True, but the only way to RUU it back to stock is with a ***LOCKED*** or ***RELOCKED*** HBOOT.
Click to expand...
Click to collapse
Can you please explain it? RUU is to revert to stock right? Can HTC see if I had unlocked my phone earlier if I do this? Care to post a guide or something?

No guide necessary, you just run a .exe and away it goes.
However it will fail if you try and use it with an unlocked bootloader, so as you have one, you have to relock it. Sadly though, it won't hide that you've done it, but at least it wont have CM10 on it anymore.

Rusty! said:
No guide necessary, you just run a .exe and away it goes.
However it will fail if you try and use it with an unlocked bootloader, so as you have one, you have to relock it. Sadly though, it won't hide that you've done it, but at least it wont have CM10 on it anymore.
Click to expand...
Click to collapse
Restored it with RUU, wish me luck tomorrow at T-mobile
EDIT: Aight, they sent it to HTC. They'll get back to me in 2 weeks.

This is ****ing retarded.
They've replaced the screen and the battery, but it has the same build issue but on the left side. ARE YOU ****ING KIDDING ME?!
I'm going to ask for a replacement tomorrow. What the flying **** HTC. Feels like I'm being trolled

I had this "problem" from the beginning.
Not sure why this is a big deal, since i never squeeze my phone on the sides.
I thought this was a normal thing...

Are you sure they actually replaced the screen? And why the battery? You have every right to be pissed off

JoeyDez said:
I thought this was a normal thing...
Click to expand...
Click to collapse
It's not

root and hardware

Hi, so i got a G4 H815 and i can unlock my bootloader, but my only concern is that after unlocking it my warranty will be void.
So my question is does anyone have a hardware problem? Like screen problems or anything?

I unlocked my bootloader, but I didn't notice my digitizer is broken. It's really dysfunctional. Using multi-touch results in my phone thinking that I'm touching the screen at random locations. Scrolling is a pain in the arse as well.
I don't know whether I can send my phone to LG to just get it fixed. I should be, since the law in the Netherlands states that if it's a hardware fault, you still have warranty.

Returned my first G4 because of a faulty screen.
I had Bootloader unlocked it via LG Dev site and had no problem getting a new one.

johnny8910 said:
Returned my first G4 because of a faulty screen.
I had Bootloader unlocked it via LG Dev site and had no problem getting a new one.
Click to expand...
Click to collapse
R3NC0N said:
I unlocked my bootloader, but I didn't notice my digitizer is broken. It's really dysfunctional. Using multi-touch results in my phone thinking that I'm touching the screen at random locations. Scrolling is a pain in the arse as well.
I don't know whether I can send my phone to LG to just get it fixed. I should be, since the law in the Netherlands states that if it's a hardware fault, you still have warranty.
Click to expand...
Click to collapse
thanks a lot!

I have personally not had a single issue that would make me need to take the phone back and swap it out.
I understand that you are nervous about that, but just be careful as far as drops and around liquids and you will be good to go buddy.

Z3ldaFan88 said:
I have personally not had a single issue that would make me need to take the phone back and swap it out.
I understand that you are nervous about that, but just be careful as far as drops and around liquids and you will be good to go buddy.
Click to expand...
Click to collapse
thanks! i will unlock it today!

advice for nexus 5x

hi freind i need your advice.i have a nexus 5x 32GB running android 7.0 40 days ago.i show that some people have bootloop probleme after nougat update.what are you advising me???keep my nexus 5x without fear?or I sold it quickly and keep a new phone???i love my nexus 5x but iam afraid what we advising me
NOTE:i dont have warranty because i bay my phone used from a shop

If something happen and you will send it RMA you will receive phone with replaced motherboard or refund of your money, depends if there are still replacements of motherboards available

Domin_PL said:
If something happen and you will send it RMA you will receive phone with replaced motherboard or refund of your money, depends if there are still replacements of motherboards available
Click to expand...
Click to collapse
i dont have warranty my friend bcz i bay it used from a shop

Aww so haven't you been given original receipt?
So there are two ways, you can keep your phone and disable two big cores of CPU to keep your phone safely from bootlop, or sell it.

Domin_PL said:
Aww so haven't you been given original receipt?
So there are two ways, you can keep your phone and disable two big cores of CPU to keep your phone safely from bootlop, or sell it.
Click to expand...
Click to collapse
tnx friend how to disable the two big cores?and i still have ota update?

This is it:
http://forum.xda-developers.com/nexus-5x/help/bootloped-hw-please-try-t3505392
You can keep just your bootloader unlocked or in developer settings OEM unlock state enabled to unlock bootloader when it is necessary, then you will still receive ota updates

Domin_PL said:
This is it:
http://forum.xda-developers.com/nexus-5x/help/bootloped-hw-please-try-t3505392
You can keep just your bootloader unlocked or in developer settings OEM unlock state enabled to unlock bootloader when it is necessary, then you will still receive ota updates
Click to expand...
Click to collapse
tnx my dear tell me i dont do this now.if i have bootloop probleme in the future can i do this method even if i have the bootloop?

Yes but you need to have ability to unlock bootloader enabled or unlocked bootloader

Domin_PL said:
Yes but you need to have ability to unlock bootloader enabled or unlocked bootloader
Click to expand...
Click to collapse
how to know if my bootloader is unlock??and if is lock how to unlock it?

Here you got a huge instruction:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Bootloader state is in bootloader mode, on turned off device you keep holding volume - and power button

Domin_PL said:
Here you got a huge instruction:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Bootloader state is in bootloader mode, on turned off device you keep holding volume - and power button
Click to expand...
Click to collapse
tnxxxx for your great help my dear

Domin_PL said:
Here you got a huge instruction:
http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
Bootloader state is in bootloader mode, on turned off device you keep holding volume - and power button
Click to expand...
Click to collapse
my stat of my bootloader is locked its fine or not?

I'd just gamble and keep using the phone as long as it works. If it bootloops later on, you'd worry about it then. Not to mention, the smartphone prices are constantly dropping and new hardware is coming to the market all the time, so a new phone you could buy a half year later will be superior to what you get now on the same budget.

znayver said:
hi freind i need your advice.i have a nexus 5x 32GB running android 7.0 40 days ago.i show that some people have bootloop probleme after nougat update.what are you advising me???keep my nexus 5x without fear?or I sold it quickly and keep a new phone???i love my nexus 5x but iam afraid what we advising me
NOTE:i dont have warranty because i bay my phone used from a shop
Click to expand...
Click to collapse
Remember the bootloop issue on N5X is hard ware related. Maybe the phone gets hot on a large update like the Nougat one, and the bad soldered 808 SOC fails. Its not about the Nougat itself.
It only happens to a small % of N5X owners, so you should not be afraid. Just use it as normal. And if you dissable the large cores its not much of a Nexus left.
Thanks
KnieveI

Locked bootloader after custom ROM

Okay, I guess it's been a while since I played with flashing ROMs etc, but I didn't know this was possible. I just flashed Colt OS on my Pixel 2 XL, everything was going fine. I've been having issues with a few apps not allowing me to proceed because the bootloader is unlocked/phone is rooted. So I figured I would lock the bootloader to see if I could get around it. Rebooted to fastboot, did "fastboot flashing lock" and followed the onscreen prompt.
Phone rebooted: Cannot find a valid OS. Device will not start.
Ah crap. Booted back into fastboot, assuming I'd just unlock it and if needed wipe the phone. However, when I type "fastboot flashing unlock" I get the heart-stopping message:
Code:
FAILED (remote: Flashing Unlock is not allowed
)
Finished. Total time: 0.006s
Trying to boot into twrp using "fastboot boot twrp.img" results in
Code:
Downloading 'boot.img'
OKAY [ 1.659s]
booting
FAILED (remote: Can not boot in Lock State)
Finished. Total time: 1.751s
I've unlocked it before with no issues. Why is it suddenly doing this? I can't get into recovery, I can't boot the device, it's effectively bricked until I can figure out how to solve this. Other fastboot commands work fine, as far as I can tell. I have this huge lump in my stomach right now because I *thought* I was experienced enough to not brick my phone. I don't know how I could have forseen this, though.
Any and all help is appreciated. The "fastboot getvar all" returns this, which I've put in a pastebin: https://pastebin.com/NzwfE67T
I'm on the verge of really panicking here. There must be a way to unlock it, I can't imagine why this would even happen. I am literally sick to my stomach right now, reading that other people had to RMA. I bought this phone used about a year ago, no way it's under warranty and I doubt Google will replace it. I cannot go without a phone, I'm seriously freaking the **** out.

Sorry to say but you've screwed yourself.
You only ever lock the bootloader if you're completely stock.
This happens too often because people don't do a quick search to find out if locking the bootloader after unlocking is a good idea.

Sigh...
Sent from my Pixel 2 XL using XDA Labs

ilal2ielli said:
Sorry to say but you've screwed yourself.
You only ever lock the bootloader if you're completely stock.
This happens too often because people don't do a quick search to find out if locking the bootloader after unlocking is a good idea.
Click to expand...
Click to collapse
Yeah well, I've unlocked and relocked bootloaders a million times before on other phones. I just forgot and now I have a ****ing $800 paperweight.

AirCombat said:
Yeah well, I've unlocked and relocked bootloaders a million times before on other phones. I just forgot and now I have a ****ing $800 paperweight.
Click to expand...
Click to collapse
Sorry to hear about your issue.
The only way to safely lock the bootloader on the 2 XL is to be completely stock (as far as I'm aware)... Not sure if you've looked into Deuce's Tool Kit (search it) to see if there is a "brick" option...
Like others have said, I'm afraid you might have an irreversible situation there.
Any chance this device was purchased via Google and still under warranty? If so, might be able to RMA it through them. I thought I bricked my 2 XL while it was under warranty and called Google, told them it was unlocked with a cust Rom, but wouldn't boot and they issued me an RMA for refurb, but I figured it out and ended up keeping the new device over getting a refurb.
Best of luck with this!

AirCombat said:
Yeah well, I've unlocked and relocked bootloaders a million times before on other phones. I just forgot and now I have a ****ing $800 paperweight.
Click to expand...
Click to collapse
Can you get Google to RMA it?

Az Biker said:
Sorry to hear about your issue.
The only way to safely lock the bootloader on the 2 XL is to be completely stock (as far as I'm aware)... Not sure if you've looked into Deuce's Tool Kit (search it) to see if there is a "brick" option...
Like others have said, I'm afraid you might have an irreversible situation there.
Any chance this device was purchased via Google and still under warranty? If so, might be able to RMA it through them. I thought I bricked my 2 XL while it was under warranty and called Google, told them it was unlocked with a cust Rom, but wouldn't boot and they issued me an RMA for refurb, but I figured it out and ended up keeping the new device over getting a refurb.
Best of luck with this!
Click to expand...
Click to collapse
I didn't know Google even had a phone number to call... I thought they were famous for being unreachable and having no customer support. Can you share the number or where you got it? I'm in Canada, not sure if that matters.
I have no idea if it was bought from Google, but I suspect it was because it was factory unlocked. If it did have a warranty I'm sure it's expired, but maybe I can sweet talk someone.
My backup option is to buy a smashed/broken Pixel 2 XL and swap the mainboard out. Cheaper than buying a new one, and I do have an electronics lab at home, so I'm quite confident I can do the swap (have done many many screen replacements, board swaps before). Someone offered to buy it for parts, but I have a feeling that's not the best route to go unless I can't fix/replace it.
Thanks for the info. It does seem bricked. I'm pretty pissed that it's even possible to get in this state. The bootloader should check before locking if there is a valid OS! You'd think it'd be pretty simple to add that check in.

AirCombat said:
I didn't know Google even had a phone number to call... I thought they were famous for being unreachable and having no customer support. Can you share the number or where you got it? I'm in Canada, not sure if that matters.
I have no idea if it was bought from Google, but I suspect it was because it was factory unlocked. If it did have a warranty I'm sure it's expired, but maybe I can sweet talk someone.
My backup option is to buy a smashed/broken Pixel 2 XL and swap the mainboard out. Cheaper than buying a new one, and I do have an electronics lab at home, so I'm quite confident I can do the swap (have done many many screen replacements, board swaps before). Someone offered to buy it for parts, but I have a feeling that's not the best route to go unless I can't fix/replace it.
Thanks for the info. It does seem bricked. I'm pretty pissed that it's even possible to get in this state. The bootloader should check before locking if there is a valid OS! You'd think it'd be pretty simple to add that check in.
Click to expand...
Click to collapse
If your phone was bought from Google it will still be under warranty. I'm not sure if that warranty transfers when it is bought from a third party though. There website does state that the warranty applies to the US and Canada. Here is the link. https://support.google.com/store/answer/6160400?hl=en&ref_topic=3244667

Help relocking bootloader

I can't relock my bootloader no matter what I do, I always get this message:
command: fastboot oem lock begin
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.004s]
Finished. Total time: 0.006s
Why is this happening? I'm not trying to unlock it, it's already unlocked. I was able to relock it once before today but now I can't. I've tried wiping everything on twrp and installing different firmware but still get the same message. Before this I used to get a message saying "Please fully flash the signed build before locking phone" when I tried locking.

Why are you trying to relock it? Unlocking a bootloader does not cause performance issues or anything wrong and there is simply no point in relocking it. If your wanting to relock it before sending it in to Motorola don't even bother. They will know if it's been unlocked and relocking it doesn't magical get your warranty back. If selling it simply tell the person that the performance of the phone is not affected at all.

ninjakira said:
Why are you trying to relock it? Unlocking a bootloader does not cause performance issues or anything wrong and there is simply no point in relocking it. If your wanting to relock it before sending it in to Motorola don't even bother. They will know if it's been unlocked and relocking it doesn't magical get your warranty back. If selling it simply tell the person that the performance of the phone is not affected at all.
Click to expand...
Click to collapse
I really don't understand why this comes up so much. The answer is almost always the same too, warranty, sale, or return. None of which are good reasons to lock it.
This is a bit off topic but I'm going to share it anyways because I think it's hilarious. I once rooted and installed twrp on my neighbors phone to debloat it. Now, he's not tech savvy in the least bit. A few days later, he accidentally boots into twrp while turning his phone on. I wasn't home so he couldn't ask me what to do. In his anger and frustration, he dunked it right in the toilet. It still worked after that so he went to Best Buy to return it. The geek squad in all their wisdom... thought that twrp was special software designed to break into government servers. They call the police. The police show up and don't know what it is, or what to do with it. After 2.5hrs of head scratching and a nice chat with the FBI, he finally got his phone replaced. (The FBI knew exactly what it was.) If anyone had bothered to read what twrp's menus say, they would've understood what it was for in like 1-2min.
Tales from the tech department...

Right like I guess I understand the logic behind the thought process though so I don't mind it to much lol. and that was the best story about geek squad I've ever heard ??? leave up to them to think it's for hacking stuff lmfao this would go great ona Reddit geek squad encounters post

go to "developer options" and check again "oem unlock" and try again

ninjakira said:
Why are you trying to relock it? Unlocking a bootloader does not cause performance issues or anything wrong and there is simply no point in relocking it. If your wanting to relock it before sending it in to Motorola don't even bother. They will know if it's been unlocked and relocking it doesn't magical get your warranty back. If selling it simply tell the person that the performance of the phone is not affected at all.
Click to expand...
Click to collapse
Takes longer to boot and reboot. Stays stuck on bad key for a little while before it actually boots.

jrebmontana said:
go to "developer options" and check again "oem unlock" and try again
Click to expand...
Click to collapse
I can't, it's grayed out.

Spaceminer said:
I really don't understand why this comes up so much. The answer is almost always the same too, warranty, sale, or return. None of which are good reasons to lock it.
This is a bit off topic but I'm going to share it anyways because I think it's hilarious. I once rooted and installed twrp on my neighbors phone to debloat it. Now, he's not tech savvy in the least bit. A few days later, he accidentally boots into twrp while turning his phone on. I wasn't home so he couldn't ask me what to do. In his anger and frustration, he dunked it right in the toilet. It still worked after that so he went to Best Buy to return it. The geek squad in all their wisdom... thought that twrp was special software designed to break into government servers. They call the police. The police show up and don't know what it is, or what to do with it. After 2.5hrs of head scratching and a nice chat with the FBI, he finally got his phone replaced. (The FBI knew exactly what it was.) If anyone had bothered to read what twrp's menus say, they would've understood what it was for in like 1-2min.
Tales from the tech department...
Click to expand...
Click to collapse
Takes longer to boot.

needhelp4 said:
Takes longer to boot.
Click to expand...
Click to collapse
That's not true. An unlocked device actually boots up slightly faster. The reason why is; when you unlock the bootloader it skips verifying the boot.img signature. Meaning there's actually less work for the cpu to do before startup. The difference is extremely minimal though and probably not noticable without timing it in milliseconds.

Spaceminer said:
That's not true. An unlocked device actually boots up slightly faster. The reason why is; when you unlock the bootloader it skips verifying the boot.img signature. Meaning there's actually less work for the cpu to do before startup. The difference is extremely minimal though and probably not noticable without timing it in milliseconds.
Click to expand...
Click to collapse
You can see why in my reply to ninjakira. The screen displays 'bad key' on boot and only after a while restarts and actually boots.

needhelp4 said:
You can see why in my reply to ninjakira. The screen displays 'bad key' on boot and only after a while restarts and actually boots.
Click to expand...
Click to collapse
It's actually not restarting. That's the bootloader handing off control to the boot.img. The bad key screen, is actually the boot logo screen. The bootloader is just designed to show that instead of the logo if you're unlocked. The boot animation has it's own splash screen that perfectly matches the one in the boot logo. So when you're still locked and the hand-off occurs, it looks seamless. When you're unlocked it goes from black to the Moto logo, so you end up seeing the transition. The current brightness setting also kicks in at the boot animation, which makes it look even worse when unlocked. You can fix that by flashing one of my boot logos from here.