Wondering if I need the MAC addresses of the pci ports? The lights on the ports also turn on, Orange to show it's a 1000mb connection, and the green power LED.īut it's stuck on solid, not flashing so that shows no communication is going on even though it's connected and powered. The PCI network card does appear in the BIOS, each port appears separately. But I'd rather not stress it anymore than necessary.But I dont want to use the card adaptor, I have a HP Gen8 microserver, which has a built-in microsd slot.īut yeah atm I am using the adaptor and it's values, though prefer not to.īut if sd cards dont have those values, I guess I can ignore that part of the setup then. Last thing I might try is to pull the image of the original SD again, in case it was faulty. freezefile to that moment, it would neither continue nor start, but just show me that never-ending hourglass. Maybe the downgrade process won't finish because the serial is checked in the process. The firmware-upgrade screen finishes, but afterwards it does not start. But it seemed like I could, downgrade the new SD with the cloned 5.20 image down to 5.14. I thought it might be because my fw image was at 5.20, but since the original SD is read only now, I don't want to risk a downgrade on it. Also found a screenshot somewhere that shows the hex value needs to be used. I was not sure if I was using the right SD serial (hex or binary value) using the "russian tool", so I tried both, but still no luck. Started all over for a third time, but no luck. Lots of zeros (and no O) but that seems correct. Double-checked I entered my devices serial correctly recreating the. freezefile and double-checked it was updated by checking the files timestamp and verified it did not change attributes. So I made a script for the PB writing out the external SDs serial:Įcho -e "$(cat /sys/block/mmcblk1/device/serial)" > /mnt/ext2/sd_ext_serial.txtĪnd used this with the "russian tool" to generate a patched. First time I messed up by using the original SDs serial, but as I understand it, with this method I need to use the new SDs serial. Next I tried the "new method" of patching and replacing the. That did not work of course, because as I read later on, this method does not support firmware 5.20. Then, reading this thread from the beginning, I tried "the old method" of reading out the original Sds serial and patching the monitor.app. but I rather think I'm probably just stupid.įirst thing I did was to create an image of the original SD. I ran firmware 5.20 when the card became read only and maybe that could be a problem. I have read the whole thread and also the translated instructions from the russian forum linked in #93, but so far I have not succeeded in saving my device. My PB626 was also affected by memory death a few days ago and so I found my way here. Hi all and thanks for sharing solutions to save those doomed devices Next time when I read the card the version I have uploaded recently is missing and instead the latest version is still there (probably the SD is read-only?!). The device is reproducing the latest update downloaded on the internal SD via Wi-fi. I've tried several times to upload older version of the firmware on the internal SD and to install it but without success. So now I'm unable to execute above instructions. Nhedgehog, you've done a great job! I have PB 624 and after firmware update over Wi-fi the touch panel stopped working. Monitor.app is copied into the same folder from cramfs. sd_original_serial with your CID is created in the root folder of the external SD. Run the app which is now available on the Pocketbook. Insert the prepared MicroSD into the Pocketbook. sd_original_serial & copy monitor.app from cramfs.Ĭopy the folder applications from the package (including SD_Prepare.app) into the root of this MicroSD. It will read the CID of internal SD, create the file. To make it easier here is a little app for that. Update to the new firmware (U626-) worked without any problems. Insert new SD card into internal SD card reader of PB and restart. # mount /dev/9 (mounting the 9th partition)ĥ. serial with your device ID (YT12345.) and CID of the new SD card (0x12345678) as shown in the post of zledas ² Linux run "make", switch to created serial folder and run. Copy the old SD card to you new SD card ((as root) # dd if=dev/old-sdcard of=/dev/new-sdcard)ģ. Download serial.app from nhedgehog, extract and place the application folder on your new SD card, plug it in your PB and run as instructed, you'll need device ID (YT12345.) and CID of the new, external(!) SD card (0x12345678).Ģ. But now it is all working and even better the firmware update worked, too!Īll steps simmer down to (assuming Linux PC):ġ. I have a Pocketbook T元 (Firmware U626 5.14) and suddenly the SD card was read-only (could not keep Wi-Fi password, firmware update failed silently). Thank you for sharing, you solved mine, too.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |