-
-
Notifications
You must be signed in to change notification settings - Fork 2
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
Firmware not flashing #10
Comments
This is the one gig version of Bobcat? |
I had the same issue with my PX30. I was never able to get it to boot from SD. |
Yes, model MINER3001. |
An update: I decided to do some investigating using ADB: Turns out my model is not PX30-based, but RK3566-based! The label on the bottom reads MINER3001, yet it's the 2GB model. I'll try running the other image and see if that works. Some notes: By opening the device, you can access a microUSB port labelled 'USB_OTG'. By holding the recovery button as you insert the power cable, you can access an ADB debug shell that you can use to query system information (e.g. the CPU with |
So you mind posting a photo of the internal? |
Of course. Just a moment |
Yeah, tried with the RK3566 image and it's still just booting straight to the stock OS. |
Thanks! Yeah, this is fairly different looking than my PX30 |
I’ve tried every method on both versions and nothing. rktool says it completes fine, just bricks the device. Using SD on PX30 doesn’t work. I’ve tried at least 4 rk3566 boards all the same result, and two px30 boards. Hopefully you get somewhere with it! Keep us updated. |
2 gig version doesn't work at the moment. |
Did try a look at Crankk method ? i just installed for test Crankk Image on one of my Bobcat 295 which is 2GB version base on RK3566 - and it is working but there are issues with their firmware, so i hope that you can take a look over their method and make proper image for Bobcat 2GB version based on RK3566. |
Hi,
I've followed your instructions for flashing this firmware on the PX30 model, but it just boots up as normal.
I have:
It then just boots to the normal OS. Am I missing something?
Many thanks,
Josh
The text was updated successfully, but these errors were encountered: