iPad 6th Gen bootloop after restarting from sshrd (iPadOS 16.6.1)

[fpandroid]

Hi, after using sshrd the device will flash white with apple logo then reboot not getting into iOS

Really appreciate if someone knows a fix.

[AlexChecker]

same thing, but on IOS 16.7.2 on Iphone 8. Used 15.6, 16.0 16.7.2 IPSW for ramdisk, but after rebooting it jumps straight to bootloop

[imnltsa]

@fpandroid @AlexChecker Can you get back to me? Have you done anything to resolve it? I'm not getting my device recognized by ANYTHING, no matter if I enter DFU or not, and it's starting to get a little worrying.

[David-mca]

Same issue on iphone 8 ios 16.6.1 if anyone know how to fix it pls tell

[imnltsa]

Same issue on iphone 8 ios 16.6.1 if anyone know how to fix it pls tell

Your only solution is to restore. Backup any data you need and restore the device. Sorry.

[David-mca]

Ohh no... Well atleast i can wait for the battery to ran out as last resort befoure restoring. Thanks for the reply tho!

[mast3rz3ro]

Well at least i can wait for the battery to ran out as last resort before restoring

Trust me you will just waste your time for waiting, instead why not play with the device and try real attempts?

[imnltsa]

Well at least i can wait for the battery to ran out as last resort before restoring

Trust me you will just waste your time for waiting, instead why not play with the device and try real attempts?

Once this happens to you your device is cooked. You're not recovering from this until you do a restore.

[mast3rz3ro]

Once this happens to you your device is cooked. You're not recovering from this until you do a restore.

Hmm, I wonder why you commented with this when I said we can try and you didn't comment to @David-mca when he stated that he will wait until battery drains out in hope that it will work.

I believe we could find a solution for it at least for people who actually knows their password.

[imnltsa]

Once this happens to you your device is cooked. You're not recovering from this until you do a restore.

Hmm, I wonder why you commented with this when I said we can try and you didn't comment to @David-mca when he stated that he will wait until battery drains out in hope that it will work.

I believe we could find a solution for it at least for people who actually knows their password.

Source: This happened to me. I lost everything.

This has nothing to do with passwords or whatever you're on. Doing stuff you shouldn't in a ramdisk will result in a bootloop. Not one that I've seen before either, with visual artifacts, and letting the battery die is useless as doing literal hard resets with the btn_reset combination change nothing.

Backup what you need and restore. Not sure why or how you butted into this conversation but anyone with this issue is not keeping their current iOS version.

[mast3rz3ro]

Source: This happened to me. I lost everything.

It's did happened to you once but it did happened to me serval times :).

This has nothing to do with passwords or whatever you're on. Doing stuff you shouldn't in a ramdisk will result in a bootloop.

Actually the problem mainly starts after trying to mount the device on iOS 16 but apparently the author @verygenericname doesn't knows about this issue and hence a lot of people are going to face the same problem.

Not sure why or how you butted into this conversation

If you mean how did I noticed about this issue without even began participating, it's because I was already watching the repo changes since I started developing SSHRD Lite another fork meant to be more efficient by focusing in the main task which is making the ssh ramdisk but apparently it's has serval errors and needs to be fixed.

but anyone with this issue is not keeping their current iOS version

Instead of stating this why not just try something and see If it works? I personally made some real tries and unfortunately all didn't worked. the only thing I haven't tried until now is resetting the device via purple mode maybe somebody can give it a shout and confirm If it works.

[imnltsa]

Do you mount with mount_filesystems or do you manually mount the devices to mount points

[AlexChecker]

My problem probably was caused by damaged wire. I figured it out, because I was trying to do similar thing with iPhone, and it was mostly the same. Some tangling to the wire fixed issue for iPhone, for iPad cannot verify this theory, but it looks very similar to me

[imnltsa]

My problem probably was caused by damaged wire. I figured it out, because I was trying to do similar thing with iPhone, and it was mostly the same. Some tangling to the wire fixed issue for iPhone, for iPad cannot verify this theory, but it looks very similar to me

I'm betting on that being a placebo because of how unrealistic/non-problematic it sounds and you probably indirectly did something else that would be good to take note of.

[mast3rz3ro]

Do you mount with mount_filesystems or do you manually mount the devices to mount points

I used to use this mount script but not anymore, I found manually mounting to be fan and more interesting. Actually I was planning to write my own mount script which is still unfinished yet.

My problem probably was caused by damaged wire

I doubt that can be the case with you for getting the bootloop

[imnltsa]

afaik mounting is broken on 17+, idk if thats still the case with current commits but the way sep partition mounting is handled causes errors and stuff and shit with booting the ramdisk with pongo to actually make sep work and allat idk its been a while i gave up lol but i hope you figure something out eventually, imo just seems like a deadend then and now especially considering the artifacting i mentioned persists hard reboots (would like to know if you got this too, while the device bootloops theres a little line visible halfway down the screen thats just a bunch of monochrome colors and spans half the screen horizontally, idk if thats just an ipad thing cuz of the big screen but thats a dead giveaway this thing is happening.) i did manually get sep parition working with manual mounts and sep locker gigalocker whatever but yeah the bootloop happened just once idk i give up good luck

[mast3rz3ro]

afaik mounting is broken on 17+, idk if thats still the case with current commits

I can confirm that mounting in iOS 16 and above are broken even with current commits.

while the device bootloops theres a little line visible halfway down the screen thats just a bunch of monochrome colors and spans half the screen horizontally,

Hmm, actually I haven't seen that ever, maybe it's was because of hardware issue on the device?

[imnltsa]

Hmm, actually I haven't seen that ever, maybe it's was because of hardware issue on the device?

not hardware related. not at all, definitely software. im not sure how though, considering checkm8s required in order to boot sshrd which would then all(?) be in ram and cleared by a reboot

i dont have this issue anymore so obviously i cant find out myself but whatever iboot was trying to boot after the bootloop started causes those artifacts and then a subsequent reboot. i have an iPad7,1, this would probably happen on the 6th gen too if i were to guess. ofc it doesnt indicate whats wrong.. i had originally thought maybe the ssv seal was broken (15+) but apparently that would just result in a recovery loop.

immediately out of my knowledge range and devs/rjb "geniuses" dont know anything either

[imnltsa]

I can confirm that mounting in iOS 16 and above are broken even with current commits.

mounting broken due to

1. script doesnt get the proper paths right
2. no sep exploit is used

there is #279 (comment)

i used this long after i got a bootloop, safest way to go imo. i will never use mount_filesystems and would not recommend anyone to simply because of this, at least on 15/16/17+ (idk when exactly it breaks at least while mounting mnt2)

[imnltsa]

another thing to note, i believe i did reboot using the built in reboot command too like this threads title. mounting filesystems + typing reboot thru ssh = bootloop? would rather not test this myself rn 😭🙏

maybe some part of nvram is affected, this is all i can think of

[mast3rz3ro]

not hardware related. not at all, definitely software. im not sure how though, considering checkm8s required in order to boot sshrd which would then all(?) be in ram and cleared by a reboot

Right, all should be wiped after a reboot also I have never seen anybody who were mentioning about this.

mounting broken due to

1. script doesnt get the proper paths right
2. no sep exploit is used

Nope, this is isn't true If not at least for iOS 16

idk when exactly it breaks at least while mounting mnt2
mounting filesystems + typing reboot thru ssh = bootloop?

I recently made some research and it's seems that the device gets panic only at stage where the mount_filesystems tries to initialise SEP by running the seputil commands.

[imnltsa]

panic is due to not using pongoOS to boot the ramdisk

[mast3rz3ro]

panic is due to not using pongoOS to boot the ramdisk

I meant panic by getting a bootloop after reaching that stage in mount_filesystems