-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downgrade Solution #20
Comments
Were you able to figure out an option here? Im shopping for a wallbox with the plan of immediately rooting it |
No way around... |
I, too, got a Pulsar Plus shipped with 6.1.12 (and it restores to that version after restore :/ ) There is a Raspberry PI Compute Module 3 inside the unit. Is there a hardware way of adding the key to |
I actually lucked out and received a unit from my local distributor with an older firmware. But I saw brief comments on a forum of a user removing the cm3, and transferring their own ssh key in place. I’m not sure on the exact process, but if you can mount the cm3 as an external drive on another system you should be good to go. |
I successfully rooted a 6.1.12-shipped wallbox using an external CM3 carrier board (BalenaFin). Here's how to do that: Then you'll need to install raspberry pi's git clone --depth=1 https://github.com/raspberrypi/usbboot
cd usbboot
make
./rpiboot You'll have a new block device available then - in my case it was /dev/sdf. Compute module's flash is partitioned into 3 partitions:
You'll need to mount the 2.6G partition to any folder. mkdir ~/mountpoint
sudo mount /dev/sdf2 ~/mountpoint
cd ~/mountpoint Now, add your key to echo "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDHVPVOodEfXLy1VhyC6LydiVNNIdZqNxvi6RH7SJXk771y0qEgbIarcMJIrwWWwI/2dq9aC8Z6lQP9BS2FVaAkdFrMVvE5Y+tT2EhIcCJUg1J8fO57StERnkk2RHJj7b/BqQ9SibRaRs48D7Q0upetsjSu6q6+COAtF6kSL5KiLgQ2z1Dnn86GkJ+HIRzd5SklMl7HgHI00J6RQFIjk1xx6wsWPt/xOxBxdTEbq854E77FwtMvqMLo1zClwK5Aj8Gho2jIkk8OcBII6yYkCVpVPoodzKgOEVzCjFFnMA724BSDYTAizsA38Lft9LU0rmQ3yz2Nn38ZmIinFbyp5T1L" > ~/mountpoint/home/root/.ssh/authorized_keys What's odd is that there's someone else's ssh key in there already: After that, unmount the CM3 and power down your CM3 carrier board (physically) You can now install CM3 back into Wallbox - it's fully rooted now. One note that I have is that in order to ssh into it, I needed to pass some ssh options - otherwise it would look like rooting didn't work. Here's my ssh connect command: Note that you do loose root access if you restore the unit to factory defaults, but you can do this whole thing again to re-gain root once more. It also looks that you can in theory turn your unit into a downgradeable one by swapping the .tar.gz in that 1G partition to a donor one, but I haven't tested that. |
Many thanks @toxuin for posting such a detailed set of instructions 👏 My Pulsar Plus is over 5 years old now and still going strong. Recently I pulled the front cover off and swapped the output cable from Type 1 to Type 2. I don't think the output terminals are that great and I do wonder how long my Pulsar Plus will last with more current going through it now. For this reason, I will probably avoid charging at the full 32 Amps unless I really need to. The top end of the output cable gets quite warm where it comes out through the case, whereas at 20 Amps, it's no warmer than the case itself. Fingers crossed my Pulsar Plus will last a few more years yet. However, in the case I need to buy a new charger, I would have no hesitation in buying another Wallbox Pulsar Plus, thanks to your excellent guide 👍 |
Just got a new WB pulsar plus with 6.2.13 version when I restore it. Is there any ways or hack to flash v5 on a new version?
I can't root it (stuck on receiving pwnware).
Thanks,
The text was updated successfully, but these errors were encountered: