Database Info

[TUTORIAL] Create Flashable Zip From CWM/TWRP Backup (MTK)

Hi,
today I'm going to show how to create a flashable
zip from a CWM/TWRP Backup. This is specially for MTK
device(you can try in other device,may work). Here is
my step by step tutorial...
Requirements:
* PC
* CWM/TWRP Backup
* Winrar
* Brain
you need META-INF,system & boot.img for making a
flashble zip rom, so you have to collect these from
your backup
*CWM method:
1. Copy the CWM backup from Phone to PC
2. Extract system.ext4.tar file with winrar, you
will get the system folder
3. Collect the boot.img from the backup
4. Now collect a META-INF folder from any custom
rom which is made for your device
5. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
6. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
7. Done.
TWRP method:
1. Copy the TWRP backup from Phone to PC
2. Collect the file 'system.ext4.win' rename it
to 'system.ext4.tar'
3. Extract the system.ext4.tar. Now in case if your
TWRP backup is not in compression method, you will
directly get the system folder. Or if your TWRP
backup is in compression method, you will get a
file named 'system.ext4', don't worry just again
rename it to 'system.ext4.tar' and extract to get
the 'system' folder
4. Collect the 'boot.emmc.win' file and rename it
to boot.img, now ypu manage the boot.img also
5. Now collect a META-INF folder from any custom
rom which is made for your device
6. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
7. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
8. Done.

akash_bd said:
Hi,
today I'm going to show how to create a flashable
zip from a CWM/TWRP Backup. This is specially for MTK
device(you can try in other device,may work). Here is
my step by step tutorial...
Requirements:
* PC
* CWM/TWRP Backup
* Winrar
* Brain
you need META-INF,system & boot.img for making a
flashble zip rom, so you have to collect these from
your backup
*CWM method:
1. Copy the CWM backup from Phone to PC
2. Extract system.ext4.tar file with winrar, you
will get the system folder
3. Collect the boot.img from the backup
4. Now collect a META-INF folder from any custom
rom which is made for your device
5. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
6. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
7. Done.
TWRP method:
1. Copy the TWRP backup from Phone to PC
2. Collect the file 'system.ext4.win' rename it
to 'system.ext4.tar'
3. Extract the system.ext4.tar. Now in case if your
TWRP backup is not in compression method, you will
directly get the system folder. Or if your TWRP
backup is in compression method, you will get a
file named 'system.ext4', don't worry just again
rename it to 'system.ext4.tar' and extract to get
the 'system' folder
4. Collect the 'boot.emmc.win' file and rename it
to boot.img, now ypu manage the boot.img also
5. Now collect a META-INF folder from any custom
rom which is made for your device
6. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
7. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
8. Done.
Click to expand...
Click to collapse
where is thanks button

This is awesome. Thanks for the easy tutorial. What about adding the cache and data segments as well? How would we go about doing that with the twrp backup? Thanks!

What if my TWRP backup folder got 2 system.ext4.win files?
system.ext4.win000
system.ext4.win001
What should i do to combine these 2 files into single .tar ?

You are 1 bright mutha effa
Dude,
You are the brightest Mutha Effa Ever. Thanks for sharing that; Good Thinking dude.

CYGWIN Unpacking TWRP Backup Files
limcs79 said:
What if my TWRP backup folder got 2 system.ext4.win files?
system.ext4.win000
system.ext4.win001
What should i do to combine these 2 files into single .tar ?
Click to expand...
Click to collapse
This is for Latest TWRP used with safestrap (my phone is AT&T Note 3)
rename them both seperatly
system.ext4.win000.tar
system.ext4.win001.tar
winrar and 7-zip failed for me
I used CYGWIN
CYGWIN Unpacking TWRP Backup Files

akash_bd said:
Hi,
today I'm going to show how to create a flashable
zip from a CWM/TWRP Backup. This is specially for MTK
device(you can try in other device,may work). Here is
my step by step tutorial...
Requirements:
* PC
* CWM/TWRP Backup
* Winrar
* Brain
you need META-INF,system & boot.img for making a
flashble zip rom, so you have to collect these from
your backup
*CWM method:
1. Copy the CWM backup from Phone to PC
2. Extract system.ext4.tar file with winrar, you
will get the system folder
3. Collect the boot.img from the backup
4. Now collect a META-INF folder from any custom
rom which is made for your device
5. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
6. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
7. Done.
TWRP method:
1. Copy the TWRP backup from Phone to PC
2. Collect the file 'system.ext4.win' rename it
to 'system.ext4.tar'
3. Extract the system.ext4.tar. Now in case if your
TWRP backup is not in compression method, you will
directly get the system folder. Or if your TWRP
backup is in compression method, you will get a
file named 'system.ext4', don't worry just again
rename it to 'system.ext4.tar' and extract to get
the 'system' folder
4. Collect the 'boot.emmc.win' file and rename it
to boot.img, now ypu manage the boot.img also
5. Now collect a META-INF folder from any custom
rom which is made for your device
6. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
7. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
8. Done.
Click to expand...
Click to collapse
Thanks for your thread
Just 1 question: i have see multiple flashable zip on XDA, and they have a diffrents compression level, so how decide it?

