yashsingh1/xdaforums huggingface dataset:
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
You're welcome.

My daughter is in school and I have reminder issues. I can take the pdf calender and plug in ALL the holidays, short days and off days and never miss a wake-up or miss her at the bus stop again. And not have to worry about waking up early on a non school only to find out later they're wasn't school that day.

The backup to sdcard comes in handy too. Set it, back it up and forget it; but check the widget frequently.
[Nexus 7 (2013) Q&A] JackOfOwls:
Can't access FastBoot mode & sporadically won't power back on after I attempt it!

When it's working, my brand new Nexus 7 2013 Wi-Fi powers on and off normally when pressing and holding the power button for 3 seconds. But when I attempt to enter FastBoot mode (I plan on rooting it) by pressing the power & vol up/down simultaneously, nothing happens, just a black screen as if the device is dead. What's worse is that I then have great difficulty getting the Nexus to even power on normally. Right now it appears to be dead but if I press & hold the power button in many attempts it might come back on. This always happens right after I attempt to enter fast boot mode. Using Android 5.01. Can anyone help me with this problem? I'm on the verge of RMAing it since I can't seem to get it to power on anymore but will keep trying. I really would like to root this but it seems impossible at this point.
[Nexus 7 (2013) Q&A] Snowby123:
Instead of using fastboot, I would recomend you use the Nexus Root Toolkit.

It automates the process. Follow the tutorial in the following thread.

Just make sure you have USB debugging enabled in the developer options.

http://xdaforums.com/showthread.php?t=1766475
[Nexus 7 (2013) Q&A] JackOfOwls:
Thanks for the pointer. The website for the tutorials & FAQ in the first post of that topic appears to be down right now but I'll check it out later. Still curious as to why I can't access the FastBoot on my new Nexus 7 2013 by pressing Power + Volume up/Down. Hmmm. Makes me think something is fubared. Heh.
[Nexus 7 (2013) Q&A] JackOfOwls:
This is becoming FAR more complicated than I would have wished. I used the latest version of the Nexus Toolkit and everything seemed fine, window popup tell me it's rooting, then I come to the Teamwin GUI. Now I'm stuck on that screen with a sh*tload of options and no idea what to do next. All the while the Nexus Tookit popup tells me it's Waiting For Device. If I select Reboot from that menu it gives me a warning that there's no OS installed then proceeds to normally boot to Android 5.02 with a final Nexus Toolkit popup when I get there saying I need to open Busy Box & SuperSU and blah blah blah blah. I check my apps for SuperSU and it's no where to be found. I run Root Checker to see if my tablet is rooted and it's not. I had really hoped this was going to be simple, but I suppose I should be thankful that it didn't brick my new Nexus.
[Nexus 7 (2013) Q&A] Snowby123:
It should have been simple.

Whenever it fails for me I just try again.

Read the instructions carefully.

You should know what you are doing before you attempt anything.
[Nexus 7 (2013) Q&A] JackOfOwls:
I'm almost at my wit's end. Re-tried it FOUR times and I always hit that "Team Win Recovery Project v2.8.7.0" GUI with the following options: install, wipe, backup, restore, mount, settings, advanced, reboot. None of them offer easy or intuitive answers on what I should do next when I click on them. Just to exit that goddamn GUI I have to select Reboot, with the result that no rooting takes place. Unfortunately, the video tutorials on the site are for older versions of Nexus Tookit and don't show the TWRP GUI at all (just the splash screen), and just goes directly into the rooted tablet. I'm guessing that the latest versions of these tools are for advanced users, whereas I'm pretty much a total newbie. I tried posting in that topic but it says I don't have rights to do so.
[Nexus 7 (2013) Q&A] Snowby123:
In response to this reply you gave me, I decided to test the toolkit out myself.

I successfully performed a full backup, an update to the latest OS, and successful root.

I can't say what your problem is.

Team Winn Recovery Project (TWRP) is the custom recovery that gets installed.

