yashsingh1/xdaforums huggingface dataset:
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
In the case of the TyTn 2 it may be that the connector to the screen needs reset. There are far fewer reports of chip problems on the Kaiser so it may be a less problematic fault.

If you have a warranty then use it. If you have some skills in a technical direction, you could consider dismantling (voids warranty).

If you are not technically minded, then be aware that attempting this might leave you with a pile of bits in a worse mess than it is now. If you fear this then a PDA repair shop is a better idea. The site above lists a few such organisations, but you may have one local to you.

Mike
[8525, TyTN, MDA Vario II, JasJam General] GTX2009:
I got my problem solved!!

Mine was a FLEX cable problem, it wasn't needed to reset neither format the phone.

To fix mine was just simple as putting a business card between the lcd screen and the keyboard of your htc, and make it slide a bit.

This will fix the bad contact between the flex and the lcd screen.

Hope it helps, it helped me and spare me a lot of time and money.

Tought, i was desperate earlier and hard reset'd my phone.

Thanks god i made a backup last week and could get back my +5.000 contacts and my entire year calendar!

;)
[8525, TyTN, MDA Vario II, JasJam General] ariyano:
Thank u guyz, thd dpad trick got my months old dead hermes back 2 life, i had the white screen and i jus bought a new one and the old 1 was biting the dust, but i got it up n running now.

Thanks again.

Aj.
[8525, TyTN, MDA Vario II, JasJam General] Disillusioned:
My iMate JASJAM has somewhat the same issue.

When I switch on the phone, everything looks normal, then after 1-2mins, the display becomes white, I can see everything on the display at an angle but its very difficult to figure out whats written.

Next, I put the phone on standby by pressing the power button, and again I press it back to get the phone back on. Now the display is normal again but only for 5seconds. It again goes white.

I kept the phone in freezer for 10mins, and I saw the time for the phone to get to white screen increased. Instead of 5seconds, it was 40 seconds.

I changed the display completely but all in vain.

The other member who got their phone fixed with the card trick have had normal display then white screen or permanent white screen?

White screen is damn bugging.
[8525, TyTN, MDA Vario II, JasJam General] Disillusioned:
I just did the DPad trick but still no help. Normal display and then white screen.

I've tried various ROMs however nothing worked.

Is there any solution for my phone's problem, did anyone had the same problem?
[8525, TyTN, MDA Vario II, JasJam General] AnzeM:
Same problem, solved it by removing some software(read: games), which actually made me problems in other applications as well white screen and alignment. At least alignment and software problems are gone..., still waiting for white screen not to happen :)

p.s. tried all that stuff with cables and screws and nothing worked.
[8525, TyTN, MDA Vario II, JasJam General] jfg69:
I'm having a permanent white screen problem on my 8525, which started right after playing around with S2U2. I sort of think it was coincidence, but I have no idea. I have had the thing apart 3 times, cables all look ok, connections all clean, pressing in usual places shows no changes. How do you figure out which part is the culprit?
[8525, TyTN, MDA Vario II, JasJam General] shaggyleo:
Im going to try this in a little ill tell you if it worked
[8525, TyTN, MDA Vario II, JasJam General] shaggyleo:
thank you it worked perfect i spent hours trying the other way but this in one minute thankx again
[8525, TyTN, MDA Vario II, JasJam General] playmike:
yeah men tnx a lot everything is ok now
[8525, TyTN, MDA Vario II, JasJam General] kudtz:
Thank You! You helped me with my white screen!
[8525, TyTN, MDA Vario II, JasJam General] LightOwl:
Thanks everyone for the research and instructions. Followed the instructions above last night and within 20 mins, my hermes was back up and running good as new. No sign of white screen at all since then - fingers crossed it's gone for good.
[8525, TyTN, MDA Vario II, JasJam General] KingRichard1st:
Fabulous.. this solved my white screen WITH a new Win6.1 ROM!!

To All of you who helped with instructions on how to disassemble my Hermes.. I thank you for saving my phone!

I use CrC's ROM which I must recommend! After updating to a recent stable version with Win Mobile 6.1, every now and again, I would suffer the WSOD which became more frequent over time (to the point of every 3 times i activated the phone).

BUT, since taking my Hermes apart, reseating all the connectors AND discovering that the chip by the 'end call key' in fact didn't even have the rubber pad in in the first place so it wasn't pressed in place (from the factory!!!??), I now have a much faster phone (over Win Mob 5 by T-Mobile which was terribly sluggish) and no worries about the WSOD!!!

My Hermes is now fabulous to use and VERY reliable thanks to all of you who provided such valuable info but let's not forget CrC for his great work too!! :-P

