Hello. On my phone had a problem with the backlight - is not exposed to maximum brightness + blinking. The problem is clearly not a program, because I pierced the phone numerous times. I took it to a service center. After a long diagnosis, they say: The problem is that you have installed the unofficial software.
Yes, install, but before hand it in for repair, I beg stock image of (5.1), blocked the boot and threw flag burglary.
I told him that know about it they can not, because everything is done correctly. However, he said that all of the programmer will be displayed.
If he's lying? Is it possible to find out that I pierced the machine?
Sorry, I seem wrong section . Transfer the theme , please, if this is the case .
first off, questions go into the q&a section, not the original development section. secondly, im still trying to figure out what you are asking. what did you pierce your phone with? pierce meanimg that you stuck something into your phone and made a hole in it.
simms22 said:
first off, questions go into the q&a section, not the original development section. secondly, im still trying to figure out what you are asking. what did you pierce your phone with? pierce meanimg that you stuck something into your phone and made a hole in it.
Click to expand...
Click to collapse
I in every possible way stitched the phone custom insertions. But before carrying it I returned an official insertion to the service center, blocked the loader, cleaned a breaking flag. According to this instruction: http://4pda.ru/forum/index.php?showtopic=514104&st=40#entry28295175
I don't think that it is a program problem. There was it suddenly, and after many reinsertions didn't improve. I wasn't engaged in dispersal of the processor.
OsBuilder said:
I in every possible way stitched the phone custom insertions. But before carrying it I returned an official insertion to the service center, blocked the loader, cleaned a breaking flag. According to this instruction: http://4pda.ru/forum/index.php?showtopic=514104&st=40#entry28295175
I don't think that it is a program problem. There was it suddenly, and after many reinsertions didn't improve. I wasn't engaged in dispersal of the processor.
Click to expand...
Click to collapse
ill start with this.. я не понимаю, что вы пытаетесь сказать
are you asking why the service center can tell that you had the phone rooted at one point?
simms22 said:
ill start with this.. я не понимаю, что вы пытаетесь сказать
are you asking why the service center can tell that you had the phone rooted at one point?
Click to expand...
Click to collapse
Sorry. My question: Whether can learn the service center about the past of phone? (It was stitched, or not)
OsBuilder said:
Sorry. My question: Whether can learn the service center about the past of phone? (It was stitched, or not)
Click to expand...
Click to collapse
well, there are "flags" that will show that the bootloader was unlocked at some point.
simms22 said:
well, there are "flags" that will show that the bootloader was unlocked at some point.
Click to expand...
Click to collapse
Yes, but in the instruction just was how to dump it. The flag shows false value. I.e. everything is normal.
OsBuilder said:
Yes, but in the instruction just was how to dump it. The flag shows false value. I.e. everything is normal.
Click to expand...
Click to collapse
well, i see that. but they could tell, maybe some other way. is this service center where you bought the device? does it matter to them that you had your bootloader unlocked?
simms22 said:
well, i see that. but they could tell, maybe some other way. is this service center where you bought the device? does it matter to them that you had your bootloader unlocked?
Click to expand...
Click to collapse
Yes, it is the official service center LG. They can't understand in what a problem. They speak, because of that that you established the informal software, and we can refuse under repair. I told that you can't check it, I returned everything to initial situation.
ahhh, lg. that makes sense now. they do have that right to refuse service if the bootloader is unlocked unfortunately. if you changed the tamper flag, im curious how they knew then.
simms22 said:
ahhh, lg. that makes sense now. they do have that right to refuse service if the bootloader is unlocked unfortunately. if you changed the tamper flag, im curious how they knew then.
Click to expand...
Click to collapse
It turns out, if i changed the tamper flag, they can not know about it. Yes?
OsBuilder said:
It turns out, if i changed the tamper flag, they can not know about it. Yes?
Click to expand...
Click to collapse
there might be other ways that they could tell.
Use the LG flashtool, I used it when I returned my phone to LG and it was tested and repaired
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
JonesL said:
Use the LG flashtool, I used it when I returned my phone to LG and it was tested and repaired
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
^^^ what Jones said.
Related
so my nexus is stock, but unlocked.
i cherged my nexus today an i read on a thread that to calibrate the battery it should be plugged at 100% and then u should turn it off then on and while it boots u should take out the battery. i did it. and now it doesnt boot, not even in fastboot.
some help?
Who said to pull out the battery while booting? It's a dangerous action you may brick your phone. Add I know a lot Chinese users of Nexus S had done this accidentally. Like rebooting without the battery cover when the battery fell off.
And unfortunately I didn't see anyone made their phone back, yet.
Anyway you can search for some threads for saving bricked phone.
Sent from my Nexus S using xda app-developers app
vikingsail said:
Who said to pull out the battery while booting? It's a dangerous action you may brick your phone. Add I know a lot Chinese users of Nexus S had done this accidentally. Like rebooting without the battery cover when the battery fell off.
And unfortunately I didn't see anyone made their phone back, yet.
Anyway you can search for some threads for saving bricked phone.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
So... my phone is bricked.
well, no smartphone until christmas!!!! yeah! (being ironic)
Cascabreu said:
So... my phone is bricked.
well, no smartphone until christmas!!!! yeah! (being ironic)
Click to expand...
Click to collapse
Not exactly you can saved it. I find a thread on Chinese forum says use Ubuntu to unbrick a bricked ns. I think the thread actually comes from xda. Try to search here you can find it. Sorry I'm on my phone now can't do a search. All the best.
vikingsail said:
Not exactly you can saved it. I find a thread on Chinese forum says use Ubuntu to unbrick a bricked ns. I think the thread actually comes from xda. Try to search here you can find it. Sorry I'm on my phone now can't do a search. All the best.
Click to expand...
Click to collapse
i know about that, its called adam tool. but that tool is useless if your screen doesnt even light up. i tried the tool and it didnt worked
thanks anyway
you cannot fix a dead boot with any software/USB connection to a PC. A bricked/Dead boot can only be fixed by having a certain hardware called JTAG/RIFF. Check this link: http://www.youtube.com/watch?v=iejfuW7XcKA
its a bit high in price between 100-150$, usually repair centers have it and charge 50$ for a fix. I suggest taking your nexus to a repair center and specifically tell them that you have a "DEAD BOOT AND NEED IT FIXED BY JTAG/RIFF"
ismailham said:
you cannot fix a dead boot with any software/USB connection to a PC. A bricked/Dead boot can only be fixed by having a certain hardware called JTAG/RIFF. Check this link: http://www.youtube.com/watch?v=iejfuW7XcKA
its a bit high in price between 100-150$, usually repair centers have it and charge 50$ for a fix. I suggest taking your nexus to a repair center and specifically tell them that you have a "DEAD BOOT AND NEED IT FIXED BY JTAG/RIFF"
Click to expand...
Click to collapse
i already understand that XD i im back from vacacion i will go to the store with my warranty and maybe i dont pay anything for thr fix
I had my phone fixed for free!!!!!!! Thanks anyway!!!
sent from my Nyan NeXus S
Do share
Cascabreu said:
I had my phone fixed for free!!!!!!! Thanks anyway!!!
sent from my Nyan NeXus S
Click to expand...
Click to collapse
Can you please tell me how? I was booting mine and bettery fell out...now it cant even be recognized with USB connected...help!!!
kali4nian said:
Can you please tell me how? I was booting mine and bettery fell out...now it cant even be recognized with USB connected...help!!!
Click to expand...
Click to collapse
i used my warranty in a local store XD
i went there and said that i turned off the phone over night and in the morning he didnt wanted to turn on. they said it was a normal issue. LMAO
Yep, I've got there too
My power button is acting up. When in the ROM it doesn't work completely. When I take out my battery and put it back in, it powers up by itself. ANy ideas? Will take it to the service this weekend? Any idea if it's just the button that's messed up or something more important?
Also, when on the lockscreen, sometimes, the touch buttons light up by themselves. Only those it seems..
andrei1015 said:
Yep, I've got there too
My power button is acting up. When in the ROM it doesn't work completely. When I take out my battery and put it back in, it powers up by itself. ANy ideas? Will take it to the service this weekend? Any idea if it's just the button that's messed up or something more important?
Also, when on the lockscreen, sometimes, the touch buttons light up by themselves. Only those it seems..
Click to expand...
Click to collapse
This is a common problem of the Nexus S. Take it to your neareset samsung service center. The temporary solution is to set your volume rocker as the wake-up button, then Nexus Root Toolkit for shutdown/reboot/recovery.
Originally Posted by andrei1015<br />
Yep, I've got there too <br />
My power button is acting up. When in the ROM it doesn't work completely. When I take out my battery and put it back in, it powers up by itself. ANy ideas? Will take it to the service this weekend? Any idea if it's just the button that's messed up or something more important?<br />
<br />
Also, when on the lockscreen, sometimes, the touch buttons light up by themselves. Only those it seems..
Click to expand...
Click to collapse
<br />
<br />
This is a common problem of the Nexus S. Take it to your neareset samsung service center. The temporary solution is to set your volume rocker as the wake-up button, then Nexus Root Toolkit for shutdown/reboot/recovery.
Click to expand...
Click to collapse
Wugfresh toolkit wouldn't boot it to recovery while it was boot looping. Any help ?
sent from your moms phone
Don't need reboot much. Taking it to my friendly neighbourhood service. Hoping for a quick and easy fix really. Any detailed idea of what happened?
Flowed from Nexus S
93fuelslut said:
Wugfresh toolkit wouldn't boot it to recovery while it was boot looping. Any help ?
Click to expand...
Click to collapse
Well in my case it did. I'm on WIn7 with installed proper drivers, adb, android sdk, etc.. I had it fixed thru samsung service center in about 2hours.
andrei1015 said:
Don't need reboot much. Taking it to my friendly neighbourhood service. Hoping for a quick and easy fix really. Any detailed idea of what happened?
Click to expand...
Click to collapse
Moisture.
ej8989 said:
Moisture.
Click to expand...
Click to collapse
I see. Well, The service told me it's gonna be fine, and now I've gone back to my old Spica. Thank you for the information and help
Service said it's much worse than expected and I have to take it to an official samsung service. Doing that on Saturday. This means I have to put stock on it.. and re-lock the bootloader.
andrei1015 said:
Service said it's much worse than expected and I have to take it to an official samsung service. Doing that on Saturday. This means I have to put stock on it.. and re-lock the bootloader.
Click to expand...
Click to collapse
I took it to an official samsung service center near my place while on a custom 4.2.1 rom. They didn't touch the software so i don't think you need to put stock on it, unless you're claiming warranty.
ej8989 said:
I took it to an official samsung service center near my place while on a custom 4.2.1 rom. They didn't touch the software so i don't think you need to put stock on it, unless you're claiming warranty.
Click to expand...
Click to collapse
Yea, I'd like to claim warranty. They told me it's a motherboard problem so it should be pretty expensive to repair. I'm wondering if it's possible to relock the bootloader AND flash a stock ROM with a power button that's pressed all the time. Any idea?
andrei1015 said:
Yea, I'd like to claim warranty. They told me it's a motherboard problem so it should be pretty expensive to repair. I'm wondering if it's possible to relock the bootloader AND flash a stock ROM with a power button that's pressed all the time. Any idea?
Click to expand...
Click to collapse
Nexus root toolkit.
ej8989 said:
Nexus root toolkit.
Click to expand...
Click to collapse
One click stocking? I am usually a fan of classic methods where I know exactly what every step does, but desperate times ask for desperate measures. Will look into it, thanks
andrei1015 said:
One click stocking? I am usually a fan of classic methods where I know exactly what every step does, but desperate times ask for desperate measures. Will look into it, thanks
Click to expand...
Click to collapse
It's reliable and fast. I don't wanna risk messing up and/or bricking my phone using adb codes
ej8989 said:
It's reliable and fast. I don't wanna risk messing up and/or bricking my phone using adb codes
Click to expand...
Click to collapse
It's actually fun and you say I can go back to stock AND relock the bootloader even if the power button is always pressed?
andrei1015 said:
It's actually fun and you say I can go back to stock AND relock the bootloader even if the power button is always pressed?
Click to expand...
Click to collapse
Yes. On most cases. lol
There's always a bit of uncertainty in everything.
ej8989 said:
Yes. On most cases. lol
There's always a bit of uncertainty in everything.
Click to expand...
Click to collapse
Ahh yes, but that's what makes it fun!
EDIT: my computer does not detect the phone in fastboot. and the volume keys are working in normal mode but not in fastboot
I everyone, sorry if I ask.
I've bought a chinese OPO and I've seen that, at the bottom of the screen I've the "famous" yellow line.
Is there a way to fix it?
Thanks in advance.
Castore said:
I everyone, sorry if I ask.
I've bought a chinese OPO and I've seen that, at the bottom of the screen I've the "famous" yellow line.
Is there a way to fix it?
Thanks in advance.
Click to expand...
Click to collapse
does it stay every time ?? like even at boot
if yes replace the phone its hardware problem
no solutions for that.
@SidDev said:
does it stay every time ?? like even at boot
if yes replace the phone its hardware problem
no solutions for that.
Click to expand...
Click to collapse
I fear you're right.
Castore said:
I fear you're right.
Click to expand...
Click to collapse
I hope you are under warranty ?
if not repair it from local repair center .
@SidDev said:
I hope you are under warranty ?
if not repair it from local repair center .
Click to expand...
Click to collapse
Yes, I'm under warranty but I've bought the phone from China and I'm from Italy, only the ship cost will be more than the repair.
There's no place to repair a china phone here, nobody even known the phone
But it's a problem that has a lot of OPO and the manufacturer said that, they're good enough and, even N% has yellow screens...
But I'm really not happy with this phone, not only for the yellow line.
There is no way to fix it, with usage and time it gets slightly better. 99% of phones have this, so you should not have bought the phone, if you think this is a deal breaker.
Dzhedaj said:
There is no way to fix it, with usage and time it gets slightly better. 99% of phones have this, so you should not have bought the phone, if you think this is a deal breaker.
Click to expand...
Click to collapse
at least not 99%
Dzhedaj said:
There is no way to fix it, with usage and time it gets slightly better. 99% of phones have this, so you should not have bought the phone, if you think this is a deal breaker.
Click to expand...
Click to collapse
I didn't know that this kind of phone has this kind of screen. Obviously I never bought a phone with this defect.
I really never bought a phone even if I had known the state of Cyano 11s.
But it'd definitely my fault.
Thanks for the answers.
There's an entire thread dedicated to this. Try using a UV lamp (found at a nail salon) for ten minutes with the device turned off.
Please search before posting.
Transmitted via Bacon
timmaaa said:
There's an entire thread dedicated to this. Try using a UV lamp (found at a nail salon) for ten minutes with the device turned off.
Please search before posting.
Transmitted via Bacon
Click to expand...
Click to collapse
I've seen the post but I've had not seen a solution.
Sorry if I asked.
Damir franc has a video on YouTube
Archipago said:
Damir franc has a video on YouTube
Click to expand...
Click to collapse
I have never had that problem
The display stopped working 2-3 days ago. On booting i can see the google logo for 2-3 seconds before the screen goes dark. The phone works and i can hear dings of messages, but i cant access any of it. Once i kept shut it for a day i was able to see the screen for 10-15 seconds( i used this window to remove the screen lock so that i can use the usb transfer ). Now keeping the phone shut for long duration has no effect.
I can see the fastboot screen but not the recovery screen throught it.
I also bought a slimport so that i could see the screen on my pc. It works (not for the fastboot or recovery), however the touch doesn't work and the volume and power buttons response is too sluggish. I can connect the mouse but it is of no use as i can't see the screen on PC and use the mouse at the same time. I tried adb ( i have no experience of it ) but i cant touch the allow pernmissions key on the screen for the above reasons. Also what advantage would adb be in this case?.
Any advice ?
PS: i have cyanogenmod
I think ram is your only option. It definitely sounds like it's hardware and not software related.
Sent from my Nexus 5 using XDA Free mobile app
Sorry, i don't follow. U mean a ram replacement is needed ?
jd1639 said:
I think ram is your only option. It definitely sounds like it's hardware and not software related.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
nexmus said:
Sorry, i don't follow. U mean a ram replacement is needed ?
Click to expand...
Click to collapse
It was a typo.. He meant RMA
- Sent from an IceCold Hammerhead!
Oh, you mean sending it to LG for servicing? I am a bit hesitant since i have cyanogenmod and also am in india and i doubt they will give a replacement. I think going back to stock rom and then sending it for repairs might help but i have no idea how to go about doing that in this situation.
vin4yak said:
It was a typo.. He meant RMA
Click to expand...
Click to collapse
nexmus said:
Oh, you mean sending it to LG for servicing? I am a bit hesitant since i have cyanogenmod and also am in india and i doubt they will give a replacement. I think going back to stock rom and then sending it for repairs might help but i have no idea how to go about doing that in this situation.
Click to expand...
Click to collapse
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
How can i do it using fastboot ?
rootSU said:
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
Click to expand...
Click to collapse
nexmus said:
How can i do it using fastboot ?
Click to expand...
Click to collapse
I do t understand the question. Is this question one you're asking having already read the fastboot return to stock guide?
Same issue I had pretty much, it died about 2 months ago. I was still able to copy all of my files, phone worked perfectly but the screen was black. Had it replaced it no time. Is that by any mean a 311k? I've seen another thread like that pop up lately.
vnvman said:
Same issue I had pretty much, it died about 2 months ago. I was still able to copy all of my files, phone worked perfectly but the screen was black. Had it replaced it no time. Is that by any mean a 311k? I've seen another thread like that pop up lately.
Click to expand...
Click to collapse
What does the month it was made have to do with anything?
rootSU said:
What does the month it was made have to do with anything?
Click to expand...
Click to collapse
I don't know yet, I'm just trying to figure out whether it's a particular batch that started failing or it's completely random, just curious. The two replacements I was sent were 403K. Build is perfect, but they both had some light bleed issues. Looks like every batch comes with some good and some bad, QC definitely hasn't been too great on this phone.
vnvman said:
I don't know yet, I'm just trying to figure out whether it's a particular batch that started failing or it's completely random, just curious. The two replacements I was sent were 403K. Build is perfect, but they both had some light bleed issues. Looks like every batch comes with some good and some bad, QC definitely hasn't been too great on this phone.
Click to expand...
Click to collapse
They're not really built in batches. Manufacturing was continuous. They just changed the serial number every time the month changes so I dont think this would actually mean anything
I know but I'd still use it as a milestone more than anything, I mean there have been some differences in the units (eg bigger speaker holes), this way it's easier to track them along the timeline, because they definitely do change something in the manufacturing process from time to time if they have to make up for issues or something. They also did it with the N4 if I remember well.
vnvman said:
I know but I'd still use it as a milestone more than anything, I mean there have been some differences in the units (eg bigger speaker holes), this way it's easier to track them along the timeline, because they definitely do change something in the manufacturing process from time to time if they have to make up for issues or something. They also did it with the N4 if I remember well.
Click to expand...
Click to collapse
Speaker holes is a bad example because even the latest built devices it was still a lottery whether you got bigger or smaller holes. That's down to what you mentioned earlier, QC
rootSU said:
Its all done via fastboot or lg flash tool. Probably the latter is best for you. Have a read of the guides in my signature
Click to expand...
Click to collapse
I was able to unroot and flash the stock image. The problem still exists though, so it has to be a hardware issue. Fortunately the phone is still in warranty.
Thanks for all the support.
Hey all,
I'm having a few issues with my multitouch. Firstly using a multitouch app it picks up all of the fingers a different inputs but they flicker unless you're moving your hand around, so it's impossible to use it for games and such. I'm fairly certain that this is a hardware issue. Although it doesn't seem like it's completely broken as I can still register multiple touches, its just impossible to have continuous multiple touches. Any idea on how to fix this?
gfish4573 said:
Hey all,
I'm having a few issues with my multitouch. Firstly using a multitouch app it picks up all of the fingers a different inputs but they flicker unless you're moving your hand around, so it's impossible to use it for games and such. I'm fairly certain that this is a hardware issue. Although it doesn't seem like it's completely broken as I can still register multiple touches, its just impossible to have continuous multiple touches. Any idea on how to fix this?
Click to expand...
Click to collapse
How old is your phone?
itisiryan said:
How old is your phone?
Click to expand...
Click to collapse
Its around a year old.
gfish4573 said:
Its around a year old.
Click to expand...
Click to collapse
It should still be under warranty if you haven't rooted it. So I guess you should take advantage of it.
Sounds like the calibration for the active digitizer for your device needs to be recalibrated.
iceepyon said:
Sounds like the calibration for the active digitizer for your device needs to be recalibrated.
Click to expand...
Click to collapse
How do I go about doing this?
gfish4573 said:
How do I go about doing this?
Click to expand...
Click to collapse
There are some apps for it.
I tried a few of these apps to no avail. I'm going to have to assume its a hardware issue. unless theres any more ideas.
gfish4573 said:
I tried a few of these apps to no avail. I'm going to have to assume its a hardware issue. unless theres any more ideas.
Click to expand...
Click to collapse
Most probably it's a hardware problem.
Could it be that it's a lose connection? Or do you think the whole screen and digitizer assembly will require replacing.
gfish4573 said:
Could it be that it's a lose connection? Or do you think the whole screen and digitizer assembly will require replacing.
Click to expand...
Click to collapse
We'll never know unless we open it up.
Looks like a hardware issue...may be you should replace..
gfish4573 said:
How do I go about doing this?
Click to expand...
Click to collapse
Enter *#*#2664#*#* into the dialer to run the Touchscreen diagnostic test to see if your device's active digitizer is really to blame. I don't know the code that will recalibrate the active digitizer of your device. You would probably have to send your device to Honor to get it recalibrated.
iceepyon said:
Enter *#*#2664#*#* into the dialer to run the Touchscreen diagnostic test to see if your device's active digitizer is really to blame. I don't know the code that will recalibrate the active digitizer of your device. You would probably have to send your device to Honor to get it recalibrated.
Click to expand...
Click to collapse
This code doesn't do anything. I'm not sure Huawei will be willing to do anything as I have unlocked the bootloader for root.
gfish4573 said:
This code doesn't do anything. I'm not sure Huawei will be willing to do anything as I have unlocked the bootloader for root.
Click to expand...
Click to collapse
Haven't opted for repair yet?
itisiryan said:
Haven't opted for repair yet?
Click to expand...
Click to collapse
Will they repair it as I unlocked the bootloader?
gfish4573 said:
Will they repair it as I unlocked the bootloader?
Click to expand...
Click to collapse
Just make everything stock..relock bootloader...
And claim warranty...