Related
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 ???
My Infinity's bootloader is unlocked and I was rooted. It was running a little slowly so I decided to do a factory reset. It rebooted and just froze on the ASUS booting screen.
Tried rebooting it and it just froze on ASUS screen again.
So I tried starting while holding power + vol down and the recovery options were there. I went over to Wipe data and it said "wiping data" then it just froze on "initiating bootloader" so I had to force a reboot.
Now it just stays stuck on the ASUS boot screen. When I attempt to hold power and vol down the recovery options never even come up now. It just stays stuck on the ASUS screen.
When I hold down the power button the device never stays off. The screen will turn off, it'll vibrate, and then just try to boot up again.
I tried putting a paper clip in the hard reset hole to press the button and it will reset the device but my issues are still the same.
Is there some way to recover the device either with a computer or by putting files on the MicroSD card or something? I heard something about that but can't find any solid info on what to do. Any help is appreciated.
wushdishmeen said:
My Infinity's bootloader is unlocked and I was rooted. It was running a little slowly so I decided to do a factory reset. It rebooted and just froze on the ASUS booting screen.
Tried rebooting it and it just froze on ASUS screen again.
So I tried starting while holding power + vol down and the recovery options were there. I went over to Wipe data and it said "wiping data" then it just froze on "initiating bootloader" so I had to force a reboot.
Now it just stays stuck on the ASUS boot screen. When I attempt to hold power and vol down the recovery options never even come up now. It just stays stuck on the ASUS screen.
When I hold down the power button the device never stays off. The screen will turn off, it'll vibrate, and then just try to boot up again.
I tried putting a paper clip in the hard reset hole to press the button and it will reset the device but my issues are still the same.
Is there some way to recover the device either with a computer or by putting files on the MicroSD card or something? I heard something about that but can't find any solid info on what to do. Any help is appreciated.
Click to expand...
Click to collapse
Not looking too good, possible bricked and need to send in. Give it another try, as soon as the device turn off, hold volum down and power button, see if some how magically boot back into recovery?
Edit: is your pc detecting your device?? just plug in the usb and let it boot up.
buhohitr said:
Not looking too good, possible bricked and need to send in. Give it another try, as soon as the device turn off, hold volum down and power button, see if some how magically boot back into recovery?
Edit: is your pc detecting your device?? just plug in the usb and let it boot up.
Click to expand...
Click to collapse
If that's true then this thing is pretty crappy. I've only had it for a few months and I never flashed any custom ROMs to it and all I did was the factory reset which is a stock feature. I unlocked the bootloader with ASUS's official tool.
My Galaxy S3 is nearly impossible to brick... there's always a way to boot into either stock or custom recovery. Then you always have the option to flash it back to stock using Odin.
It's not showing up in My Computer either. Isn't there some way to force a flash by loading some files onto the MicroSD card? There has to be some last resort option other than sending it back.
wushdishmeen said:
If that's true then this thing is pretty crappy. I've only had it for a few months and I never flashed any custom ROMs to it and all I did was the factory reset which is a stock feature. I unlocked the bootloader with ASUS's official tool.
My Galaxy S3 is nearly impossible to brick... there's always a way to boot into either stock or custom recovery. Then you always have the option to flash it back to stock using Odin.
It's not showing up in My Computer either. Isn't there some way to force a flash by loading some files onto the MicroSD card? There has to be some last resort option other than sending it back.
Click to expand...
Click to collapse
There are but I don't think any one of these options apply:
1. Do you have nvflash backup? --nope
2. Do you have recovery ?--nope (probably corrupted bootloader due to factory wipe)
3. Can you pc see your device through ADB or fastboot ?-- I don't think so either.
So without the 3 mentioned above, your device is bricked. Just curious, what kind and what version of your recovery?? also what bootloader version you're using before the crash?
buhohitr said:
There are but I don't think any one of these options apply:
1. Do you have nvflash backup? --nope
2. Do you have recovery ?--nope (probably corrupted bootloader due to factory wipe)
3. Can you pc see your device through ADB or fastboot ?-- I don't think so either.
So without the 3 mentioned above, your device is bricked. Just curious, what kind and what version of your recovery?? also what bootloader version you're using before the crash?
Click to expand...
Click to collapse
I had the latest jellybean firmware and my device was up to date. I don't know what version my bootloader is... I'm guessing the latest version since I updated to jellybean? My recovery WAS working... I went into the settings and chose "Wipe data" and it said it was wiping data... but then froze on initializing boot or something.
I can get my computer to recognize it in APX mode if I start with Power button and Vol Up. But my computer doesn't have the drivers so it says "installing device" and APX driver is missing. Plus the screen on my tablet is just pitch black when I boot it in APX mode. Can I do anything with APX mode? Maybe use somebody else's NVflash backup? There has to be a way if ASUS is able to "repair" it when they get it. If someone here can figure it out for me I'll pay them $50 via PayPal or something.
This is such bullcrap. I'm always able to recover from a brick with any other android device. Why is this thing basically programmed to force a repair? I contacted ASUS and somehow the customer service rep knew my device's bootloader was unlocked. I'm guessing when you use the ASUS Bootloader tool it sends ASUS your serial number so they know you unlocked the device.
So the guy is claiming I am going to be charged $200 for the repair/replacement because my device is unlocked??? Are you kidding me? I rather just throw this thing out the window for fun.
ASUS entices you with an official bootloader unlock tool then clearly makes it so the device will brick if you basically try any sort of factory wipe. Plus the bootloader tool doesn't offer the option to re-lock the bootloader like every other device and third party unlock app does. Clearly making it so once you take the plunge you're screwed if you ever run into issues.
wushdishmeen said:
I had the latest jellybean firmware and my device was up to date. I don't know what version my bootloader is... I'm guessing the latest version since I updated to jellybean? My recovery WAS working... I went into the settings and chose "Wipe data" and it said it was wiping data... but then froze on initializing boot or something.
I can get my computer to recognize it in APX mode if I start with Power button and Vol Up. But my computer doesn't have the drivers so it says "installing device" and APX driver is missing. Plus the screen on my tablet is just pitch black when I boot it in APX mode. Can I do anything with APX mode? Maybe use somebody else's NVflash backup? There has to be a way if ASUS is able to "repair" it when they get it. If someone here can figure it out for me I'll pay them $50 via PayPal or something.
This is such bullcrap. I'm always able to recover from a brick with any other android device. Why is this thing basically programmed to force a repair? I contacted ASUS and somehow the customer service rep knew my device's bootloader was unlocked. I'm guessing when you use the ASUS Bootloader tool it sends ASUS your serial number so they know you unlocked the device.
So the guy is claiming I am going to be charged $200 for the repair/replacement because my device is unlocked??? Are you kidding me? I rather just throw this thing out the window for fun.
ASUS entices you with an official bootloader unlock tool then clearly makes it so the device will brick if you basically try any sort of factory wipe. Plus the bootloader tool doesn't offer the option to re-lock the bootloader like every other device and third party unlock app does. Clearly making it so once you take the plunge you're screwed if you ever run into issues.
Click to expand...
Click to collapse
Yes, I feel you man, did you had CWM custom recovery? When you did the factory reset, did you do it in the system settings or you did it through recovery (wipe data icon)? APX mode is for nvflash backup recovery and nvflash is specific per device, so you can't use someone else nvflash. I know you're mad, but it's still cheaper to get it repair than to buy another device with the same amount of money for the same meat.
ASUS Infinity Won't Boot Into Recovery BRICK ($50 IF YOU CAN HELP FIX IT)
buhohitr said:
Yes, I feel you man, did you had CWM custom recovery? When you did the factory reset, did you do it in the system settings or you did it through recovery (wipe data icon)? APX mode is for nvflash backup recovery and nvflash is specific per device, so you can't use someone else nvflash. I know you're mad, but it's still cheaper to get it repair than to buy another device with the same amount of money for the same meat.
Click to expand...
Click to collapse
Yea I am seriously baffled by this. ASUS just lost another customer. I was doing the reset so I could sell the device and put the money towards something else. It figures this happens...It's almost like the ASUS gods are trying to screw me over so I am stuck with their crap device. This is shady business considering all my other android devices are so easily recoverable and they don't even offer a tool to unlock the bootloader. You have to do it via a third party method and somehow even that is recoverable easily. You don't find it strange that ASUS offers the tool themselves and it's the only tablet that is unbrickable?
Again... $50 to the first person who can help me unbrick this thing. I will send it via PayPal for sure. The money is not the issue it's the principle of giving ASUS $200 more of my money when I know for a fact they programmed this thing to brick so they could pick my pockets. I'm getting really angry just thinking about it and I am close to smashing this thing with a hammer and filming it for YouTube.
Here is the exact chain of events.
1) I went into Android settings, backup/restore, and then choose Factory Reset. It restarted the tablet and just froze on the ASUS screen where it says "the device is unlocked" in the top left corner.
2) I waited 15 minutes and nothing happened. So I was forced to hard reset. After resetting the same crap happened and it just stayed on the ASUS logo screen.
3) I tried booting it with Power + Vol Down and got the recovery options. (i seriously wish I stopped here and checked the forum because I could of possibly fixed it). Figuring it would help, I went over to the WIPE DATA option in the recovery menu.
4) It said "wiping data.." and then said it was initializing bootloader or something and it just froze at that point.
5) Waited another 15 minutes and nothing happened. At this point I wasn't worried because every other device I have I would have ODIN as the last resort and it ALWAYS works.
6) Reboot the device again and that's where I'm at now. It stays on the ASUS boot screen and goes nowhere. I've tried getting back into recovery with Power + Vol Down but the options never appear again. Just goes to the normal boot screen no matter what I do and hangs there. It's clearly setup to brick itself which is incredibly ridiculous.
Do you think a method to fix it will come out eventually or is it impossible to unbrick this thing? Would replacing the motherboard from another tablet that was never unlocked fix the issue? I see the motherboard for this tablet selling for $175 and the iFixit teardown shows how to take it apart. It doesn't look too difficult.
I just cannot believe that an hour ago I had a $500 tablet and now the thing is worthless unless I want to shell out another $200. I seriously wish I didn't buy this thing. Maybe I can take it apart and sell the parts separately as is and hope to salvage my money back.
buhohitr said:
Yes, I feel you man, did you had CWM custom recovery? When you did the factory reset, did you do it in the system settings or you did it through recovery (wipe data icon)? APX mode is for nvflash backup recovery and nvflash is specific per device, so you can't use someone else nvflash. I know you're mad, but it's still cheaper to get it repair than to buy another device with the same amount of money for the same meat.
Click to expand...
Click to collapse
Also I did have CWM because I remember going through a tutorial and it being different than all my other devices. I had the RCK icon as the first option when I booted with Power + Vol Down.
The options were an RCK icon, a USB icon, something else I don't remember, and then Wipe Data/reset icon. I chose the wipe data icon and that's when my device was bricked. But FIRST I used the factory reset in the android settings under Backup/restore and it froze during that which is what caused me to try the factory wipe in the recovery options.
Would not having CWM improve my options to unbrick it? Or is having CWM a good thing?
It's bricked in my opinion.
You possibly had an old version of cwm that was incompatible with the JB bootloader. You asked the bootloader to wipe which asked the incompatible recovery to do it and it has corrupted the bootloader partition.
Without nvflash backups which you don't have you have no other choice other than to pay Asus to fix it (they will probably switch the motherboard) or sell it for scrap.
I don't think anyone on here can get you unbricked. There is always a risk something can go wrong when unlocked with custom recoveries which is why Asus make you agree to a waiver.
Sorry.
I've decided the best course of action is to part out the tablet. The digitizer alone goes for $130 on eBay and I could make $200 if I just sell the front panel, LCD, and digitizer as one assembly. It would actually be super useful to someone with a cracked screen since mine is flawless and you can remove a screen by simply popping a few clips inside the hinge holes for the keyboard dock and then a few around the device. Then they would just have to take mine, connect a ribbon cable, and then snap it into place.
Then I can probably sell the rest of the parts here or there for at least $100 and that's 80% of my money back already. The only other option is to just hold onto the thing and hope that someone here figures out a fix for this issue in the future. But I rather have the money now and just be done with this crappy product. Never buying ASUS again and I'm steering everyone else I know away from them as well.
If I paid ASUS the $200 to replace the motherboard and then sold the fully functional repaired tablet I would only get about $390 if I'm lucky. Newegg sells them brand new for $450 now already and I paid $490 for it not even 6 months ago. So I'd actually LOSE money if I sold it brand new even if I didn't need the repair. Fact is people need parts for their tablet more than they need the tablet itself.
sbdags said:
It's bricked in my opinion.
You possibly had an old version of cwm that was incompatible with the JB bootloader. You asked the bootloader to wipe which asked the incompatible recovery to do it and it has corrupted the bootloader partition.
Without nvflash backups which you don't have you have no other choice other than to pay Asus to fix it (they will probably switch the motherboard) or sell it for scrap.
I don't think anyone on here can get you unbricked. There is always a risk something can go wrong when unlocked with custom recoveries which is why Asus make you agree to a waiver.
Sorry.
Click to expand...
Click to collapse
Don't be sorry it's not your fault. It's ASUS' fault for releasing a bootloader tool that voids your warranty and then sets your device up to brick by removing your recovery options after a normal factory wipe. Why else would they release a tool that they are fully aware could brick your device with no chances of recovery? Especially since it doesn't let you re-lock the bootloader. Your serial number is sent to them the minute you unlock your device so it's not like someone would try to re-lock it to hide the fact that they locked it. So the only reason could be to make money off repairs.
Thanks for the attempted help guys it is very much appreciated. ASUS left a bad taste for sure. I own a lot of their products and I'm just really disappointed.
wushdishmeen said:
I've decided the best course of action is to part out the tablet. The digitizer alone goes for $130 on eBay and I could make $200 if I just sell the front panel, LCD, and digitizer as one assembly. It would actually be super useful to someone with a cracked screen since mine is flawless and you can remove a screen by simply popping a few clips inside the hinge holes for the keyboard dock and then a few around the device. Then they would just have to take mine, connect a ribbon cable, and then snap it into place.
Then I can probably sell the rest of the parts here or there for at least $100 and that's 80% of my money back already. The only other option is to just hold onto the thing and hope that someone here figures out a fix for this issue in the future. But I rather have the money now and just be done with this crappy product. Never buying ASUS again and I'm steering everyone else I know away from them as well.
If I paid ASUS the $200 to replace the motherboard and then sold the fully functional repaired tablet I would only get about $390 if I'm lucky. Newegg sells them brand new for $450 now already and I paid $490 for it not even 6 months ago. So I'd actually LOSE money if I sold it brand new even if I didn't need the repair. Fact is people need parts for their tablet more than they need the tablet itself.
Don't be sorry it's not your fault. It's ASUS' fault for releasing a bootloader tool that voids your warranty and then sets your device up to brick by removing your recovery options after a normal factory wipe. Why else would they release a tool that they are fully aware could brick your device with no chances of recovery? Especially since it doesn't let you re-lock the bootloader. Your serial number is sent to them the minute you unlock your device so it's not like someone would try to re-lock it to hide the fact that they locked it. So the only reason could be to make money off repairs.
Thanks for the attempted help guys it is very much appreciated. ASUS left a bad taste for sure. I own a lot of their products and I'm just really disappointed.
Click to expand...
Click to collapse
Unfortunately it's not Asus, unlocking or the bootloader that is the problem - it's the older incompatible version of CWM that has caused the issue. It didn't understand what you asked it to do as it is not compatible with Jelly Bean. You need to get this part clear. Many people wipe successfully from Android or the bootloader from ICS and JB regularly. Asus don't write code into their bootloader to deliberately brick your device when wiped. They also don't support custom recoveries that are not compatible with their bootloaders.
It is a documented issue that has caused others like yourself to brick your device when wiping JB when still essentially on an ICS recovery. Unfortunately there is no way you would know this without some research and Asus can't be held responsible for it as you waived your warranty when you unlocked for this very reason. Why should they pay for something you did that they don't support?
I know that doesn't help solve your problem but in this case it is not Asus who is at fault.
Re: ASUS Infinity won't boot into recovery or startup ($50 to person who helps fix it
sbdags said:
Asus can't be held responsible for it as you waived your warranty when you unlocked for this very reason. Why should they pay for something you did that they don't support?
I know that doesn't help solve your problem but in this case it is not Asus who is at fault.
Click to expand...
Click to collapse
Asus should really give us our SBK when we unlock our devices - the we could fix this ourselves using nvflash.
_that said:
Asus should really give us our SBK when we unlock our devices - the we could fix this ourselves using nvflash.
Click to expand...
Click to collapse
Yes but I can totally understand why they don't as it would be a nightmare to support. It's a shame it cannot be reverse engineered.
sbdags said:
Yes but I can totally understand why they don't as it would be a nightmare to support. It's a shame it cannot be reverse engineered.
Click to expand...
Click to collapse
They don't support an unlocked device anyway. It would be as easy as returning the SBK from the server together with the unlock token.
As I said I understand the idea of the warranty being voided by using the unlock tool. But ASUS certainly has programmed the device to brick when using custom recoveries which is something you just said yourself. They are being irresponsible by offering this tool and not telling customers that a custom recovery would brick the device for good. You honestly think they don't know this will happen?
My Galaxy S3 has an unlocked bootloader (through a third party method nonetheless), is rooted, has CWM recovery, is on Jellybean, and the recovery options never disappear with a factory wipe. So clearly it's possible. Even if the device won't boot into android it will still be recognized by Odin because it has download mode built in as a start up option. Holding power + vol up will allow me to enter download mode and I can flash the stock ROM again.
Unlike APX mode I don't need some encrypted nvflash backup just to recover my device. I can simply use the stock ROM to recover my device back to stock no matter what ROM or recovery I'm running. I maybe gave you the impression that I didn't know what I was doing. This issue is something that anyone could fall into and frankly ASUS should be telling people not to use factory wipe if they install a custom recovery. Why would they offer a bootloader unlock for any other reason than to cater to people who want to install custom recoveries and flash ROMs? There's no other use for it to a typical consumer.
The ASUS Infinity loses it's ability to communicate with your computer when this happens. That's the problem here. They need to either need to make it impossible to flash a custom recovery altogether or put a warning on their website near the download that says "Custom recoveries could brick your device when doing a factory wipe". Seeing as it's a well documented issue like you claim.
We are all entitled to our opinion. I'm not buying ASUS products anymore. It's not like I did something wrong and screwed it up. I did something that's possible on every other modern android device and was kicked in the nuts for it.
_that said:
Asus should really give us our SBK when we unlock our devices - the we could fix this ourselves using nvflash.
Click to expand...
Click to collapse
So you're saying that it is actually possible to fix it if you had access to something that ASUS is voluntarily withholding from TF700T owners? So here is my question then. Why is it that ASUS is charging customers for motherboard replacements in order to fix this issue rather than simply reprogramming the existing motherboard?
I have never in my 18 years of working with computers seen a software issue corrupt or destroy a piece of hardware, whether directly or indirectly related to it. Whether we as consumers have the tools available to recover from the software issue is not the point. Nor am I saying that ASUS should fix it for free, since they clearly state that using the tool will void your warranty. My point is that ASUS should certainly have the ability to simply reprogram our motherboards for a reasonable fee, rather than forcing a motherboard replacement and charging 50% of the tablet's price to fix it.
To claim that the motherboard needs to be replaced is the same as me saying your computer's motherboard needs to be replaced because your Windows installation was corrupted. It just doesn't happen and Windows certainly also has it's share of bootloader errors. There is always a way to recover from software issues and salvage the hardware, unless it's some incredibly rare series of failures that lead to an electrical problem that fries the hardware. Which is certainly not the case here or anything remotely close to it.
MOD EDIT: DELETED
What I said was they should not be charging $200 for a replacement motherboard for a software related issue. They should be charging a reasonable fee to reprogram the existing component. From what I hear they also permanently lock the boot loader on the replacement motherboard. This is not helpful at all considering you lose the ability to customize your device now that you've learned what not to do.
Also warning people that a custom recovery can brick your device is not that crazy even though you seem to think it is. It's a well documented issue and the only thing that bricks the device. Not to mention the only purpose of unlocking the boot loader is so you can flash custom recoveries. So it's not like they have to run through a long list of possible problems like your over exaggeration implies.
Anyway... I managed to disassemble the tablet without breaking anything.
Question: Does anyone know if there is any way to reprogram the motherboard? Even with some sort of software or tool to connect it to a computer? Does swapping the motherboard with one that was never unlocked give the device a new serial status or will ASUS still think it's an unlocked device?
I'm assuming not obviously but I might as well ask. I guess my choices are to either spend $160 on a new motherboard and swap it out and sell it, or further disassemble and sell the parts. If anyone needs a flawless brand new digitizer and LCD panel let me know.
Thought I'd share some photos so others in the same situation feel more comfortable taking it apart. It was actually really easy. The motherboard is the long dark green component running along the top.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wushdishmeen said:
So you're saying that it is actually possible to fix it if you had access to something that ASUS is voluntarily withholding from TF700T owners?
Click to expand...
Click to collapse
From my understanding of the situation, after all that I read about the Tegra 3, APX mode, NVFlash etc.: yes, it would be possible if you knew the unique 128 bit AES "secure boot key" that is burnt into the fuses of your Tegra 3 chip. This key together with NVFlash enables you to write arbitrary partitions or blocks to the eMMC.
wushdishmeen said:
So here is my question then. Why is it that ASUS is charging customers for motherboard replacements in order to fix this issue rather than simply reprogramming the existing motherboard?
Click to expand...
Click to collapse
I can only guess that their service centers do not have access to the database that stores the mapping from serial numbers to SBKs, and that they are generally unorganized - which shows because so many people have problems unlocking their tablets.
wushdishmeen said:
I have never in my 18 years of working with computers seen a software issue corrupt or destroy a piece of hardware
Click to expand...
Click to collapse
It happens... https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557
wushdishmeen said:
To claim that the motherboard needs to be replaced is the same as me saying your computer's motherboard needs to be replaced because your Windows installation was corrupted.
Click to expand...
Click to collapse
I agree - it's ridiculous and only the consequence of trying to lock users out of their own devices. I think the whole crap is due to DRM, to make media companies happy.
wushdishmeen said:
Also warning people that a custom recovery can brick your device is not that crazy even though you seem to think it is. It's a well documented issue and the only thing that bricks the device.
Click to expand...
Click to collapse
For Asus, there are no "well documented issues". They don't even document the issues they fix with firmware updates. Their customer service is a joke. And they don't need it - they are a big company. Big companies do not succeed by providing good customer service, they succeed by sucking slightly less than other big companies.
wushdishmeen said:
Question: Does anyone know if there is any way to reprogram the motherboard? Even with some sort of software or tool to connect it to a computer?
Click to expand...
Click to collapse
The "official" way is simply via USB in APX mode, but that's impossible without the SBK due to the encryption. The low-level way would be JTAG, but I have read that it is disabled on encrypted devices, and I don't even know where the connector is.
If you didn't know yet, here are more pictures of the internals:
http://www.ifixit.com/Teardown/Asus+Transformer+Infinity+TF+700+Teardown/10306/1
wushdishmeen said:
Does swapping the motherboard with one that was never unlocked give the device a new serial status or will ASUS still think it's an unlocked device?
Click to expand...
Click to collapse
Every Tegra 3 has a unique chip serial number. And the Asus serial number is stored on the eMMC.
Thanks for actually reading my post and providing all that useful info. I appreciate that you took the time and also understood where I was coming from. My first few posts were a reaction to the realization that it was bricked and I might have to pay $200 to fix it. But everything after that was a legitimate concern for the way ASUS is choosing to handle this issue. Hopefully anyone else who ends up in this situation will see this thread and it'll help them. I went through the motions for them and will hopefully end up with a good result either by swapping the motherboard myself or selling the parts for a good profit. I'll let everyone know the outcome either way.
_that said:
It happens... https://bugs.launchpad.net/ubuntu-cdimage/+bug/1040557
Click to expand...
Click to collapse
I didn't read what the entire issue was. But I can make a guess that this is an issue that can be resolved and the problem is just that the common consumer doesn't have the tools to fix it themselves. My actual point was not that we should be able to fix the ASUS tablet ourselves, but that ASUS should be able to fix it without needing to replace the motherboard.
_that said:
The "official" way is simply via USB in APX mode, but that's impossible without the SBK due to the encryption. The low-level way would be JTAG, but I have read that it is disabled on encrypted devices, and I don't even know where the connector is.
If you didn't know yet, here are more pictures of the internals:
http://www.ifixit.com/Teardown/Asus+...ardown/10306/1
Click to expand...
Click to collapse
When you said JTAG I was thinking of the tools I have for my XBOX to JTAG and flash the NAND. That's unfortunate that it's not possible.
I'm aware of the iFixit article. I looked at it before taking the tablet apart and it helped me avoid breaking the side clips like he did. The reason I took the pictures wasn't because I thought there were none. It was basically just visual proof to instill confidence and encourage people to take theirs apart as well. I figure if they see a regular person like me take it apart with no hesitation they might opt to replace their own motherboard rather than pay ASUS $200.
_that said:
Every Tegra 3 has a unique chip serial number. And the Asus serial number is stored on the eMMC.
Click to expand...
Click to collapse
Is the eMMC part of the motherboard or separate? I'm just curious if I could continue the warranty of whatever motherboard I install in the tablet. If I could even figure out the serial number to it.
wushdishmeen said:
I'm aware of the iFixit article.
...
Is the eMMC part of the motherboard or separate?
Click to expand...
Click to collapse
Read the whole article, there are pictures of the motherboard with the chips explained - one of them is the eMMC.
wushdishmeen said:
I'm just curious if I could continue the warranty of whatever motherboard I install in the tablet. If I could even figure out the serial number to it.
Click to expand...
Click to collapse
I don't think you have any warranty on a "naked" motherboard at all except if it was installed by an authorized service center.
So it looks like I have a phone to return.
I had the winning bid for a Doubleshot. Got it today, turned it on (with a spare battery), no problem setting it up. No issues unlocking the bootloader as well. I then set the device up for Google Play, then I ran into problems.
I slid the keyboard out to register with Google, typed two letters, and the device turned off. I relocked the bootloader, and factory reset the device, still shuts off when I use the physical keyboard. I then (on a whim) tried every configuration when I first used the device (SIM card in, SD card out), still nothing.
I fear the flex cable is acting up already. Any other ideas? Anything I can do without tearing it apart (rather return it)? Would I get a hassle for having a re-locked device (should I even mention that part, or let them figure it out - would rather be without my money because they wouldn't take it back than be without both because I neglected to mention before - not that it would be a software issue)?
Thanks in advance.
Unlikely they'd ever notice that you tried unlocking the bootloader and it sounds like they tried to pawn off a failing doubleshot on you so i guess you don't have to feel bad about returning it modded, especially because any warranty it may have had definitely expired a long while ago.
just don't tell eBay because they will likely side with the seller if you let them know you did any modding, even if it was fully reversed.
Ziida said:
Unlikely they'd ever notice that you tried unlocking the bootloader and it sounds like they tried to pawn off a failing doubleshot on you so i guess you don't have to feel bad about returning it modded, especially because any warranty it may have had definitely expired a long while ago.
just don't tell eBay because they will likely side with the seller if you let them know you did any modding, even if it was fully reversed.
Click to expand...
Click to collapse
Thanks Ziida. I don't know if I would call it fully reversed, because HBOOT now says "**RELOCKED**" instead of "**LOCKED**". That's the tell if the ever look for it.
I didn't say anything in case they would make a big deal of it. It's a hardware issue anyway, but if they were willing to pawn off a failing Doubleshot, then it wouldn't be much of a stretch to claim modding caused the failure.
Ah well, it is en route back to them now. And I had another eBay special months ago that I noticed failing after unlocking (couldn't hear the caller) - and they gave me a fuller refund (covered the cost of the return shipping) than these guys - so I'm fretting over nothing.
UPDATE: The phone has been returned, and I got the refund for the phone. What irks me though is although their policy says full refund, I didn't get the cost of shipping (to me) returned as well. I complained about this, and so far no response as to the reason why. Considering almost half the cost went toward shipping the thing forth and back, I may have been better off keeping the broken thing (not using the physical or trying to fix it myself) than have nothing to show for it.
As much as I want to leave their eBay username here as a warning, I think to myself (through this experience) ah well, such is life (although nothing would prevent me from answering if I got a PM).
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
Hello everyone, I've enjoyed my sgs3 for several years now a few months after its release. It's been through hell and back but has worked never skipping a beat until about a week ago.
The screen suddenly became non-responsive. I'm thinking the digitizer is probably bad or something. Someone recommended restoring the factory rom via odin as a last resort. Although I doubt this will work, because not only was I unable to unlock the phone in the rom, I also was unable to unlock twrp. This leads me to believe digitizer issues. Now I could buy the digitizer with a screen for about 65 dollars or just buy a used sgs3 for a few more bucks from swappa. The problem is I don't have those few bucks to spend. Hell I'm on selectel's cheapest non-data plan for goodness sake.
I have successfully put MB1 back on the phone via odin. However this replaces the stock recovery, and I am unable to wipe data in the stock recovery because you must use the power button to select the options. I ripped that out over a year ago when it was causing me problems with random rebooting. I did all I could to keep the power button going using several methods, which worked for a while but eventually I pulled the damn thing out. I realize I could take apart the phone solder two wires to the board and use that for a makeshift switch but I don't want to go through that in all honesty.
What do you experts here think? Is it now junk ready to be sold for scrap or given away, or does anyone know of a way to wipe data so I can at least get it to boot and maybe just maybe salvage this thing? I just bought a nice new hybrid case about 2 days before this occurred for about 4 bucks because my case was falling apart..
I'd like to be able to wipe data/cache from odin, or somehow use adb from the odin screen. Stock recovery isn't an option and I can't for the life of me get TWRP or CWM touch to flash. I don't know why but it fails every time. I've read and read until I'm blue in the face, and there's a sticky here in this section about using the sdcard to unbrick phones, but my pc doesn't have a card reader so that's a no go too.
Thanks in advance
griz.droidx said:
Hello everyone, I've enjoyed my sgs3 for several years now a few months after its release. It's been through hell and back but has worked never skipping a beat until about a week ago.
The screen suddenly became non-responsive. I'm thinking the digitizer is probably bad or something. Someone recommended restoring the factory rom via odin as a last resort. Although I doubt this will work, because not only was I unable to unlock the phone in the rom, I also was unable to unlock twrp. This leads me to believe digitizer issues. Now I could buy the digitizer with a screen for about 65 dollars or just buy a used sgs3 for a few more bucks from swappa. The problem is I don't have those few bucks to spend. Hell I'm on selectel's cheapest non-data plan for goodness sake.
I have successfully put MB1 back on the phone via odin. However this replaces the stock recovery, and I am unable to wipe data in the stock recovery because you must use the power button to select the options. I ripped that out over a year ago when it was causing me problems with random rebooting. I did all I could to keep the power button going using several methods, which worked for a while but eventually I pulled the damn thing out. I realize I could take apart the phone solder two wires to the board and use that for a makeshift switch but I don't want to go through that in all honesty.
What do you experts here think? Is it now junk ready to be sold for scrap or given away, or does anyone know of a way to wipe data so I can at least get it to boot and maybe just maybe salvage this thing? I just bought a nice new hybrid case about 2 days before this occurred for about 4 bucks because my case was falling apart..
I'd like to be able to wipe data/cache from odin, or somehow use adb from the odin screen. Stock recovery isn't an option and I can't for the life of me get TWRP or CWM touch to flash. I don't know why but it fails every time. I've read and read until I'm blue in the face, and there's a sticky here in this section about using the sdcard to unbrick phones, but my pc doesn't have a card reader so that's a no go too.
Thanks in advance
Click to expand...
Click to collapse
Hmm, not sure, can you get the phone to boot? You have touch access still?
You could simply reroot the thing without touching the phone at all, then use Odin to flash twrp to your phone once it's rooted. Before you can use adb you have to activate debugging, which is impossible without being able to use the touch screen.
There is no adb command for what you're asking for. However, it's possible through fastboot. But I don't think we ever got fastboot to work for the S3. It's a specific bootloader menu similar to download mode.
If you cant do it in an easy way, I'd suggest getting another phone.
Thanks, yeah, I'm not going to repair it when I can buy one for 69-70 or get a better one for a little more. I'm not crazy about some of the newer devices being locked down so hard or not having removable batteries or sd card slots. I know they exist. Guess I'll have to do some homework if it comes to that. The touch access is the issue along with not having the power button, and no it won't boot. It goes past two boot images, static images, then loops during the boot ani. I've let it sit for about 10 minutes. This should be plenty of time.
Thanks for the reply
griz.droidx said:
Thanks, yeah, I'm not going to repair it when I can buy one for 69-70 or get a better one for a little more. I'm not crazy about some of the newer devices being locked down so hard or not having removable batteries or sd card slots. I know they exist. Guess I'll have to do some homework if it comes to that. The touch access is the issue along with not having the power button, and no it won't boot. It goes past two boot images, static images, then loops during the boot ani. I've let it sit for about 10 minutes. This should be plenty of time.
Thanks for the reply
Click to expand...
Click to collapse
sounds like you're doing everything you can.
As a last ditch effort to give your phone a bit of life, you could just load the newest version. Sure it'll lock your phone and you won't be able to unlock it anymore, but if you load all the latest software it'll be completely stock. I'm sure it'll boot up then, then you can see exactly what you have to work with.
Thanks for the reply again, I think I'm going to stick with MB1 for now. I don't want to lock it up at the moment. Although I doubt the experience could be that much different, better in some ways and worse in others by doing that, I prefer freedom if I can keep it. ha ha. Master Cylinder has mentioned a few more things to try and should they work, I'll post the results here.
I did use a paper clip to activate a data cache wipe in stock recovery since I don't have a power button. This was the first time I needed the button in over a year, I was going to solder two pieces of wire to use as a power button but my soldering iron is shot.
thanks again