Well, I don't think this is good

Search This thread

HappyKhicken

Senior Member
Jul 30, 2009
87
16
So I tried the juopunutbear method to get s-off. I got partway through, then got this error:

Code:
[1]   Segmentation fault      su -c "/data/loc...
Quit....
Press ENTER to exit.....

My phone now won't get past the bootloader. It just sits on the black screen with a picture of the phone and a green arrow.

I also seem to have lost clockworkmod.

Any ideas on what to do here?

I'm unlocked, 1.45.0013.
 

HappyKhicken

Senior Member
Jul 30, 2009
87
16
I managed to get clockworkmod reinstalled and did a recovery. It's still just sitting at that screen.
 

HappyKhicken

Senior Member
Jul 30, 2009
87
16
I can access the bootloader, fastboot, and CWM fine. However, past that it just sits at the screen with the green arrow.
 

HappyKhicken

Senior Member
Jul 30, 2009
87
16
Looks like I got it fixed. Thanks for trying to help me out xmc, I appreciate it.

From what I can tell with my limited Android knowledge, something was up with the boot file. Whenever I used fastboot to flash a new boot.img it fixed it.
 

Indirect

Senior Member
Mar 25, 2011
2,346
3,001
Florida
Ugh, run control bear with -r command line argument
Load up cmd or terminal, goto the directory where control bear is, and type

controlbear -r

and it will restore your boot.img >.>

Segmentation fault has nothing to do with the exploit, it's that adb is borking itself.

---------- Post added at 01:14 PM ---------- Previous post was at 01:11 PM ----------


Why would you direct him to the mt4gs channel if he needs help with Juopunutbear? Why not send him to that channel so he can get assistance from the devs of it?
 

crimedave1987

Senior Member
Jul 10, 2009
218
23
Maryland
i think ill just wait

for the root of these specs

Doubleshot PVT SHIP S-ON RL
HBOOT-1.45.0013
MICROP-0353
eMMC-boot
Nov 21 2011,20:20:47

**MY BOOTLOADER IS UNLOCKED**

AOS: 2.3.4 ("GINGERBREAD")
HTC SCENE VER: 3.0
SOFTWARE NUMBER: 1.55.531.3

KERNEL VERSION:
2.6.35.13-ge4be2bc
htc-kernel@and18-2 #1
SMP PREEMPT Thu Nov 17 18:32:14 CST 2011

Baseband Version:
11.59.3504.00U_11.16.3504.20_2

Build Number:
1.55.531.3 CL210454 release-keys

Browser Version:
WebKit/533.1
 

obig2

New member
Dec 2, 2012
1
0
Help please

Looks like I got it fixed. Thanks for trying to help me out xmc, I appreciate it.

From what I can tell with my limited Android knowledge, something was up with the boot file. Whenever I used fastboot to flash a new boot.img it fixed it.

How did you get it fixed what did you do? please help!
 

HappyKhicken

Senior Member
Jul 30, 2009
87
16
How did you get it fixed what did you do? please help!

Just yanked the boot.img from my nandroid and fastboot flashed it.

Looking back, it's funny to think that I didn't even think to try that at the time. Now flashing the boot.img has become second nature to me.

I tried to do Juopunutbear again, but I just can't get it to work so I've been s-on unlocked this entire time.
 

Dr.Gonz0

Senior Member
May 21, 2007
346
32
Just yanked the boot.img from my nandroid and fastboot flashed it.

Looking back, it's funny to think that I didn't even think to try that at the time. Now flashing the boot.img has become second nature to me.

I tried to do Juopunutbear again, but I just can't get it to work so I've been s-on unlocked this entire time.

Exact same issue here. Just learned to do what you do and fastboot the boot.img file

Sent from my myTouch_4G_Slide using xda app-developers app