[X]Assistant

[ilnur2198]

DiscussionAlcatel One Touch 5095Y / 5095K Pop 4S
Alcatel POP 4S
Discussion пїЅ

• Before asking a question, look Android OS FAQandGlossary. Respect your and other people's time.
• To discuss and search for third-party programs / games, use the following sections: Programs and Games.
• To compare the device with competitors and on the choice of devices, please contact: Selection and Comparison.
• The available amount of RAM and memory for installing applications is discussed in the topic: How much memory do you have in the machine?
• The results of performance tests of Android devices, see the topic: Benchmark
• Before posting photos, read the topic Working with Images on the forum
• Messages that are not related to the topic of discussion (offtopic) are deleted without warning.
  

Specifications

Detailed specifications

General characteristics
Android 6.0
micro SIM
The number of SIM-cards 1
Weight 150 g
Dimensions (WxHxT)
77x152x7.99mm

Screen

5.5 inches 1920x1080
Number of pixels per inch (PPI)
401

Camera

13 million pixels. Autoflash
5 million pixels.
autofocus
Aperture f / 2
Max. 1920x1080 video resolution
Max. video frame rate of 30 frames / s

Connection

GSM 900/1800/1900, 3G, 4G LTE, LTE-A Cat. 6, VoLTE
Supports LTE bands 3, 7, 8, 20
Wi-Fi 802.11n, Wi-Fi Direct, Bluetooth 4.2, USB
GPS
A-GPS system

Memory and processor

MediaTek Helio P10 (MT6755) processor
The number of processor cores 8
Video Processor Mali-T860 MP2
16 GB internal memory
2 GB RAM
Slot for memory cards is, up to 64 GB

Nutrition

Battery capacity
2960 mAh
Talk time
15h
Standby time
500 h
Type of charging connector
micro usb
There is also a fast charge function.

Sensors
light, approach, hall, compass, fingerprint reading
Audio amplifier Hi Voice Hi-Fi AKM4375
There are two versions of this smart:
5095Y - 1SIM, 1 SD slot, support LTE Cat.6 up to 300 Mbps
5095K - 2SIM, 1 SD slot, support LTE Cat.4 up to 150 Mbps

Reviews

Text
http://www.ixbt.com/mobile/alcatel-pop-4s.shtml
http: //mobile-review.c...w/alcatel-pop-4s.shtml
Video reviews
https://www.youtube.com/watch?v=R_RUTTqRMTQ
https://www.youtube.com/watch?v=rxEALmAHhrk

Useful

Engineering menu: * # * # 825364 # * # *
Code setting Audio: * # * # 82533284 # * # *
Software Recovery Software
Photos taken with Google camera
The version of the program Files (File Manager) without advertising and optimizer "
"Disable / delete" octopus "and advertising in applications Joy Launcher (Standard mode), Files (File Manager) and Voice Recorder (Sound Recorder)"
Firmware v01001 under Flashtool

There is no curator in the subject. For questions about filling the caps, please contact the section moderators via the buttonunder the messages to which you want to add links.

Post has been editedAlexanderL - 17.09.18, 12:32

Reason for editing: Flashtool v01001 firmware

[booroondook]

So, for those who want to have fun and fuck on the phone root, which is valid before the reboot or shutdown.
Instruction

I. Download the following files:
1) Set "fastboot enable" from the previous message://savagemessiahzine.com/forum/d…32/fastboot_enable.zip
2) Authorization file for SP FlashTool from the previous message://savagemessiahzine.com/forum/d…/MT6755_SHINE_PLUS.zip
3) SP FlashTool utility from here (there is also an authorization file in the bundle):https: //drive.google.c...1SMzBlSDZuUzNfdjA/view
4) TWRP-recovery image for external download from the previous message://savagemessiahzine.com/forum/d…ternalTWRPrecovery.zip
5) su.img image:su.zip(373.73 KB)
6) Routine bootloader image:bootSU.zip(9.16 MB)
7) Application "SuperSU":SuperSU.apk(5.93 MB)


Ii. Create a folder on your computer, and there are subfolders in it to unpack downloaded files there. It is advisable not to confuse files from different groups with each other. In general, you will understand, not small.
And it is also assumed that you have a "gentleman's set" for working with ADB and fastboot on your computer.