T H A N K Y O U..
[8525, TyTN, MDA Vario II, JasJam General] Dubhaltach:
Like Me: 1st of all the buttons stopped working. Then the screen would start to fade white ( a few days after ) If i tapped the screen a lot, or, incidentally dropped it, it would work. Now, It only white screens. Hardware I'm guessing? It's out of warranty anyway and it isn't very important to me, I'm just intrested.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
It is now generally accepted that the white screen problem is caused by cracked solder joints on the d-Pad daughter board.

The standard method to check is to re-seat the screen connectors and if the white screen remains, then the best chance of success is to do one of the following:

1

Replace the d-pad daughter board OR

2

Have the solder re-flowed on the daughter board OR

3

as a DIY job, place a bit of padding on the d-pad chip to press it firmly against the board when you re-assemble. (some have reported good results doing this, but it can be hit or miss and may not be a very permanent solution)

It is generally thought that the chip solder joints get cracked through the pressure put on them when you press the d-pad buttons.

Mike
[One (M7) General] xiaohan:
Software update: 7.18.708.2

Size: 836.9MB

International unlock version HTC One M7, bought in Hong Kong.
[One (M7) General] troly:
Expect .707 :D
[One (M7) General] LenAsh:
Thread closed

This subject (updates) is already covered adequately HERE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
Hey everyone so I took my phone out of my pocket and it was stuck in a boot loop. I tried taking the battery out, volume up + power + home, volume down + power + home but nothing. I've tried booting it also without a battery.

I have Quantum running on my phone, and have never had any problems. The occasional restart but now my phone won't even get to the home screen. I get just a boot loop with normal sounds, and then my LED begins to flash. Then it just loops again ..

Don't really know what to do.

UPDATE: Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/

Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StoneyJSG:
DELETED - irrelevant information.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
Why ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Will your computer detect it if connected? (Odin, Heimdall, adb)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
Yes computer is detecting it with Odin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
What is on the phone's screen while the device is detected by Odin?

There are a couple of notn-standard images that will actually function as download mode, allowing you to reflash a custom recovery. And then, hopefully restore a nandroid of your rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
I get two options for either volume up and volume down. After pressing volume up I got the android with "Downloading Do not turn off target"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
Update: After reading some more I decided to use this tutorial to flash back to factory: http://gs3.wonderhowto.com/how-to/r...sh-stock-roms-using-odin-for-windows-0142713/

Now that I have flashed to factory, I am stuck on the glowing samsung logo.. I have to tried factory reset / wipe but still nothing. Download mode is still working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
I agree with dawgdoc. Use Odin to reflash the latest version of TWRP, or the custom recovery of your choice. Uncheck auto reboot before you flash. Upon successful flash when it says reset in the status window unplug USB then pull the battery. Replace battery and try to boot to recovery with vol up + home + power; keep holding all three for a second or two after it vibrates until you see the blue text for booting to recovery (hopefullly)...

Then restore a nandroid backup, or load CM 10 or 11 on a microsd and flash that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
Using the same battery but now I can't get into recovery at all. I get the little blue text in the top left hand corner but I can't get to recovery.

Edit: Just realized I used the wrong TWRP for my phone. I redid everything and now I can get into Recovery mode. Going to try and put a rom on my device. Will be back shortly with an update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
So I keep getting a bunch of errors with TWR. I tried installing AOKP but got stuck at a boot screen again, and after trying to wipe my phone I get an error message saying "Failed". Now I'm trying install Quantum again but get an error message saying "Zip file is corrupt". T__T

Going to try another rom..

Update: I've tried Quantum again and it finally installed but now I'm stuck in a bootloop again. This is so frustrating ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
It seems like you are on the correct track. Don't give up.

Hopefully it is not a matter of the internal sdcard going bad.

If you continue to have trouble you might consider reflashing the bootloader and modem that the phone is currently on, or a newer one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
Installed Clockworkmod to see if TWR was the issue and still I'm getting boot looped. Is there a clean start from scratch method I can do that guarantees a fix for this ?Although I didn't get any errors with Clockworkmod just getting looped again. I haven't tried anything with the bootloader and modem. Is there a updated tutorial on this? I can't find anything
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Couple of thoughts:

Is there any chance that following the tutorial in your original post you tried flashing a ROM image using Odin that had a bootloader different that what was on your phone when it was working normally? If so was it an older or newer version.? If older, then reflash the newer one that was previously on the phone, along with its matching bootloader.

It could be that a full wipe before trying again to flash the ROM would be what you need.

If the wipe doesn't work you may need to flash a stock based ROM and then go back to Quantum, or whatever you choose.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
I honestly don't remember .. Any tutorials on doing a proper full wipe for my device? I did try initially flashing a stock based rom, but I'll try it again with Clockwork.

