Develop Bugs

[SOLVED] Custom Recovery Mounting Problem

Im unable to connect to usb while in recovery because I can't find the drivers. I've installed every drivers I could find and no go. I tried also switching ports and no matter what the driver isnt found and it prevents me from running scripts like the auto debloat because my device cannot be found. im running stock rooted Help!

Did you enable USB debugging?

tonymtl said:
Did you enable USB debugging?
Click to expand...
Click to collapse
Yeah

Why in recovery mode? You can run it booted to ROM.

tonymtl said:
Why in recovery mode? You can run it booted to ROM.
Click to expand...
Click to collapse
well the auto debloat i found needed to be used in cwm. While I would appreciate if you can point me to and alternate solution; I still need figure this out to avoid future mishaps.

I mean you should be booted to ROM with USB debugging on and run it, it will auto reboot to recovery.

tonymtl said:
I mean you should be booted to ROM with USB debugging on and run it, it will auto reboot to recovery.
Click to expand...
Click to collapse
ah gotcha. well I did but when i get to recovery my computer is asking for a driver that cant be found and i have no idea why. the script says that the "device is not found" and im pretty sure this is why. thanks for the help btw

Plug in your phone to PC, it will show locate drivers recommended, leave it.
In Windows go to control panel/system/device manager you'll see one with yellow "?" mark right click on it and update driver software>browse my computer for driver software >let me pick from list>pick Samsung android ADB interface. That should do it.

tonymtl said:
Plug in your phone to PC, it will show locate drivers recommended, leave it.
In Windows go to control panel/system/device manager you'll see one with yellow "?" mark right click on it and update driver software>browse my computer for driver software >let me pick from list>pick Samsung android ADB interface. That should do it.
Click to expand...
Click to collapse
you hit it on the nose. thanks man. now the next problem. all the apps were not found on the debloat script. smh. 1 down 1 to go. many thx

I believe that script was written for international gs3. You can download root browser and manually delete apps you don't like.

tonymtl said:
I believe that script was written for international gs3. You can download root browser and manually delete apps you don't like.
Click to expand...
Click to collapse
yeah i just read about it. what a bust. big help man.

Recovery Mode?

Ok, so here's what happened.
When I got my ouya, the first thing I did was root it and set up Wireless adb. I noticed that when I had adb running over wifi though, it would disable my micro usb port for some reason, and I couldnt copy anything to the device while I had debugging enabled.
Long story short, I disabled adb to copy some files, and I accidentally replaced the launcher while trying to get GAPPS working. Unfortunately whatever launcher overwrote the ouya one doesnt work, and just force closes on boot.
Does anyone know of a recovery mode for the ouya? Most phones require holding down the power button as well as one of the volume buttons, but the ouya doesnt have any volume buttons.
I opened the case, and didnt see any switches or jumpers either.
I even tried using a usb keyboard and holding down the volume buttons on it out of desperation haha.
Is it possible to get Clockwork Mod booting from USB or something?

with wireless adb, if you disconnect from it by closing the cmd window, you need to type adb usb to re-enable the usb mode
its okay if the launcher fails as long as it still boots and you get into android, you can turn on adb again and just re-install stock launcher. I'll attach it in an sec

Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk

Paulenski said:
Wanted to mention, you don't need to root (already rooted), I wouldn't suggest flashing any random recovery, it needs to get made for it first(eventually gonna happen soon).
I would suggest deleting/uninstalling whatever launcher you tried installing. Because the launcher they used is built with the framework so you need to do more work to get an third party launcher to work correctly.
First:
adb install Pathofapk\OUYALauncher.apk
Second:
adb shell
su
cd /data/app
ls (get the name of the launcher that's FC)
rm name.apk
Click to expand...
Click to collapse
Thanks for attaching the launcher. I hopefully will be able to use that soon. Unfortunately, I disabled USB debugging in the Developer options on the Ouya itself.
I tried running your command (adb usb) and it tells me that no devices were found. I tried doing 'adb connect x.x.x.x' as well, but since USB debugging is disabled, it won't connect that way either.
Thanks for the suggestion though. Do you have any other ideas?
I have this samba app installed, and I was hoping i could access root through that, but I can only figure out how to access the sd card.
I also have airdroid and es file manager installed if there are any exploits to get those running.
Thanks for any help offered

Check this command
adb devices
does it even show up on the list?

Paulenski said:
Check this command
adb devices
does it even show up on the list?
Click to expand...
Click to collapse
i tried it, but it doesn't show up. I also checked device manager to see if it came up it there but all I get is an mtp device. I also copied the hardware id from that device and added it to the adb driver and reinstalled it that way, but it still does not show up in adb devices.
just to clarify, the mtp has a different hardware id than the adb mode one. When I did adb TCP originally, it disabled my micro USB port from mtp access, so I could not transfer files. That's why I had to disable USB debugging on the ouya. I'm afraid adb is doomed to not work until we can figure out how to get a USB bootable recovery image.
thanks for the suggestions I really appreciate it
any other ideas? I have been toying around with samba a little. I noticed that there is a share named admin$ but it doesn't work with the password I set up for the other share. Does anyone know what the default root password is for samba? If this will let me access the system folder, I can dump the launcher back in through samba.... Probably a long shot though.

https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem

Paulenski said:
https://devs.ouya.tv/developers/docs/setup
Did you follow that? If you don't do the echo command, it won't work on usb adb.
If you have Skype or GTalk, let me know, we can talk on there to try and remedy your problem
Click to expand...
Click to collapse
I have PM'd you.
I double checked, and made sure to do the echo command. Still no dice.

Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
This is the process:
HOW TO RECOVER:
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse
check out the thread here: http://forums.ouya.tv/discussion/1380/recovery-mode
Thanks for all the help here guys! I am glad to be running again

darthcircuit said:
Just as an update, MBM on the ouya dev forums posted how to get into the recovery mode of the console if anyone is interested. I was able to get my ouya running again with his help.
Click to expand...
Click to collapse
Glad it helped.
- mbm

[Q] ADB works, but no MTP/PTP functionality

So I got my Nexus 7 2013 to work perfectly on my laptop, which runs Windows 7 x64. However, on my desktop, which also runs Win7 x64, I only have the ADB working correctly for the N7. As I recall, sometimes there is a device under Device Manager called "D:/", which is non-descriptive, but seems like the closest thing to the N7. I have tried to update this mysterious device's drivers by pointing to Google's USB drivers and the OEM drivers, but neither was accepted. There are also no devices with missing drivers listed in Device Manager.
At this point, I am not sure how to proceed. Is there a precise way identify under what device name/category the N7 shows up in Device Manager? Please advise. :fingers-crossed:

See if this helps:
http://forum.xda-developers.com/showthread.php?t=2391236

Cool, I'll give this a try in a bit.

zeppelin101 said:
Cool, I'll give this a try in a bit.
Click to expand...
Click to collapse
I cant get Nexus 7 to show has folder when check in MTP mode. it will show as camera folder PTP. Any solutions to this problem? very frustrating!

mickrg123 said:
I cant get Nexus 7 to show has folder when check in MTP mode. it will show as camera folder PTP. Any solutions to this problem? very frustrating!
Click to expand...
Click to collapse
Make sure USB Debugging is disabled, device is plugged in, and go to device manager in windows. Then right click on nexus 7 or android adb device, or any similar name. Then after uninstalling everything, unplug device and replug it in. Let windows get the drivers, and MTP should work!

fevanson said:
Make sure USB Debugging is disabled, device is plugged in, and go to device manager in windows. Then right click on nexus 7 or android adb device, or any similar name. Then after uninstalling everything, unplug device and replug it in. Let windows get the drivers, and MTP should work!
Click to expand...
Click to collapse
Thats my problem it doesn't when trying this.

mickrg123 said:
Thats my problem it doesn't when trying this.
Click to expand...
Click to collapse
get this and delete anything related to google and adb.
http://www.nirsoft.net/utils/usb_devices_view.html

fevanson said:
get this and delete anything related to google and adb.
http://www.nirsoft.net/utils/usb_devices_view.html
Click to expand...
Click to collapse
Deleted everything related to google and nexus. Still installs as adb device but doesnt show as nexus 7 device! Wug fresh has this program in its tool kit

It might sound dumb, but I was literally just having this issue. But apparently certan roms or kernel disable MTP mode when they are installed. i reinstall every driver just now. My fix was as easy as going to Settings > Storage > Menu Button Top right > Enable MTP box.

tonu42 said:
It might sound dumb, but I was literally just having this issue. But apparently certan roms or kernel disable MTP mode when they are installed. i reinstall every driver just now. My fix was as easy as going to Settings > Storage > Menu Button Top right > Enable MTP box.
Click to expand...
Click to collapse
What kernal or rom are you running?
---------- Post added at 10:10 PM ---------- Previous post was at 10:02 PM ----------
mickrg123 said:
What kernal or rom are you running?
Click to expand...
Click to collapse
Going to try a custom rom see if that works!

I have tried a number of the suggestions in this thread, including the deletion of all my google/adb/nexus (and samsung) drivers. None of these steps resolved my problem. However, at the end of the day, I can still use both ADB and MTP, just not at the same time. So it's not a big deal. I think I will mess around with Tasker and/or get a widget for turning ADB on/off.

Are you ale to get a nexus 7 device to show so you can access internal storage? I can only access camera storage.

mickrg123 said:
Are you ale to get a nexus 7 device to show so you can access internal storage?
Click to expand...
Click to collapse
Yea, that's what MTP is.

zeppelin101 said:
Yea, that's what MTP is.
Click to expand...
Click to collapse
That's my problem I can't access mtp.

mickrg123 said:
Are you ale to get a nexus 7 device to show so you can access internal storage? I can only access camera storage.
Click to expand...
Click to collapse
Are you running stock?
If so, do you have USB debugging turned on?
If you have USB debugging turned on, the USB IDs change and it might not (depending on what you have previously installed) recognize the MTP device anymore.
If you turn off USB debugging, it should recognize MTP.
Now if you are on a custom ROM, there might be some issues on the ROM side causing the MTP problem. Try going back to stock and see if it works.
If you are on stock and have the case where MTP only works with USB debugging disabled, then you can try this driver inf I put together to address that.
It is available in this thread:
http://forum.xda-developers.com/showthread.php?t=2391236

Need help getting ADB to work

I apologize if this has been gone over already, but I searched and have not found a solution. I have a Verizon m8 and would like toy around with a custom ROM. I got weaksauce to achieve root, but cannot get s-off or TWRP because I cannot for the life of me get ADB to work, It just won't recognize my device. I have Windows 7 and I feel that it may be a driver problem. I downloaded HTC Sync manager but it won't recognize the device either. I've called HTC and they have not been much help just want me to use AirDroid. Anybody have any suggestions to what I might try? Thanks a bunch in advance, I really like the phone but would like to make a few changes if I can.

Is the USB debugging on your phone enabled ? It is needed for ADB to work.
and you need at least ADB version 1.0.31

Try to uninstall and re-install HTC Sync. Also there are some "minimal" HTC drivers around XDA which folks sometimes have better luck with. Try different USB ports, and make sure its a direct link (no USB hub, etc.). You might even have to try a different computer.
---------- Post added at 01:00 PM ---------- Previous post was at 01:00 PM ----------
ckpv5 said:
Is the USB debugging on your phone enabled ? It is needed for ADB to work.
Click to expand...
Click to collapse
This is also a good point. Seems silly and obvious. But I forgot myself, when doing root, S-off on this phone.

ckpv5 said:
Is the USB debugging on your phone enabled ? It is needed for ADB to work.
and you need at least ADB version 1.0.31
Click to expand...
Click to collapse
Oh yeah, yes USB debugging is enabled. Thanks for the reminder.

redpoint73 said:
Try to uninstall and re-install HTC Sync. Also there are some "minimal" HTC drivers around XDA which folks sometimes have better luck with. Try different USB ports, and make sure its a direct link (no USB hub, etc.). You might even have to try a different computer.
---------- Post added at 01:00 PM ---------- Previous post was at 01:00 PM ----------
This is also a good point. Seems silly and obvious. But I forgot myself, when doing root, S-off on this phone.
Click to expand...
Click to collapse
I've tried unistalling and reinstalling HTC Sync. Its plugged directly into my computer and I've tried different ports

Means that your PC device manager doesn't show Android USB devices and My HTC under it ? Any yellow unknown device there ?
Something like this
View attachment 2883823
If no, then that's driver issue

ckpv5 said:
Means that your PC device manager doesn't show Android USB devices and My HTC under it ? Any yellow unknown device there ?
Something like this
View attachment 2883823
If no, then that's driver issue
Click to expand...
Click to collapse
My device manager does not show any Android usb devices. It shows up under portable devices though

I remember that I have this problem before long long time ago ... never expect the latest HTC sync doesn't fix it.
Here is the steps : http://forum.xda-developers.com/showpost.php?p=28963569&postcount=171
and http://forum.xda-developers.com/showpost.php?p=28965062&postcount=173
Here are the drivers
Hopefully this helps and you can manage it .. bed time for me here

ckpv5 said:
I remember that I have this problem before long long time ago ... never expect the latest HTC sync doesn't fix it.
Click to expand...
Click to collapse
Yes, you would think such a thing would be more consistent by this point. You wouldn't expect it to be rocket science, but USB connectivity on HTC devices tends to be more problematic that you would think. For me, adb and fastboot worked perfectly out of the box, but my M8 would not mount internal storage to my Windows 7 PC. That was on my home computer. On my work laptop (also Win 7) it mounted internal storage just fine.

ckpv5 said:
I remember that I have this problem before long long time ago ... never expect the latest HTC sync doesn't fix it.
Here is the steps : http://forum.xda-developers.com/showpost.php?p=28963569&postcount=171
and http://forum.xda-developers.com/showpost.php?p=28965062&postcount=173
Here are the drivers
Hopefully this helps and you can manage it .. bed time for me here
Click to expand...
Click to collapse
Thanks guys. Really appreciate it. Looks like I got it working, I'm able to use adb commands now. Now I'm trying to achieve s-off and can't get firewater to run. I get to the last step /data/local/tmp/firewater and nothing happens. Any ideas. Thanks again, I really appreciate the help.

[Q] E980 bricked - Computer says "unknown device" - Only boots into Recovery and DL

[Q] E980 bricked - Computer says "unknown device" - Only boots into Recovery and DL
My wife somehow managed to bork her Optimus G Pro. She was running rooted stock, and the phone ended up somehow booting to CWM. She said she "picked a few selections", and the phone won't get past CWM now.
I can't do the mobile flash tool because every time I connect the phone, it somes up as Unknown Device. This is after I updated the drivers on both computers. Tried various ports & USB cables, same thing. MY E980, by the way, shows up fine in Device Manager.
I've tried restoring a previous backup, but it still boots right back to recovery. For some reason, the phone doesn't recognize the external card, or I would have tried making a backup on the other phone with the bootloader included, but I have no way of getting it onto the broken phone, unless I can push it via adb somehow.
Anyway, I appreciate any help anyone can give

ixijimixi said:
My wife somehow managed to bork her Optimus G Pro. She was running rooted stock, and the phone ended up somehow booting to CWM. She said she "picked a few selections", and the phone won't get past CWM now.
I can't do the mobile flash tool because every time I connect the phone, it somes up as Unknown Device. This is after I updated the drivers on both computers. Tried various ports & USB cables, same thing. MY E980, by the way, shows up fine in Device Manager.
I've tried restoring a previous backup, but it still boots right back to recovery. For some reason, the phone doesn't recognize the external card, or I would have tried making a backup on the other phone with the bootloader included, but I have no way of getting it onto the broken phone, unless I can push it via adb somehow.
Anyway, I appreciate any help anyone can give
Click to expand...
Click to collapse
If the message you are referring to is one that pops up using a windows computer. I have seen it most of the times I have flashed back to stock. Unknown device, device can't be recognized, something not installed, etc. Carrying on with the restore method even so has also worked every time.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
Return to stock method: http://forum.xda-developers.com/showthread.php?t=2420219

abumy said:
If the message you are referring to is one that pops up using a windows computer. I have seen it most of the times I have flashed back to stock. Unknown device, device can't be recognized, something not installed, etc. Carrying on with the restore method even so has also worked every time.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
Return to stock method: http://forum.xda-developers.com/showthread.php?t=2420219
Click to expand...
Click to collapse
Yep, that's the message. I'm running Windows 7.
I'll give it a shot when I get home, but without the device showing up in the com port section of device manager, I can't change the phone over to port 41, right?

I have a TWRP backup from my other E980 that I included the Bootloader option in the backup. Is there any way to push that to the phone using ADB?

I don't know if OP has the same problem as mine. My phone just keep boot into CWM all the time. No matter which rom I flash.
And I Finally found a method to solve this problem, please look here:
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
It salve my phone and I don't have to use the LG tools
@ixijimixi

laofan said:
I don't know if OP has the same problem as mine. My phone just keep boot into CWM all the time. No matter which rom I flash.
And I Finally found a method to solve this problem, please look here:
http://forum.xda-developers.com/showpost.php?p=49370751&postcount=70
It salve my phone and I don't have to use the LG tools
@ixijimixi
Click to expand...
Click to collapse
Reading that post, it sure seems like what I'm going through. I'll have to give it a shot tonight. Either way, thanks for the response. This thing has me pulling my hair out.

ixijimixi said:
Reading that post, it sure seems like what I'm going through. I'll have to give it a shot tonight. Either way, thanks for the response. This thing has me pulling my hair out.
Click to expand...
Click to collapse
before you boot into system, make sure you already have one system installed( I did once wipe system and fogot to install a rom..)
At least that post is working for me! Now I am using TWRP,

laofan said:
before you boot into system, make sure you already have one system installed( I did once wipe system and fogot to install a rom..)
At least that post is working for me! Now I am using TWRP,
Click to expand...
Click to collapse
No luck with that post. Followed every step on two different computers, but neither computer will recognize it (keep getting that "unknown device" error in windows).
I saw a post somewhere that someone had luck formatting their system drive in Recovery, but that seems a little bit drastic to me. I'll probably try uninstalling and reinstalling all the drivers again first. And more swearing. LOTS more swearing...

ixijimixi said:
No luck with that post. Followed every step on two different computers, but neither computer will recognize it (keep getting that "unknown device" error in windows).
I saw a post somewhere that someone had luck formatting their system drive in Recovery, but that seems a little bit drastic to me. I'll probably try uninstalling and reinstalling all the drivers again first. And more swearing. LOTS more swearing...
Click to expand...
Click to collapse
Did you install LG driver in those two computer?
That post has cover issues when device is not recognized. If that doesn't help, you need to go back to stock using files in the General section

I'm also having the same problem. Can I run those adb commands on a Ubuntu machine?

ixijimixi said:
No luck with that post. Followed every step on two different computers, but neither computer will recognize it (keep getting that "unknown device" error in windows).
I saw a post somewhere that someone had luck formatting their system drive in Recovery, but that seems a little bit drastic to me. I'll probably try uninstalling and reinstalling all the drivers again first. And more swearing. LOTS more swearing...
Click to expand...
Click to collapse
try this one, use the TWRP method. ( I got into recovery bootloop again today, my computer could not see my phone at all. And I accidently press continue on OTA... f**k, then phone run into recovery for 2 hours.)
This method help me out even when computer could not see your device.
http://forum.xda-developers.com/showthread.php?t=2451696

laofan said:
Did you install LG driver in those two computer?
That post has cover issues when device is not recognized. If that doesn't help, you need to go back to stock using files in the General section
Click to expand...
Click to collapse
Right, but if my computer isn't connecting to my phone (except to show it as an "Unknown Device"), and ADB isn't connecting, and none of the recoveries see the ext. SD card, how do I get the files across?

laofan said:
try this one, use the TWRP method. ( I got into recovery bootloop again today, my computer could not see my phone at all. And I accidently press continue on OTA... f**k, then phone run into recovery for 2 hours.)
This method help me out even when computer could not see your device.
http://forum.xda-developers.com/showthread.php?t=2451696
Click to expand...
Click to collapse
Holy crap...that idea with the TWRP terminal command got me up and booting! So glad that I kept TWRP on there!
For some reason, it's still not reading either the SD card or recognizing the device on USB, but at least this is progress, and at least I can run the thing.
*update* and now it seems to be reading the SD card. At least with that and wifi, I'll be able to move files to/from the phone. I'm going to try reinstallng drivers. With all the reinstalling, uninstalling, and swearing I've done lately, I think there's a good chance that'll work.

ixijimixi said:
Holy crap...that idea with the TWRP terminal command got me up and booting! So glad that I kept TWRP on there!
For some reason, it's still not reading either the SD card or recognizing the device on USB, but at least this is progress, and at least I can run the thing.
*update* and now it seems to be reading the SD card. At least with that and wifi, I'll be able to move files to/from the phone. I'm going to try reinstallng drivers. With all the reinstalling, uninstalling, and swearing I've done lately, I think there's a good chance that'll work.
Click to expand...
Click to collapse
well You should owe me 8 thanks hit for saving your phone..:fingers-crossed: LOL
I would also recommend reinstall drivers, then reboot computer( it is important), and try different USB ports on your PC. my computer just won't recongize my phone on one port, but it does on the other. God knows why...

laofan said:
well You should owe me 8 thanks hit for saving your phone..:fingers-crossed: LOL
I would also recommend reinstall drivers, then reboot computer( it is important), and try different USB ports on your PC. my computer just won't recongize my phone on one port, but it does on the other. God knows why...
Click to expand...
Click to collapse
Heheheh, yeah, I was going to, but then I read your previous sig. Perfectly happy to ignore.
My google-fu failed me major league on this mess. I'm just hoping it's not a busted USB port on the phone.

ixijimixi said:
Heheheh, yeah, I was going to, but then I read your previous sig. Perfectly happy to ignore.
My google-fu failed me major league on this mess. I'm just hoping it's not a busted USB port on the phone.
Click to expand...
Click to collapse
Try different USB ports on PC. When my PC could not see my phone, I also panic and thinking that the USB port on the phone goes wrong.
Then I switch the port which my mouse is usually hook up. Bang! Windows is installing driver and few seconds Iater I was accessing the files on the phone.
Just give it a try.
My signature is just for fun...Emm, I should change it to " hit thanks twice if you like my post "..

laofan said:
Try different USB ports on PC. When my PC could not see my phone, I also panic and thinking that the USB port on the phone goes wrong.
Then I switch the port which my mouse is usually hook up. Bang! Windows is installing driver and few seconds Iater I was accessing the files on the phone.
Just give it a try..
Click to expand...
Click to collapse
Well, I'm out of ports to try on my work computer. I'll try on my home computer later on. It didn't read it last night...but then again, the phone wasn't booting last night either
My signature is just for fun...Emm, I should change it to " hit thanks twice if you like my post "..
Click to expand...
Click to collapse
"Hit the thanks button like a rat pressing a lever for a nugget of food, thanks"