With all the random qhsusb_bulk hardbricks coming around, I've decided to create a thread to share debrick.img files just in case. You do not need to create this, but if you ever need it, you'll be glad you did.
EXPLANATION:
If you ever HARDBRICK your phone, which can be caused by flashing an incompatible ROM, bad bootloader flash, or anything, your processor will fallback into a mode called USB_BULK mode. In this mode, it will await an SD card with a special image flashed to it, called debrick.img, and boot to that. Once booted from the SDcard, it will await a firmware flash from a computer (download mode.)
However, this image needs to be specific to the bootloader version the phone was running before the hardbrick occured. That's why I've created this thread: people on different bootloaders can share their debrick images.
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
HOW TO USE ONE:
If you ever have the unfortunate luck of needing to use a debrick image, here's what to do:
-Download Win32DiskImager
-Put your microsd into your PC (yes you will need an adapter in some cases)
-Use Win32DiskImager to write the debrick.img to the SD card
-Take battery out of phone
-Put the SDcard into the phone and put the battery back in
-Do Vol Dn+Power+Home
-Your device should boot into Download Mode, and you should see "SDCARD MODE" at the top right
-Flash stock firmware using Odin
Downloads will be added to the 2nd post
Downloads
PB1 BOOTLOADER DEBRICK
PD1 BOOTLOADER DEBRICK (thanks @klabit87)
PLEASE SHARE YOUR OWN DEBRICK IMAGES! I WILL ADD THEM HERE
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
al50 said:
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
Click to expand...
Click to collapse
It is completely based on bootloader version. You can use "Phone Info - Samsung" to confirm before creating an image.
This is great would be nice if you could create Bod5 img for us who are still able to downgrade
Sent from my SM-G900V using Tapatalk
When I get a chance I'll make one for the OC4. Just want to be sure to do it correctly. Since I'm on UL OC4 Bootloader, PB1 firmware
Nandr0idC0nsumer said:
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card
Click to expand...
Click to collapse
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
ben_pr said:
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
Click to expand...
Click to collapse
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
[email protected] said:
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
200mb is all thats needed on sd.
Only for samsung devices.
Nandr0idC0nsumer said:
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
Click to expand...
Click to collapse
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
ben_pr said:
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
Click to expand...
Click to collapse
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Nandr0idC0nsumer said:
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Click to expand...
Click to collapse
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
Nandr0idC0nsumer said:
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
Click to expand...
Click to collapse
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
ben_pr said:
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
Click to expand...
Click to collapse
Good point. I will update the OP later. This is not my package btw
Nandr0idC0nsumer said:
Good point. I will update the OP later. This is not my package btw
Click to expand...
Click to collapse
My mistake; I thought you made the zip!
Nandr0idC0nsumer said:
200mb is all thats needed on sd.
Only for samsung devices.
Click to expand...
Click to collapse
Thanks
Sent from my SM-G900V using XDA-Developers mobile app
ben_pr said:
My mistake; I thought you made the zip!
Click to expand...
Click to collapse
Lol nope. Usually I like to have it all in the updater-script so I wouldn't have had a seperate script
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
akaplo said:
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
Click to expand...
Click to collapse
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Nandr0idC0nsumer said:
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Click to expand...
Click to collapse
See my thread. http://forum.xda-developers.com/showpost.php?p=67159556&postcount=14
Related
If you do, can you please do me a favor: Can you please copy the gzip executable to /sdcard and upload to this thread?
Boot into recovery and:
Code:
mount /sdcard
cp /sbin/gzip /sdcard/gzip
devsk said:
If you do, can you please do me a favor: Can you please copy the gzip executable to /sdcard and upload to this thread?
Boot into recovery and:
Code:
mount /sdcard
cp /sbin/gzip /sdcard/gzip
Click to expand...
Click to collapse
ignore sig. reflashed 1.3.1. when i cp /sbin/gzip /sdcard/gzip i get cannont stat /sbin/gzip no such file or directory
edit: i found gzip in /system/bin. just take off .txt extension.
Thanks for you efforts. But the problem is I need the static binary that was present in the 1.3.1. The one in /system/bin is a dynamic one and won't run (tried it already) in 1.4 recovery.
I need to figure out where did that static binary in 1.3.1 come from. That binary is 3 times faster in compressing than the one in busybox.
sorry i couldn't find it. did you try asking cyanogen?
david1171 said:
sorry i couldn't find it. did you try asking cyanogen?
Click to expand...
Click to collapse
He is on vacay until the weekend is over.
erissiva said:
He is on vacay until the weekend is over.
Click to expand...
Click to collapse
can you extract it from the update.zip?
i believe the link was
http://n0rp.chemlab.org/android/cm-recovery-1.3.1-signed.zip
edit: nvm its proly a .img inside. i believe theres an image unpacking tool out here, ill try and find it
B-man007 said:
can you extract it from the update.zip?
i believe the link was
http://n0rp.chemlab.org/android/cm-recovery-1.3.1-signed.zip
edit: nvm its proly a .img inside. i believe theres an image unpacking tool out here, ill try and find it
Click to expand...
Click to collapse
Thanks guys, you are awesome!
Hmm... [No Luck]
Devsk, I just scowered every recovery image that Cyanogen has released (using unpack.pl http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images) for the gzip file you mentioned, however, I saw no static-binary that you speak of.
(yes, I checked every image file, including the ones in the .zip update file that cyanogen released for 1.3.1)
I'm actually curious myself, and have begun searching JF's recovery images too... still no luck...
HOWEVER, and I'm not too keen on scowering... perhaps if you ask Cyanogen if he ever released a recovery image in one of his update.zip's... perhaps thats what you're looking for?! *ponders*
good luck! I think i'm going to check it out!
rikupw said:
Devsk, I just scowered every recovery image that Cyanogen has released (using unpack.pl http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images) for the gzip file you mentioned, however, I saw no static-binary that you speak of.
(yes, I checked every image file, including the ones in the .zip update file that cyanogen released for 1.3.1)
I'm actually curious myself, and have begun searching JF's recovery images too... still no luck...
HOWEVER, and I'm not too keen on scowering... perhaps if you ask Cyanogen if he ever released a recovery image in one of his update.zip's... perhaps thats what you're looking for?! *ponders*
good luck! I think i'm going to check it out!
Click to expand...
Click to collapse
when in recovery 1.3.1, what does 'which gzip' give you? I am not sure where that executable is being gotten but doing 'gzip -h' and 'busybox gzip -h' resulted in two different things in 1.3.1 but same in 1.4.
One question: is it safe to go back to 1.3.1 and switch back & forth? I need to figure where some of the executables are coming from and how come it can load the same dynamic executable in 1.3.1 but not in 1.4.
devsk said:
when in recovery 1.3.1, what does 'which gzip' give you? I am not sure where that executable is being gotten but doing 'gzip -h' and 'busybox gzip -h' resulted in two different things in 1.3.1 but same in 1.4.
One question: is it safe to go back to 1.3.1 and switch back & forth? I need to figure where some of the executables are coming from and how come it can load the same dynamic executable in 1.3.1 but not in 1.4.
Click to expand...
Click to collapse
yes, it is safe, the ONLY issue i've had is I cannot seem to be able to successfully edit a recovery.img and reflash it, it works, the only issue is I don' thave command I get the "A N D R O I D" when i try to use terminal at the recovery menu, (although everything works via adb)
I am on 1.4, I just downloaded ALL the Cyanogen.zips (I hope I don't overuse his bandwidth, I would feel so bad...) but I found no recovery images within his .zips,
try flashing a 1.3.1, (I'm not able to use my android phone, as I left it at work haha)
and trying which. just m ake sure you do a nandroid backup before you flash back to 1.3.1 (though I doubt it should make a difference)
Code:
IDEA!
try to mount all your partitions within the recovery command (from the phone, not adb).
type
# mount -a
(it'll error, don't worry its normal )
# exit
press enter, and then type "which gzip"
I think that its actually loading the /system/bin/gzip... which would make sense... but idk, can you give it a try?
*EDIT AGAIN*
ok, the reason for what I told you, is that I noticed that if you reset the terminal (exit, enter) its like re-adding the PATH to the shell, i guess? I'm still a wee bit new to linux, but I know how to search (or rather... scower)
Can Someone adb Pull The Triumph System Files And Send Them To Me? I Will IM My Email Address To You If Neccesary.
barnito at androidforums posted a stock 039 nandroid backup
http://androidforums.com/3036500-post178.html
it has system.img in there
Hello
I am here too, just can't post links yet, I backed up my Triumph without powering it on....
How do i extract the files from the system.img
souder14 said:
How do i extract the files from the system.img
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=961164
zurui said:
http://forum.xda-developers.com/showthread.php?t=961164
Click to expand...
Click to collapse
The system.img extraction keeps freezing and stopping could someone just adb pull their system folder and zip it then send it to me?
souder14 said:
The system.img extraction keeps freezing and stopping could someone just adb pull their system folder and zip it then send it to me?
Click to expand...
Click to collapse
I've got dd dumps of the entire MT "disk" and individual dd dumps of each partition. I also have tars of each file system.
I took the dd "images" prior to the first boot into the OS, by holding volume-down+power. That put me into the strange read-write boot loader mode. Then I connected the phone via USB to a linux box. Unfortunately, Ubuntu auto-mounted the phone "disk" and all the file systems which no doubt updated some file system timestamps, but I didn't change anything. I unmounted the file systems, took my dd images then mounted them again and tar'd them up. Then unmounted and rebooted the phone and activated it.
Unfortunately, I doubt I have enough karma to upload yet. Perhaps I can put them somewhere for you to download directly? PM me for the location. Sorry offer open to souder14 only, or someone else with enough karma to post them to xda.
Did you find an upload location? If so please share it.
Thanks
srmuc69
Hello I am trying to flash the factory image on to my Nexus 5 with the flash all option in the zip file and it keep going missing boot.img as seen in the picture and I am unsure what to do at this point cause I disconnect my phone and it does boot up in to android 4.4.4 but I need help here
hell I would let some one remote connect if that helps any lol
Buckii said:
Hello I am trying to flash the factory image on to my Nexus 5 with the flash all option in the zip file and it keep going missing boot.img as seen in the picture and I am unsure what to do at this point cause I disconnect my phone and it does boot up in to android 4.4.4 but I need help here
hell I would let some one remote connect if that helps any lol
Click to expand...
Click to collapse
1) "Stuck" is NOT a question. Please use descriptive thread titles
2) You haven't unzipped the image-hammerheadxxx.zip that contains the images :/
but I have I followed the instructions to a T and put all file in the folder under platform tools
Buckii said:
but I have I followed the instructions to a T and put all file in the folder under platform tools
Click to expand...
Click to collapse
Not sure what instructions you've followed. Either they're incomplete or you made a mistake. Like I said, your screenshot shows a zip file. You need to unzip that in the location that it is in now
picture
rootSU said:
Not sure what instructions you've followed. Either they're incomplete or you made a mistake. Like I said, your screenshot shows a zip file. You need to unzip that in the location that it is in now
Click to expand...
Click to collapse
This is now what I have done you were right but still missing boot.img
Buckii said:
This is now what I have done you were right but still missing boot.img
Click to expand...
Click to collapse
Just fastboot flash it then.
Link to guides in my signature.
I have similar issues. Mine complains that the archive doesn't contain boot.sig and recovery.sig, and then it fails to allocate space and the update package missing system.img.
Going to do it manually now to see if it works
Desca said:
I have similar issues. Mine complains that the archive doesn't contain boot.sig and recovery.sig, and then it fails to allocate space and the update package missing system.img.
Going to do it manually now to see if it works
Click to expand...
Click to collapse
Mine shows same as you, but just reboot and it is working
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
Try the tools in this thread . I used them last week to extract a build prop.
Just load up the system.IMG and drag the file from the system folder to your desktop.
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
daniel4653 said:
The tar file for Cricket has already been posted in the general section of ATT
Sent from my SAMSUNG-SM-G920AZ
Click to expand...
Click to collapse
I already downloaded that file.... I just need to extract the build.prop from the system.img which I already have. The thing is I am having trouble getting the build.prop
Sent from my SAMSUNG-SM-G920AZ
gmx1994 said:
I have the stock rom for the Galaxy S6 Cricket variant... I am having trouble in getting the build.prop from the system.img. I have tired many methods from other threads but none seem to work. Any suggestions or working ways to extract the build.prop from the system.img or any way to open up the .img file.
I am doing this to post the rom in the ROM WIP section for the root.
Click to expand...
Click to collapse
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
tiboric said:
I got your PM. Sorry for the late reply. I'm posting here in case someone else needs the info.
Download Ext2explore.
Extract to your PC.
Run as administrator.
In app: go to file - open image - (find your system image) and open
It will display your image in tree and folder view
Use either one (depending on your preference) (but your build.prop will be in the first view as its in the root of the system).
Right click the file/s you want to extract
Select save
Save your file.......profit
Hope this helps
Click to expand...
Click to collapse
When I try to open the file the program just closes and i go to the log and this is what it says.
Error Opening \\.\PhysicalDrive1. Error Code 2
No of disks 1
Scanning \\.\PhysicalDrive0
index 0 ID 7 size 976769024
Partition Table Error on C:/Users/giovany/Desktop/New folder (2)/system.img
Invalid End of sector markerBad Super Block. The drive is not ext2 formatted.
Drive is not right formatted.
solution for img extraction/fix here
Hi!
I'd like to know where the OTAs are stored in our M2. Anyone that hasn't done yet the update download, and that has Root permissions, can use this app to find where they're stored, and if possible, upload it and post a link to it.
Thank you!
Do you still needed the file, sir ?
FunSucker said:
Do you still needed the file, sir ?
Click to expand...
Click to collapse
Yep. It's for some research
I think, the app didn't work sir. After I wait 30 minutes, none of the files were copied to my storage. Then I try searching using manual method, I found one file, the file size is as large as my OTA update. The nama file is "update-package".
The file extension is not ".zip", in the folder recovery (internal storage). My estimate, the file extension .LZMA or .tar.LZMA or .zipx.
I've tried to extract and decompress in the PC (windows os) using some programs, but failed.
If you still need the file, I'll upload it now .
FunSucker said:
I think, the app didn't work sir. After I wait 30 minutes, none of the files were copied to my storage. Then I try searching using manual method, I found one file, the file size is as large as my OTA update. The nama file is "update-package".
The file extension is not ".zip", in the folder recovery (internal storage). My estimate, the file extension .LZMA or .tar.LZMA or .zipx.
I've tried to extract and decompress in the PC (windows os) using some programs, but failed.
If you still need the file, I'll upload it now .
Click to expand...
Click to collapse
Yes please! Thanks
oke, sir. when finished i will share the link.
Oke sir, check this out --> Google Drive
FunSucker said:
Oke sir, check this out --> Google Drive
Click to expand...
Click to collapse
Great, thank you very much!
Okay, so this is what I got:
The update zip refuses to be flashed in UBL devices. FOTAkernel system is broken after you open the bootloader, which leads us with an unused partition (but that's other thing). The recovery logs just say: WARN: Status Rooted, ERR: Bootloader is unlocked.
I've tried to force it using AOSP Recovery commands
Code:
echo 'boot-recovery' > /cache/recovery/command
echo '--update_package=/sdcard/update.zip' >> /cache/recovery/command
reboot recovery
But just got a big nope.
So, now time to have a look at it. I tried to unpack it several times but no luck. The reason seems to be, very probably, because this is a LZMA compressed file (as 7-Zip reported) but with 2 additions at the end (which corrupts the entire read of it): An unencrypted/uncompressed XML which points out which is the software available right now in the phone (<source>), and which is the version that is going to be installed (<target>), plus, some a weird <generation> section. This is the XML
Code:
<?xml version='1.0' encoding='ISO-8859-1'?>
<metadata version="3.3">
<product>
<manufacturer>Sony</manufacturer>
<model>D2302</model>
<hwplatform>msm8226</hwplatform>
</product>
<update>
<generation>
<version>1.1.2</version>
<date>2015-12-28T12:10:19Z</date>
<rb_version>7.0.15.117</rb_version>
<rb_ua_version>7.0.15.117</rb_ua_version>
</generation>
<source>
<software>
<revision>18.6.A.0.175</revision>
</software>
<customization>
<variant>1281-0464</variant>
<revision>R2C</revision>
</customization>
</source>
<target>
<software>
<revision>18.6.A.0.182</revision>
</software>
<customization>
<variant>1281-0464</variant>
<revision>R2C</revision>
</customization>
</target>
</update>
</metadata>
And, right after that, I can perfectly see a SIN header, so I isolated it and, looks quite similar to the FOTAkernel.sin included in FTFs (330613072905Z010U S1_FOTA0 ‚"0), I personally guess it's a very, very small ELF binary, by the size of it.
So, the problem now comes to isolate the 3 parts, the LZMA file, the XML and the SIN, separetly. After that, I think we can probably have a look insde them.
How about linux os? Can we unpack or decompress that file on linux os, sir? Do you have tried?
FunSucker said:
How about linux os? Can we unpack or decompress that file on linux os, sir? Do you have tried?
Click to expand...
Click to collapse
I've tried many tools and combinations (ext4, .img, etc) and none of them worked... I'll think more about it.