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.
Related
I have made a custom ROM, with additional API's and patches using stock ICS source - Downloaded from source.android.com.
After modifying, patching etc, I built the ROM using 'make' on my Ubuntu machine.
I followed the steps here to build the ROM: http://source.android.com/source/building.html
The output of this procedure is attached as a screenshot
(I copied the folder to windows hence the screenshot shows a windows OS)
Now I have a ROM I am asked to flash it using'fastboot flashall' per the instruction here:
http://source.android.com/source/building-devices.html
My device doesn't seem to support a Fastboot mode.
The output folder of the ROM is attached as a screenshot.
A> When I try to use CWM, it fails to flash - MD5 Mismatch:
Also I am unsure how CWM flashes and which of the folders are to be included. A CWM recovery generates:
1. boot.img
2. recovery.img
3. system.ext4.tar
4. data.ext4.tar
5. cache.ext4.tar
6. nandroid.md5
Clearly my output folder is not aligned to this format. So I'm a bit lost here.
B> Odin takes on tar file. I am not sure if simply making the folder a tar will work.
C> Heimdall doesnt support this tab I guess...
Any ideas on a solution would be appreciated.
Thanks & Regards
Indrajit
Downloaded & Installed a custom ROM zip, it worked. How can I make mine into a zip?
Most of the custom ROMs have a boot.img, system folder, data folder and meta-inf.
What is Meta-Inf?
Also If I zip my ROM (created as mentioned above) and try installing it doesnt since I dont have a Meta-Inf & I cant use the other meta-inf.
This is the ROM I installed: Worked fine except USB-PC connection didnt:
http://forum.xda-developers.com/showthread.php?t=1643736
Any ideas / suggestions would be highly useful & appreciated.
Thanks in advance.
{
"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"
}
Welcome
FazHDv3 is the Samsung S4 Based Custom Rom
This ROM is ported from SamHDv3 for Customizations and Smoothness of 701HD
Special Thanks to abhishek for his invaluable contribution.
FAZHD ROM Features
Same as http://forum.xda-developers.com/showthread.php?t=2201122
How To Flash :
( You Can Take CMW Backup for Revert back to your old system )
Flashing procedure is different Don't Skip
1) Download Fazhd rom and bin files
Extract them both.copy allfiles in bin files to rom's system/bin
copy updater-script and replace with updater-script in here .META-INF/com/google/android/here
make a zip of rom
2) Put into External SD Card
3) Go To CMW Recovery
4) Wipe Data/Factory Reset And Wipe Partition
5) From Advance Menu Do Dalvik Catch Clear
6) Go in Mount And Storage select FORMAT SYSTEM
7) Select Intall From SD and Select File And Click YES
8) Select FazHDV3.zip And Select YES
9) Reboot Your System
10) Enjoy
Downloads
Rom http://d-h.st/NVu
bin files http://d-h.st/BBf
updater-script http://www.mediafire.com/?mv7fksxvttm4c41
Hi Buddy, Can you port the Ultimate 2.1 Rom by Back37 of Xolo Q800/GiONEE GN708W to Lava IRIS 504Q??
It's SUPER AWESOME ROM!! GIONEE FIRMWARE ROCKS!
Here's the link.
https://disk.yandex.com/public/?hash=MliKIOx5Mpen0T9iZd1uQmMX6bJee7QjjfPLQtVMXoU=
Thanks lot!
NHS2008 said:
Hi Buddy, Can you port the Ultimate 2.1 Rom by Back37 of Xolo Q800/GiONEE GN708W to Lava IRIS 504Q??
It's SUPER AWESOME ROM!! GIONEE FIRMWARE ROCKS!
Here's the link.
https://disk.yandex.com/public/?hash=MliKIOx5Mpen0T9iZd1uQmMX6bJee7QjjfPLQtVMXoU=
Thanks lot!
Click to expand...
Click to collapse
I ported lewa os to lava iris 504q..
Will upload soon
Sent from my iris504Q using xda premium
Thanks I would be very greatful if you could port that rom. Its too goood
Thanks a Lot.... can you try to port Canva4HD from same dev...
fandroid7 said:
Welcome
FazHDv3 is the Samsung S4 Based Custom Rom
This ROM is ported from SamHDv3 for Customizations and Smoothness of 701HD
Special Thanks to abhishek for his invaluable contribution.
FAZHD ROM Features
Same as http://forum.xda-developers.com/showthread.php?t=2201122
How To Flash :
( You Can Take CMW Backup for Revert back to your old system )
Flashing procedure is different Don't Skip
1) Download Fazhd rom and bin files
Extract them both.copy allfiles in bin files to rom's system/bin
copy updater-script and replace with updater-script in here .META-INF/com/google/android/here
make a zip of rom
2) Put into External SD Card
3) Go To CMW Recovery
4) Wipe Data/Factory Reset And Wipe Partition
5) From Advance Menu Do Dalvik Catch Clear
6) Go in Mount And Storage select FORMAT SYSTEM
7) Select Intall From SD and Select File And Click YES
8) Select FazHDV3.zip And Select YES
9) Reboot Your System
10) Enjoy
Downloads
Rom http://d-h.st/NVu
bin files http://d-h.st/BBf
updater-script http://www.mediafire.com/?mv7fksxvttm4c41
Click to expand...
Click to collapse
Thanks a Lot.... can you try to port Canva4HD from same dev... great abhishek.....
and can it be possible if you put bin files... in the same.. .zip.. and do we need to sign the zip after copy - paste of bin files and updater script...
port MTK6589 roms easy
defy403 said:
Thanks a Lot.... can you try to port Canva4HD from same dev... great abhishek.....
and can it be possible if you put bin files... in the same.. .zip.. and do we need to sign the zip after copy - paste of bin files and updater script...
Click to expand...
Click to collapse
Download MTK firmware adaptor forum.china-iphone.ru/post862552.html
you should install adb and root access to phone and your stock boot.img
1. download Rom you need to port
2. open mtk firware Adaptor
3. select profile as mtk6589
4.get files from your phone.
5. make your system files as system.zip (will get from backup of your rom)
get files from your system.zip
the tool will look like not responding but its copying rom files
6. get files from port rom
7. tick automated boot.img and make modded boot.img from stock boot.img
8. make adapted rom (port rom for your device)
it will automatically sign your rom
you can edit build.prop before creating rom
copy to phone and flash via cwm
updater-script will be automatically created.
test the rom and tell me if you have any problem like
dark camera. audio not wotking
will tell you how to fix it
stuck on boot loop....
fandroid7 said:
Download MTK firmware adaptor forum.china-iphone.ru/post862552.html
you should install adb and root access to phone and your stock boot.img
1. download Rom you need to port
2. open mtk firware Adaptor
3. select profile as mtk6589
4.get files from your phone.
5. make your system files as system.zip (will get from backup of your rom)
get files from your system.zip
the tool will look like not responding but its copying rom files
6. get files from port rom
7. tick automated boot.img and make modded boot.img from stock boot.img
8. make adapted rom (port rom for your device)
it will automatically sign your rom
you can edit build.prop before creating rom
copy to phone and flash via cwm
updater-script will be automatically created.
test the rom and tell me if you have any problem like
dark camera. audio not wotking
will tell you how to fix it
Click to expand...
Click to collapse
stuck on boot loop.... what to do now......!!!
defy403 said:
stuck on boot loop.... what to do now......!!!
Click to expand...
Click to collapse
its becouse of boot.img
just tap modifying boot.img button two or more times after selecting boot.img
its because of bad repacking of boot.img
if you use android kitchen
then make portrom.zip working folder and replace your stock boot.img
unpack boot.img by going to advanced and unpack repack boot.img unpack pressing w
rename boot extracted to stock boot
change boot.img with port roms boot.img
unpack port boot.img
copy zimage or zboot (i forgot real name) zxxxxxxx from stock boot to boot exracted
repack boot.img and make zip using 7zip of new boot.img+meta+system and flash rom it will boot
need help badly....
fandroid7 said:
its becouse of boot.img
just tap modifying boot.img button two or more times after selecting boot.img
its because of bad repacking of boot.img
if you use android kitchen
then make portrom.zip working folder and replace your stock boot.img
unpack boot.img by going to advanced and unpack repack boot.img unpack pressing w
rename boot extracted to stock boot
change boot.img with port roms boot.img
unpack port boot.img
copy zimage or zboot (i forgot real name) zxxxxxxx from stock boot to boot exracted
repack boot.img and make zip using 7zip of new boot.img+meta+system and flash rom it will boot
Click to expand...
Click to collapse
hi sir,
how to boot into recovery... i am getting 8038 in sp flash tool... have cwm backup...... device is not detected on mtk... and getting 8038 error in sp flash tool... what to do... plz plz help...
defy403 said:
hi sir,
how to boot into recovery... i am getting 8038 in sp flash tool... have cwm backup...... device is not detected on mtk... and getting 8038 error in sp flash tool... what to do... plz plz help...
Click to expand...
Click to collapse
are you using cwm
download mobile uncle tools for mediatech and select reboot to recovery
resolved... phone is back to life....
defy403 said:
hi sir,
how to boot into recovery... i am getting 8038 in sp flash tool... have cwm backup...... device is not detected on mtk... and getting 8038 error in sp flash tool... what to do... plz plz help...
Click to expand...
Click to collapse
done... phone back to life... selected... firmware upgrade and did... flash factory rom backup.... and it's again alive...
with CWM & SU along with mobile uncle....
i think from next time... whenever i will try to do experiments.... will... make sure... i have backup ready..
so doing a new backup with CWM and SU... right away... also doing IMEI restore as it went to null.....
---------- Post added at 08:03 AM ---------- Previous post was at 07:54 AM ----------
fandroid7 said:
are you using cwm
download mobile uncle tools for mediatech and select reboot to recovery
Click to expand...
Click to collapse
HI....
i was stuck on boot loop... so not getting into recovery... even mtk was not detecting my phone... so i flashed... factory rom.. backup.. via firmware upgrade in sp flash tool... 3.13.... and did a factory reset and i am back in business,,,, still thanks for help...
you are from India... i am from mumbai.... can i just replace.... boot.img in custom rom with my phone's boot.img.... and do same for LK.bin... i.e. uboot.img... will that work....
---------- Post added at 09:01 AM ---------- Previous post was at 08:03 AM ----------
defy403 said:
done... phone back to life... selected... firmware upgrade and did... flash factory rom backup.... and it's again alive...
with CWM & SU along with mobile uncle....
i think from next time... whenever i will try to do experiments.... will... make sure... i have backup ready..
so doing a new backup with CWM and SU... right away... also doing IMEI restore as it went to null.....
---------- Post added at 08:03 AM ---------- Previous post was at 07:54 AM ----------
HI....
i was stuck on boot loop... so not getting into recovery... even mtk was not detecting my phone... so i flashed... factory rom.. backup.. via firmware upgrade in sp flash tool... 3.13.... and did a factory reset and i am back in business,,,, still thanks for help...
you are from India... i am from mumbai.... can i just replace.... boot.img in custom rom with my phone's boot.img.... and do same for LK.bin... i.e. uboot.img... will that work....
Click to expand...
Click to collapse
hi all...
http://forum.xda-developers.com/show....php?t=2012770
http://forum.xda-developers.com/show....php?t=1574401
check this thread...
this even works with our Zen 701HD... so install and enjoy.... new freedom... and.. no custom rom.. needed....
Replaced boot.img and it worked
fandroid7 said:
Download MTK firmware adaptor forum.china-iphone.ru/post862552.html
you should install adb and root access to phone and your stock boot.img
1. download Rom you need to port
2. open mtk firware Adaptor
3. select profile as mtk6589
4.get files from your phone.
5. make your system files as system.zip (will get from backup of your rom)
get files from your system.zip
the tool will look like not responding but its copying rom files
6. get files from port rom
7. tick automated boot.img and make modded boot.img from stock boot.img
8. make adapted rom (port rom for your device)
it will automatically sign your rom
you can edit build.prop before creating rom
copy to phone and flash via cwm
updater-script will be automatically created.
test the rom and tell me if you have any problem like
dark camera. audio not wotking
will tell you how to fix it
Click to expand...
Click to collapse
Replaced boot.img and it worked... bootup perfectly first time... all things working correctly... but now not booting up again... after i tried to restart...
troubleshooting done.... only needed to replace build.prop... and it works great.... even blow to unlock works...
only camera is dark... as told by you.. please tell me how to fix....
defy403 said:
Replaced boot.img and it worked... bootup perfectly first time... all things working correctly... but now not booting up again... after i tried to restart...
Click to expand...
Click to collapse
Hi can you share the files I need to flash from S.P. Tools to make my Irsi 504q back working?
I only have CWM backup. I've bircked it while trying a ported rom from Q800...THANKS!
please help me with camera
fandroid7 said:
Download MTK firmware adaptor forum.china-iphone.ru/post862552.html
you should install adb and root access to phone and your stock boot.img
1. download Rom you need to port
2. open mtk firware Adaptor
3. select profile as mtk6589
4.get files from your phone.
5. make your system files as system.zip (will get from backup of your rom)
get files from your system.zip
the tool will look like not responding but its copying rom files
6. get files from port rom
7. tick automated boot.img and make modded boot.img from stock boot.img
8. make adapted rom (port rom for your device)
it will automatically sign your rom
you can edit build.prop before creating rom
copy to phone and flash via cwm
updater-script will be automatically created.
test the rom and tell me if you have any problem like
dark camera. audio not wotking
will tell you how to fix it
Click to expand...
Click to collapse
only camera is dark... as told by you.. please tell me how to fix....
defy403 said:
only camera is dark... as told by you.. please tell me how to fix....
Click to expand...
Click to collapse
to fix camera.
I assume you use dsixda's kitchen.
Set up working folder for stock rom
Go to advanced > tools for boot.img
> unpack boot.img
Navigate to the folder called Boot-extracted.
> rename it to something else (for now: stock boot)
Set up working folder for port rom.
Go to advanced > unpack boot.img
Do a google search for 'winmerge' > install program (free).
Open winmerge, for left navigate to the 'stock boot' folder, and select init.rc (about 40kb)
For right, navigate to the port 'boot-extracted', and select init.rc (about 40kb)
In winmerge find lines like this
Chmod camera blablabla (on the left pane you will see where there are differences)
Chown camera blablabla
If there are differences in those lines, copy the stock lines, and overwrite the port ones
Save the files (crtl+s)
Navigate to boot extracted folder, you can close winmerge. Copy stock Zimage (from 'stock boot' folder) to port, and overwrite the Zimage there with stock one.
Go back to kitchen, > advanced > tools for boot.img > build new boot image.
Unable to open your site for downloading ROM, could you reupload please.
Looking for more ROMS.
Hi again fan droid.... It would help if you can fix the issues and upload the completed ROM....
I faced the same camera issue when I ported naturewiz HD..... Will you help fix that too?
Sent from my ultrafone 701HD
bro post the ROM, so that we could test it.
use MTK root tools
NHS2008 said:
Hi can you share the files I need to flash from S.P. Tools to make my Irsi 504q back working?
I only have CWM backup. I've bircked it while trying a ported rom from Q800...THANKS!
Click to expand...
Click to collapse
use MTK Root tools ...
1. recovery..backup tab
2. select prepare blocks for flash tool
3. select .md5 file from your CWM backup
4. it will checksum... and prepare files which can be flashed via... SP Flash Tool...
5. make sure you select... firmware upgrade... while flash...
* please note... you will need sp flash tool v3.13 & also.... all the files.... i.e. from preloader to cache.. and even userdata... nvram...tar...
please hit thanks if i help
post the ROM bro, so that we could test it. waiting for a long time.
Credits - Manish Singh ([email protected])
Simplified and detailed by me (Arun Sharma)
{
"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"
}
Base Rom - CM12.1
Port Rom - Any Rom from here
First of all Comes Extracting the system.new.dat file :laugh:
Here's how to do it:-
1) Download sdat2img tool from here
(Source - thanks to @xpirt)
2) copy it to your port rom folder
3) Shift+Right click and choose Open Command window here
4) enter the command
sdat2img system.transfer.list system.new.dat system.img
hit enter.
It'll show reading blocks, will take around 20 seconds and you'll see a System.img file, newly created
5) You can now extract that with ext4unpacker to get the system folder
just choose the image, select contents and extract anywhere you want.
Now, let's Port!
1) Open Lib folder in port rom &
Copy EGL folder,
Libandroidfw, libandroid_servers, libandroid_runtime.so
libskia, libinput ,libsurfaceflinger, libjavacore, libcamera files (except libcameracustom)
files to a new folder, name it lib
Open Bin folder, copy the file named input to a new folder, name it bin
2) Copy all Libs, Bins from cm12.1 to port Rom (leave existing ones in port rom)
after its done, copy back the files that we copied in step 1 in that lib, bin folder to port rom (original ones from port)
3) Copy vendor folder from CM12.1 to port rom
4) Copy Firmware folder from CM12.1/etc to port rom
you may also copy the lib/ hw folder from cm12.1 to port rom (if you face any issues with sensors)
5) Use boot.img of cm12.1 Or pacman or AICP
Or Make one Yourself
Making boot.img for cm12.1 based roms :-
1) Extract port and stock boot.img files using Android Kitchen
2) Copy zImage file of stock boot.img to port boot.img
3) Repack the port boot folder and use that boot.img
in case it doesn't work, copy the uevented.rc file from stock boot/ramdisk folder to port boot/ramdisk (along with zimage)
and pack it!
Done.. add this boot.img to your port rom folder)
:laugh:
------------------------------------------------------------------------------------
Now, your rom will work, however, you may see that none of the storages are mounted!
So, here's how to fix that
1) Copy the Framework-res.apk from any of the CM12.1 based roms for your device or the stock rom
2) Decompile it (TickleMyAndroid tool can be used for that)
3) open the working folder, go to res/xml folder and copy Storage-list.xml file
4) Now decompile the port rom's Framework-res.apk also, in separate folder
and paste that copied storage-list.xml file into it's res/xml folder
5) Compile it and copy back to port/framework folder.
Storage will be fixed now
6) You may wanna add some changes to build.prop also (if you want)
7) Use the meta-inf of any existing CM12.1 or CM12 rom for your device also!
8) Now, zip the rom and Copy the rom to anywhere in SDCard or internal storage
Flash from recovery!
Happy Porting :laugh:
Thanks
arun6106 said:
Credits - Manish Singh ([email protected])
Simplified and detailed by me (Arun Sharma)
Base Rom - CM12.1
Port Rom - Any Rom from here
First of all Comes Extracting the system.new.dat file :laugh:
Here's how to do it:-
1) Download sdat2img tool from here
(Source - thanks to @xpirt)
2) copy it to your port rom folder
3) Shift+Right click and choose Open Command window here
4) enter the command
sdat2img system.transfer.list system.new.dat system.img
hit enter.
It'll show reading blocks, will take around 20 seconds and you'll see a System.img file, newly created
5) You can now extract that with ext4unpacker to get the system folder
just choose the image, select contents and extract anywhere you want.
Now, let's Port!
1) Open Lib folder in port rom &
Copy EGL folder,
Libandroidfw, libandroid_servers, libandroid_runtime.so
libskia, libinput ,libsurfaceflinger, libjavacore, libcamera files (except libcameracustom)
files to a new folder, name it lib
Open Bin folder, copy the file named input to a new folder, name it bin
2) Copy all Libs, Bins from cm12.1 to port Rom (leave existing ones in port rom)
after its done, copy back the files that we copied in step 1 in that lib, bin folder to port rom (original ones from port)
3) Copy vendor folder from CM12.1 to port rom
4) Copy Firmware folder from CM12.1/etc to port rom
you may also copy the lib/ hw folder from cm12.1 to port rom (if you face any issues with sensors)
5) Use boot.img of cm12.1 Or pacman or AICP
Or Make one Yourself
Making boot.img for cm12.1 based roms :-
1) Extract port and stock boot.img files using Android Kitchen
2) Copy zImage file of stock boot.img to port boot.img
3) Repack the port boot folder and use that boot.img
in case it doesn't work, copy the uevented.rc file from stock boot/ramdisk folder to port boot/ramdisk (along with zimage)
and pack it!
Done.. add this boot.img to your port rom folder)
:laugh:
------------------------------------------------------------------------------------
Now, your rom will work, however, you may see that none of the storages are mounted!
So, here's how to fix that
1) Copy the Framework-res.apk from any of the CM12.1 based roms for your device or the stock rom
2) Decompile it (TickleMyAndroid tool can be used for that)
3) open the working folder, go to res/xml folder and copy Storage-list.xml file
4) Now decompile the port rom's Framework-res.apk also, in separate folder
and paste that copied storage-list.xml file into it's res/xml folder
5) Compile it and copy back to port/framework folder.
Storage will be fixed now
6) You may wanna add some changes to build.prop also (if you want)
7) Use the meta-inf of any existing CM12.1 or CM12 rom for your device also!
8) Now, zip the rom and Copy the rom to anywhere in SDCard or internal storage
Flash from recovery!
Happy Porting :laugh:
Click to expand...
Click to collapse
Thanks bro but this porting tut not working on Mokee LP rom......
but works for other roms......
Not Working
Getting error while enter code in CMD:crying::crying:
ZeroVirus said:
Getting error while enter code in CMD:crying::crying:
Click to expand...
Click to collapse
make sure you downloaded the correct tool
should be 5.4 mb in size
then, verify that both input files exist there:-
system.new.dat
system.transfer.list
You may want to, re-write all the OP.
otherwise, this will be closed.
...
And who built CyanogenMod 11/12/12.1 for "regular" MT6582 / 92 devices?
The most important persons you failed to mention...
You know, the ones who actually built it?
--> The 6582/92 development group.
yeah its 5.4 mb and all files are there
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
i dont have this two file
system.new.dat
system.transfer.list
after extracting how can i compile back to system.new.dat?
hello need a help............ i have booted a rom ... but when i installed apps and trying to open its fortunately stopped... can you help.. mt6592
Even marshmallow ROMs?
Cam lib files means which can u post it please
Does it work on cm13?
HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE
Most of us have always wanted to use custom roms but there just no custom roms for our devices so we just use different app launchers and uninstall some bloatware to make our stock rom feel good.
Rom porting makes it possible to use a custom rom on your mtk device provided in this tutorial they have the same chipset (example: mtk 6582 ported to mtk6582).
THINGS NEEDED :
1. B1 archiver / ES FILE EXPLORER
2. Root Browser.
4. A rooted device is also needed but not much important if you have CWM INSTALLED WITHOUT ROOT.
PROCEDURE :
1. Make a backup of your current rom, preferably CWM backup. You can either use MTK DROID TOOLS or ROM MANAGER...
The location of the backup will be at clockwork/backup/"date and time of the backup ". This is very important since we will need stuff from the back up and we will also use the backup to recover the phone should the ported rom give any problems.
2. At this point I presume you have already downloaded the apps needed and the custom rom you want to use which is in a zip format( this was not important but I had to bring it up cause I know zombies could be reading this.
3. Now extract the custom Rom with Root Browser. if you extracted with Root Browser then the location will be "speedsoftware/extracted/"folder with the name of the custom rom "".
4. Now open Root Browser and open the folders side by side "custom rom which will be ported at one side and other side will be used for searching for the location of the things needed for the custom rom.
5. Delete the following from the Custom rom:
Boot.img
logo.bin (You do this only when you like the Your current logo.bin)
system/vendor
system/usr
system/lib/hw
system/lib/modules
system/lib/libncurses.so
system/etc/firmware
system/etc/vold.fstab
system/etc/vold.fstab.nand
system/etc/bluetooth
6. Now that you have deleted them from the custom rom replace them. You will find the boot.img at clockworkmod/back/"folder with date and time"/boot.img. The rest of the files and folders will br located in the Root /system. Just copy and paste
7. Now at the custom Rom panel go back to where you find the "META-INF" folder,open /google/android will now long press on "updater script" and tap on open with then select text editor.
8. Check The mount & format point check something like this mmcblk0p. A number is always written after the "P" replace the number of your BASE to PORT.
9. Check multi select in B1 archiver Select ( do not archive the folder the files are in but the individual files in the folder containing the extracts)
10. Compress to ZIP file wait till the process finished. Now boot to recovery and flash your ROM
Good luck in porting Your Rom... I have used this method to port 5 roms including AROMA ROMS. and I have never ported a Rom with a pc before
MAYBE U NEED TO EXTRACT THE BOOT IMG TOO IF THIS DIDNT WORKED
DO IT AS FOLLOWS
Requirements:
-- BusyBox (cpio, gunzip and gzip is mandatory)
-- /System Write Permissions (Does not need to be a modified kernel)
-- Terminal Emulator
-- ES File Explorer (or similar)
-- Hex Editor (or use of DD)
-- Open up your android terminal emulator.
-- Now go ahead and pull your boot.img from your device (or use another one if you wish)
-- Open up your boot.img with the Hex Editor and look for: ANDROID!. Remove everything before it so that the ANDROID! header is the first to be read then save it over top of the boot.img. NOTE: This is only required if you are using a stock boot.img.
OR USE THIS IF U DIDNT UNDERSTOOD THIS
Hello Everyone, I’ll show you how to Unpack and Repack your Phone’s Boot.img & Tweak Karnel. Lets start.
Make a new folder named “boot edit” in cache/
image
Pull your boot.img in this folder
image
Now open ApkTool. Long press on “cache“, click on Get Access Permission.
image
Open cache folder and do same with boot edit. Give ApkTool access permission
image
Open boot edit, click on boot.img select Expack(MT65xx), press ok
image
It will unpack your boot.img.
image
Now open file manager & go to cache/boot edit/. You wil find your unpacked boot.
image
Now edit/modify the files or tweak karnel.
Again open ApkTool. Goto cache/boot edit click on ramdisk select repack-mt65xx.
image
It will repack your boot.
image
You will find an img file named new.img
image
This file is your Tweaked/edited/custom boot.img!!
Flash it via Recovery or Flashify & Enjoy..
FOR DETAILED AND STEP WISE GUIDE WITH SCREEN SHOTS SEE HERE
Mod Edit: link removed
XDA:DevDB Information
HOW TO PORT ROMS TO YOUR MTK WITH ANDROID DEVICE, ROM for all devices (see above for details)
Contributors
manhar2108, manhar2108, 2108kick
Source Code: Mod Edit: link removed
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: all
Version Information
Status: Stable
Created 2015-08-16
Last Updated 2015-08-16
HIT THANKS IF I HELPED U
Good guide..
Especially for noobs....
Darshan601 said:
Good guide..
Especially for noobs....
Click to expand...
Click to collapse
i too am a noob so i tried and made this guide
how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel
manhar2108 said:
i too am a noob so i tried and made this guide
Click to expand...
Click to collapse
Yeah....Even I am a noob
gunzgunz said:
how bout porting 5.1 rom to 4.4.2 stock?
what should I consider?
aside from tweaking kernel
Click to expand...
Click to collapse
just replace all these files and use stock kernal to port them
good luck
Sir i tried your guide in porting rom. Mt6582 tp mt6582 chipset roms.. But after replacing those files you mentioned and when i flashed it to my phone, it was tuck in boot screen and keep on restarting. How am I going to fix this?
Thread closed. Pay per click links are not allowed on XDA.
Darth
Forum Moderator
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.