Database Users

Problems with the s3

So 6 months down the line I have reached a time where something has gone wrong with the phone.
Unfortunately I am not into rooting and In general happy with the phones capabilities.
However after the 4.1.1update its been sticking and acting weird. The keyboard can never remember the default setting I put it in, lockscreen shortcuts cannot be deleted after a while, and screen types or number cannot be deleted either. Touchwiz crashes and sometimes it fixes itself by hard resetting, sometimes it doesn't. The gmail wasn't updating yesterday either nor I was given the option to re-enable sync. The email client kept counting the emails after deletion of the read ones as -1....
God knows how many times I had to redo my contacts- calendar, settings etc... because of course no backup program is actually that good.
I have contacted samsung and they want to see the phone and decide if it can be repaired. I'm going to be left without a phone which is a tool for my work. Do you think I ought to get a loan phone or replacement?
Is there anything I can try before I send it that might work?
sent with nokia 5110

Gmail had some problems over the past couple of days.
If your deem it necessary, send it in for diagnostics, by all means. They will reflash your phone with new software and see what's what.

Thanks for that
sent with nokia 5110

after sending the phone to samsung, i am told that they updated the firmware, so the problems were eliminated.
I am waiting to pick up the phone tomorrow, so hopefully it will be back in business.
in the meantime i have also bought the front panel and back cover along with some assorted parts to make my white phone into pebble blue. Cool stuff! Dont know how to root the phone,but im good with changing the appearance of it!:laugh:

just an update on this.
i got the phone back with all they have done is upgraded to 4.1.2
the phone once i start to put my info back on gets stuck on the following areas:
1) deleting screens on touchwiz, the screen taken to the dust bin, crashes touchwiz and are not able to delete it.
2) Default keyboard turns back to samsung on every restart, even though you set a different default. This was also found to be true from samsung technical team!!!
3) Lockscreen options delete, also crushes touchwiz.
What i usually do after each hard reset is to eliminate the animations(all off) as i want the phone to go faster, i there is speculation that this may be the cause. I have now used up to .5 animation and so far its ok.
However the default keyboard is the only annoying thing now, and i cannot get rid of the samsung keyboard as i dont know how, and im reluctant to root just for that at risk of warranty!
All this has started after the 4.1.1 upgrade by the way,
and as i went and bought a second S3 today, brown one which looks fab, it did EXACTLY the same thing! so i returned it of course.
If others test it similarly and the same things happen, maybe samsung may need to log this as a bug and issue an update in the future.

1. My S3 did not crash when I deleted 5 pages of screens.
2. I love the default keyboard.
3. Never test that.

not had any of those issues, just tested them once more to see and all works fine
Ive swapped and changed keyboards many many times and never once had an issue with the default one being changed.
Can only suggest you send it back to them making sure they know they didnt fix it last time

Clearing data for Touchwiz launcher can fix the launcher crashes.

Would that also clear my settings?
Also how can it be that 2 completely different phones in manufacturing times had the exact same problem?
Those who tried the above, did you take the animations to off?

skimminstones said:
not had any of those issues, just tested them once more to see and all works fine
Ive swapped and changed keyboards many many times and never once had an issue with the default one being changed.
Can only suggest you send it back to them making sure they know they didnt fix it last time
Click to expand...
Click to collapse
Unfortunately the samsung technicians are at a loss themselves. My s3 on 4.0.4 had no such issues

vasp3690 said:
Unfortunately the samsung technicians are at a loss themselves. My s3 on 4.0.4 had no such issues
Click to expand...
Click to collapse
so get them to swap the phone under warranty. They cant find/fix the problem, the problems you have arent generic to the phone so they should give you a working model

skimminstones said:
so get them to swap the phone under warranty. They cant find/fix the problem, the problems you have arent generic to the phone so they should give you a working model
Click to expand...
Click to collapse
What good will it make if they change the phone? Since a completely new phone does exactly the same. Should I be changing every phone until I get one that works? How long will that take?
I was betting that a new phone would work and hence I bought the new one which I returned immediately of course as id had the same issues. This is why it makes me think it may be a firmware bug

vasp3690 said:
What good will it make if they change the phone? Since a completely new phone does exactly the same. Should I be changing every phone until I get one that works? How long will that take?
I was betting that a new phone would work and hence I bought the new one which I returned immediately of course as id had the same issues. This is why it makes me think it may be a firmware bug
Click to expand...
Click to collapse
well as not every phone is doing the same it would probably do some good but its upto you.
as i said earlier, not every phone has this faults, yours is the only one ive ever heard of with those faults. Its certainly not a firmware bug as its never happened on mine

Have you done exactly what I have above?
Jelly bean 4.1.2 or 4.1.1, animations to off, and also use a different keyboard and after setting the default see if samsung keyboard comes back as default?
I find it very hard to believe that I went and bought a random phone that once I did the above it immediately reacted as my previous one.And at the same time a technician from samsung also verifying that the samsung keyboard always flips back to default as well!!! The default only changes if you restart the phone, not on the fly
I cannot play a game with samsung to have the phone back and forth as its a daily tool for me. Unless I get a second handset as a replacement I cannot see any point me sending phones back and forth.

vasp3690 said:
Have you done exactly what I have above?
.
Click to expand...
Click to collapse
yes...as posted above
skimminstones said:
not had any of those issues, just tested them once more to see and all works fine
Ive swapped and changed keyboards many many times and never once had an issue with the default one being changed.
Can only suggest you send it back to them making sure they know they didnt fix it last time
Click to expand...
Click to collapse
still, if you dont want to believe me and think that every single gs3 out there is faulty its upto you i guess. Personally id be getting the phone swapped but thats just me

Thanks for verifying that at least your phone works fine. I will have to see what I have to do. So far I bet samsung wont do anything and according to them they have to try and fix it 3 times before they offer a replacement for it. What a shame

SGS III no usb connection only charges
Guys,
I bought my SIII on Monday(17th)....plugged it in my laptop and it worked fine.....But for the last couple of days whenever i plug it using the usb cable it only charges and the pc doesn't even recognize it. I tried checking this through the device manager but still it does not show any device connected to the computer.
I've done a factory reset and still no hope.
Can anyone help me out here ????? this is really frustrating....

mohsinmasoom said:
Guys,
I bought my SIII on Monday(17th)....plugged it in my laptop and it worked fine.....But for the last couple of days whenever i plug it using the usb cable it only charges and the pc doesn't even recognize it. I tried checking this through the device manager but still it does not show any device connected to the computer.
I've done a factory reset and still no hope.
Can anyone help me out here ????? this is really frustrating....
Click to expand...
Click to collapse
Why do want to connect it ? If you to transfer some data you can use airdroid https://play.google.com/store/apps/details?id=com.sand.airdroid
We only have what we give

A small update on this.
Samsung has received my phone and I hope they replace the motherboard for this issue. I'm on i9305 now and I will be selling the s3 once its back from the repair.
I also bought a secondhand s3 and it didn't have any issues with these glitches. For all I know these could be issues of a dying motherboard of this sudden death issue.

[Q] URGENT HELP with a fully bricked defy

Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve

To get into the bootloader , keep the volume up button pressed and then press the power button. Is this what you tried to do?
And I didn't get the part where you wiped through the bootloader. As far as I know there is no option there. Do you mean the stock recovery?( The yellow dots are there in the stock recovery)
Sent from my MB526 using xda app-developers app

wahat3 said:
Hi Everybody,
I believe that I am now in serious trouble with my Motorola Defy. I have tried to look everywhere today to find a similar problem to what I am experiencing, and although I can find all the problems, I can't find anyone which has happened like this. It would be so great if someone could help me. I am so so desperate and in total panic right now. I need this phone to work which I had bought in Germany (where my home base is set up) but I am currently working in Estonia where salary really does not allow me to just go out and buy a new one - not even a cheap 20€ phone.
I originally bought the phone about 1 1/2 years ago with Android 2.1. After about 6 months I did the official update to Android 2.2. This is where a few things started to go wrong. Google maps would crash the phone so that I would have to take the battery out to restart it. The camera didn't work properly, and not at all with the flash, and the phone would quite often restart itself. I could however live with all this and just accepted it as I didn't want to do anything to make it worse - I trust myself 100% with computers and there isn't much that I can't do with them. But with phones, that's where I have to put my hands up as I really don't trust myself to do anything because of the fear of bricking one.
Anyway, today as I was using the phone after taking a few pictures the phone had frozen, so as always I took the battery out and turned it on again, when it loaded up and as soon after I put my pin and unlock number in, it restart itself, So I again I put my pin and unlock number in, and it restarted itself. After this I couldn't even put my pin number in.
I then did went into Bootloader to do a wipe and restore, This however, after taking two hours and just watching the yellow dots move along, was clear to me that this also wasn't working. After coming home from work I then copied the instructions found I think in the Beginners Defy Guide on this site for using RSD Lite and an SBF File. This then failed and in Bootloader it also then said Corrupt.
So I then started to watch a video on youtube for a complete guide from unbricking to installing CM10 (something I wanted to do the whole time and never trusted myself). Meanwhile, whilst everything was downloading, although the phone still had about 60% battery, I thought I would plug it in just to charge it for a bit, this however also did not work but I left it in just in case it was working.
After everything was finished downloading, I unplugged the phone from the wall and now it won't even turn on,, neither in Bootloader, or the screen. It does NOTHING! :crying::crying:
When I plug it into the computer the little white led light comes on (top left of the phone) and the computer makes the sound that something is plugged in. This is also recognised my RSD Lite, however once a file has been created it cannot be flashed. It's like the phone is there, but it isn't.
I am really desperate to get this working as I really need this phone for work, and like I said just cannot afford to run and buy anything.
I'm very sorry if I have posted this in a wrong area, but I honestly did try to find something. I just don't understand how plugging it in to charge can stop it from not even opening bootloader, It's like it's got a mind of it's own.
Thank you very very much for reading, and I apologise that it's so long,
Best Wishes,
Steve
Click to expand...
Click to collapse
Check out this link all the best :good:

LG G2 Display Issue

Hello everybody i have been using this phone for months (i bought in july 2014) and sometimes an issue comes up.
As you can see by the photo there is a vertical white line on the right of the display. I noticed that is more visible on a gray scale and if i use a program like BURN FIX for 10 minutes or so, the line tend to vanish.
Does anybody know what is this? Thank you.

I haven't had any white line issues with my g2, but you could try the JDI kernel. If that doesn't help then it is a hardware issue and you have to get it to warranty service, just flash stock rom AND check that under download mode you have unrooted.

1ackass said:
I haven't had any white line issues with my g2, but you could try the JDI kernel. If that doesn't help then it is a hardware issue and you have to get it to warranty service, just flash stock rom AND check that under download mode you have unrooted.
Click to expand...
Click to collapse
JDI kernel? Is compatible with cloudyG3 2.1?

DavideFV said:
JDI kernel? Is compatible with cloudyG3 2.1?
Click to expand...
Click to collapse
I thought CloudyG2 switched automatically? o_o

i also am having this issue.
this is with a brand new screen.
guess what?
about a few months ago i had another vs980 black that i also ordered the lcd assy.
guess what
it had same problem but i was also having a knock issue but that turns out i just needed to add a piece of tape to make it contact better.
anyhow the screen was like this one and like the guys above after i flashed the cloudy or xdabbeb
cant rem exactly but anyhow i had been trying and trying to get the knock fixed but in process fixed the white screen somehow on that phone.
i was flashing different bootloaders and all kinds of custom roms but in the end it was an official stock 26a vzw rom but the problem i had alredy fixed somehow so i flashed that hoping it would stick and it did.
i do not know or remember exactly how i fixed it but it did.
well onto this white vs980 that i had also flashed custom stuff too also
this phone had a cracked digitizer so i used a usb otg cable and my mouse to get around
the lcd worked fine.
well today i got my new screen and swapped it out
guess what
those same white lines and white screen
guess what?
the phone was on xdabbed and twrp 2.8.2.0 (i think) but anyhow i think something not right is happening when we have custom rom on.
this is my 2nd screen (new) that it has done this on.
there is a way to fix out by flashing stuff but i have no idea how i did it.
i was trying to fix the knock on so i tried the touch firmware update a few times.
anyhow i dont think this is hardware related so is there a way to tell if i have a jdi or jdl screen?
right now im on stock official vzw 26a and am thinking about flashing the stock 27a
any info would be great

DavideFV said:
Hello everybody i have been using this phone for months (i bought in july 2014) and sometimes an issue comes up.
As you can see by the photo there is a vertical white line on the right of the display. I noticed that is more visible on a gray scale and if i use a program like BURN FIX for 10 minutes or so, the line tend to vanish.
Does anybody know what is this? Thank you.
Click to expand...
Click to collapse
Hello,I have the same problem on my lg g2,at the end of this story I dont know if the problem is in hardver or softver,and if I insert a cloudy g3 rom will I fix the white line problem,tnx in regrete.

LG G6 Bootloop -- Don't Know What Else to Do! -- Please Help!

I have an LG G6, international version (H870DS) that has been having bootloop issues for a while now. For the first few months it would come and go -- sometimes it would be a week between issues, sometimes just a few minutes. I tried many things, multiple factory resets, removed the SD card, deleted possible troubles apps, basically anything I could find online to try. But, for a while the phone would work pretty much normally until it decided to restart and loop.
But... about two weeks ago the phone got into its bootloop and never came out -- I can't get past the LG logo screen anymore. If I let the phone go for a while eventually it gets to a green screen talking about a RAM dump. One time I managed to get it to a screen talking about unlocking the bootloader but that part got a bit over my head. Basically, I can let the batter die but as soon as I plug it in, the phone starts lopping again for 15 minutes or so, eventually ending at that green screen.
Over the last few days I have tried downloading a stock KDZ file to try to flash stock ROM back onto the phone. The problem is, I can't get the phone to communicate with my computer no matter what I do. I've downloaded LGUP, installed all the drivers, tried the LG Flash Tool and pretty much anything else I could find -- but I just can't get anything to recognize the phone, even when I get it into download mode. I know the problem isn't with drivers because when I try my wife's identical G6 on my computer it gets recognized right away.
I should mention that I never tried to tweak anything with the phone -- the issue has been occurring since it was basically brand new. I am by no means an idiot when it comes to tech but also far from an expert, but I have done my research and tried everything I could.
So -- basically I am out of options and appealing to anyone who can help. I currently live in Africa and have no access to LG service centers. I have spent upwards of 10 hours trying to figure this out now and I just don't know what else to try. Any tips or advice would be incredibly appreciated. Thank you!

This looks like a hardware failure. if you have warranty, you should send it back to them. The seller can't take care of the warranty ?

Screen dead + Front camera keeps trying to open

Hey!
While I was calibrating my fingerprint, phone suddenly turned off and went to recovery with screen off.
I managed to reflash stock rom through fastboot and it boots to system fine, but the screen stays off and the front camera keeps trying to open while playing the MIUI camera sound (sometimes, while booting, the camera does manage to open once, kinda like it's calibrating). Some playing around with ADB and it seems that the SIM isn't recognized either.. antenna maybe?
I opened the phone up and checked everything, there's no visible issues with the electronics, however it could just be the inside of a cable that died?
Does anyone know what this could be? I noticed the screen, fingerprint reader and antenna are all connected to the same removable PCB, but the camera isn't so that's odd.

Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.

XDHx86 said:
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
Click to expand...
Click to collapse
It's a bit of a long one, so I didn't want to bother too much with the details if anyone knew what those specific issues could be caused by, here goes though:
I am on a Mi 9T bought on Amazon Italy in July 2019. I cannot comfortably send it to a repair center due to every authorized shop around here is just a drop-off point for Xiaomi RMA. I talked to them and, due to (>6 months old) glass damage to the screen and back of the phone, they intended to charge me way more than I can afford, as "solving issues covered by the warranty would require us to replace the accidentally damaged components"
As for what happened:
I was running LOS 17.1 with no issues for a few months. I went to unlock the phone and I heard the reboot vibration, which sent me to recovery (softbricked) but with no screen signal. I assumed it was just a software problem, so I flashed MIUI 12 (global, V12.0.7.0.QFJMIXM) to see what would happen.
As it completed, the phone rebooted itself, the MIUI logo popped up and it went to system (seemingly) without any issues.
I went through the initial wizard and played around with it. everything seemed fine and I even made sure the screen did work in recovery and fastboot. Later, when I went to setup the fingerprint reader, the screen went blank for half a second when I first touched it, and then the same screen death -> reboot to recovery.
The phone was softbricked again, though, this time, reinstalling MIUI didn't yield the same success. Now:
MIUI boots "normally" again
The screen isn't working at all
The front camera opens, as if it's calibrating, when system boots up
The front camera randomly tries to open again every now and then, failing to do so as if the motor is stuck, while MIUI plays the camera closing sound.
Meddling through ADB, the antenna doesn't seem to be working, but I can't be 100% sure due to the methods used
The power and volume buttons, speakers, and the charging light all work.
I have opened the phone up myself, thoroughly checked every cable, connection and PCB, but there is no sign of damage. I put it back together and the same issue continued.
My best guess is that something inside the fingerprint reader went bad and shorted something else.
What that something else is, I couldn't find out. Given the antenna, screen and FOD are all connected to the same little PCB which then runs a couple cables to the motherboard, I am now in the process of finding a couple replacement cables to see if that fixes anything.
As I mentioned before, repair centers are not an option due to the lack of anyone who's willing to help me for less than a good chunk of the price of the phone.

Interesting. So basically what happened is due to the initial soft brick and accordingly you flashed a global MIUI 12 ROM, which in return brought you to the second soft brick which caused some issues within the hardware of the device.
Now you're stuck with a faulty screen, a faulty camera and a faulty antenna.
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
I can't help you if you messed up your phone circuit since I have no knowledge about android hardware, however I can safely assume that what caused your issue isn't related to hardware.
I think the issue is caused by an incomplete flashing of a ROM (In this case MIUI 12 global) OR flashing a different variation from your device.
e.g. you flashed only the ROM, but didn't flash the other components of the ROM.
Needless to say, flashing a variation of the ROM that isn't meant for you device can be a disaster recipe.
I recommend flashing LOS again, since you can't go back on Xiaomi devices due to rollback protection.

XDHx86 said:
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
Click to expand...
Click to collapse
I understand why you'd think that and have seen people do similar stupid things, however I didn't watch any youtube video and know what I'm doing quite well.
I made sure I flashed the correct rom through fastboot to restore everything to stock. I did try to reflash LOS and whatever else (though it's kind of a pain with adb shell), but it doesn't fix the problem, sadly.
That's why I'm betting on a HW issue.
The fingerprint reader and everything else worked flawlessly in LOS for months, but it made the screen go blank and bricked the device in both LOS and fully functional, stock MIUI.
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?

angometry said:
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
Click to expand...
Click to collapse
If the touch screen is dead then you can use mouse and OTG cable.
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one). Or you can use playstore on pc to download and install apps like (Screen stream over HTTP) on your device, just make sure your device is connected to the internet and you're signed in on your phone as well, you might have to type in the screen password if you have one.
angometry said:
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
Click to expand...
Click to collapse
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
All I can think of is:
Wiping dalvik cache, though you might have already done that.
Trying other custom ROMs from here.
You may try to get your device rollback index and installing a MIUI ROM that has index higher than it, and see if that works.
That is as far as I can help, unfortunately.
I have zero knowledge when it comes to hardware, so I can only help with software issues. If none of my solutions worked then sorry for wasting your time :/

XDHx86 said:
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one).
Click to expand...
Click to collapse
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
XDHx86 said:
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
Click to expand...
Click to collapse
Sorry, I didn't explain myself, I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
If I can get it on, I can then use things like scrcpy to get screen signal through USB.
Main problem with everything else is that the screen is 100% dead. Even with usb otg I don't know how I could possibly get through the setup wizard haha

angometry said:
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
Click to expand...
Click to collapse
I haven't tried it myself, however it should detect it as a second monitor. Give it a try the cable isn't costly at all anyway.
angometry said:
I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
Click to expand...
Click to collapse
TWRP has debugging mode on by default, however that strictly applies to recovery and fastboot modes only as debugging mode is pretty powerful and can cause security issues. So you better forget about it.
I saw one of my friends who owns an authorized service center use some cable connections to get the screen to display on another touch screen. If you have the capabilities and resources I recommed trying it, though don't mess too much with the motherboard.
Just a question though, can you confirm if the touch is working? If not then there's a chance - Although slight - that this is just a UI problem (Which is pretty common in MIUI ROMs for some reason). In that case deleting dalvik cache or completely reflashing the ROM might solve the issue.
I may not do much help but certainly someone there can help so it's better if you include "usb debugging" in the title and/or the tags. Like changing the title to "Enabling usb debugging without screen" or "Screen is dead, need help to flash ROM"
Using proper title and proper tags can get the right person to help.