That depends. Have your antidepressants kicked in yet?should I feel happy yet?
0.1mm works great for this size soldering. Do make sure that your soldering tip is the right size, most people try to do this type of soldering work with an iron tip that is WAY too big, and solder that is awful for the task. Use some thin lead or bismuth solder, something with a low enough melting point that you won't risk knocking other components off the board if you're not super good. Your solder should melt low enough that you can easily solder non-ground points at 280-300 Celsius. Invest in paste or no-clean flux.What thickness do you recommend? 0.1mm, 0.5mm?
can you show the source code of the project?I found long press VOL- & VOL+ boot original HOS
Can play games
I use this diagram
yes and noSo there is working firmware now?
Any way you could tear the custom BCT from an eMMC dump?Either is fine 0.5 is easier to work with though as it's abit thicker
Hello everyone.yes and no
current fw boots hekate, linux, android
current fw retuns error when launching hos
doesnt work.
Given the seeming lack of context before it being posted and the very obvious pico ID in the file name, I'd hazard a guess it's meant for the ID in question.doesnt work.
blue led...then red led like the original firmware dump we had
im fully aware...but no doubt people where going to ask me anyway and for the sake of spending 2 minutes to test...Given the seeming lack of context before it being posted and the very obvious pico ID in the file name, I'd hazard a guess it's meant for the ID in question.
Fair enough; I don't know offhand what people do and don't know and it's hard enough trying to parse info out of here.im fully aware...but no doubt people where going to ask me anyway and for the sake of spending 2 minutes to test...
Considering 'original' here, I'd assume this is that the "Ubuntu-only" firmware bypasses running a payload if the combination is held? I'm very unsure what to take away from this but that's the best I can try to grasp.I found long press VOL- & VOL+ boot original HOS
Can play games
I use this diagram
0x100012c2 in ?? ()
(gdb) x/s 0x200259C8
0x200259c8: "\346aA\004\003y\247\071W\003"
(gdb) x/8x 0x200259C8
0x200259c8: 0xe6 0x61 0x41 0x04 0x03 0x79 0xa7 0x39
(gdb)
100043c4 <_retrieve_unique_id_on_boot>:
100043c4: b510 push {r4, lr}
100043c6: 4802 ldr r0, [pc, #8] ; (100043d0 <_retrieve_unique_id_on_boot+0xc>)
100043c8: f000 f80c bl 100043e4 <flash_get_unique_id>
100043cc: bd10 pop {r4, pc}
100043ce: 46c0 nop ; (mov r8, r8)
100043d0: 20000628 .word 0x20000628
100043d4 <pico_get_unique_board_id>:
100043d4: b510 push {r4, lr}
100043d6: 2208 movs r2, #8
100043d8: 4901 ldr r1, [pc, #4] ; (100043e0 <pico_get_unique_board_id+0xc>)
100043da: f7ff fd43 bl 10003e64 <__wrap___aeabi_memcpy>
100043de: bd10 pop {r4, pc}
100043e0: 20000628 .word 0x20000628
undefined FUN_10002608() -- _retrieve_unique_id_on_boot
undefined r0:1 <RETURN>
FUN_10002608+1 XREF[0,1]: 10016b48(*)
FUN_10002608
10002608 10 b5 push {r4,lr}
1000260a 02 48 ldr r0,[DAT_10002614] = 200259C8h
1000260c 00 f0 0c f8 bl FUN_10002628 undefined FUN_10002628()
10002610 10 bd pop {r4,pc}
10002612 c0 46 mov r8,r8
DAT_10002614 XREF[1]: FUN_10002608:1000260a(R)
10002614 c8 59 02 20 undefined4 200259C8h <-- ID IS STORED HERE!
**************************************************************
* FUNCTION *
**************************************************************
undefined FUN_10002618() -- pico_get_unique_board_id
undefined r0:1 <RETURN>
FUN_10002618 XREF[1]: FUN_100169bc:10000714(c)
10002618 10 b5 push {r4,lr}
1000261a 08 22 movs r2,#0x8
1000261c 01 49 ldr r1,[DAT_10002624] = 200259C8h
1000261e ff f7 9f fe bl FUN_10002360 undefined FUN_10002360()
10002622 10 bd pop {r4,pc}
DAT_10002624 XREF[1]: FUN_10002618:1000261c(R)
10002624 c8 59 02 20 undefined4 200259C8h <-- ID IS READ HERE!
I've noticed using this thin enameled wire that you pick up crosstalk from other magnetic fields and get the wrong data.Either is fine 0.5 is easier to work with though as it's abit thicker