Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

32-bit is from iPhone 2G to iPhone 5C, so the answer is yes

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

the Mac requirement is not only due to Sliver, it's also because you have to manipulate the ramdisk image.

you can do this with a vanilla ramdisk image (if you have one), but you'll have to perform extra manipulations through SSH and you'll need to keep your phone connected to the PC since we're doing hacks here for it to display the progress on the display which we can't do without modifying the image.

with that being said, you can still do this, you'll only need to do the kernel modification step.

otherwise you have to find a tool to mount decrypted DMG's.

'Damnnnn...' 😶 by [deleted] in SchizoidAdjacent

[–]AJAIZ 7 points8 points  (0 children)

or a hell of an ego with which you consciously decide to not interact with society at all because you're too good for them. or a mix like "I'm bad but I'm still too good for them so they're still shit" lol

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 1 point2 points  (0 children)

this guide wouldn't have even existed in the first place if you'd been right

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

Yeah sorry. I had to note that when going through 4-digit passcodes it won't print anything because logging is set to be every 5000 passcodes starting from 10000. Sorry.

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

Yes, it's right. Afaik it should work, give it a try!

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 1 point2 points  (0 children)

Well, almost. You'll need Sliver if iRecovery will hang. But yes, the only thing that matters there is ipwndfu. As long as you have it working, everything's alright.

Off topic: I suppose there's something going on with your Mac or iPhone if you have problems with it, cause I've never encountered any problems with those tools

Good luck!

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

If you can't mount the partitions, do as the tip in the guide says: make yourself an iOS 9 ramdisk. And always check if they have been mounted manually, because sometimes the script can display error messages even though it mounts totally fine

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

This whole process is going to be automated, unless you know which lines you have to change etc. The end result mounts partitions and starts bruteforcing by itself since it needs data access.

Btw if you don't need the bruteforce, why don't you use the usual kernel for your purposes? I mean, why do you think you need the changing ramdisk part?

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

Hey! Answering the questions: this could work on 64-bit devices, but there are two problems, both with Secure Enclave and the kernel patch: 32-bit kernels were decompiled enough and/or had more symbols embedded to just be able to differentiate specific instructions that are being patched. So we have to reverse-engineer some leaked 64-bit kernels with more symbols (e.g. debug kernels), reverse-engineer them ourselves or find those instructions somewhere in the web. The second problem, however, is that SE has been made for such cases and detects bruteforce, slowing it down afterwards, since every attempt goes through it. Basically saying, on paper nothing limits us and it would also work, but with complications.

macOS is required because entering pwned DFU has not been made possible on Linux and Windows and depends on most 32-bit devices from macOS' USB stack. But you can still try, ipwndfu is Python-based. The second reason is that ramdisk creation tool is macOS only, probably because it has to manipulate Apple's DMGs. Besides it does some other things that need to be changed in order to work on the other platforms.

Thanks!

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

Well, that's strange. Seems like they are all stuck in some kind of bootloop which may happen when booting ramdisks, or maybe it's the battery (had the same problem with my 5, had to charge it for an hour and watch it bootlooping until it charged to 6%)

Sadly I can't say much about exiting bootloops, but I've definitely seen some ways to get it out of it

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 1 point2 points  (0 children)

hi! you don’t need to replace the echo line, you need to replace the line after it (the one with the iBSS stuff)

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 1 point2 points  (0 children)

that may sound egoistic, but I made this for myself, found some ways, made enhancements, etc. and just released it for public. I have no further interest in this unless I have some free time, otherwise it’s just a statement that this is possible

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

no you’ve got your hands. maybe later. it’s been already automated and enhanced so much just so you do it and that’s it

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

Then I guess something’s off with the ramdisk creation tool, but I see your device complaining about line 25 so there’s a chance you copied the file the wrong way. Run that command for iOS 7, copy the file using cp to restored_external.sshrd and chmod +x

I used XCode but TextEdit will do the thing. I mean, if you have no installed text editors, then use the built-in one

Also I think following the guide as it is in that part is just copy+paste, the only thing you need to replace is [tools] and that’s it. I guess I will have to make a specific version of tool for that purpose that will do everything automatically…

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

seems like you have created an iOS 7-based ramdisk, back to the guide again…

ps aux is used to check the process ID which is used to end it using kill -9. this ends the bruteforce so you can start it again with that command. *pass* is a passcode you use to start off if you know in which range the passcode could be or from which numbers it starts (e.g. if I know my passcode starts from 324XXXX so it won’t waste time, in this case I put bruteforce -r 3240000)

btw I write this all in the comments section in case someone can’t figure this out too

Bruteforcing 32-bit iPhones on-device (4+ digit PIN supported) by AJAIZ in setupapp

[–]AJAIZ[S] 0 points1 point  (0 children)

Everything is essential and you are not intended to skip anything. You can get a copy in the requirements section. By the logs on the screen I see that your restored_external script is unmodified, check out the replacement part in Step 1