Samgisaninja / SuccessionRestore

Restore iOS devices without updating via rootfilesystem DMG
GNU General Public License v3.0
406 stars 90 forks source link

No Restore bar appears on 1.4.12/b4 #108

Closed Saad-bloop closed 4 years ago

Saad-bloop commented 4 years ago

on Succession 1.4.12/b4 while doing restore on any phone the after clicking erase it says restoring please wait and then there is no progress bar under it on iphone 6s it doesnot show anything and on iphone X it just shows loading sign and no bar no writting etc. I waited for hour but nothing happened please help

Samgisaninja commented 4 years ago

can you please send a log

Saad-bloop commented 4 years ago

How to send the log ?

Samgisaninja commented 4 years ago

just drop it in github comments

Saad-bloop commented 4 years ago

I need a bit help can you guide me how can i get the log of my succession app. Like from where can i find my log and should i get log after pressing erase and restore or before it.?!

Samgisaninja commented 4 years ago

go to settings turn on logging cause the issue use filza or something to share /var/mobile/succession.log to this github comment thread

Saad-bloop commented 4 years ago

succession.log see

Saad-bloop commented 4 years ago

IMG_1333

Saad-bloop commented 4 years ago

Any idea whats the problem?

Saad-bloop commented 4 years ago

@Samgisaninja

Samgisaninja commented 4 years ago

Ok bud I'll get around to it when I get a chance. That might be a few weeks. If that's too long for you, succession is open source, and I accept contributions. I understand you're impatient, but making separate comments to spam my inbox, reacting with eye emojis to spam my inbox, and tagging me when I don't reply within an hour, again spamming my inbox... does not make me more likely to fix your problem. It's a beta release for a reason: so that I can take time to iron out these problems. Stop complaining.

Saad-bloop commented 4 years ago

I understand it brother. I thought it was some kind of small bug or i was doing some kind of mistake while using the app but i guess its not that. But I really appreciate you help and kindness and i am sorry for being impatient a

Samgisaninja commented 4 years ago

This was fixed in 853102e