Related
Unfortunatelly I haven't found any support for this watch (system img, or saved full Twrp backup, factory img...) to repair the softbrick. I have found the ota.zip file, but I can't use it because of the system7 error. I have a Twrp on my watch, but I can't find any way to restart my wach. I'm so sad because I can't use my watch.
me too. I stuck with the smaller model because I thought that it looked much better with my Nemesis leather cuff band than the larger model. But no one seems to have the original system image or a recovery I could use for it since I bricked mine. I've gone back to my Misfit Shine, which is not even close to being a smartwatch
Take a look to my thread, I uploaded a twrp backup, but for WI501Q (system+boot)
TWRP BACKUP
https://www.dropbox.com/s/6d51x7mkub6e5ag/TWRP-2016-03-08.zip?dl=0
matze19999 said:
Take a look to my thread, I uploaded a twrp backup (system+boot)
---------- Post added at 21:25 ---------- Previous post was at 21:16 ----------
TWRP BACKUP
https://www.dropbox.com/s/2dcjdeen58kz0qy/asus2.zip?dl=0
Click to expand...
Click to collapse
I downloaded the file and unzipped it. I booted to twrp recovery and used ADB PUSH to send the files to /sdcard/ on the watch. I then used Install in twrp to install the recovery and boot img files (there is no option in twrp to install system.img). After all of this I still cannot boot the watch, it goes to CSC Fastboot.
Am I doing something wrong?
Yeah, its a twrp backup file. Create a random backup ( for example only Boot.IMG ) in twrp. It will create a folder in /sdcard/twrp/ which is named XXXX-XXXX. Its different from device to device. In this folder you can move my twrp backup folder. Then reboot again to twrp. Now you will find a backup item in restore tab. Thats my backup
matze19999 said:
Yeah, its a twrp backup file. Create a random backup ( for example only Boot.IMG ) in twrp. It will create a folder in /sdcard/twrp/ which is named XXXX-XXXX. Its different from device to device. In this folder you can move my twrp backup folder. Then reboot again to twrp. Now you will find a backup item in restore tab. Thats my backup
Click to expand...
Click to collapse
Thank you for all the steps.
I tried the steps and I noticed that when I selected the restore option only BOOT was able to restore. So I looked at the backup that twrp made and the filenames were actually boot.emmc.win, recovery.emmc.win, and system.emmc.win. So I took your three files and renamed the img extensions to emmc.win extensions and moved them directly to the backup folder that twrp created. This allowed me to be able to select all three options for restore (boot, recovery and system). The restore completed without errors. However when I reboot the watch it continues to quickly show "Recovery Mode!" and go to "CSC Fastboot Mode!"
Am I still doing this wrong?
download the backup file again and test it
matze19999 said:
download the backup file again and test it
Click to expand...
Click to collapse
I downloaded it again using the same method I described earlier, but I get the same result.
I have the wren device WI502Q.
Backup file is only for sparrow
I guess this thread really does prove there is no support for wren, as the title states. Too bad..
Welp i'll just buy a new watch. My CAVS just won!!!! Wooooo!!!!!!
cland216 said:
I guess this thread really does prove there is no support for wren, as the title states. Too bad..
Click to expand...
Click to collapse
https://r3---sn-h0j7snel.gvt1.com/p...9A6B905E737F34D1021CDEC6AED82CB6617A&key=cms1
stock rom for small version
matze19999 said:
https://r3---sn-h0j7snel.gvt1.com/p...9A6B905E737F34D1021CDEC6AED82CB6617A&key=cms1
stock rom for small version
Click to expand...
Click to collapse
I get an Error 7:
"this device has omni_wren wren:6.0.1/MHC19J"
I updated the watch to MM before I bricked it. Where can I find MHC19J image?
I have a stock Wren on mm, you still need a backup?
couchlock said:
I have a stock Wren on mm, you still need a backup?
Click to expand...
Click to collapse
I am thinking of rooting and would really appreciate a backup just in case. I really would appreciate it and I know others would appreciate it as well.
I'll be off in a couple days. I'll post a link from my mega account when I get it.
https://forum.xda-developers.com/zenwatch-2/general/wi502q-how-unbricked-watch-twrp-backup-t3521916
Unbrick guide I made.
So what do you need a back up of and how do I make the backup. Sorry so long but I finally have time. And a PC again
I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Just off the subject slightly...but Eliminater74 already has a flashable zip (thought TWRP) for the 20J release. Its a 2 Part System.
Eliminator74's zip is modified. I want to take a 100% pure stock system.img (extracted from stock firmware) and put it into a zip that can be flashed in TWRP. When I say stock, that's what I mean. No root, no Xposed, no BusyBox, nothing. This has already been done for Lollipop on the v10, but I have MM. I have already explained why I want to do this. I'm currently looking into whether Superr's Kitchen can accomplish this.
He has a Fully Stock 20J release..just gotta read the thread..
AnonVendetta said:
I have a system.img file, which I extracted from a 20J KDZ. I would now like to convert it into a flashable zip. I have 2 reasons for this. One, I dont want to have to use LGUP to revert my phone to a 100% stock system. It is much easier to just flash a zip of the system partition. Two, I would like to get into modding and ROM development. I believe that it is best to start from pure stock and make changes from there, instead of basing your work off of something that someone else has already modded.
I found these threads but they're a bit old (Lollipop):
1. http://forum.xda-developers.com/lg-v10/development/lg-h901-stock-img-files-boot-recovery-t3238638
2. http://forum.xda-developers.com/tmobile-lg-v10/development/lg-h901-stock-images-device-restore-t3241170
In one of them a member provided img's for recovery, boot, and system. In the other thread flashable zips of these img's were posted. These are for the Tmo v10. So it's not a matter of whether it can be done, but how. What tools are needed?
I downloaded the zip from one of the aforementioned threads, deleted the boot.img, replaced his system.img with mine, edited updater-script, and zipped up the meta-inf and system.img files with 7zip. I also checked to be sure that the block to be flashed was correct, it is the same (even though my img is for MM). I tried flashing with TWRP, I immediately get an error code 6.
What should I do?
Click to expand...
Click to collapse
What tool did you use to extract the KDZ? I am trying to get a stock boot.img for the H901J build and I cannot seem to find it. I used the WindowsLGFirmwareExtract 1.2.5.0 release and all I see are a ton of .bin files and system.img. Is boot.img inside system.img?
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
AnonVendetta said:
@Sippi4x4man: I also used WindowsLGFirmwareExtract. Inside the KDZ there is a DZ and DLL file. Just extract the DZ, then you see lots of BINs. The system.img is split up (since it's around 4GB alone), but the tool can combine the pieces into one file. I was able to figure out how to manually flash the IMG, by running a dd command with TWRP's terminal emulator.
dd if=/external_sd/system.img of=/dev/block/platform/f9824900.sdhci/by-name/system
It takes a few minutes to finish, followed by a message that says no more space is available (I guess /system got filled up). I think when you dd anything you are copying both free and used space, since an IMG is usually just a (sometimes raw) disk image. TWRP will also initially say that no system is installed, I just ignored it, the device boots fine, everything is pure stock, no issues at all. System is mountable after subsequent boots into recovery. I used Magisk and the phh Superuser Magisk module to gain root without modding system partition, and the Magisk version of Xposed. But I would still like to create a flashable zip to automate this. If I figure it out I don't mind uploading it so the community can benefit.
As for the stock boot.img, I would imagine that the boot.bin inside the DZ is probably what you're after. The file size seems about right. However, I tried renaming boot.bin to boot.img and flashing from TWRP. Device wouldn't boot. So maybe there is some other conversion process that needs to be done. I can't think of any other way to obtain a pure stock boot image, extracting it from stock firmware seems like a sure way. If you ever figure it out then please provide a copy. Make sure it isn't patched by SuperSU, Xposed, Magisk, etc. I could maybe merge it into a stock zip.
Click to expand...
Click to collapse
It's been a while from this post... But I'm looking after the same goal you were and got the same error 6 trying the same things you described in your previous posts. Despite of these long 4 years, let me try: did you finally achieve to make the flashable zip with system.img?
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
AnonVendetta said:
I do not own an LG V10 anymore.....it is the most garbage phone I've ever had.
I now use SuperR's Kitchen to create flashable zip from system.img. Works like a charm every time. Downside is that you need a PC to use it. It works for all phones (but you must also have an unlocked bootloader and custom recovery, or you will not be able to flash the zip). There are both free and donate versions, both will work fine.
Click to expand...
Click to collapse
Thank you for your reply. My device is Lenovo Z6 Pro but I thought this wouldn't make a difference.
Just to be sure, what you get with SuperR's Kitchen is a zip including system.img file and not the /system folder, right? Thank you in advance.
Edit: I had tried with other kitchen softwares with no success but SuperR's Kitchen did the job as you said, like a charm. Tons of thanks.
@descarao81: No, SuperR's Kitchen does not include system.img/boot.img, you must provide them yourself. They are device-specific. And system.img is a very large file, so it cannot reasonably be included in the Kitchen zip.
Yeah, maybe I wasn't clear, I meant if the resultant zip would include those raw image files being the original image files provided by the user. It's clear now. Thank you.
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Upytry2 said:
Here is how to do it...
1. Go to:
https://forum.xda-developers.com/tm.../lg-h901-stock-images-device-restore-t3241170
Download from the link he provided.
2. Extract the .zip file that you downloaded.
3. Make a new folder called "rom"
4. Copy the META-INF folder from the folder you extracted and place it into the "rom" folder.
5. Download any other flashable rom for your device. Extract it.
6. Go to {EXTRACTED_FLASHABLE_ROM}\META-INF\com\google\android\update-binary in your flashable extracted rom folder. Copy the "update-binary" . Got to the "rom" folder and go to META-INF\com\google\android. Delete the update-binary there and replace it with the one you have copied.
7. Now copy the boot.img from the other rom that is for your device. And place it into the "rom" folder.
8. Now Finally Compress the all the files.
9. Now you will have a flashable system.img.
10. Go to TWRP and flash the .zip that you have just made!
Click to expand...
Click to collapse
Trying that exactly when im home! Thank you!
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Downunder35m said:
While trying to create my first ever Android firmware I had solve several problems, especially if you consider that I prefer under Windows instead of Linux.
I won't go into too many details as I have to assume everyone attempting this did at least some reading on the general how to of firmware installations and modifications.
Things you need:
Original firmware for your device as a IMG file
Amlogic's Customisation tool
A Rom Kitchen of your choice (I use Carliv)
System_Extractor-WIN-master
Some time...
Step1: Load the firmware into the AML tool and tick all boxes except the last one.
In the tmp folder you will find the unpacked files.
Under Level one are the files we want.
You will see a bunch of "PARTITION" files, we copy the following ones into a seperate folder for further use to create the ZIP.
I suggest to name the folder "Install" so we are all on the same page here.
boot.partition
bootloader.partition
logo.partition
recovery.partition
If you checked a flashable ZIP update before you will notice some files are missing, let's try to fix that.
Rename all partition files you copied to img, so instead of boot.partition you get boot.img.
Unpack the boot.img with your kitchen.
You will find a file "boot.img-second" - copy that into your install folder and rename it to dtb.img.
Inside the unpacked ramdisk (In your kitchen) of the boot.img you will fing the "file_contexts" file - copy that into your install folder as well.
Most AML firmware I had so far used a system.new.dat and a system.transfer.list to create the system partition.
We can create them from the system.partition file after renaming to system.img in System_Extractor-WIN-master .
To do this the system.img needs to be unpacked and we need again a copy of the file_contexts.
After the image is unpacked we can pack it again as system.new.dat and system.transfer.list.
The last missing bits can be tricky though as now we need a META-INF folder that works for our device in question.
There are two way to fix that.
Method one:
Search the usually chinese websites using Google to find original firmware for your device.
Chance are that you will find something like an OTA update - in there you will find what you need.
Method two (I never tested that):
Take the META-INF folder from an OTA update of a box with identical hardware specs.
Most important part here is the memory configuration so for a 2/16GB box you need a 2/16GB OTA update.
Next of same importance is the WiFi/Bluetooth config.
If you only have Wifi than an update for a box With daul wifi and BT4.0 won't help you.
If the actual Wifi chip is a different one but CPU, GPU, Memory and connections are the same it should still work.
Once you have the META-INF folder included into your Install folder the firmware is ready to be zipped - in theory!
The X96 for example uses a hash check for the update and created system partition.
To be able to flash your image you need to know what the original recovery would expect - has check or not.
The updater script within the META-INF folder needs to be updated to match your build.prop details as well hash check/no hash check.
Again, with an original OTA update you will find these infos.
Only if you don't have the OTA and no clue what your updater script and recovery needs you are a bit lost.
I know I has not all the steps in detail and if you are without and OTA update you need to search but otherwise feel free to ask and I will try to assist to make it complete if I can.
Click to expand...
Click to collapse
Thank you for this explanation, but the explanation of the video to better understand everyone
Will see if I can at least add some pics while working on Nougat.
Hello,
Thanks for you tutorial.
I have a h96 Pro+ and the last firmware was a .img file... (Link of the firmware : https://mega.nz/#F!d1tHVZgA!Qc0mAom7FBHT9HDv3rGtGQ )
Is there a good guy who can convert this .img to a .zip file please ?
A lot of users are asking for this, me too and if you can help me to do this it will be really cool and appreciate
Thank you,
Carmin.
Thanks for your explanation im trting to port 7.1.1 to my tv box and i have found one funcional the only troble is the wi fi drivers not working ill give it a try latter today
Sent from my SM-N9300 using Tapatalk
I'm trying to root my M5 (SHT-W09, C567). I have unlocked the bootloader and installed Magisk but am having problems extracting and patching the ramdisk.img file. I would appreciate anyone who could double check my steps or see if they spot my error.
Here is what I have done.
1) Using HFF, downloaded, the Update.zip file (full image), size is approximately 4 GB.
2) Copied image over to Windows laptop
3) Downloaded Huwei Image Extractor
4) Set image extractor to unknown profile
5)Under settings, unchecked verify header and file checksum
6) The extractor extracted 33 files
Here is where I need assistance, how do I proceed? Do i need to .zip the ramdisk file and then copy it over to the tablet? I've attached an image of the files that were extracted. Any assistance would be appreciated.
Thanks,
Rick
@C5Longhorn you can now select the RAMDISK.img entry from that bundle and extract it to your PC. Then you copy that file by e.g
adb put RAMDISK.img /sdcard/
onto your device. Then you need to open Magisk-Manager (which you should have already installed on your device) and seldct the RAMDISK.img from /sdcard/ and a patched_boot.img will be created. This is the file which you later on need to flash back onto your device as ramdisk.img
AndDiSa said:
@C5Longhorn you can now select the RAMDISK.img entry from that bundle and extract it to your PC. Then you copy that file by e.g
adb put RAMDISK.img /sdcard/
onto your device. Then you need to open Magisk-Manager (which you should have already installed on your device) and seldct the RAMDISK.img from /sdcard/ and a patched_boot.img will be created. This is the file which you later on need to flash back onto your device as ramdisk.img
Click to expand...
Click to collapse
Ok, i copied the file to my computer desktop, and then attached device to computer and I copied into my SD card download folder but kept getting an error when I would run Magisk that it failed.
Do I need to use adb to push the file or does it not matter how it's copied. Maybe I'm placing in the wrong folder or need to zip file.
I'll try again and screenshot the messages. I really appreciate your help.
Sent from my Pixel 2 using Tapatalk
@C5Longhorn how you copy the file to your device doesn't matter. Do you have Magisk-Manager installed? Did you select the patch option and did you choose patch boot file and did you select the RAMDISK.img as the file to be patched? What is the error message Magisk-Manager is giving you? Did you use MagiskManager-5.7.0.apk?
Yes, to all. I'll capture and post the error I'm receiving when I can get back to the tablet. Thanks again.
Sent from my Pixel 2 using Tapatalk
I finally got it. I zipped the ramdisk file, moved it to Dropbox and then downloaded it locally to the tablet. I then went through the Magisk Manager process and it created the patched file.
I'm rooted now but notice I can't open Magisk without the app closing very quickly afterwards.
Is this normal? Also, I noticed "preserve AVB 2.0/dm-verity is not checked. Should it be?
Sent from my SHT-W09 using Tapatalk
I wiped the Magisk app data and now the app will open.
Sent from my SHT-W09 using Tapatalk
If run MagiskManager - run 1..2 second - self-close : it's a bug.
The new Version is 5.8.0 and i hope it's debuged.
The Bug is a optical Problem, root work.
Can version 5.8 be installed without losing root or do you have to repush the patched file again?
Sent from my Pixel 2 using Tapatalk
I installed 5.8 Magisk Manager and did not have to reload ramdisk image file.
Sent from my SHT-W09 using Tapatalk
2 Way for install Magisk
Way 1 : the device is new and TWRP is not available
download your build, extract "ramdisk.img" and copy on device (example: to "download")
download MagiskManager.App (actual 5.8.0), install, run and let MM modify the boot.img (in OREO is inside ramdisk.img)
fastboot flash ramdisk patched_boot.img
Way 2 : install "twrp_p10_0.1.img"
fastboot flash recovery_ramdisk twrp_p10_0.1.img
boot to recovery (TWRP) and TWRP-Install Magisk-v16.0.zip (actual)
this 2 way work on my device CMR-AL09 8.0.0.161(C432)
i use way 1 if device new on market and twrp not available
if twrp available i use way 2
the core-question is : the build from your device
extract from your-build full-update "ramdisk.img"
All Huawei/Honor with OREO have the same OS, but the build is different
HI,
I would like to update my mediapad to the latest update available.
However, you can't update through the official updater when you're root.
Can i flash back the original ramdisk.img and do the official update, then root it back with the new ramdisk.img patched ?
Tanogeek said:
HI,
I would like to update my mediapad to the latest update available.
However, you can't update through the official updater when you're root.
Can i flash back the original ramdisk.img and do the official update, then root it back with the new ramdisk.img patched ?
Click to expand...
Click to collapse
Normally when there are changes on the ramdisk.img a full update image will be installed by the OTA update process. Your proposed way will be probably sufficient to get only the delta update.
Hey all. Currently working on my Moto One 5G Ace. Bootloader unlocked, have achieved root.
However, since Android 10 has this messed up file system that does not allow any writing of the system files, I want to know what tool can I use to Unpack Super.Sparsechunk files and then repack them so I can flash them as stock via fastboot. All I want to do is delete the stock ringtones on this phone and replace them with my own .ogg files (as I've done on every Moto I've ever had). Thanks.
Use simg2img, then lpunpack to unpack it.