Thank you for such a simple and amazing tutorial

Great tutorial
[my phone iz better than urz]

I want to make KK Stock ROM for iBall Slide 3G 7271 HD70
Hi,
Regarding the 4th step, Their are no ROM available for this device so I don't have the files.
I have the block MAP for the device,
So could u plz guide me to make the meta files?
"4. Now collect a META-INF folder from any custom rom which is made for your device"

babai93 said:
Hi,
Regarding the 4th step, Their are no ROM available for this device so I don't have the files.
I have the block MAP for the device,
So could u plz guide me to make the meta files?
"4. Now collect a META-INF folder from any custom rom which is made for your device"
Click to expand...
Click to collapse
What version is your phone

These are the files i have.. Is UBOOT.img is necessary?
boot.img
cache.ext4
data.ext4
nandroid.md5
recovery.txt
system.ext4
uboot.img
Click to expand...
Click to collapse

akash_bd said:
Hi,
today I'm going to show how to create a flashable
zip from a CWM/TWRP Backup. This is specially for MTK
device(you can try in other device,may work). Here is
my step by step tutorial...
Requirements:
* PC
* CWM/TWRP Backup
* Winrar
* Brain
you need META-INF,system & boot.img for making a
flashble zip rom, so you have to collect these from
your backup
*CWM method:
1. Copy the CWM backup from Phone to PC
2. Extract system.ext4.tar file with winrar, you
will get the system folder
3. Collect the boot.img from the backup
4. Now collect a META-INF folder from any custom
rom which is made for your device
5. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
6. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
7. Done.
TWRP method:
1. Copy the TWRP backup from Phone to PC
2. Collect the file 'system.ext4.win' rename it
to 'system.ext4.tar'
3. Extract the system.ext4.tar. Now in case if your
TWRP backup is not in compression method, you will
directly get the system folder. Or if your TWRP
backup is in compression method, you will get a
file named 'system.ext4', don't worry just again
rename it to 'system.ext4.tar' and extract to get
the 'system' folder
4. Collect the 'boot.emmc.win' file and rename it
to boot.img, now ypu manage the boot.img also
5. Now collect a META-INF folder from any custom
rom which is made for your device
6. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
7. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
8. Done.
Click to expand...
Click to collapse
I try to follow the tutorial you created but when the flash still fails , a description that appeared md5 not found , and whether the Meta - Inf / updater - script that must be made because I was dizzy with it

irwandwiyanto said:
I try to follow the tutorial you created but when the flash still fails , a description that appeared md5 not found , and whether the Meta - Inf / updater - script that must be made because I was dizzy with it
Click to expand...
Click to collapse
You need to use the Meta folder from a working rom installer for your phone, you then select the Meta folder, system folder (hold down the ctlr key to select each folder, then right clink the selected file and zip.

carl1961 said:
You need to use the Meta folder from a working rom installer for your phone, you then select the Meta folder, system folder (hold down the ctlr key to select each folder, then right clink the selected file and zip.
Click to expand...
Click to collapse
how do I get the Meta folder from the backup of my ROM ?

irwandwiyanto said:
how do I get the Meta folder from the backup of my ROM ?
Click to expand...
Click to collapse
sorry I meant META-INF folder, you use the META-INF from a working rom install for your phone. Look under your phones thread here on XDA and locate a rom and use it to go with your backup files so you can make a install of your backup

Question onf TWRP Step 3
akash_bd said:
Hi,
today I'm going to show how to create a flashable
zip from a CWM/TWRP Backup. This is specially for MTK
device(you can try in other device,may work). Here is
my step by step tutorial...
Requirements:
* PC
* CWM/TWRP Backup
* Winrar
* Brain
you need META-INF,system & boot.img for making a
flashble zip rom, so you have to collect these from
your backup
*CWM method:
1. Copy the CWM backup from Phone to PC
2. Extract system.ext4.tar file with winrar, you
will get the system folder
3. Collect the boot.img from the backup
4. Now collect a META-INF folder from any custom
rom which is made for your device
5. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
6. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
7. Done.
TWRP method:
1. Copy the TWRP backup from Phone to PC
2. Collect the file 'system.ext4.win' rename it
to 'system.ext4.tar'
3. Extract the system.ext4.tar. Now in case if your
TWRP backup is not in compression method, you will
directly get the system folder. Or if your TWRP
backup is in compression method, you will get a
file named 'system.ext4', don't worry just again
rename it to 'system.ext4.tar' and extract to get
the 'system' folder
4. Collect the 'boot.emmc.win' file and rename it
to boot.img, now ypu manage the boot.img also
5. Now collect a META-INF folder from any custom
rom which is made for your device
6. Now select META-INF,system & boot.img, click
right button of your mouse and select 'Add to archive'
now select archive format 'ZIP' and press ok
7. Your flasable zip rom is ready. Just copy it
to your sd card and flash with CWM or TWRP
8. Done.
Click to expand...
Click to collapse
QUESTIONS
---------------------------
1. On STEP 3 I did the following:
Extract the system.ext4.tar.
If your TWRP backup is in compression method, you will get a file named 'system.ext4',
Rename it to 'system.ext4.tar'
Next part, " Extract to get the 'system' folder", does not work. What do I do here?
2. Doing #1 in Linux or does this need to be done win Windows?
3. META-INF - My HTC ONE X+ (code name evitare UL) does not have any custom ROMs I can find. What other sources of META-INF are there?
Please notify me at [email protected] when you post answers. Thanks
Click to expand...
Click to collapse

[email protected] said:
QUESTIONS
---------------------------
1. On STEP 3 I did the following:
Extract the system.ext4.tar.
If your TWRP backup is in compression method, you will get a file named 'system.ext4',
Rename it to 'system.ext4.tar'
Next part, " Extract to get the 'system' folder", does not work. What do I do here?
2. Doing #1 in Linux or does this need to be done win Windows?
3. META-INF - My HTC ONE X+ (code name evitare UL) does not have any custom ROMs I can find. What other sources of META-INF are there?
Please notify me at [email protected] when you post answers. Thanks
Click to expand...
Click to collapse
Rom List
You can get your META-INF from one of them
Extract to get the system folder:
CYGWIN Unpacking TWRP Backup Files
Download CYGWIN http://cygwin.com/
rename:
data.ext4.win to data.ext4.win.tar
system.ext4.win000 system.ext4.win000.tar
system.ext4.win001 to system.ext4.win001.tar
Make a directory in your CYGWIN Home [Username]folder
Example: untar
Use Windows File Explorer go to your CYGWING Home
C:\cygwin\home\carl (your user name will be here)
make any folder you choose
Example:
C:\cygwin\home\carl\untar
and C:\cygwin\home\carl\untar\data ( for data files)
put your renamed data files in a folder named data
C:\cygwin\home\carl\untar\data (this is to keep files separate when unpacked)
While in Explorer put your renamed system files in untar folder
start CYGWIN ( Use the Cygwin Terminal and then you can copy and paste these commands)
cd to untar folder
example:
cd\untar
do these commands one at a time, it will extract to a folder named system
tar -xvf system.ext4.win000.tar
tar -xvf system.ext4.win001.tar
cd to data
do this command
tar -xvf data.ext4.win.tar
tar -xvf data.ext4.win000.tar
tar -xvf data.ext4.win001.tar
all your data files will extract
Click to expand...
Click to collapse

carl1961 said:
What version is your phone
Click to expand...
Click to collapse
This is iBall Slide 7271 HD70 with preloaded KitKat 4.4.2

I lost my nandroid backup of stock network carrier's ROM so my friend made backup using same TWRP recovery and now I want to build flashable zip. He excluded only data and cache.
There are some things that confuses me.
This device (Alcatel OT M' Pop) has custpack.ext4.win. Do I have to include it and how?
This is all files from backup:
{
"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"
}
Also I used Cygwin Terminal to unpack system.ext4.win because 7Zip and WinRar gave me errors during unpacking process but interesting thing is that when I open archive with 7zip I can see META-INF folder Can I use that META and how the hell WinRar doesn't show it? Or is it safer to include META from another ROM for this device?

BLU DASH 5.0 D410a Stock ROM Images + Root + TWRP

STOCK ROM IMAGES BLU DASH 5.0 D410a V27-GENERIC Android Kitkat 4.4.2 MT6572 Chipset (no UBIFS)
PLEASE READ THE INSTRUCTIONS BEFORE FLASHING YOUR PHONE SO THAT YOU WON'T BRICK IT.
EDIT: 14 January 2015. Updated the TWRP 2.8.2.0 download link. Fixed the problem where ADB and MTP was not functioning in TWRP. Added backup support for a few other partitions including the Baseband.
EDIT: 19 January 2015. Changed method of rooting and added flashable zip with modified kernel to add init.d support (that was tested and is functioning properly.)
STEP 1
BACKUP YOUR MEDIATEK DEVICE
Prerequisites
All of the software is for Windows.
Download and Extract the MTK USB Drivers and the SP Flash Tool found closest to the top of the list at:
http://mtk2000.ucoz.ru/
Press the play button to the right of the file to start the download.
Download MTK Droid Root & Tools
Latest version can be found by following the link of the following post.
http://forum.xda-developers.com/showpost.php?p=38320254&postcount=1
Hint: Click the show content button to see the link to another forum with the download link
Direct Download Link of MTK Droid Root & Tools if you are having problems getting the link.
http://depositfiles.com/files/ne1gnposp
You will need Winrar to extract the files.
That can be downloaded from: http://www.rarlab.com/download.htm
READ HERE ON HOW TO BACKUP: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Thanks to @rua1 for the instructions and software.
NOTE: I WOULD RECOMMEND BACKUPING UP THE USRDATA PARTITION AS WELL TO DO THAT USE HEX "0X96B40000" AS THE LENGTH DURING READ BACK IN SP FLASH TOOL
To flash the DASH 5.0 you need to use the Preloader to do it.
STEP 2
Installing the Preloader Driver (READ this section entirely before trying)
Open Device Manager
Start -> Run
Type:
Code:
devmgmt.msc
Press Enter
Turn off the phone until it is completely shut down with nothing plugged in the USB port. You will see the screen go black and shortly afterwards it will vibrate.
With Device Manager open, connect the USB cable to the phone without turning it on.
You will see the MT65XX Preloader appear (see image)
{
"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"
}
Quickly double click MT65XX Preloader before it disappears, if it disappered, just unplug and plug back in the cable and try again.
Under the Driver tab, click Update Driver, click Browse my computer for driver software.
Using the Browse button find the MTKUSBAll folder you extracted and click on "New inst. win 7&8x64" and click OK
Click Next
If you get the message "Windows can't verify the publisher of this driver software", just click "Install this driver software anyway"
Click Close
Click Close
After the driver is installed you can unplug the phone.
STEP 3
Uploading the image files to the phone{/B}
WARNING: The BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip file has all of the necessary images but do not flash them unless you trying to recover from a brick.
DO NOT FLASH THE PRELOADER.BIN AS IT MAY BRICK YOUR PHONE.
THE ONLY FILES I HAVE PERSONALLY TESTED ARE boot.img, factory_NONmodified_recovery.img and system.img
Download BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip from here:
http://d-h.st/3L9G
See Step 5
Extract the SP Flash Tool.
Extract the system.img and MT6572_Android_scatter.txt (and/or boot.img and factory_NONmodified_recovery.img, if you wish)
Open the SP Flash Tool
Click the Download tab
Click the Scatter-loading button and select the MT6572_Android_scatter.txt file.
Click the location of ONLY the parition(s) you are going to flash: ANDROID = SYTEM partition (system.img), BOOTIMG = KERNEL (boot.img) and RECOVERY=RECOVERY (factory_NONmodified_recovery.img or custom recovery file)
Select the image file (e.g. system.img or system_rooted.img)
MAKE SURE ALL OTHERS ARE NOT TICKED
Click the Download button.
Plug in the phone or unplug and plug it back in to start flashing the images to the phone.
Note: This can also be done with the battery removed.
Your phone will have root.
STEP 4 - Adding TWRP
First we need to rename the file recovery-from-boot.p found in the /system folder.
Using a File Manager with root permissions rename
Code:
recovery-from-boot.p
to
Code:
recovery-from-boot.bak
OR
From an adb shell, rename the file
Code:
su
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
Now turn off the phone and with SP Flash Tool flash TWRP 2.8.2.0. Download link below.
NOTE: Select only the RECOVERY partition to flash. TWRP themes are supported as well as the Aroma File Manager.
http://d-h.st/aQmt
STEP 5 - Rooting and adding init.d support
Go to http://download.chainfire.eu/supersu
Download the latest SuperSU.
Go to http://d-h.st/AJQ
Download the init.d support zip file.
Boot to TWRP while connected to a PC with adb tools run the command
Code:
adb reboot recovery[/url]
OR
Hold down the power select Reboot and hold down the volume up button until you see the TWRP logo.
Via the install menu, flash the SuperSU zip and inti.d support zip.
ALL DONE!
THANKS:
[user=631273]@Chainfire[/user] for SuperSU
[user=5119815]@rua1[/user] for MTK Droid Root & Tools and instructions on how to use SP Tools
[user=4478781]@yuweng[/user] for creating the tool to make TWRP for MediaTek devices
[user=912474]@Dees_Troy[/user] for TWRP

I will give a brief explanatoin and will elaborate more when I have the time.
For Root:
Thanks to @Chainfire
I basically mounted the system.img in a Linux OS and copied the files from the SuperSU v2.36 zip file and placed them in their relevant directories added the relevant permissions, etc.
For init.d scripts
Thanks to @alireza7991
See his thread: http://forum.xda-developers.com/showthread.php?t=2287540
I modified the kernel to boot and created a flashable zip that adds busybox to /system/xbin and creates the necessary folders then flashes the modified kernel.
For TWRP:
Thanks to @yuweng
I used Easy Magic TWRP Installer for MTK. See http://forum.xda-developers.com/showthread.php?p=53752834#post53752834
It worked but changed my partition information for some reason even though the size fit my paritition size. I wiped my phone and lost my baseband and recovered it. Posted a new thread on how to do that. See http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
That is why I posted the image file so no one has to face that problem too. I tested it and it is functioning without any problems.
You can follow yuweng's thread to make it smaller if your partition size is smaller than 6MB for some phones, at a cost of course.

Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh

After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.

jorgefar said:
After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.
Click to expand...
Click to collapse
What procedure did you use to flash it?

SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok

jorgefar said:
SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok
Click to expand...
Click to collapse
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img

Thanks for you le answer! Thats right, is a Blu Dash 5.0 D410a, I try on Monday the suggested and post results!!!

Hi again, flashed system and recovery only, stuck on Blu screen again, try wipe and reset cache, stuck on screen Blu,any recomendation??

Added a flashable zip to add init.d and install LInk2SD with a modified mount script to run properly on this phone, BLU DASH 5.0 D420a running V27 Android 4.4.2.
See post #3

dechronic said:
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img
Click to expand...
Click to collapse
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.

Sexyr said:
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.
Click to expand...
Click to collapse
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.

dechronic said:
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.
Click to expand...
Click to collapse
Cool got it and am on v27 now. thanks..... now if ony there were other roms for it ah well, at least i'm rooted again with recovery.

can i flash this on BLU Dash 5.0 D400a

dechronic said:
Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh
Click to expand...
Click to collapse
This say file no longer available..could it be downloaded elsewhere?

Does this work on 5.0+?

Stiffymeister said:
Does this work on 5.0+?
Click to expand...
Click to collapse
Don't think so but I think I have a 5.0+ image. Anything in particular you looking for? I should be able to provide it tomorrow

i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27

dlongnasty said:
i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27
Click to expand...
Click to collapse
I probably need to redo the steps for a couple of the posts.
Download the TWRP at http://d-h.st/aQmt
Upload it to the phone. Make sure that only recovery is ticked in the Smart Phone Flash Tool (SP Flash Tool) and select the file you downloaded. You should be able to figure out the rest based on my instructions.
Flash SuperSU which can be downloaded from http://download.chainfire.eu/supersu
It will rename the file that would put back the original recovery.
That should be it.

got it working thanks. are their any custom roms for the d410a?

[Guide][SC8830/SC7731/SC9830]Custom ROMs Porting Guide for Spreadtrum phones.

Thread will be best viewed in website
Code:
[CENTER][COLOR="red"]Your warranty is now void.[/COLOR]
I am not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research before asking help and reporting bugs.
Please read the entire OP instructions and FAQ,if any.
You are choosing to make these modifications, and if
you point the finger at me for messing up your device, I will laugh at you.
A lot.[/CENTER]
This thread is for spreadtrum Marshmallow, lollipop and KitKat phones. I made this guide for porting especially CM/CM based ROMs. This thread is in under progress, I'll be keep adding and changing things. These lines will be removed when I think I'm done.
Requirements
A PC /Laptop /Even your android phone is enough for porting, since your not building ROM, provided that you know how to get things done
Android Image Kitchen
A ZIP archiver(winzip,7z,etc)
Notepad++/your favorite one
HEX Editor (for Android available on play store)
A working brain with basic understanding skills properly installed
An Android device with the chipset as per the title (of cource this will work on iPhone and Windows phones but sadly my kitten eaten flashing instructions , so blame my kitty:silly
A working custom recovery (if you don't have one, this thread might help you)
Aroma File Manager (this is used to skip the process of extracting system files from system.ext.win and system.new.dat and compressing it back)
Stock ROM (extracted to easily accessable folder, since we are going to port the ROM not using normal File Manager but a recovery based file manager
Custom ROM(S) (download links are in the 2nd post)
I'll suggest you to concentrate on booting the ROM rather fixing bugs at first shot, because if we are sure that the ROM boots we can go further, otherwise it's waste of time.
{
"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"
}
Marshmallow ROM porting guide
=> Download and Extract the ROM. Since ROM(S) is zipped out of custom recovery backup you'll see system.ext4.win (which is a compressed system folder) boot.emmc.win (boot.img) and some, maybe, compressed using system.new.dat.
Porting boot.img
=> Copy stock boot.img to working directory of AIK
=> Unpack boot.img and rename ramdisk to ramdisk.s and split_img to spli_img.s
=> Copy boot.emmc.win to working directory of AIK and rename it to boot.img
=> Unpack boot.img
=> Replace the following
/ramdisk/lib/modules with /ramdisk.s/lib/modules
/ramdisk/lib/modules/mali.ko with /system/lib/modules/mali.ko from stockrom
=> delete split_img and rename split_img.s to split_img
repack it and rename image-new.img to boot.emmc.win and replace Custom ROM boot.emmc.win with ported boot.emmc.win.
Porting System
=> Boot to recovery and wipe system, data, cache and dalvik-cache and flash the CM13/Marshmallow ROM
=> Go back to tab menu of TWRP tap on 'Mount tab' Mount system and go back to flash tab and flash aroma file manager zip
=> Now you are on Aroma FM. Copy and replace the following files with stock ROM files:
/system/lib/hw/<all files> except files audio.primary.sc8830.so & bluetooth.default.so
/system/etc/ all audio related files except audio_effect.conf
/system/etc/codec_pga.xml
/system/etc/ media related files
/system/etc/tiny_hw.xml
/system/lib/egl/libGLES_mali.so
/system/lib/libEGL.so
/system/lib/libGLES_trace.so
/system/lib/libGLESv1_CM.so
/system/lib/libGLESv2.so
/system/lib/libMali.ko,if any
=> After replacing files exit Aroma FM and reboot the system. Booting will take a while (~10m) so please be patient.
Bug Fixing Guide
Camera Fix
Open lib files one by one on stock rom lollipop & search for "_ZN7android5Fence4waitEj"(without quotes) with notepad++ (mainly look into the files related to camera.sc8830.so, to know open it with HeX editor and see what are the necessary lib***.so files)
In my case "_ZN7android5Fence4waitEj" are available on stock libui.so where that file needed by camera.sc8830.so
SO open camera.sc8830.so with HexEditor and search for libui.so
Then rename libui.so of stock rom file to libcm.so and save it
Copy and paste modified file to the exact directory and wipe data, cache, dalvik-cache (data is nedded because if the camera HAL fails to load at first time CM ROMs won't show camera app in that case it is must to wipe data)
Then reboot & make sure camera.sc8830.so loaded correctly with logcat
Fix for possible bootloops when porting Marshmallow ROM using lollipop kernel
Soon.....
Note:-I'm sure the marshmallow ROM(s) will boot on lollipop device also (because I personally tested with my phone but I need confirmation that this works on marshmallow devices also.
Lollipop ROM porting guide
Porting boot.img
=> Copy stock boot.img to working directory of AIK
=> Unpack boot.img and rename ramdisk to ramdisk.s and split_img to spli_img.s
=> Copy custom ROM boot.img to working directory of AIK
=> Unpack boot.img
=> Replace the following:
/ramdisk/lib/modules with /ramdisk.s/lib/modules
/ramdisk/lib/modules/mali.ko with /system/lib/modules/mali.ko from stockrom
delete split_img and rename split_img.s to split_img
repack it and rename image-new.img to boot.img and replace Custom ROM boot.img with ported boot.img.
Porting system
=> Boot to recovery and wipe system, data, cache and dalvik-cache and flash the CM12/lollipop ROM
=> Go back to tab menu of TWRP tap on 'Mount tab' Mount system and go back to flash tab and flash aroma file manager zip
=> Now you are on AromaFM. Copy and replace the following files with stock ROM files:
/system/lib/egl/libGLES_mali.so
/system/lib/hw/<all files> except files audio.primary.sc8830.so & bluetooth.default.so
/system/lib/modules<all files>
/system/vendor/lib/libbt-vendor.so with stockrom /system/lib/libbt-vendor.so.
=> After replacing files exit Aroma FM and reboot the system. Booting will take a while (~10m) so please be patient.
Typing Bug Fixing Guide
KitKat ROM porting guide
Porting boot.img
=> Copy stock boot.img to working directory of AIK
=> Unpack boot.img and rename ramdisk to ramdisk.s and split_img to spli_img.s
=> Copy custom ROM boot.img to working directory of AIK
=> Unpack boot.img
=> Replace the following
/ramdisk/sbin files with /ramdisk.s/sbin files
/ramdisk/init.sc8830.usb.rc with /ramdisk.s/init.sc8830.usb.rc
/ramdisk/init.usb.rc with /ramdisk.s/init.usb.rc
=> Delete split_img and rename split_img.s to split_img
repack it and rename image-new.img to boot.img and replace Custom ROM boot.img with ported boot.img.
Porting system
=>Replace the following:
/system/lib/egl/<all files>
/system/lib/hw (following files) :
camera.sc8830.so
camera2.sc8830.so
gralloc.default.so
gralloc.sc8830.so
hwcomposer.sc8830.so
keystore.default.so
lights.sc8830.so
local_time.default.so
power.default.so
sensors.sc8830.so
sprd_gsp.sc8830.so
/system/lib/modules<all files>
/system/vendor/lib/libbt-vendor.so with stock ROM /system/lib/libbt-vendor.so
Booting will take a while (~10m) so please be patient)
NOTE: If you stuck at Splash Logo (Manufacturer's logo) then delete CM11/system/lib/egl/libGLES_mali.so from recovery and then wipe data, cache, dalvik-cache and reboot.
Bug Fixing Guide
Camera Fix
Copy files camera.sc8830.so, camera2.sc8830.so & libandroidfw.so from stock ROM
Rename libandroidfw.so to libandroidcm.so
=> Download and install Hex Editor (Users who are using Android for porting can use Hex editor from playstore)
Open camera.sc8830.so with Hex Editor and search for libandroidfw.so & rename it to libandroidcm.so
Save camera.sc8830.so file, copy and paste it to CM/CM based ROM
Do the same for camera2.sc8830.so
This will fix the error "Cannot load Camera HAL" which is caused by camera.sc8830.so mising start_SprdPrefTracking & stop_SprdPrefTracking argument which is available only on original libandroidfw.so on your stockrom.
Reboot your device
If you haven't seen camera app then you may need to wipe the data and dalvik-cache but there is an alternative for this. The alternative is using third party camera app from play store if the camera works then you are good to go
but to have CM stock camera you must need to wipe data
WiFi/Hotspot fix
Part - I
Make sure your stock ROM WiFi (WLAN) driver name is sprdwl.ko on /system/lib/modules
Copy the following folder(s) from stok rom & paste to cm-11.0 rom
--/system/etc/wifi/<all files>
/system/etc/dhcpcd/<all files>
--/system/etc/connectivity_calibration.ini (related to WiFi connectivity)
--/system/etc/connectivity_configure.ini (related to Bluetooth connectivity)
I suggest you to replace files from Aroma FM (since we don't need to set permissions, etc which will automatically done by Aroma FM)
If you are replacing files from root explorer you need to properly set the permissions and Ownership/Group of particular for otherwise there will be no point in replacing the files and this will result in either unfixed bug or bootloop for this properly note down the permissions and Ownership/Group of individual files
for ex: /system/etc/dhcpcd/dhcpcd-run-hooks has permissions "-r-xr-x--- or 0550" and Owner is "dhcp" and Group is "shell"
Part - II
Unpack cm-11.0/based ported boot.img and replace "init.wifi.rc" file with this init.wifi.rc
Flash the modified boot.img using Flashify/ from recovery using flash image option (recommended)
To test whether the WiFi driver properly loaded or not
use terminal emulator type
Code:
su
<enter>
cat /proc/modules
<enter>
see whether the sprdwl.ko present on loaded modules list.
Try to use WiFi and immediately see the logs (use logcat Extreme app from play store) set if there are any errors
Do the same with Hotspot
as a result you may need to replace some files under --/system/bin/
ex:
--/system/bin/dhcpcd
--/system/bin/hostopad
--/system/bin/wcnd
--/system/bin/wpa_cli
--/system/bin/wpa_supplicant
etc
To root flash Magisk (systemless-root only for lollipop and above) or SuperSU
Credits: Hadi Khoirudin, Advan S4p [Official] fb group, @@ki,
@Jitheshwar (it's me :silly: )​
Created 2/10/2017
Last Updated 3/10/2017

Downloads:-
Marshmallow
CyanogenMd 13.1
Bug fix Update (extract zip and replace files and port boot.img and then zip it, boot to recovery wipe cache and dalvik-cache flash the zip and reboot)
=====================
Resurrection Remix 5.7.4
Offline Charging fix
PAC-MAN ROM
Lollipop ROMs
CyanogenMod 12.1
=====================
Resurrection Remix
WiFi-Hotspot-fix-for-CM/based-lollipop-ROMs
KitKat ROMs
PAC-MAN ROM
=====================
MIUI7-7.4.26
Video codec fix
WiFi-Hotspot-fix-for-CM/based-KitKat-ROMs
More links have been adding​

Reserved

You could have given me the credits.......well nice thread.....just a updated version of my thread

@ki said:
You could have given me the credits.......well nice thread.....just a updated version of my thread
Click to expand...
Click to collapse
But I took nothing from your work. I made this thread keeping CM ROMs in mind. But I have given credits to you in recovery porting thread since I used some of your work. Anyway you have given me Idea. PM me with more suggestions.
Edit: credits updated.

Jitheshwar said:
But I took nothing from your work. I made this thread keeping CM ROMs in mind. But I have given credits to you in recovery porting thread since I used some of your work. Anyway you have given me Idea. PM me with more suggestions.
Edit: credits updated.
Click to expand...
Click to collapse
Sorry for being so rude.......well i will try to suggest if anything good comes to my mind

Will the camera fix work with evercrossmod rom

[email protected] said:
Will the camera fix work with evercrossmod rom
Click to expand...
Click to collapse
No. That fix is for CM/CM based roms only. For stock based ROMs you just need replace camera libs.

Jitheshwar said:
No. That fix is for CM/CM based roms only. For stock based ROMs you just need replace camera libs.
Click to expand...
Click to collapse
This did not worked...the camera icon is showing but it says app not installed.I replaced the previous hw files (camera.sc8830.so and the camera2.sc8830.so). Now the app is opening but can't connect to camera.

[email protected] said:
This did not worked...the camera icon is showing but it says app not installed.I replaced the previous hw files (camera.sc8830.so and the camera2.sc8830.so). Now the app is opening but can't connect to camera.
Click to expand...
Click to collapse
You have to replace files having name "libcamera****.so" too.

How to unpack and repack system.ext4.win ?

[email protected] said:
How to unpack and repack system.ext4.win ?
Click to expand...
Click to collapse
just rename the file to system.ext4.win.tar.gz
and open it like a norma zip file

[email protected] said:
How to unpack and repack system.ext4.win ?
Click to expand...
Click to collapse
rename extension with .tar and extract it as usual but while repacking make sure you're using .tar compression type only. But I recommend using Aroma FM since extracting and compressing system.ext4.win may result in incorrect file permissions, as it is compressed by recovery.

@ki said:
just rename the file to system.ext4.win.tar.gz
and open it like a norma zip file
Click to expand...
Click to collapse
no need of .tar.gz, .tar is sufficient. As it is backuped in recovery by disabling "Enable Compression option" means we'll see the system files after extracting the system.ext4.win and not the system.ext4.win (compressed system image).

Jitheshwar said:
no need of .tar.gz, .tar is sufficient. As it is backuped in recovery by disabling "Enable Compression option" means we'll see the system files after extracting the system.ext4.win and not the system.ext4.win (compressed system image).
Click to expand...
Click to collapse
Now which software extracts .tar file. Plz tell me a software for windows

Jitheshwar said:
no need of .tar.gz, .tar is sufficient. As it is backuped in recovery by disabling "Enable Compression option" means we'll see the system files after extracting the system.ext4.win and not the system.ext4.win (compressed system image).
Click to expand...
Click to collapse
Yup....i forgot to mention that......just thought why anyone wants to backup without compression......

[email protected] said:
Now which software extracts .tar file. Plz tell me a software for windows
Click to expand...
Click to collapse
A zip archiver like 7zip, Winzip, etc. Mist if these software will be available for free. If you are using mobile to port I recommend ZArchiver.

After i'm port cm12 rom to sc7731 my device, is say Android is starting.... After that is restart and do that again, what i'm do wrong?

RustyDiamond said:
After i'm port cm12 rom to sc7731 my device, is say Android is starting.... After that is restart and do that again, what i'm do wrong?
Click to expand...
Click to collapse
your kernel....

RustyDiamond said:
After i'm port cm12 rom to sc7731 my device, is say Android is starting.... After that is restart and do that again, what i'm do wrong?
Click to expand...
Click to collapse
You may not replaced necessary lib(s).
Wipe everything before flashing the ROM (it is suggested to wipe internal storage also).
Don't replace everything (like camera libs) because they might give issues that you are facing, first key the device boot then fix bugs. If possible take logs using adb.

[Guide] How to unpack/repack diffrent img files easily without pc.

Hey, today in this post I've discussed on the topic
"How to unpack/repack img without PC or android tools (android tool is a little complicated and sometimes doesn't works)."
So let's get started
First of all download & install 'android image studio'
1: open it and click on repack/unpack
2: select the port ROMs boot or recovery img.
3: we get two folders
a.) Split_img --->> contains kernal zimage.
b.) Ramdisk----> contains init.rc recovery. Fstab etc..
4: to delete any file long press on it and click delete
5: to import any file click on import button in right panel & select the file
6: after making desired changes. Repack the img using repack button
7: a file will be created with the name image-new.img
8: export this file using export button and select the desired location.
Congratulations you have just ported an img without PC easily.
Link for the tool: https://play.google.com/store/apps/details?id=com.redlee90.imagekitchenforandroid
Link to my video toitorial for better understanding on this:
If you liked it just PRESS the THANKS button

I need more help, trying to open a .IMG boot file for Samsung s5, it gives the "No Image Supplied" error

Screenshot

Using AIS. Trying to port custom recovery but first thing I've tried is to just unpack and repack stock recovery. When repacking output of AIS is new IMG and new ramdisk. New IMG is smaller than original but from what I've read this should be okay. Flashed new IMG and attempted reboot recovery and all I got was black screen. Flashed stock recovery and it booted recovery fine. Not sure what I'm doing wrong. I used AIS to open the new image it created and then kept doing file/folder comparisons on the output. I narrowed down the difference being recovery.img-ramdisk.cpio. But when I unpack with cpio the contents of the archive are the same. Additionally, I repacked the contents with cpio but it still comes up as not matching the original recovery.img-ramdisk.cpio. My device can and does make replacement recovery images using applypatch with bonus files and boot img. Any help greatly appreciated!

Need boot.img FRD-L09 B404

Hello everyone.
I unlocked a bootloader in my freshly bought Honor 8 last week and I the first thing I did was to flash a root package (obviously). I'm used to SuperSU, so tha's what I flashed. Then I found out about Magisk. I want to try it, but I need to flash stock boot.img in order to install it. My build number is FRD-L09C432B404 (EMUI 5.0, Android 7.0). Could anyone upload corresponding boot img? I'd be thankful.

Do it yourself! ^^
Wagierek said:
Hello everyone.
I unlocked a bootloader in my freshly bought Honor 8 last week and I the first thing I did was to flash a root package (obviously). I'm used to SuperSU, so tha's what I flashed. Then I found out about Magisk. I want to try it, but I need to flash stock boot.img in order to install it. My build number is FRD-L09C432B404 (EMUI 5.0, Android 7.0). Could anyone upload corresponding boot img? I'd be thankful.
Click to expand...
Click to collapse
Hello!
You can do it yourself, just follow these steps:
1) Download your firmware (update.zip) from hicloud url: update.zip
2) Extract zip
3) Download "Huawei Update Extractor 0.9.9.5" (zip file): HuaweiUpdateExtractor_0.9.9.5.zip
4) Extract zip
5) Open "HuaweiUpdateExtractor.exe" extracted from previous step
6) Click on the 2 dots button and navigate to the file to add the "UPDATE.APP" file ( extracted from step 2) ), it will show you all the files like boot.img , recovery.img , recovery2.img , system.img , etc.
7) Select "BOOT.img" and right-click > "Extract Selected". Choose this destination folder: Where fastboot/adb are installed.
8) Use fastboot command to flash "BOOT.img":
Code:
fastboot flash boot BOOT.img
Hope it helps you!

I'd rather not download 1.3GB of firmware for the sake of one small boot.img which can't be bigger than 50MBs, not to mention additional software I'll use probably never again, so I'd be thankful if someone sent already extracted boot

Wagierek said:
I'd rather not download 1.3GB of firmware for the sake of one small boot.img which can't be bigger than 50MBs, not to mention additional software I'll use probably never again, so I'd be thankful if someone sent already extracted boot
Click to expand...
Click to collapse
BOOT.img file from FRD-L09C432B404 firmware: Google Drive or MEGA
( Because I have nothing more important to do tonight lol )

Thanks for your support. I had to extract it anyways for stock recovery, so here it is in case someone needed it.
https://drive.google.com/file/d/1ILYXoUvKMSsb8uLmSY2pIMvFWeBJ--9X/view?usp=sharing