Database Info

confused between adb,mtkdroid tool, flashtool?

lenovo A319
i am still in the research phase before rooting so,
Now i figured out three ways to install a custom room
1- adb: unlock boatloader ,flash custom recovery , and using it to install a custom rom .zip file
i like this method , neat easy , i understand it and i have needed files
2-mtkdroid tool:
it needs files have extension which is in existed inside the custom rom .zip file, and also want md5 file which is not compatible with my lenovo anyways
3-flash tool: same thing need files i have no idea about, and doesnt exist in the custom rom .zip file
i made a scatter file from my stock phone using mtkdroid -which i have no idea what is that file-
are mtkdroid and flashtool used together???and if so then why all the headache while using the adb solve the whole thing in couple of lines?

[Lenovo][Tab3] ROM Readback

Hi - I managed to follow tutorials (using SP Flash Tool and MTK droid tool) posted in this forums to readback Lenovo Tab3 710F, and managed to flash the ROM to other devices.
I have one issue thought, that /data/ folder is not copied along with the ROM, mainly the apps and their settings under /data/data.
My question : Which file when reading back ROM includes the /data/ information ? does the readback even pull that folder ?

A newer version of SP Flash tool for Linux

I want to root some phones that have a MTK MT6755 SoC, and first I want to do some full backup of their flash. In order to do so, I have to use SP Flash Tool.
The latest version of SP Flash Tool is 5.1524.00, at least for windows users. I'm working on linux all the time, and I don't really operate on windows. The version of SP Flash Tool for linux seems to be a little bit outdated because it's 5.1520.00.
This version was fine for my older phones, but for the new ones only the 5.1524.00 seems to accept my scatter.txt file and the problem is in the newer SoC.
Does anyone know whether (and when) a newer version of SP Flash Tool will be released for linux? Maybe is there a way to do some stuff to make the older version of SP Flash Tool work with the MT6755 SoC on linux?

morfikov said:
Does anyone know whether (and when) a newer version of SP Flash Tool will be released for linux? Maybe is there a way to do some stuff to make the older version of SP Flash Tool work with the MT6755 SoC on linux?
Click to expand...
Click to collapse
SPFT Linux, I use v5.1712 for the MT6737T. Readback all your partitions for backups.
How to setup on linux.

So is this website outdated?
https://spflashtool.com/
I downloaded the newest version from the link you've provided, but it seems that SP Flash Tool needs to be updated:
Code:
SP_Flash_Tool_v5.1728_Linux/flash_tool: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
And I have this lib installed:
Code:
# dpkg -l | grep libpng
ii libpng16-16:amd64 1.6.32-3 amd64 PNG library - runtime (version 1.6)
I had to install the lib from here: https://packages.debian.org/jessie/libpng12-0 , but it seems to work well, and also it loads my scatter file without a problem.

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

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 and please read the entire OP.
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]
All suggestions and helps are welcome here so please help me in improving this thread by suggesting your ideas.
This guide will work for any SPRD phone (any SPRD chip) from Old versions of android to latest Oreo but recoveries that I provided in this thread will work for devices from KitKat to Marshmallow no guarantees for older or newer versions.
Buckup! Backup! Backup!​
Before modifying system it's highly recommended to have full dump of your device. So don't forget to take backup.
It's simple to get custom recovery for rooted users as they can directly backup, modify and flash recovery or boot images on the go with the help of root. But non-rooted users need to do some extra which will be explained later. Follow the below steps:
=>Download and setup AIK (Android Image Kitchen)
=>Grab your stock_recovery.img
For rooted users​Install Flashify, Rashr, Partitions Backup or like apps (available on play store for free) and backup the stock recovery. If you are using Flashify to backup you have to rename the backed up image with .img extention
For non-rooted users​Download your stock firmware which will be in .pac extension extract it using this guide and copy the recovery.img
=>Now download custom recovery (for downloads see 2nd post)
=>Port recovery
For PC version of AIK​
• Extract the AIK on desktop in a folder (extracting inside other folder(s) is not recommended)
• Place stock_recovery.img (use the name recovery.img only I added stock to refer the image) in earlier extracted folder
• Now double click on 'unpacking.bat'
• Now you'll see two folders 'ramdisk (mostly executables)' and 'split-img (kernel to boot recovery) rename those folders like this 'ramdisk.s' and 'split_img.s' (renaming is used to avoid copying/moving needed files)
• Now delete the earlier pasted stock_recovery.img and paste custom_recovery.img (rename it to recovery.img)
• Unpack it just like stock_recovery
• Delete the split-img and rename the 'split_img.s' to split_img
• Open recovery.fstab from /ramdisk.s/etc (stock recovery's fstab) and /ramdisk/etc (custom recovery's fstab) using Notepad++ or with your favorite note editor. In case of TWRP recovery this file will be named as twrp.fstab if there is recovery. fstab you can ignore it.
• Edit the partition names and mount points in custom recovery with your stock recovery's fstab. But in most cases the mount points will be shown like this 'mmclbk0p17 for system partition' in that case you need to change custom recovery.fstab with the mount points of your device, to find out mount points of partitions install Diskinfo from play store and enable all options in it which will show complete information regarding each and every partition on your device
• At last double click on 'repackimg.bat' now you'll see 'image-new.img' which is ported custom_recovery.img for your device
• The final step is flashing the recovery. It's easy for rooted users simply use Flashify app to flash. For non-Root users you need to flash it over fastboot mode for this look at this thread.
For mobile version of AIK​
You can also port the recovery on-the-go using AIK-Mobile unfortunately to use this needs your device must be rooted with BusyBox (Stephen (stericson) is recommended) installed.
It's a flashable zip but you can extract the zip and place the files manually. Follow below steps for setup:
• Extract the AIK-Mobile.zip
• Paste the AIK-Mobile folder under data/local of extracted zip to /data/local
• Paste files under /bin of extracted zip to /data/local/AIK-Mobile/bin
• Make sure all files including folders are having these permissions "-rwrx-xr-x-".
For placing files, changing permissions and executing scripts 'Explorer' by speed software is recommended.
For porting follow above steps (steps in PC version of AIK) the only difference here is .bat files of PC version will be as .sh in mobile version which are to be executed as root for unpacking and repackaging images.
Note:Follow the instructions properly, don't quote entire OP while asking for help. Due to some touch related drivers missing in kernel of recovery in some devices touch recovery won't work in that case please use Non-Touch recovery. In lollipop or later versions don't flash <3.x.x versions which may result in SD card mounting issues and even flashing errors. First test the recovery that you ported by flash a simple mode (I prefer AIK-Mobile since it doesn't modify the system partition hence there is not chance of bootloop. Also see whether wipe options works properly or not in some devices wiping (even cache) takes ~10m in that case goto settings check the option "use rm -rf instead of formatting".
Hit thanks button instead of posting thanks it'll boost me to create more threads like this.
Credits:
Advan S4P [Official] (fb group), SuDroid Tech (fb group), @@ki , @Jitheshwar (it's me), and some aliens from other universe.​
Created: 27-09-2017
Last Updated: 27-09-2017

Custom recovery downloads
1) TWRP recovery images
2.7.0-0
2.8.5-0
2.8.5-0
3.0.0-0
3.0.2-0
3.0.2-0
3.0.2-0
3.1.1-0
2)Cyanogen recovery (for lollipop)
3)Cyanogen recovery (for kikat)
4)MIUI recovery
5)Ultra CWM
6)Temporary CWM (only for KitKat and older
7)Temporary Philz (only for KitKat and older)
Temporary recoveries provided here are not for porting. You can flash those zips directly from you stock recovery these recoveries will have basic functions like flashing ROMs, Wiping (in some devices it'll take too long to wipe so just use factory reset option of stock recovery and then flash this recovery finally the ROM. Back up option of recovery might not be fully functional. Scrolling is glitchy but it'll work when you press button. These are more for users who are unable get working recovery

Reserved for FAQ.

Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp

Jitheshwar said:
Click to expand...
Click to collapse
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??

Jitheshwar said:
..
Click to expand...
Click to collapse
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?

HemanthJabalpuri said:
Sir...
you wrote that delete only split_img.s.....
but not ramdisk.s.......
Is there any problem will arise when repacking with ramdisk.s with ramdisk and split_img of custom recovery?
Click to expand...
Click to collapse
Read again carefully you have to pack custom recoveries ramdisk with stock split_img and reversing the process will mess up the recovery and then you have to flash the stock recovery. So read the guide carefully step-by-step and follow the process exactly unless you know different working method.

unknown said:
I have fpt x50 , vn phone , which runs android 7.0 with sc7731c
Will this guide work ??
Click to expand...
Click to collapse
Give it a try it may work. But none of the recoveries that are provided here will work for your device, you need to find Android 7.0 and later recoveries which will be compatible with your chipset model.

kaew158 said:
Do you know how to port boot to help twrp recovery mode boot up ? Please guide me.
Boot Secure & twrp
Click to expand...
Click to collapse
TWRP has nothing to do with boot.img. If you are not able to boot to recovery try different key combination. Is you messed up recovery too then flash it via fastboot and then flash the stock Rom.

Jitheshwar said:
Click to expand...
Click to collapse
Sir finally the process is to pack
⇛split_img of stock recovery ......
⇛ramdisk of custom recovery you listed by replacing recovery.fstab file
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....

HemanthJabalpuri said:
Sir finally the process is to pack
⇛ramdisk of recovery you listed by replacing recovery.fstab file
⇛spit_img of stock recovery right......
Some doubt are ... from where the recoveries are taken sir?
another one is can i port a custom recovery made for similar device to my device by using these steps?
Thanks for supporting spreadtrum devices....
Click to expand...
Click to collapse
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.

Jitheshwar said:
Kindly go through the entire post carefully, I believe I provided sufficient info that even a newbie can port.
Click to expand...
Click to collapse
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore

HemanthJabalpuri said:
Sir I read entire post...
But there is no line that states to delete ramdisk of stock recovery....
Check and add that line sir....
Also process of installing AIK for Mobile changed...
We directly install and use the AIK as all other apps on playstore
Click to expand...
Click to collapse
I clearly stated all the steps in an easy and simple way. My kind request to you to read the post again. And one more thing if you want to use apk version use it I don't have any issues but don't ask me if anything goes wrong.

i ported twrp 3.2.1 to sc8830 sucessfully but touch is not working , can you help?
where can i find non-touch recovery
I'm using android 5.1

What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.

denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones

Please fix the twrp links!!!

@Vortex said:
This is just some copy&paste guide thath will not work on most bootloader locked spreadtrum OEM phones
Click to expand...
Click to collapse
No custom recovery will work on bootloader locked devices...

denmasgie said:
What is specification kernel architecture in this tutorial?. I have HH Advan S50 same with the name of chipset version.I still doubt fo following your tutorial.
Click to expand...
Click to collapse
Kernel architecture is ARM.

Question Anyone know how to unbrick an OP9 on Linux? I do not use Windows

Hello all,
Yes, this is another request to unbrick an OP9 from a Lineage recovery installation, but I don't have, nor want to have Windows. Not certain if this question has been asked before but due to choices, I will not use Windows anywhere except QEMU. I run Artix Linux (a rolling release based on Arch, with OpenRC), and as some of you may know, Linux does not have native .exe support. I have tried WINE for use on MSM tool, no luck as I only have the factory option from the dropdown only. I've tried QEMU and Win7, Win10, and Win11 (granted they are all debloated versions to speed boot times). The only error I'm getting is during a USB passthrough error when loading EDL mode. The last thing I tried was a python script that unpacks payload.bin for setting up fastboot flashing in a specific order. It requires a recovery.img, but I don't have it making this method useless. I do not have a windows machine in the home nor do my neighbors. How can I stick with Linux and unbrick my OP9?
Thanks all,
Your fellow Linux enthusiast.

Hello,
If you need this recovery.img, did you try to extract it from payload. bin using payload dumper ?

sbute said:
Hello,
If you need this recovery.img, did you try to extract it from payload. bin using payload dumper ?
Click to expand...
Click to collapse
Yes I used the payload dumper script on the latest version of OOS for the OP9. There was no recovery, and I found a similar post stating it was built into the boot.img file. I still was unable to get recovery working afterward, but that method was good for Android 11 only.

Ok, I'm a linux user too, I endeed up installing a small partition of windows on dual boot just to run msm tool on OP9. But I know you don't want that. Did you try flashing partitions in fastboot ? There 's a thread about that in this forum .

sbute said:
Ok, I'm a linux user too, I endeed up installing a small partition of windows on dual boot just to run msm tool on OP9. But I know you don't want that. Did you try flashing partitions in fastboot ? There 's a thread about that in this forum .
Click to expand...
Click to collapse
I should take a look but that is what I tried, maybe I didn't flash the partitions correctly

Wich rom did you come from ? Can't you get the right recovery from their website ?

sbute said:
Wich rom did you come from ? Can't you get the right recovery from their website ?
Click to expand...
Click to collapse
you have to receive the image from oneplus themselves and it's the full image including recovery

Ah ok, you're on stock rom. Maybe wait for other user's advice

fl0wedm said:
Hello all,
Yes, this is another request to unbrick an OP9 from a Lineage recovery installation, but I don't have, nor want to have Windows. Not certain if this question has been asked before but due to choices, I will not use Windows anywhere except QEMU. I run Artix Linux (a rolling release based on Arch, with OpenRC), and as some of you may know, Linux does not have native .exe support. I have tried WINE for use on MSM tool, no luck as I only have the factory option from the dropdown only. I've tried QEMU and Win7, Win10, and Win11 (granted they are all debloated versions to speed boot times). The only error I'm getting is during a USB passthrough error when loading EDL mode. The last thing I tried was a python script that unpacks payload.bin for setting up fastboot flashing in a specific order. It requires a recovery.img, but I don't have it making this method useless. I do not have a windows machine in the home nor do my neighbors. How can I stick with Linux and unbrick my OP9?
Thanks all,
Your fellow Linux enthusiast.
Click to expand...
Click to collapse
What did you do to brick the phone? Did you just flash LineageOS recovery? What happens when you try to boot the phone? Can you access bootloader mode?

you don't need to install windows for that
you can use WinPE
Hiren's BootCD PE
or in Linux
you can use edl tool from github and manually flash firmware , its too hard and terrible but here you go
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
fl0wedm said:
my OP9
Click to expand...
Click to collapse