yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Q&A, Help & Troubleshooting] DutchessDucky:
My nexus 5 is three days old now. This morning when I was reading an article in Chrome my screen started to just freak out. It was clicking links, going back to my app drawer, opening programs, going to Google now, opening (and sending!) emails, hangouts, Google Voice SMS messages, etc.

Thinking it might just be a glitch I did the first troubleshooting step - I turned it off and then turned it back on again. After a few minutes it was glitching again.

When it stopped momentarily I went right ahead and did a hard reset - just in case there was a Virus or something insidious on my phone. Normally I'd hold off on that option, but for this time since I didn't really have anything on the device I figured it was the appropriate course of action. After doing the hard reset and starting up my phone again, within a few minutes it was freaking out again. Luckily, I had the presence of mind to grab my old Galaxy Nexus and take a video recording of what I was seeing:

www [dot] youtube [dot] com/watch?v=6J5ILs-MqjI

Here are the facts:

- The phone is three days old.

- This is the first time that I've noticed this issue, however on day 1 I left the phone on my desk when I went to get some lunch. When I left (and came back) the battery was approximately 70%. Yet, mysteriously, in that 30 minute time frame the unit had shut itself off.

- The phone has not yet been exposed to moisture, extreme heat, or extreme cold. It has not yet been dropped. There are no other indications of manufacturer's defect readily visible.

- The screen is clean

- While having the tantrum, the phone went in and out of airplane mode several times.

- The tantrum occurred both before and after the hard reset. Installed apps weren't even completely downloaded when recurrence happened.

- In another fit, it eventually restarted itself.

Is this a hardware issue? Software issue? User error? Should I initiate an RMA?
[Nexus 5 Q&A, Help & Troubleshooting] FourPointedFreak:
It definitely doesn't look like a user error, seems to prove you're using it fine when you can. This tantrum could be both hardware and/or software. If it were me with such a new device having an issue like this, i'd get a new one. I'd initiate RMA sooner rather than later.
[Nexus 5 Q&A, Help & Troubleshooting] DutchessDucky:
Thanks. I guess with no other defects I just want to make sure it isn't user error or an app I have installed or anything. Seems like a waste to wait another month to get another unit and increasing the chances of it being someone else's refurb.
[Nexus 5 Q&A, Help & Troubleshooting] FourPointedFreak:
Well based on my experience with Google and Nexus devices, typically they'll try hard in your situation to get a you a new device and sooner. They'll probably resell yours as a refurb but issue you a new one.

Fingers crossed.
[Sony Xperia L] ullmapet:
Hello, Xperia L is good phone for gaming. I can play Real Racing 3 without lags, pretty smooth, same as Death Trigger2 on high settings. But any of Gameloft games from Asphalt 8 is not compatible with this phone. Even this phone can run them. It is Asphalt 8, GT racing 2, Thor, and old games from them(Brother in Arms, GT racing academy, etc). Is this because of some HW problem with Xperia L, or Gameloft just f***ing with us?

Sorry for my english
[Sony Xperia L] jokerpappu:
i hav played all game u hav incuded in ur comment.they run smoothly on xperia L bt i also dont understand why gameloft says its not compatible with xperia l
[Sony Xperia L] Sparksys:
gameloft is ****ing with us
[Sony Xperia L] ZN6:
Did you try this method?

http://xdaforums.com/showpost.php?p=46910263&postcount=44

via Tapatalk.
[Sony Xperia L] Rohit@91:
Is it working??
[Sony Xperia L] ZN6:
http://s8.postimg.org/7kce5w811/Screenshot_2013_11_16_16_52_31.png

via Tapatalk.
[Sony Xperia L] siankatabg:
Confirm,its work on my phone too.
[Sony Xperia L] Hnk1:
It's easy if you are rooted. You will only need to change your phone name to C6603 in build.prop and this will do the trick for you.

If you are still confused, I will write a guide in general section for you guys!

Good Luck!
[Sony Xperia L] Rohit@91:
Share build.prop

Can you upload your build.prop? I am rooted with vroot. Am just confused for editing build.prop, never did that.
[Sony Xperia L] Joel16:
You should do that :( cause I'm new to androids and I haven't touched the build prop before so I'm quite worried

Sent from my C2104
[Sony Xperia L] Hnk1:
Replace your build.prop with this one.

You will find it in device/system. Just copy and replace. You can only do it with any explorer with root rights.

This should be used on 4.2.2 and it is ZIP file, so extract it first and then replace it.
[Sony Xperia L] Joel16:
Are you sure there's no harm in that? like perhaps your bootloader is unlockable and mine isn't (Although it is, but this is just an example), Will there be any problems when replacing the build prop?

Other than that Let's say you have a C2105 and I'm using a C2014 and I replaced mine, with the one you provided with the link? is that okay?
[Sony Xperia L] kanaka0907:
Oh man... Thanks a lot... Love you sooo much... At last my problem is solved... Tnx buddy... :laugh:
[Sony Xperia L] Hnk1:
Well, I understand your concern. I bootlooped my device thrice before I got it right.

For me, Build.prop Editor from google play didnot help so I changed it myself. I will suggest you just change one line in your script.

Just change ro.product.device from C2105/4 to C6603. Save your file and then go into apps in settings and clear google play cache .

Restart your phone!

You may do this by build.prop editor or do it manually using a good root explorer (ES file Explorer)

Good Luck! Just backup your data to be safe!
[Sony Xperia L] Joel16:
That went well, haha thanks.
[Sony Xperia L] Hnk1:
The reason was I was writing the wrong name of the device.

I didnot write c6603 but c6605, sgh454 etc. Finally I found c6603 to work. That's all. You mess things up alot and then you finally learn. You should be open to learning!

---------- Post added at 01:08 AM ---------- Previous post was at 12:36 AM ----------

Sorry for spamming you mates, I just made the guide for how to make games compatible for your Xperia L.

I thought you might be interested.

http://xdaforums.com/showthread.php?t=2530022
[Sony Xperia L] siankatabg:
Can't get why you change it to c6603 when "Xperia L" work like charm and its the name of your phone
[Sony Xperia L] Shivam Kuchhal:
I'm very very thankful to you for providing this method. Looks like developers made a mistake regarding the model number of phone that's why no game is compatible. I think we should message Sony and other game developers regarding this confusion.
[Sony Xperia L] Rohit@91:
Your build.prop didn't worked for me. I manually edited my device name to Xperia L and product to taoshan. Now its working.
[Sony Xperia L] Hnk1:
Device name isn't changed in settings but only Google play is forced to believe it's Xperia Z and thus applications are compatible like asphalt 8(not sure now if it is) which weren't before. So it's only to enable full market access which should have been provided by developers themselves.

All that matters is that it works for you now!
[Sony Xperia L] linuxmount:
all new game compatible with xperia l

download new game from othrt app store (no google )
[Sony Xperia L] ullmapet:
For example? I tried Amazons appstore but there is the same problem
[Sony Xperia L] faizur1999:
you won't bootloop your device if u change the right thing on build.prop :D
[Samsung Galaxy S Relay 4G] scopedial:
The Link bellow provides a de-hard-bricking file for the S3.

They appear to be great instructions.

Unfortunately I have a T699. Does anyone have the file for the T699? Mine is most definitely hard-bricked.

Any other de-hard-bricking advice is also greatly appreciated!

Lou

http://xdaforums.com/showthread.php?t=2369125
[Samsung Galaxy S Relay 4G] gee one:
OK, if I follow those other threads, there is a mode to boot the bootloader from an SD card, but you need the stock bootloader? I think those are available from the stock firmware.

How did you hardbrick your relay? No download mode? What happens when you power up with volume down? or whatever the key combination is to get into download mode.

---------- Post added at 10:36 PM ---------- Previous post was at 09:47 PM ----------

OK, after a little research, that debrick image appears to be the modem, sbl1, sbl2, sbl3, and aboot paritions, which appear to be the first 5 partitions on the relay... coincidence?

At any rate, I think the steps are to grab these partitions from a working phone, write them to an SD card, and try booting from in it a bricked phone.

How strong is your linux fu? I think you will need the dd command and something like odin or heimdall to flash the stock images, if this works.
[Samsung Galaxy S Relay 4G] gee one:
I put together a potential debrick file, but I need a bricked relay to test it. I don't want to brick mine to test, however, it appears that you have nothing left to lose. PM sent
[Samsung Galaxy S Relay 4G] Balthasar85:
Even my Relay is "hard-bricked", completely dead, and if I connect it to the PC detects it as "QHSUSB_DLOAD." Even the USB-JIG has changed the situation.

I follow the conversation, I hope you can find a solution.

Keep me posted, thank you very much.

[Swapper 2 bricked my Relay!] - > http://xdaforums.com/showthread.php?t=2504647

CIAWA
[Samsung Galaxy S Relay 4G] scopedial:
Bricking

Man, it is bricked! :crying: The only light is the camera flash that flashes when I insert the battery. No

switched or buttons do anything, no dowload no CWM, nothing.

I was attempting to put the 11/15 nightly of CyanogenMod on it when it happened. Up to this point I was having

problems with the bootloader but I thought I had resolved that. I think I have the stock bootloader at least I think that it

is stock. Maybe it is not and that is what caused this issue.

BTW my Fu is strong. My dd is strong. I have CrunchBang running on an old IBM laptop. If I wipe that I get her going

again in an hour or so.
[Samsung Galaxy S Relay 4G] :
So tell me, just *how did* you brick your phone?
[Samsung Galaxy S Relay 4G] scopedial:
What did it

I was attempting to put a recent build of CyanogemMod on it. I was having problems with my bootloader and I thought

I had fixed it but maybe not :(
[Samsung Galaxy S Relay 4G] scopedial:
Results so far

I have used dd to put the image on the SD card. No problem.

The hard part is the magic key sequence to get into download mode. Nothing appears to be working. I used a 16G card

but I think I will try a 8G card to see if I get a different response.
[Samsung Galaxy S Relay 4G] gee one:
The other thread had something like remove(?) battery, insert SD card, replace battery(?), then turn on. It might be volume down/home/power. I think another post said they had to hold the power button down for several seconds.

I think a 16gb card would be fine, although I think the other thread said it took several write attempts to the sd card. You should be able to see the partitions in the disk utility or gparted. fdisk won't recognize the GUID partition table.
[Samsung Galaxy S Relay 4G] scopedial:
Battery Issue

After trying a number of different actions I decided to check the voltage on my battery.

It appears to be completely drained! Any advice on how to charge it?

I am thinking of cobbling together an adapter and using one of my other phones to charge it or maybe

my hobby/model chargers.
[Samsung Galaxy S Relay 4G] gee one:
Maybe the t-mo store will let you charge it? For other phones, I've used a generic charger, but it was designed for nickel and lithium batteries.

sent while running with scissors
[Samsung Galaxy S Relay 4G] scopedial:
Battery good

I re-checked my battery and it looks like I made a mistake. The voltages are good.

I guess that means that I will be back attempting different button sequences. I will also re-check

the partitions on SD card.

I am also preparing a USB jig just in case this fails also.
[Samsung Galaxy S Relay 4G] gee one:
That image has the modem, sbl 1-3, aboot, and rpm partitions. I'm guessing that is enough to boot to download mode, but I really don't know. Maybe it needs a few more partitions?

sent while running with scissors
[Samsung Galaxy S Relay 4G] scopedial:
Testing update

I think that It may need more.

I have been testing it, on and off, for the last week or so, with no luck.

One good bit of luck is that I have adopted a well used i415 that I can use to charge the battery.

Can I use this to create a recovery SD?
[Samsung Galaxy S Relay 4G] :
Try this thread for a better method of creating a de-brick file http://xdaforums.com/showthread.php?t=2549068

If I get bored I may create and post one
[Samsung Galaxy S Relay 4G] gee one:
The de brick file I posted is missing the tz partition. I'll upload a new one tonight. Hopefully we'll get this to work.

sent while running with scissors
[Samsung Galaxy S Relay 4G] gee one:
I posted a new version of the debrick file to a few testers- if it works, I'll release it into the wild... if not :crying:
[Samsung Galaxy S Relay 4G] scopedial:
Good News

The sweet-sweet smell of success :)

Thank you for the new de-brick file. It finally workd. I had to use volume-down, home and the power button.

I am now in download mode.;) I am going to use Heimdall from my mac again.

But I have to figure out where to go next, what ROM (load, image, whatever) to put on next.

*Update*

I should probably talk my way through this process. Right now I am in download mode, so I am simply assuming that I am going to use Heimdall to place

an "image" in the recovery partition. Is this the correct assumption? The phone was hard bricked and I am now recovering it. What would the best path to take

to recover it? Of course I eventually want it unlocked and rooted.

Should I try a stable release of CM or just the stock T699 image?

'Gain, any advice is appreciated,

Lou
[Samsung Galaxy S Relay 4G] :
Flash the stock jb image before you do anything
[Samsung Galaxy S Relay 4G] scopedial:
T699 Stock Image

I am having a hard time :( locating the stock T699 firmware

Samfirmware has the following message -

Hotfile has been shudown. A download link to Terafile.co will be presented as soon as the firmware is uploaded. We are busy uploading all files to the new host. We apologize for the inconvenience.

If anyone has the stock image available it is appreciated,

Lou
[Samsung Galaxy S Relay 4G] scopedial:
Stock Image Download

Thanks for the stock image. I am downloading it now. I think you are right. I will have to replace the bootloader. I thought that I

had fixed a bootloader problem before all this happened. Apparently I made it worse.:(

I am now getting CM to boot but the SD card has to be in place to do it. Another sign.

Now if I was to use Heimdall to install that image would I do something like ...

heimdall flash --primary-boot debrick_sgh699_v2.img --no-reboot

???

I am still trying to sort out the partitions in my mind.

***update

I am just remembering that Heimdall was not behaving when I tried to use it last.

I was getting "Failed to Initialize Protocol".

However, I did manage to get CWM to work again. Any chance that I can use that to re-install the stock firmware

and repair the bootloader?

Thanks again,

Lou
[Samsung Galaxy S Relay 4G] gee one:
I think it would be something like this:

Depending on how bricked the phone is, you might have to "reformat" which always comes with some warnings. I've never tried it, but it might be something like this:

heimdall flash --reparition --pit [pit filename] --MODEM NON_HLOS.bin --SBL1 sbl1.mbn ... --RPM [rpm filename] .... etc. I think you would need modem, aboot, rpm, sbl1-3 and tz to get to download mode. From there you can flash recovery, boot, img. I'm not sure what this would do to EFS.

I don't recall having too much luck with flashing by partition name, I usually flash by number, although I think the newer version of heimdall fixes this.
[Samsung Galaxy S Relay 4G] scopedial:
no CM but CWM and download

Just for the heck of it I thought I would try to use CWM to apply the stock image.

That wasn't so good. I still have access to download mode but instead of booting into CM I boot straight into CWM.

It is a shame that there are no tools that can validate the configuration of the partitions and/or bootloader of my phone.

I think my focus is going to be getting heimdall to work so that I can at least get a partition mapping of some sort.
[Samsung Galaxy S Relay 4G] gee one:
There is a rooted JB image on the ftp server link I sent you. There is also a goodies file that flashes the modem and other partitions. It might work, depending on what partitions are borked on your phone. Flash them both through cwm.

sent while running with scissors
[Samsung Galaxy S Relay 4G] scopedial:
OK Odin then

I have switched to Odin on my son's PC. I am also using the stock image. The reload appears to being going very well, slow, but well.

I will start over again, but using Odin, if it completes successfully.

***Update

The load of the stock image completed successfully. I can now boot into the stock Android. However, I still need the boot image on the SD card.

Is there anything I can do to take that image and copy it to a partition on the phone? I used dd to dump the image to the SD card, and I now

have a terminal shell on my phone, can't I use the Android dd command to take the image of the SD card and put it into a partition?

Maybe the boot partition? Or maybe some bootloader image that I can put in place using Odin? Since it appears to work with the T699.

Thanks,

Lou
[Samsung Galaxy S Relay 4G] gee one:
The debrick file is a data dump of the first 65MB or so of the internal phone memory. I'm not sure how you borked your phone, so it's hard to figure out what needs to be fixed. I think dumping the debrick image to your phone might work, but it will be a crude solution and could break things even worse. It might be /dev/block/mmcblk0 *maybe* but it will still need a recovery, boot, and system to work, which are in the stock image. The debrick image will overwrite the boot, so write the boot after the debricking image.

Heimdall does spit out partition information with the print-pit option. It will also backup partition information with the download-pit option. I sent you links with the stock pit info. I think using heimdall would be safer. I haven't used odin ever.
[Samsung Galaxy S Relay 4G] :
Your stock image should contain all the partitions you need. Unless you flashed a modified version. You need the *original* stock tar
[Samsung Galaxy S Relay 4G] scopedial:
Fixing the bootloader

I found this article from the "Root Lord" on fixing the Galaxy Y - http://rootlord.blogspot.ca/2013/07/repair-and-unroot-bricked-samsung.html

Can I assume that I can do something similar to fix my bootloader on my T699? Of course I would be using the stock rom that

I have. I have restored just about everything using the "PDA" option but I have not tried the bootloader option, with the stock rom.

I am continuing to have boot up problems in the mean time.:confused:
[Samsung Galaxy S Relay 4G] gee one:
That is odin and I have no clue about it. I did notice that a lot of people in the comments were complaining about no having the bootloader file. The debrick image does contain the bootloader, however it is probably not in a format that odin will accept.

If it were me, I would use heimdall write the partitions.
[Samsung Galaxy S Relay 4G] scopedial:
Yup, I understand. The problem I have is that heimdall isn't working so well (I tried Linux too) with the T699 but Odin is. Actually Odin appears

to be working great with it. I was even using the same USB cable with all three computers.

More later. ;)
[Samsung Galaxy S Relay 4G] scopedial:
*** Update

I used Odin last night with the stock load with no new results. The phone still will not boot without the SD card.

The one interesting thing was that Odin did not like the PIT file that you sent me. Are you able to validate that file for me?

Or is that file only valid with Heimdall? I might go back and try Heimdall again, but like I mentioned earlier, it just is not behaving well.

I really wish there were some diagnostics that I could run to figure out what the problem is. :confused:
[Samsung Galaxy S Relay 4G] gee one:
The PIT file was pulled using heimdall, so it might be in a different format, or lacking headers that odin is expecting. Just to be clear, don't use the text file which is the interpretation of the pit file.
[Samsung Galaxy S Relay 4G] :
So I read somewhere else that once you boot with the sd you can dd the debrick file to /dev/block/mmcblk0 to completely unbrick

dd if=/sdcard/debrick.img of=/dev/block/mmcblk0
[Samsung Galaxy S Relay 4G] gee one:
I think that will work to boot without the sd card, but the debrick file I posted is missing the ROM and maybe even recovery. These can be flashed through heimdall or adb.

sent while running with scissors
[Samsung Galaxy S Relay 4G] chuckiev79:
can you guys please post that link to de-brick file. I just bricked my relay last night. I was an idiot and drunk and tried to flash a kernel from another phone. please please help!
[Samsung Galaxy S Relay 4G] gee one:
If it's just the kernel, you can probably just flash the boot.img. Whatever rom you flashed last will have the right kernel. Just flash it again.

Let me know if that works.
[Samsung Galaxy S Relay 4G] chuckiev79:
phone wont boot into download or cmw or boot at all.

---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------

odin doesnt see it either
[Samsung Galaxy S Relay 4G] gee one:
OK, here's the link http://www.mediafire.com/download/nd22282tn46nr4r/debrick_sgh699_v2.img

As usual, use at your own risk, no refunds, no warranties, no drama. FYI, I sold my relay, so I can't test anything on my end.

If I recall correctly, use a 16gb or bigger sd card, even though the file is only 78M or so. Use dd to copy the file to the SD card. With some magic and a few beers the phone should boot, then use heimdall to restore.
[Samsung Galaxy S Relay 4G] chuckiev79:
thanks man for sure! ill let you know how it goes.
[Samsung Galaxy S Relay 4G] chuckiev79:
Thank you gee one! The file worked like a charm. Not sure how it all worked but it did. I talked to several people about this and none of them had a clue. Xda has soo many members and i can only imagine how many people do these kind of things worldwide, but in baltimore md people look at you like an alien if you talk about roms and kernels. I dont know much yet but hopefully someday. Thanks again!?
[Samsung Galaxy S Relay 4G] chuckiev79:
Strangely enough, however, my relay will not boot without the sd card with debrick file written to it. I have factory data reset and restored backup before all this. Interesting. Any thoughts, by anyone? Not a major deal just curious.
[Samsung Galaxy S Relay 4G] gee one:
My theory is that the partitions on your phone might be a bit messed up. What and How exactly did you flash to get to this state?
[Samsung Galaxy S Relay 4G] chuckiev79:
I used the De brick file and got to downloading mode flashed cwm.tar and then phone booted into current rom as nothing had even happened.
[Samsung Galaxy S Relay 4G] gee one:
oops, I meant how did you brick you phone in the first place. What ROM did you flash that bricked it.
[Samsung Galaxy S Relay 4G] chuckiev79:
Ohh k it was the asci kernel. It read compatible with all cm 11 roms, but it probably only meant for that phone. I deleted the file soi cant remember more than that. And i reflashed jb stock modem and bootloader and phone boots without debrick sd card. This would make a great tutorial.
[Samsung Galaxy S Relay 4G] gee one:
Thanks for the info.