Iii. Procedure.
1) Go to the settings of the phone, the menu "for developers", and there we include "Unlocking the bootloader". We read some kind of warning there, but we still turn it on.
2) Turn off the phone in the regular way and while putting it aside.
3) Run SP FlashTool, select the MT6755_Android_scatter.txt scatter file from the folder where we unpacked the "fastboot enable" set. We specify the file MT6755_SHINE_PLUS.auth as the authorization file.
4) We check that from the entire list of images there are only three check marks:
- preloader
- lk
- lk2
... and in front of each of these images, the path to the real-life file from the "fastboot enable" suite is specified (for lk and lk2, the same file is used).
5) We check that the "Download Only" mode is set, click the "Download" button, connect it with a cableoffphone and flash it. The process is fast, because small images are sewn.
6) Boot into recovery mode. To do this, press the "Volume Up" button and, without releasing it, press the "Enable" button. As soon as the phone starts to turn on, release the "Enable" button, and still hold the "Volume Up". As a result, we should get into the menu of the recovery itself, but the choice of the recovery menu language. Use the volume buttons to select the desired language, start the recovery menu with the power button. There is exactly the same - the choice of volume, the implementation of the inclusion. Run the second top item - "reboot to bootloader". We connect the phone to the computer (if it was not connected).
7) If everything was done correctly, then after 5-6 seconds the screen will turn dim gray (weak backlight), and in the lower left corner information will appear about being in fastboot mode.
8) From the computer we give the command "fastboot devices". In response, you should see a list of connected devices, consisting of one device - our phone.
9) ATTENTION:If you continue, all data from the phone will be erased, and it will return to the factory state. If everything is clear, then go further.
10) From the computer, we give the command "fastboot oem unlock". A bunch of warnings will appear on the phone. The general meaning is that if you press "Volume Up", the bootloader will unlock, the phone will be removed from the guarantee and in general you are all fools. If you press "Volume Down", then nothing will happen. In general, click "Volume Up".
11) On the computer, we will see that the operation was successful, on the phone the information will change to the standard for "fast-boot" phones menu boot mode selection - fastboot, recovery or normal. Unfortunately, the selection and execution keys specified in this text do not work for us. In general, no keys work. Therefore, the phone will have to restart manually. It is better for this to disconnect it from the computer, then hold down the power button and wait until the reboot begins.
12) The reboot is now done with a delay of 5 seconds, during which we are informed on the phone screen what bad we are, that we dared to unlock the bootloader. It is necessary to drop the feeling of false shame, wait for these unfortunate 5 seconds, and then the normal load will go on. Yes, I forgot to warn - loading with a delay of 5 seconds is now forever. Even if you reset or rewrite your phone. Get used to it.
13) So, the reboot has gone. First, it will be unsuccessful, then the phone will reboot itself again, and this time it will turn on the cleaning by the recovery forces - you will see the "green man" for a few seconds. Then everything will be like after a clean firmware - a long download and a welcome wizard - select a language, connect to WaiFay, specify an account, etc.
14) Having finished the reboot and start-up manipulations, we will again load the phone into fastboot mode (i.e., completely repeat the execution of clause 6, see above). We connect the phone to the computer if it is not connected.
15) On the computer, go to the folder where we unpacked the TWRP-recovery image, and from this folder, issue the command "fastboot boot recovery.img".
16) The phone will boot into TWRP-recovery, but there is little special joy here - this is not a permanent TWRP-recovery, but loaded from the outside. That is, it works only before the reboot. And the native factory recovery as it was stitched into the phone, so it lives there. And let him live.
17) The first thing TWRP-recovery will ask is to specify a password to decrypt the / data partition. It is encrypted here, thanks to the “brilliant idea” of Alcatel, or Media Library, or both. Actually, because of this encryption, we can’t install SuperSU in the normal way - so we have to pervert. So, the password. We do not know the password (and no one knows), so we press the "Cancel" button and move on, namely, we move the slider to allow access to the file system for writing.
18) TWRP-recovery automatically includes ADB access, which we will use. Our task is to place the su.img image (extracted from my archive it should be 100 megabytes in size) and the SuperSU.apk file in the / cache folder (and not / data, because / data is encrypted and therefore not mounted). To do this, use the ADB commands from the computer:
adb push su.img / cache /
adb push SuperSU.apk / cache /
19) Well, now the fun part.If it worked, then I would just write - flash the patched bootloader "bootSU.img" into the / boot section of the phone. But this option, unfortunately, does not work (hopefully, temporarily).
20) On the phone in the TWRP-recovery menu, click the "Reboot" button and select the "Bootloader" option. The phone restarts again in fastboot mode.
21) On the PC, go to the folder where we unpacked the patched image of bootSU.img and send the following command:
fastboot bootSU.img
22) Our phone should boot into working mode. Among the installed applications should be the application "SuperSU", which everyone knows how to use.
23) That, strictly speaking, is all. As I have already warned above, this “rudiness” will work until the reboot, because the external boot loader is only in RAM, there is no “hard copy” on the phone. Therefore, after a reboot, the factory factory loader will be loaded, and there will be no root. If this happens, then we switch the phone to fastboot mode again and reload the external patched bootloader, as described in section 21.

Post has been editedbooroondook - 24.02.19, 23:02

[erak31]

New passwords for Sugar

Post has been editederak31 - 25.02.19, 09:46

[erak31]

While the screen is broken, I decided to try to return the phone to the factory state, flash it with a sugar pipe.
But this is what this sodom betrays and does not want to go on. (at least at least the login and password came up)

And Mobail upgrade native also does not want to connect, writes that the model is not correct. I did something with Flash Plus firmware (

It looks like the image of mobile_info.img from FL2. The FL2 flashlight image flies, but the native Nivka, referring to the error

status_sec_img_type_mismatch 0xc002002a

Post has been editederak31 - 25.02.19, 12:56

[booroondook]

erak31,Flashlight native firmware tried to flash?

[erak31]

booroondook,
Watching what. Although even his own one, which he poured with a flashlight, does not want to sew entirely. Swears on simlock, info mobile. Although from Flash Plus 2 they fly into the light. They have different sizes compared to ours. (mine and with a drain in a hat.)
So I don’t know, because of these images, the sugar does not want to determine whether the passwords are still not suitable.
It is necessary for someone to try these passwords and with a normal machine, maybe I tortured myself (

[booroondook]

[email protected], 19:02

Someone needs to try these passwords and normal devices.

Well, I have already sewn my own sugar four times, and everything is fine.
True, I have never flooded the firmware from FP2 there - maybe it saved me ..

[email protected], 19:02

They have different sizes compared to ours.

The sizes are almost the same. At least, the scatter files on both phones are the same - it means that the addressing of the sections is the same.
A small difference may be in the size of the images - but this should not affect other sections. The fact is that in memory the space for a section is allocated with a margin. For example, 16 MB are allocated for the boot, and the image supplied in the factory firmware has a size of 9 MB. When recording, just left unused "tail", which does not affect anything. Accordingly, different models of "related" phones may have fluctuations - one but 9 MB, the other 9.2 MB. But the image still does not block the place allocated to it.
Another thing is that when images are merged from the phone, then the entire section is merged in accordance with the selected place (there is simply no information about the space actually occupied, so not only the image but also the “tail” is merged, complementing the section to completion.
Therefore, merged images, as a rule, are always more factory-made. An experienced “picker” can run over the dump and cut off unnecessary “tails”, thus bringing the firmware in order. Well, inexperienced will lay out everything in the form, as downloaded from the phone.

[erak31]

booroondook,
You will be able to merge FlashTool from your device via OTP

These blocks are:

partition_index: SYS10
partition_name: mobile_info
file_name: mobile_info.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x8bc8000
physical_start_addr: 0x8bc8000
partition_size: 0x800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
is_upgradable: true
empty_boot_needed: false
reserve: 0x00

- partition_index: SYS11
partition_name: simlock
file_name: simlock.img
is_download: true
type: EXT4_IMG
linear_start_addr: 0x93c8000
physical_start_addr: 0x93c8000
partition_size: 0x800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
is_upgradable: true
empty_boot_needed: false
reserve: 0x00

- partition_index: SYS17
partition_name: md1img
file_name: md1rom.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0xc300000
physical_start_addr: 0xc300000
partition_size: 0x1800000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
is_upgradable: true
empty_boot_needed: false
reserve: 0x00

- partition_index: SYS18
partition_name: md1dsp
file_name: md1dsp.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0xdb00000
physical_start_addr: 0xdb00000
partition_size: 0x400000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
is_upgradable: true
empty_boot_needed: false
reserve: 0x00

- partition_index: SYS19
partition_name: md1arm7
file_name: md1arm7.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0xdf00000
physical_start_addr: 0xdf00000
partition_size: 0x300000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
is_upgradable: true
empty_boot_needed: false
reserve: 0x00

- partition_index: SYS20
partition_name: md3img
file_name: md3rom.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0xe200000
physical_start_addr: 0xe200000
partition_size: 0x500000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
is_upgradable: true
empty_boot_needed: false
reserve: 0x00

I'll try to insolently fill in with formatting sections.

[booroondook]

erak31,But why merge from the phone if there are ready-made factory images?
I once already wrote about this. If you have already tried to flash the phone with Sugar, then in the folder c: \ Program Files (x86) \ SUGAR MTK_SP_Gotu2 \ bin \ download \ you should have downloaded firmware images - true, in a packaged-encrypted form - like this:
71B57070CA00.mbn_274803
81B5HN71CA20.mbn_276476
B1B57070CA00.mbn_274805
D1B5HN71CA20.mbn_276477
E1B5HN71CA20.mbn_276478
F1B5HN71CA20.mbn_276479
G1B57070CA00.mbn_274806
H1B57070CA00.mbn_274807
I1B57070CA00.mbn_274808
K1B5EMMCCA00.sca_230930
L1B5HN71CA20.mbn_276480
P1B57070CA00.mbn_274809
R1B57070CA00.mbn_274810
S1B5HN71CA20.mbn_276481
T1B57070CA00.mbn_274811
U1B57070CA00.mbn_274812
W1B07070CA00.mbn_274813
X1B0HN01CA20.mbn_276482
Y1B5HN71CA20.zip_276483
If the files are not there, then run Sugar and wait for the download of these files.
Then, at the beginning of the firmware process, these files will be decrypted-unpacked and placed in the% TEMP% folder in the form of normal FlashTool images. Only the file names they have will be as incomprehensible.
Copy these files to a folder (because they will be deleted if you quit Sugar) and rename them to normal names - lk.bin, system.img, etc. Where what file - you will understand by the sizes and titles. In particular, the scatter file is K1B5EMMCCA00.sca.
You will have a complete set of firmware. The only thing is that the file X1B0HN01CA20.mbn (it is also simlock.img) may be zero length. You can not flash it. Well, or if you really want, then take it from the archive in this message:Alcatel OneTouch 5095Y / 5095K Pop 4S - Discussion (Post by djhim # 77096820)

[erak31]

booroondook,
Yes, the essence is that sugar does not define the device and it is not possible to take all these files.
Hanging on authorization.

Apparently because of the info_mobile.img firmware, simlock.img and md3rom.img. from FP2.
And with the firmware of the drain, from the message above, swears at info_mobile.img, simlock.img and md3rom.img.
If you have the opportunity to pull out these images from the sugars, you would try to flash them. But if they have hash coincides with stock, then they will not help.
But if you try to merge with FT using the OTP method, the partitions that I asked for, you can try to pour them into the brazen.

[booroondook]

erak31,well, check:
Backup.zip(9.83 MB)

[erak31]

booroondook,
No, it does not sew.

Please drain via OTP

[booroondook]

erak31,What is "OTP"?
I downloaded SP FlashTool via USB cable.

Post has been editedbooroondook - 26.02.19, 15:16

[Shurupeye]

Something I can not find:
1) Sugar itself (the post with it is empty)
2) Firmware for 5095k (I doubt that they are compatible with 5095y)
Help, plz, who than can. Than the corpse hanging to reanimate?

[erak31]

Shurupeye,
Download the sugar from the Internet if it does not work here. A login and password from my posttyk

Post has been editederak31 - 06.03.19, 12:59

[Shurupeye]

Where is the password? Empty post. Empty spoiler in the post, without text.

And how does this comment from the "black" forum
http://forum.gsmhosting.com/vbb/f606/sugar-mtk-sp-tool-need-1914128/index2.html

Because of ridiculous public sharing, TCL closed all shared accounts,
moved to new login / registration system

So, you are not gonna find it, because nobody is crazy
which will be blacklisted very quickly.

Those times of easy alcatel flashing are gone for good. Live with it.

However ... as always, there is
able to flash new models. Use search on forum to find out which ones ...

b.r.
Alex

Alcatel was surprised at the silly sharing of accounts, and blocked all old logins. They began to follow the new logins more carefully, began to bind them to IP.

Post has been editedShurupeye - 06.03.19, 15:02

[A-Z-H]

Shurupeye,
There is a hidden text, go to the forum with authorization, the text will be visible.

[Shurupeye]

That I am always logged in. So, my account does not have enough rights. It is necessary c "Active users" to grow to the group "Friendssavagemessiahzine.com".

[trojan4egg]

booroondookHello, if you get a root on the phone, will all the data be erased?

[booroondook]

trojan4eggYes. They are erased after unlocking the bootloader.

[morphay]

erak31 -Thank you!