Also, how do I know which bootloader is correct and which files to flash if I can't access the info through my phone. I swear half of these damn tutorials have broken links and only spam files. I don't know what to do since there's so many damn options... I'm ready to throw my phone against a wall.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
You still have download mode and recovery working, so there's still some things you can try. Don't smash it just yet.

I know how feel about searching for information on this phone. It's either fragmented and spread across a dozen forum posts, or you find stuff from tech websites and whatnot that is really dated. To make matters worse, some of the changes Samsung made to the more recent bootloaders made those dated articles and forum threads downright dangerous (stupid Knox and efuses:eek:). There are plenty of landmines and some bear traps out there.

Since TWRP is still functioning you can check what bootloader you're using; it's good to know if you aren't sure. I think you could do this on CWM too, but you'd have to use a computer and adb shell. Might be easier just to flash TWRP 2.8.5 back as your recovery if you don't already have adb and drivers set up on your computer. Boot into TWRP and go to Advanced -> Terminal Command -> the Select. In the command line enter:

getprop ro.bootloader

That will output your bootloader. Report that back here. It is not safe to flash any firmware updates with Odin or custom recovery without knowing your current bootloader version. Flashing wrong, downgraded, or mismatched firmware is the #1 way to brick this phone and it can be hard to recover from.

Was your storage encrypted when you were running normally?

The usual clean flash procedure for TWRP is this: Pick Wipe -> Advanced then tick dalvik cache, cache, system, and data then slide to wipe. These wipes will not touch files stored in your internal sdcard. Once those wipes are complete you're typically set to flash your new rom and Gapps, but...

If the rom zip you're going to flash is loaded on an external SD card you can also format the internal SD, also under Wipe. This will erase all your pictures, user data, etc stored on internal sdcard (you've been warned); it will also erase the rom you're going to flash if it is stored there. Do not format the internal SD if you aren't using an external SD card, or you'll have a blank phone with no rom to flash. You can recover from this with adb, but it can be tricky if you aren't familiar with it so just don't do it ;). The way your phone is behaving (spontaneously bootlooping in your pocket) I would consider formatting the internal storage, provided you have an external SD available to flash files from after formatting your phone. Any files that you must save on internal storage you could move to external SD with TWRPs file manager.

If a good clean flash and possibly fixing up your firmware doesn't cure it, I've heard TWRP and Odin just aren't as thorough as a full wipe in the stock recovery. Loading stock recovery and doing a factory reset in it might not be a bad next step, but check on the firmware and make certain you do a proper clean flash before you resort to stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
+1

also to confirm modem , type in ...

getprop | grep version.baseband

"all i can really do , is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
Thank you for the information. It's good to know that me being unable to find a solution wasn't just due to my frustration.

My bootloader is: I747UCDLK3

I did do the same type of wipe but all of my roms are on an external SD card. I was under the impression the internal storage was wiped completely. I currently have Quantum / Gapps / Kernel all stored on the external SD. At this point whatever it takes to get my phone working again will do.

Hmm .. that command didn't seem to pull anything up for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
LK3 is a pretty out of date bootloader, and in this case that might be a good thing. :D

You can go to sammobile.com and download the full firmware for your phone and flash it with Odin: http://www.sammobile.com/firmwares/database/SGH-I747/

For reference the newer firmwares (MJB, NE4, and NJ1) cannot be downgraded, any attempt will result in a brick. On LK3 you are safe. Repeat, don't try this at home unless you know what bootloader version you have.

This will Odin your phone back to pure stock Jellybean. This used to be the go to method for fixing screwed up S3's before Samsung started bricking us for downgrading the firmware at version MJB.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
Alright I'm downloading this now. Assuming this works, should I do an OTA update then root or am I safe to root the device from odin as soon as this bootloader is installed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Your modem will definitely prevent data from working on most of the custom roms newer than ~Fall 2014. I think Quantum dates to summer 2014, which is why you were fine.

Before you take any upgrades you might consider SIM unlocking your phone if you haven't already. Not at all necessary, but nice to have. You'll be on an android version where it's pretty easy: http://xdaforums.com/showthread.php?t=2529200

Taking OTAs is a nice, safe way to update your firmware. Just be aware you'll probably have to take more than one from LK3; they will be stepwise upgrades and from what I've heard they'll come about 24 hours apart. You'll need to get to at least NE1 firmware to run the newest roms. NJ1 is the most up to date AT&T firmware, you're done when you hit there.

That will take a few days. If you're not the patient type, then there are some custom recovery flashable zips. I've used these and they're from a good developer. Just read the threads very, very carefully and upgrade incrementally like they say to. This is a bit riskier than taking OTAs, but it worked fine for me.

MJB and NE4: http://xdaforums.com/showthread.php?t=2789917

NE4 to NJ1: http://xdaforums.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792

The easiest way to root your phone on any S3 stock rom is to download a recovery flashable SuperSU and store it on your SD card: http://xdaforums.com/showthread.php?t=1538053

Then use Odin to flash a custom recovery, be sure to uncheck auto reboot. Upon success unplug USB and pull battery from phone. Replace battery and boot straight into custom recovery with vol up + home + power. Don't let your phone boot normally or you'll lose custom recovery. Once in custom recovery, flash the SuperSU zip from your SD card. When you reboot your phone you'll probably have to update your SuperSU app from the Play store and it might take a few reboots, but you'll end up rooted. Or, if you mean to flash a custom rom anyway skip the whole SuperSU business, boot to your custom recovery, make a backup, then flash your custom rom.

Good luck. Hope the Odin back to stock works. Bootlooping in your pocket is certainly peculiar behavior; most people actively do something to mess up their phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
Same thing is happening. I'm stuck at the glowing Samsung logo now after the AT&T animation.

Here's exactly what

1. Wiped data/dalvik/etc

2. Put phone into download mode, and connected it to PC with odin

3. Downloaded the file, extracted it, and put it into the "PDA" section of odin

4. Hit start, and let it do it's thing

5. Phone restarted and got stuck.

I am on stock recovery now too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Try a full wipe, or factory reset (can't remember quite what its called) in the stock recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Try reflashing with Odin but do not check anything in Odin except f.reset time. Once it starts flashing and you see the word reset in the status window, remove the USB cable, remove battery, replace battery, boot into recovery, full wipe, reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rovon:
FINALLY! Don't know why a combination like that worked but it did. Thanks for all the help. I was ready to lay down $600 for a new phone T__T
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Those are some nice write-ups, Jason. I hope you don't mind if I quote them for others in the future.

Also, once you get the first OTA installed, Rovon, you can short circuit the waiting 24 hours between OTAs by changing your system date/time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
There's nothing like a wipe in the stock recovery for getting everything squared away. Glad it worked out for you. :highfive:

---------- Post added at 03:04 PM ---------- Previous post was at 03:00 PM ----------

Quote away.

Between Knox, the brick if you downgrade bootloaders, and lack of released full firmware I found the learning curve to be a little steep for this phone.
[Motorola Droid 4] QA Bot:
[Q&A] [ROM][JB] [4.4] Avatar ROM for Motorola Droid 4 (maserati) - Updated [Jan 13,2

Q&A for [ROM][JB] [4.4] Avatar ROM for Motorola Droid 4 (maserati) - Updated [Jan 13,2014]

Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.

Before posting, please use the forum search and read through the discussion thread for [ROM][JB] [4.4] Avatar ROM for Motorola Droid 4 (maserati) - Updated [Jan 13,2014]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.

Thanks for understanding and for helping to keep XDA neat and tidy! :)
[Dell Venue] beestee:
I figured out how to enable the measurement tool in the dell gallery app after the update that removed the functionality.

Within the app, go to settings then tap the app version number (it said 'Gallery 1.3.1' in my case) several times quickly and debug options will appear. Tick the option for "show measurements" and you are in business.
[Dell Venue] jumpup:
[MENTION=1438946]beestee[/MENTION] thanks for the tip. Worked like a charm on my Venue.

I am quite surprised the Venue community hasn't grown to the unit having its own forum. This is an amazing device.
[Galaxy Note 4 General] Mr.Menu:
Hi,

This looks like a very helpful website and I have a tricky objective that I wondered if anyone here could help me with.

My wife bought a Note 4 (N910G) and she would really like to have a few options that aren't available on the stock Telstra firmware.

She is Japanese and would really like to have the stock dictionary from a Japanese note 4.

and also the Japanese language isn't available on the default N910G

Is this the place I can request help with things like this?

or is there a place I can request custom roms?

or is there a place I can learn to take bits and pieces from other firmwares?

I started a tutorial but I can'T find the firmware for the Japanese release note4.

and I don't know where to even start.

Is there even a way to just add more languages to the default phone language dictionary ?

I'm sorry if this isn't in the correct forum, I'm off to search a bit more.

on a side note I also have a note 4 N910U and that actually has the japanese language available by default but does not have English to Japanese dictionary by default.

The dictionary I am referring to is the one that pops up when you highlight things in the default samsung browser and such.

Thanks again for any help
[Galaxy Note 4 General] toofimoofi:
910G/F roms here

http://xdaforums.com/note-4/snapdragon-dev
[Galaxy Note 4 General] yussuf007:
Language enabler from playstore i think its do it. Ask Wanam or download the app and try.