I'm trying to flash the Russian Stock ROM into my XZ because I think it's the cleanest one (the one with less bloat). I have followed many guides on the internet and they all yield the following log on the flashing tool:
10/024/2017 23:24:47 - INFO - Start Flashing
10/024/2017 23:24:47 - INFO - No loader in the bundle. Searching for one
10/024/2017 23:24:47 - INFO - No matching loader found
10/024/2017 23:24:47 - WARN - No loader found or set manually. Skipping loader
10/024/2017 23:24:47 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_110 / Bootloader status : ROOTABLE
10/024/2017 23:24:47 - INFO - Max packet size set to 4M
10/024/2017 23:24:47 - INFO - USB buffer size set to 512K
10/024/2017 23:24:55 - INFO - Parsing boot delivery
10/024/2017 23:24:55 - INFO - No flash script found.
10/024/2017 23:24:55 - INFO - Flash script is mandatory. Closing session
10/024/2017 23:24:55 - INFO - Ending flash session
10/024/2017 23:24:56 - INFO - Flashing finished.
Click to expand...
Click to collapse
It never does any actual flashing because the "Flash script is mandatory" log message. I have looked like crazy and I know that the famous "Flash script" is an fsc file. However none of the tutorials I have followed have provided download links for them or have explained how to make them. Could someone give me a hand with this?
For what is worth, I'm trying to use the ROM named "F8331_39.2.A.0.327_R4C_Russia Generic_1305-0896.ftf", and yes my device model is indeed F8331.
Hey, I had the same issue when I first tried to use the Flashtool! When you download the ftf from XperiFirm in the Flashtool, it should pop up with a dialogue saying that a script for your device was found, would you like to include it? You should say yes to that and it will pack it in the ftf. If you don't want to do that, under Appdata/Roaming/.flashtool/devices/F8331 there should be a script there that you can use. I would recommend using the built in XperiFirm option though
Sent from my F8331 using Tapatalk
Thanks a lot! I found the "devices" folder and I effectively found this folder:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How exactly do I use it with flashtool?
Thanks for your help so far.
I have tried XperiFirm too, but it's having issues connecting to the internet. Most of the time it won't connect, and when it does the downloads always die halfway through (yeah I'm trying to Flash with both Windows and Mac, no success with either )
get the latest flashtool or at least tell us which version you have
try a "refresh devices" in flashtool
delete the devices folders and reinstall flashtool
flashtool normally does "the right thing" with the scripts and other info it finds in the device tools folders. Sometimes it asks "use script?" -> say yes
Flashtool Version 0.9.23.1 built on 11-01-2017 15:12:00
I downloaded it last night from their website. I have deleted devices and reinstalled Flashtool, doesn't seem to want to pick up that fsc automatically.
I'm currently downloading my own version via XperiFirm (can run it on my Mac with Mono). Hopefully this will work but in the meantime I'm open to other ideas.
Alright, I downloaded a version with XperiFirm. It never asked me for a FSC file. Is there perhaps an up to date guide to install another stock ROM on this device? I have followed thousands of tutorials with both macOS and Windows. I have downloaded many FTFs as well as attempted to create my own. My log always looks exactly the same as in the first page. Flashtool never asks me for the FSC. Yet the FSC exists in the devices directory of Flashtool.
I don't care about root. I don't care about unlocking my bootloader. Everything I want to install fresh with Nougat.
I did it!
There's a lot of stuff I did there was not mentioned in any of the tutorials at all.
- The FSC file will indeed be under .flashtool/devices/F83XX. What no one tells you is that there's two FSC files there (and there can be more). These device folders get pulled from a Github repo so their content will vary in time. If a tutorial or answer is showing you different files, that's unfortunately normal - I say unfortunately because it's very easy to get lost if it's your first time flashing this device. At the time of this answer there's only three files in the F83XX folder: 39.fsc, default.fsc, and F83XX.properties. We have TWO FSC files here, so witch should you use? The answer is "39.fsc". How do I know? By looking at the Github commit message, at the time of this writing 39.fsc says "New fsc for all XZ devices". This file is also newer than default.fsc. So use this one. Use a similar logic to this if you are flashing your device and are reading this post months later after it was posted.
- Alright, you have a FSC file, what do you actually do with it? You need to create your own FTF file and add the FSC to it. When I was first attempting to flash, I downloaded the FTF file some other guy created and his file didn't include the flash script. So add this to the files downloaded by XperiFirm (as in, in the folder you are downloading the files, copy this file, at the same level as the "boot" directory). When you are creating your Bundle with Flashtool (Tools > Bundler), the FSC script should show up in the file list and you can add it to the right pane. Don't worry if the file doesn't show up. It's still there, and it will be included in your FTF. This is probably a display bug. Funnily enough if you don't add a FSC file to your bundle Flashtool freezes when you attempt to build the bundle. Some people say XperiFirm should download the FSC file. Mine didn't, maybe yours won't either, so hopefully this will help you get that ever so elusive file.
Leonne said:
I did it!
There's a lot of stuff I did there was not mentioned in any of the tutorials at all.
- The FSC file will indeed be under .flashtool/devices/F83XX. What no one tells you is that there's two FSC files there (and there can be more). These device folders get pulled from a Github repo so their content will vary in time. If a tutorial or answer is showing you different files, that's unfortunately normal - I say unfortunately because it's very easy to get lost if it's your first time flashing this device. At the time of this answer there's only three files in the F83XX folder: 39.fsc, default.fsc, and F83XX.properties. We have TWO FSC files here, so witch should you use? The answer is "39.fsc". How do I know? By looking at the Github commit message, at the time of this writing 39.fsc says "New fsc for all XZ devices". This file is also newer than default.fsc. So use this one. Use a similar logic to this if you are flashing your device and are reading this post months later after it was posted.
- Alright, you have a FSC file, what do you actually do with it? You need to create your own FTF file and add the FSC to it. When I was first attempting to flash, I downloaded the FTF file some other guy created and his file didn't include the flash script. So add this to the files downloaded by XperiFirm (as in, in the folder you are downloading the files, copy this file, at the same level as the "boot" directory). When you are creating your Bundle with Flashtool (Tools > Bundler), the FSC script should show up in the file list and you can add it to the right pane. Don't worry if the file doesn't show up. It's still there, and it will be included in your FTF. This is probably a display bug. Funnily enough if you don't add a FSC file to your bundle Flashtool freezes when you attempt to build the bundle. Some people say XperiFirm should download the FSC file. Mine didn't, maybe yours won't either, so hopefully this will help you get that ever so elusive file.
Click to expand...
Click to collapse
By the way, the bundling on that Flashtool version is bugged. You have to manually update the Flashtool jar file to 9.23.2 to be able to bundle through Flashtool. It's quite odd that at no point Flashtool asks for a script but everyone's device interacts in a unique way usually! Good to hear you finally got it sorted out [emoji1]
Sent from my F8331 using Tapatalk
I am glad you figured it out.
"updating the devices" pulls updated scripts and more from github
a fsc-file contains a script making sure that the parts the rom land in the proper parts of your devices storage
the fsc file is necessary for the XZ but does not get "bundled"
read the changelog of the tools you use
Related
Download NOW from SourceForge!!
VIEW YOUR SYSTEM.IMG (HAVEN'T TESTED OTHERS) FROM YOUR ODIN DUMPS IMG'S FROM THE TUTORIAL:
"[GUIDE][HOW-TO]Create custom ODIN packages"
VIEW THE IMG FILES AND THEN SAVE THEM AS EXT4!!!
VIEW XML (NICELY)
HEX TOO!!
For WINDOWS!!!
UNPACK folders to any place in Windows:
(ie: look at your system.img in this tool, then select the folder you want to have in Windows, right-click on it, and click "extract", and then choose where in your Windows Directory where you want it saved.)
"I had not tried it with anything but the System.img. But if you right-click on ANY folder in the tool, you can extract it (save a copy in windows) to anywhere. And it's totally readable. You can also extract the apk's, etc, etc.."
PERFECT TOOL. EASY TO USE. I FOUND IT WHILE BROWSING SOURCEFORGE AND NOBODY HAD DOWNLOADED IT YET.
DOWNLOAD HERE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PHOTO SOURCE: SourceForge.net (they were better than my screenshots)
THIS TOOL WAS NOT MADE BY ME. NOR DID I HAVE ANYTHING TO DO WITH IT OTHER THAN THE FACT I FOUND IT WHILE WHILE BROWSING...
Android RFS Unpacker
HERE IS ANOTHER TOOL FROM THE SAME PERSON:
HERE
THE ANDROID RFS UNPACKER
Nice find.
Ta,
Alqi
Sent from my SCH-I535 using xda app-developers app
Nice find! Hopefully, this can help some of the Devs on here that know what they are looking at.
Sent from my SCH-I535 using xda premium
It really helps me out a lot if I am stuck in Windows and don't feel like firing up my Ubuntu Machine or having to start VMware. I mainly use it for the Odin dumps I pull off my extSdCard (if I am already in Windoze...
Sent from my SCH-I535 using Tapatalk 2
I get "Unknown file" when I try to open the .ext4 file. How do I fix this?
MinnesotaVikings1961 said:
I get "Unknown file" when I try to open the .ext4 file. How do I fix this?
Click to expand...
Click to collapse
Me too.
I can See the files, But cannot do anything else
h311sdr0id said:
Download NOW from SourceForge!!
VIEW YOUR SYSTEM.IMG (HAVEN'T TESTED OTHERS) FROM YOUR ODIN DUMPS IMG'S FROM THE TUTORIAL:
"[GUIDE][HOW-TO]Create custom ODIN packages"
VIEW THE IMG FILES AND THEN SAVE THEM AS EXT4!!!
VIEW XML (NICELY)
HEX TOO!!
For WINDOWS!!!
UNPACK folders to any place in Windows:
(ie: look at your system.img in this tool, then select the folder you want to have in Windows, right-click on it, and click "extract", and then choose where in your Windows Directory where you want it saved.)
"I had not tried it with anything but the System.img. But if you right-click on ANY folder in the tool, you can extract it (save a copy in windows) to anywhere. And it's totally readable. You can also extract the apk's, etc, etc.."
PERFECT TOOL. EASY TO USE. I FOUND IT WHILE BROWSING SOURCEFORGE AND NOBODY HAD DOWNLOADED IT YET.
DOWNLOAD HERE
PHOTO SOURCE: SourceForge.net (they were better than my screenshots)
THIS TOOL WAS NOT MADE BY ME. NOR DID I HAVE ANYTHING TO DO WITH IT OTHER THAN THE FACT I FOUND IT WHILE WHILE BROWSING...
Click to expand...
Click to collapse
I can view the files inside the folder. But cannot do anything. It is shown in a dialogue window. When open it says, unknown file. Can anyone help to extract an apk from the list??
Thanks! Works great.
Hi.. I saw your tutorial.. I tried to extract system.sin from my Stock ROM of Xperia S.. And when i did, i got to extract it in "ext4" format instead of what other tutorials showed me as "yaffs2" format.. Well, i googled about how to extract ext4 format files and found your tutorial.. I happened to find only app and bin folders as in the SS i have given you and even when i try to extract those folders i am unable to.. I see the error i have given you in 2nd SS.. And i couldn't even exit the application.. Can you help?
sudhindrakv said:
Hi.. I saw your tutorial.. I tried to extract system.sin from my Stock ROM of Xperia S.. And when i did, i got to extract it in "ext4" format instead of what other tutorials showed me as "yaffs2" format.. Well, i googled about how to extract ext4 format files and found your tutorial.. I happened to find only app and bin folders as in the SS i have given you and even when i try to extract those folders i am unable to.. I see the error i have given you in 2nd SS.. And i couldn't even exit the application.. Can you help?
Click to expand...
Click to collapse
i get unknown file formay when i try to open a system.img file. or pretty much any file .it seems
I downloaded the ext4 unapcker v. 16.10.2013 (R2) archive.
The file inside are quite old (April and August 2013) and didn't include latest changes (italian translation and tips for translation).
Please update the files in the distriibution archive.
Could add simple text file for documentation
*** README.TXT
- Info about command line parameters
- How to change GUi language
- How to create a new language
*** CHANGELOG.TXT
- Small info about changelog in different releases
If I can help you I can post a sample for two files.
Hi.
There some serious bugs in this util.
1. Didn't extract all files (compared with other similar utils)
I checked that utils didn't extract all files (compared with other utils).
I made a comparison between the file/folders extracted from saprse file iamge (ex. Android systm.img of some smartphones) by this util and Total commander Diskinternal Total Commander Plugin)
EXT4 unapcker extract a lot of file less than Total Comamnder with DiskInternal plugin (about 300 Mb elss).
2. File extracted dind't maintain original date/time
Opening a system.img file and extracting the files inside, the extracted files/folders have today date/time instead original date/time.
Please mantain original date/time for the file extracted.
3. Comamnd line use - it crashed
Using command line for EXT4 unpacker it crashed
The error is
Extracting \system\xbin\Base64
Exception EListError in module ext4_unpacker.exe at 00019E8A
List index out of bounds (0).
Is it a really living project?
No one answer.
The autho din't reply since first day of novembrer.
There are some critical issues.
The file into sourceforge repository are wrong.
Very interesting project but (probably) dead.
The idea is good, but..
From time to time i need to unpack system images for android. It happens. the latest models have HUGE images ~2Gb+
But unfortunately, the program designed to load data to RAM, wich makes problems for 32 bit applications to work with huge images.
Actully, EXT4 partitions may be unpacked in many ways (WinHex can do it easy), but we have here some-kind of compressed images wich have to be uncompressed before we can read it with any 3rd party tool.
According to the SF sources i made a small tool for this purpose.May be it will help to someone
BR
@darkmen
jb.ext4 comamnd
Could you customize the app with more option like
/nodetail to avoid showing the progress
add an option to specify the output file name, ex
jb.ext4 system.img newsystem.img
Should be possible to make a similar command to extract all ffles/folder by system.img?
Or should be possible to use unyaffs command?
Thanks.
I believe that we can close this thread!
The program was very interesting but had some bug and from November the author didn't replay on Sourceforge.
Thanks.
bovirus said:
@darkmen
jb.ext4 comamnd
Could you customize the app with more option like
/nodetail to avoid showing the progress
add an option to specify the output file name, ex
jb.ext4 system.img newsystem.img
Thanks.
Click to expand...
Click to collapse
Hi, source is attached, so its very easy to modify.
Updated the download URL with these fixes.
Many thanks darkmen.
If I will have some improvement proposals I hope that you can help me to implement it.
Which language do you sue for this program?
Which resources/program are needded to compile it?
Thanks. Bye.
bovirus said:
Many thanks darkmen.
If I will have some improvement proposals I hope that you can help me to implement it.
Which language do you sue for this program?
Which resources/program are needded to compile it?
Thanks. Bye.
Click to expand...
Click to collapse
Just open zip and you will see (delphi).
[TUT]Extract kernel "zimage" From boot.img and Convert to .tar and Flash using Odin
[Extremely Noob GUIDE]Since there is no explained and easy Guide to Extract Kernel [zimage] and Ramdisk [Ramdisk] from Boot.img, Then Convert it to zimage.tar and Flash it using Odin
Well here it is step by step:
Note: This Method is used to Extract Kernels form Stock Rom's Boot.img
First you need to install Python, which is round about 17MBs software freely available on python website.
Step 1:Download the attached Python script named "split_boot_img" from attachments down Below, Extract it and copy to the folder created in Step 2.
Step 2:Create a folder with any name you like. I recommend "boot.img extraction".
Step 3: Copy the boot.img, you want to extract, to the folder you created in Step 2.
Step 4: Run the script named "split_boot_img"by double-clicking and see the magic.
Congratulations!!! Here you go. the "zimage" and "ramdisk" files are extracted.
Now the Conversion Part:
Step 1: Download this IZARC software and install it from Here:http://www.izarc.org/download.html
Step 2: Open the folder created in First-Step 2.
Step 3: Right Click the ziamge File Extracted from boot.img. as in Image 1 in attachments.
Step 4: Select add to archive file from IzArc right click options as in Image 1 in attachments.
Step 5: Now scroll the Archiving type to ".tar" as in Image 2 in attachments.
Step 6: Click the Add button as in Image 3 in attachments.
Last Step: Now flash the "zimage" file created in Step 6 Using Odin.
View attachment split_boot_img.zip
Image 1:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Image 2:
Image 3:
Not Working
extraction doesn't work for me :/
shivasharmaarya said:
extraction doesn't work for me :/
Click to expand...
Click to collapse
Did you follow till last step. What message did you get?
yes
exceptionalkhan said:
Did you follow till last step. What message did you get?
Click to expand...
Click to collapse
Python script of yours is not working.Its giving error which flashes for microsecond and i am unable to see it
shivasharmaarya said:
Python script of yours is not working.Its giving error which flashes for microsecond and i am unable to see it
Click to expand...
Click to collapse
Maybe he should have put in that you need to use Python 2.7.9 not 3.x ... Had the same problem.
All steps worked after, but didn't flash it yet, I'll do it today or tomorrow.
Also you should mention IZArc is full of crapware, it open one install and even if I chose to not install stuff, it installed iStart and Search Enginer extensions to my browsers. After, surprise, another install showed up to actually install IZArc ... not I need to de-crap my system
dotuletz said:
Maybe he should have put in that you need to use Python 2.7.9 not 3.x ... Had the same problem.
All steps worked after, but didn't flash it yet, I'll do it today or tomorrow.
Also you should mention IZArc is full of crapware, it open one install and even if I chose to not install stuff, it installed iStart and Search Enginer extensions to my browsers. After, surprise, another install showed up to actually install IZArc ... not I need to de-crap my system
Click to expand...
Click to collapse
Did the kernel.img actually work for you? I tried this same process as well. It took me 4 hours to clean all the maleware from my laptop. I mad the .Tar file and tried to flash it. it failed completely. I think this OP needs to be removed. More than likely the OP is getting paid for all the downloads he is tricking people into.
Chillyz12 said:
Did the kernel.img actually work for you? I tried this same process as well. It took me 4 hours to clean all the maleware from my laptop. I mad the .Tar file and tried to flash it. it failed completely. I think this OP needs to be removed. More than likely the OP is getting paid for all the downloads he is tricking people into.
Click to expand...
Click to collapse
No, it failed also. Yes, it should be removed.
Ended up using http://forum.xda-developers.com/showthread.php?t=2446269 but for a strage reason Odin would not like it when I moved the .tar archive from a folder to an other from that method (I keep my pc organized), had to create the tar, flash it from that folder, then... deleted it because after I couldn't use it anymore.
dotuletz said:
No, it failed also. Yes, it should be removed.
Ended up using http://forum.xda-developers.com/showthread.php?t=2446269 but for a strage reason Odin would not like it when I moved the .tar archive from a folder to an other from that method (I keep my pc organized), had to create the tar, flash it from that folder, then... deleted it because after I couldn't use it anymore.
Click to expand...
Click to collapse
It won't trip knox, right?
Joker87 said:
It won't trip knox, right?
Click to expand...
Click to collapse
Flashing any modified boot / kernel / recovery trips Knox, doesn't matter what method you use. Sometimes even stock trips Knox as some users said.
What i did was take a stock rom from SamMobile that was 'hackable' through TowelRoot, extracted the kernel with WinRar, made the kernel flashable in Odin using that tool, flashed it via Odin, rooted device with TR, then used same steps to download,extract,make kernel bootable to restore my original kernel. Knox stayed 0x0 on i9195.
You can try reading about Heimdall. Supose you can flash without Odin and without converting. It would make your life easier, but for me it didn't work (didn't start on Win 64bit, i think i needed another MS visual c++ , a dependency of Heimdall).
ps.: the tool to create flashable archives would't work for me just by double-clicking, so I had to open an command prompt - CMD with admin rights, go to the directory where i had the tool and type ImgToTar.MD5.bat . Just put everything in C:\tool including recovery.img / boot.img or kernel.img then go start-> type in search box CMD -> right-click on the result and Run as admin -> in the black box type the next text followed by Enter key:
cd /
cd tool
ImgToTar.MD5.bat
I hope it works, i need it for the same reason of you, flashing an older kernel to root with towelroot keeping knox 0x0 at the end of this process
INTRODUCTION
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*/WARNING
This tool is in [B]BETA[/B] phase and is not for noobs. If you use this, you are choosing to play with your device on your own.
I will not be responsible for any damage to your device or your belongings in your home.
If you blame me for anything that goes wrong I'll die laughing at you/*
Hello all!
Today I present you F2I converter. This tool can convert system folder back to ext4 image format suitable for flashtools without cygwin.
Basically, this tool was made in keeping mind the format used by lollipop structure where dat files were converted to ext4 format and then unpacked, repacking them was kind of hard (or lazy to do so in my case) as it required linux or Cygwin [Based on Xpirt's Guide. Now I've always preferred a way to avoid linux and cygwin
I managed to put together a set of tools that can easily convert the extracted system folder back to img for flashing and in lollipop can be converted back to dat format on windows.
So this is what this tool is capable of! If you on lollipop and want @xpirt guide to do so then here it is - [HOW TO] Lollipop DAT files | Compression and Decompression
FEATURES
• Supports all Android Versions
• Works without Linux or cygwin
• Generates Log that help to troubleshoot the issues
• No extra software required (Except Git for Windows)
• Supports both way conversion
• Suggest more features
• Much more to come!
HOW TO USE
You need GIT for windows to run this tool. Kindly download and install GIT from HERE
Now install GIT and when you're done download F2I converter and extract it in core C: directory. There will be a folder names as "IMG_WIN" kindly make sure it is extracted in C:
Recommended GIT is v 1.9.4 or newer.
Mostly everything is self-explanatory in the tool but when you will convert "SYSTEM" folder back to "EXT4 img" format you will be asked to enter size in bytes.
Here is what you are asked to do..
1) Open the system.img inside the respective folder you're working on and then right click on it and click Properties
2) In General tab you'll see something like this
Now copy the highlighted part and paste in the box shown below in image
Now you can continue. Ahead
DOWNLOADS
MAJOR LINK
MIRROR
BUGS
This tool is in BETA phase so you are likely to face some bugs. Though I have paid a lot of attention while creating this tool but you may encounter some small code errors (like path not found etc) I request you to kindly see for yourself and correct it.
You are likely to face this error mostly though
Code:
error in bla bla bla ..... failed to allocate block [NUMBERS] out of space?
If you encounter something like this then it will not work with your files. This will occur mostly in Android 2.3.x-4.4.x and in some cases with 5.0 and 5.1
I am trying to fix this issue. Please co-operate
Rest no major bug.
CREDITS
@xpirt for his awesome guide on lollipop compression and decompression of dat files
Google for being so hepful :angel:
XDA for it's awesomeness
XDA:DevDB Information
[F2I Converter] Convert System folder into EXT4 Image without cygwin on Windows!, Tool/Utility for all devices (see above for details)
Contributors
Tech N You
Version Information
Status: Beta
Current Beta Version: v1.0
Beta Release Date: 2015-05-03
Created 2015-05-03
Last Updated 2015-05-03
Reserved.
Reserved Again.
Nice Dude ! extracted xolo one files using this ... hoping to port it for q700s
Great tool mate!
Enviado desde mi OnePlus One
Tech N You said:
.....This tool is in BETA phase so you are likely to face some bugs.....I request you to kindly see for yourself and correct it......
Click to expand...
Click to collapse
i've tried this. see the screenshot. i find only 2 files to copy back to my rom zip.
what about "file_contexts"? can/should the original be retained?
large size difference between original "system.transfer.list" and modified one ok?
Doesn't work for me. I'm unable to find system.img. So I downloaded "sda2img.exe" and I made system.img with it. Then, when I try to recompress system folder in DAT format, there is this problem ( see the screenshot ).
Then I noted that after using it, in "Working_Do_Not_Touch", system.transfer.list and system.new.dat get losts.
m0han said:
i've tried this. see the screenshot. i find only 2 files to copy back to my rom zip.
what about "file_contexts"? can/should the original be retained?
large size difference between original "system.transfer.list" and modified one ok?
Click to expand...
Click to collapse
AlessandroXCV said:
Doesn't work for me. I'm unable to find system.img. So I downloaded "sda2img.exe" and I made system.img with it. Then, when I try to recompress system folder in DAT format, there is this problem ( see the screenshot ).
Then I noted that after using it, in "Working_Do_Not_Touch", system.transfer.list and system.new.dat get losts.
Click to expand...
Click to collapse
Thanks for trying out the tool. You must use same file_contexts
As per your issue sir thing is the output is cleaned up and no file is left back. I request you to try the size from xpirts post on this. Kindly check that and reply back.
[system_new.img?]
Any ideas on how to fix this:
When I try repacking [system folder] back to [system.new.dat] the program throws an error : File not found -- system_new.img
MeTaL-01 said:
Any ideas on how to fix this:
When I try repacking [system folder] back to [system.new.dat] the program throws an error : File not found -- system_new.img
Click to expand...
Click to collapse
Option 4 is the correct one for Lollipop i see u chose option 3
Tech N You said:
....You must use same file_contexts.....
Click to expand...
Click to collapse
did so. upon trying to flash rom zip file, "error executing binary in zip....."
Tech N You said:
Option 4 is the correct one for Lollipop i see u chose option 3
Click to expand...
Click to collapse
I've tried both, none work
MeTaL-01 said:
I've tried both, none work
Click to expand...
Click to collapse
Okay then let me recheck whole thing and I'll revert back to you
ahh boy, you never cease to amaze me. Thanks for this
kirito9 said:
ahh boy, you never cease to amaze me. Thanks for this
Click to expand...
Click to collapse
Glad to know you liked this tool :good:
I keep getting a Permission denied error when using option 4. Any ideas why??
LupusGrande said:
I keep getting a Permission denied error when using option 4. Any ideas why??
Click to expand...
Click to collapse
Tool is not getting administrative privilege.
Kindly make your Windows user prompt to lowest
Tech N You said:
Tool is not getting administrative privilege.
Kindly make your Windows user prompt to lowest
Click to expand...
Click to collapse
after conversion there is nothing in system folder
well done bro ......................though small glitches bt overall grt tool (Y)
I can't convert the system folder back to dat files.
I use option 4 but nothing works.
Where I have to put the system.transfer.list and the system.new.dat?
What I have to do?
Hey guys!
Since there was no thread about it yet, and since Sony released recently a new bootloader update for the Xperia M2, I decided to open a new one, and explain a little more how it works.
The bootloader update is used, in the Xperia M2, to unlock the R/W features in the recovery partition. This means that, if you've an UBL device, and you flash the update, you'll get permissions to install a new UBL recovery inside the partition itself. So, you won't need to include an external ramdisk inside your boot image.
How can I obtain it?
You've currently 2 ways:
1. Download and install Emma and apply the update from there, which will be always the latest available.
2. Download it through an FTF (explained below).
How can I install it if I choose FTF way?
First, download the latest FTF from below. Once downloaded, place it in flashtool's firmware folder, which is located in C:\Users\<your-name>\.flashTool\firmwares\.
Now, launch Flashtools (it needs to be version 0.9.18.6 or below, mandatorily), choose the FTF update (you'll easily notice which one it is), and simply hit flash.
Once prompted, connect your device while off to the Micro-B end of the USB cable, and, while you press & hold the Vol- key, connect the USB-A end to the PC. Then flash will start.
How can I install a custom recovery?
Download my ADB Pack 'Herramientas-de-flasheo.zip'.
Now, unzip my ADB Pack 'Herramientas-de-flasheo.zip', which contains basic ADB and Fastboot executables to a folder in your desktop. Also, copy the file Recovery file you downloaded to that folder.
Put your phone in Fastboot mode, this means, while pressing and holding the Vol+ button, connect the USB cable. Once the Led goes blue, stop pressing it.
Now, execute the following keyboard shortcut (Win+R) and type inside the Run prompt CMD. Inside the Command Prompt, using CD (change directory), navigate to the folder you created in the desktop. It'll be something like...
Code:
cd C:\Users\linuxct\Desktop\adbpack\
Now, execute the following command:
Code:
fastboot flash recovery <[COLOR="Purple"]NAME-OF-THE-RECOVERY[/COLOR]>.img
How can I access the recovery?
To enter into the recovery, press and hold the volume down button, and while you're holding it, press and hold the Power button until it vibrates. When you see the Sony logo, stop holding the Vol- Button.
DOWNLOAD: Latest Bootloader Update FTF [ver 1.716]
--------------------
DOWNLOAD MIRROR: Latest Bootloader Update FTF [ver 1.716]
Amazing work as always @linuxctt
Maybe be our Cyanogenmod 13 maintainer...? I'll walk my self out
There is a another way to launch command window in selected location.
Like: Open adbpack folder. Pressing SHIFT button,right click anywhere on that folder and you get option "Open new command window ".
I hope it helps noobs.
Btw,great tutorial buddy
imzihad said:
There is a another way to launch command window in selected location.
Like: Open adbpack folder. Pressing SHIFT button,right click anywhere on that folder and you get option "Open new command window ".
I hope it helps noobs.
Btw,great tutorial buddy
Click to expand...
Click to collapse
That's the one I commonly use, but I found easier the one I wrote in the tutorial
Thanks
Thank you Linuxct, It works as always.
Do i need install Ric disabler this time?
Can I update D2302 with this
I can't see any file in the flashboot firmware selector dialog box.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nishchayv said:
I can't see any file in the flashboot firmware selector dialog box.
Click to expand...
Click to collapse
I think you're on a different user account where the FTF is actually placed in, there's no reason for not showing up...
linuxct said:
I think you're on a different user account where the FTF is actually placed in, there's no reason for not showing up...
Click to expand...
Click to collapse
I have confirmed that the FTF is placed in the account I am using. Is the FTF file corrupt or something? Mine file is only 3.13 MB.
nishchayv said:
I have confirmed that the FTF is placed in the account I am using. Is the FTF file corrupt or something? Mine file is only 3.13 MB.
Click to expand...
Click to collapse
I've just tried it out with Flashtools 0.9.18.6, and it's working, however on Flashtools 0.9.20.0 and above it's not showing up, since it compares the device model written in the FTF with a database, and since the entry I made was customized, it's not showing up.
What I'm going to do is to check if there's any update in Emma, if so, I'll update the file with new bootloader update.
linuxct said:
I've just tried it out with Flashtools 0.9.18.6, and it's working, however on Flashtools 0.9.20.0 and above it's not showing up, since it compares the device model written in the FTF with a database, and since the entry I made was customized, it's not showing up.
What I'm going to do is to check if there's any update in Emma, if so, I'll update the file with new bootloader update.
Click to expand...
Click to collapse
Thanks fo your help. BTW I have downloaded version 0.9.18.6 from this linkhttps://drive.google.com/file/d/0B1AAC4lt7nzOQzR3aTZKUFZqem8/view?pli=1 and it's working fine for me.
hi, I have stock kitkat so can i still update my bootloader using flashtool, i have root and unlocked bootlloader
Emma won't open for me, it shows the splash screen and then nothing comes up, the process is there running, but the program won't show up.
And via FTF the flashtool 0.9.18.6 gives an error and won't flash the FTF in my device.
I have a D2306, running the FW 18.3.C.0.37
gabrielmr said:
Emma won't open for me, it shows the splash screen and then nothing comes up, the process is there running, but the program won't show up.
And via FTF the flashtool 0.9.18.6 gives an error and won't flash the FTF in my device.
I have a D2306, running the FW 18.3.C.0.37
Click to expand...
Click to collapse
The update's only compatible with 18.3.1.C.1.17 and above, AFAIK, so that might be your issue.
linuxct said:
The update's only compatible with 18.3.1.C.1.17 and above, AFAIK, so that might be your issue.
Click to expand...
Click to collapse
It worked, I just started Flashtool in administrator mode.
Flashtool and Emma gives a hard time (Jul 2016)
Hi,
Same as gabrielmr... Emma installed, seems to update and restart, and then disappear in the background. Ok, then I'll use flashtool. Oh wait, there is a new version, before all, I'll update it and then flash the ftf. So I updated to latest version and... no way to see that firmware. If I had read the tread closely, I would have seen that flashing with Flashtool Version 0.9.19.8 would have taken 2 seconds, instead of trying my best to use the last flashtool version, which doesn't show the downloaded firmware XPERIAM2_1.716_BOOTLOADER_UPDATE_(ONLY_OPEN_DEVICES).ftf.
Just saying for noobs following the procedure.:cyclops:
Can anyone explain to me what are advantages of updating bootloader? Is it like only for custom roms, or unlocked bootloader or what? Please, thank you in advance
aleksa069 said:
Can anyone explain to me what are advantages of updating bootloader? Is it like only for custom roms, or unlocked bootloader or what? Please, thank you in advance
Click to expand...
Click to collapse
Basically yes only for unlocked bootloader devices
Hey, i have got problem with Flashtool. AVAST Says, that version have malware. Can someone send my that version witchout malware?
Hello, it will work with Xperia m2 dual d-2302?,
Thanks in advance
Sent from my D2302 using Tapatalk
Unpacking tool nb0 firmware files used my Infocus/Nokia (made by FIH mobile)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you want to repack nb0 image:
edit files "list" of unpacked nb0 image, remove .md5 file from list.
Not guarantee moded packed nb0 will work - OST may give an error. Some images work some require md5. Depending from mlf content.
05.04.18 v3.4
-fixed long filenames in nokia firmware
-added repacking (may not working for new images for OST 3.1.4 with md5 check permanent)
27.01.18 v3
-added unpacking for nokia firmwares
-supporting images up to 6 gb
Thank you for the tool. Took a lot of searching to find this topic for v2.
Unfortunately Nokia has changed something in the .nb0 format and the extracting fails mid process.
Can you take a look with nokia 8 firmware file? NB1-308B-0-00WW-B01_2 Nokia 8.rar from https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
@heineken78 why it keeps on crashing with arithmetic problems?
wolfyapl said:
@heineken78 why it keeps on crashing with arithmetic problems?
Click to expand...
Click to collapse
tool is updated
Hello.
Tried using it, but the button for selecting file to pack back is not working (cannot click on it).
Tried with v2, but receive that arithmetic error.
Can you help me?
ktutza2006 said:
Hello.
Tried using it, but the button for selecting file to pack back is not working (cannot click on it).
Tried with v2, but receive that arithmetic error.
Can you help me?
Click to expand...
Click to collapse
Packing back is now in development. OST is using special table now for different files, so not 100% packing is ok.
But you dont need it! You can flash in OST by selecting of unpacked .mlf file
Yes, thanks, tried that, working.
I need now to figure a way to change the system.img, cause the md5 check is ruining that for me.
The version of firmware i have for okia 6 ta-1003 have no .mlf file, and if i try to take just the system.img file from it and put in ta-1000 extracted firmware(same hardware, different android customisation, 1000 is for china) i get a md5 error.
If i manually update the size and md5 checksum in md5 file, also crashed.
A bit offtopic here, but anyway, thanks for the tool, is very helpfull
@heineken78, Still have arthimetric error, and the password for emmc zip file is WLBGFIH123 if you care to add. Thank you!
my computer freezes in unpacking process, what to do?
EDIT: Nvm, i unpacked it successfully, tnx for tool
SkaboXD said:
my computer freezes in unpacking process, what to do?
EDIT: Nvm, i unpacked it successfully, tnx for tool
Click to expand...
Click to collapse
updated
can you please look if problem with unpacking this nb0 is with your tool or with rom file?
in unpack progress a get error about out of memory... more info here
thanks
SkaboXD said:
my computer freezes in unpacking process, what to do?
EDIT: Nvm, i unpacked it successfully, tnx for tool
Click to expand...
Click to collapse
I'm having the same issue, how did you fix it?
Loku_kika said:
I'm having the same issue, how did you fix it?
Click to expand...
Click to collapse
just wait for it to flash, it took around 5 minutes for me, when you see that is not responding just click on app and it will update unpacking status.
I found a scatter file after extracting. can I simply extract .nb0 file and flash with sp flash tools or there is something additional needed before flashing the extracted content through sp flash tools?
@heineken,
can you check nokia 3.1 nb0 file, looks like they changed something, again ...
ES2-042E-0-00WW-B02
b.r.
Whenever I try to unpack the NB0 (Nokia 7 plus TA-1046) file using the NB0 tool v3.4, it always gives me an error (see screenshot) and if I click on "Continue", it gets stuck in halfway.
@heineken I am trying to unpack the Nokia 2.1 firmware (nb0) and the tool is only able to read the first 2 files. Do you have any idea and can we expect an update to the tool?
@singhnsk
for E2M-021Q-0-00WW-B02.nb0 you can use nb0-utils.exe or nb0-utils.jar
regards
Now available on neon through qtapp.
Qtapp which is part of Neon can be downloaded from Neon Updater latest
Sometimes you must install vccred15 from microsoft
kenkitt said:
Now available on neon through qtapp.
Qtapp which is part of Neon can be downloaded from Neon Updater latest
Sometimes you must install vccred15 from microsoft
Click to expand...
Click to collapse
So it would seem now that a username and password is required. How do i get pass this if possible without sending an email
Never mind, i saw the application qtapp installed as well. Thanks.