[Tool] unpack Repack nb0 Rom - General Topics

***********************Unpack Repack nb0 Rom******************
Here Is a nb0 tool that unpacks and packs SUT nb0 factory images Used By Some manufactures like Infocus,
Requirements-
Window pc with java Installed
How to unpack
1. Paste your stock Rom File, something.nb0 in Tools Folder
2. Rename it to firmware.nb0
3. Run unpack.exe file hit enter , Done, check unpack Folder Your extracted Rom IS Present,
How To Repack-
1. cut whole Rom From unpack folder and paste in Repack Folder[ you can edit your images],
Like System app etc, don't change name]
2. Run Pack.exe hit enter Done,
3. Your New Rom Is readdy with the name System.nb0 in tools folder
Downloads-
MOD Edit :- Links Removed

bro after i unpack firmware.nb0 file theres no file that related to system.img.???

Incomplete unpacking
Sir please help to completely unpack nb0 file as sut is not working nor my phone's flashier with scatter file is available online. My phone is Infocus m330 with mediatek mt6592 chipset. It's bootloader locked with hard brick that not showing any sign of active other than when connected to pc can be flashed with v com drivers
Please help

Going to test it now ?
Thank you mate

link is dead

Thread Closed.
Thanks
SacredDeviL666.

Related

[Guide][Easiest Way] Recovery Porting For MTKs

Difficulty Level – Medium
Requirements –
.
1. Developing Skill
2. img unpack-repack tool ( kitchen or other tool)
3. Notepad++
4. Brain
.
So Let’s start.......
.
Step 1 : Unpack both ( stock and port) recovey.img
How to Unpack-Repack without kitchen? Follow this
tool/guide -->
Michfood Tools
.
Step 2 : Now open the default.prop file with
NotePAD++ from the Extracted “rmdisk” FOLDER.
Open those build.prop file do all Changes the all
changeable things what you can just like that we do
when PORTING ROM.
Then COPY the ueventd, meta & factory files those
are in (.vc) FILES from the STOCK “rmdisk” FOLDER
to PORT…
Step 3 : FROM rmdisk>etc FOLDER open
recovery.fstab FILE with NP++ .... REPLACE the from
your Stock block with PORT mmcblk ……If you want
replace with StockRecovery
rmdisk>res>recovery.fstab or with workable
RECOVERY. JUST replace the emmc block . If you dont
know your phone’s emmc block then dont do this. It
maybe harmful.
Step 4 : Now replace kernel
Step 5 : Now all the works for PORTING is now
Finished..... Repack the port recovery .img . Flash it.
Enjoy.
.
If you don't find any file unpack boot.img get them from there...
.
This method worked with my MTK6572 Device! I have ported COT, CTR, PhilZ, CWM by this method
.
Thanks to
1.Arnav
2.Michfood
3.Akib

[Tool] [Windows] Auto Tool Unpack Repack Rom Android .DAT

[Tool] [Windows] Auto Tool Unpack Repack Rom Android .DAT [No Cygwin] [No Linux]
***(Marshmallow Supported)***
Develop by MTK THAI ROM MODDER (Thiland) Group
Create Tool by: Kritsada Chaitan
SS:
Youtube : https://www.youtube.com/watch?v=nKYozWOETIU
-NOTE 1.-
***First Install Needed For Use This Tool.***
1. Java SDK
2. Python v3.xx
-NOTE 2.-
***First Copy system.new.dat , system.transfer.list To "Paste-DAT-Here" Folder.***
Download:
MEGA
Thank you Original Thread by: "xpirt" https://forum.xda-developers.com/member.php?u=5132229
Thanks for the tool
Bebooo43 said:
Thanks for the tool
Click to expand...
Click to collapse
Good.... ^^
It is a wonderful tool, brother.
is this tool works fine?
Getting error about incompatible operating system when recompressing dat so I tried on windows and got the same do I have to install the java or the phyton to a certain directory or the auto tool to a certain directory it extracted fine thanks in advance for the feedback
Can someone lend a hand.... Program works great. After removing a couple apps, one from 'app' another from 'priv-app', I made a zip file with 7zip and tried flashing but it fails. Is 7zip okay to make a zip file? was I not supposed to remove a 'priv-app' ? I can't find any solid guides on editing a MM rom. thanks in advance.
i succesfully unpack .dat files and repack .dat files (without edit anything) using this tool .
then i replace the repack .dat file to the rom and zip it and flash it .
but the problem is, when i flash i get error 7 system partition has unexpected contents after ota update . any solution ?
can't unpack system.new.dat cm14 (7.1)
Thank you very much, really useful
update - https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Is it work for N based ROMs
tooolll
worked for me also...
t.y.
please update it to new version waiting for it.

[Guide] 4 ways to unpack/repack boot/recovery/logo without pc [IMG and BIN files]

In this guide I'm going to tell you about unpacking/repacking your boot(kernel),recovery.
I won't be responsible if u kill your phone and your mom beat the hell outta u.
Please do some research before trying this stuffs.
Method 1----
Put your boot or recovery.img in root/cache/here folder.
Get apktool mobile.
Open it and navigate to root folder.
Press hold on cache folder
Click on 'Get access permission(root)'
Now click on your img file
Select and click unpack all(mt6***) and bang...
U will see unpacked everything there.
And to repack click ramdisk folder and hit repack mt**** ...
Method 2---
Get unpack repack boot.img apk from google play
Put your boot.img in your SD card(default write disk)
Create a folder and name it unpack in SD CARD.
open that app and search for boot.img in SD CARD
Select it
Choose where to unpack(choose unpack folder)
Hit start and done
To repack,find out kernel base,page size in unpack folder.
Write them down in repack option
Select the zlimage(kernel) and select ramdisk
select the 'unpack' folder(where new img will b created)
click start and done
Method 3---(Advance Stuff)
Get Android Image Kitchen from play store
Open and click on ( ) sign
Select unpack and select boot.img or recovery.img
(U must should put the img in root of your default sd card and don't rename it)
U will see two folder like
ramdisk
and
kernel stuff
press hold on them and export them to modify
U can repack in same way by clicking repack option.
Method 4---
There is already a guide on xda about un/repack using terminal emulator.
U can check that out if u want to.
Facing problems?
comment below..
bump

MTK Firmware Backup & Extraction ( All Partitions )

Acquire a similar scatter file for another device.
Use ADB to extract Partition information.
Edit similar Scatter using ADB and Device for Reference's.
Add the Partition information into the similar scatter.
Test scatter file for proper PMT & HW Chip ID.
Error & Repairs for HW ID Mismatch & PMT Changed.
Test Error repaired scatter to extract Preloader.
Extract preloader from BOOT_0.
Test Preloader with boot.img extraction & download.
Save Scatter file & Preloader into a safe place.
Use Scatter & Preloader for Memory Test.
Use Memory Test information for Read back of entire Memory.
Save Full Read back to a safe place.
Extract System.img, Boot.img, Recovery.img, NVram.img, NVDATA.img, frp.img, Etc.
Compile Firmware for SP Flash Tool.
Edit & Remove proprietary information from firmware for custom release.
Leave stock for stock Firmware extraction.
For Pure time consumption reasons, this guide may take me a while to complete, however the steps above should give you a rough idea of how everything is going to be written...
To start with, the information is so much at once, that I've made a video to help people go along with it...
The video is in 2 parts & in English... Please watch these first, that'll cover about everything in the steps except a few things like compilation of extracted IMG files.
The second video should be watched after the first video, so I've put that link in the description of video 1.
https://youtu.be/e2_U68EGSlY
OK... Now you've seen the instructions, you can work through extracting every partition you'll need for a firmware backup.... You don't need all of them !
After that, Copy the following files (you should now have them all ) to a new folder called Stock Firmware for SP Flash Tool ..
boot.img
cache.img
lk.img
logo.img
preloader.bin
recovery.img
secro.img
system.img
trustzone.bin or .img
userdata.img
MT*****_Android_scatter.txt
Now you need to edit the Scatter file using NotePad++ or another program that won't wreck line endings... Word pad & Notepad will wreck line endings and destroy the scatter file.
Edit the scatter file to now have the correct file names, eg.....
preloader_******_njh_gjb_.bin TO preloader.bin - The same as your copied file name.
boot_example_mt.img TO boot.img - The name of the file for boot.
Now the scatter file, Image's & Preloader should be all together...
ZIP the folder to remove empty space in .img files, Shrink the Firmware to a Zip file.....
You just need to extract the zip file and open the scatter file in SP Flash Tool v5.16+ .. Then select Download to do a firmware installation.
I will edit this guide in time, however I just wanted to get out how I do this on my MTK Device's... People keep asking me how to do it, so I released the video and this extra information for them... I don't make money on YouTube so everything here is provided free & I don't make any money from helping !!! Sorry about the terrible audio !

A7 (2018) – Working TWRP

Hi!
I tried 4 TWRP versions that i found on youtube and this forum, but none seems to work. Each version makes my screen glitchy then restarts into bootloop.
Can someon help me with the right TWRP version for my device?
RP SWREV: B:5 K:5 S:5
Device is SM-A750FN
{
"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"
}
itsmirel said:
Hi!
I tried 4 TWRP versions that i found on youtube and this forum, but none seems to work. Each version makes my screen glitchy then restarts into bootloop.
Can someon help me with the right TWRP version for my device?
RP SWREV: B:5 K:5 S:5
Device is SM-A750FN
View attachment 5264873
Click to expand...
Click to collapse
Download the stock recovery and any TWRP from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Tab E said:
Download the stock recovery and any TWRP from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Click to expand...
Click to collapse
Yes, my bootloader is unlocked (if you mean to ask if i have checked OEM/USB debugging in developer mode), I unlocked it first time i tried to run TWRP.
By "repack this image and FLASH IT", flash it using Odin, right?
My current TWRP is unaccessible
Tab E said:
Download the stock recovery and any recovery from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Click to expand...
Click to collapse
itsmirel said:
Yes, my bootloader is unlocked (if you mean to ask if i have checked OEM/USB debugging in developer mode), I unlocked it first time i tried to run TWRP.
By "repack this image and FLASH IT", flash it using Odin, right?
My current TWRP is unaccessible
Click to expand...
Click to collapse
Is fastboot available? If yes then use fastboot to flash. If no try odin
Tab E said:
Is fastboot available? If yes then use fastboot to flash. If no try odin
Click to expand...
Click to collapse
I guess so
Ok great. Then go ahead with fastboot
Tab E said:
Ok great. Then go ahead with fastboot
Click to expand...
Click to collapse
i will use odin, i dont know how to enter fastboot and couldnt find
Tab E said:
Download the stock recovery and any TWRP from the internet for your device. Downlaod carliv image kitchen and extract your stock recovery. Copy recovery.img-kernel and “recovery.img-kernel_offset”to any location in your pc. Now take the TWRP for your phone that you download but it's not WORKING. Extract it in the same way using carliv image kitchen. Form this extracted TWRP of your device delete recovery.img-kernel and “recovery.img-kernel_offset” and replace it with the file you copied from your stock recovery in the first step. Then repack this image and flash it. BTW is your bootloader unlocked?
Click to expand...
Click to collapse
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
itsmirel said:
i will use odin, i dont know how to enter fastboot and couldnt find
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
Click to expand...
Click to collapse
ALSO, the stock rom i downloaded has only .md5 files
itsmirel said:
i will use odin, i dont know how to enter fastboot and couldnt find
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
Click to expand...
Click to collapse
itsmirel said:
i will use odin, i dont know how to enter fastboot and couldnt find
can you be more specific please? i dont know and understand how to use carliv image kitchen
this is what i downloaded
Click to expand...
Click to collapse
Use md5 firmware extractor
[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-D710)
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs...
forum.xda-developers.com
Open carliv.bat batch file.
Copy your device’s stock ROM’s recovery.img and paste it in the “recovery-resources” named folder that is located inside the unzipped folder.
In the Carliv Image Kitchen window, type in R and press enter. Next, type 1 and hit enter again.
Type 1 to unpack the image file that you downloaded earlier.
If you get a message, “Your image is unpacked in recovery folder”, you have successfully unpacked the image file.
Now open the recovery folder in the Carliv unzipped folder. Look around for a folder named “ramdisk” and other files.
Create a new folder somewhere and name it “stock” (you can name it anything you want). Copy and paste all the contents from the “recovery” folder (ramdisk folder and all 10 other files).
Next, delete the recovery.img file that was left behind on the “recovery-resources” folder before.
Also, delete all the contents in “recovery” folder.
Copy and paste the custom recovery image file, the TWRP that you want to port into the “recovery-resources” folder.
You will need to repeat the same steps as before.
never delete the custom recovery image in the “recovery-resources” folder.
Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the stock folder and paste it to the TWRP which you extracted in recovery folder in carliv image kitchen . Overwrite it to replace existing files with the same name.
In the Carliv Image Kitchen window, type 2 and hit the enter key.
A message notifying that the image file was repacked will appear. You can view it on the output folder named “output”. This is the brand new TWRP ported image file.
Copy the newly made image file from the “output” folder and paste it to a new folder. Rename it as you want with any name of your choice. Hope it helps. If you are still stuck I'll do it for you
Tab E said:
Use md5 firmware extractor
[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-D710)
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs...
forum.xda-developers.com
Open carliv.bat batch file.
Copy your device’s stock ROM’s recovery.img and paste it in the “recovery-resources” named folder that is located inside the unzipped folder.
In the Carliv Image Kitchen window, type in R and press enter. Next, type 1 and hit enter again.
Type 1 to unpack the image file that you downloaded earlier.
If you get a message, “Your image is unpacked in recovery folder”, you have successfully unpacked the image file.
Now open the recovery folder in the Carliv unzipped folder. Look around for a folder named “ramdisk” and other files.
Create a new folder somewhere and name it “stock” (you can name it anything you want). Copy and paste all the contents from the “recovery” folder (ramdisk folder and all 10 other files).
Next, delete the recovery.img file that was left behind on the “recovery-resources” folder before.
Also, delete all the contents in “recovery” folder.
Copy and paste the custom recovery image file, the TWRP that you want to port into the “recovery-resources” folder.
You will need to repeat the same steps as before.
never delete the custom recovery image in the “recovery-resources” folder.
Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the stock folder and paste it to the TWRP which you extracted in recovery folder in carliv image kitchen . Overwrite it to replace existing files with the same name.
In the Carliv Image Kitchen window, type 2 and hit the enter key.
A message notifying that the image file was repacked will appear. You can view it on the output folder named “output”. This is the brand new TWRP ported image file.
Copy the newly made image file from the “output” folder and paste it to a new folder. Rename it as you want with any name of your choice. Hope it helps. If you are still stuck I'll do it for you
Click to expand...
Click to collapse
The stock rom i downloaded has multiple .md5 archives. And [AP_A 750...] has inside a recovery.img.lz4 file
Should i download other stock rom? Or use this as .img.lz4
itsmirel said:
The stock rom i downloaded has multiple .md5 archives. And [AP_A 750...] has inside a recovery.img.lz4 file
Should i download other stock rom? Or use this as .img.lz4
Click to expand...
Click to collapse
Btw, the tutorial "How To Extract Files From a TAR.MD5 Stock ROM" isn't working anymore. his MyBB forum doesnt work. (MyBB has experienced an internal error and cannot continue.)
Tab E said:
Use md5 firmware extractor
[TUTORIAL] How To Extract Files From a TAR.MD5 Stock ROM (SPH-D710)
I've received a TON of PM's and emails asking how to do this and I've decided to do a write-up for everyone. Now to start off, this does not automatically make you a Super Duper Developer, this does not show you how to make your own TAR ROMs...
forum.xda-developers.com
Open carliv.bat batch file.
Copy your device’s stock ROM’s recovery.img and paste it in the “recovery-resources” named folder that is located inside the unzipped folder.
In the Carliv Image Kitchen window, type in R and press enter. Next, type 1 and hit enter again.
Type 1 to unpack the image file that you downloaded earlier.
If you get a message, “Your image is unpacked in recovery folder”, you have successfully unpacked the image file.
Now open the recovery folder in the Carliv unzipped folder. Look around for a folder named “ramdisk” and other files.
Create a new folder somewhere and name it “stock” (you can name it anything you want). Copy and paste all the contents from the “recovery” folder (ramdisk folder and all 10 other files).
Next, delete the recovery.img file that was left behind on the “recovery-resources” folder before.
Also, delete all the contents in “recovery” folder.
Copy and paste the custom recovery image file, the TWRP that you want to port into the “recovery-resources” folder.
You will need to repeat the same steps as before.
never delete the custom recovery image in the “recovery-resources” folder.
Copy the “recovery.img-kernel” and “recovery.img-kernel_offset” from the stock folder and paste it to the TWRP which you extracted in recovery folder in carliv image kitchen . Overwrite it to replace existing files with the same name.
In the Carliv Image Kitchen window, type 2 and hit the enter key.
A message notifying that the image file was repacked will appear. You can view it on the output folder named “output”. This is the brand new TWRP ported image file.
Copy the newly made image file from the “output” folder and paste it to a new folder. Rename it as you want with any name of your choice. Hope it helps. If you are still stuck I'll do it for you
Click to expand...
Click to collapse
i am in the same position, have read your guide intensively but do not succeed in finding the "recovery-resources" folder, and i my version of CiC there is no R (ecovery) in the main menu. will you be so kind to make the twrp?
benniehelder said:
i am in the same position, have read your guide intensively but do not succeed in finding the "recovery-resources" folder, and i my version of CiC there is no R (ecovery) in the main menu. will you be so kind to make the twrp?
Click to expand...
Click to collapse
Following this guide has booted TWRP on some devices. Please make sure you are on android 10
Tab E said:
Following this guide has booted TWRP on some devices. Please make sure you are on android 10
Click to expand...
Click to collapse
thx,thx,thx for the support!. I have done the carliv protocol but in the end the new compiled twrp failed in Odon. Maybe the new image converting to ,tar is the culprit? after that i tried to do the method in the video but twarp was 3 seconds visible and then back in bootloop!. i shall DL the magisk 20.3 edition. maybe that makes the difference'I bought this A7 last monday after a HUawei, that has no posibilities whatsoever for twrp or root, but in this Samsung I totally surprised that it, untill now, is so umbeatable, albeit unlocked!
benniehelder said:
thx,thx,thx for the support!. I have done the carliv protocol but in the end the new compiled twrp failed in Odon. Maybe the new image converting to ,tar is the culprit? after that i tried to do the method in the video but twarp was 3 seconds visible and then back in bootloop!. i shall DL the magisk 20.3 edition. maybe that makes the difference'I bought this A7 last monday after a HUawei, that has no posibilities whatsoever for twrp or root, but in this Samsung I totally surprised that it, untill now, is so umbeatable, albeit unlocked!
Click to expand...
Click to collapse
how to make from the new homemade recovery a tar, so you can flash with odin?
benniehelder said:
how to make from the new homemade recovery a tar, so you can flash with odin?
Click to expand...
Click to collapse
Convert TWRP .img to .tar (for ODIN)[Easy]
Sometimes the latest version of TWRP is in ".img", so some people use an older version instead, which is in .tar, so they can flash it with ODIN. The thing is that the ".tar" version is just the ".img" compressed XD, so I'm going to show you how...
forum.xda-developers.com
i had done this with z7 myself already, but to no avail, but: i began, in a moment of despair, with Odon to try all the .tars i had collected sofar , to flash and when i flashed PBRP (it was not the first time) it worked!!!. after a week the gizmo do have a recovery, that is not stock! Little new prob: By rebooting system he bootloops (for a change!) in bootloader mode.

Categories

Resources