Rep: (124)
Hello. I am looking for a router capable of easily piercing 2 walls without loss of speed and supporting Padavan firmware. Frequencies 2.4. What can you advise from reliable and not old?



Rep: (124)
TWRP for Oukitel C8

I strongly recommend that before any manipulations with the phone make a full ROM backup using SP Flash Tool is a flash driver for MTK smartphones.
Scatter file for Oukitel C8:Attached fileMT6580_Android_scatter.txt(9.54 KB)

Scatter in zip archive:Attached fileMT6580_Android_scatter.zip(1.18 KB)

Preloader file for Oukitel C8:Attached filepreloader_wd393b.zip(79.3 KB)

Stock Boot and Recovery (in case you need to recover):Attached fileStock_Boot_and_Recovery_Oukitel_C8.zip(18.3 MB)


Recovery collected on the basis of the kernel firmware Android 7.0 version OUKITEL_C8_V7.0_20171012.

Download TWRP:

Version 3.1.0:Attached filetwrp310.zip(11.5 MB)

Version 3.1.1:Attached filetwrp311.zip(11.23 MB)

Version 3.2.3-0 (recommended):Attached fileTWRP_3.2.3-0.zip(10.23 MB)


ATTENTION! When using the "TWRP Installation Instructions with ADB"you need to unlock the bootloader. This action leads to the cancellation of the guarantee. You take all actions at your own peril and risk. No one except you is responsible for any problems.

You will need a computer.

Instructions for unlocking the bootloader:
As a result of unlocking, you will receive a completely clean phone: all user data and programs will be erased!
1. In the "Settings" menu of the smartphone, activate the "For Developers" menu (as a rule, by repeatedly pressing the build number in the "About phone" tab) and select "Allow factory unlock" in the menu. Turn off the machine.

2. Switch the device to the "fastboot" mode by pressing the volume up and power off from the off state of the key combination by selecting the "fastboot" (bootloader) option from the appeared text menu of the bootloader.

3. Connect the smartphone cable to the USB port of the computer (in the Device Manager, the Android ADB Interface device should appear), (if necessary, install the appropriate ADB device drivers).

copy the necessary utilities to the computer:Attached fileAdb.rar(1.44 MB)


, unpack them into a separate folder and open it in the command line (in the explorer, highlight the folder, press and hold shift, right-click on the folder and select "Open command window" in the menu that appears - a black terminal window will appear).

4. At the command prompt, enter the command:
fastboot devices
at the same time, if everything is installed and connected correctly, as a result of the command, you will get the output line of your smartphone like:
fastboot 0123456789ABCDEF

5. Enter the unlock command:
fastboot oem unlock
while on the screen of the smartphone you will be prompted to confirm the intentions by pressing the volume up. Press the volume up.
On the command line, if the command is successful, you will see the following:

C: \ ADB>fastboot oem unlock
...
(bootloader) Start unlock flow

OKAY [43.920s]
finished. total time: 43.921s

IMPORTANT!! Do not miss this item! ->
6. Restart the smartphone with the command
fastboot reboot


Instructions for installing TWRP using ADB:
Turn off the smartphone and call the mode "fastboot". Connect it to the computer.
Copy the image of TWRP recovery.img to the folder with ADB utilities. At the command prompt, type:
fastboot flash recovery recovery.img
In this case, the recovery will be flashed into the memory of the smartphone. Reboot your smartphone with a team
fastboot reboot
Immediately after the command, hold down the "Volume Up" button and wait until a menu of 3 items appears. Select recovery. Must boot into TWRP.
Unplug the cable. Is done.


Instructions for installing TWRP using the SP Flash Tool:
InstallSP Flash Tool is a flash driver for MTK smartphones.I am using version 5.1628.
Create a folder in the root of the C drive with the name TWRP, copy the downloaded recovery.img and scatter file into it.
Open the flash driver:
Do not touch the "Download Agent" line.
In the "Scatter-loading file" line, select the previously prepared scatter file.
The line "Aunthetication File" (if any) is not touched.
If everything is done correctly, then below, in front of the item "recovery" there will be a tick.
Then select the firmware mode: Download Only, click the Download button,and only after that we connect the switched off device!
The process of the firmware will start, a window with a tick will appear after successful completion. Close the program, turn off the smartphone.
Now you can enter the recovery by holding the "Vol +" and the power button (on the phone off).


Instructions for updating TWRP to a new version using the internal toolkit:
Boot into TWRP. Select the Install-Install Image (or img) item,
select the recovery.img file, select the Recovery section for the firmware image,
We make a svayp to confirm the firmware, at the end we select Restart.
New version of TWRP installed.


Instructions for obtaining ROOT rights:
Download the zip archive from SuperSU:Attached fileSR1-SuperSU-v2.82-SR1-20170608224931.zip(5.99 MB)

Boot into TWRP. Select the item Installation,
select the downloaded zip archive from SuperSU,
do svayp to confirm the firmware,
at the end, select Reboot.
ROOT rights obtained.


Post has been editedAgafonoff - 08.09.18, 14:37
Reason for editing: Added TWRP 3.2.3-0



Rep: (124)
TWRP Recovery 3.2.3-0

Updated TWRP to the latest version. Recovery collected on the basis of the Android 7.0 kernel kernel version OUKITEL_C8_V14.0_20180116.

Download:Attached fileTWRP_3.2.3-0.zip(10.23 MB)


Posted on 09/06/2018 at 20:56:

* gromovou with joy, but it’s necessary to correct a lot, that's why I wrote that, maybe, someone would do it before and put it out. I'm sick now, I will pick it slowly.



Rep: (124)
* sataniq, Thanks I'll know.



Rep: (124)
* sataniq, I honestly do not remember, but from fastboot like the command fastboot reboot recovery does not work. But I don’t say for sure, because I haven’t bothered about it for a long time and don’t remember. I recently remembered the phone, tried again to fasten the imprint, but still could not. It was not the first attempt, this time that I didn’t make it, I tried the variation to the fig, it didn’t work. Head spinning, threw. ))

P.S. The guys in the topic of porting found a solution to inactive incoming calls on Los 14.1. Now I ported Los 14.1 to our device, this edit also works for us. Inbox come. While testing, you need to edit the jambs. If anyone needs to, later lay out. Although maybe someone will fill his faster.

Post has been editedAgafonoff - 06.09.18, 17:13



Rep: (124)
Hello. It was previously written here that twrp 3.1 does not work with ver firmware. 14. I checked and found out that it is not. Simply, in the case of firmware via adb, after running the fastboot reboot command, you should immediately hold down the "Volume Up" button and select recovery from the 3-item menu that appears. After that, twrp should boot successfully.
P.S. Later for the sake of the purity of the experiment I will check it again.

Post has been editedAgafonoff - 06.09.18, 15:16



Rep: (124)
Hello. I have a tablet Chuwi vi8 Ultimate white. As I understand it, it differs from yours only in the display resolution. Smashed the touch, came new pb80jg2296 FHX. Replaced, but the bottom of the wheel does not work. No one came across this? Maybe someone has a driver for this tacha?



Rep: (124)
* ska-vova
something I can not find. I searched differently. Please share the program archive or give a link if it's not difficult for you.



Rep: (124)
Hello. Windows 10, And_Pda utility from Akella's post. Attempting to pack stock or modified system.img from two different donors ends the same way. I did not find a similar search on the topic.

Log:

error: file_skip: lseek64: No error
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument

Has anyone met with this, is there a solution or standards utility for Android 7, 8?



Rep: (124)
* vad1m morozov when you try to pack, it also gives an error. I tried two different images. Does anyone have a un / repacker system.img for Nougat / Oreo under Windows 10?
P.S. I apologize, with the eyes apparently bad. The topic is confused with 6580.

Post has been editedAgafonoff - 27.08.18, 19:11



Rep: (124)
Hello. Used PackUnpackSystem from Akella's post. Disassembles normally, during assembly issues
error: file_skip: lseek64: No error
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
error: file_skip: lseek64: Invalid argument
but the file is going. Somewhere six months ago I worked with this program, everything was normal.
Has anyone encountered this problem?



Rep: (124)
Hello, everyone. After the last update, Youtube became buggy. I press back, the video being played as always rolls up in the corner on the right, but now it does not close with the right swipe. Vipy kesh / data did. Someone came across.



