Develop Bugs

[Q] I need serious help here my phone is broken

I have tried to flash my phone to EB13 new 2.2 Froyo. I have rooted my Epic 4g using the one click method a long time ago and never had a problem. I tried all steps on previous posts (http://forum.xda-developers.com/showthread.php?t=963652) and nothing seems to help. I have done the following to update to 2.2 Froyo:
1) I tried to do the update.zip file method. I went to recovery mode and did as you all stated and would return with errors.
2) I have tried to use the odin method (this is where my phone got broken.)
a) I have done all the steps that you guys posted; and odin would return as failed.
b) In odin i have done the following: (Odin recognizes my phone and i have the yellow box and it uses "com6")
I) made sure that the only box that should be checked is Auto Reboot (i didn't know this until the second time i ran odin so the F. Reset Time was checked by default the first time around)
II) the first time around i only placed this file (SPH-D700-EB13-8Gb-REL.tar.md5) in the PDA box. And it returned with errors. (this is where my phone got broken; i realized it when i tired to turn on my phone to call someone)
III) At this point and time i said screw 2.2 i just want my phone back up and running and tried to do your methods to return to stock using these steps (http://forum.xda-developers.com/showthread.php?t=773032)
IV) it doesn't work at all. I can still go to the Downloading section of the phone doing the #1 and then power button. and at times i can go to recovery mode (when it wants to) but nothing happens. i get these icons while trying to turn on my phone "a phone with a computer next to it"
c) in Odin i have noticed that it takes an extreme amount of time while in the Param.?? (this takes about 8 hours and than returns with a "red fail" in other occasions it gets stuck on "initializing"
d) Odin is not working for me!!!!!!
3) i have also tried the samsung update method (since odin doesn't work for me)
a) i have done all the steps that samsung says and it all passes until i get to the "start download" section.
b) after i press "start download" it stays in idle for a long time than goes to that param.?? and it wouldn't go anywhere and it stayed there for a whole day and nothing ever happened.
Please guys i have had no phone for 2 days now and i need my phone for work and i need my phone by Friday. If there is any help you guys can give me it would be appreciative or else i would have no choice but to go to sprint store and get me a new phone or have them fix this issue and i don't want to be penalized for messing with my phones OS. Please return with suggestions and help me fix this asap.
*Note: My phones Drivers are all installed using you driver download link and i am using Windows 7 64bit.
Thank you in advance!

Try again with a different USB cable. If you are sure you got the drivers installed properly
Sent from my SPH-D700 using XDA App

win 7 64 bit drivers
Here are the drivers I used to Odin my Epic with Win 7 ultimate 64-bit. I put the zip in my google documents.
https://docs.google.com/leaf?id=0B8DFupwiCOXyMGViMDJmY2MtMGU4YS00MGY5LWFkOGItNjkyMDY3MjkyNjgx&hl=en
I used the eb13 from here :
http://forum.xda-developers.com/showthread.php?t=853209
using this tar : Stock EB13 Deodexed EXT4 + CW 3.0.0.6
Also, check your usb connector. there are pins in it that can bend and prevent a good connection. I have read a few posts here on XDA where people had to straighten things out.
Good luck!!

Uh, ouch.
SPH-D700-EB13-8Gb-REL.tar.md5 is not the same file as SPH-D700-EB13-8Gb-REL.tar
Flashing the wrong file is a very good reason why your odin attempt did not work.

I will try this out im having my fingers crossed. Hopefully it works out.
Just to be clear....
I have re-downloaded the 64bit drivers for Win7.
Now in Odin what do i have to put in "PIT"?
Do i use "s1_odin_20100512.pit" for the PIT tab?

Results:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
why is this happening? I did all what u guys requested to do.
I used a new cable

Thank God! Its working!!!!!
All is working well for me Thank you so much guys and special thanks to you jdelano for your help.
My last question...
Is this rooted already?
let me know.
Thank you guys!!!!

So I just tried this because I couldn't get CW3 on my phone without it being all funky. When I would do it before I would have android flashing over the sprint bootup. This only has the android showing. Did I do it right?

Files won't transfer properly

I'm going insane... my Note 2 was working just fine yesterday but today in the afternoon, i began to search the web trying to find a way to get Mass Storage back on the Note 2 perhaps someone out there created a custom app for it. Well i ended up finding one called " SGS3 Easy UMS " everything worked fine though i couldn't transfer to the internal drive. I ejected it from the pc then put it to mount the sd card back to the Samsung .. it said the card wasn't found and it couldn't mount, i managed to get it working again by restarting the Samsung however now i can't transfer files properly to the Samsung. It keeps switch either between the " Cannot Copy Item The device has either stopped responding or has been disconnected " or an strange bug in which you drag a folder or multiple and loads them right away into the phone without showing the transfer bar, if you look into it and check you'll notice folders are incomplete and if you tried to put multiple files it would screw up [ for example a music file played its proper song then suddenly switches to one of the song it was transferred with like they got merged ]
I'm going not nuts nothing im doing is working and no one else seems to be having this problem.
Please someone help....
Thank you in advance for taking the time to read through my issues and i appreciate any help provided.

Obdulio said:
I'm going insane... my Note 2 was working just fine yesterday but today in the afternoon, i began to search the web trying to find a way to get Mass Storage back on the Note 2 perhaps someone out there created a custom app for it. Well i ended up finding one called " SGS3 Easy UMS " everything worked fine though i couldn't transfer to the internal drive. I ejected it from the pc then put it to mount the sd card back to the Samsung .. it said the card wasn't found and it couldn't mount, i managed to get it working again by restarting the Samsung however now i can't transfer files properly to the Samsung. It keeps switch either between the " Cannot Copy Item The device has either stopped responding or has been disconnected " or an strange bug in which you drag a folder or multiple and loads them right away into the phone without showing the transfer bar, if you look into it and check you'll notice folders are incomplete and if you tried to put multiple files it would screw up [ for example a music file played its proper song then suddenly switches to one of the song it was transferred with like they got merged ]
I'm going not nuts nothing im doing is working and no one else seems to be having this problem.
Please someone help....
Thank you in advance for taking the time to read through my issues and i appreciate any help provided.
Click to expand...
Click to collapse
The app you are using is made for a different device. The SGS3 appear similar but aren't actually similar at all by the way they are built. My suggesting is to reflash stock and that will probably solve your issue. Maybe after a few weeks someone might find a way to get mass storage on our device but for now the sgs3 one is instable.

Silent25r said:
The app you are using is made for a different device. The SGS3 appear similar but aren't actually similar at all by the way they are built. My suggesting is to reflash stock and that will probably solve your issue. Maybe after a few weeks someone might find a way to get mass storage on our device but for now the sgs3 one is instable.
Click to expand...
Click to collapse
I reflashed the stock using Odin 3 from the Galaxy Note 2 Toolkit and unfortunately it didn't make a difference i still can't transfer files over properly the issue persists

Obdulio said:
I reflashed the stock using Odin 3 from the Galaxy Note 2 Toolkit and unfortunately it didn't make a difference i still can't transfer files over properly the issue persists
Click to expand...
Click to collapse
That's how I usually use

The new Perseus kernel seems to have fixed this issue for me.

Do you have another micro sd card you could install and find out if the problem continues?
Obdulio said:
I'm going insane... my Note 2 was working just fine yesterday but today in the afternoon, i began to search the web trying to find a way to get Mass Storage back on the Note 2 perhaps someone out there created a custom app for it. Well i ended up finding one called " SGS3 Easy UMS " everything worked fine though i couldn't transfer to the internal drive. I ejected it from the pc then put it to mount the sd card back to the Samsung .. it said the card wasn't found and it couldn't mount, i managed to get it working again by restarting the Samsung however now i can't transfer files properly to the Samsung. It keeps switch either between the " Cannot Copy Item The device has either stopped responding or has been disconnected " or an strange bug in which you drag a folder or multiple and loads them right away into the phone without showing the transfer bar, if you look into it and check you'll notice folders are incomplete and if you tried to put multiple files it would screw up [ for example a music file played its proper song then suddenly switches to one of the song it was transferred with like they got merged ]
I'm going not nuts nothing im doing is working and no one else seems to be having this problem.
Please someone help....
Thank you in advance for taking the time to read through my issues and i appreciate any help provided.
Click to expand...
Click to collapse

i doubt that is the issue since i can't transfer anything even into the internal sdcard, I'll give the Perseus kernel a try.
UPDATE: Been trying to add CWM i hadn't before but during install via Odin3 once it gets to recovery.img it just stays there, the program doesn't crash or anything but it just stays loading recovery.img forever
UPDATE 2: I let it stay loading recovery after a good long while it eventually said "FAIL!"
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> __XmitData_Read ..
<ID:0/006> XmitData Fail..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
UPDATE 2: Note 2 got all screwed up after trying to install the Perseus kernel but the logo still appeared though all screwy.. i nuked the phone and set to back to full stock and got it up and running, then i rerooted it using the Toolkit provided on this site. File Transfers still don't work properly.
UPDATE 3: Uninstalled drivers completely , unplugged phone, reinstalled drivers using Toolkit, replugged phone. File transfers still not working. I'm afraid to try to install the kernel again though admittedly it was first time trying like this .. i had used odin to try and install with pda like the other tar files but thats what screwed up my phone. Im not going to try again since i can't find cleat instructions on how to. For now i'll just use my Samsung Galaxy Media Player 5.0 to transfer files into my external sd card then just switch back to the Note 2.

Easy button for rooted users:
Installing Recovery: Play Store > GooManager > Install custom recovery script
Installing Kernel: Recovery > Install Perseus .zip file
It's disappointing that we have to jump through hurdles to get MTP to work. :/

mrnamster said:
Easy button for rooted users:
Installing Recovery: Play Store > GooManager > Install custom recovery script
Installing Kernel: Recovery > Install Perseus .zip file
It's disappointing that we have to jump through hurdles to get MTP to work. :/
Click to expand...
Click to collapse
At the moment im just transfering stuff in my mircosd from my galaxy media player.. i'll definitely give this a try. Though before i do i just want to let you know that i used the toolkit and the All-one rooting it provides .. it wont conflict will it ?

[ Bump ]
Forgive me for bring this post back but i just want to report that i have successfully flashed Perseus into my Note and it has in fact restored file transfers!
Thank very much to everyone who provided aid. I really appreciate it. ^ ^
UPDATE: N/m .. it was working only for a little while and it soon returned to the whole " The Device has either stopped responding or has been disconnected "
It happened after switched to camera and back to MTP while the usb was still connected.
ugh.. back to square one

[Q] Should I give up on my SGH-T999?

To start out, some basic information. I got my SGH-T999 about 2 years ago and used it for about a year on the Stock ROM before proceeding to root the phone. The firmware version before things when went wrong was android 4.1.2. Everything was working fine until about a few days ago when the phone would stop being responsive after putting it into sleep mode, or the screen will turn black and the whole unit is unresponsive (the latter only occurring while I was in the home screen, not while running any apps. Rather, the phone would be fine while an app is running).
Troubleshoot Stage 1
Initialy, I thought there was some sort of app update that was causing this problem, and so I tried uninstalling a few apps that might have been culprits. Didn't work. On occasion, the phone would freeze up while i was trying to uninstall the app. So reading around, someone mentioned that it was possibly the TouchWiz Home that was acting up and I should, clear cache. So I rebooted into recovery (I had the clockworkmod recovery from the initial root). Cleared user data/factory reset as well as clear cache. Didn't work. At this point, the phone was restarting itself almost instantly after booting into the lock screen. I searched a bit more about why this would happen, and came across a post saying that I could be a faulty power button. I actually didn't want to physically alter my phone in any way, so I decided to try to do something with the software first before resorting to altering the physical phone.
Troubleshoot Stage 2
Next thought process was that maybe somehow an OTA was pushed onto my phone and now the firmware is screwed up because of it. So reading through many posts on XDA, I came upon this thread (http://forum.xda-developers.com/showthread.php?t=1771687) for a pre-rooted version of 4.3. I figured, if I was going to re-flash the firmware, I might as well go to the latest one. I proceed to go through the process of flashing the firmware with Odin 1.85, leaving Auto Reboot and F. Reset Time checked. Odin flashes PASS message and I unplug the phone and wait for the reset. Phone starts up all the way past all the logos and to where the home screen was supposed to be. But there was no home screen, just a black screen with only the pull down menu at the top and a message saying "Unfortunately, Settings has stopped working". This message would keep repeating even after pushing the ok button. Next thought process is, maybe TouchWiz is acting up still. So I boot to recovery, reset/format to factory, clear cache, and reboot. Now the phone wont boot past the Samsung logo. Tried to boot to recover again, phone won't boot to recovery anymore. Tried to re-flash the same exact firmware again and this time, odin had some trouble. It would sometimes stop working where it is loading the main code at which point I check the task manager to see if it is still running processes or utilizing any of the computer resources to communicate with the device. I would then have to unplug the phone and reset by removing the battery. This kept occurring about 2 more times before it successfully finished and on doing so, the original problem when I first flashed it was still there.
Troubleshoot Stage 3
Ok, maybe my phone doesn't like the pre-rooted firmware. Looked around XDA again and found this thread (http://forum.xda-developers.com/showthread.php?t=1949687) and downloaded the stock firmware. I stayed with android 4.3 because i read that I can no longer downgrade to a previous android version. Proceeded to flash the Stock firmware 4.3 using Odin 1.85. The process completed on the first try. SUCCESS!! Boot up phone, got past logo, home screen appeared. SUCCESS!! Here, I thought that I was done and my phone was finally working again. So I begin to tweak the settings for my own preferences. I didn't flash anything else or try to root the phone again. I was just plain using the Stock 4.3 firmware that I got from the thread above. After about 10 or so minutes of using the settings, the phone freezes and becomes unresponsive. Won't restart by holding the power button or return to the home screen with the home button. Only other option was to remove the batter and restart the phone. This time, the phone doesnt make it past the Samsung logo screen, and I can no longer boot into recovery. It was stuck on a boot loop and could only be turned off by removing the battery. It didn't occur to me that I should flash Clockworkmod Recovery to reset/format to factory and clear cache as I have read previously and thought that I could just re-flash the stock again. Nope, the same issue came up in Odin as it did with the pre-rooted firmware. Again, I went through the process of checking that Odin was no longer communicating with the phone before unplugging and restarting the procedures to flash the firmware. After about 3 times, the 4th time after unplugging, the screen that tells you "Firmware upgrade encountered an issue, Please select recovery mode in Kies & try again". And when I try to flash again using odin, I get the following message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Troubleshoot Stage 4
New problem! I now no longer have a PIT partition........and reading around, I found this thread (http://www.sammobile.com/forum/showthread.php?t=15719) of someone who has the same error message coming up in Odin. Thus, I found the PIT file via this thread (http://forum.xda-developers.com/showthread.php?t=1848267&page=4) using the link given by DocHoliday77. Downloaded the T999_16GB.pit as the back panel of my phone indicated that the phone was 16GB. I begin trying to flash with Odin 1.85, checking Auto Reboot, re-partition, and F. Reset Time, including the PIT file and using the Stock 4.3 firmware. This didn't work and only came up with the following error message
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Tried, the same procedure with the pre-rooted 4.3 firmware, still the same message. And haven't gotten past this point since.
Looking back at what I choose to do to try an fix this shutting down problem, I realize there were a few things I could have tried before moving on. But now what I really want to figure out is whether or not my phone can be saved. What have I not tired and what is the end of end to rescue this phone or if its even worth rescuing. I read that JTAG would be the final resort, and I will take that into consideration. Any feedback on what procedures I could've missed would be great as well (for future reference). Thanks for reading this long post and I really do hope I can get this resolved.

I'll try to answer some of this but tbh, tl:dr.
I can very much appreciate a very thorough and detailed post when someone is asking for help. Don't take this the wrong way, but this was a bit much. I could've answered hours ago, but didn't have the time to read it. More importantly though, the majority of people will see how long it is and just close the thread and move on. Like I said, details are good to include, but it gets to a point where it's too overwhelming. Right now I don't even remember a good chunk of what you wrote, and I wasn't able to read it all to begin with.
Not trying to lecture you or anything, but wanted to address it in case it can help you in the future.
I'll try to answer what i can real quick... first, don't use Odin 1.85. That is a very old version. You should only use 3.07 or above. Best to stick with 3.09 or 3.10.
Try the pit file with one of those.
Put the pit file in the pit section and make sure re-partition is checked. Put the firmware in AP. F-Reset time and auto reboot should also be checked, but nothing else.
It does sound a lot like a faulty power switch probably caused all of this. The constant rebooting, crashing and boot looping can and will cause corruption. This is probably what happened to its internal pit. if so, it is very highly likely there is more corrupted data on some of the individual partitions. Depending on which ones, you may or may not be able to fix it without a jtag service.
It is also possible the memory itself could be damaged. If this is the case, the only option is a motherboard replacement. You probably won't know this for sure though unless you try a jtag repair and it fails.
I will say that if the power button is faulty, you should absolutely get that fixed before doing much else. Otherwise it could just bring you right back to where you are now.
If it were me, I would look for a device on ebay with a broken lcd, but a good motherboard with clean imei. Then swap the board. Otherwise it seems to me you'd be spending money on repairs that may or may not work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

Thanks you so very much for the reply! Sorry that it was long and looking at it again, It really is TL: DR. I will keep that in mind for any future posts.
I have tried different versions of Odin 3.04, 3.06, 3.07, 3.09. The first two version also give the same message as version 1.85 while the latter two stall at initializing for more than and hour and there doesn't seem to be any progress. I will try Odin 3.10 and see what happens there.
I guess buying a broken LCD phone would be the best course of action cost-wise afterwards if Odin 3.10 doesn't work. Again I really can't thank you enough for all the help and taking the time to read my post.

Quick tip on buying used devices like that...Be Careful! Pay extra close attention to how every listing is worded. Only buy ones that say things like:
Fully functional except display
Powers on but no picture
Some will try to trip you up by using "clever" phrases, or trying to lead you to assumptions. Also, try to only but from sellers with excellent ratings and a large number of them. They will be more likely to help you if you have a problem.
Good luck!
Sent from my SGH-T999 using Tapatalk

$20 to whoever helps me Unbrick my soft bricked Note 3

Hello Everyone,
I am by no mean a novice in software/hardware repair, however, this Note 3 got me baffled. Not even the Cellphone repair shop was able to flash it, he tried 4.2, 4.3, 4.4 and a PIT file and still couldn't get it. I also tried ODIN 3.07 and 3.09 with a PIT I got from the Heimdall thread with no avail.
I also tried the Heimdall Tutorial and also failed. I have the option to send it to mobiletechvideos but $70 is a bit too much for me right now and they aren't even accepting new orders.
The phone originally freezing so every time it became unresponsive, I would pull the battery out. I have pulled the battery out at least 10 times. Then one time, I pulled it out and put it back in, restarted the phone, then the phone hung at the Samsung Logo.
However I have access to the download mode by pressing PWR + MIDDLE + VOLM DN combo. the following message appears:
ODIN MODE
PRODUCT NAME: SM-N900T
CURRENT BINARY: Samsung Official
SYSTEM STATUS: OFFICIAL
KNOCK KERNEL LOCK: 0X0
KNOCK WARRANTY VOID: 0X0
QUALCOMM SECURE BOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A3, P2
WRITE PROTECTION: Enable
UDC START
Downloading...
Do not turn off target !!
Now, one thing worth mentioning, is when i try to factory reset using PWR + MIDDLE + VOLUME UP, I get the following message:
MMC: mmc_read fail
Movinand Checksum Confirmation Fail
by the way I don't have an SD card in there.
When I hook it up to ODIN 3.09 and try to insert the firmware and PIT file, here the message I get on the phone:
SECURE CHECK FAIL: PIT
ODIN: flash read failure
and on ODIN, it says:
Repartition Operation Failed.
I believe the NAND chip is corrupted and I might need to just get a new Logic board. But its worth a try before I try to shell out $50+ for a new one.
If anyone can help me with this, as in HOLD MY HAND and guide me through this by providing links etc, I have $20 in PayPal ready. If you are in the Orange County, California area, I can drive to you to give you your $20 and i'll buy you a Starbucks Frapuccino. Please help!

Call me a quitter, But I've sold my problem to someone else. Not worth putting more money into the thing. Thanks everyone!

I don't blame you, I Prolly would've done the same thing in that case
Mods need to lock this thread js

Searched Hours Already, Help! Reboot after 25 Seconds

My N910A was stuck in a loop. It would load Andriod 6.0.1, but then after around 25 seconds, it would reset itself.... it would do this continually. I've noticed the top center section of my screen feels significantly warmer than the rest of the phone as this continues.
I tried using ODIN to reflash 6.0.1 and got stuck in a bootloop within the "Android App Optimization" It would make it to object 12 or 13, freeze, and then reboot.
I found the EPH5 Recovery Firmware and successfully flashed it onto the device, but that brought me back to square one of the rebooting after 25 seconds of loading.
The fact that the phone is getting warm leads me to believe something is screwy in the hardware, or something is locking up the processor on boot, and causing it to overheat.
I was able to get into the About Phone menu and noticed something odd - many of the objects had values of "unknown". My Phone Number, IMEI, IMEISV, IMS Reg (Not Registered), IP Address (Unavailable)
It's running a security patch from Aug 1, 2016 if that is needed for any diagnostics.
I don't know much about ODIN, but found a detailed write up what-is-odin-and-how-to-use-full-guide and chose to tick "Re Partition" when I flashed a firmware with a PIT file to ensure something wasn't corrupted in the file system.
I also read that when the IMEI shows unknown, it will wipe all settings files and create new, clean ones, so I ticked EFS clear.
Also, when I used a specific BL file to flash, I ticked "Phone BL Update" to clear out the old settings and reinitialize the new ones.
NOTHING I am doing is fixing this restarting issue though. I can barely make it through the About Phone menus to see the information.
I've literally searched for around 4 hours, downloaded about 16 different firmwares, and flashed a dozen times.... I've tried doing this on my own, and now I'm reaching out for an answer I'm sure is somewhere I haven't found yet.
Please help.

FWIW, I've also tried 3 different batteries as that seems to be a large suggestion for troubleshooting. All have the same result, so the issue is definitely with the phone.

Word for word
Started messing with this note 4 and word forword experienced the same issue you did. Did you notice though if you booted into recovery or download mode the phone will remain cool and run all day as long as you post pone the android os from booting? Then Samsung refuses to continue servicing this model? Sounds to me more like corporate greed rather than human error guys.
Ps seems like the oldest virus in the book. Continuously opening notepadbwindow after window until the hardware juat gives in and crashes. Or a kill system scriptbwith a random timer vatiable and overclock parameter. That's what i would do if i were them