yashsingh1/xdaforums huggingface dataset:
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Before attempting to root the device I already had fingerprint / pin setup, hence just simply needed to re-enter the pin in that case. But, I was not sure if it is a must. Unfortunately, to fix it you will need to reset your os, using same steps as in https://xdaforums.com/yotaphone-3/development/yota-3-firmware-news-t3862999. Then ensure your device has pin installed, and then re-try rooting steps. I've updated my post with pin pre-req step.

---------- Post added at 04:12 PM ---------- Previous post was at 04:06 PM ----------

To determine if you're device is rooted you will see in Magisk app two green tickboxes (Latest Version: v18.0; Installed Version: v18.0) even after you reboot your device.

Please specify what steps you're unclear about, but before doing that please read through comments in: https://xdaforums.com/yotaphone-3/development/yota-3-firmware-news-t3862999 or google the step you're unclear about (especially pre-req ones)
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HvMES:
Well I did now with a password and it looked OK but still it is not rooted. :(
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] hanguyen1589:
has root been yota phone 3+ yet?

I have followed the instructions many times but still cannot succeed
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] paolinger:
Yota 3+ Stock Recovery access

1. On the phone off, press and hold the "Volume up" and "Power" keys

2. A robot will be lying with an open belly and an error on the lack of a command.

3. Lock the "Volume Down" and "Power" buttons, briefly pressing the "Volume Up" button
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Yota 3+ 8.1 System Root with TWRP recovery, Magisk and storage encryption disabled

Merged 2nd instruction into 1st post.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] nnlife82:
I've tried the latest instruction; failed in cmd as following :

"Ensuring the bootloader is unlocked..."

...

FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')

Anyone?
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Can you check if in developer options OEM unlocking is ON (as in first instruction > pre-recs > step 4).
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] nnlife82:
Yes, it's on.

So technically I don't have to unlock bootloader first right?:)
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
If it was ON, the expected message in script should've been "Already unlocked" instead of message you've seen ("Need wipe userdata. Do 'fastboot oem unlock-go"). Maybe because in my case I had already unencrypted userdata at point of re-testing the script, it was working for me. Hence, I will fix the script by replacing "fastboot flashing unlock" to "fastboot oem unlock-go" to see if it fixes the issue for you.

---------- Post added at 02:25 PM ---------- Previous post was at 02:21 PM ----------

I've updated the script, please re-download install.bat
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] nnlife82:
Thx dude, trying it.:fingers-crossed:

ps I just tried instruction 1 . When it told me to enter the pin after reboot, I did, but it says it's wrong. Can't boot, so reflashing now:silly: My phone is absurd lol
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Before you did the instruction 1 attempt, one of pre-recs was that your device had already pin setup (Settings > Security > Screen lock > PIN), did you have it? As the only use case I am aware of this situation is if you didn't have pin setup before. It would still ask you for pin, but it does't exist, hence wrong.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] nnlife82:
Tried the modified installed.bat. Unlocked successfully, now this:

https://imgur.com/a/IxLHp1G

Stops at waiting for device.

https://imgur.com/a/MFDJCPs

The phone rebooted as data-wiped. I turned on the developer option and saw this.

Any idea..?

Thx for help!

-------update------------------------------------------

I closed the cmd and re-ran install.bat. Now it shows:

rebooting into bootloader...

OKAY [ 0.013s]

finished. total time: 0.014s

error: cannot load '.\patched_boot.img'

"Errors encountered during execution. Exited with status: 1"

Start Time: 0:05:49.23

Finish Time: 0:06:11.19

"Press any key to exit..."
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Second screenshot is expected - nothing to worry about.

First screenshot - when it is waiting for device do you see on phone screen "powered by Android"? (This means that device was able to reboot into bootloader). Anyway, maybe it needed "fastboot flashing unlock" as well, I've updated install.bat, please re-download and try again.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] nnlife82:
Thanks for keeping me up dude.

Latest error:

error: cannot load '.\patched_boot.img'

"Errors encountered during execution. Exited with status: 1"

(with new install.bat)

ps the first screenshot--while waiting for device, the phone had itself rebooted into system, as a data-wiped phone. Not in fastboot mode though.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HvMES:
Missing file patched_boot.img

Hi, when I run the script it tells me missing patched_boot.img, can you add this to the download?

This is when I run the script:

"=============================================================="

"| TWRP & Rooting script for Yota 3+ 8.1 by vvinjj 2019.02.02 |"

"=============================================================="

You about to flash your device to Y3 plus v8.1, all data will be lost. Are you sure?[Y/N]:Y

List of devices attached

f261e007 recovery

"Rebooting into bootloader... Please wait!"

Waiting for 0 seconds, press CTRL+C to quit ...

f261e007 fastboot

"Ensuring the bootloader is unlocked..."

OKAY [ 0.000s]

Finished. Total time: 0.000s

"Rebooting into bootloader to apply unlock. Please wait!"

rebooting into bootloader OKAY [ 0.016s]

Finished. Total time: 0.016s

Waiting for 0 seconds, press CTRL+C to quit ...

Sending 'boot' (12331 KB) OKAY [ 0.313s]

Writing 'boot' OKAY [ 0.109s]

Finished. Total time: 0.454s

Invalid sparse file format at header magic
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Looks like I forgot to upload patched_boot.img, please re-download it and try again.

---------- Post added at 04:47 PM ---------- Previous post was at 04:46 PM ----------

Done

---------- Post added at 04:58 PM ---------- Previous post was at 04:47 PM ----------

I've uploaded patched_boot.img. Regarding, "Invalid sparse file format at header magic" message - it is expected, just ignore it and script should continue.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HvMES:
Still a error se the script responce.

Waiting for 0 seconds, press CTRL+C to quit ...

"Remounting system rw..."

Mounted '/system'

Done processing script file

Done processing script file

command is: 'sideload' and there is no value

Starting ADB sideload feature...

Waiting for 0 seconds, press CTRL+C to quit ...

"Installing Yota updates and root. Don't panic if progress percentage is stuck, you can see the actual sideload progress in twrp."

Total xfer: 1.00x

Waiting for 0 seconds, press CTRL+C to quit ...

adb: error: cannot stat '.\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip': No such file or directory

"Errors encountered during execution. Exited with status: 1"

Start Time: 18:01:14.05

Finish Time: 18:13:11.26

"Press any key to exit..."

Press any key to continue . . .

---------- Post added at 06:22 PM ---------- Previous post was at 06:17 PM ----------

Hi I updated my Y3 to Y3+, do I need first to run all update's and then use this script or do I just run this script after the install from Y3 to Y3+.

I need to root this updated Y3+ to restore my IMEI, I lost it after the update Y3 to Y3+

Thanks for all the help.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
You can run this script on Y3+ regardless of installed updates (so just run this script).

Regarding, the:

adb: error: cannot stat '.\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip': No such file or directory

I identified that it was working for me because I had those files on my external sd_card in root folder, hence twrp could automatically map them, when executing this command.

Give me a moment to fix it, I'll let you know soon.

---------- Post added at 05:58 PM ---------- Previous post was at 05:40 PM ----------

Fixed, please re-download install.bat again and try again.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] nnlife82:
Succeed here. :good:

But the wifi hotspot is dead. You think it's a bug?

https://imgur.com/a/gUtGO90
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HvMES:
Sorry still this error: adb: error: cannot stat '.\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip': No such file or directory

"Errors encountered during execution. Exited with status: 1"
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Works for me, try reboot the device again
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HvMES:
Still having some errors:

Waiting for 0 seconds, press CTRL+C to quit ...

.\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip: 1 file pushed. 6.9 MB/s (3994882 bytes in 0.554s)

Unable to locate zip file 'Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip'.

Installing zip file 'Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip'

Checking for Digest file...

Skipping Digest check: no Digest file found

Failed to map file 'Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip'

Error installing zip file 'Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip'

Done processing script file

adb: error: failed to copy '.\Magisk-v18.0.zip' to '/data/media/0/': remote Is a directory

.\Magisk-v18.0.zip: 0 files pushed. 11.5 MB/s (196584 bytes in 0.016s)

"Errors encountered during execution. Exited with status: 1"

Start Time: 19:31:36.40

Finish Time: 19:43:42.13

"Press any key to exit..."

Press any key to continue . . .

I will install from scratch and run the script to see if it will work then.

Thanks for all the help, I will let you know how it went.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Stange, according to [MENTION=9724037]nnlife82[/MENTION] user succeeded.

Can you ensure you've replaced the install.bat by opening it with text editor and check if file contains: call adb push .\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip /data/media/0 || goto :error

If yes, then the alternative method is to install these two zip files manually through twrp:

Go to your PC > This PC > mido > Internal Storage > copy there Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip and Magisk-v18.0.zip

In TWRP > Install button > sdcard > click on Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip and Magisk-v18.0.zip > Add more Zips > click on Magisk-v18.0.zip > Swipe to confirm Flash > Reboot System

---------- Post added at 07:02 PM ---------- Previous post was at 06:58 PM ----------

Ah I see, /data/media/0/ should be /data/media/0, I've updated the script
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HvMES:
Sorry still having this error even with the new script;

Waiting for 0 seconds, press CTRL+C to quit ...

.\Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip: 1 file pushed. 6.6 MB/s (3994882 bytes in 0.574s)

Unable to locate zip file 'Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip'.

Installing zip file 'Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip'

Checking for Digest file...

Skipping Digest check: no Digest file found

Failed to map file 'Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip'

Error installing zip file 'Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip'

Done processing script file

.\Magisk-v18.0.zip: 1 file pushed. 6.4 MB/s (4188255 bytes in 0.624s)

Unable to locate zip file 'Magisk-v18.0.zip'.

Installing zip file 'Magisk-v18.0.zip'

Checking for Digest file...

Skipping Digest check: no Digest file found

Failed to map file 'Magisk-v18.0.zip'

Error installing zip file 'Magisk-v18.0.zip'

Done processing script file

Waiting for 0 seconds, press CTRL+C to quit ...

Downloading 'boot.img' OKAY [ 0.305s]

booting OKAY [ 0.687s]

Finished. Total time: 0.994s

"Re-installation is done. Setup you phone. Connect to Wifi."

"As soon as you are on home screen browse your e-ink screen at least once, otherwise the OS might crash after ~ 5-10 minutes due to inability to properly access its launcher."

"Once done. Reboot your device."

Start Time: 20:21:01.28

Finish Time: 20:33:11.20

"Press any key to exit..."

Press any key to continue . . .

After booting only the YotaPhone 3+ is showing but not booting.

I hope you can solve this, thanks for all you already have done.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
According to your log it was unable to properly install those two zip files. I will re-execute install.bat myself without sdcard installed to see if I get same error. Will let you know soon.

---------- Post added at 10:44 PM ---------- Previous post was at 10:12 PM ----------

Confirmed, turns out without sdcard the /data/media/0 location is not working, when re-executing install.bat fully from scratch. Hence, I've changed the script to point to /data instead, which works (re-tested myself again by fully re-executing the install.bat). I've updated install.bat once again please re-download and try again. Note, you can boot into TWRP recovery by holding power + vol up and re-execute the script once booted into TWRP.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HvMES:
It is working, nice.

Thank you.

I have one question, my /dev/block/mmcblk0p17 is empty I have also a Y3+ 128 original WW version and when I copy the /dev/block/mmcblk0p17 from this phone with Partition backup and restore it to the upgraded Y3 to Y3+ it is still empty.

I copy'd it as a mmclblk0p17.img.

When I restore it to the Y3+ 64 upgraded it still is empty with the program Partition backup restored .

Any help is well come.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Not sure if I fully understand your problem. So, I had a look on mmcblk0p17 and it is referring to fsg partition which is according to some google threads are generally related to modem 3g/4g staff. I have Y3 64GB Chinese version phone which I updated to Y3+. So I checked mine, made a .img backup and if to open it with notepad, then it is just filled with NULL chars, it's size is 1,572,864 bytes (1.5 MB) . I shared it in same link: mega.nz/#F!yMBGBYIY!24gGnv0DXNhqBvE7IbrEmA in backup folder. Both Wifi and 3g/4g works on my device, is it not on yours?
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HvMES:
Hi thanks, I have your backup also restored and it is still all 00, I use HEX Editor to look in to the file. With Hex Editor I can fill the file but it will take me days to enter all the info it needs to have, and no error in the file else it will not work.

This file is for the Radio but it refuse to be restored even if I give it all rights 777 it is still not working to restore it.

I have renamed it and then did a restore but it is not restoring the correct name back or even overwrite it.

/dev/block/mmcblk0p1 is OK

/dev/block/mmcblk0p13 is OK

/dev/block/mmcblk0p14 is OK

/dev/block/mmcblk0p17 is all 00's

Wifi is working, only the IMEI 1 and IMEI are Unknown.

I have try all utilities like including WriteDualIMEI(W+G_eMMC).exeWriteDualIMEI(W+G_eMMC), EFS backup, Partitions backup, FW-ddumper to backup and restore this partition but none is working.

If you have any help how to solve this?

Thanks
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HvMES:
Hi sorry it did not work, it looks like it is always NULL and will not update the IMEI.

It looks as if there is a Database where all information is stored but this is not with the correct values. I will look how to get this information and try to restore it so I can use the phone.

Is there a bootloader.img for the YotaPhone 3+ 64GB?

Thanks for all the help.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] hanguyen1589:
help me

Can you help me backup the QCN file to support imei backup? thank you very much

email: hanguyen1589@gmail.com
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] wording95:
Hello, I am new to this thread. I want to say I just bought my yotaphone 3+ global and just received it in the mail. Now, here is my situation. It appears I have the old version of Yota 3+ where is hasn't updated yet. I'm attmepting to root my phone. Will updating ruin my ability to root?? I've heard the update is pretty undesirable. Can anybody tell me what I should and shouldn't do with this? I don't want to ruin it immediately. I want to root it so I can remove most of the google bloatware. I really don't care for google. Then I'm going to put F-droid on there and try to remove any back doors if possible. Any help is appreciated. I'm in school and work 12 hours a day so I have very little time to do any research. :( Help is appreciated
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Dirkifiz:
Hi vvinjj,

at first thanks for your big efforts to this all!

Unfortunatly I am not getting it to work.

setup :

It is an original Yota 3+ 128 GB , with two SIM cards installed and no SD card.

Computer is Windows 10, ADB and drivers working.

USB debugging and OEM unlocking is enabled.

After first run of the install.bat the phone was deleted and booted again like it was first start.

But the installation of the install.bat didn't run through.

So if I now re-run the install.bat it happens like this :

Then the phone is in the bootloader , showing "powered by android" and nothing else.

When being in this state , re running the install.bat will not find the phone.

So I have to reboot , and it happens the same again as above.

I tried to POWER & VOL UP to get into TWRP as you suggested,

but then comes a lying droid , saying "no command" which probably means that TWRP isn't installed.

Can you please give me a clue, what to do now ?

Thank you in advance !

Greetings

Dirk
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Dirkifiz:
Dear vvinjj,

after trying, the Yota 3+ is rooted now and boots normally.

But now there are 2 main issues :

- WLAN can't be switched on. The slider will flip back to "off"

- the fingerprint- sensor doesn't work anymore

both worked flawlessly before, and I have re-booted several time without success.

Do you have any hint on that ?

Thanks in advance

Dirk
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
This is really strange, as I hear this for the first time. There might be couple of reasons of why this happened and might be not easy to troubleshoot. Also, fingerprint and wlan issues might be related or might be not.

1. Your hardware of the phone wlan / fingerprint might be different, hence the provided drivers are not compatible. I bought mine Y3 from China (Chinese version) about a year ago and upgraded to Y3+ . You will need to do some research to investigate if hardware ids are same or different. If hardware is available / accessible from shell console. If it is different, then you will need to replace vendor.img and possibly system.img provided in download src with compatible ones (OS 8.1), hopefully available somewhere online. You can compare them by file size.

2. Something could go during upgrade process, I suggest to try again and ensure you each step is precisely followed. Re-flashing process is same as upgrade process, just follow same steps.

3. Have a look online if any users faced similar issues during Yota upgrade, that might give you a hint.

4. Try alternative Y3 re-flashing methods available online.

Sorry not providing nothing specific as each step takes tremendous amount of time to investigate, and experimenting through trial and error.

Good luck!
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Dirkifiz:
Dear vvinjj,

Thank you very much for your fast and detailed reply.

I will go through your suggested steps and hopefully get it back to working state.

Thanks again and Greetings

dirk
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] timmerricks:
yota3+ root/TWRP my journey

I had a problem when I first tried to install root/twrp. It had barely started when it finished, leaving my Yota 3+ (upgraded from china Yota3) in a boot loop. I managed, by holding power and volume + buttons to get it to dead android figure. Then by pressing power and volume up buttons again into the basic android recovery where I tried to do a clear cache and reset to factory settings. It did something at the bottom of the screen but not very much just a couple of lines. So I then tried the reboot setting but no luck, straight back into the boot loop. So I got it out of that again power and volume+ buttons dead android (or at least very unwell). I can't quite remember my exact next step I might have pressed power and vol+ again to get it into the android recovery screen. I plugged it into my pc, it recognised the device so I flashed the boot image from the 3+ upgrade rom that was still on my hard drive ''fastboot flash boot boot.img'' from the folder with the boot image in it. I then tried rebooting it but this time nothing just a blank screen it was dead.

Then by pressing all 3 buttons at the same time and holding them until the computer made the connection sounds put it in to EDL mode where I flashed the Yota 3+ rom (I still have all the drivers files on my pc do not get rid of them just in case, they should work on both the 3 and 3+ varieties as they are the same phone). It booted up into the new phone set up and it eventualy after a while saw my wifi. I set it up, developer options, usb debugging, allow boot loader to be unlocked etc.

So this time over usb from my computer I sent the command to unlock the boot loader something like ''fastboot bootloader oem_unlock'' there are other variations of the unlock command that are easily found. Back in the developer options in the settings menu the allow bootloader to be unlocked option is grayed out with the message boot loader is already unlocked. Then I went back to my yota 3+ root/TWRP folder and, fingers crossed, clicked the install command. Hurray!! the install went through without a hitch although in the set up it did take a while to find my wifi. I had left it 2 or 3 minutes and decided to skip it but when I clicked next it showed it, I entered the password it connected no problem.

Sorry to have been so long winded, I didn't mean to be but one thing lead to another. Many thanks to all the experts who spent so much time on it even a amateur like me got there in the end, so once again MANY THANKS the yota 3+ lives on rooted and booted. Make sure you set up a pin only in the security part of the settings something like 1234 just in case.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HomerJ917:
Hi,

today I tried the first instruction to root my Yotaphone 3 (Yota 3+ Update 54). But when i make the following steps, the phone reboots and ask me for pin. The phone dont accept the pin that I set before I start.

The following steps I try:

- Get new9008-0112.zip from: https://xdaforums.com/yot...-news-t3862999 Is this the right img for the Update 54, too??

- Extract new9008-0112.zip > copy boot.img to your phone

- Boot.img is copied to phone

- Install Magisk. : https://xdaforums.com/app...mless-t3473445

- Open Magisk > Install > Patch Boot Image File > direct to copied boot.img > It will generate a file > Close

- Copy created patched_boot.img from device Downloads to your PC:

Magisk generate a "magisk_patched.img" not a "patched_boot.img" -> maybe because of the new Version (19)??

- Copy patched_boot.img from phone to pc

- Run cmd on pc from place where you copied file > adb reboot bootloader > fastboot boot patched_boot.img

adb reboot bootloader

Now, I can not execute the "adb reboot bootloader" command, because the phone immediately reboots after "fastboot boot patched_boot.img". And after the reboot the phone ask for the pin. The phone doesnt accept my pin :(.

After shutdown the phone, it starts normal, of course without root.

Am I must to flash the boot image? I mean am I must to call: "fastboot flash boot patched_boot.img"? Is it a problem if the phone is encrypted?

Thx to everyone who can help!

Greetings