yashsingh1/xdaforums huggingface dataset:
[Xperia Z General] Hellscythe:
mmmmm, unlucky.

Used my xperia z without a case for about 3 weeks and its still fine.
[Xperia Z General] danw_oz:
Yes sir they do, that is one big hype on all the Xperia Z overview pages on the Sony internet sites
[Xperia Z General] kuppodolphin:
Can you post the picture of the glass crack in your Xperia Z ?
[Xperia Z General] danw_oz:
Dude I have seen more broken screens on Iphones than any other phone, so I guess they have to do something about it, when the phone to buy outright is almost twice the price of almost any others.
[Xperia Z General] biffsmash:
Pure bad luck maybe...?

I hate to say it, but phones don't break by themselves.

Mostly people damage them like a chip on a windscreen and don't notice it, and it gets worse over time until BOOM.

I only know that over the many many years i've had phones, and trust me, since the dark days of bricks i've almost had them all, with all the punishment i've given my phones, including dropping them onto concrete (I've never owned an apple phone before anyone goes hang on), i've never had unexpected issues like this arise. In fact, i've been lucky enough not to actually ever crack or shatter a screen.

Sorry but i'm with Sony on this one, and they burned me with the X10.

As for Apple, they will just tell you your phone is water damaged and to get the hell out of their store unless you come back in a cardigan, slippers and non prescription glasses, and buy a new iphone off them when you do come back.
[Xperia Z General] OsiBasi:
I used mine as a ping pong ball .....

Maybe you bended it ALOT.
[Xperia Z General] Rchard:
That's pretty sad man. Then again these things happen, but not for everyone. I had a similar issue with my Samsung Galaxy S2. It got bended in my pocket while, I was sitting. When took it to repair they said we cannot fixed it under warranty coz it has been damaged. I was shocked and they said we can fix it with over 400 euros. Its insane.

Best way is to fix it yourself if its fixable by ordering the parts.
[Xperia Z General] decentgi:
if you wanna sell it let us know lol im sure in a few months parts will become really cheap. we have a guy at our local shopping centre who charges by the hour to fix your phone, im sure it wont take more than an hour to replace since i saw a video of one being put together in under 5 min lol

---------- Post added at 09:50 PM ---------- Previous post was at 09:25 PM ----------

and to be fair there is no way for sony to really know how it got broken, if apple honoured warrenty on their broken screens they would have gone bankrupt but there is nothing more disspointing than to have that happen. i dropped mine a few times not a scratch on it
[Xperia Z General] MinnesotaVikings1961:
Of course shouldn't that kind of dammages be coverd by the warranty. Sony has thr right on their side. On the otherside, I understand that you get mad at Sony.
[Xperia Z General] Geoffxx:
Those German guys ran over this phone with a car and it survived - I can't imagine how this happened - sorry dude
[Xperia Z General] Dsteppa:
People here that feel sorry for the OP, should stop doing so...

Don't get me wrong tho, you should be worried about your own device. There were numerous reports of the glass suddenly breaking, I really don't think that that these incidents are because all of these people weren't careful enough. What if all of these people with cracked glass were careful enough with their phones? Could it really be a heat issue? Or maybe a manufacturing error. Until we know the reason we all should be extra careful.

The people with cracked glass should report if they still had the anti shatter sheet and/or a case just so that we can narrow down some things for ourselves.

One note about the heat being the probable cause: The phone needs to become REALLY REALLY hot before it will break just like that. Lets just put the phone in our pocket for this example, the phone would/could reach a temperature of about 40C? (About the same as our body temperature)

But when the phone becomes hot because of heavy usage it becomes warmer then that 40C doesn't it? The only difference is that when the phone is in your pocket the entire phone gets hot, @ heavy usage only the part near the processor becomes hot. So there are really some things we need to think about and we should take these reports really serious, specially if Sony keeps waving us off that it's a user error.

(The reason why I chose the pocket example is because someone glass cracked while he removed the phone from his pocket)
[Xperia Z General] wawyed:
FYI.

How they make gorilla glass.

Can you explain the ion-exchange process?

Ion exchange is a chemical strengthening process where large ions are “stuffed” into the glass surface, creating a state of compression. Gorilla Glass is specially designed to maximize this behavior.