When I rerooted with the toolkit the tablet automatically booted into TWRP in order to complete the rooting procedure.
[Nexus 7 (2013) Q&A] JackOfOwls:
I've read of a few people that had the exact same issue I've had but couldn't find any solution. Even tried manually browsing with the TWRP Install button but couldn't even find the TWRP recovery images (though Nexus toolkit does appear to download them during the install of that toolkit). I guess this is suppose to all be automatic but for me it's the opposite of that. This is too much for a newbie to try and figure out on their own. Looks like I'll just have to find an alternate method to root. Thanks for your help.
[Nexus 7 (2013) Q&A] JackOfOwls:
Update: I just used CF-Auto Root and it worked perfectly. Literally a one-click solution to get my Nexus 7 Wi-Fi rooted. This is what I should have done in the first place. Another benefit of this entire issue I had is that the problem with not being able to enter FastBoot mode by pressing Pwr + Volume down (the reason for my original post) went away, luckily, since I wouldn't have been able to use CF-Auto Root without it. My next goal is to downgrade my Android version to KitKat 4.4.4 which I should be able to do now. New question: how do I do this? lol
[Nexus 7 (2013) Q&A] Snowby123:
To downgrade to 4.4.4, follow the instructions given by Google.

https://developers.google.com/android/nexus/images?hl=en
[Nexus 7 (2013) Q&A] JackOfOwls:
Oh, okay, thanks. I hear a lot about users bricking their android devices going from Lollipop to Kitkat, but I figure you can't go wrong following the directions of the Great God Google himself...or can you? ;)
[Nexus 7 (2013) Q&A] Snowby123:
What benefit does kit Kat have over lollipop?
[Nexus 7 (2013) Q&A] JackOfOwls:
Gaming supposedly. A lot of users claim that Lollipop plays Android games, especially older ones that haven't been updated lately for 5.0+, sluggishly compared to KitKat. However, after just having bricked my Nexus 7 using Nexus Toolkit trying to downgrade to KitKat earlier tonight (luckily, was also able to restore back to 5.1.1 using Nexus Toolkit), I may just stick with 5.1.1 for a while longer. It actually runs rather snappy for me on my Nexus 7 2013, and it plays 8-bit and 16-bit emulated games beautifully.
[Nexus 7 (2013) Q&A] elonus:
You can manually install kitkat if you want to try. This guide tells you how:

http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/

The only thing you have to do differently is that you have to download the 4.4.4 image instead of the one linked in the guide. You can download that from here: https://developers.google.com/android/nexus/images
[Nexus 7 (2013) Q&A] JackOfOwls:
Hi. I followed this tutorial to the letter but it ends up bricking my Nexus 7 2013. It just hangs at the Google boot screen after typing the last command "fastboot reboot." Any ideas on why this happens and how I can get a successful downgrade to KitKat?
[Nexus 7 (2013) Q&A] Snowby123:
try using the nexus root Toolkit. it can be used to automatically update the software, so I find nothing wrong with trying to downgrade the software with it. also, it works great at repairing a soft brick
[Nexus 7 (2013) Q&A] JackOfOwls:
My Nexus 7 2013 is one of those that can't normally downgrade to KitKat due to hardware issues so I had to use the information in the last post of this thread to revert to KitKat 4.4.4. But I discovered I have an issue under KitKat where I can't connect my Nexus 7 to my PC with the USB cable and use it for data transference (there's a missing Nexus 7 device driver under Win7) so I went back to Lollipop 5.02 for the time being. Does anyone know why KitKat gives me a missing Nexus 7 driver in Win7? I have all my google USB drivers installed and working.
[Android Q&A, Help & Troubleshooting] husamali2111:
Help with my Samsung E7 AKA (SM-E700H)

please guys i need a custom rom for my phone Samsung E7 AKA (SM-E700H) :confused: :confused:
[Android Q&A, Help & Troubleshooting] vk diwan:
Really man if you find it pls tell me too.
[8525, TyTN, MDA Vario II, JasJam General] alkizmo:
First, it'd like to thank

MikeChannon

for pointing out something important that narrowed down my testing.

Now, onto the problem Symptoms :

- D-Pad, IE and Email buttons cease to work

- Screen fades to white or comes back from standby as white

- Display is slight disaligned to the side, 1mm of left appears on right side.

- Randomness in all above symptoms.

Cause : It is the D-Pad connector.

Yes, the D-Pad connection DOES cause the whitescreen. It's odd and illogical, but this is the conclusion I have reached.

ALL the previous guides, such as sliding plastic between the screen and casing, were randomly moving things inside.

By CHANCE ONLY it'd affect the D-Pad connector positively. That is why such solutions only worked for a few people temporarely.

SOLUTION :

You will need to try variants of the following things :

- Tightness of the screws over the connector

- Disconnecting the plug and reconnecting it very carefully

- Pressure over the bibbon between the D-Pad connector and the screen.

- Pressure over the D-Pad connector itself

- Tightness of the screws over the D-Pad PCD

- Tightness of the screws closing the plastic casing of this part of the phone

To stress-test the variants, I ran a D-Pad intensive game (Skyforce) for 30 minutes or until the symptoms came back.

I've played around with all those, giving mixed results, but definitively making a difference.

My final and best result was by putting a thin foam piece over the blue parts in the picture below. (Ignore the red circles, original picture is taken from a website)

The foam I used was the typical foam sheets you find in packaging for fragile electronics such as motherboards, hard drives, graphic cards etc. It has to be super thing in other to close the casing without buldges.

There isn't a specific thing you can do that will make your D-Pad be reliable and the whitescreen to go away. You'll have to do several tests, so I recommend you keep your phone disassembled while testing. The connector is VERY VERY SENSITIVE. That is why I cannot be any more precise in how to fix this. However, you NOW KNOW what causes the screen to freak out and buttons to stop working.

What I did for testing :

I have tested my phone while it was completely disassembled. Meaning I had the back of the monitor open, as seen in the picture above.

That way, I could fiddle around and instantly test the result.

I've fiddle with the cables, the screen pressure, everything. Nothing returned the screen from being white or becoming white.

Putting pressure D-Pad connector's ribbon or actual pin caused the screen to either turn on white, or fade to white. (Results often noticed only after going in & out of standby)

It also caused my D-Pad buttons and the top 2 buttons (IE & Email) to either work or not work.
[8525, TyTN, MDA Vario II, JasJam General] alkizmo:
Oh and this is my testing setup. Elastic band to hold the battery in place, everything else opened. However, I had to place/remove the backcover of the screen part of the phone to test as it affects the pressure put on the connector.
[8525, TyTN, MDA Vario II, JasJam General] mutantblack:
wow. I don't have balls to break apart my 8525 like that.
[8525, TyTN, MDA Vario II, JasJam General] alkizmo:
Well this fix is for those who got a big enough problem and can't return it under warranty.

Anyhow, taking apart the TyTN is quite simple, and the thing is sturdy.

Only and only the D-Pad connector is tricky. The big ribbon connecting the two halfs of the phone is quite solid and never caused problems.
[8525, TyTN, MDA Vario II, JasJam General] jwagman1:
guys... what/where can i get the screw driver to open this mofo... it looks like a hex allen wrench but that doesnt work...

i have had this issue for months now and will try anything to fix it but i need to know where i can get this screw driver and fast!!!!
[8525, TyTN, MDA Vario II, JasJam General] Vasichko:
So it is a problem with the connector itself or cause by flex in the cable?

Also, where are you putty pressure on the connector? Are you saying if the screws are too tight this is a problem as well.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
It's a TORX No6 screwdriver you need. Available online or from stores like Maplin who sell Phone screwdriver sets.

Check out links in the Wiki here or in my signature for internal pics, dismantling guides and to download the service manual (that also has a dismantling walkthrough)

Mike
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Seems to me there may be a bit of trial and error regarding the fix. The service manual points out that the d-pad connector must be precisely inserted and absolutely level. So both under-tightening the screws or over-tightening could distort the connection. If you have it apart, take out and reconnect the push in connector several times This helps to ensure there is no oxidisation on the contacts.

(PS. this is not my fix so I cannot testify that it will work for you, though I believe it is on the right track, at least for some cases of this problem)

Mike
[8525, TyTN, MDA Vario II, JasJam General] marciton:
It's really intersting to know I'm not alone to have this issue ...

Do you have a site who describe how to open the Hermes ?

Thanks
[8525, TyTN, MDA Vario II, JasJam General] jwagman1:
THANK YOU!! amazon.com overnight!!! woooo
[8525, TyTN, MDA Vario II, JasJam General] Vasichko:
I tried this diy.

I didnt have a small enough phillips to remove the screws from the connector on the D-Pad.

Know where I can get one?

So I took all the connections, put some automotive electronic connection cleaner on a q-tip and cleaned all of the other ones.

I used some automotive light double sided adhesive that you can get at Auto Zone instead of form. I only used 1 side of the adhesive and didnt peal the other side off, if it doesnt work, its easily removeable, just wanted to make sure it stays in place when I re-assemble the phone.

I also added some in a place you didnt which I show in yellow on your photo.

So far so good after 5 minutes.
[8525, TyTN, MDA Vario II, JasJam General] Miguel-:
Mine PDA was also totally disassembled and atleast in my device the problem wasn't a faulty connector.. I had the front panel off and when I squeezed the Xilinx fpga-chip(black square on d-pad circuitboard) the the screen worked fine -when i took my fingers off it faded back to white. Earlier I also tried re-soldering the connector but it didnt work on my device.
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Dismantling guides and the service manual:

www.mikechannon.net

Mike
[8525, TyTN, MDA Vario II, JasJam General] RaptorGuy:
Hermes / TyTn / 8525 White Screen

Hey guy,

Nice write-up.

Good that someone has taken the time to experiment with different procedures.

I gave up on mine, after taking it apart time and time again.

-Reseating the cables and completely disassembling the unit was a tempereary fix, so I sold it on eBay for a parts / repair.

I just purchased another on eBay.

This time, instead of getting worked up about the white screen of death, I had purchased a warranty from www.squaretrade.com.

I am not an AT&T customer, so I unlocked the phone.

Neither AT&T or HTC can help when you dont have their service , or it's a branded phone.

Keep up the good work.
[8525, TyTN, MDA Vario II, JasJam General] Vasichko:
So far since my post before lunch today. No problems at all.

It used to white out when taking a picture with the camera, randomly when sliding out the keyboard, randomly when using the D-Pad.

No problems at all today after doing this fix posted here and adding the extra pad that I did.
[8525, TyTN, MDA Vario II, JasJam General] Chryslerq:
im gonna have to try this when i get my new housing....anyone know where i can get a front camera?
[8525, TyTN, MDA Vario II, JasJam General] Vasichko:
Just giving another update. So far so good, no problems at all.

DPad no longer has the issue of not working here and there.

White screen issues appear to be gone.

Hopefully for good.

I will still post updates so you all can know the status.

Thx again for the right up. I will post some pics of the type of tape I used as well.
[8525, TyTN, MDA Vario II, JasJam General] fone_fanatic:
I have the rest of december left on my warranty. Do you guys think PPCtechs will know how to fix this? i don't want to send it to them and have it sent back with the same probs (like they did last time i sent it in to get my scroll wheel and camera lense repaired).
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Yes indeed, re-aligning and reconnecting the connector works for many but will not work for all. There are, as you say instances where it is a chip connection that's at fault. There is little if anything you can do with that problem other than board replacement unless you have the correct tools - http://xdaforums.com/showpost.php?p=1724236&postcount=66

Mike
[8525, TyTN, MDA Vario II, JasJam General] Vasichko:
It looks to be a design flaw. I dropped my maybe 3ft on the carpet yesterday and got the white screen issue. I took apart and looked at the connector in question. Even with it screwed in you can unplug it half way. So I added some more padding.

I think part of the problem is that coming from the back of the LCD to the DPad board or whatever you call it, the angle of the ribbon cable declines.
[8525, TyTN, MDA Vario II, JasJam General] :
Thanks for the fix and all those who contributed. I was worried that my "backup phone" wouldn't be a good backup phone after all lol.

Thanks again!
[8525, TyTN, MDA Vario II, JasJam General] EvilAsh:
Got mine fixed

Had to assemble and disassemble my unit like 3 or 4 times (first 3 times I kept forgetting screws). The first time I only put foam on top of the ribbon. Worked for about a day. Re-opened it again and placed an extra foam at the bottom and so far it seems to be working again. Keeping my fingers crossed that it doesn't bork again. Thanks for the awesome guide!
[8525, TyTN, MDA Vario II, JasJam General] jtf:
Fixed at last

Hi,

i got mine hermes 200 fixed too by refloating the Xilinx chip on the PCB with a heatgun.

I tried the foam method several times, and it seems to work in the first time (the screen was schown when the phones was dissasembled ) but still got the white screen and dead buttons when the phone was assembled. And in the end i always got white screen.

I dissasembled and reasembled the D-pad connector a few times, and personaly dont think thats the Problem.

I read about the Xilinx chip and figured out while the phone was disasembled, that when i pressed on the chip the hermes the white screen was gone. So i resoldered the chip with a heatgun and some liquid flux and it worked. After reassembling the hermes booted up just fine with the screen and the buttons all working.

I'll hope this will last.

Cheers

jtf
[8525, TyTN, MDA Vario II, JasJam General] cabi.costa:
- Tightness of the screws over the connector

- Disconnecting the plug and reconnecting it very carefully

- Pressure over the bibbon between the D-Pad connector and the screen.

- Pressure over the D-Pad connector itself

- Tightness of the screws over the D-Pad PCD

- Tightness of the screws closing the plastic casing of this part of the phone

but...while talking about tightness, you mean less tight or more tight?
[8525, TyTN, MDA Vario II, JasJam General] hgupta:
thanks for this guide!

Mine started acting up when I pulled off an adhesive based screen protector, then I started getting whitescreens.

So I took mine apart this afternoon. Found lots of dust and debris that must have worked its way in. Taped up the dpad connector between the screws. barely tightened scews on either side of dpad. Reassembled everything as tight as possible.

Everything is working great again!

Those screws are tiny! Don't lose them!
[8525, TyTN, MDA Vario II, JasJam General] EvilAsh:
My screen still goes white from time to time but I found a simple way of fixing it without dismantling the entire thing. I just power down the screen, squeeze the d-pad. Once I turn on the screen it's back to normal :D. I think the reason why I keep getting the whitescreen of death is because wear really tight pants! :eek: Whenever I take out my phone I may have squeezed the D-pad hence the white screen.
[8525, TyTN, MDA Vario II, JasJam General] cabi.costa:
Ok with this method the screen doesn't goes white anymore..but strange thing happens:

the dpad lights up when i turn on the screen, and lights offf when i turn off the screen. Also, pads are not always working when pressed. The led status it's not working...it seems that dpad led's are working also as a led status but this has influence with the work of pads because sometimes allows me to do something, like start the dialer, and sometimes also if pressed thay don't do anything... how can I solve?
[8525, TyTN, MDA Vario II, JasJam General] wdmerrifield:
I'm coming to this post way after the fact, but I have a Cingular 8525 and I want to know where the Xilinx chip is. It is referenced here, but there is no description of where it is.
[8525, TyTN, MDA Vario II, JasJam General] jtf:
in Post #163 there is the pcb for the front buttons under the touchscreen shown of the hermes200 and the Xilinx chips is the black IC on the right side.

you've got the hermes100 and on your buttons pcb the Xilinx chip should be more at the right end of the pcb.

I think the picture on this side should be the right pcb:

http://www.cellphone-repair-shop.com/prodimages/parts/HTC8525Keyboard-150.jpg
[8525, TyTN, MDA Vario II, JasJam General] afaast:
This guide is excellent, fixed my problem! Problem started after I took my phone to a Grinspoon and Shihad concert. Got bashed around in the mosh. Keypad used to only work for say three presses and random white screen. So don't take your good phone to gigs that's all I can say!

I ended up sticking a few layers of tape on top of the connecter so it presses tight against the cover. At first I used a bit of rubber but it was too thick, I put the whole phone back together and the keypad would press the wrong buttons. Took apart again :( and replaced it with some tape now all is good :)
[8525, TyTN, MDA Vario II, JasJam General] stevieboy:
had much the the same issue as here,in the course of trying to fix it i tried all the prescribed wisdom and in the end found my own variant problem and solution.on the underside of the runner that sits directly over the d pad connector was a black strip of stiff thin foam/plastic this was deforming the connector causing intermittant contact,once this was removed all was restored to health
[8525, TyTN, MDA Vario II, JasJam General] maryogav:
happy:D

done everything he said... and i was surprised to see it really works:D

i've just put some tape u use to electric wires... nothing fancy :P and it stopped getting white... i hope it won't be doing that ugly thing 4 a long time... because i'm used with this phone... i find it really useful... so thanks 4 this advice... if u were in romania... i'd give u a beer... u deserve it;)
[8525, TyTN, MDA Vario II, JasJam General] TheLegace:
Surprisingly this worked, I cant even beleive it, this whitescreen issue has been bothering me for almost a month now. As I am in no position to get a new smartphone, and I desperately need it to run some applications I am so happy that this is working. I just taped down some foam I got from my hard drive. It is working quite well now for about an hour.

I figure the foam just acts as an insulator preventing electrical charge from disappating into the air and rather into the circuit that is designed.

Kudos because there would be no way I could have figured this out.

Cheers and Thanx

TheLegace.