Database Info

Request for radio.img of MZ601

I am trying to convert a MZ600 to MZ601.
I assume there are no actual hardware differences, but only software.. and I have not found any sources/info proving otherwise...
I have allready fastboot-flashed system/user/boot/recovery of MZ601 Europe stock images, to my VZN MZ600 Xoom and everything works fine except the mobile-network ofcourse...
(btw SIM is working!)
So how can I flash the baseband to the European one ?
Is the radio.img all I need ?
In that case, can somebody send me one?
I have tryied a full EU firmware flash with RSDlite, but I get an error "Unable to retrieve initialization values from INI file." so I cant start flashing...
Any ideas?
Thanks

I saw in other thread you have gsm sbf, perhaps using sbf recalc or sbf depacker you can extract its radio image..
please check this link
http://modmymobile.com/forums/402-general-motorola-android/530781-sbf-depacker-1-3-03-22-2011-a.html
http://and-developers.com/sbf

I thought the recovery / img files were on motorola's website now?

Thanks lesjaw , I will try..
(I did a search for sbf extractors but did not find those ones! )
Lothaen , motorola gives away the common partitions, (userdata/system/boot/recovery) and not the hardcore ones such as the radio one!

lesjaw, I tried both software. They both allow me to split files, from the SBF.
That results into 13 SMG files, which I assume are partitions (and something else?)
What format are these ? can I open them ? How do I identify the radio.img
is the IMG format same as SMG ?
MotoAndroidDepackerMono, has an option to extra radio.img, but thats from an update.zip, which I what I am trying to create

i see, honestly I never use those app, in sunday i'll give a shot..
btw, you can join #milestone-modding in freenode (irc), many of those members channel have good experience regarding sbf file..
good luck brother..

Any idea anyone, how to identify the radio image, from a SBF extract to SMG files ?
Once identified, can I use an SMG file as a "radio.img" ?

HMJ37 sbf
Motorola did just release a few days ago a new sbf for the MZ600 that is the full HMJ37 version. Here is the full file name out of the latest spreadsheet for anyone with RSD access:
VZW_MZ600_Signed_HMJ37_Signed_MDM6600BP_C_02.0F.00R_SW.combo.sbf

I think he needs an image from MZ601, not MZ600!

its been quite some time, and have not yet found an answer to this problem!!..
attached is the export from the SBF file of MZ601
I asume one of these files, is the radio.img , correct ? which one is it?
Can I do a fastboot flash radio radio.img ,using one of these files!?
Is it safe to try with the user partition to confirm my theory ? (I can identify it, from the byte size)
I tried to open the images with unyaffs-x86-win and cygwin but I always get an error message "broken image file" even on motorola's official images, hence I've got something else wrong (?)
So many questions left unanswered for so long! and I though XOOM was for hardcore android users!

nikil511 said:
its been quite some time, and have not yet found an answer to this problem!!..
attached is the export from the SBF file of MZ601
I asume one of these files, is the radio.img , correct ? which one is it?
Can I do a fastboot flash radio radio.img ,using one of these files!?
Is it safe to try with the user partition to confirm my theory ? (I can identify it, from the byte size)
I tried to open the images with unyaffs-x86-win and cygwin but I always get an error message "broken image file" even on motorola's official images, hence I've got something else wrong (?)
So many questions left unanswered for so long! and I though XOOM was for hardcore android users!
Click to expand...
Click to collapse
Are you sure that's from a MZ601 and not a Wi-Fi only MZ604 (see the "HUBBLE" and "WIFI" strings)?
You cannot fastboot flash the radio partition (which probably is called something like bpsw given this is a Motorola device). Given that these are proprietary firmware blobs, do not expect to get far assuming that these are yaffs/ext/whatever filesystem images.

thisi is where i found the SBF
http://www.mod2xtreme.com/showthread.php?t=10571
so I assume it has the radio partition.
So if I can not extract it from the SBF, how are all these baseband update zip been constructed on all other tablets/phones ? why are there none for XOOM eventhout various baseband versions exist ?

or this h.6.2 means that should be for mz604(wifi only) so it should contain no baseband image. ?

convert mz600 to mz601
hello all,
nikil511 , did you found any solution? i'd really like to convert my mz600 to mz601 !

concerning the sbf, because of the name we know it's from the wifi xoom.
but as info, the radio is cg5
regards

http://sbf.droid-developers.org/everest/list.php here new full image
in amms_sec.mbn
we can find string for new firmware VTHUBBLE_N_01.100.07P
or in rdl1.smg ..
how to use it? or convert to .img in .zip file ?

i do it
http://forum.xda-developers.com/showthread.php?t=1845212

Pit File Required - GT-P6810 WIFI (32GB)

Hello All,
Just wondering if anybody happens to have a .pit file for the 32GB wifi version?
Let's just say I didn't read instructions... and my tab is showing as a 16GB instead of 32.
Require a 32GB version pit file for the GT-p6810 to re-partition and get it back to normal.
Thanks in advance

bangkenny said:
Hello All,
Just wondering if anybody happens to have a .pit file for the 32GB wifi version?
Let's just say I didn't read instructions... and my tab is showing as a 16GB instead of 32.
Require a 32GB version pit file for the GT-p6810 to re-partition and get it back to normal.
Thanks in advance
Click to expand...
Click to collapse
Hi, usual disclaimer - use at your own risk. Here's why:
1) I extracted this from mine with heimdall, it is a binary so I have no idea if it extracted correctly.
2) I never flash pit, so this has never been used.
Suggest you compare with another poster before using.
Including the text version (also extracted from same device with heimdall) so you can see what is supposed to be in the binary.
Hope it helps

davp said:
Hi, usual disclaimer - use at your own risk. Here's why:
1) I extracted this from mine with heimdall, it is a binary so I have no idea if it extracted correctly.
2) I never flash pit, so this has never been used.
Suggest you compare with another poster before using.
Including the text version (also extracted from same device with heimdall) so you can see what is supposed to be in the binary.
Hope it helps
Click to expand...
Click to collapse
You are a legend. Worked like a treat, I've got a '32GB' tablet again.
Thank you so so much for your help. I'd buy you a beer if I could

Glad it worked! Enjoy your tab.
Cheers

davp said:
Hi, usual disclaimer - use at your own risk. Here's why:
1) I extracted this from mine with heimdall, it is a binary so I have no idea if it extracted correctly.
2) I never flash pit, so this has never been used.
Suggest you compare with another poster before using.
Including the text version (also extracted from same device with heimdall) so you can see what is supposed to be in the binary.
Hope it helps
Click to expand...
Click to collapse
Please help me, Pit for P6800 32GB.

davp said:
Hi, usual disclaimer - use at your own risk. Here's why:
1) I extracted this from mine with heimdall, it is a binary so I have no idea if it extracted correctly.
2) I never flash pit, so this has never been used.
Suggest you compare with another poster before using.
Including the text version (also extracted from same device with heimdall) so you can see what is supposed to be in the binary.
Hope it helps
Click to expand...
Click to collapse
Hi, I was wondering if it is this file (but then the 16GB version) of the pit-file that I should use and change in orde to increase my system memory?
If so, how do I get the correct pit file for my device, and how do I change it ?
Any idea's (or is my idea a stupid one ? it's just that my device is hellishly slow because the system mem is Always so low...)

Felica is valid scl22, Custom Image

It is a system image to root of odin in the SCL22 of Japan.
Su is enabled at startup.
System status is official.
Felica is enabled.
Custom Image v1 is Here.
http://www1.axfc.net/u/3168553
Custom Image v1.1 is Here.
http://www1.axfc.net/u/3172168
XDA:DevDB Information
Felica is valid scl22, Custom Image, a ROM for the Samsung Galaxy Note 3
Contributors
dolphin_fune, dolphin_fune
Version Information
Status: Testing
Created 2014-02-11
Last Updated 2014-02-15

Reserved

dolphin_fune said:
It is a system image to root of odin in the SCL22 of Japan.
Su is enabled at startup.
System status is official.
Felica is enabled.
Custom Image v1 is Here.
http://www1.axfc.net/u/3168553
Custom Image v1.1 is Here.
http://www1.axfc.net/u/3172168
XDA:DevDB Information
Felica is valid scl22, Custom Image, a ROM for the Samsung Galaxy Note 3
Contributors
dolphin_fune, dolphin_fune
Version Information
Status: Testing
Created 2014-02-11
Last Updated 2014-02-15
Click to expand...
Click to collapse
This Mod is Update.
ver1.1 is Here.
http://www1.axfc.net/u/3172168

What the hell
Sent from my SM-N900T using Tapatalk

Hi,
I also interested in this rooting method. However, the link for v1.1 seems to be invalid. Please check.
Thanks!

i have SCL22
what is this thread all about
can anyone explain

niranjan.anu said:
i have SCL22
what is this thread all about
can anyone explain
Click to expand...
Click to collapse
SCL22 rooting, the custom image maintains working NFC (NFC in Japan market is different with international market, as it is involved in mobile payments). You will need to flash the custom image via Odin, but you'll lose all of your data.
---------- Post added at 10:24 AM ---------- Previous post was at 10:03 AM ----------
dolphin_fune said:
Custom Image v1.1 is Here.
http://www1.axfc.net/u/3172168
Click to expand...
Click to collapse
Hi again, it seems that the link for your v1.1 is corrupted. Also, KDDI has updated their firmware version to SCL22KDUBNB1. Could you please provide any rooting information about this new version? Thanks in advanced!

There is no link of v1.1. I am sorry. Nb1 even can make an effective system of felica. For more information, please contact github.com/rara7886/make_rooted_system-rara7886[/url].
Thx.

dolphin_fune said:
There is no link of v1.1. I am sorry. Nb1 even can make an effective system of felica. For more information, please contact github.com/rara7886/make_rooted_system-rara7886[/url].
Thx.
Click to expand...
Click to collapse
Thank you very much for your reply. However, I don't understand Japanese, it also takes a huge amount of time to learn it
So could you please help to translate those instructions in the git repository to English? We are very grateful if you provide us a translated version.
I also have one more question to ask, if I flash custom recovery/kernel to SCL22, FeliCa won't work; does this affects NFC too? Then after I re-flash stock recovery/kernel, will FeliCa & NFC work again?
Thank you very much for your time!!!

Anyone tried to install this? Does it work?
Sent from my SCL22 using xda app-developers app

SCL22 AU - Got Root. I'll help if I can ....
The long story that is my SCL22 (AU) successful root. I’ve been trying for months and doing lots of reading but I did not want to trip the Knox fuse so I kept waiting. Last weekend I went at it hard. I blended a couple of threads together and will try to explain below so the rest of you can try it.
1) I tried lots of ROM downloads but some were broken and some were for the SC-01 (Docomo) which I was reluctant to try. I also installed and reinstalled SU several times but I think I could have just installed it early and left it.
2) I downloaded the “make_rooted_system-rara7886-master” and figured it out. I eventually had to correct line 274 of the .sh file where the word "install" was spelled wrong. I got the system.img.ext4 and cache.img.ext4 output in a nicely wrapped .tar file named . (See step 8) I ran it in Ubuntu 14.04 but it took a little doing. You will need to SUDO it and when it is working you will see the BusyBox and other files copying. When there are no errors, you’ve got it. Link is
http://www.rwilco12.com/forum/showthread.php?tid=71
3) Next I flashed this ROM with Odin. Easy. But I could not install SU. I thought I failed.
4) So I tried another downloaded file named SCL22KDUBNB1_SCL22KDIBNB1_SCL22KDUBNB1_HOME.tar
This flashed the ROM perfectly and the phone was working fine but once again I couldn’t get root.
5) It seems as long as I am only writing the two .img files, Knox is not tripped. So I think I can keep trying with different versions in the .tar file indefinitely. I must have flashed it 6 or 7 times. (Can anyone confirm this?)
6) I finally ran out of patience and decided to try the SC-01F rooted ROM called
SC01F-ROOTED-system.tar
7) This flashed fine but when the phone booted (complete with DOCOMO logo) I kept getting a message “MMBPROCESS stopped unexpectedly” every 10 seconds or so and this made the phone unusable. I wasn’t even able to check for root but I wonder if this was when I actually got root (or later with GNT3eXT?)
8) Then I flashed back to my own custom made .tar.
SCL22KDUBNB1-ROOTED-system.tar
Again this was easy with Odin. My system was back to normal but when I tried su I got an error. Then I tried GNT3eXT again and was careful to check the boxes. (I had missed this before because they are not worded very clearly) and suddenly I was done. Then I tried su again and it searched for administrative rights and I knew I was good. Rootchecker is fine, RootFTPServer works as does TB. Bluetooth is also fine.
I was working off of a number of explanations but I think this one is pretty close to how I did it.
http://forum.xda-developers.com/showpost.php?p=46447385&postcount=2
I did not need to do anything with Busybox and I haven’t installed Xposed either. If I had checked the boxes in GNT3eXT earlier, this may have taken WAY less time. My bad but I got it in the end and I didn’t trip Knox and FeliCa works in case I want it in the future.
So, long story short
1) Get the latest ROM from Samsung. Extract the system.img and cache.img and run it through system-rara7886.
2) Try flashing it and then enabling su in GNT3eXT first. THEN check SU. If this doesn’t work you may consider flashing a ROOTED version of SC-01F and then immediately flashing the ROOTED SCL22 ROM from rara. Then enable GNT3eXT and you’re golden.
Let me know how it goes for you.
Bad quality Youtube video is here https://www.youtube.com/watch?v=9LfzWOxcwrQ

make_rooted_system-rara7886 Simple Explanation
jcroot003sh said:
The long story that is my SCL22 (AU) successful root. I’ve been trying for months and doing lots of reading but I did not want to trip the Knox fuse so I kept waiting. Last weekend I went at it hard. I blended a couple of threads together and will try to explain below so the rest of you can try it.
1) I tried lots of ROM downloads but some were broken and some were for the SC-01 (Docomo) which I was reluctant to try. I also installed and reinstalled SU several times but I think I could have just installed it early and left it.
2) I downloaded the “make_rooted_system-rara7886-master” and figured it out. I eventually had to correct line 274 of the .sh file where the word "install" was spelled wrong. I got the system.img.ext4 and cache.img.ext4 output in a nicely wrapped .tar file named . (See step 8) I ran it in Ubuntu 14.04 but it took a little doing. You will need to SUDO it and when it is working you will see the BusyBox and other files copying. When there are no errors, you’ve got it. Link is
http://www.rwilco12.com/forum/showthread.php?tid=71
3) Next I flashed this ROM with Odin. Easy. But I could not install SU. I thought I failed.
4) So I tried another downloaded file named SCL22KDUBNB1_SCL22KDIBNB1_SCL22KDUBNB1_HOME.tar
This flashed the ROM perfectly and the phone was working fine but once again I couldn’t get root.
5) It seems as long as I am only writing the two .img files, Knox is not tripped. So I think I can keep trying with different versions in the .tar file indefinitely. I must have flashed it 6 or 7 times. (Can anyone confirm this?)
6) I finally ran out of patience and decided to try the SC-01F rooted ROM called
SC01F-ROOTED-system.tar
7) This flashed fine but when the phone booted (complete with DOCOMO logo) I kept getting a message “MMBPROCESS stopped unexpectedly” every 10 seconds or so and this made the phone unusable. I wasn’t even able to check for root but I wonder if this was when I actually got root (or later with GNT3eXT?)
8) Then I flashed back to my own custom made .tar.
SCL22KDUBNB1-ROOTED-system.tar
Again this was easy with Odin. My system was back to normal but when I tried su I got an error. Then I tried GNT3eXT again and was careful to check the boxes. (I had missed this before because they are not worded very clearly) and suddenly I was done. Then I tried su again and it searched for administrative rights and I knew I was good. Rootchecker is fine, RootFTPServer works as does TB. Bluetooth is also fine.
I was working off of a number of explanations but I think this one is pretty close to how I did it.
http://forum.xda-developers.com/showpost.php?p=46447385&postcount=2
I did not need to do anything with Busybox and I haven’t installed Xposed either. If I had checked the boxes in GNT3eXT earlier, this may have taken WAY less time. My bad but I got it in the end and I didn’t trip Knox and FeliCa works in case I want it in the future.
So, long story short
1) Get the latest ROM from Samsung. Extract the system.img and cache.img and run it through system-rara7886.
2) Try flashing it and then enabling su in GNT3eXT first. THEN check SU. If this doesn’t work you may consider flashing a ROOTED version of SC-01F and then immediately flashing the ROOTED SCL22 ROM from rara. Then enable GNT3eXT and you’re golden.
Let me know how it goes for you.
Bad quality Youtube video is here https://www.youtube.com/watch?v=9LfzWOxcwrQ
Click to expand...
Click to collapse
Hi,
Thanks a million for taking the time to report your methodology. Unfortunately I have been racking my brains trying to sort out how to use the zipped files in Linux Ubuntu to get it all working. The explanation is in Japanese (big thanks to the Japanese gentlemen who have worked hard on this - if they are in Osaka Ill buy them a beer!!) but difficult to comprehend using translators online - guess I need to study harder.
My request is for you to step by step in simple English go through th esteps in Linux to use the zipped folder that ma34 put together. I have my AU SCL22 firmware file and have run it through WIndows as you suggested to extracte the system.img.ext4 and cache files. Next I go into Linux Ubunto and have the make_rooted_system-rara7886 folder I downloaded on the desktop. I have put my two files (do I also need the cache one?) in the root of this folder and am kind of stuck what to do next.....Can you take the time to explain this more throughroughly? Look forward to getting this working with your explanation.
Update: Ok I have managed to set permissions as in the read me text file, for example..
Please add execute permissions to bin/ext4_utils/mkuserimg.sh and make_rooted_factoryfs.sh.
(dir) $ chmod a + x make_rooted_factoryfs.sh
(dir) $ chmod a + x bin/ext4_utils/mkuserimg.sh
And then in terminal dropped and executed the make_rooted_system.sh file but receive the following error..
185: .: Can't open ./install_su
BTW (I checked for any mispelling in files but all seems okay.
If you could post your tar file so I can test that would make it easier but I still wanna get this going by myself for the sake of it and for others. Thanks a million for any support. Have an awesome day!!!!!!!!
Update :good:: I overcame the cant open install_su issue by logging in as root using sudo su. I was able to execute the chmod commands on the two files (as Im on AU KDDI it was make_rooted_system.sh not the one listen above Ive used the windows method to get the readable img file for Linux Ubuntu but I get the following error messages:
Error reading sparse file header
mount:you must specify the filesystem type
and lots of umount...No such file or directory
Maybe Ill try redoing the files through the windows method. Anyone with any ideas?

xdaoxs,
Sorry for the delay. Apparently I am not getting any of the updates from this site. I'll check into that.
OK, I am running Ubuntu 14.04 on my server here and I copied the rara folder to the desktop and then put the two files (you mentioned that you already have them) into the correct location according to the info below (from the rara instructions which I have semi translated) :
Instructions
In the same directory as readme.txt, put in place the factoryfs.img (system.img.ext4) from the factoryROM。Files and folders should be positioned/named as below
(dir)
├ bin/
├ config/
├ img/
│ └SCL22 (your phone’s model name)
│ ├(cache.img) ※you must add this
│ └factoryfs.img(system.img.ext4 or system.img) ※ you must add this
├ sed/
├ user/
│ └SCL22 (your phone’s model name)
│ └Sample (This was already there I think)
│ ├install.sh
│ └xxxx.so (I actually didn't have this file and it still worked)
│ └.gitignore (this file came included as well)
│ readme.txt
├ install_su
├ make_rooted_factoryfs.sh
└ user_custom.sh
When the positioning is finished, start Terminal, navigate to the the folder and execute as “sudo make_rooted_factoryfs.sh"
You will get a .tar file in a folder which will be created called "out" that can be flashed as is using Odin. Mine is called SCL22KDUBNB1-ROOTED-system.tar
Hope this helps. I'm in Nagoya by the way. Let me know how it goes.

moved on to KitKat
Thanks jcroot003sh. I managed to succeed with this process but due to work wasnt able to respond. Thanks for trying to help.
I just updated to SCL22 KitKat and am working on getting a proper root using the method here. Will post when I have success.
Thanks again
jcroot003sh said:
xdaoxs,
Sorry for the delay. Apparently I am not getting any of the updates from this site. I'll check into that.
OK, I am running Ubuntu 14.04 on my server here and I copied the rara folder to the desktop and then put the two files (you mentioned that you already have them) into the correct location according to the info below (from the rara instructions which I have semi translated) :
Instructions
In the same directory as readme.txt, put in place the factoryfs.img (system.img.ext4) from the factoryROM。Files and folders should be positioned/named as below
(dir)
├ bin/
├ config/
├ img/
│ └SCL22 (your phone’s model name)
│ ├(cache.img) ※you must add this
│ └factoryfs.img(system.img.ext4 or system.img) ※ you must add this
├ sed/
├ user/
│ └SCL22 (your phone’s model name)
│ └Sample (This was already there I think)
│ ├install.sh
│ └xxxx.so (I actually didn't have this file and it still worked)
│ └.gitignore (this file came included as well)
│ readme.txt
├ install_su
├ make_rooted_factoryfs.sh
└ user_custom.sh
When the positioning is finished, start Terminal, navigate to the the folder and execute as “sudo make_rooted_factoryfs.sh"
You will get a .tar file in a folder which will be created called "out" that can be flashed as is using Odin. Mine is called SCL22KDUBNB1-ROOTED-system.tar
Hope this helps. I'm in Nagoya by the way. Let me know how it goes.
Click to expand...
Click to collapse

ducmthai said:
SCL22 rooting, the custom image maintains working NFC (NFC in Japan market is different with international market, as it is involved in mobile payments). You will need to flash the custom image via Odin, but you'll lose all of your data.
---------- Post added at 10:24 AM ---------- Previous post was at 10:03 AM ----------
Hi again, it seems that the link for your v1.1 is corrupted. Also, KDDI has updated their firmware version to SCL22KDUBNB1. Could you please provide any rooting information about this new version? Thanks in advanced!
Click to expand...
Click to collapse
Root SCL22 working fine - http://forum.xda-developers.com/galaxy-note-3/general/samsung-galaxy-note-3-scl22-au-kddi-t2964801

Hello
Is there any lolipop bootloaders for scl22 note 3 au kddi. I want to install lolipop custom rom. But without lolipop bootloaders i cant intall any custom roms.
Sent from my SM-N910F using XDA Free mobile app

[REQUEST] OTA .182 update Zip

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.

[GUIDE] Downgrade SM-G920i from Android 7.0 to 6.0.1 with Secure Download Enabled

Hello all!
This is my first tutorial here, hope to be useful as it was for me. After several attempts and extense research mainly here in XDA I finally achieved to downgrade my SM-G920I from 7.0 to 6.0.1 even with secure boot enabled.
The basics: Using a chilean stock 6.0.1 ROM:
- I've extracted all files from the stock rom and repacked it as 4 files without sboot.bin Instructions here: forum DOT gsmhosting DOT com/vbb/f777/tutorial-create-samsung-4-file-multi-firmware-your-own-100-a-1860706/- I've used a PIT default file for my model and region from here: sammobile dot com/forum/threads/30173-galaxy-S6-G920-pit-files
The instructions are the usual, Using Odin 3.12, flash the files into their respective slots and select the PIT file into PIT tab also. In options disable auto reboot and check re partition.
Download link in progress, but you can DIY with the instructions before.

downgrade issue can you give me the PIT file for sm-g920f please
also i have issue to back to nougat an error occured hidden.img durinf flashing

Mehar Zain said:
also i have issue to back to nougat an error occured hidden.img durinf flashing
Click to expand...
Click to collapse
Have you downloaded a 6.0.1 stock rom for your model and then followed my instructions?
PD: The FRP for your device in on the second link mentioned before.

There is easier way ,after extracting delete all .bin (aboot cache hidden and something else cant remember)then repack using 7zip to the originat format u will notice that the new archive is bigger it's about 3.6 gb inside there is data,system and some other files flash the new archive with odin and thats all ,worked fine t mobile g920t downgrading from nougat to mm

amin44 said:
There is easier way ,after extracting delete all .bin (aboot cache hidden and something else cant remember)then repack using 7zip to the originat format u will notice that the new archive is bigger it's about 3.6 gb inside there is data,system and some other files flash the new archive with odin and thats all ,worked fine t mobile g920t downgrading from nougat to mm
Click to expand...
Click to collapse
Yes, you are right. Using 7zip is a lot easier.

Will work on Att version G920A with locked bootloader on 7.0? I've been researching 2 days to see about downgrading it 6.0.1 while taking least chances as possible. If answer is yes, when repackaging should I remove md5 extension on all 4 files?
Thanks

amin44 said:
There is easier way ,after extracting delete all .bin (aboot cache hidden and something else cant remember)then repack using 7zip to the originat format u will notice that the new archive is bigger it's about 3.6 gb inside there is data,system and some other files flash the new archive with odin and thats all ,worked fine t mobile g920t downgrading from nougat to mm
Click to expand...
Click to collapse
how you repack to original format with 7zip?
i always get error cheksum when put the file in odin

zhadow88 said:
how you repack to original format with 7zip?
i always get error cheksum when put the file in odin
Click to expand...
Click to collapse
Just select the file and compress them using normal compression in options ,maybe the problem is with your version of odin

https://forum.xda-developers.com/showpost.php?p=81418691&postcount=29