Replacing apu is posible?

[xiran64]

Hi to all!

I want to know if is posible to replace the nvidia apu, specifically from had-cpu-10, to hac-cpu-21.

I think, it need to restore nand files, if the process is success.

After that, it would be necesary to be modded physically? Online services may not be a priority.

Thx in advice!

 

[deeps]

no, not without also replacing the emmc since the encryption key is hardcoded in the cpu bootrom

 

[l7777]

I doubt anyone has tried, but we know the emmc and APU are tied together via encryption key as noted above. I suppose theoretically if you replaced both you could do it. What is the use case that makes APU replacement more desirable than other alternatives?

 

[xiran64]

I doubt anyone has tried, but we know the emmc and APU are tied together via encryption key as noted above. I suppose theoretically if you replaced both you could do it. What is the use case that makes APU replacement more desirable than other alternatives?

Thx for answer, to both!

The reason is the apu is internally in short (i've desoldered from motherboard, and desoldered all caps), is not a low impedance case, is a short in the pad caps.

The apu looks like a popcorn, yes, the owner tried to fix BSOD =' ( ... putting in short internally...

So, first step, is to substitute apu, later, reconstruct from 0 the nand files, but in the labeled text are some changes, and caps orientation.

 

[l7777]

Thx for answer, to both!

The reason is the apu is internally in short (i've desoldered from motherboard, and desoldered all caps), is not a low impedance case, is a short in the pad caps.

The apu looks like a popcorn, yes, the owner tried to fix BSOD =' ( ... putting in short internally...

So, first step, is to substitute apu, later, reconstruct from 0 the nand files, but in the labeled text are some changes, and caps orientation.

I suppose that's my question, the APU and EMMC are tied together. If you have already determined that the APU is faulty there is no reason to replace it. Just replace the board with a working one rather than attempt to replace the APU and EMMC with donor parts or rebuilding the EMMC.

 

[masagrator]

You need also to replace battery since calibration data is stored in emmc and by losing battery tied to it you won't be able to fully charge your battery without i2c shenanigans on every boot.

 

[xiran64]

I suppose that's my question, the APU and EMMC are tied together. If you have already determined that the APU is faulty there is no reason to replace it. Just replace the board with a working one rather than attempt to replace the APU and EMMC with donor parts or rebuilding the EMMC.

Oh, that most be the ideal, but we want to learn, if that titanic work is in our hands.

You need also to replace battery since calibration data is stored in emmc and by losing battery tied to it you won't be able to fully charge your battery without i2c shenanigans on every boot.

Oh, i've seen some people changing batteries without that point in mind ='(

 

[masagrator]

Oh, i've seen some people changing batteries without that point in mind ='(

That's why you are buying 4310 mAh replacement because it's the default one you can charge fully without calibration data. Anything above that requires calibration (stock battery design capacity is 4667 mAh)

 

[l7777]

You need also to replace battery since calibration data is stored in emmc and by losing battery tied to it you won't be able to fully charge your battery without i2c shenanigans on every boot.

What kind of shenanigans? I've swapped batteries around before but never done anything like that. Isn't it simply a matter of draining and charging it a couple times? All of them charged to ~4.2 volts.

Post automatically merged: May 22, 2025

Oh, that most be the ideal, but we want to learn, if that titanic work is in our hands.

Got ya, if it's a learning experiment then by all means have fun.

 

[masagrator]

What kind of shenanigans? I've swapped batteries around before but never done anything like that. Isn't it simply a matter of draining and charging it a couple times? All of them charged to ~4.2 volts.

As long as calibration data fits your device, you don't need to worry about it. Issues start when it doesn't fit. Most people are waking up to this after wiping their nand without any backup which results in complete lack of calibration data.
Fresh example:

After that no homebrew will help you. Dunno if porting from one similar unit to another can help and if it's possible at all. We know only that it's possible to fix this with I2C, but not permanently since this would need to run as sysmodule constantly in background.

---

Maybe I just worry too much and there won't be a need to do any replacement, just have it in mind when you see battery charging issue after emmc swap.

 

[xiran64]

As long as calibration data fits your device, you don't need to worry about it. Issues start when it doesn't fit. Most people are waking up to this after wiping their nand without any backup which results in complete lack of calibration data.
Fresh example:

View attachment 506210

After that no homebrew will help you. Dunno if porting from one similar unit to another can help and if it's possible at all. We know only that it's possible to fix this with I2C, but not permanently since this would need to run as sysmodule constantly in background.

---

Maybe I just worry too much and there won't be a need to do any replacement, just have it in mind when you see battery charging issue after emmc swap.

Oh, ok!

First time i´ve hear about it, but first the first!

Thx!

 

[l7777]

As long as calibration data fits your device, you don't need to worry about it. Issues start when it doesn't fit. Most people are waking up to this after wiping their nand without any backup which results in complete lack of calibration data.
Fresh example:

View attachment 506210

After that no homebrew will help you. Dunno if porting from one similar unit to another can help and if it's possible at all. We know only that it's possible to fix this with I2C, but not permanently since this would need to run as sysmodule constantly in background.

---

Maybe I just worry too much and there won't be a need to do any replacement, just have it in mind when you see battery charging issue after emmc swap.

Interesting, I got a unit with missing battery and completely failed emmc. Put in a used OEM battery and rebuilt the EMMC from a donor and it seems to be working correctly but I only really use it for tinkering. I'll have to pay more attention to it and see what voltage it charges to. It certainly displays 100% charge.

 

[xiran64]

New update:

Some erros:

 

[masagrator]

You didn't put all Hekate files on sdcard

 

[xiran64]

You didn't put all Hekate files on sdcard

Yep, that sd card works in another switch without problem

Some times, give sd read errors, like no sd card (this was bad conection, solved)

Post automatically merged: May 24, 2025

Battery, soc and emmc info, compared to a god console:

sdram_bad:0 vs sdram_good:12
Battery_info_bad:0 vs Battery_info_god:values
emmc_bad: no gpp data detected emmc_god: yes gpp data