Database Develop

my screen are not functioning!!!

i am not able to use my screen anymore and then i continue to ;
1) clear storage with keyboard support of 1,2,3,4
2) succeeded to restore
3) the problem now is stuck at the beginning of setup, but i cannot do anything becoz the screen not able to use anymore!!
plz help, what i'm goin to do now is download 1 of the rom and try to reflash see how.
any other method someone plz advise
million thank
joei

cant even install the HARDSPL http://forum.xda-developers.com/showthread.php?t=334679
sob sob....someone plz help

Touch screen not functioning or no picture due to screen itself not functioning? Anything specific happen that might have caused this? Still under warranty?

the touch screen not functioning at all. i didnt do anything thing before that.it just happen all i did to clear the storage and try to flash with some other roms but not successful.
no more warranty.
thanks for ur reply Guilf. or any other method that i can flash the roms? since i not even able to do anything. but i still can able to go into the bootloader. anything roms that works on the bootloader ?
i still not able to install the HARDSPL and SUPERCID

I've never heard of a ROM negatively impacting the touchscreen - so I'd be somewhat surprised if it fixed it. However, anything is worth the effort.
FYI - you don't need to SuperCID. Just HardSPL. Or try to JumpSPL it. Check for the thread on White Screen Issue during HardSPL in Upgrading section.
If it's still not under warranty and needs to be fixed - PPCTechs replaces the LCD and touchscreen in one unit. $160, I believe. Good luck.

thanks for ur reply, i even try to open up everything and ensure all the cabling is attached propoerly. still not work!
i cant even go into the windows screen i cant do the jumpspl either.
and the PPCTechs is broken link.
sigh...................

found out some scratches on the cable, could it be the reason that my screen not functioning anymore? pplllzzzzzzzz someone advise thanks
{
"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"
}

I think I bricked my Tab?

It is showing a small round mobile phone, 2 dots, a ! inside an orange triangle, 2 more dots, and a computer.
This is the first time I'm seeing this screen.
Edit: Just to give some insight as to what I was doing...
I was using a SGT7 build of CM9, and I noticed USB Tethering wasn't working (native nor Wired Tether 1.4 worked). I had to run to a friends house for the night real fast, so I figured I'd just go back to Stock firmware and use that for a few hours just so my desktop could get Internet.
I am also using Windows 8 Release Preview. Odin could see my device fine, but upon pressing Start to start the flashing process, it did nothing (I'm guessing Odin or Samsung's drivers don't work well on W8RP). No progress was made on either Odin or my tab for about 5 minutes. Since nothing was done, I figured I could close Odin, and restart my Tab. Now I only get this screen:
{
"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"
}
I immediately went to the "How To Unbrick Your Galaxy Tab!" thread, but didn't find mention of the screen I described in this post, and then I made this post in panic.
When I went back to Windows 7, Odin was able to reflash my tab successfully, and USB Tethering was working fine. So perhaps Windows 8 has some weird incompatibility with Samsung Drivers? In any case, this might serve as a warning to anyone trying to use Odin in Windows 8.

I think it was mentioned in a few threads.
Many confirmed that it is another download mode.
You just have to make sure it is fully charged, and keep trying Odin restocking. It will go through.
(I never experienced it myself)
Edit: many reference, just search in here fore "phone exclamation pc"

Yea it would seem it's another download mode. I was able to flash with Odin just fine in Windows 7, so all is well again

i have said this in many threads. this is the result of faulty flashing. just use the latest version of odin
please thank me if you found this helpful

Wrong Colors

Hello there!
i'm observing a irritating display/color problem on my Xperia Z1(Screenshot, yes these pink things aren't supposed to be there and they don't change their position in the picture(!) if i flip the device. According to the background they also appear in green, blue and red; they change only positions if i change the overall portion of green color in the settings).
How the problem occured: A few days ago my girlfirend droped my phone and the glas broke. (touchscreen was also defect nothing more; still controlable via mouse) Instead of repairing it myself i gave it to an repairer (insured event). I got it back with a working touch but i noticed this colorproblem very soon. The repairer said it could possibly be the mod. So i flashed back to a 5.1 stock rom and the color problem was gone. But when i flashed the phone back to Cyanogenmod i've got the same problem again. Is this because of the "nightly" status or did something go wrong in the garage? The Problem is only visible on the screen. If i broadcast the screen to a pc or send a picture with "broken" colors e.g. via whatsapp it is free from these scratches.
I would have no Problem with flashing back to c11 but is it save? (stagefright) And is there meanwhile a fix for the slowly/sometimes not starting camera?
Any help would be appreciated!
best regards
Tilas
PS: Sorry I can't find the "manage attachments"-button and it seems like resizing in bbcode is not supported..
{
"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"
}

yep,thats a busted screen alright and not a software problem.I guess you need to get it replaced...again.

If it is a broken screen then why is it working fine with a stock rom? The repairer already replaced it. But it didn't help. Maybe low quality screens? I already tried some changes in dpi with no luck. The original worked fine even with cm12.1 until i gave it away.

Your replacement screen may be a cheap knock off from china or somewhere .so it might work fine with the stock firmware but have problems with CM's screen drivers! .
PS: Did you do a full wipe and flash with a new rom or did you restore one of your old backups? Try to do a full wipe and flash the latest CM nightly.

From cm12.1 i used flashtool and xperifirm to find the newest stock rom for my device and flashed it. I made use of the wipe-options in flashtool. After that, with a working stock rom, i downloaded the newest cyanogenmod rom for my device to my pc and flashed the boot.img via cmd and fastboot and installed the new cm12.1 in the recovery (after wiping data and cache) via adb sideload. That broad up the colorproblem again.
Today i did the same but flashed the last cm11 snapshot. -> works fine.
Maybe i should try a cm12.1 nightly from a date before i took it to the repairer. I'm pretty sure that it worked until i gave it away and he had no option to apply a update himself due to the active lock. But i remember that some settings were changed the day i got it back e.g. the root-access was deactivated wich caused problems for some apps.

nexus 6 marshmallow root using mac osX - error message! - device is currupt -

nexus 6 marshmallow root using mac osX - error message! - device is currupt -
wanting better optimization for my Nexus 6 with marshmallow build MRA58R, i started the process of unlocking BL and going for root access following this guide:
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
right in the beginning already im stuck. i unlocked bootloader fine, had toggled on in the device, checked through terminal. everything fine. started root process and as soon as i ran CF-Auto-Root it started its thing and rather pretty quickly a new screen came up reading in red letters "Device is corrupt. It can't be trusted and may not work properly." for maybe one second before shutting off. i can briefly get it to power up, only to get that same screen. a couple times i did have it back in bootloader mode through ADB from the terminal. but nothing since. the few times i did get bootloader up i tried a recovery process from the site referred by the error screen itself here: https://support.google.com/nexus/answer/6185381?p=verified_boot&rd=1
but when i ran fastboot oem unlock it now says it cannot find device and tells me to go into device and change OEM setting in developer tools. kind of tough when it wont boot up. i sure would love a solution to this one, id appreciate any help..
added: on the device in bootloader mode it reads USB connected but on the laptop will not recognize any connected devices?
{
"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"
}

I am no expert, but it seems like you are having the exact same problem that this person had. It seems that the guide will not work on 6.0, but luckily, he seems to have found a solution.

ICStevenC. said:
I am no expert, but it seems like you are having the exact same problem that this person had. It seems that the guide will not work on 6.0, but luckily, he seems to have found a solution.
Click to expand...
Click to collapse
dear Lord baby Jesus, thank you. only on step 2 and its further then ive been in hours. :good:

[RESOLVED] Redmi Note 9 Hard Hard Hard Bricked Help?

Okkaayy guys, so, i'll take you to the end of the whole thing which is, I installed and downgraded 2 versions in stock rom, which was V12.5.1.0 worked like a charm, then I updated the version with Xiaomi's original it's own system updater to newer version and it was still fine then I updated it to Android 12, MIUI 13 and it bootlooped.
So, I wasn't able to get into recovery, trieedd soo many times and neither I was able to get in to fastboot mode. What did I do? Flashed it again with Format All + Download option. I got the bar and everything but I waited a bit and nothing happened. I'm like, is this working? And I did the mistake. I pulled the plug. And here I am. Surely I've 60+ battery. Besides that I charged it for more than 15 minutes. No power button works, no fastboot, no recovery. Nothing "HAPPENS". Literally. No matter what I do, how long I press to any button, device won't turn on in any sort of way. Libusb still detects it as Mediatek driver but I can't use SP Flash Tool because simply device won't turn on. Bypass utility stays like this.
{
"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"
}
Held power button for 5 min (literally I did) nothing happened
No fastboot or recovery
SP Flash Tool simply can't do the trick because device doesn't turn on
I have 60+ battery %100 surely.
USBLIB still able to detect the port.
What do? Is it even possible to rescue this poor guy? It was my main phone btw...
EDIT - UPDATE: I have no idea how but I was playing around with SP Flash Tool, trying to do some things, nothing was actually happening but like after few minutes phone just gone back into bootloop, It turned on, I genuinely don't know how and just for confirmation, after I installed stock rom back my charge is %73 so surely it wasn't related to my battery. IDK this devices are weird. Sorry for the topic mods..