Hacking I updated to 7.0 like a fool, and have autoRCM active. Am I screwed?

ssmatt · Feb 20, 2019

Basically I'm now in a position where I can't boot into CFW, or into stock firmware presumably because whatever 7.0 did is blocking that method of boot.

Is there anything I can do other than wait/hope they get CFW working on 7.0

x65943 · Feb 20, 2019

ssmatt said:
Basically I'm now in a position where I can't boot into CFW, or into stock firmware presumably because whatever 7.0 did is blocking that method of boot.

Is there anything I can do other than wait/hope they get CFW working on 7.0

What happens when you turn off autorcm? Shouldn't that allow you to boot?

Hayato213 · Feb 20, 2019

Just wait for 7.0.0 support.

ssmatt · Feb 20, 2019

x65943 said:
What happens when you turn off autorcm? Shouldn't that allow you to boot?

I tried switching it off using Hitake, but it won't do anything, and trying to boot into stock from there just comes up with an error.

ZachyCatGames · Feb 20, 2019

Luckily for you, Atmosphere is getting 7.0.0 support sometime within the next few days

ssmatt · Feb 20, 2019

ZachyCatGames said:
Luckily for you, Atmosphere is getting 7.0.0 support sometime within the next few days

Oh thank god

(And thank you/Atmosphere)

Deathscreton · Feb 20, 2019

ssmatt said:
Basically I'm now in a position where I can't boot into CFW, or into stock firmware presumably because whatever 7.0 did is blocking that method of boot.

Is there anything I can do other than wait/hope they get CFW working on 7.0

Do you have a backup from before 7.0?

ssmatt · Feb 20, 2019

Deathscreton said:
Do you have a backup from before 7.0?

Yeah I have on on one of my cloud storage. I'll find it eventually if I can use it

Phenj · Feb 20, 2019

ssmatt said:
Basically I'm now in a position where I can't boot into CFW, or into stock firmware presumably because whatever 7.0 did is blocking that method of boot.

Is there anything I can do other than wait/hope they get CFW working on 7.0

There's no way you can't boot stock. Just turn off autorcm with hekate

Deathscreton · Feb 20, 2019

Yes, you can. Boot up Hekate, restore your NAND backup. I don't believe there are any fuse changes between 6.2 and 7.0, so once you restore, you should be able to boot right up, AutoRCM or no. If your last restore was 5.x, you'll need to have AutoRCM enabled so you can avoid the Fuse check.

XaneTenshi · Feb 20, 2019

Deathscreton said:
Yes, you can. Boot up Hekate, restore your NAND backup. I don't believe there are any fuse changes between 6.2 and 7.0, so once you restore, you should be able to boot right up, AutoRCM or no. If your last restore was 5.x, you'll need to have AutoRCM enabled so you can avoid the Fuse check.

That won't work. FW 6.2 burns the fuse count to 8, while 7.0 and 7.0.1 burns 9 fuses. So he won't be able to boot without Hekate if he restores a previous FW backup.

Deathscreton · Feb 20, 2019

XaneTenshi said:
That won't work. FW 6.2 burns the fuse count to 8, while 7.0 and 7.0.1 burns 9 fuses. So he won't be able to boot without Hekate if he restores a previous FW backup.

Ahh, I was under the impression that 6.2-7.0 did not burn any additional fuses. Eitherway, he can still downgrade and use Hekate to boot. He's not stuck.

paulzheng · Feb 21, 2019

Hayato213 said:
Just wait for 7.0.0 support.

it also can downgrade into 6.1 cfw.

--------------------- MERGED ---------------------------

Deathscreton said:
Yes, you can. Boot up Hekate, restore your NAND backup. I don't believe there are any fuse changes between 6.2 and 7.0, so once you restore, you should be able to boot right up, AutoRCM or no. If your last restore was 5.x, you'll need to have AutoRCM enabled so you can avoid the Fuse check.

7.0's efuse is 9 but 6.2's efuse is 8, so it couldn't be downgrade directly. BTW hekate can launching cfw ignore efuse.

Deathscreton · Feb 21, 2019

paulzheng said:
it also can downgrade into 6.1 cfw.

--------------------- MERGED ---------------------------

7.0's efuse is 9 but 6.2's efuse is 8, so it couldn't be downgrade directly. BTW hekate can launching cfw ignore efuse.

Someone already mentioned that, and I know you can boot using Hekate. See my post that's says all this two above yours.

Raugo · Feb 21, 2019

If he still have autorcm didn't burn any fuse and can downgrade it without problems. Also with the fuses burned can downgrade it but only can launch the OS using a custom bootloader like hekate or fusee.

Xuman · Feb 21, 2019

You can boot into hekate and remove autoRCM and it'll boot normally. Just happened to me a few days ago

Hacking I updated to 7.0 like a fool, and have autoRCM active. Am I screwed?

Well-Known Member

i can be your sega dreamcast or sega nightmarecast

Newcomer

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum