Thread: Alpha 100 US in EU, problems after fw downgrade & cure used

Well, it's difficult to know for sure that it made no difference because the device has Cure firmware loaded and cure fw isn't meant to boot in fact it's intentionally made so it doesn't boot the device fully.

Knowing that the Alpha can't read from the card isn't totally unexpected however given what's happened to it. It simply isn't getting far enough into the boot process to execute Ldr.bin in the 1562 folder.

Let's try with a modified boot.bin as RGN flashed in preboot to run the txt commands:

• Remove Ldr.bin from the 1562 folder of the microSD card (very important), leave only Update.txt file in the 1562 folder.
• Insert the card into the Alpha and ensure it's off with the battery charged.
• Behind the spoiler below is 156201000300.zip, extract it to find 156201000300.rgn and save it somewhere convenient on your PC, the desktop is fine.
• Open the RGN in Updater.exe and leave it's GUI open and visible with the radio button next to 'USB Device' enabled.
• Plug a 'known-good' USB cable directly into a rear USB2 port of the PC. Put Alpha in preboot and immediately connect the USB cable to it and when you see the device details in GUI's window very quickly press 'OK' or just hit 'Enter' key on PC's keyboard.

When 'Loader' appears on screen you should be ok to release the button, or for safety hold it until the device tries to re-boot signalling the end of data transfer to the card. Hopefully it holds preboot long enough to initiate Update.txt.

Spoiler:

[Only registered and activated users can see links. ]

This method doesn't rely on the device fw initiating to start Ldr.bin so it is more likely to work to dump region contents. Good luck!

Hi
I followed the instructions.
Everything went OK, including entering the preboot mode.
Then, when I pressed the OK button on the Updater.exe, the following message appears for couple of times.

Spoiler:

[Only registered and activated users can see links. ]

Then, after a couple of times, the following message appears. It appears that Updater.exe recognizes v3.2 of the fw in the device, and asks if I want to put an older version instead.

Spoiler:

[Only registered and activated users can see links. ]

When I press Yes, within miliseconds, the picture below appears, and it shows the bar to be full 100%. In the meantime, the screen on the device, first goes OFF, then shows LOADER text.

Spoiler:

[Only registered and activated users can see links. ]

Then, the next message appears saying that the update was successful, all the while, the screen still shows LOADER text, and is stuck on that. I remove the USB cable, and it still continues to show LOADER text. When I press the OFF button, the screen goes black (NOT OFF), and then goes off. If I press OK, the Updater.exe turns itself OFF, but, the screen on the device continues to show the LOADER text.

Spoiler:

[Only registered and activated users can see links. ]

When I allowed the device to connect to the PC, I found out that only 48 .bin files have been copied to the SD Card. All but 9 of them are “empty” (0 KB). Those 9 are of different size in KB. The file named 48.bin is the biggest, but its size changes with every attempt as Updater.exe tries to write to disk.
So, I decided to leave the device connected to Updater.exe even as the message reads that the update was successful, and even though Updater.exe has shot itself OFF. I am waiting for the LOADER text to disappear and/or something else happens to the screen for over 20 minutes now, and nothing new is happening.
The Update.txt file shows there are 255 .bin files to be copied, so, I decided to leave the device, and get back to it after a while. I will update afterwards.
Thanks for your patience.