yashsingh1/xdaforums huggingface dataset:
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] timmerricks:
homer j917

I think you should enter '' adb reboot bootloader>fastboot boot Magisk_patched.img'' only. I don't think the adb reboot bootloader on the next line is part of the command as it is not in bold. I am not an expert. It's worth a try. Also that is what it shows in the image.

Ignore the above text I misunderstood your problem. Did you have the security pin set before you made the patched boot image, just a thought
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
I updated instruction broken screenshot link, I hope it will clarify the step.

Anyway, based on your comment the steps should be:

Enter in cmd:

adb reboot bootloader

It will reboot your device into bootloader mode, then enter in cmd:

fastboot boot magisk_patched.img

It will boot the magisk patched image, then continue accordingly to instructions to complete the remaining steps.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HomerJ917:
Hi,

thanks for the fast reply.

This steps work for me this was not the problem.

- Device pin is enabled (Settings > Security & location > Screen lock > PIN) -> Set the PIN "1234" in the security setting.

- adb reboot bootloader -> ok!

- fastboot boot magisk_patched.img -> ok!

The Problem is, that after reboot the phone ask me for PIN. When I type inside "1234" the phone say "wrong PIN". I try this several times with PIN and Password, no difference.

Some member have had the same problem, but I dont know the status of this case.

It looks like this have something to do with the encrypted filesystem on Android 8.1 and the Update 54. Do you have had this Update when you root your device?

Can I use the boot.img file from this thread (includes the Update 54)?

https://xdaforums.com/showpost.php?p=79596295&postcount=233

Greetings
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
I did this long time ago, so don't remember if I already had update 54 installed. My phone was already encrypted before proceeding with root instructions as it is getting automatically enabled on fresh OS install.

Troubleshooting:

- Your device should have pin already enabled, before creating magisk_patched.img, if not then re-create it and re-try;

- You can try magisk patching boot.img from url you mentioned or take it from mine Mega url, from ota_update-Y3-54_patched_as_YT.zip they should be same; This should not harm your OS in anyway as you just trying to boot it, not flash.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HomerJ917:
Thanks for the help, but it doesn't work. The phone always ask after reboot for PIN but never accept my PIN. I try with boot.img from the link and from you, I always set the PIN before creating patched boot img.

Maybe a problem with magisk, do you know how to install your version (18)? I dont see an offer in magisk manager to install old version from a zip file , I only can install the version 19. I dont have another idea what can be the problem.

Greetings.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
- I don't believe this is something to do with version of magisk, but you can try to download it from: github.com/topjohnwu/Magisk/releases/tag/manager-v6.1.0

- I've came up with instruction 1 after I performed the upgrade from Y3 to Y3+:

xdaforums.com/yotaphone-3/development/yota-3-firmware-news-t3862999, and then used the included boot.img from there and installed 53, 54 updates. You could do the same re-installation flow, but at this point instruction 1 becomes more complex then instruction 2.

- In your installed magisk, in instuction 1 there are two tickboxes: Preserve force encryption, Preserve AVB 2.0/dm-verify, only first one should be ticked.

- Just to avoid potential causes of issue: Ensure your fingerprint disabled.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HomerJ917:
I cant believe, I try with different boot.img. I try with older version of Magisk (18, btw: 19 dont have the "enforce" option filed), fingerprint disabled, try with PIN and password, but no chance!! Always the wrong PIN/Password. This phone is not a Y3 -> Y3+ device, its an original Y3+. Maybe I must to "flash" the boot image, but i am affraid to stay in bootloop. Is it possible to reflash the old, not patched Boot.img file?

Greetings
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
- Don't try to flash the boot it will fail due to decryption failure (boot loop) or your PIN will be always wrong in your current situation.

- I am not sure if instruction 2 will work on original Y3+ as I heard some people had issues with wifi and fingerprint functionality (not sure if it is due to Y3 vs Y3+ device difference). I suggest to find online the original ROM for Y3+, extract it and use those files (boot.img, cache.img, mdtp.img, persist.img, splash.img, system.img, vendor.img) with my script install.bat. See it that Y3+ rom has any additional images, if yes then you will need edit the script to include them as well. No guarantees at this point that it will work, but in theory it should.

- Try to find online the alternative rooting method for Y3+

- You might try approach 3, which is partially based on instruction 2 (risky, as not tested):

1. Boot TWRP using bootloader in the same way as you trying to boot boot.img (available in mega twrp_recovery.img)

2. Format your storage partition (all your personal data will be lost)

3. Trigger factory reset, clean dalvik cache without restarting the TWRP

3. Install Magisk-v18.0.zip from TWRP (available in mega)

4. Install Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip from TWRP (available in mega)

5. Reboot TWRP into system

WARNING: before you do this, read around how TWRP works, and understand:

xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] timmerricks:
homer j917 This is what I did.

Right!!!! it is time to stop messing about. Download and install the files on to your pc for the upgrade from 3 to 3+ (it does not matter if your phone was the 3 china version or the international 3+ it is the same phone/hardware) and read the instructions carefully. It is a fire hose installation (it wipes everything no matter what). It uses the powerful software. edl mode, I had to do it more than once due to my own lack of expertise.

Once you have flashed the the phone set it up, as in unlock developer options, allow bootloader unlock,allow usb debugging etc.

From your PC adb unlock bootloader '' adb fastboot unlock bootloader oem_unlock'' . Do not install any upgrades.

Download the files for instruction 2 it will take some time on the basic download as in 3 to 6 hours for the free download. When it tells you that your download has over run it's capacity and you can't download any more for 3 hours, just leave your computer on and when the time has elapsed click on the green download circle at the bottom left of the screen. It will complete the download in about 20 minutes ish. When you have got this file unzip it to its own folder, From that folder first connrct your phone then click the install.bat and let it do its thing.

I know this all seems a bit drastic but it is what I had to do and it all worked out in the end.

good luck timmerricks.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] HomerJ917:
Thanks for the Infos. But are you sure that this is so easy and simple? E.g. I read that some people lose the IMEI configuration, and without root I am not able to backup this configuration.

Is it possible to make a full 1:1 backup of my actual firmware (like "dd")? So, I can try and roll-back if something went wrong...
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] timmerricks:
homer j917

I have read that some people lost the IMEI, I dont know why,I have just checked mine and they are there. There may be a way to make a back up of the whole system without root but I do not know of one off hand. I would try searching and see what is suggested, maybe there is a windows program that will do it. I persevered see ''my journey post above and got there in the end.

good luck
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] timmerricks:
homer j917

Come on Homerj917

What are you Man or mouse. I want to see your post, that you have grasped the nettle and gone for it. Just down load the relevant files, go over the instructions a few times, you can do it. If I can you can. Once you have flashed your phone with the 3 to 3+ which is not difficult for someone of your knowledge, just try instruction 1 if you have not down loaded the files for instruction 2 (once you have the files for instruction 2 it is so much easier) but once your have the upgrade version you should be able to root your phone either 1 or 2 smoothly with no problems,, Everyone who posts on here has had times when you just have to go for it. So come on and let us see you post your journey '

Go for it timmerricks
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] hammel66:
FAILED (remote: partition table doesnt exists) - vendor

Hi there,

sorry for my bad english ....

I have tried the second instruction with the install.bat.

I have problems to access my phone with fastboot under WIndows (bad USB driver ???) so I use Linux booted from USB (FWUL). I typed the adb and fastboot commands of the install.bat in the Linux console window.

The command "fastboot flash vendor .\vendor.img" failed with:

writing 'vendor' 1/2...

FAILED (remote: partition tabel doesn't exist)

Any idea how to fix it?

Thanks a lot....
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] timmerricks:
Hi hammel66

I am not an expert but I think the ''install.bat'' is a windows command/batch file containing a number of instructions, so linux won't recognise it.

The fastboot drivers that I got to work after quite a few failed attempts (with the message waiting for device) is a small program called Minimal ADB and fastboot I found it by googling it. Once installed connect your yotaphone 3+. I typed ''adb devices'' and it came up with my device after starting the daemon (whatever that is). Then I typed ''adb reboot bootloader'' and it rebooted the phone into fastboot mode then typed ''fastboot devices'' and (fingers crossed) hit enter. It came up with my device (hurray) instead of the waiting for devices. Then I think this is the essential part I unlocked the boot loader I think the command is ''fastboot oem unlock''.

Then ''fastboot reboot'' to get the phone back to normal. Once the bootloader was unlocked I double clicked on the ''install.bat'' and everything went through smoothly.

I hope this helps and someone with a lot more knowledge will correct me if I have gone wrong somewhere.

Good luck
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] vvinjj:
Partition problem is a bad sign, did you try to proceed with instruction on Android Yota 3 OS 7? In this case you will need to proceed first with Yota 3 to Yota 3+ upgrade:

https://xdaforums.com/yotaphone-3/development/yota-3-firmware-news-t3862999

This is required as partitions / sizes between Y3 and Y3+ are different.

Only after that, you can root Y3+ (attempt instruction 1 or 2).

Good look.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] hammel66:
Thank you very much. I upgraded with success.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] poloxu:
I'm in a catch22 position. My Yota3+ suddenly lost ability to write to the internal memory. I searched for solution and found all methods require the phone to be rooted. The instruction above requires files to be copied to the phone. Is there a way to install magisk from the computer?
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] bambi007:
Thank you for your post and your effort.

I got my Yota 3+ yesterday and used your files. Worked without any problems.

Thank you!!!
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] ahmadexp:
I am stuck on the YOTA 3+ screen after I attempted to root my phone. What are my options?
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] bambi007:
Could you be more specific? What option did you choose? Did you use the bat file? were there any errors during execution? Do you have access to TWRP?

Did unlock bootloader work?

If you are able to go into Fastboot Mode then you could try again for example.

If you can start TWRP you can start from there and flash the images like in the install.bat.

What I did was open the install.Bat in Notepad and copy pasted all instructions one after the other in the cmd-prompt to see if everything works.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] ahmadexp:
I had a problem with the install.bat at the point were it starts the TWRP and the swiping was required within the 25 sec delay. Happy to say, everything is fine now. Also with regards to the WiFi, after I went through install.bat phone started without WiFi functioning. After restarting the phone everything came up perfect. Hopefully this come helpful to someone
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Mehedi34:
I tried to follow Instruction 2. when i open "install.bat" it get stuck at "ensuring the bootloader is unlocked"... waiting for device.... Yota 3+ get stuck into "Powered by Android" screen.

Looks like i can't enter in fastboot mode or bootloader option and isn't unlocked. how to do it?

Plz help.?
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] bambi007:
ADB Debugging does work ?

If you enter : adb devices in Cmd Prompt. Does it show your mobile?

then enter: adb reboot bootloader (like in the install.bat).

Dont execute install.bat, just copy paste the commands to ensure that every step works
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Mehedi34:
[IMG="and the phone remains in this state"]https://i.imgur.com/d5Tfg8h.jpg[/IMG][IMG="cmd prompt image"]https://imgur.com/8pejPfV[/IMG]

here is the cmd prompt photo and the state of phone at that time..

my phone cant reboot into bootloader. the above screen appears when i try to enter bootloader mode? where is the problem?

thanks
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] bambi007:
Did you activate the Slider 'OEM unlocking ' in the Developer settings?
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Mehedi34:
Yes.

And can you plz tell what does bootloader mode looks like in Yota 3+? Everytime I enter into bootloader mode by power and volume button this screen appers and nothing happens.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] bambi007:
I just entered bootmode with "adb reboot bootloader"

This is the picture.

The LED is blinking red every 4 or 5 seconds.

with "fastboot devices" I get my mobile .

ANd then I check my status with this command:

fastboot oem device-info

...

(bootloader) Device tampered: false

(bootloader) Device unlocked: true

(bootloader) Device critical unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

OKAY [ 0.072s]

finished. total time: 0.084s

F:\fastboot>
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Mehedi34:
Is that the expected result?

So, what should I do now?
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] bambi007:
yes, when your bootloader is unlocked it should be like this.

So do you have bootloader mode or not? does it blink red?

if so then the command "fastboot devices" should give you your device id.

then unlock bootloader with "fastboot oem unlock"
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Mehedi34:
My Yota 3+ is rooted now?

Changed my laptop for unlocking bootloader. My old laptop was the culprit. Possibly due to decaying USB ports.

Flashed twrp.img which was included in instruction 2 file.

Flashed Magisk via twrp.

Thanks
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] nexkat:
still NO systemless root

I did the whole procedure again, this time with Magisk Manager 6.1 and Magisk v18.0 (like in the original instructions). Now the phone won't boot past the pin entry (always tells me that it's wrong).

I have to long-press the power button, then the phone reboots (and accepts my pin entry). I tried with paolinger's boot.img, and also with the boot.img I found in ota_update_Y3_54.

Has someone succesfully rooted with the system-less method? With which version of Magisk/Manager did it work?

Finally, is the pin screen lock essential, i.e. can something break when I try with the screen lock disabled?

Thanks for any hints!

EDIT: I tried with Magisk 18.1, 19.0 and 19.1 - and get always stuck at the pin entry. Just for fun I tried with the latest version 20.1 again, that gets me past the pin entry but does not give me root. magisk is somehow installed

Y3:/sbin $ ls -la
total 488
drwxr-xr-x 3 root root 280 2019-11-18 22:47 .
drwxrwxrwt 21 root root 780 1970-01-01 02:02 ..
lrwxrwxrwx 1 root root 9 2019-11-18 22:47 .core -> ./.magisk
drwxr-xr-x 6 root root 160 2019-11-18 22:47 .magisk
lrwxrwxrwx 1 root root 13 1970-01-01 02:02 charger -> /root/charger
-rwxr-xr-x 1 root root 149848 1970-01-01 02:02 magisk
lrwxrwxrwx 1 root root 8 1970-01-01 02:02 magiskhide -> ./magisk
-rwxr-xr-x 1 root root 345412 1970-01-01 02:02 magiskinit
lrwxrwxrwx 1 root root 12 1970-01-01 02:02 magiskpolicy -> ./magiskinit
lrwxrwxrwx 1 root root 8 1970-01-01 02:02 resetprop -> ./magisk
lrwxrwxrwx 1 root root 8 1970-01-01 02:02 su -> ./magisk
lrwxrwxrwx 1 root root 12 1970-01-01 02:02 supolicy -> ./magiskinit
lrwxrwxrwx 1 root root 13 1970-01-01 02:02 ueventd -> /root/ueventd
lrwxrwxrwx 1 root root 15 1970-01-01 02:02 watchdogd -> /root/watchdogd

but does not have the right permissions:

Y3:/sbin $ su
Permission denied

More info from: > fastboot oem device-info

(bootloader)	Device tampered: false

(bootloader)	Device unlocked: false

(bootloader)	Device critical unlocked: false

(bootloader)	Charger screen enabled: false

(bootloader)	Display panel:

OKAY [ 0.057s]

Finished. Total time: 0.057s

I have bootloader unlocked in the settings, but never did "fastboot oem unlock-go", since I don't want to loose my current installation.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] ngochaodoiba@gmail.com:
sorry, but.... it has error. help me pls!!!

all step done until

...

Finished. Total time: 1.214s

Sending 'recovery' (15793 KB) OKAY [ 0.431s]

Writing 'recovery' OKAY [ 0.128s]

CreateProcess failed: The system cannot find the file specified. (2)

fastboot: error: Cannot generate image for userdata

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

Start Time: 22:40:21.21

Finish Time: 22:44:59.93

"Press any key to exit..."

Press any key to continue . . .

Help me pls!!!
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Tippfehler:
I'm not sure, but I think I had the same issue and it was possible to fix it. The file was missing or the name of the file. (different Magisk-Version?)

Can you try it line by line manually?
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] ngochaodoiba@gmail.com:
i can't :eek::eek:

you say erorr by the name, so i can rename for wich file at that line error
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] Tippfehler:
I can't remember, but by executing the batch file line by line, the error was possible to fix.
[YotaPhone 3 ROMs, Kernels, Recoveries, & Other Dev] pinappxu:
In your mega files, there are boot.img and patched_boot.img. Are these files identical to those files generated from steps 2 and 5 in the first method? If I use the patched_boot.img from your mega files, can I start from step 5?
[Android Q&A, Help & Troubleshooting] scorpion-58:
My ZTE V9180 has showing No Kernel (boot partition is bad). If there is any solution please post the same.
[Xiaomi Poco F1 Questions & Answers] najjurocks619:
It's been pushed since yesterday, i wonder if anyone get hold of it?

Edit: Everyone is getting it now, Check updater.
[Xiaomi Poco F1 Questions & Answers] cediedc:
Check System Updater it's there..
[Xiaomi Poco F1 Questions & Answers] Saswata Chakraborty:
It's beta stable which mean only a handful of users will get it for testing, if I am not wrong.
[Xiaomi Poco F1 Questions & Answers] katoda_ltd:
Well, apparently I'm in this group - just got it via System Update and I'm on stable (10.1.3.0 PEJMIFI)
[Xiaomi Poco F1 Questions & Answers] najjurocks619:
Everyone Got It Now Nice Update
[Xiaomi Poco F1 Questions & Answers] georgh1991:
i can enable wifi calling now but it doesnt work though. anyone the same problem?
[Xiaomi Poco F1 Questions & Answers] TNSMANI:
Is it supported by your service provider and does your plan permit it?
[Xiaomi Poco F1 Questions & Answers] georgh1991:
of course. telekom d1 in germany... my plan supports it, for sure
[Xiaomi Poco F1 Questions & Answers] TNSMANI:
Check THIS and see if it helps.
[Xiaomi Poco F1 Questions & Answers] georgh1991:
no no.

i am on the stable 10.2.2. and want wifi calling to work without root... and i hoped it is possible with this stable now..
[Asus ZenFone Max Pro M1  Questions & Answers] Chikku@8:
Google Keeps Crashing Every 20-30 mins frequency....

I keep getting this pop-up...

I Clean flashed Stock Rom for 5-6 times

Still it exists....this is ridiculous to see...

Asus simply can't give 1 stable update....

Even fingerprint got worst in v338....

It's not that accurate doesn't recognise my finger...

I feel like I am done with Asus and their FOTA system....

They introduce new bugs with every build...

I am expecting very less from Android P by Asus...

They released it for Zenfone 5Z And Zenfone 5 and results aren't great...

They messed up with their flagship Device how will they be better on low end...

Anyways... suggest me what can I do I am annoyed. With Google app Crashing
[Asus ZenFone Max Pro M1  Questions & Answers] z1_nile:
Sell the phone if you can't solve basic problems.

In build 338 there aren't any major bugs as you are complaining and if you unlocked boot and flashed a custom os there's no point of complaining about the software. (supposing by clean flash you mean by twrp)

And for to fix Google app problem uninstall all updates and update again from play store and give all permissions also check if some other app interferes or integrates into Google app as it may cause errors.
[Asus ZenFone Max Pro M1  Questions & Answers] BetterMyself:
You need to be polite....

and you cant simply say some sell your phone if you dont know how to get basic problems done right....

havent you read rule of the forum??

respect each other

the way you are talking looks rude...aand by no means you should talk to another person in this way...

you simply could have answered it rather then asking him to sell....

and by clean flash he also may be saying complete factory data reset

or the method of getting back to stock via fastboot...

and you can visit zenfone forums...fingerprint issue is there......

if you dont face that issue it doesnt mean the build is stable...

get the basics clear mate...

be polite and respect each and every member...

peace:good:
[Asus ZenFone Max Pro M1  Questions & Answers] z1_nile:
I am always polite the op kind of angered me. The question should be Google app keeps crashing every 30 min interval, any fix?

Tried clean install (specified what action is taken)

Instead of nagging about each update, zenfone 5,5z, being done with Asus and FOTA (which made me tell the person to simply sell for peace of mind).

Still I'm sorry for my words if they offended or hurted your or op creator's feelings. I am used to see direct on point op's for everything on xda so it kinda feels wrong to me to make things go in circles instead of being short and on point.