[X]Assistant

[jemmini]

пїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ download

Device or OS, firmware:all platforms

• To get started, it is strongly recommended to get acquainted withForum RulesandRules section "Android - Development and Programming"
  
• Before asking a question, lookAndroid OS FAQandGlossary. Respect your and other people's time.
  
• The administration of the resource and the authors of the manuals for the erroneous or incorrect actions of the owners with their deviceare not liable
  
• All operations with your phone,You do at your own risk.
  
• Sure tomake a full backup before any manipulations with the device!
  
• Before posting photos, read the topicWorking with Images on the forum
  
  
• The topic does not imply a discussion, messages that are not related to applications can be deleted without warning.

In this thread, you canleave and executeapplications for the creation of recovery for Android-devices on any hardware platform.
Perhaps you will help. However, you should understand that your application may not be completed ...

IMPORTANT!! You should clearly understand that the firmware of the device with third-party software most likely entails a loss of warranty, and may also lead to the exit of the device. All actions you take at your own peril and risk, responsibility for them entirely falls on you, no complaints are accepted.

IMPORTANT!! For devices with a locked bootloader (as a rule, some devices from the Meizu, Xiaomi, Huawei, etc., usually in the upper price category), third-party recovery cannot be made, applications will not be considered! Before applying for such devices, unlock the bootloader. For information on unlocking, look for the relevant topics on the devices.

ATTENTION!!For some devices, such as "Sony Xperia", the recovery is not provided by the developers of the original firmware. For some devices, the recovery may be provided in the device’s memory, but the entrance to it may be blocked. Thus, there are exceptions when recovery even if it can be created, but cannot be used. Consider this circumstance before applying for third-party recovery: you mustbe able to log in to the original recovery on your device ...

IMPORTANT!!Before submitting your application, you mustclearly understand how you will flash recovery.Questions about how firmware are covered in the relevant topics on the devices and are beyond the scope of this topic.

Also, please kindly familiarize yourself withthis, as well as withthisinformation.

IMPORTANT!!

Application form and necessary files

The application for recovery must provide:

1.The type of device (smartphone / tablet / clock / set-top box, etc.), the full name (revision) and year of the device, a link to the discussion topic onsavagemessiahzine.com, a link to the theme of the firmware, if possible, a direct link to the firmware (in case there is no full firmware, but there is a file update.zip, specify the link to this file), the version of the firmware for which recovery is required. In case the corresponding topic is not on the forum, give another link to the description and characteristics of your device or specifybriefcharacteristics of their own, namely: processor, operating system and screen resolution.ATTENTION!!!Check out this information !!Additionally indicate whether you have rights.rootIn the system, are there already created third-party recovery for your device (provide links), and if so, for what reason do you need to create a new one.
If you do not know the processor, information about it is in the file / proc / cpuinfo
If you do not know the screen resolution, take a screenshot (you can use it to determine the resolution)
The type of operating system and firmware version can be viewed in the Settings menu ->"About phone / tablet"

2.Files from firmware for which recovery is required:at least the boot partition imageboot.imgbut if possible the same wayrecovery.imgandblock map by namesections. In the extreme case, if for some reason you find it difficult to extract individual files, but have a link to the entire firmware, provide such a link.

If you do not have firmware for your device, and as a result there is not even a boot.img file, it will be almost impossible to make recovery. However, for some devices it is possible to relatively simply read the firmware directly from the device. And for some devices there is no such possibility. For example, for devices based on Mediatek processors using a computer and utilitiesSP Flash Tool is a flash driver for MTK smartphones.you can almost always (with the exception of devices with a locked bootloader), read the firmware directly from the device (reference to instructions)

Instructions

Getting recovery.img

The recovery.img image can be obtained from the full firmware (if available), or from the boot.img image and the recovery-from-boot.p files, recovery-resource.dat of the system.img image, by running the install-recovery.sh script
Also, the recovery.img image can be obtained from the flash memory dump (for Mediatek devices)

Getting a block map

A block map can be obtained on different platforms in various ways.
Typically, this is:
- for platformMediatek(arm) - the "scatter" file, or, depending on the operating system, type of installed memory and processor, respectively,
- for Android 4.x and mt65xx processors - file / proc / dumchar_info or"main-pt" block from flash memory dump
- for Android 5.x, 6.x, 7.x and mt67xx processors - file / proc / emmc or / proc / partitions or GPT block from a flash memory dump (the first 0x2000h bytes of the USER region)
- for platformQualcomm(arm) - the result of the terminal command execution (root rights are required):
ls -l / dev / block / bootdevice / by-name /
either from the fastboot command mode:
getvar all
- for platformSpreadtrum(arm) - the result of the terminal command execution (root rights are required):
ls -l / dev / block / platform / sdio_emmc / by-name /
- for platformRockchip(arm) - the result of the terminal command execution (root rights are required):
ls -l / dev / block / ... etc. , depending on the type of installed memory and operating system.
(e.g. /dev/block/platform/soc0/e0000000.noc/by-name/, etc.)
- for the Intel platform(x86) - from fastboot mode, the result of the command execution
getvar all

In any case, upon receipt of a block map options are possible. The method of passing along the path "/ dev / block / ..." and further is universal for all platforms, but requires root privileges. At the stage of creating the recovery block mapnot obligatory, but highly desirable.

Consider case, this is important. For example, paths:
/dev/block/platform/mtk-msdc.0/11230000.MSDC0/by-name/system
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system
The system is regarded as different, due to the different register "MSDC" and "msdc"

Creating a full backup for devices on the Mediatek platform

Creating a full backup for devices on the Mediatek platform

Post has been editedjemmini - 17.09.18, 21:07

[illialoo99]

1. TabletPrestigio MultiPad PMP5570C | 2012 | Discussion Firmware theme Firmware All firmware (4.1.1)| PMP5570C_20130321_v1.1.9 |Description | Root| CWM (I did not find the links), just need a better recovery.
2. The tablet is not mine and because of this I don’t have access to any system files yet. On a rockchip, I don’t know how to get the recovery.img file and boot.img, I’ll look, in principle, I threw you the firmware, download and disassemble yourself , it weighs a little and is called update.img. In the future I will add everything, so do not delete.

Post has been editedillialoo99 - 29.12.16, 16:46

[SVV001]

I ask for help in creating a CWM for our device:
Smartphone ASUS Pegasus 2 Plus X550 T550KLC
Firmware
boot.img(32 MB)
from the firmware above.
recovery.img(32 MB)
from the firmware above.
block map.txt(3.05 KB)

cpuinfo.txt(355 bytes)

mounts.txt(2.31 KB)

Route is installed.
Thank you very much in advance.

Post has been editedSVV001 - 31.12.16, 11:33

[Ki11er_34]

1. Tablet "Oysters t84ni 4g"
2. Oysters T84NI 4G - Discussion
3. Android 5.1
Ruth is
boot.img(7.38 MB)

recovery.img(8.09 MB)

K

Done -Oysters T84NI 4G - Discussion (Post by jemmini # 56653103)

Post has been editedvaalf - 30.12.16, 19:46

[V.A.G.R.A.N.T.]

Hello! Happy holidays to you!
Need help ... Please make TWRP Recovery for this tablet:
DIGMA Plane 7004 3G
Model Code: PS7032MG
Year of release: 2016
Operating system: Android 5.1
Processor: ARMv7 Processor rev 3 (v71)
Hardware: MTK MT8321M
link to the factory software version
Screen diagonal: 7 "(17.78 cm)
Screen Resolution: 1024x600
I attach the stock files from the firmware: boot.img, recovery.img, MT6580_Android_scatter.txt, and two files from the installed system: / proc / emmc and / proc / partitions:
boot.img(6.82 MB)

recovery.img(7.48 MB)

MT6580_Android_scatter.txt(8.84 KB)

emmc + partitions.zip(902 bytes)

---------------------------------------------
ROOT - available
----------------
Thank you very much in advance!

K

DoneDigma Plane 7004 3G - Discussion (Post by jemmini # 56652517)

Post has been editedRu4kin - 30.12.16, 19:16

[maksnogin]

Hello, you can make a recovery or help get a root.

Theme:Jinga Basco L500 - Discussion

Files from the stream:
boot.img(4.03 MB)

recovery.img(4.4 MB)

MT6572_Android_scatter.txt(7.12 KB)

K

DoneJinga Basco L500 - Discussion (Post by jemmini # 56648499)

Post has been editedRu4kin - 30.12.16, 16:49

[Papuk]

Good day. need help with TWRP
Theme:Discussion BQ-6050

Stock boot and recovery
boot.img(16 MB)

recovery.img(16 MB)

MT6737M_Android_scatter.txt(9.83 KB)

K

DoneBQ-6050 - Discussion (Post by jemmini # 56655380)

Post has been editedRu4kin - 30.12.16, 22:03

[Doommann]

Greetings.
Body BV6000s. MT6737T processor. Theme:Blackview BV6000S - Discussion
Booth, recovery, and scatter:

boot.img(8.56 MB)

MT6737T_Android_scatter.txt(9.16 KB)

recovery.img(9.54 MB)

K

Done -Blackview BV6000S - Discussion (Post by jemmini # 56674533)

Post has been editedvaalf - 31.12.16, 13:10

[Ilyamost]

Hey, big do TWRP Recovery

Brand: iPhone 7 China
Year: 2016
Manufacturer: China
Android 6.0 operating system
MediaTek MT6580 processor, 1 GHz, 4 cores.
The amount of RAM 2 GB.
The amount of ROM 8 GB.
Root: not received

K

Done -IPhone7 replica on MTK6580 - Discussion (Post by jemmini # 56962245)

Post has been editedjemmini - 09.01.17, 15:11

[Geo_GEO]

Greetings I will ask the respected masters to make TWRP for our device.

1.SmartphoneFly FS510 Nimbus 12, 2016 year of releaseFly FS510 Nimbus 12 - Discussion (Post tommi2 # 56301932)
Firmware version SW07_FLY_FS510_2016_10_20 (I plan to install it on version SW10_FLY_FS510_2016_10_28, it is not yet available).

Specifications

Ruth is absent, like other custom recovery.

2.Attached files:

boot.img(7.29 MB)

recovery.img(8.06 MB)

MT6580_Android_scatter.txt(8.52 KB)

Link to firmware:https://yadi.sk/d/VVXUMou636JTA6
Thank!

K

DoneFly FS510 Nimbus 12 - Discussion (Post by jemmini # 56701028)

Post has been editedRu4kin - 01.01.17, 18:04

[ilia3367]

Respected jemmini!
I ask for help in creating TWRP forLenovo Tab 3 TB3-850M - Discussion. Firmware themeLenovo Tab3 A8 850M - Firmware
Root no ...
Firmware archivehttps://cloud.mail.ru/public/B7Ga/PUAoShUK3
boot-sign.img(8.69 MB)

recovery-sign.img(9.61 MB)

MT6735M_Android_scatter.txt(9.85 KB)

Thanks in advance! : thank_you:

K

Done -Lenovo Tab 3 TB3-850M - Discussion (Post by jemmini # 56709371)

Post has been editedvaalf - 01.01.17, 23:32

[valera201085]

recovery.log(22.84 KB)
Hello, help make TWRP 3.0.2 on the device Jinga Basco M1
Topic of discussionJinga Basco M1 4G - Discussion
Root is received through KingRoot
Specifications

Key features of the smartphone JINGA Basco M1 4G White
Country china
ARE COMMON
Android operating system
OS version at the beginning of sales 5.1
Type of SIM card Micro-SIM
Support 2 SIM cards
CPU
Manufacturer MediaTek
Type MTK6735m
Frequency 1300 MHz
MEMORY
RAM size 1 GB
8 GB internal memory
MicroSD, microSDHC memory cards
The maximum amount of memory cards 64 GB
SCREEN
IPS type
5 "diagonal
Amount of colors 16000000
480x854 pix resolution
STANDARDS CELLULAR COMMUNICATIONS
GSM 900, 1800, 1900
Work in 3G networks Yes
Work in 4G (LTE) networks There are
COMMUNICATIONS AND COMMUNICATIONS
Wi-Fi Yes
Bluetooth Yes
A2DP Yes
GPS satellite navigation
WAP Yes
GPRS Yes
EDGE Yes
HSDPA Yes
E-mail There is
HTML there are
MULTIMEDIA
Support audio MP3, WAV
Video support 3GP, MP4, MPEG4, WMV, MOV
FM tuner Yes
RDS Yes
Java there are
Built-in speaker Yes
CAMERA
5 megapixel resolution
Built-in flash
Video recording Yes
Autofocus Yes
Zoom digital 2x
Front camera Yes
2 megapixel front camera resolution

Archive with firmware
https://cloud.mail.ru/public/77ov/nAY3DiV56
The scatter file in the archive with the firmware is apparently not correct, but this is just my guess.
Block map

partno: start_sect nr_sects partition_name
emmc_p1: 00000400 00001800 "proinfo"
emmc_p2: 00001c00 00002800 "nvram"
emmc_p3: 00004400 00005000 "protect1"
emmc_p4: 00009400 00005000 "protect2"
emmc_p5: 0000e400 00000400 "lk"
emmc_p6: 0000e800 00000400 "para"
emmc_p7: 0000ec00 00008000 "boot"
emmc_p8: 00016c00 00008000 "recovery"
emmc_p9: 0001ec00 00004000 "logo"
emmc_p10: 00022c00 00005000 "expdb"
emmc_p11: 00027c00 00000400 "seccfg"
emmc_p12: 00028000 00001000 "oemkeystore"
emmc_p13: 00029000 00003000 "secro"
emmc_p14: 0002c000 00004000 "keystore"
emmc_p15: 00030000 00002800 "tee1"
emmc_p16: 00032800 00002800 "tee2"
emmc_p17: 00035000 00000800 "frp"
emmc_p18: 00035800 00010000 "nvdata"
emmc_p19: 00045800 00012800 "metadata"
emmc_p20: 00058000 00300000 "system"
emmc_p21: 00358000 000c8000 "cache"
emmc_p22: 00420000 00300000 "userdata"
emmc_p23: 00720000 00767c00 "intsd"
emmc_p24: 00e87c00 00008000 "flashinfo"

Native Boot and Recovery attach
recovery.img(6.98 MB)

boot.img(6.31 MB)

K

Done -Jinga Basco M1 4G - Discussion (Post by jemmini # 56801977)

Post has been editedvaalf - 04.01.17, 22:55

[Noldestram]

Please, ask for help in creating TWRP for YUNSONG S9 Plus smartphoneYUNSONG S9 Plus - Discussion

aliexpress page with description, below the screen of detailed characteristics

https: //www.aliexpress....3966725-09626-VnYZvQVf

MTK 6580M
Android 5.1
Display 540 * 960
Root is, through KingRooT, I would like to later replace it with SuperSU, the usual methods did not fit.

boot.img

https://yadi.sk/d/yVXg6QyW36fD8q

recovery.img

https://yadi.sk/d/78lb_jNZ36fNRM

Firmware

https://yadi.sk/d/Llv7GjNh35Zmhb

MT6580_Android_scatter.txt(8.52 KB)

K

Done -YUNSONG S9 Plus - Discussion (Post by jemmini # 56802623)

Post has been editedvaalf - 04.01.17, 22:57

[stingerst]

You need a custom recovery for the tablet:
DEXP Ursus NS310. Year of release 2015.
Theme:Dexp Ursus NS310
It is stitched by analogy with this device:Chuwi vi7
Firmware:Dexp Ursus NS310
Ruth is received.
Android 5.1.1
Firmware: NS310_R01_24.05.2016_V1.1

Instead of images * .img in firmware * .fls
boot.fls
recovery.fls

Block map fails how to do

[ShadyTiger]

Greetings Please help!
I really want TWRP for a fresh version 3.0, maybe something will work out ...

Smartphone: LG G Pro Lite Dual D686 (MTK6577, 5.5 "- 540 x 960, 4.4.2 KK / ROOT)
Theme:LG G Pro Lite Dual - Discussion

Stock Recovery:recovery.img(7.1 MB)

Stock boot.img:boot.img(7.01 MB)

2nd boot.img:unsecuredboot_d686.img(7.07 MB)

Block Map:MT6577_Android_scatter_emmc.txt(688 bytes)


Old TWRP worker:TWRP_2.8.7.0_d68x.img(8.12 MB)


Post has been editedShadyTiger - 08.01.17, 13:35

[itrump]

I ask for help in assembling TWRP forBlackview BV6000 - Discussionwith the current kernel version from Android 7.
Characteristics: MT6755 processor, resolution 720x1280.

• Recover from Android 7 -recovery.img(12.19 MB)
  
  
• Android 7 boot -boot.img(9.53 MB)
  
  

In the theme with the firmwareBlackview BV6000 - FirmwareThere are several versions of TWRP with Android 6 cores and in most cases they work correctly with Android 7 as well.
But if file system encryption is used (Settings ->security -->encrypt data ), then TWRP can not decrypt the section, always the error "Password is not correct." Accordingly, it can not mount partitions. Apparently the new firmware has a different file system encryption mechanism. This shows a similar problem. Youtube (video)


I dumped the flash drive and cut sections by offset from the scatter file, as in the instructions from the header.
Found differences in the system section headers. In the old firmware with Android 6, the system section starts like this

3AFF26ED 01000000 1C000C00 00100000 CCFF0C00 7D0D0000 00000000 C1CA0000 01000000 0C100000
File utility defines image as Android sparse image, version: 1.0

At the same time, in the new firmware with Android 7, the image that I read from the flash drive starts with zeros and the file utility defines it as

Linux rev 1.0 ext4 filesystem data, UUID = da594c53-9beb-f85c-85c5-cedf76546f7a, volume name "system" (extents) (large files)

I am sure that I was not mistaken in the offsets, because it turned out to cut all the other sections correctly.
I see two possible reasons:

• In the new firmware, the partition table is changed?
  
• Does the new firmware have a different file system?

I did not manage to get the current scatter file for the firmware from Android 7, because MTKDroidTool did not work for me with MT6755.

There are no information on all known paths in the system:

/ proc / mtd
/ proc / emmc
/ proc / dumchar_info

Post has been editeditrump - 04.01.17, 06:46

[treever]

I ask to assist in the creation of a full TWRP recovery for:
Smartphone Elephone S3 (second revision, i.e. device released after 08/24/2016)
1. Topic on the forum:Elephone S3 - Firmware (OS 6.0)
Firmware:Elephone S3 - Firmware (OS 6.0) (Post ValeriyVK # 52641415)or immediately link to the cloudhttps://mega.nz/#!nk9S…6-3_DC7edQf2op43BMW_roOther existing firmware on the network do not go to the new revision (the screen and sensor fail, the system starts up, judging by the sound).
User hanuma50 has developed a partially working TRWP recovery.http: //savagemessiahzine.com/forum/d...381599/TWRP_ELE_S3.rar
The sensor does not work, flashing zipy with errors (maybe it's not about recovery). You can make backups. Using an OTG cable with a mouse, you can get root stitching SuperSUhttps://yadi.sk/d/WO2QUgkvxxoYm- accordingly, there is a root.

I do not know how important it is, but in the folder with the firmware there is a recovery-verified.img without having stitched the stock recovery, it also boot-verified.img

2. All necessary files are attached and signed, if necessary I will provide any other files and explanations.

hanuma50_recovery.img(12.79 MB)
stok_boot.img(8.62 MB)
stok_MT6753_Android_scatter.txt(9.17 KB)
stok_recovery.img(9.71 MB)
modified scatter for the first revision (extended system section for custom firmware) .txt(9.17 KB)
working on the first revision_recovery.img(14.13 MB)

K

Done -Elephone S3 - Firmware (OS 6.0) (Post jemmini # 56798289)

Post has been editedvaalf - 04.01.17, 21:04

[DpblHkuHc]

welcome dear need help
tel BQS-5515 need TWRP
no topicBudget smartphone BQS 5515 Wide went on sale
bootloader unlocked
boot.img(6.44 MB)

recovery.img(7.15 MB)

firmware 5.1 took herehttp://www.needrom.com/download/bqs-5515/

K

Done -BQS-5515 - Discussion (Post by jemmini # 56832839)

Post has been editedvaalf - 05.01.17, 21:17

[nik-68]

Hello, I need help.
tel Doogee X9 Pro need TWRP
ThemeDoogee X9 Pro

boot.img(8.23 MB)

recovery.img(9.05 MB)

Firmware 6.0 Official from 20161203-133951MP_mt6737_n381b_a53t

K

Done -Doogee X9 Pro - Discussion (Post by jemmini # 56831166)

Post has been editedvaalf - 05.01.17, 20:45

[malchik-solnce]

Hello: blush:
You need to update TWRP for Mi Note Pro on the new Android 7.0

The core of the firmware from Android 7.0https://yadi.sk/d/pxyt0CRe37AxGn
Current version 3.0.2Xiaomi Mi Note Pro - Firmware (Post jemmini # 47124222)

[syanusik99]

You need to recover twrp 3.0 forDexp ixion ml145

firmware stock 2.0 (Android 5.0)

Core

boot.img(4.15 MB)

Recovery

recovery.img(4.96 MB)

Scatter

MT6582_Android_scatter.txt(6.73 KB)

K

Done -DEXP Ixion ML145 - Firmwares (Fast jemmini # 56908564)

Post has been editedvaalf - 07.01.17, 23:41