yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] Robogar:
So I was unlucky enough to drop my N4 before I was able to get a case for it. I dropped it from my lap while getting out of a taxi so it wasn't a full on drop. At first I thought the only damage was cosmetic - a nick on the chrome trim on the top right corner of the phone.

However afterwards I noticed a small white/bright spot on the screen near that corner where it looks like the backlight is bleeding through. It's most notice-able when the screen is showing something white, less notice-able with colors (red, green, blue etc), and completely fine when showing black.

I've checked some info and it doesn't seem like it's a dead pixel, and just seems overall larger than a dead pixel. At the same time it doesn't seem like a lit pixel either since it's not visible on black. At the moment I'm very thankful that the phone is still very much use-able, but would like to find out what the problem is, and perhaps how intensive a repair this would involve since it is a bit annoying sometimes.

Anyone have had a similar problem or have any ideas?
[Nexus 4 Q&A, Help & Troubleshooting] jamesc760:
Is normal. Stop obsessing about it. No phone is perfect. Even my wife's iPhone 4s has defects. If you are looking for flaws, you will find them, guaranteed. Just use your phone like you used to.
[Nexus 4 Q&A, Help & Troubleshooting] Robogar:
Yeah I'm definitely learning to live with it. It may also not look so bad in a photo but it's still pretty noticeable when you're holding the phone in your hand - especially when I'm scrolling around and you can see this static white spot that doesn't move.

Just overall interested in what the problem is as well. I've seen dead pixels and also phones that were dropped where the screen looks completely fubar'd... but haven't been able to find any examples where the screen is like this.
[Nexus 4 Q&A, Help & Troubleshooting] caaznkid:
RMA if it's that annoying. Assuming ur phone doesn't look too damaged that they'll say it was your fault.
[Nexus 4 Q&A, Help & Troubleshooting] ak700:
I do see a few scratches on the screen. Google may not RMA for that reason. If there is another reason like a defect, use that to RMA. IML no Nexus 4 is perfect. I have RMA'd about 4 times till now with a new reason every time. Now after completely blocking my credit card, I have learned to live with an imperfect Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] Robogar:
Where do you see the scratches? I haven't even noticed them! :p

I guess from the replies I should learn to live with it then. Thing is I really thought this was due to the drop, but it's also possible it was a defect that I didn't notice... I saw some N4s with the light bleed problem, but were from the edges of the screen, that's why I really thought this was due to damage.
[Nexus 4 Q&A, Help & Troubleshooting] ismethajametovic:
Send it back in, duh. It's still under warranty. :crying:
[Nexus 4 Q&A, Help & Troubleshooting] ak700:
Check these -

I don't know whether these are scratches or camera problems.
[Optimus One, P500, V Q&A, Help & Troubleshooting] Enthydor:
Hello XDA.

See, here is the problem ...

My friend has a LG Optimus One P500, he asked me to root it. I succesfully rooted his phone.

The other day, he send me a message that he bricked his LG Optimus One P500, he said that he installed a font with ROM Toolbox.

I went to his place, the phone was totally bricked, we looked all across the internet, every solution we found ... Did just not work.

So I came here, the place of all android knowledge lives to ask this, How can I unbrick this blazing phone.
[Optimus One, P500, V Q&A, Help & Troubleshooting] shinobisoft:
Have you tried booting into recovery ( Power + Volume Up + Home ) and then wiping cache and dalvik cache?
[Optimus One, P500, V Q&A, Help & Troubleshooting] pmvyas:
Hope you have installed a custom recovery. If you have only rooted, maybe a factory reset would help.

Sent from my LG-P500
[Optimus One, P500, V Q&A, Help & Troubleshooting] Enthydor:
No, unfortunatly he did not install a custom recovery, but something happened, when I plugged the hone to the PC and tried to do a hard reset.

But I can'y put my finger on it. Maybe u can tell me?
[Optimus One, P500, V Q&A, Help & Troubleshooting] shinobisoft:
With stock recovery you should be able to perform a factory reset by pressing and holding the Power button and both volume buttons for 10 seconds. If the USB drivers were previously installed, you might be able to boot the device in to fastboot mode and then use Android Flash Recovery to install a custom recovery.
[Optimus One, P500, V Q&A, Help & Troubleshooting] Enthydor:
Thanks mate, I will give it a shot. I will reply you later.
[MDA II, XDA II, 2060 Accessories] Zer0:
Does anyone know a place to get spare parts for the XDA II (not likely) or does someone have a broken XDA II they are selling parts off of?

I somehow managed to crack part of the casing of my I-mate around my power switch. Well tonight it finally broke off and I am devistated. (ok well.. pretty upset at least)

If anyone has a spare... I am looking for a replacement black piece (antenna cover) of the casing. Would pay generously for one.
[MDA II, XDA II, 2060 Accessories] Rayan:
I'm looking for a spare casing... :cry:

Last friday I dropped my MDA2 and the case now has a small dent near the Bluetooth LED and a small scratch on the opposite corner and I want to replace it as soon as possible!

Anybody knows where to get replacements?

Is the case metal or plastic?

Thanks in advance...

Rayan
[MDA II, XDA II, 2060 Accessories] Matt Ryan:
I may have XDA 2 Spares!

I am currently battling to get my XDA 2 repaired under warranty by o2 in the UK..

If i lose: I will have an xda 2 worth of parts (minus the mainboard) less than six months old immaculate apart from the board and its connector.

so case is scratch free, screens perfect etc...

Failing that if anyone has an busted xda 2 with a working mainboard please mail me...
[MDA II, XDA II, 2060 Accessories] cmcmill01:
parts

Matt,

How did you get on with O2, I'm looking to get all the parts except the main board as I've got one of them.

Cheers

Cmcmill01
[MDA II, XDA II, 2060 Accessories] Matt Ryan:
I lost! No repair, no warranty, 6 weeks and no service!

I have come up with another solution for my broken xda connector.

The device still functions but i cant connect to my laptop/docking station, so im going to buy a bluetooth card and spare batt, keep the spare batt on charge using the docking station and use bluetooth to sync with laptop...

spare batt = £15

bluetooth card = £20

my total = 35

O2's = £185 a mear £20 cheaper than a brand new XDAII !!!

AND THEY WERE GOING TO CHARGE ME £17.50 to send the bloody thing back without having lifted a finger to repair the device! Until i went ballistic in the store in front of a dozen customers, and i do mean ballistic a bit digruntled wont work you have to loose it in front of as many customers as possible to force them to back down and return your property.

I will never buy new from O2 again, and as soon as the contract hits 12 months they are history bollox to them. The warranty is not worth the paper its written on, the shop service is less than i would expect from cowboys r us, save yourselves time and pain buy second hand theres still no warranty but its cheaper by far..

p.s. for those who are bound to ask, No mention of any charges including postage are/were made at the point of handing my phone over or at any time until 17.50 was demanded for its return.
[MDA II, XDA II, 2060 Accessories] gazzaman2k:
@ Matt Ryan

my XDA 2 connector snapped from the pbc

ill tell you how to fix.....

get hold of an ipaq 38xx or 39xx, SPV 1, or spv2 or xda 1 or xda2 board and desolder the connector off and put a new one on

i got hold of a spv1 for less then £30 and ive stripped the board and sending it to my mate who deals in small eloctronics reapir hes charging me £15 to hot air rework the connector off the spv and put it onto the XDA2 pbc

meaning all repaired and stronger then before :)

gaz
[MDA II, XDA II, 2060 Accessories] shwhost:
did you not sign an a-novo repair sheet. It states clearly on the reverse side of this that is your device is beyond economical repair, or if you refuse a quote, you will be charge £17.50.
[MDA II, XDA II, 2060 Accessories] Matt Ryan:
nope i didnt sign a-novo contract/ job sheet

I took the phone to an o2 shop and signed THIER repair sheet, nothing on reverse nothing refering to charge for returning device if not repaired

Nothing anywhere, nada...
[MDA II, XDA II, 2060 Accessories] xdapartsfromTW:
Repair XDAII's screen, connector and casing in the UK

Hi guys,

I can repair the following faults/damage of XDAII here in the UK.

1. replace broken connector.

2. repalce broken LCD screen.

and please email me for any damages/faults/repair that you require for your unit, and I'll qoute you accrodingly.

all parts are brand new!!! not spare ones from broken unit.

please email me for a 'HAPPY' qoutation today on info@wangtao.co.uk

cheers
[MDA II, XDA II, 2060 Accessories] CDTV:
Hello-I need help finding a place that in the USA can repair my xdaII. I just dropped it on my marble floor -- OOPS! I thought you may have heard of a place for me to send it?? I believe I've broken the lcd & glass...it functions fine but has major cracks/shatter marks thoughout the screen...Let me know if you can help & thank you
[MDA II, XDA II, 2060 Accessories] cruisin-thru:
For anybody interested, I have an xda 2, the screen is bleeding, the imei is blocked in UK owing to insurance claim but will work in rest of the world. I want £50 gbp. If nobody takes it I will post on ebay.

S O L D
[MDA II, XDA II, 2060 Accessories] Kaizer:
hello christin

contact me at +65-98787543, i buy your phone

regards

Kaiser

www.kaiserelectronics.net
[Desire HD Q&A, Help & Troubleshooting] Steam.:
whenever I try to get the identifier token, i get command error.I've read that I need the newest HBOOT for it to work.It's android 2.3.5, and it won't work with AAHK as far as I know.So, can anyone link me to the latest RUU, or just the HBOOT so I can flash it?

software number: 3.12.405.1

baseband:12.65.60.29U_26.14.04.28_M

build number:3.12.405.1 CL199157 release-keys
[Desire HD Q&A, Help & Troubleshooting] glevitan:
AAHK has been retired and has nothing to do with an unlocked bootloader. Find links in my signature on how to achive your goals. Whenever you enter an IRC channel, wait, perhaps people is busy doing something....a minute is not time enough. ;)
[Desire HD Q&A, Help & Troubleshooting] Steam.:
My bad, I left immediately, I have very few experience with IRC anyways.I saw you were online, but I couldn't tell if idle or present at the moment.anyways, simplegoldcard tool requires framework, so I'm downloading that atm.I'll be on the IRC too now.
[Desire HD Q&A, Help & Troubleshooting] Steam.:
I rushed it.Turns out the Easy Ace Root Tool by glevitan gets everything done on 2.3.5.Just DL it and use it.It supports what AAHK doesn't.(AAHK works best 2.3.3/2.3.4)
[Desire HD Q&A, Help & Troubleshooting] Steam.:
Also flashing kernels from the rom zip requires S-OFF, learned that from glevitan's guide too.Thanks to glevitan again.This thread can be locked now.
[HTC Desire S] fstarockr:
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.

Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.

I had ICS for htc running before without any mods and wanted to try the root / mod thing.

My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.

Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).

anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).

Ive been chasing my tail and just gave up.

please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.

thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!

HTC Desire S GSM

unclocked via htcdev

S-ON

hboot: 2.02.0002

Radio: 3831.19.00.110

Latest CMWR

Gets stuck @ white screen

Tried:

factory reset / wipe / dalvik / batt stats

reboot to recovery: install SU, gapps, cwm rom 10.1 (also tried 7.1). reboot / then fastboot boot boot.img (from the CWM zip). nothing.

Ive tried re installing the EU RUU - also nothing. Renaming the rom.zip to PG**IMG.zip, it reading the file then stops 2 fastboot screen. nothing. nada.zip.
[HTC Desire S] asgardr:
There are so many people, blindly walking in to troubles just because they do not read,

and you seem to be one of them....

When you unlock your device via htc dev, your device stays s- on,

it means- whatever you flash, you have to flash boot.img from that thing ( meaning rom naturaly )

via fastboot

through command:

fastboot flash boot boot .img

Without it your phone will never boot...

Recovery you flash via fastboot as well via command:

fastboot flash recovery recovery.img

Then , when you have it, reboot your device to recovery

and flash superuser and its binaries

And that woud be all you have to do in order to have rooted and booting device...

Edit: Now i've seen your other post- it is a 100% the one im reading now,

You should know it is enough to post your question once,

people'll find it...

Because of impatience you're in trouble already with your phone;)
[HTC Desire S] fstarockr:
tx -

tx for that info - ill give it a go.

I reposted because some1 there said i was in the wrong section and supplied a link for the correct section (here) - so yes, i reposted to get the correct replies.

not to digress:

but as for not reading - i can assure u ive read alot. Been a freelance developer for 15 years. That doesnt mean that rooting often requires a handful of little hacks when things dont go smooth. Just like alot of programming tuts, the rooting ones have a similar "assumption" that u know whats half potting, and what will cause what and what wont. All the articles i read i made sure were either 2012 or 2013 - there is ALOT of old non applicable info around, I stick to xda of course as i really trust this place. as usual, not all is 1-2-3. thats all.
[HTC Desire S] asgardr:
Well thats true, obvious things for me do not have to be obvious for

somebody else- one sometimes forgets that- begging your pardon:)

If not for XDA, i'd've known not much at all...

I've given the shortest and simpliest way that never failed me before

so, i truly hope, for you it'll turn out to be usefull as well- with no further accidents...

As for comming back to stock: you must relock device's bootloader before flashing,

otherwise procedure will always be throwing an error....

Success;)
[HTC Desire S] fstarockr:
details details

As for coming back to stock: you must relock device's bootloader before flashing,

otherwise procedure will always be throwing an error....

Im trying to get a picture of the inter relations ~ pls bear with me:i dont want to be trying to sys c: when i dont have a partition kind of scenario - absolute clarity is needed :p - my apologies as i try wrap this up..

#bootloader:

do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?

#S-on/Off

I have been unable to get mine to off -

#unlocked bootloader

its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?

#RUU / Mods

I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?

#recovery

this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).

Im trying to figure out what i can do once, and what i have to keep fiddling with, so i can hone in and get up and running.

If my questions appear ignorant - then ignore me. Im trying to paint a very clear picture of the tech relations between the various aspects and how they relate / interact - which is crucial to moving on from noobness - so pls bear with me and drop the remarks / attitude. Ive read my a$$ off and am still unclear for what many assume is basic understanding.

Im sure there are ALOT of sane unlazy logic ppl out there stuck in the same boat - and sometimes ppl who are VERY knowledgeable get a bit semi-aggressive putting ppl off from asking questions.

So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?

lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?

Success;)[/QUOTE]
[HTC Desire S] Husky34:
i think u have MDDI pannel (not the one compatible with cianogen) try to flash a sense rom ;)

have a look of THIS
[HTC Desire S] Aquous:
Hi :)

On HTC devices, the bootloader is called HBOOT. This is a 100% device-specific program whose sole purpose is to initialize the hardware so that an operating system (such as Android, i.e. Linux) can load. If your bootloader is damaged, your device is 100% bricked.

To prevent tampering with the system, HTC have locked ("S-ON") their bootloaders so that they won't accept unsigned ROM images. So, on your HTC phone, you cannot install any operating system other than what's provided by HTC. You can partially lift these restrictions by unlocking via htcdev, as you have, or you can fully lift all restrictions on your device by going S-OFF. S-OFF-ing the Desire S is done by exploiting a bug in HBOOT version 0.98 and overwriting the bootloader with a patched version ("Revolutionary") that has all write protection disabled.

In order to flash official HTC upgrade packages ("RUU"s), you can be either S-ON or S-OFF, but if you're S-ON you MUST lock the bootloader. Anything that's not a RUU can (only) be flashed without re-locking the bootloader.

Having an unlocked bootloader is only relevant when flashing new ROMs or recoveries. Having an unlocked or locked bootloader per se will not affect booting at all, with one well-known exception: if you're S-ON and htcdev unlocked, the write protection installed by the bootloader is still on for the bootloader, radio, and kernel partitions. This means that you can't flash kernels from a running OS -- only from the bootloader. This means that when you flash a custom ROM, it will not be able to flash the kernel automatically, you have to do that manually via fastboot. Failing to do that will result in your phone freezing on the white HTC screen when it tries to boot.

That's expected, because you're most likely not running a ROM that has a HBOOT version that is vulnerable to the exploit used by Revolutionary.

edit: nope, your HBOOT is newer than 0.98 and is therefore not exploitable.

Only official HTC RUUs require that the bootloader be locked.

Cyanogenmod can only be installed with the bootloader unlocked, but you may always re-lock after installing it. Remember to manually flash the boot.img (that's the kernel) via fastboot directly after flashing CM through your custom recovery.

A RUU is a *complete* software package for your device made by HTC. It contains everything from bootloader to operating system. I don't really know what else you're trying to ask, so please elaborate.

The recovery is a specialized mini-Android OS that allows you to flash new software (such as unofficial ROMs such as CM) to your device. What recovery you have installed has no bearing on your main OS. If you're htcdev unlocked, the only way you can install a custom (i.e. non-stock and non-crippled) recovery is via fastboot; if you're S-OFF you can use the 4EXT updater app from Google Play.

Why do you want to install stock?

boot.img is inside the zip of the ROM you're going to flash.

I hope I've been able to answer most of your questions. If you require more help, please search first, and if you can't find what you're looking for, please do ask.
[HTC Desire S] teadrinker:
# bootloader

The bootloader must be locked to install an RUU (stock rom), it must be unlocked to install a custom rom.

# s-on / s-off

If you unlock your bootloader through htcdev.com, the phone stays s-on. This means you can't install a different radio or hboot (mostly not necessary anyway), or write to the /boot partition or recovery apart from in fastboot.

That means, after every rom installation, you have to reboot to bootloader (fastboot), and flash the boot.img (extracted from the rom you installed)

# recovery

A custom recovery is a must for flashing custom roms (it's where you flash the zips) , I recommend 4ext, other known recoveries are Cwm and twrp. Be aware that you can only flash recoveries in fastboot (not through an app) , if your device is s-on