5,597,397 Members 30,791 Now Online
XDA Developers Android and Mobile Development Forum

Req: file - System/bin/debuggerd

Tip us?
 
gurudev32
Old
#1  
gurudev32's Avatar
Senior Member - OP
Thanks Meter 163
Posts: 110
Join Date: May 2011
Location: Bengaluru
Default Req: file - System/bin/debuggerd

Tried updating from 4.2.1 to 4.2.2.
But assert check failed returning above file in results. Somehow it's been modified. No idea when and how.

Anyone running 4.2.1, could you please provide me this file.
Thanks in anticipation.

Sent from my Nexus 7 using Tapatalk HD
 
marty331
Old
#2  
marty331's Avatar
Senior Member
Thanks Meter 240
Posts: 769
Join Date: Jun 2011
Location: Dallas, TX
Quote:
Originally Posted by gurudev32 View Post
Tried updating from 4.2.1 to 4.2.2.
But assert check failed returning above file in results. Somehow it's been modified. No idea when and how.

Anyone running 4.2.1, could you please provide me this file.
Thanks in anticipation.

Sent from my Nexus 7 using Tapatalk HD
I have the exact same issue!
Current Devices:
Phone: Nexus 4
ROMs: CM10.1

Device: Nexus 7
ROM: Stock Rooted
CM10

Previous:

Phone: Infuse SGH-I997
ROMs: Infused 2.2
Serendipity VII
CM7
CM9
CM10

Device: Kindle Fire
ROMs: CM7
ICS/CM9
 
gurudev32
Old
#3  
gurudev32's Avatar
Senior Member - OP
Thanks Meter 163
Posts: 110
Join Date: May 2011
Location: Bengaluru
Default Re: Req: file - System/bin/debuggerd

Here is the list of only apps with root access in my tab.

Carbon - App backup and restore, Solid explore, Stick mount, SuperSU, System tuner pro and Terminal Emulator.

Thought to seek out the culprit!

Sent from my Nexus 7 using Tapatalk HD
 
PhoenixTank
Old
(Last edited by PhoenixTank; 13th February 2013 at 12:58 AM.) Reason: Moar info
#4  
PhoenixTank's Avatar
Member
Thanks Meter 31
Posts: 46
Join Date: Dec 2010
https://dl.dropbox.com/u/17326185/debuggerd

MD5: B59443115C4181F49A57C1290EE3225B

https://dl.dropbox.com/u/17326185/build.prop

MD5: D9D1855E0C90049DC410A4406B802259

Pulled this from the 4.2.1 factory image. I seem to have got past the debuggerd error message now (though I need to revert my build.prop entirely, apparently).
Included build.prop (not yet tested) from 4.2.1 image too.

Working for me and now running 4.2.2.

At your own risk, yadda yadda, not responsible for explosions or anything less terrible, blah blah.

FWIW, I had been using Stickmount and superSU.
The Following 5 Users Say Thank You to PhoenixTank For This Useful Post: [ Click to Expand ]
 
gurudev32
Old
#5  
gurudev32's Avatar
Senior Member - OP
Thanks Meter 163
Posts: 110
Join Date: May 2011
Location: Bengaluru
Quote:
Originally Posted by PhoenixTank View Post

Pulled this from the 4.2.1 factory image. I seem to have got past the debuggerd error message now (though I need to revert my build.prop entirely, apparently).
Included build.prop (not yet tested) from 4.2.1 image too.

Working for me and now running 4.2.2.

At your own risk, yadda yadda, not responsible for explosions or anything less terrible, blah blah.

FWIW, I had been using Stickmount and superSU.
Thanks Now 'm on 4.2.2
 
bftb0
Old
#6  
Senior Member
Thanks Meter 774
Posts: 2,120
Join Date: Feb 2010
In the future, If you want to pull arbitrary file(s) from Google N7 factory images, a useful skill set is to figure out how to use "sim2img" utility and loopback mounts (Windows need not apply).

Those system.img files shipped by Google are "sparse ext4 images" - they can not be directly mounted as a loopback, but that's where the "sim2img" utility comes in

The sequence goes like this:

- use sim2img to convert Google image file to regular ext4 image file
- loopback mount reg. image file
- grab whatever files you want (and check user/GRP ownership & modes)

It really is just that easy.

The "sim2img" utility is part of the android ext4_utils toolset. See this XDA thread from the Galaxy S forums for more details. (Yes the N7 system.img files from Google are also in this format.)

cheers
The Following 2 Users Say Thank You to bftb0 For This Useful Post: [ Click to Expand ]
 
TheRejzo
Old
#7  
TheRejzo's Avatar
Junior Member
Thanks Meter 0
Posts: 17
Join Date: May 2012
Location: Bratislava

 
DONATE TO ME
Quote:
Originally Posted by PhoenixTank View Post
https://dl.dropbox.com/u/17326185/debuggerd

MD5: B59443115C4181F49A57C1290EE3225B

https://dl.dropbox.com/u/17326185/build.prop

MD5: D9D1855E0C90049DC410A4406B802259

Pulled this from the 4.2.1 factory image. I seem to have got past the debuggerd error message now (though I need to revert my build.prop entirely, apparently).
Included build.prop (not yet tested) from 4.2.1 image too.

Working for me and now running 4.2.2.

At your own risk, yadda yadda, not responsible for explosions or anything less terrible, blah blah.

FWIW, I had been using Stickmount and superSU.

How to make it? and i will lose all data? thanks
 
SidereusOne
Old
#8  
Junior Member
Thanks Meter 0
Posts: 23
Join Date: Feb 2012
Quote:
Originally Posted by TheRejzo View Post
How to make it? and i will lose all data? thanks
Big thanks.

Replacing the debuggerd file allowed twrp to load the 4.2.2 update.

Also interesting, other than titanium, the only other root app on this device is Stickmount.
 
diba320
Old
#9  
Senior Member
Thanks Meter 24
Posts: 163
Join Date: Dec 2011
Did not work for me ...
I have a N7 3G and the same message when trying to update. Replaced mine with the one from the download, no change, same error.
 
grybouille
Old
#10  
Junior Member
Thanks Meter 0
Posts: 1
Join Date: Feb 2013
Quote:
Originally Posted by diba320 View Post
Did not work for me ...
I have a N7 3G and the same message when trying to update. Replaced mine with the one from the download, no change, same error.
First of all, thanks a lot to PhoenixTank who provides me the solution.
In fact to make it work, I had to change the permissions allowed on that file named "debuggerd", I checked what permissions were allowed on the original file and do the same on the copied one. I did it with ES explorer in root mod.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes