I first unlocked the bootloader, then I loaded in twrp and from there I made decrypt.zip and immediately did wipe data. Then I patched my native recovery blocked the bootloader from the fast food mode. The smartphone then booted up normally. But now I think how to remove this decrypt and if you leave it as it will in the future affect the system.

Post has been editedgrom2 - 06.07.18, 13:24

Install yourself a fresh winrar, there is most likely a RAR5 compression, in the old version is not unpacked.

2 skyus - link to repacked in ZIP saved. Yes, I like the last portable version that I found put, did not open. ZIP is still more practical, there the standard Windows Explorer will open

2 grom2 And how to get the loader lock back? I understand that if I set up the recove, you can return the lock ...

Post has been editedsumerok - 06.07.18, 13:28

That's exactly what I did, one to one. As a result, Red State and everything from the beginning.
The only thing I think, I upgraded to firmware 311, it might not have been necessary.

Post has been editedskyus - 06.07.18, 13:28

https: //forum.xda-deve...api-stock-rom-t3810022According to the instructions of paragraph 17, but when locking the bootloader, the smartphone will reset all settings and installed programs and root as well. Only Cam2API.zip patch for google camera will remain untouched.

Post has been editedgrom2 - 06.07.18, 13:55

it means partial access, sorry.

I suggest the following (again, for those who have the device rooted) - check the file platform.xml, which is the root folder / system / etc / permissions along the way

Open platform.xml through the built-in text editor of any file manager, which one you use, but it is better through Solid Explorer and check the lines circled on the third screen, are all present.

Huge request - unsubscribe from someone like)

I do not have these lines only write media storage. The device is not ruled.

When upgrading the firmware Cam2API will not fly off?

how to do?

what team should be?

Something basically all the camera is discussing. And no one has installed the firmware yet? I have RR worth, like, a lot of settings. Interestingly, it will be just as good on this max or not.
Question. To install these "unofficial" firmware you need to do Unlock?

Post has been editedHaoose - 06.07.18, 18:24

I have some kind of tin, I put it according to the instructions of Magisk-v16.0.zip, I am overloaded - it seems everything works, both green ticks stand. Titanium receives RTH. Then turn off for google drinkMagisk GUI in the settings disable Magisk Hide, I reboot into TvRP, I sew universal-safetynet-fix-v2-beta-5.zip, I am overloaded - and Magisk writes that it is not installed. The label remains.

And by Google some ambush - I have two accounts, so this is the first fine is added, synchronized .. (WIFI or SIM cards), and by adding a second spell that Google servers available again later ... And I have all the games and payment it is tied to the second account, first there contacts, calendar. Tried and reset, and sew from tvrp open_gapps-arm64-8.1-micro-20180705 and other versions (pico, nano) - all else fails, a second account is not included. And that comes in the mail "suspicious activity", I click that it was me but again also not included.

When I try to flash the firmware via TV (tried UL-ASUS_X00T-WW-15.2016.1805.309-user and WW_ZB601KL (ZB602KL) _15.2016.1805.309-20180607.zip an error is generated"E3009: This package is for sku:" WW "; this is a sku:" ".
Updater process ended with ERROR 7 .

How to flash the firmware on a new one (I think that because of these locks / unlocks of the bootloader, maybe something went wrong) ..?

I did not do the full format (system), only reset. It looks like TWRP is normal, not encrypted (the size shows both internal folders and cards).


upd. It seems that the Google account with the dances was wound up, turning off WIFI and went to it on SIM, then disconnected the Internet on the SIM and everything went through WIFI.

It remains with root and Google PAY to figure out what worked)

upd 2 Why such a complex instruction to bypass root, I just put in the end of last Magisk all. There he is hiding from the program (Google PAY machine Add to hide, but the banks have myself put a tick) in the settings. Sberbank is normally open, also Touch and Tinkoff, root, they have not seen. But Titanium Ruth was great), there is not much to deal with permissions to write to the stick (but it is not critical, I Titanium backups just in memory postponed phone) and you're done. In general, all day messing gave off!)

Post has been editedsumerok - 06.07.18, 19:12

1. Launch Fastboot on smart
2. Unpack the archive WW_ZB602KL_15.2016.1805.309-20180607 for AFT (service) .zip on PC
2. If Windows is on a PC, then run flashall_AFT.cmd

sumerok , I was also picking, then I formatted it just flashed Magisk and it all worked right away, without additional disabling Hide and the firmware of the additional safe.zip file.

How to modify the officialFULL firmware for use via TWRP
1. download the official firmware from off site
2. download and install notepad ++npp.7.5.7.Installer.exe(4.25 MB)

3. unpack the firmware
4. follow the pathMETA-INF \ com \ google \ android and open the file updater-script in notepad ++
5. Further in this file we find these lines:

6. select these lines and click on notepad ++edit-cut
7. after cutting the data lines, the file now starts with lines:
and so on (tsiferki is the firmware numbers that modify (make sure this!)
8. click in notepad ++file save
9. Now we will pack back the folder inzip archive
ten . that's all, firmware is ready for Twrp firmware.

Post has been editedjide - 04.08.18, 01:43

But can you copy your platform.xml, archive it in .zip and send it to me in koumiss? I want to look in full and compare with my out of 5 android.

File "Stock Recovery" for a subjectrecovery_stock.img(50.04 MB)

Who put custom questions, how long did the first launch last?

Given the Project Trabl, is it worth waiting for the adaptation of the firmware from 5Z under Max Pro?
I am a big fan of the Zen shell and for me personally its absence in Max Pro is the only significant drawback.

Before you begin, read through this instruction to the end and only after the ALL FOR YOU UNDERSTAND, start, NO ONE IS NOT RESPONSIBLE FOR ANY DAMAGES TO YOUR device, ALL THAT YOU DO YOU DO AT YOUR OWN RISK!
AT THE TIME OF THE USE OF THIS MANUAL UPDATE actual files TWRP AND USE TSELESOOBRANNOST "DECRYPT" depends on your firmware to this point in TOPIC

INFORMAL METHOD OF UNLOCKING THE LOADER
To begin, you should understand that when you unlock the bootloader, you lose the warranty, you will not receive the ota update, but the benefitsinformal way It is an opportunity to block the bootloader again and return the device as it was. When using off. unlock utilities there is no way back! so ;
1. install Android usb driverlinkas well as ADBlink
2. download archive with files for unlock / locklink
3. connect the device to the computer in fastboot mode (volume up button + shutdown button)you must first enable usb debugging
before the next step, save the existing data to internal memory somewhere as all data will be deleted!
4. unpack the archive from point 2 and run a file in itunlock.cmd (for linux users, file " unlock.sh ") the file can be run as administrator.
5. unlock the bootloader and delete all data on the internal memory of the device.
6. load the device into normal mode after unlocking and that's it, you're ready for the next stage;
ALTERNATIVE PROCEDURE IF UNLOCKING UNDER THE HIGHER METHOD DOES NOT WORK
WINDOWS 10
open the unlock folder
we clamp on the clave buttonshift , then in a free space in this folder we click right click ,Further
select in the context menuopen the powershell window here
in the windowpowershell enter the command below:
pay attention to the "point" at the beginning of the command!
WINDOWS 7
procedure also only in the context menu selectopen command window Further in the command window we enter the command;


INSTALLING CUSTOM RECOVERY
Depending on preference, you can use any of the following custom recovery, I personally prefer TWRP and have never used RWRP (therefore, to whom as);
but. TWRPlink
b. RWRP (Red wolf recovery project)link
1. download this fileDECRYPT.ZIPandput in advance on the memory card
2. Download and install minimal adb and fastbootlink
3. reboot the device to fastboot mode and connect to the computer (USB debugging must be enabled )
4. run "minimal adb and fastboot" and execute the command in it;
make sure that our device is visible in the form of a serial
after this command we pressspace bar then we write the recovery file directory or simply from the desktop with the mouse in the minimal adb and fastboot window (this way the directory of the twrp.img file is also set) Most importantly, there should be a space between the command itself and the .img file itself.
4. after flashing custom recoveryIT IS NECESSARY TO DOWNLOAD INTO IT AND DON'T LET DAYS FIRST DOWNLOADING INTO THE INITIAL SCREEN, OTHERWISE THE STOCK RECOVERY WILL BE RESTORED! (To do this, you need to hold down the "volume down + power off / on" button and as soon as you select the device, immediately throw the "power off / on" button while continuing to hold the "volume down" button until you see the first TWRP window
VERY VERY IMPORTANT MOMENT AFTER RELOADING TO TWRP!
but .Being in TWRP flashing file decrypt.zip from point number 1
b. After the firmware file decrypt.zip, without leaving twrp, click thereWIPE-FORMAT DATA in the next window we write in the field Yes Next, click " SWIPE TO FORMAT DATA "and you will have all the data on the device deleted.
with. reboot into normal mode.
ATTENTION ! ! For some, when you first log into twrp after the firmware, it asks for a password, in this case you must click cancel \ cancel then return to the main twrp screen, then follow the intended instructions, tobish the firmware decrypt.zip then back to the twrp main screen, and there WIPE-FORMAT DATA write yes and confirm the removal of the swipe below

ROOT
1. Download the latest version of magisklinkand put on the memory card or internal memory
2. boot into TWRP and flash magisk and all profit, now you have a unlocked bootloader, custom recovery and root!

DOWNLOAD LOCK
Very important ! Since the blocking process is also accompanied by the removal of all user data in the internal memory, I highly recommend making backup of your data so ;
1. swingstock recovery link
2. Download utilities for removing magisk (root) and pre-putting it on an external memory cardMagisk-uninstaller-20200323.zip(2.57 MB)

3. reboot into TWRP and flashmagisk-uninstaller , reboot into normal mode and make sure that there is no root.
4. load the device into fastboot mode and connect to the computer (USB debugging must be enabled )
5. open minimal adb and fastboot and execute the command in it again;

this time we are flashingstock recovery!
6. for fidelity, after the stock recovery firmware, you can (even need) download the off-firmware and flash it again from the already installed stock recovery.
7. download again if you do not have it archiveunlock / lock link
8. We connect the device again in fastboot mode and from the archive run the file calledRelock.cmd or "relock.sh" for linux users (files can be run from admin if that)
9. after file launchrelock.cmd All data on the internal memory will be deleted as well as the bootloader is locked.
everything works if you follow the instructions correctly

Post has been editedjide - 04.06.20, 23:09

Now I understand why I get the state Red State, this item explains everything.