tihmstar / futurerestore

A hacked up idevicerestore wrapper, which allows specifying SEP and Baseband for restoring
GNU Lesser General Public License v3.0
863 stars 275 forks source link

11 Pro Max fails to restore to 13.5 with 13.5.1 SEP and Baseband ERROR: Unable to find component node for Rap,RestoreRTKitOS #320

Open goodboydheeraj opened 4 years ago

goodboydheeraj commented 4 years ago

I had successfully compiled futurerestore v182. Tried restoring my 11 Pro Max to 13.5 using 13.5.1 sep and baseband. Every other steps were successful but the restore failed twice at "Unable to find component node for Rap,RestoreRTKitOS"

https://pastebin.com/wZtZyAjQ

Someone had the same issue using idevicerestore and was fixed in Apr 13. Futurerestore git doesn't include this fixed commit of idevicerestore. Is it an issue with futurerestore or idevicerestore itself?

m5performance commented 4 years ago

Did you get it working? I’m trying to downgrade my iPhone 11 Pro Max to iOS 13.5

Do you mind sharing your compiled updated version or if not at least direct me towards how to compile so I can do it myself?

goodboydheeraj commented 4 years ago

Even If I give you the compiled version you will get an error like me at the end of the restore. Anyway are you trying to downgrade from 13.5.1 to 13.5? Then its not possible. Or updating from 13.3.x to 13.5?

m5performance commented 4 years ago

Thank you for your reply! Long story short I was on iOS 13.5 jailbroken and I have missed up my jailbreak to the point that it was not usable and had no option other than to update my phone unfortunately to iOS 13.5.1. Before I have updated believe me, I tried EVERYTHING to fix or even restore iOS 13.5 without updating but all failed (Resetting Settings, Erase all contents, etc.) what made it even worse is that I couldn’t even jailbreak on iOS 13.5 using unc0ver it keeps getting stuck on step 15 which says “error obtaining Entitlements”

I know that I “can’t” downgrade back to iOS 13.5 because of the two main issues

1- I’m not jailbroken this I can’t set my Nonce 2- Futurerestore is not compatible with A13 devices (I think so)

I really wish that I’m wrong with what I said above and there is away. I just can’t stand the fact that I forced willingly to updated to iOS 13.5.1 and see my jailbreak vanish before my eyes 😢

remilouise commented 4 years ago

You can do a full restore from 13.5 to 13.5 via Succsession. Can you jailbreak your device?

When the sep and baseband in 13.5 and 13.5.1 the same you can downgrade from 13.5.1 to 13.5. shsh still required.

m5performance commented 4 years ago

Unfortunately, I can’t jailbreak because Unc0ver was broken (gets suck at step 15 “unable to obtain entitlements”) and had no option but to update to iOS 13.5.1 which is not jailbreakable (yet). I have shsh blobs saved but no luck downgrading since I can’t set my nonce and futurerestore is incompatible either

jinghanghang commented 4 years ago

Can I update from 13.3 to 13.5 with 13.5 shsh2 and 13.5.1 sep +baseband ? I don’t know V180 is good for 11ProMax

jinghanghang commented 4 years ago

I had successfully compiled futurerestore v182. Tried restoring my 11 Pro Max to 13.5 using 13.5.1 sep and baseband. Every other steps were successful but the restore failed twice at "Unable to find component node for Rap,RestoreRTKitOS"

https://pastebin.com/wZtZyAjQ

Someone had the same issue using idevicerestore and was fixed in Apr 13. Futurerestore git doesn't include this fixed commit of idevicerestore. Is it an issue with futurerestore or idevicerestore itself?

Can I update from 13.3 to 13.5 with 13.5 shsh2 and 13.5.1 sep +baseband ? I don’t know V180 is good for 11ProMax

m5performance commented 4 years ago

Can I update from 13.3 to 13.5 with 13.5 shsh2 and 13.5.1 sep +baseband ? I don’t know V180 is good for 11ProMax

It’s possible but I highly recommend you staying on iOS 13.3 the time_waste exploit is very stable and updating to iOS 13.5 had lots of issues and excessive battery brain (had the same tweaks and exact setup from iOS 13.3 and now lost my jailbreak because I had to update to iOS 13.5.1 as my firmware became very unstable