Build350 - Bricked iPhone

[j5an]

I installed the Build350 as is onto a jailbroken phone. I was able to start springboard and work with the app settings. However, when I clicked on "WTFJH Settings", the general settings always failed. I rebooted the whole, and now the only thing I� see is an apple logo. I am not even able to get the logs as of now, to debug. Has anyone faced this issue already?

[Naville]

@j5an This is probably a issue from original Introspy. Try start in SafeMode

[Naville]

@j5an Check issues #4. Should be the same one

[Naville]

Ah ha yes. You should compile yourself from master instead of using the pre-built binaries in RELEASES .

[j5an]

I dont think it is really the original introspy as you mentioned. I had introspy up and running till my update to 9.0. And i tried building the master a couple of times, but was having some issues. But lesson learnt.

[Naville]

any log about "issues"?
It built successfully on TravisCI.
And yes Introspy has the same problem as in iSECPartners/Introspy-iOS#38

Not sure about what lesson you learnt though

[j5an]

ld: can't open -sectcreate file: ./classdumpdyld.dylib
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[3]: *** [/Users/j5an/Documents/mobile/WTFJH/.theos/obj/debug/armv7/B34IC3VUCQ8S9ZV.dylib] Error 1
make[2]: *** [/Users/j5an/Documents/mobile/WTFJH/.theos/obj/debug/armv7/B34IC3VUCQ8S9ZV.dylib] Error 2
make[1]: *** [internal-library-all_] Error 2
make: *** [B34IC3VUCQ8S9ZV.all.tweak.variables] Error 2
Make Exit With Status:  512

ThirdPartyTools---Building: classdumpdyld
Loader For classdumpdyld Doesn't Exist. Creating
Makefile:1: theos/makefiles/common.mk: No such file or directory
Makefile:6: theos/makefiles/common.mk: No such file or directory
Makefile:7: /tweak.mk: No such file or directory
Makefile:8: /library.mk: No such file or directory
make: *** No rule to make target `/library.mk'.  Stop.
mv: rename ./obj/debug/classdumpdyld.dylib to ../../classdumpdyld.dylib: No such file or directory
ThirdPartyTools---Building: dumpdecrypted

I dont think i have missed any steps while building. Let me know if i may have.

[Naville]

Ah yes.

Seems like a issue exists in Theos.
That's why

Makefile:1: theos/makefiles/common.mk: No such file or directory
Makefile:6: theos/makefiles/common.mk: No such file or directory
Makefile:7: /tweak.mk: No such file or directory
Makefile:8: /library.mk: No such file or directory
make: *** No rule to make target `/library.mk'.  Stop.

Thus broke the whole thing

EDIT:
TravisCI doesn't have theos installed by default. I added ./InstallTheos.sh to the CI Command and it works like a charm

[Naville]

As you can see in https://travis-ci.org/Naville/WTFJH/builds/146533529

My guess is this build error is a issue on your theos installation

[Naville]

Also, do you have write access to your local cloned repo?
That is needed for build.py to work

EDIT:
This is a issue of legacy theos.
Modern theos use $THEOS instead of symlink

[j5an]

It got successfully built. As you said, i just had to run the InstallTheos.sh instead of downloading theos and setting its path. My bad.

Make Exit With Status: 0 cp: ./obj/debug/VMSI6DJARRE27F9.dylib: No such file or directory xattr: No such file: theos/vendor/include/rocketbootstrap/framework xattr: No such file: theos/vendor/include/rocketbootstrap/layout/Library/MobileSubstrate/DynamicLibraries/RocketBootstrap.dylib xattr: No such file: theos/vendor/include/rocketbootstrap/overlayheaders xattr: No such file: theos/vendor/include/rocketbootstrap/tests/framework **dpkg-deb: building package 'naville.wtfjh' in './Build-387.deb'.** Cleaning Misc Files Unlinking TheOS...

I will try to set my phone on Safe Mode and remove the old one, to install the built verison. As you said, the brick happened because of the old introspy code for sure. I will try to get logs as much as i can, so if it gets bricked back again, i can post the previous logs.

Thanks for your help Naville.

[Naville]

I've pushed a fix to master that removed THEOS Legacy support and therefore no more problems caused by theos legacy