My 820 was dropped and cracked, and I had it successfully repaired. It had been having memory issues from day 1, because of all the pictures imported from my Samsung, so I had them do a hard reset after the glass was replaced.
So now I had a physically repaired phone with a clear OS, and I was reloading stuff when a message popped up to update the OS(). I said 'sure' and set the unit down so it could do its thing. I picked it up later, and it was totally bricked. Side-button-based soft and hard resets don't work (buttons respond, but the procedure doesn't work right) and the screen doesn't respond to touch at all.
I simply want to flash it. I tried this procedure from another website, to no avail. I downloaded a lot of files and the Nokia Care App, but I got some permissions denied error, etc.
Does anyone know of a tried-and-true procedure for this?
Much thanks!
IrvAdams said:
My 820 was dropped and cracked, and I had it successfully repaired. It had been having memory issues from day 1, because of all the pictures imported from my Samsung, so I had them do a hard reset after the glass was replaced.
So now I had a physically repaired phone with a clear OS, and I was reloading stuff when a message popped up to update the OS(). I said 'sure' and set the unit down so it could do its thing. I picked it up later, and it was totally bricked. Side-button-based soft and hard resets don't work (buttons respond, but the procedure doesn't work right) and the screen doesn't respond to touch at all.
I simply want to flash it. I tried this procedure from another website, to no avail. I downloaded a lot of files and the Nokia Care App, but I got some permissions denied error, etc.
Does anyone know of a tried-and-true procedure for this?
Much thanks!
Click to expand...
Click to collapse
The 820 and 920 are essentially the same phone. Just a few higher spec hardware bits on the 920. Use the unbrick guide from WPcentral. Google it. (sorry can't post external links yet as am still in noob status). It does work. I have used it.
Hope it helps.
Related
My two months old Nexus S started to behave in a way that renders it pretty much useless - Freezing / Locked U
Freeze/Delay Between Menu and basically the phone is dead.
Very often when the screen is off, pressing power button powers up the screen with the screen lock, but the phone is not responsive so the screen just goes off again as it is impossible to slide to unlock it.
On top of that, leaving the phone with the screen off for a half an hour or so brings up some sort of warning sign and a small android (can see the screen shot here: http://yfrog.com/h3apmgqj) and the phone is effectively dead. The only thing to do in any of the two cases is remove and reinsert the battery, but that is no solution to anything. All this is while the battery is fully charged.
Did anyone experienced this before? resetting phone does not help.
Here is more info on this topic: http://www.google.com/support/forum/p/Google+Mobile/label?lid=4e31a500f89fe575&hl=en
Are you using a custom recovery/ROM? That icon you posted isn't the stock image
Hi, no I do not - the image is actually from different phone but it looks exactly as it did on my Nexus S (little green guy with an exclamation mark). I never rooted my phone or done any custom mods to its system.
I actually sent it to Samsung and they are claiming that they found no problem, so they re-flushed the phone and are sending it back. I am seriously angry at samsung. It is arriving on the 11th so I'll let you know if that helped but I doubt it.
I believe this might be a faulty memory because I often received notification that the internal storage was unavailable or something of that nature as well, right before the problem would occur. Are the any tests I could perform for memory / storage?
just try to flash it back to stock
then do wipe data and wipe cache
see if that gets it back on its feet
Hey,
thank you, I thank that means I would have to root it first ehhh
Samsung told me they've done just that (flashed phone) so I am seriously hoping that my phone will work when it arrives on the 11th.
thanks!
Samsung supposedly is looking into this problem, please see link below:
http://www.google.com/support/forum...ad?fid=44db6d8e31129d4c00049e3b2a6db4d1&hl=en
Update:
I just received my phone from Samsung repair and of course, the phone is NOT fixed. On the side note, they also sent back my note that explains the problem meaning it was ignored completely.
I will be contacting @SamsungServic and calling but at this point I am not sure that they can fix the phone other then replace it.
Also,
I've spoken to Samsung and chat online and - yes they nice and throw back lots of promises and niceness back but they are NOT doing anything about it, for now at least.
I copy and paste the best answer on the google support topic to here:
I've been keeping a notebook to document my debugging of this problem. No app in particular is responsible, in my opinion. I have observed the phone lock up after a Factory Data Reset + USB wipe, and with no accounts configured. In fact, I have had it freeze after following this procedure:
1. Factory Data Reset + USB erase from Settings menu
2. Phone reboots.
3. Go through initial setup screens, skip account setup.
4. Power down phone.
5. Remove battery.
6. Remove SIM card.
7. Replace battery.
8. Power up phone.
9. Let phone sit for 15 minutes or more.
10. Phone freezes.
This is about as close to bare bones as I can get with this device.
I have also documented at least four freeze modes:
1. Phone is completely dark (both display and buttons). No combination of power button or other buttons can bring phone back. Battery removal required.
2. Phone display is dark, but the four "hard key" buttons are illuminated. No combination of power button or other buttons can bring phone back. Battery removal required.
3. Phone displays only a green android by a warning exclamation sign. Holding power button down, then volume up, then release volume up, will bring up the Android system recovery screen, from which phone can be rebooted.
4. Phone is frozen at the unlock screen. Sometimes this freeze occurs while swiping the unlock icon. No combination of power button or other buttons can bring phone back. Battery removal required.
I have observed the phone going from normal standby state (display and buttons dark) to state 2, and at other times to state 3, while it was sitting on my desk by the keyboard.
I'm just about ready to send it to Samsung. I just wanted to verify that the problem would be reproducible after a factory reset and without the SIM card.
I think it may be a hardware problem. It's also possible that part of the Android kernel or some device driver on my device has become corrupt. Unfortunately I can't reset the OS.
Click to expand...
Click to collapse
I did a factory reset from the stock recovery, too. Doesn't help either.
My phone arrived on Friday Samsung mobile repair in Texas. And like they did to ohter Nexus S devices from other users they will do the following to mine:
Reflashing the phone -> doing some functional tests ...
... and this is the crazy thing about it. The error we have is just appearing when the phone is in standby and because of this the phone passes the functional tests Samsung is doing at the end of the service. Phone goes back to user. A defective phone.
Some guy managed to keep the phone alive by setting the display turning off after 30mins. He is charging it twice a day
I got a reply from @SamsungSupport on twitter:
Thank you Fabian for again reaching out to us. We are aware of this issue as some of us have your same phone.
An evaluation is already being conducted to determine the fix. We don't have a timeframe of the resolution.
But understand it will be pushed to phones. We will advise once we have a timeframe.
Click to expand...
Click to collapse
The support team is friendly and to me it feels like they try to do anything they could.
Funny: One guy got a replacement device. But then no one other. Just reflash...
I think they will do something but on the other hand I'm worried that they will do nothing. But time will tell....
Maybe it would help us if Google will be aware of the problem, too. Ok maybe they allready know it, but I don't know that.
So if some of you here do have some connections... please do us a favor and forward this topic or the link to the google support topic. Feel free to forward this topic to any website you think it would write a news about it. Maybe Google will throw a eye on it. My phone is 8 weeks old and yeah this so anoying. And of course all my friends who are iHippster are trolling me like hell.
It don't want to flame or blame Samsung\Google for this.But our phones are in warranty. The error hits only a few devices and so they should replace it. My 50cent about it... this is not a Google expierence they talked about...
I also had the same problem and sent my phone into Samsung. They only re flashed it, which didn't fix the problem. I immediately called Samsung to inform them that the issue was not fixed and they just told me to send it back for "double checking." Do you think it is better to send it back in or just wait for fix to emerge?
I will be sending it back and demand replacing the phone, also making sure they just don't re-flash again. I guess anything but re-flashing could work.
Remember that I've mailed my phone with one page letter explaining the problem. Their response was flashing the phone and sending it back - with my letter.
Here is note from the support team:
----------------------------------------
Original Problem:
Technical Inquiry
Phone Freezing / Locked U
Freeze/Delay Between Menu
Problem found:
NO TROUBLE FOUND
SW,PRL,OTSL RESET
Solution:
Passed All Functional Testing
--------------------------------------
@Samsungservice did not even acknowledge it officially that this is a problem.
Yeah i wrote a letter too explaining the issue and how to recreate it (the first time). They told me that it passed their quality assurance inspection after re-flashing it, which must be very poor because my phone shut off again 15 minutes after receiving it. Just dropped it back off at UPS today. Can they replace the phone because of this issue? I know one person had success, but it doesn't seem anyone else has.
Nexus S faulty
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Guys,
Did anyone have tried to flash a custom rom to see if this will solve the problem ?
cheers !
No, but this problem is not ROM related.
discr said:
Samsung may not be able to reproduce it after reflashing; as this issue does not seem to occur when connected to a PC/computer via USB. Their automated testing could be over USB.
Looks like more and more people are facing this issue as the day goes by.
Search for "Nexus S fault state" on google and you'll find the google support forum thread discussing it
Click to expand...
Click to collapse
I figured that was why they couldn't recreate the shutdown. Made sure they knew that it has to be unplugged. Mine always shuts off within 10-15 minutes if untouched.
I have same problem.Only remove battery helps. I have been having nexus s for 2 and half months and this problem just came last week. I don't know how to solve it. I tried reflash firmware but didn't help.
welcome to the club. you have to send it to USA to get it serviced (make a extreme detailed problem description and make sure the support worker writes it down 1:1 into their ticket system). they provide a 2day ups shippment label, BUT only to locations in USA.
I can recommend FedEx. They helped me a lot with this duty stuff for shipping to USA. That's not so easy . I paid €50 to get it shipped to a friend of mine in USA.
You have to send only the foreparts of the device. No battery and back panel, no charger and so on. But they will give you all informations at the end of the service request.
or: wait for a hotfix. which maybe never will come.
Update:
I just mailed my phone again... they told me they do not replace phones (not sure what that means yet). The Rep was arguing that if I want the phone replaced then I need to talk to T-Mobile - it does not make any sense.
Anyway, I explained the problem as much as I could and did not mail any notes this time as they obviously do not care for it. But I made sure he included every detail in his notes.
I am very skeptical but still hoping....
Also,
About the part when the phone does not freeze when plugged in or charging. I had my Nexus S charging overnight and it was frozen in the morning.
Update:
Also, I've contacted @SamsungServic via Twitter and asked if their team recognized it as a problem, but I've got no response.
On the other hand if you report the problem to them, they will respond that they will look into it - which means nothing, but if enough people asks the same question them they will have to.
-thanks
I've got some sort of responce via Twitter from @SamsungService, here is what they wrote back:
@SamsungService
Thank you for reaching out to us. We are aware of this issue as some of us have your same phone. An evaluation is already being conducted to determine the fix. We don't have a time frame of the resolution, but understand it will be pushed to phones. We will advise once we have a time frame. Thank you. ^Mary
@Keinam
Does this mean we should stop sending our phones back for repair and just wait for your OTA update? If it happens?
@SamsungService
Many issues can be resolved with warranty service. Regarding the issue you've referred to,It is my understanding that a fix if being worked on which would be sent out OTA. ^Mary
Hi,
I recently dropped my i9023 and smashed the glass.
Bought a new screen with digitizer from global direct parts (www globaldirectparts com/Samsung-GT-I9023-LCD-and-Digitizer-Assembly-p/smsng6102150.htm)
Having put the new screen in it boots up fine and displays perfectly but the touch screen is not working at all and I can't do anything. If I put my smashed screen back in touch input works fine.
I've flashed back to stock I9023XXKB3 and I9023XXKB1 firmware, but nothing seems to help.
The ribbon to the screen doesn't appear to be damaged and because global direct parts had a minimum purchase of 2 I have 2 new ones and they are both unresponsive.
Anyone have any ideas?
My first idea would be to have the manufacturer fix it.
Sorry you are having trouble getting the touch screen to respond. I too have cracked my screen and would be very interested in your strip down and replacement steps as I am going to be doing the same. If you get time, could you write down your steps. There is a pretty good teardown at
http://www.ifixit.com/Teardown/Nexus-S-Teardown/4365/1
but I am not confident of the last bit of using a heat gun to separate the screen from the frame. Did yours come off easy ?
Yes I could have sent it to an authorized repairer but I would of been without the phone for a a while and it would cost twice as much. Plus I like pulling things apart.
markread544 - I pretty much followed the ifixit guide. however when pulling out the motherboard make sure the front and rear cameras and speaker are loose as well otherwise it wont come out.
I didn't use a heat gun, I just applied pressure until it started to lift, it would of definitely been easier if it had been warmed up but I didn't want to use a heat gun either. You would want to use an adjustable heat one on low if you did, I think a hair dryer would work as well.
I pulled mine a bit further apart then they did, the grey part in the attached pic comes off as well which makes it easier to get the screen out of the front bezel which it is also glued to.
Phone is back together at the moment with the cracked screen but I'll take some photos if I pull it apart again.
same problem here.
i bought an lcd on ebay for i9023 (slcd)
display OK , but no tactil response.
i had MP the OP but still no answer.
if you have any suggestion
thanks
how much for the screen? seems that 9023 is cheaper than 9020
80 euros for the less expensive , about 120-150 for the others
I ended up returning the screens from global direct parts and after about a month they gave me a refund.
After being quoted AU $250to get the screen replaced by an authorized repairer I decided to try again and bought a replacement screen on eBay from a seller called stream_beautiful for $86.
Got it today, installed and it works perfectly. No idea why the original screens from global direct didn't work.
I'm sorry to bump such an old thread, but I was wondering if there was any more information on this issue... I ordered an i9023 screen to repair a friend's phone about 2 months ago and had the same issue as the OP with it; touch input didn't work. I then contacted the seller (forceviewer on aliexpress) and he told me he'd replace it. After sending it back I then had to contact him again and send him pictures of the back of the old screen (with which touch input still works) because according to him there are 2 versions. Now I received the second screen a week ago and lo and behold, it exhibited the same problems. I noticed a number on the back of the screen is different, and the atmel IC (which I assume handles the digitizer input) has a different number on it too, however the seller has now adopted the position that it is definitely the correct display (quote: "If the pictures is right
The item will be right
I just send you the one same with your picturs
There are only two version.
Thanks")
Can anyone shed some light on what causes this? I know the guy's company tests their displays before sending them out, so that's probably not the problem, and receiving 2 faulty units in a row would be a bit weird, so I guess there's actually multiple versions (with a different digitizer controller IC?) which aren't compatible with each other... How do I make sure I'm getting the right one for my friend's phone? And, optionally, how would I go about convincing the seller to take this one back too and send me one that really works?
I'm having exactly the same issue...two replacement screens and touch input non responsive, re-install original and hey presto no problem...what I have noticed is that the part number on what I assume is the digitizer is different...
original -> KJ00423-101228-P00-7F-1
replacement -> KJ00423-101228-P00-5F-1
Yeah, my replacement says 6F-1 at the end, I can't check the original right now because my friend has his phone, but I'm willing to bet it doesn't say the same. Maybe I can make my case with this with the vendor, I'd really hate to have to buy another one of these displays for nothing
Guys,
It's the third SLCD screen that one of my fried is replacing to my I9023 Nexus S, and none of them is working. Yesterday he told me that when he bough the third one, the seller told him to "reprogram" the phone, because the drivers for new SLCD will be installed only then.
To be honest I didn't quite understood him, so, I though that the seller means to flash with a ROM. I did that, I installed CyanogenMod 9, everything went fine, but the touch still not working .
Does anyone knows how the phone could be completely wiped. Meaning everything what is in it to be reinstalled from the beginning....
I don't know what else to do, besides to buy a new phone
Hi All,
Just want to ask if anyone came to the solution yet ...?
Cheers,
no touch
Hello
i have the same problem:
1. The display works
2. But no touch reaction
i had bought a new screen for my I 9023 .
thanks for solutions
Yep, I have the same problem.
Original: KJ00423-101216-P00-1F-1
Replacement: (Not responding to touch): KJ00423-110207-P00-1F1
eBay Seller: mike410512
Bump - anyone sort this issue out?
I know this is an old thread, but since I have a shattered SLCD screen and i'm willing to replace it, i'd like to know what to do in case there's no touch response...
To get touch input again
Hi all,
I have smashed my phone screen twice on my S3 i9300. The first time I had the issue with the touch screen not detecting input but displaying correctly, I had taken it to an authorised repair centre and initially they did not know what was wrong.
There is only one way to "fix" this situation. You must remove the custom recovery and then reflash your phone with the stock samsung rom. Flashing the stock rom with stock recovery should pose no problem as it will be "official" and thus not blocked by stock recovery.
After reflashing, you must do a factory wipe + data reset. This is where you change your screen, making sure not to boot the phone for "the first time". If it does not work, repeat the reflash + factory wipe and try again.
The samsung rom will register the new hardware profile, and touch input will work. Why it works this way is beyond me, but taking these steps when changing the screen on a custom rom will ensure that the touch input works. Perhaps custom roms "borrow" drivers left over from stock rom? I don't know.
You can back up your current rom and restore after messing around with the samsung stock rom and you have gotten your touch screen working properly.
I have tried a whole heap of different "solutions" with this problem and this is the only one that works, and if you are taking it to a repair centre, make them aware that you have a custom rom installed.
Change screen
sinphild said:
Hi all,
I have smashed my phone screen twice on my S3 i9300. The first time I had the issue with the touch screen not detecting input but displaying correctly, I had taken it to an authorised repair centre and initially they did not know what was wrong.
There is only one way to "fix" this situation. You must remove the custom recovery and then reflash your phone with the stock samsung rom. Flashing the stock rom with stock recovery should pose no problem as it will be "official" and thus not blocked by stock recovery.
After reflashing, you must do a factory wipe + data reset. This is where you change your screen, making sure not to boot the phone for "the first time". If it does not work, repeat the reflash + factory wipe and try again.
The samsung rom will register the new hardware profile, and touch input will work. Why it works this way is beyond me, but taking these steps when changing the screen on a custom rom will ensure that the touch input works. Perhaps custom roms "borrow" drivers left over from stock rom? I don't know.
You can back up your current rom and restore after messing around with the samsung stock rom and you have gotten your touch screen working properly.
I have tried a whole heap of different "solutions" with this problem and this is the only one that works, and if you are taking it to a repair centre, make them aware that you have a custom rom installed.
Click to expand...
Click to collapse
Did anybody else use this way?
spanusorin2005 said:
Did anybody else use this way?
Click to expand...
Click to collapse
UP ..
i'm going to buy a screen + digitizer and i would have some advice about this, what code should i look ??? there are only two kind of screen or more ? what should i ask to the seller ???
I bought this phone for my bride. THe screen was smashed it was changed and now the phone will not boot. It ios recognized by the computer and shows up as the proper device. THe screen is just dead. It vibrates, but that's all. There is no screen I have tried everything I can think of. I have done the hard and soft reset with no luck. Of course, I can't be sure as I can't see the screen. I was able to use a Nokia program to update the software. (Nokia Software recovery Tool version 1.5.0) see attached photo. Any ideas or help is appreciated. When the phone reboots the software is asking for the phone pin. This is impossible for me to input it because I don't know it and further I have no way to input it. Any advice is needed.
Hello, that's sad.
Something you can do is disassemble it and see one of those disassembly videos and check if something is wrong.
Example :
Maybe this one is not the best, but you can surely find one with lots of details on connections.
If you're lucky, it's only a connector not correctly linked.
Who has changed the screen ?
Not that lucky
The connections are correct. I'm starting to think BRICK.. These window phones are just garbage in my opinion or I am just dumb or both. I got to figure this out as it is what my bride wants. I again thank all of you for any ideas.
did you make it work?
I have the same problem like you...
Hello All,
In my attempt to root the device which I was successful in doing somehow things went south when i tried to flash TWRP on my device. I performed the .img to tar.md5 conversion with the CWM Tool on another thread then i flashed the file to my device, afterwards the devices were rebooted and now I am unable to touch the screen with my fingers and only my S-Pen works, which tells me hardware wise the screen is ok but something software wise is causing this issue. Can someone please help me in troubleshooting this issue. I seen another user have this same exact issue but it ended with him sending it to the service center. I have performed a full dat/factory reset.... I have performed a full reflashing of the stock rom i have re-rooted. I am all out of options.
See video i made regarding this issue.
https://www.youtube.com/watch?v=orLEnWhlATo
Thanks in advance!
Can anyone help with this
Capacitive touch and spen use 2 totally different chips inside the tablet. The spen uses a Wacom digitizer, while touch interaction is processed using standard methods.
In fact, each one has their own ribbon cable from the screen to different points on the motherboard.
I have no idea how rooting broke your touch ability, but the spen working is not an indication that the touch interaction is not damaged in some way.
I can tell you that on mine (especially when using papyrus) it has a tendency to lose touch until I shut the screen off and turn it back on. Maybe something screwy is going on with the touch driver. Flash back to stock and see if it's still broken
Did the reset work?
I ask because we just got a used tablet off ebay and it is doing the same thing to me. My wife emailed Samsung who said blah-blah-blah so we are stuck with it. I know enough to brick a phone really fast, but I have been running custom Roms a long time and have replaced screens so I may check the cables on my day off.
But it was doing it before I rooted it, recovery, and Hyper-drive Rom.
though the knox had been tripped before I got it, so I don't know what has been done to it before this. So please let me know what you think even if you try it and it does or doesn't work and I will gladly do the same for you.
Thanks--Rick
Hi,
I have Nexus 5 and was running good with Marshmellow and suddenly one day the screen started scrolling up. Restart or factory reset did not help. While starting the boot logo was also corrupted and I use to get is display with random pixels lit with different colors, mostly white and red. So have tried different bootloaders and even downgrading to 4.4.4 but the issue is still there.
Called up Google and LG as well. Since device is not under warranty now, it is going to cost for repair. So would like to know if there is any solution to this problem before I try the repair or give on this device.
Appreciate any suggestions. Thank you,
Sandeep.
Was the phone ever dropped? It's possible that there is a loose connection inside the phone. I suggest removing the back and inspecting the phone's internal components and connections.
If everything appears fine, it could be A problem with the lcd of motherboard, neither of which is cheap to repair. I suggest trying to find a used nexus 5, either with a smashed screen and working internal components or one with a working screen and damaged internals to troubleshoot your own phone.
audit13 said:
Was the phone ever dropped? It's possible that there is a loose connection inside the phone. I suggest removing the back and inspecting the phone's internal components and connections.
If everything appears fine, it could be A problem with the lcd of motherboard, neither of which is cheap to repair. I suggest trying to find a used nexus 5, either with a smashed screen and working internal components or one with a working screen and damaged internals to troubleshoot your own phone.
Click to expand...
Click to collapse
I do not recollect dropping it. I would wait to see if any better option comes up. And will keep an eye for an broken Nexus to see if I can get the motherboard swapped. Thanks for ideas though.