Related
Hello to all,
i've been trying since 1 week now to root an Ulefone Armor 8, but it doesn't work. All drivers are installed. The OS installed on the device is Android 10, the build version is X70WSFFB.GQU.EEA.FHJ.Q0.TJAPA9VDYPTS.0703.V3.01. I have already contacted Ulefone and asked if there is another build version (for EU), but it is the only one currently available.
In the firmware there are two boot.img. One is called "boot.img" and the other is called "boot-debug-img". First I only patched the "boot.img" with Magisk and flashed the patched "magisk-patched.img" via ADB. After that the Armor 8 had a bootloop. The bootloop could be removed by flashing the original "boot.img" via ADB. The Armor started normally again.
After that I patched the "boot.img" and the "boot-debug.img" with Magisk and renamed them to "magisk-patched1.img" and "magisk-patched2.img". After that I flashed first the " magisk-patched1.img" and then the " magisk-patched2.img" via ADB. The Armor 8 then had a boot loop again. To get the bootloop away, the original "boot.img" was flashed back and Armor 8 is back in its factory default state.
How can it be rooted, what should I do differently? Could it be because there are two "boot" files in the firmware?
Sorry if my english is not perfect.
Thanks for your help and tips.
Greetings
https://www.getdroidtips.com/root-ulefone-armor-8/
I have tried that too, but it doesn' t work.
I flashed the "boot.img" with Magisk, from this Magisk created the file "patched_magisk.img". I moved this file to the ADB folder. After that I did it again with the file "boot-debug.img". Then I put the armor in fastboot mode and first I entered the command "fastboot flash boot_a magisk_patched.img".
ADB writes: writing 'boot_ a'... FAILED (remote: This partition doesn't exist)
After that I still moved the patched "boot-debug.img" into the ADB folder and entered the command "fastboot flash boot_b magisk_patched.img".
ADB writes: writing 'boot_b'... FAILED (status read failed (Too many links))
Magisk didn't create 2 patched files from 1 "boot.img", but in the unpacked ROM there are 2 .img files, namely "boot.img" and "boot-debug.img", which I patched one after the other and then flashed.
I have also downloaded the firmware of Armor 7. Of course not to install it, just to see if there are 2 boot.img (= boot.img + boot-debug.img) in it, too. For Armor 7 there is only 1 file "boot.img". For Armor 8 in the firmware there are "boot.img" and "boot-debug.img"
I have now tried overall:
just flash the patched "boot.img" = bootloop
flash only the patched "boot-debug.img" = bootloop
then first the patched "boot.img" and then the patched "boot-debug.img" = bootloop
Now just now again with the command "fastboot flash boot_a magisk_patched.img" = error message and then continue with the command "fastboot flash boot_b magisk_patched.img" = error message.
I think the problem is that there are 2x boot.img files in the ROM?
Edit:
And the SP-Flash-Tool shows that I should remove the battery, but the Armor has a fixed battery.
The SP Flash Tool now works after reinstalling the Vcom driver.
I have now extracted the boot.img of Armor 8 with the SP Flash Tool via "Readback". This file was then patched with Magisk. The file "magisk_patched.img" is together with the file boot.img in the same folder.
This was then flashed to the Armor with the SP Flash Tool in "Download only" mode. The flashing process is running normally and finally "Download Ok".
After that the Armor 8 will start normally and without bootloop, but it still has no root.
Does anyone have an idea?
I also have an armor 8 and I noticed that when u enter developer mode u can unlock the bootloader from there. Which allows you to install root access more successfully
after tapping on the kernel build go back and enter the option where it says system. There u will find the developer options.
after that, I had to follow some steps from this video
I got the stock ROM from the Ulefone website https://www.ulefone.com/support/software-download.html
where I was able to get the boot.img and patch it with magisk however I kept on getting a boot loop so I'll probably figure out another way to root it
1st
2nd
ignore
Have you succeeded yet? I am interested in this phone but want to be sure it can be rooted
Instead of trying to patch it from fastboot, just try booting! Follow the instructions below.
You may want to try the following steps: Just ignore the part about using their rom since it is a different phone. You should be using the Ulefone ROM
[Guide] Install Magisk on your device, updated to handle OTAs easily
[Update in 1st September 2018] Magisk v17 stable has been released, so the August security update: a new method, more OTA-compliant, is written. Hi all, this section is quite gaunt, so I'll post my experience on unlocking and rooting my brand...
forum.xda-developers.com
So save you some clicking, I'll just paste the relevant part below:
How to root
0. You need "debug usb" and "oem unlock" enabled under "developer options" on phone's settings.
1. First, if you don't have already done it, unlock phone's bootloader:
Code:
adb reboot bootloader
fastboot oem unlock
ATTENTION: THIS WILL WIPE YOUR DEVICE, ALL USER DATA WILL BE LOST! And no, when you'll have finish this guide, you can't lock it again (each lock-unlock operation will wipe the device)
2. Download ROM system image from official site. Pay attention to download the corresponding version of your actual OS (look in system settings your current build number).
3. Extract "boot.img" from the just downloaded archive and put somewhere in your device (e.g. in a microSD, just remember where you put it).
4. Download and install Magisk Manager apk.
5. Open Magisk, choosing "yes" when it asks to install Magisk-v*.zip, then choose "patch boot image" and select "boot.img" copied in step 3.
6. At the end of patching process, Magisk will tell you where "patched_boot.img" is been stored, keep a note on it and close.
Now's the updated part, that will make possible to apply OTAs:
7. Copy "patched_boot.img" on your computer, then run this on a terminal:
Code:
adb reboot bootloader
fastboot boot patched_boot.img
fastboot reboot
This will temporarily give you root privileges (until next reboot).
8. Magisk Manager can now make the root permanent: open it and tap "Install", then "direct install (recommended)". This way (instead of flashing directly patched_boot.img) Magisk Manager can remove and reinstall root privileges directly.
9. Just to be sure that your phone doesn't install updates without your acknowledgement, go to Developer Options and disable "Automatic system updates".
Ta-dà! Now you should have Magisk permanently installed (you can check it re-opening Magisk Manager).
-------------------------------------------------------
Time to update? Here's how
If you've followed what is written above, applying an OTA should be quite easy now.
a. Go to Magisk Manager → Uninstall → Restore Images. Do not reboot now or you will have Magisk uninstalled!
b. Now go to Settings → System → System Update and apply OTA. If it fails you've some tweak on system partition that you've forgot to remove, so try to figure it out and retry. Wait for the installation to complete. DO NOT RESTART NOW.
c. Open Magisk Manager again and press Install → Install to Inactive Slot.
d. Reboot and enjoy
-----------------------
PLEASE ADVISE IF THIS WORKS!
As the guy clearly mentioned, there's a boot.img and a debug_boot.img whenever i try to patch any of that and use fastboot to flash it I only get a bootloop
The bootloader is already unlocked and there's nothing else I can do to get this phone rooted
There's also no twrp currently supported for.it and that's pretty much it
I just needed help with this but it seems like this phone is very unknown and unsupported
MasDbs101 said:
As the guy clearly mentioned, there's a boot.img and a debug_boot.img whenever i try to patch any of that and use fastboot to flash it I only get a bootloop
The bootloader is already unlocked and there's nothing else I can do to get this phone rooted
There's also no twrp currently supported for.it and that's pretty much it
I just needed help with this but it seems like this phone is very unknown and unsupported
Click to expand...
Click to collapse
Have you explicitly tried
fastboot BOOT patched_boot.img
just BOOTING the patched boot image. just ignoring the the flash command for now.
This shouldn't cause a bootloop since it'll just revert back to the virgin boot.img
TWRP isn't needed for rooting.
Thank you for sharing this , I will try it later today and let you know what happens.
MasDbs101 said:
Thank you for sharing this , I will try it later today and let you know what happens.
Click to expand...
Click to collapse
Any luck?
stizarch said:
Any luck?
Click to expand...
Click to collapse
Bootloop
Finally, I successfully rooted! Procedure is the same as in the post 7, but before flashing patched boot you should flash empty vbmeta image:
fastboot flash vbmeta vbmeta_null.img
and then:
fastboot flash boot boot_magisk_patched_root.img
and reboot to system:
fastboot reboot
I attached empty vbmeta and patched boot.
knedlyk said:
Finally, I successfully rooted! Procedure is the same as in the post 7, but before flashing patched boot you should flash empty vbmeta image:
fastboot flash vbmeta vbmeta_null.img
and then:
fastboot flash boot boot_magisk_patched_root.img
and reboot to system:
fastboot reboot
I attached empty vbmeta and patched boot.
Click to expand...
Click to collapse
how did you get a null vbmeta file i need one for the ulefone armor 10 5g i wonder if its just empty it will work or something will try
zenoblank34 said:
how did you get a null vbmeta file i need one for the ulefone armor 10 5g i wonder if its just empty it will work or something will try
Click to expand...
Click to collapse
yes flashing vbmeta null over vbmeta on ulefone armor 10 5g worked as well i got root access
Armor8 said:
Hello to all,
i've been trying since 1 week now to root an Ulefone Armor 8, but it doesn't work. All drivers are installed. The OS installed on the device is Android 10, the build version is X70WSFFB.GQU.EEA.FHJ.Q0.TJAPA9VDYPTS.0703.V3.01. I have already contacted Ulefone and asked if there is another build version (for EU), but it is the only one currently available.
In the firmware there are two boot.img. One is called "boot.img" and the other is called "boot-debug-img". First I only patched the "boot.img" with Magisk and flashed the patched "magisk-patched.img" via ADB. After that the Armor 8 had a bootloop. The bootloop could be removed by flashing the original "boot.img" via ADB. The Armor started normally again.
After that I patched the "boot.img" and the "boot-debug.img" with Magisk and renamed them to "magisk-patched1.img" and "magisk-patched2.img". After that I flashed first the " magisk-patched1.img" and then the " magisk-patched2.img" via ADB. The Armor 8 then had a boot loop again. To get the bootloop away, the original "boot.img" was flashed back and Armor 8 is back in its factory default state.
How can it be rooted, what should I do differently? Could it be because there are two "boot" files in the firmware?
Sorry if my english is not perfect.
Thanks for your help and tips.
Greetings
Click to expand...
Click to collapse
Hello I tried but I fail ..
I install all drivers..
But when
Adb reboot bootloader .. rebooted..ok
Fastboot oem unlock ... Waiting for device...
So I cannot unlock the bootloader
have you tried
fastboot flashing oem
or
fastboot flash oem
zenoblank34 said:
have you tried
fastboot flashing oem
or
fastboot flash oem
Click to expand...
Click to collapse
Only work for me
adb reboot bootloader
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock
fastboot -i 0x0E8D flash boot magisk_patched.img
fastboot -i 0x0E8D flash vbmeta vbmeta_null.img
fastboot -i 0x0E8D reboot
rebooting...
Thanks people, it worked for me.
Can you tell me how much time do you need to fully charge from 0 to 100% ?
And do you use charger from box?
PabloWalker13 said:
Only work for me
adb reboot bootloader
fastboot -i 0x0E8D devices
fastboot -i 0x0E8D flashing unlock
fastboot -i 0x0E8D flash boot magisk_patched.img
fastboot -i 0x0E8D flash vbmeta vbmeta_null.img
fastboot -i 0x0E8D reboot
rebooting...
Click to expand...
Click to collapse
What does it mean the code 0x0E8D?
I'm trying to root an Oukitel WP12 with Magisk.
I've downloaded the firmware from the vendor's link and flashed it successfully just like for other Oukitel phones (WP6, WP10).
I could also create a magisk-patched boot image. I followed regular practices: unlocked the bootloader, confirmed by orange state message and flashed the patched boot image.
The phone gets into a boot loop.
This phone differs significantly from other Oukitel phones I saw before. It comes with Android 11 by default, moreover: the device is an A/B device.
Also: apart from vbmeta, it also has vbmeta_system and vbmeta_vendor. I tried flashing a blank vbmeta for vbmeta first and than to all three vbmeta partitions without success.
Anyone came accross with a phone with vbmeta, vbmeta_system and vbmeta_vendor partitions? How I should correctly create blank vbmetas for these partitions?
Note that there's also a boot-debug partition and for several partitions there are partitions with a -verified suffix, like: dtbo-verified, tee-verified, etc.
I think it's probably the wrong vbmeta blanks I'm using causing the boot-loop. Flashing the original images restores the phone - although without magisk root of course...
If you have any ideas or instructions on how to overcome this obstacle, please let me know.
Thanks: Dw.
Unfortunately I can confirm the boot loop. I don't have a solution for now, if you have one, please share!
Hi @Dwokfur,
Finally I managed to root my Oukitel WP12. The recpie you posted is OK, you should only re-flash also the Verified Boot partitions with the proper fastboot flags.
WARNING: the vbmeta* partitions I downloaded from the phone were different from the ones found into the Oukitel firmware zip archive: So I used the one extracted from the phone with the SP Flash Tool v5 program.
After all the final fastboot recipe is:
Code:
fastboot flash boot_a magisk_patched-23000_rgkOP.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_a.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system_a.img
fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor_a.img
wrong thread, ignore, sorry.
Would anyone be able to direct me or send me the proper information on how to root my OnePlus 9 global LE2115? Because their are to many threads and Im getting confused
You can either use boot.img or you can boot into twrp and flash magisk.apk. 2 options for A11
I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help
xLLALLOx said:
I have issues rooting LE2115_11_C.44 (Lastest update android 12)
I try patched with Magisk:
fastboot boot boot.img
and that's ok, device is rooted, but when reboot my device don't keep root, so I try:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
and device go into loop in bootloader then I rolled back flashing stock boot.img
I tried install TWRP from https://dl.twrp.me/lemonadep/ using
fastboot boot twrp.img
The TWRP logo appear and next show "Qualcomm crush dump mode"
I need help
Click to expand...
Click to collapse
A12 root method is different. Not like A11 where you flash the patched boot.img,it won't work. VBmeta and a vendor.img is used also. Also, TWRP is for A11. If you want root,Use the tool here: https://forum.xda-developers.com/t/...xyysds-root-toolbox-coloros-oxygenos.4341167/
Use option 5 and then 6 and reboot. Magisk will be installed. Click the magisk app and update it.
Note: use your phone to download and extract file with password that OP provides in the link
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img.
Most of the time the below command does not work and causes bootloop, when Installing Custom recovery.
So i searched a lot and found the perfect solution which is working 100% and tested personally.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
The errors we receive while flashing this command is due to SDK platform tools version
30.0.5 version is working fine and i have attached it along with this post so nobody else will go through the searching i have went.
This is the whole sole purpose of this thread.
Can you tell me how to do it with Heimdall on Linux? Using this file attached below, but i also ask you, is this file i posted only special for my device? The guy who told me to flash this told me to use odin and place the file on ap slot, just like how i previously flashed the custom recovery.
hi ,may i ask which first, do i need to flash the vbmeta before custom rom?. thanks much appreciated
Luffy83 said:
hi ,may i ask which first, do i need to flash the vbmeta before custom rom?. thanks much appreciated
Click to expand...
Click to collapse
Recovery, VBMETA (if required), Rom, (Microg if you want, i never recommend), and magisk root if you wanna root.
SignatureBoy said:
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img.
Most of the time the below command does not work and causes bootloop, when Installing Custom recovery.
So i searched a lot and found the perfect solution which is working 100% and tested personally.
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
The errors we receive while flashing this command is due to SDK platform tools version
30.0.5 version is working fine and i have attached it along with this post so nobody else will go through the searching i have went.
This is the whole sole purpose of this thread.
Click to expand...
Click to collapse
can also be wrote this way : fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
This is a very important post.
I am currently having poco m2, and previously I tried flashing costom recovery but everytime got stucked into boot loop, so what should I do, regarding vbmeta, anyone can help - which step should I follow to flash costom rom and vemeta + for fixing bootloop issue in Xiaomi phone , do we have to flash vbmeta
Vedant2 said:
I am currently having poco m2, and previously I tried flashing costom recovery but everytime got stucked into boot loop, so what should I do, regarding vbmeta, anyone can help - which step should I follow to flash costom rom and vemeta + for fixing bootloop issue in Xiaomi phone , do we have to flash vbmeta
Click to expand...
Click to collapse
Are you sure your custom recovery works for your phone? You need to flash vbmeta to get rid of the AVB verification steps, otherwise you end up with a non-booting system because of the differences in keys built in to the hardware, the system partition and the boot partition.
Can anyone tell me, i am having poco m2 Xiaomi , what's the use of vbmeta and is it compulsory to flash vbmeta while flashing custom rom or recovery.
Just used the latest adb tools on cmd admin. Fixed
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
Has the full rom been released yet?
arsalturtle891 said:
Has the full rom been released yet?
Click to expand...
Click to collapse
No, at least on Oxygen Updater. Are you on F20 and you want to root?
TheNewHEROBRINE said:
No, at least on Oxygen Updater. Are you on F20 and you want to root?
Click to expand...
Click to collapse
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being
arsalturtle891 said:
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being
Click to expand...
Click to collapse
When you rooted did you do fastboot flash or fastboot boot and then direct install in Magisk app?
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
Then you can't restore your original boot image from Magisk. You should only ever do fastboot boot and then use direct install in Magisk. Unfortunately the latest full rom available for your device is LE2115_11_F.17, so I think your only chance is that someone share a stock F18 boot image so that you can flash it and then update.
arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
Appreciate it!
shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
I'm not seeing the attachment
Here is the stock unrooted F.18 boot.img. Make sure to extract it first.
So I was able to remove root by first following the same commands I used to root in the first place with the boot image you provided. However, I cannot update to F20 using the system update. It keeps failing
Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.
shadabkiani said:
Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.
Click to expand...
Click to collapse
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?
arsalturtle891 said:
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?
Click to expand...
Click to collapse
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?
shadabkiani said:
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?
Click to expand...
Click to collapse
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"
arsalturtle891 said:
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"
Click to expand...
Click to collapse
Why do you always "fastboot boot......" and then "fastboot flash boot...."?
Generally, fastboot boot.... will make you phone boot up the given image temporarily (whether it's a boot image or a bootable recovery image). Whereas, fastboot flash boot.... will permanently flash the given image. Normally, you only have to go with one of these methods depending on your task/goal.
Anyway, since you have flashed the stock unrooted boot.img and OTA is still failing, I suggest you just back up your personal data (photos, stuff) to PC or whatever, and then go with the MSM tool method. It will wipe all your data on phone, and revert your phone to OOS11 with locked bootloader. From there, you can take OTA updates all the way upto OOS13 F.20. This seems to be the simpler way to get out of your current predicament.
How to use MSM tool:
1. Download the package according to your device/variant, and extract it.
2. Power off your phone and keep it aside. DO NOT connect your phone to PC for now.
3. Run the MSM tool exe. It will take a couple of minutes to load.
4. Click on Target drop-down menu and choose O2 if you are on Global.
5. Click Start. It will go to Waiting for Device mode.
6. Now on your phone (which should already be powered off), press & hold both the vol+ and vol- buttons (NOT the power button) and connect the data cable from PC to your phone. Your phone's screen will still stay black and it will enter EDL mode.
7. The MSM tool will start flashing as soon as the connection is successful.
Note: You need to have OnePlus device drivers on PC.
I appreciate the support. Can you also provide me with the F20 boot image by any chance.
Sure. Stock unrooted F.20 boot.img attached. Make sure to unzip it.
By the way, if you have MSM tool, you can get your current boot.img from its readback feature. Super simple. Launch MSM tool. Press F8. Select the desired boot image (boot_a or boot_b). Enter the password as: oneplus. Click read. Power off phone, and get it into EDL mode by pressing holding vol- vol+ buttons then connecting data cable from PC. The desired boot.img will be dumped in C: drive.
Also, F.21 has just been released, so you better update to that. I haven't yet as I am currently on crDroid.
Anyway, F.20 boot has been attached.
Hello sir Can I get F.21 boot
vendor boot
dtbo
there're no FULL package out there for Global variant
Just only incremental update
How can I get that Full Image?
Or Should I extract it from India Variant Full Image F.21
will It work normally?