The glass is placed in a hot bath of molten salt at a temperature of approximately 400°C. Smaller sodium ions leave the glass, and larger potassium ions from the salt bath replace them. These larger ions take up more room and are pressed together when the glass cools, producing a layer of compressive stress on the surface of the glass. Gorilla Glass’s special composition enables the potassium ions to diffuse far into the surface, creating high compressive stress deep into the glass. This layer of compression creates a surface that is more resistant to damage from everyday use.
[Xperia Z General] fartlec:
yeah, i'm a bit concerned on this one, too. i've heard and read a number of cases like this that painfully reminds me of the nexus 4. i'm not gonna say it's the heat (someone on youtube registered a 49°C max at the middle-top, under the camera module, which isn't the spot where all these cracks occur, during a demanding game session), but it's somehow alarming. it's strange, because a lot of videos on youtube show xperia zs bended, trampled, thrown against almost everything like crazy. and then, someone (even a review, can't recall which, said their unit had a web of cracks in the rear panel after a week, so in the conclusion they assumed it's a fairly fragile device). the only thing i can think about is that different panels, front or rear, have a different resistance.

and no, sony isn't right. they advertised it as durable like hell (when they showed it, all the reviewers were dressed like near-perfect japanese gentlemen and where told to shatter it against a marble bath, prior to be introduced to a bikini hooker under the shower
[Xperia Z General] nick2crete:
This can happen to everybody ..lets be more kind to the OP :cool:
[Xperia Z General] Clark Joseph Kent:
Looks like thoughts have been expressed to/for the OP. As always if you are not happy with your device, the option to change is there. Thank You.
[MDA II, XDA II, 2060 ROM Development] spanky:
Do you want to upgrade from T-Mobile 1.60 to Dangaard 1.60.21???

This is what you have to do step by step:

1) download ruu16021wwe_dangaard.zip from the ftp specified in the post here in the forum

2) Unpack the zip file, then click with the right button on the extracted file (ruu16021wwe_dangaard.exe, make sure

you've winzip installed) and select extract to. Choose a folder where you'd like to put all the upgrade files

3) download xda2nbftool.exe from this page:

http://www.xs4all.nl/~itsme/projects/xda/xdaii-update-format.html and put the file in the

created folder

4) Open the MS-DOS prompt, go to the folder where all files are unpacked and digit the following

instructions:

xda2nbftool -d NK.nbf nk.nba 921211 (enter)

xda2nbftool -sd PH10 -so TMobile -sl WWE -v ms_.nbf (enter)

xda2nbftool -sd PH10 -so TMobile -sl WWE -v Radio_.nbf (enter)

xda2nbftool -sd PH10 -so TMobile -sl WWE -v nk.nba (enter)

xda2nbftool -e nk.nba NK.nbf 921211 (enter)

5) Now launch the upgrade file and enjoy!

This procedure could be adapted to any rom changes. The important thing is setting the right password for the HimaUpgradeUt.exe file. Pass is HTC for 0500 version and 921211 for 0600

version.

Many thanks to XDA developer Itsme for the support!!!
[MDA II, XDA II, 2060 ROM Development] popsi:
Thanks mate! I'll give it a try when I get home from my work.
[MDA II, XDA II, 2060 ROM Development] spanky:
Yesterday I unfortunately updated to 1.60 T-Mobile, So today I've started from T-Mobile 1.60 rom, then I’ve made all explained at the beginning of this post, ok?

But surely you can start from rom 1.52 and upgrade directly to 1.60, but you’ve to change T-Mobile with Qtek from the MS-DOS instructions, ok?
[MDA II, XDA II, 2060 ROM Development] orinoco:
Hello:

What are the benefits of the upgrade? Is it better radio stack (GPRS and BT)? Is it the ROM itself?

Thanks for your input?

Fernando
[MDA II, XDA II, 2060 ROM Development] popsi:
So does this look ok?

http://www33.brinkster.com/popsiwarez/screen.jpg

(needs to be opened in a new window, please cut&paste to new browser window, ¤&/% brinkster)

Just thought the new CE image version looks a bit odd, but I guess thats what happended after the commands on the file, just wanna be sure before I hit the upgrade button. So after I have installed this T mobile upgrade the one from Qtek should work.. right...

Again thanks!
[MDA II, XDA II, 2060 ROM Development] spanky:
cannot access to the page you linked !
[MDA II, XDA II, 2060 ROM Development] xtinc:
I'm sorry for my silly question. I got confused.

This method is for T-Mobile 1.60 to Qtek_Dangaard 1.60.21. However I can't find where ruu16021wwe_dangaard.exe is applied. I can see only the TMobile being extracted and updated. Does it mean we have to rea-apply the Dangaard update after this procedure? :?
[MDA II, XDA II, 2060 ROM Development] spanky:
Accessed!

Stop!!!!

It's wrong!!

From which Rom do you start (which is the rom you've installed?)
[MDA II, XDA II, 2060 ROM Development] popsi:
I got the T-mobile installed, and want the Qtek one...
[MDA II, XDA II, 2060 ROM Development] spanky:
You should see:

To:

CE Image version: 1.60.00

Extended image version: 1.60.21

Radio version: 1.06.01

Have you follow my instructions???
[MDA II, XDA II, 2060 ROM Development] spanky:
Sorry

There's a mistake in the rom link I've posted

The right rom image is the follow:

ruu16021wwe_dangaard.exe

Download it from the ftp indicated in previous posts
[MDA II, XDA II, 2060 ROM Development] popsi:
But you say you do the changes to the RUU16006WWE_T-mobile_NL.zip Sure you don't mean the Qtek one, since this is what I will install?
[MDA II, XDA II, 2060 ROM Development] spanky:
You'll find the rom here:

http://xdaforums.com/viewtopic.php?t=4857
[MDA II, XDA II, 2060 ROM Development] popsi:
That's what I thought... Good thing I didn't install the modded T-mobile I made 8)
[MDA II, XDA II, 2060 ROM Development] xtinc:
That's what i thought. Now I got it :)
[MDA II, XDA II, 2060 ROM Development] popsi:
Re: Read!How to upgrade from TMobile 1.60 to Dangaard 1.60.2

So here this should be:

ruu16021wwe_dangaard.exe

2) Unpack the zip file, then click with the right button on the extracted file (ruu16021wwe_dangaard.exe, make sure

you've winzip installed) and select extract to. Choose a folder where you'd like to put all the upgrade files
[MDA II, XDA II, 2060 ROM Development] spanky:
yes it is

Now I've correct the original post!
[MDA II, XDA II, 2060 ROM Development] xtinc:
Nice work!! :D

Now is there somebody kind enough to cook a custom extended ROM (taking the best from O2, TMobile and Qtek)? i couldn't do it myself 'coz I do'nt have a Linux box..
[MDA II, XDA II, 2060 ROM Development] Wiz:
Works flawlessly ... after having been a T-Mobile machine, my O2 XDA II now is a Qtek one ... hehehe

Unfortunately this did not eliminate the write protection on my Extended Rom. :(
[MDA II, XDA II, 2060 ROM Development] Jos:
Tried the procedure, but always get this error with xda2nbftool: ERROR:CryptAcquireContext

I'm 100% sure the syntax is correct (cut and paste from your posting).

Any ideas?
[MDA II, XDA II, 2060 ROM Development] spanky:
Bah, it seems a crypt problem

Be sure you exactly write the command line reported in this post
[MDA II, XDA II, 2060 ROM Development] popsi:
Finally! It works perfect, back to Qtek again...

Thanks everyone!
[MDA II, XDA II, 2060 ROM Development] Wiz:
Hmmm .... my GPRS auto-disconnect is gone again in the Dangaard upgrade :(

O2 1.3 no auto-disconnect

T-Mobile 1.6 auto-disconnect

Qtek 1.6 no auto-disconnect

Boys, make your minds up, please ....
[MDA II, XDA II, 2060 ROM Development] Wiz:
By comparing the official Dangaard ROM and the unofficial T-Mobile NL ROM I have figured out the correct settings for auto-disconnect a GPRS after checking e-mail.

I have created two registry files, called remain_connected.reg en auto_disconnect.reg

You can download them in a zipfile from here.

Mind you, you will need a registry editor such as PHM.lu (free) or the one built into Resco File Explorer, otherwise your XDA will not recognize the .reg file format.

Obviously, I cannot accept any responsiblity when things go wrong. Hacking into a registry without knowing what you're doing always is risky. The registry files I published do the trick for me on an O2 XDA II that has been set up with the Dangaard Qtek 1.60.21 rom. I do not know whether this works on i-Mate roms, but I suspect they will. So please make a backup of your machine and/or your registry before you proceed.
[MDA II, XDA II, 2060 ROM Development] adhoc:
Upgrading from tMobile NL rom to french official release

First I wanted to thank spanky for his rom upgrade guide in a nutshell for WWE, and i wonder if someone could be awfuly nice to help me upgrade from tmobileNL 1.60 WWE to the french RUU15801FRA upgrade; <i get the general picture of what has to be done but i'm afraid of blocking my Qtek2020 by doing a mistake and flashing . Could therefore someone be kind enough to post the same kind of guide? thhis would also give another practical example of what has to be done; I hope that quite soon a tool will be developped like the adpatrom to make these things easy as a childs game;

Awaiting impatiently the precise and self explanatory guideto this i remain

Brgds, Adhoc
[MDA II, XDA II, 2060 ROM Development] jehlinger:
Yes, thanks spanky, it worked flawlessly. Is it just me, or does the signal meter seem to update faster with this version? Seems stable so far, I went ahead and let the qtek software load, since it's not much anyway? Anybody see a reason not to?

Personally I don't want GPRS to auto-disconnect, I can do that very easily.
[MDA II, XDA II, 2060 ROM Development] Wiz:
I'd rather have GPRS remain disconnected when idle. Saves quite some battery juice. Besides, since I am moving around quite a lot, I often experienced problems in remaining online when hopping from site to site, so remaining connected is of not much use for me anyway.
[MDA II, XDA II, 2060 ROM Development] jonburge:
I have the t-mobile 1.6 in my i-mate. Can someone please say what advantage the new qteq rom would have other than always on gprs. I would rather not risk frying my unit without some greater benefit. Thank you in advance.
[MDA II, XDA II, 2060 ROM Development] carsa:
sorry...very stupid question...how i prompt MS-DOS from win XP????

hope someone answer

Thanks a lot
[MDA II, XDA II, 2060 ROM Development] Jos:
Lol...

Start->Run->cmd
[Xperia Z Q&A, Help & Troubleshooting] Teknohtc:
Hi, i was wondering if you guys have any nicks or little pieces missing the polyamide frame? When i open the flaps i think my nail digs into the frame and acts like a knife and cuts it. There is plastic underneath the rubber layer of the frame. I wonder what i can use to fill that nick up and bring it back to normal it's actually bugging me. What's your Xperience? and any idea's on patching it up? lol Thanks! :D
[Xperia Z Q&A, Help & Troubleshooting] theindievisual:
if you're a real badass you can use some metal glaze then sand it down till it's flush with the frame again.

but that would take some seriously dextrous fingers.
[Xperia Z Q&A, Help & Troubleshooting] Egan:
Same here a little dent or nick, but nothing to write home about luckily. Hope you can make it acceptable for you again.
[Android Q&A, Help & Troubleshooting] madagascaradam:
Hi, I'm a total noob to Android phones, I admit it. I just got my first smartphone, and it's an old one - an HTC Aria. Thanks to a lot of info here in XDA-developers, I got it rooted with clockwork mod and am using the Cyanogen ROM with Android 2.3 (Gingerbread).

Well, it's such an old phone, I see that it only has ~185 mb internal storage. I added an 8GB SD card. Even though I move my apps to external storage, I can see that the data didn't get moved and is still quickly eating up all the phone's internal storage. I'm trying to use Madmack's "FolderMount" but am having trouble figuring it out. I think it might be an understanding of Android file/folder structure (I have very little). I'm considering buying the "pro" version (if it works for me), just so I can move the whole data folder at once and free up my internal memory again.

Here's my efforts at testing to see if it works. I'm trying to move the data from the "Plague, Inc." game to the external card (the app is already on the external card). So, when I choose source, it automatically starts me in the /mnt/sdcard/ but doesn't allow me to go "up" to any further root folders of that. So I found in the "Android" folder the "data" folder. I tried to FolderMount that but it gave me the error about the non-Pro version. So I tried the "com.miniclip.plagueinc" folder (knowing that it's currently using 15MB of data) and then using an app called SDCardManager (which I understand is supposed to make it easier for me to access my SD Card, like Windows Explorer or something), I made a folder with this path "/mnt/sdcard/foldermount" I think it should be the right path because it's also where my "android.tether" folder is that I know I created myself.

Anyway, when I pair those two folders in FolderMount, it copies stuff over, and the pin looks green, but it shows my internal memory hasn't changed, still almost entirely full. So what do I do to clear it up? I think my problem is in my understanding of the Android's file structure. I think on "source", I should be able to access some folder before "/mnt/sdcard", but I can't get there. Please give this noob help from anyone who can! Thanks!
[Android Q&A, Help & Troubleshooting] madagascaradam:
Can anyone help me with this? Particularly the developer, madmack? I really need to find a way to move the app data to the external memory so I can clear up space. Even if someone could help me understand the file structure better, that'd be helpful. Thanks!
[8.9" Kindle Fire HD Android Development] chmilu:
2.5.0.0 was released, hashcode will update?
[8.9" Kindle Fire HD Android Development] Hashcode:
Yep, I'll run some new recoveries over the next few days.
[8.9" Kindle Fire HD Android Development] bighead2k:
You could just be posting how to do it. Then it is not only you doing the work and being bothered ... ;)
[8.9" Kindle Fire HD Android Development] Hashcode:
It's not always about "run the new build" when it comes to TWRP. In many cases its implementing a new feature, and then running through a basic set of functional tests.

Recovery is supposed to be the last safe haven on the device. Mess it up, and there is much nashing of teeth :)
[8.9" Kindle Fire HD Android Development] Hashcode:
Updated the OP w/ TWRP 2.6.0.0

The download is a .zip file that you can use in your existing version of TWRP to update.

Enjoy
[8.9" Kindle Fire HD Android Development] manchucka:
Hmm. Flashed 2.6.0.0 through TWRP 2.4.4.0, still shows as 2.4.4.0 after reboot.

Edit: had to flash manually the .img

Sent from my mind using magic
[8.9" Kindle Fire HD Android Development] Hashcode:
Gah, had a typo in the .zip file which was causing it to fail to flash.

I've re-uploaded the file to goo.im:

http://goo.im/devs/Hashcode/jem/recovery-zip/zip-kfhd8-twrp-2.6.0.0-recovery.zip

md5sum: d451e4d53a3eee5cec09ec76c6349b8c

(the md5sum shown on goo.im might take a while to update)
[8.9" Kindle Fire HD Android Development] Hashcode:
UPDATED OP with new TWRP release

CHANGELOG for 2.6.1.0:

-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it) [HASH: not enabled for KFireHD's)

-Initial support for f2fs file system formatting (Moto X)

-Update SuperSU install for 4.3 ROMs

-Fixed a permissions bug on files created during backup

-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match

-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible

-Ignore lost+found folder during backup and size calculations

-Various other minor bug fixes and tweaks

** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **

DOWNLOAD:

[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE. IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR KINDLE FIRE HD'S ]

You can download from goo.im here and place on your SDCARD:

http://goo.im/devs/Hashcode/jem/recovery-zip/zip-kfhd8-twrp-2.6.1.0-recovery.zip

md5sum: 762532343cf5168188fc59477ca41e2e

INSTALL INSTRUCTIONS:

While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button)

Select "Install"

Navigate to where you placed the file on your device

Select the .zip filename

Swipe to confirm flash

Reboot
[8.9" Kindle Fire HD Android Development] Hashcode:
Original Post updated for TWRP 2.6.3.0

CHANGELOG for 2.6.3.0:

-Proper backup and restore of SELinux contexts (thanks to Tassadar)

-Pull in some ROM information for backup name generation

-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3

-Add 1200x1920 theme (thanks to Tassadar)

-A few other fixes and tweaks

** THIS IS A FLASHABLE .ZIP FILE FOR INSTALLING IN YOUR CURRENT VERSION OF TWRP **

DOWNLOAD:

[ DO NOT DOWNLOAD ANY FILES FROM TEAMWIN'S WEBSITE. IN GENERAL, THEY ARE MEANT TO BE FLASHED TO UNLOCKED DEVICES AND WON'T WORK FOR KINDLE FIRE HD'S ]

You can download from goo.im here and place on your SDCARD:

http://goo.im/devs/Hashcode/jem/recovery-zip/zip-kfhd8-twrp-2.6.3.0-recovery.zip

md5sum: 566cda87c738b08610f629096d608086

INSTALL INSTRUCTIONS:

While the ORANGE logo is showing on the screen, press and hold the volume up button till the BLUE logo shows. (This is the button farther away from the power button)

Select "Install"

Navigate to where you placed the file on your device

Select the .zip filename

Swipe to confirm flash

Reboot
[8.9" Kindle Fire HD Android Development] CAL7:
The download site gives this md5: bf98ffb363c897ad03e514310fc97c1d (which is also what my kfhd calculates when I download it).
[8.9" Kindle Fire HD Android Development] Bastlwastl2010:
Also here
[8.9" Kindle Fire HD Android Development] Hashcode:
Derp. copy / paste error.

I'll fix in a min.
[8.9" Kindle Fire HD Android Development] blambo:
File not found.
[8.9" Kindle Fire HD Android Development] LinearEquation:
If memory serves, there was an issue with 2.6.3 when it was first released. I won't say if this is the reason the file is missing at the moment or not but the difference's are not so significant that you will have issues by using TWRP 2.6.1.0 For time being just use this one http://goo.im/devs/Hashcode/jem//kfhd8-twrp-2.6.1.0-recovery.img
[8.9" Kindle Fire HD Android Development] Hashcode:
Fixed the link in the OP:

http://downloads.crackflasher.com/s...overy-zip/zip-kfhd8-twrp-2.6.3.0-recovery.zip

NOTE: Eventually goo.im will fix their stuff and I'll probably keep 2 mirrors in the OP.