Post some pictures pleaseHi all. Rp 2040 firmware 2.67 flashes blue for a long time, then lights up white/blue and red. On firmware 2.73 there is also a long indication with a reset and at the end it looks like =** (eMMC init failure during glitch process). I tried different Chips and added resistors, but it didn’t help. hynix memory. Tell me how to fix it. Switch lite is working fine, loading into stock.
Post automatically merged:
Hi all. Rp 2040 firmware 2.67 flashes blue for a long time, then lights up white/blue and red. On firmware 2.73 there is also a long indication with a reset and at the end it looks like =** (eMMC init failure during glitch process). I tried different Chips and added resistors, but it didn’t help. hynix memory. Tell me how to fix it. Switch lite is working fine, loading into stock.
If you got =** while the switch could go to ofw (until goes inside the hos, not blackscreen), then its you're cmd/clk line is not solid. Need to check it.Hi all. Rp 2040 firmware 2.67 flashes blue for a long time, then lights up white/blue and red. On firmware 2.73 there is also a long indication with a reset and at the end it looks like =** (eMMC init failure during glitch process). I tried different Chips and added resistors, but it didn’t help. hynix memory. Tell me how to fix it. Switch lite is working fine, loading into stock.
Post automatically merged:
Hi all. Rp 2040 firmware 2.67 flashes blue for a long time, then lights up white/blue and red. On firmware 2.73 there is also a long indication with a reset and at the end it looks like =** (eMMC init failure during glitch process). I tried different Chips and added resistors, but it didn’t help. hynix memory. Tell me how to fix it. Switch lite is working fine, loading into stock.
Really impresive, this switch is asking for a clear/transparent case!
Nice! but why are you removing the fan?I'd like to thank @Dee87 for encouraging me to go non-adaptor. My very first reball-based OLED installation. Gotta say I'm pretty proud of this.
Thank you. The "power on" ribbon cable struggles to be put on and off with the fan being too close. It just became a habit to remove it during disassembly. I learned that from a great YouTuber I like to watch named Tvpartsworld.Nice! but why are you removing the fan?
If you insert the cable AS you're putting the MB down in the case (move screen\fan\controller ribbons out of the way) you can avoid the fan removal. Just 'another way'.Thank you. The "power on" ribbon cable struggles to be put on and off with the fan being too close. It just became a habit to remove it during disassembly. I learned that from a great YouTuber I like to watch named Tvpartsworld.
Thanks, how about my OLED installation without a dat0 adaptor? Pretty cool ha?If you insert the cable AS you're putting the MB down in the case (move screen\fan\controller ribbons out of the way) you can avoid the fan removal. Just 'another way'.
Thanks, how about my OLED installation without a dat0 adaptor? Pretty cool ha?
From datasheet:Hi @abal1000x ,
I've found an OLED which sometimes can glitch and sometimes cannot .. using an DAT0 adapter.. Continuity is good, but still throws dat0 error code.
Just want to know your opinion regarding bellow voltages and ranges test.
You can, when its powered on. Its pulled up, so the low bit is high voltage.Can we check it directly on the switch unit to know this specific unit values ?
Its safe if you know what you're doing.
Logically speaking, the glitch is not affected directly by the dat0.Hi @abal1000x ,
I've found an OLED which sometimes can glitch and sometimes cannot .. using an DAT0 adapter.
No, a hardware fault can be ruled out. I installed the chip as usual and the device had also started and I entered into Hekate. However, it got stuck after about 20 minutes when creating the Nand backup. The screen was full of graphic artifacts. I know that this happens when the DAT0 is not seated correctly, but after changing the DAT0 template, I got CFW = Blackscreen and OFW = Bluescreen.
Unfortunately, I also started the OFW before I changed the template. I therefore assume that the Nand is corrupted.
it got stuck after about 20 minutes when creating the Nand backup. The screen was full of graphic artifacts after this I got Black/Blue Screen. DAT0 Adapter was used.
As a bit of background, I directed him here, since I believe this thread has the most skilled people that can help him. Cheers!Not sure if this is the right place to ask - but do you guys know where I can find a trusted modchip installer for the OLED Switch in the UK?
Thanks
afaik @RiotRetroGaming is Uk Based So Hit him upNot sure if this is the right place to ask - but do you guys know where I can find a trusted modchip installer for the OLED Switch in the UK?
Thanks
About your issue.Did someone know how i can get my biskeys over IRAM ?
CFW (Hekate) = Blackscreen and OFW = Bluescreen.
Ums-loader via IRAM = Works (and I can also dump Nand.)
Firmware 2.75 maybe fix this issue too: