OESF Portables Forum

Model Specific Forums => Gemini PDA => Gemini PDA - Android => Topic started by: Martin Bryant on February 01, 2019, 02:33:50 pm

Title: Unable to flash Firmware
Post by: Martin Bryant on February 01, 2019, 02:33:50 pm
Hi,

My Gemini wouldn't boot after flashing. I've managed to get it to connect to the Flash Tool again but now it gives and error "Invalid ROM or PMT address".

 [ You are not allowed to view attachments ]

Don't wish to brick the thing, so any guidance on what to try next?

Martin
Title: Unable to flash Firmware
Post by: gidds on February 01, 2019, 04:27:41 pm
Bad luck :-(

Never seen that error myself, but the first thing I'd check is the scatter file: have you loaded up the same file you used to flash it in the first place?
Title: Unable to flash Firmware
Post by: Martin Bryant on February 02, 2019, 12:38:56 pm
Quote from: gidds
Bad luck :-(

Never seen that error myself, but the first thing I'd check is the scatter file: have you loaded up the same file you used to flash it in the first place?

No idea. I've made all the same choices and followed the same procedure, but can't guarantee anything.

Current state.

 [ You are not allowed to view attachments ]

 [ You are not allowed to view attachments ]

Really stuck now.
Title: Unable to flash Firmware
Post by: jakfish on February 02, 2019, 05:55:18 pm
Yeah, I'm at loss, too.

Maybe re-download everything (which will create a new scatter file) from on-line partition table and see if using all new files make a friendlier flash.

Jake
Title: Unable to flash Firmware
Post by: bloblo on February 10, 2019, 01:28:17 am
Quote from: jakfish
Yeah, I'm at loss, too.

Maybe re-download everything (which will create a new scatter file) from on-line partition table and see if using all new files make a friendlier flash.

Jake
For me it was that the partitioner will allow you to easily make a choice that'll spill out an invalid image: https://www.oesf.org/forum/index.php?showtopic=35571 (https://www.oesf.org/forum/index.php?showtopic=35571)

Maybe you ran into a similar issue?