Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Debuggerd error prevented OTA

OP Ch3vr0n

4th June 2014, 11:45 PM   |  #1  
OP Senior Member
Thanks Meter: 30
 
241 posts
Join Date:Joined: May 2009
More
@Chainfire

while trying to sideload ota 443 i encountered the following error

Quote:

/system/bin/debuggerd has unexpected contents

I managed to fix it by flashing the factory system image from 4.4.2. A google search pointed me to http://forum.xda-developers.com/show...2&postcount=43 so a factory reset was not needed

It seems that this is a problem known to using stickmount. Is there anything you can do. I'd really like to avoid this in the future or i might have to swap to a different tool for mounting USB.

I lost root in the process with flashing the OTA but this was quickly fixed by using cf-autoroot and removing the oem unlock line then reinstalling the apk.
5th June 2014, 12:19 AM   |  #2  
Chainfire's Avatar
Senior Moderator / Senior Recognized Developer - Where is my shirt?
Thanks Meter: 55,783
 
9,486 posts
Join Date:Joined: Oct 2007
Donate to Me
More
Quote:
Originally Posted by Ch3vr0n

@Chainfire

while trying to sideload ota 443 i encountered the following error



I managed to fix it by flashing the factory system image from 4.4.2. A google search pointed me to http://forum.xda-developers.com/show...2&postcount=43 so a factory reset was not needed

It seems that this is a problem known to using stickmount. Is there anything you can do. I'd really like to avoid this in the future or i might have to swap to a different tool for mounting USB.

I lost root in the process with flashing the OTA but this was quickly fixed by using cf-autoroot and removing the oem unlock line then reinstalling the apk.


If you install the latest StickMount from a clean setup and are using SuperSU (this is important), it shouldn't happen again.
5th June 2014, 12:29 AM   |  #3  
OP Senior Member
Thanks Meter: 30
 
241 posts
Join Date:Joined: May 2009
More
define clean install? Factory image? Cant do that too much data on it.

In short what i did was

- restore factory 442 system image
- sideload ota
- boot su autoroot (but with the oem unlock line removed as it already is unlocked)
- reinstall SuperSU from playstore

Havent reinstalled stickmount or any similar app yet. With that being said, if i reinstall stickmount will i be safe from this happening again, or do i need to do factory reset?
5th June 2014, 12:46 AM   |  #4  
Chainfire's Avatar
Senior Moderator / Senior Recognized Developer - Where is my shirt?
Thanks Meter: 55,783
 
9,486 posts
Join Date:Joined: Oct 2007
Donate to Me
More
Quote:
Originally Posted by Ch3vr0n

define clean install? Factory image? Cant do that too much data on it.

In short what i did was

- restore factory 442 system image
- sideload ota
- boot su autoroot (but with the oem unlock line removed as it already is unlocked)
- reinstall SuperSU from playstore

Havent reinstalled stickmount or any similar app yet. With that being said, if i reinstall stickmount will i be safe from this happening again, or do i need to do factory reset?

You stated you flashed the stock 4.4.2 image to fix the OTA problem. That means a clean install. Make sure you are using SuperSU and install the latest StickMount version from Play, it shouldn't happen again.
5th June 2014, 01:06 AM   |  #5  
OP Senior Member
Thanks Meter: 30
 
241 posts
Join Date:Joined: May 2009
More
thx for the quick replies. I'll go ahead then and reinstall stickmount then. Dno why it happened in the first place. except root i'm full stock.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes