Fatal error occurred when running atmosphere 0100000000000005

[dylanea]

Fatal error occurred when running atmosphere.​

Program ID: 0100000000000005​

Error Desc: std: :abort() called (0xffe)

Report saved to /atmosphere/fatal_errors/report_0000000002c578b3.nin
Press POWER to reboot.

Installed atmosphere-1.2.4-master-e256261b8+hbl-2.4.1+hbmenu-3.5.0
Tried reformatting sdcard.

Can get to boot up in the original operating system airplane mode.
Can anyone suggest anything?
When I looked in my contents folder I could not find a 010000000000005 folder on the card.

 

[Oriordan]

What firmware ? May be you are using the wrong files or missing sigpatches !?

 

[dylanea]

What firmware ? May be you are using the wrong files or missing sigpatches !?

I always download from https://github.com/Atmosphere-NX/Atmosphere/releases

 

[CloudStrife1901]

Did you use the new fusee bin?

 

[dylanea]

Did you use the new fusee bin?

yeah

 

[Oriordan]

Try using deepsea + hekate sigpatches

 

[Toa_235]

any solutions for this ?
my consoles battery died, before it worked normal, upon recharging a bit and injecting fusee this error popped up
hekate and atmos latest... tried deepsea, tried rebuilding sd card, tried exfat, fat32, tried wiping with tegraexplorer, even creating emummc and booting, still nothing

any ideas ?
i can supply the error report bin if someone could make some sense out of it...

 

[Deleted member 585564]

0100000000000005 is boot sysmodule, any chance you could upload the error report for this?

 

[burhansalih]

https://github.com/Atmosphere-NX/Atmosphere/issues/1177

 

[Toa_235]

0100000000000005 is boot sysmodule, any chance you could upload the error report for this?

here you go m8
https://drive.google.com/file/d/10RM1Fcwn8pnJ7yyKVVEMtqNoS_PvWWTK/view?usp=sharing

also i don't have the raw partition backup...

 

[Deleted member 585564]

@Toa_235 I can't really make sense of those personally, I just thought it might be a good idea to post it in case someone who knows what to look for might be able to decipher it.

Are you able to boot into ofw though? In your case you say it started happening after battery died, so I'd try leaving it on charge for a while at least. Possible that battery state might have gone bad due to running out?

First, it initializes gpios and sets the gpio voltage to 1.8v.

Then it checks battery charge and SoC temperature using i2c. If either is bad, it shows one of two different bitmaps from .data in the framebuffer.

Because most sysmodules have not yet booted, this all uses raw IO pokes when it comes to gpio and i2c interfacing.

Otherwise, it continues by reading the bad_block_table.num_entries field from the BCT located at offset 0x00C000 in the NAND boot partition 0 (safe mode backup).

If bad_block_table.num_entries byte0 is non-zero, it does a repair with type=4. If byte1 is non-zero, it does a repair with type=5. The number of entires in the bad block table should always be 0x200 by default (represents partition_size). Values from 0x200 to 0x20F represent bad blocks in the NAND boot partition 0 while values from 0x210 to 0x21F represent bad blocks in NAND boot partition 1.

My understanding is that battery charge (or battery state) being bad would result in boot failure.

You could attempt a nand rebuild in case it's not battery-related, but make a backup and keep it in a safe place before you mess with it. You want to be able to restore the system to its original state in case messing with it screwed it up further.

 

[krycry]

any update on this? mine is doing the same thing. load into hekate just fine, same error as above when booting into atmosphere. battery in hekate shows 0%. but switch not dying or turned of even when it showed 0%.

 

[urherenow]

Does hekate also show voltage (I'm not inclined to reboot to refresh my memory at the moment)? If so, see (or wait/leave it on until) that it's drained to 3.2v, then charge it back up to 100%. This corrects most battery issues I've heard of.

 

[krycry]

Does hekate also show voltage (I'm not inclined to reboot to refresh my memory at the moment)? If so, see (or wait/leave it on until) that it's drained to 3.2v, then charge it back up to 100%. This corrects most battery issues I've heard of.

everything is 0, im really confuse.
tried rebuilding mmc still the same.

 

[Toa_235]

my battery info page looks good, did an emmc rebuild but still no boot, hekate made raw backup without problem so i presume the nand chip is not faulty, could be an age related hw failure or as some info i found online uncopletely written fw update, i'm working up to attempting a manual fw write using a pc, but i'm running into some issues with lockpick, anyone know anything about those errors ?

 

[tezzosman]

my battery info page looks good, did an emmc rebuild but still no boot, hekate made raw backup without problem so i presume the nand chip is not faulty, could be an age related hw failure or as some info i found online uncopletely written fw update, i'm working up to attempting a manual fw write using a pc, but i'm running into some issues with lockpick, anyone know anything about those errors ?

Hi,

Did you manage to do the manual fw write using a PC ?

I have almost the same issue (0100000000000005) as everyone here excepts that I can't boot into OFW at all.
Battery info shows 0 everywhere too, tried the MMC Rebuild steps with no luck, I don't know what else to try :/

 

[impeeza]

Fatal error occurred when running atmosphere.​

Program ID: 0100000000000005​

Error Desc: std: :abort() called (0xffe)

Report saved to /atmosphere/fatal_errors/report_0000000002c578b3.nin
Press POWER to reboot.

Installed atmosphere-1.2.4-master-e256261b8+hbl-2.4.1+hbmenu-3.5.0
Tried reformatting sdcard.

Can get to boot up in the original operating system airplane mode.
Can anyone suggest anything?
When I looked in my contents folder I could not find a 010000000000005 folder on the card.

a little search on google give:

https://github.com/Atmosphere-NX/Atmosphere/issues/1177

 

[kenlee168]

exfat do seem unstable

 

[krycry]

Hi,

Did you manage to do the manual fw write using a PC ?

I have almost the same issue (0100000000000005) as everyone here excepts that I can't boot into OFW at all.
Battery info shows 0 everywhere too, tried the MMC Rebuild steps with no luck, I don't know what else to try :/

same, i cant boot into ofw also.tried system wipe and mmc rebuild still cant. only hekate can load fine

 

[tezzosman]

a little search on google give:

Hi,

Thanks but I think we all went to Google and found this before posting here. Unfortunatelly the EMMC rebuild and System Wipe didn't work. I think our problem is related to the battery showing 0 but I don't know where to check to solve that