96 replies to this topic

[The_Chupacabra]

I have a bug2go folder in my sdcard and it is readable.

[my2cents]

I have a bug2go folder in my sdcard and it is readable.

Can you check and see if you have a /sdcard/bug2go folder?

Sent from my DROID BIONIC using Tapatalk 2

YES. I hadnt looked but I have a bug2go folder on the root of my sdcard. It has folders and .info files in there! Here is one of the reports that I generated.

Attached Files

•  bugreport-2013-01-10_21-36-38.000-0800.txt   5.25MB   30 downloads

[davisev5225]

Just thought I'd drop in here real fast and say I've been successful at triggering bug reports on my Razr. The only way I've been able to do so consistently is to press the power button until the "power off" menu pops up. THEN I press and hold the power button and volume up button for about 3 seconds. After that, you need to wait up to 30 seconds or so, and then you'll get 2x-3x very short vibrations in rapid succession. That's the start of the bug report.

I haven't had a chance to try and do this while the USB cord is plugged into the computer, but I will hopefully have the chance to try it tonight.

[tmyinc]

Just thought I'd drop in here real fast and say I've been successful at triggering bug reports on my Razr. The only way I've been able to do so consistently is to press the power button until the "power off" menu pops up. THEN I press and hold the power button and volume up button for about 3 seconds. After that, you need to wait up to 30 seconds or so, and then you'll get 2x-3x very short vibrations in rapid succession. That's the start of the bug report.

I haven't had a chance to try and do this while the USB cord is plugged into the computer, but I will hopefully have the chance to try it tonight.

Definitely let us know. That's one of the key things that we need to figure out. People successfully have done it without being plugged into USB port but not while plugged in.

Sent from my DROID BIONIC using Tapatalk 2

[johnthehillbilly]

Well why not un plug USB ..... trigger bug report .... plug back in ..then continue commands....... it won't hurt the process because until you enter the next command .... there should be no activity over the USB....... I have yet to be successful in even triggering the bug report (yet) ...... probably something i am doing wrong...... LOL

sent from my JB RAZR .... tapadriving

[tmyinc]

Well why not un plug USB ..... trigger bug report .... plug back in ..then continue commands....... it won't hurt the process because until you enter the next command .... there should be no activity over the USB....... I have yet to be successful in even triggering the bug report (yet) ...... probably something i am doing wrong...... LOL

sent from my JB RAZR .... tapadriving

I think people have tried to trigger the bug report and plug back in to USB but got errors. Not sure why that is the case though.

Sent from my DROID BIONIC using Tapatalk 2

[my2cents]

Well why not un plug USB ..... trigger bug report .... plug back in ..then continue commands....... it won't hurt the process because until you enter the next command .... there should be no activity over the USB....... I have yet to be successful in even triggering the bug report (yet) ...... probably something i am doing wrong...... LOL

sent from my JB RAZR .... tapadriving

I've done this about 20 times. Each time I think it might actually work, but it always comes back failed. I think that the exploit has to happen as the bug report is being generated. Since it takes time for the phone to be recognized by the computer again, I think we miss our window. If someone figures it out I am sure they will tell us...

[johnthehillbilly]

I've done this about 20 times. Each time I think it might actually work, but it always comes back failed. I think that the exploit has to happen as the bug report is being generated. Since it takes time for the phone to be recognized by the computer again, I think we miss our window. If someone figures it out I am sure they will tell us...

i kinda figured that had been tried (by someone smarter than me LOL)..........so basically it MAY boil down to a matter of timing between the bug report and continuing the commands...... and that timing may be measured in milliseconds is triggering the bug report via the developer options menu basically the same as via the button combination? i only ask because via the menu, it asks for a confirmation before actually triggering it.... is it possible that it may give us the extra timing that we may need to disconnect then reconnect the USB?

[daniel24fan]

does anybody have any luck rooting jellybean yet

[my2cents]

does anybody have any luck rooting jellybean yet

Nope. But you can help support development of a root method in the general forum, if you like...

[dave8311]

I have not been able to generate a bug report, so I did some looking around and I found this topic.....


Some devices will only let the debugger attach if the application has the android.permission.SET_DEBUG_APP permission set in its manifest file:
<manifest>
<uses-permission android:name="android.permission.SET_DEBUG_APP"></uses-permission>
</manifest>

Is this something that needs to be enabled in the buggy sudoko app?

[davisev5225]

Just thought I'd drop in here real fast and say I've been successful at triggering bug reports on my Razr. The only way I've been able to do so consistently is to press the power button until the "power off" menu pops up. THEN I press and hold the power button and volume up button for about 3 seconds. After that, you need to wait up to 30 seconds or so, and then you'll get 2x-3x very short vibrations in rapid succession. That's the start of the bug report.

I haven't had a chance to try and do this while the USB cord is plugged into the computer, but I will hopefully have the chance to try it tonight.

Just thought I'd drop a second update. I haven't had a chance to fully test USB bug reports due to family health issues, but the initial results aren't promising. Then again, I recently discovered that I'm also experiencing problems with my Razr's vibration motor seizing, so who knows. My current line of thought is to trigger the bug report before even beginning the exploit script, but I'm not sure that will lead anywhere. The motofail2go script generates another error (which I don't have handy at the moment) which I'm not sure I can correct. It tries to run a script from within /system, but obviously we can't have /system access without root.

I'll keep trying, but I'm by no means a developer. I just work in tech support, and can therefore do general troubleshooting.

[BADDINOROX99]

root exploit found they'll be posting it later

[jburchii]

Heard of a root exploit - haven't seen it yet........

[SPJESTER]

Root it out. Its on Main page and in my tool already!

Please Login or Register to see this Hidden Content

[daniel24fan]

I got it and it work great thank you Dan and everybody that work hard on it

[tucstwo]

Root it out. Its on Main page and in my tool already!

Please Login or Register to see this Hidden Content

And without a doubt the most OUT OF THE BOX thinking of any exploit I've EVER seen.