Constant reboots after Stagefright Patch

N7 2013 WiFi model sitting on my bed stand reboots every couple hours in standby. It's not rooted and nothing sideloaded... anyone else having this problem?

Constant BSOD and restart, BUGCODE_USB_DRIVER Error. Help!

I installed Windows 10 a few days ago. Since then, my computer regularly restarts and says it's because of a BUGCODE_USB_DRIVER error. This seems to only be a problem when I have my wireless keyboard and mouse attached through a wireless USB device. I have a Microsoft sculpt comfort keyboard and mouse.

So far, I've:

• Uninstalled and reinstalled all USBs.


• Updated all of my drivers.


• Completely reinstalled Windows 10.


• Updated the computers BIOS.

I thought the last step resolved the issue as I was able to use my wireless mouse and keyboard for roughly three hours before my computer restarted itself. . Please help. This is driving me insane, and I need this computer to work, among other things. Here's my system information and a crash dump analysis

System Information (local)
computer name: MASTER-PC
windows version: Windows 10 , 10.0, build: 10240
windows dir: C:\WINDOWS
Hardware: 10249RU, LENOVO, Emerald Lake
CPU: GenuineIntel Intel(R) Core(TM) i5-2430M CPU @ 2.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8499900416 total


Crash Dump Analysis
Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Fri 8/14/2015 1:10:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-16765-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE000F505A410, 0xFFFFE000F5A3DB10, 0xFFFFE000F8261A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Fri 8/14/2015 1:10:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: usbport.sys (USBPORT!USBPORT_GetHciMn+0x1096B)
Bugcheck code: 0xFE (0x4, 0xFFFFE000F505A410, 0xFFFFE000F5A3DB10, 0xFFFFE000F8261A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Thu 8/13/2015 9:48:56 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-17750-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE0001F817560, 0xFFFFE0001F37FA50, 0xFFFFE00020D1CA0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Thu 8/13/2015 9:19:10 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-17703-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001F2DA49D0, 0xFFFFE001F3C0EAE0, 0xFFFFE001F50C34DC)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Thu 8/13/2015 9:07:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-22093-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001A0CEEB60, 0xFFFFE001A2070470, 0xFFFFE001A201344C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

On Thu 8/13/2015 8:16:29 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump1315-40312-01.dmp
This was probably caused by the following module: usbport.sys (USBPORT+0x3000B)
Bugcheck code: 0xFE (0x4, 0xFFFFE001E199DCF0, 0xFFFFE001E24BCA90, 0xFFFFE001E68E1A0C)
Error: BUGCODE_USB_DRIVER
file path: C:\WINDOWS\system32\drivers\usbport.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: USB 1.1 & 2.0 Port Driver
Bug check description: This indicates that an error has occurred in a Universal Serial Bus (USB) driver.
The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time.

Stock recovery constant error, downgraded ROM and updates won't show

Hey y'all, I was on 2.19.40.22 rooted with one click root and successfully applied last week's update to 2.20.40.58 and kept root.
I tried to update to 2.20.40.59 and my phone got all sorts of ****ed up. So I successfully formatted and wiped everything and downgraded to pre-rooted 2.19.40.18 (also downgraded boot/droidboot/stock recovery). After unrooting SuperSU so I'd have a fully stock ROM, I tried updating. That got botched.

So I wiped everything again (including internal storage/data) and fully installed 2.19.40.22 and now my phone sees no updates from ASUS pending and every time I try to enter stock recovery, it just plays like it's trying to apply an update and then throws up the error message. This happens without any OTA update zips in internal storage to trigger recovery to try to apply an update.

I've also tried the other manual way to update (the method other than MOFD_SDUPDATE) and my phone will try to apply the update then displays the same error message again.

I'm at the my wits end having tried everything I can think of, have spent the better part of 6hrs ****ing with my phone. Anyone have any insight?

G900f Water Damage - Constant Reboots with a twist

Hi All

I recently took my Galaxy S 5 on holiday and got it wet at a hotel pool. Water got into the phone due to prior drops which must have resulted in the seal being broken. You could see water had got behind the screen in the top right and top left corners. The phone will no longer detect my SIM card, but is otherwise sort of OK to use.

Cutting to the chase then, the phone reboots constantly if left on, but only if I am not actively using it. If I listen to music (Spotify, PowerAmp) or generally just use the phone it doesn't reboot. Also, I can leave it in Download mode or within the TWRM options and it stays on no problem.

Does anyone have any idea then if there is something within Android that's kicking the phone into a sort of boot loop, since the other modes are fine?


Thanks in advance for any help on offer

[TIP] Solve SW2's constant conecctions-disconnections [ROOT].

Well guys, I have a short tip to solve that common problem on the SW2 (as far as I read). I have only tried it on my smartphone, but it worked and you could try just in case. You´ll need root for this. Don't worry, if it doesn't work for you, you can go back to normal easily.

In my case, my phone killed the smartwatch service and then it "revived". So I put the Low Memory Killer (LKM) (not sure if is that the English name, in Spanish it's called "Prefijos de Limpieza de Memoria") into a lower value that it had (depends of the phone). After that, my disconnections problems disappeared :D
To change it, I recommend use Kernel Adiutor, an awesome kernel tweaker.

I hope this works for you. Tell me your results. Peace :)