Rep: (124)
Compiller @ 07.12.18, 23:06*
Maybe you encourage google in the direction of vdsl, if at both ends will be your equipment?

You apparently misunderstood me. The modem is on the PBX, but the PBX is not mine). Rostelecom DSLAM ADSL2 + is on the PBX, VDSL2 does not smell there. It would be enough for me and 20 Mbps for adsl2 +, but Rostelecom does not give individual rates and will not set anything up for me.



Rep: (124)
Konstantin_73 @ 07.12.18, 21:25*
And how will the Internet go into the apartment (house)?

I have a link for eight years (I did not expect it to work so much), recently I started to reboot uncontrollably and the modem to the PBX disappeared. I think so, konder in bp or the router itself is dying. The link itself is:
ADSL modem on the PBX, from it to the roof cable to the Ubiquiti Nanostation M2, then WiFi bridge with the second Nanostation m2 on the roof of the house, from him the cable to the router of the house.

Posted 07/07/2018 22:41 PM:

Virtual13 @ 07.12.18, 22:23*
what's the difference in bridg

And there are no such concepts as shitty iron or buggy software?

Post has been editedAgafonoff - 12.07.18, 22:42



Rep: (124)
Hello.
1. ADSL2 +.
2. 6 Mbit, Rostelecom.
3. PPPOE.
4. Bridge mode.
5. Within 1500 rubles.
6. Preference one: reliability.
7. PBX (home).
Tell me, please, adsl2 + modem for uninterrupted operation for years. ) Since the modem will be from me a kilometer away on the PBX of the provider, reliability and stability of work are required (just like that, you will not get on the PBX if you have a problem).
P.S. Found two routers with adsl2 +. D-link dsl-2640U / RA / U2A and tp-link TD-8961N. In the course of anyone, which of this is more stable and better?

Post has been editedAgafonoff - 12.07.18, 20:21
Reason for editing: Completed



Rep: (124)
* <DMITRIY> , that's exactly what the fucking ADSL Rostelecom and I have now. At the same time, there are 100 Mbps Ethernet ports on the PBX, but they are not provided (for IP only). This is in our outback, where you can’t find SP in the afternoon with fire. Previously, when building the link, VolgaTelecom was the company that allowed the equipment to be installed. After swallowing Rostelecom, everything became worse. Okay, stop offtopic. There will be some progress or problems, I will turn to the topic. Thank you all for your help.



Rep: (124)
* <DMITRIY>,
Yes you are right. Authorization of ppoe at home on Kinetics, on the PBX modem only raising the link. In principle, the ping to the modem PBX is less than or equal to 1 second. Turned off dhcp on the PBX modem, it is not needed there. Look at the behavior of the Internet tomorrow. But I have the impression that just bp or modem on the PBX began to breathe (6 years without a break plowing) and Zyxel has nothing to do with it.



Rep: (124)
* anans Yes, naturally, in wan. And from the kinetics of what settings to apply?



Rep: (124)
Hello. I have an unusual network. The network structure is as follows: ADSL modem in PBX (static IP 192.168.1.1, dhcp enabled) in bridge mode, wire from it to a Wi-Fi access point Ubiquity Nano M2 (static IP 192.168.1.2, dhcp off) on the roof of the PBX, then WiFi Ubiquity Nano M2 client (static IP 192.168.1.3, dhcp off) on the roof of the house, from him the cable to the house to Zyxel Keenetic (static IP 172.16.0.4, dhcp included). Recently, the modem on the PBX has become buggy and reset. Is this possible due to the fact that dhcp is included in the modem of the PBX and in the keenetic at home? When you disable dhcp in the modem, the PBX, in theory, will not the Internet disappear and access to its web snout? In theory, after all, dhcp needs only Zyxel Keenetic, on which ppoe authorization occurs and users get IP via dhcp?



Rep: (124)
* sarbre , thank. In principle, I thought that my own prose is stupid (or rather, I think that gifts from the Chinese have come) and the battery is eating. I switched to custom, all the rules became.

Full version

Help     rules

Now: 07/30/19, 00:40