Related
Introduction
The purpose of this guide is to provide you with step-by-step instructions on how to unlock the bootloader on your Nvidia Shield.
Why Would I want to Unlock my Bootloader?
Unlocking your bootloader allows you to modify all aspects of your device to suite your needs which includes but is not limited to, installing custom Recovery images such as Clockworkmod Recovery or Team Win Recovery Project, installing custom ROM's, custom Kernels, as well as other MOD's and patches.
Will Unlocking my Bootloader Void my Warranty?
Warning: Unlocking your Nvidia Shield's bootloader will void the warranty, please note that even if you re-lock the bootloader the bootloader still show a flag that the device is voided for warranty.
This warning being given please also see this post by JordanKeyes regarding warranty information as it relates to hardware issues or hardware failures.
Unlocking your Bootloader
1. Backup everything on your device that you don't want to loose such any apps (And there respective data), pictures, videos, music, etc. as unlocking your devices bootloader will erase all data on the device. You can fully backup your devices contents without root using ADB's backup command or by using the Holo Backup Tool.
2. Download and install the ADB and Fastboot drivers for your Shield, the drivers can be downloaded here. You can also follow along with wwjoshdew's excellent video tutorial on how to properly install the ADB and Fastboot drivers for your Shield on Windows.
3. Make sure you have ADB and Fastboot setup and installed on your computer. If you haven't already setup and installed ADB and Fastboot a simple ADB and Fastboot installer can be downloaded from here.
4. Fully power off your Shield by long pressing on the Power button until the power menu appears, then select the "Power off" option.
5. Boot your Shield into Fastboot mode using one of the following ways:
5. A. Power on your Shield while simultaneously holding the Power button + Back button + Home button. Release the buttons once the Fastboot bootloader screen appears.
5. B. Run the following ADB command from a command prompt window (USB cable must already be connected from your Shield to your Computer):
Code:
adb reboot bootloader
6.Now that you are at the Fastboot bootloader screen, connect your Shield to your computer using your USB cable. Make sure that your USB cable is plugged into a USB 2.0 port directly connected to your motherboard as sometimes USB 3.0 ports can cause problems and front panel USB connections can be unreliable.
7. Open up a command prompt window (cmd) in the directory where installed ADB and Fastboot to. For example if I installed ADB and Fastboot to a folder on my Desktop which is on my D: drive I would open a command window in "D:\Desktop\Fastboot_ADB".
8. From the command prompt windows enter the following command:
Code:
fastboot devices
If you device is detected and it shows your devices serial number you are ready to move on to the next step. If no device is shown make sure you have the correctly installed the ADB and Fastboot drivers from step number 2.
9. Now that your device is detected by Fastboot the following command is used to unlock your bootloader:
Code:
fastboot oem unlock
10. You will now be presented with the bootloader unlock menu. After reading the disclaimer, use the Back button and the Home button to navigate to the "Unlock" option. Once the "Unlock" option has been highlighted use the Shield button to confirm your selection of unlocking your bootloader. It's important to remember that unlocking the bootloader will wipe all your data from the device, and that a flag showing your warranty is void will appear at the bootloader screen.
11. Once your bootloader has finished being unlocked, you will be taken back to the fastboot bootloader screen. From here you can power off your Shield.
Re-locking your Bootloader
To re-lock your bootloader you can following steps 4-8 of the procedure listed above and when you come to step 9 run the following command instead of "fastboot oem unlock":
Code:
fastboot oem lock
The above command will re-lock your Shield's bootloader. Note: As previously mentioned re-locking your Shield's bootloader will not restore your warranty or remove the warranty void flag on your device's bootloader.
Conclusion
Now that you have successfully unlocked the bootloader on your Nvidia Shield you are free to flash custom Recoveries, ROM's, Kernel's, MOD's etc. enjoy :good:.
If you are stuck with the bootloader unlocking procedure I would recommend checking out this great video tutorial by wwjoshdew.
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Edit: followed the instructions in the following video and all is dandy now. http://www.youtube.com/watch?v=XSisjVwcPbE&hd=1
themichael said:
I'm having an issue unlocking the bootloader. I have the drivers and fastboot install successfully as well as adb and fastboot. I run the command "adb reboot bootloader" which reboots my shield into bootloader but when I run "fastboot devices" nothing shows up. USB debugging is enabled.
When the device is booted normally the command "adb devices" picks up the device. It is only in fastboot that adb commands aren't recognized.
I added a picture, any thoughts?
Click to expand...
Click to collapse
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
fastboot error
chevyowner said:
Look in device manager and check if the PC recognizes the shield as an adb device when in fastboot.
For me i have to switch between using fastboot and being able to copy files to it.
Click to expand...
Click to collapse
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
gogul1 said:
Hi i am having issue with dab and fast boot drivers.
When I install the driver as adb I can't fast boot to install the thor.img but once it reboots It reverts or reinstalls a shield driver and causes confusion and blocks when I want to mount.
Click to expand...
Click to collapse
Nvidia just released a new set of USB drivers in their Tegra for Android Development Pack which you can download from here. I would recommend installing the development pack and the drivers it includes.
ok
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
gogul1 said:
I have done it and these are the new drivers I have under device manager.
Still can't mount though, operation not permitted Usb debugging enabled.
here are the two new drivers which let me get as far as the mount command but no further
View attachment 2210144
and here's it telling me no in abd and fastboot
View attachment 2210148
Click to expand...
Click to collapse
From that pic you posted the mount command failed because you were not root.
chevyowner said:
From that pic you posted the mount command failed because you were not root.
Click to expand...
Click to collapse
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
shimp208 said:
I have updated the original post in my manual rooting procedure thread that includes a new insecure boot.img that has a patched adbd binary to allow the insecure boot.img to provide a root shell when booted from.
Click to expand...
Click to collapse
Huh??????????
EDIT
Were you trying to answer this post
chevyowner said:
Huh??????????
EDIT
Were you trying to answer this post
Click to expand...
Click to collapse
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
shimp208 said:
Oh what I meant chevyowner was since you had responded to that guy's post about him not having a root shell after booting the insecure boot.img I decided to jump in and mention I had updated the original post to include a new updated insecure boot.img that should fix his root shell problem. Sorry for any confusion I caused there buddy!
Click to expand...
Click to collapse
No problem.
I had to change to oil in my car in a parking lot earlier because it was cheaper to change it then it would have been add 3-4 quarts and change it when I got home. My car need 5 quarts of oil. I was not in a a good mood then.
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
thx. works nice.
wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: [
How To Root the Nvidia Shield: []
Click to expand...
Click to collapse
Sweet thanks
wwjoshdew said:
I made two videos on the NVIDIA Shield. Please let me know what you think @shimp208.
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Click to expand...
Click to collapse
I tried another proggie to root and got jammed up.. following the videos josh did had me rooted in minutes. Great job and thanks!
why?
Code:
C:\Users\Thomas>fastboot oem unlock
...
FAILED (command write failed (Unknown error))
finished. total time: 0.582s
I tried it with the Shield RAM tool, but won't work either..
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
mr.dude5660 said:
so, i managed to root and install custom recovery without touching the bootloader. the status still reads as locked, but i am free to mod and install custom roms and such. i used towelroot apk. and flashify to flash the recovery image.
Click to expand...
Click to collapse
Where did you find the towelroot apk? Been searching for over a month with no success.
Sent from my VS980 4G using Tapatalk
BTW, bootloader mode on the tablet:
- Hold "Volume Down" -> Press "Power" and continue to hold "Volume Down" until device boots into bootloader mode.
There is no home or back button to press while the device is off.
Sorry for bump this thread, but i have to.
I want to unlock my bootloader to revert back into KK and then try to do a clean installation of LP. Reading this guide and watching the videos, and also looking into the img downloaded from nvidia, it says i have to install the fastboot drivers. The problem is that i have already installed fastboot and adb drivers since i have some other devices as a Xperia and stuff. For me, there is no Yellow sign as shown in the video, my device is recognized as Portable Device and it already says "Shield Tablet" MTP.
I've tried going into bootloader to see if it prompts any new devices but i got nothing. adb devices show my device, but i'm not sure if i need more.
Went through the Guide, however i've run into roadblocks.
i've installed all sdk packages, adb commands work, and fastboot commands return serial numbers. however once i run fastboot flashing unlock, there is a thread run in command promp window, with no change in the device's bootloader screen.
i've done the 6.0.1 update, the bootloader screen reads (some important ?) console NULL; device is LOCKED; download mode DISABLED; CONNECT USB DATA CABLE (while plugged in)
usb debugging is enabled, and the OEM unlock option is checked.
Any advice is appreciated.
Is it necessary to use this method? Won't something like Nexus Root Toolkit work too? Just a thought, I may be way off
gman88667733 said:
Is it necessary to use this method? Won't something like Nexus Root Toolkit work too? Just a thought, I may be way off
Click to expand...
Click to collapse
Haven't seen this mentioned before, but im new to this forum. Will defiantly try later if nothing else works
well it worked with unlocking, when rooting flashing twrp, i sucesfully flashed .zips in twrp, then stuck in bootloop. downlownloading the recovery to fix bootloop, any suggestions on how to succesfully root without BL using nexus root toolkit?
AlPoo said:
Went through the Guide, however i've run into roadblocks.
i've installed all sdk packages, adb commands work, and fastboot commands return serial numbers. however once i run fastboot flashing unlock, there is a thread run in command promp window, with no change in the device's bootloader screen.
i've done the 6.0.1 update, the bootloader screen reads (some important ?) console NULL; device is LOCKED; download mode DISABLED; CONNECT USB DATA CABLE (while plugged in)
usb debugging is enabled, and the OEM unlock option is checked.
Any advice is appreciated.
Click to expand...
Click to collapse
When you issue the "fastboot flashing unlock" command does it return a huge list of compatible commands? If so, your adb/fastboot is out of date.
Have you enabled bootloader unlocking in developer options?
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable
I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.
SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553
Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .
I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse
bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.
After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.
MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:
MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.
fastboot flash boot_a/boot_b yourTWRP.img
The above command worked for me. Use boot_a or boot_b depending on what you have. In addition use a separate type C cable to your PC instead of stock type C cable and remove all USB accessories plugged in the PC. I know its crazy but working with this phone may require you to do some unexplainable stuff.
MackHoncho said:
I'm a noob but a respectful one. I'm embarrassed to have to post in this forum asking for help on what should be such a simple problem but I'm three days and 500 google searches closer to insanity.
I just want to install TWRP on my Essential Android which I bought from Best Buy but activated on T-Mobile.:
Product - Mata
Variant - Openus
Bootloader Version - mata-84f7cce
Baseband Version - 2.0.c4.M2.0.3
Secure Boot - yes
Device State - unlocked
I've installed ADB and fastboot on my computer and made it system wide using the PATH variable in Windows 10 Pro System Properties "Environment Variables"
I have all the proper Windows usb drivers from the Essential website and I have activated Developer Options, OEM unlocking and USB Debugging on my phone. I've removed the pin so the device doesn't lock.
I'm using the original USB C cable from Essential plugged directly into my new HP all n one USB C slot.
I've copied the twrp image and pasted it into C:\ADB\ along with my minimum adb\fastboot install. I then opened a powershell there. Both the "adb devices" and "fastboot devices" commands show my phone is being recognized and that I am indeed in FastBoot Mode.
I originally left the twrp image name as downloaded: "twrp-mata_2" but when "fastboot flash recovery C:\ADB\twrp-mata_2" resulted in "error: cannot load 'C:\ADB\recovery.img': No such file or directory"
I renamed it and ran the command:
"fastboot flash recovery C:\ADB\recovery.img"
Same error.
Please help
Click to expand...
Click to collapse
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP
TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.
droidstyle said:
TWRP-Mata_11.img is what you should be flashing and you have to flash it via fastboot Everytime you want to enter twrp. Then you have to flash a stock boot.img Everytime you reboot the system from twrp.
Click to expand...
Click to collapse
I am semi new to this community, so I am unsure if it's doing this because I am rooted or not but I've got twrp permanently installed... So from my understanding Slot a can hold your os and slot b basically hold your twrp you just need to remember when you need to switch back.... How I installed was fast booted twrp to slot a, then in twrc switched to slot b to install rom, then switch back to slot a and did a reboot to recovery... Boots into twrp, I switched back to slot b to flash gapps, then restart system... Once inside os and everything is set up if you are rooting reboot to bootloader and flash the patched boot. Img with fastboot on pc... Then reboot system... Now when you want to use twrp all you have to do is reboot bootloader, fastboot to switch to slot a, and then boot recovery... Then Twrp will load then switch to slot b and you are good to go!
barteringram said:
There is no recovery partition on the device.
To flash TWRP, you'll need to fastboot flash boot, then boot to recovery from fastboot on your device. Once in TWRP, you'll need to flash a boot image before restart. TWRP isn't persistent, so you'll have to do this every time.
Unless you're looking for a custom ROM, the easiest way to root is just to patch a stock boot image with magisk and flash it from fastboot.
Click to expand...
Click to collapse
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise
A_Pac1 said:
You should try using a Type-C to USB cable, I ran into the same issue trying to flash mine using supplied cable, once I tried the USB to Type-C it worked. :good:
Click to expand...
Click to collapse
Worth a try I guess but I am maintaining a solid connect to my PC and all other commands seem flawless. My problem has evolved now. I have installed twrp but now the touchscreen wont work.
rignfool said:
Stop the presses!
Please do not use that old ass version of TWRP...
Many many fixes since then...
Please read and familiarize yourself with
http://mata.readthedocs.io/en/latest/
And also realize that you will not ever have persistent TWRP
Click to expand...
Click to collapse
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?
MackHoncho said:
You might have just solved my newly evolved issue (got twrp installed but now touchscreen doesn't work)
Will get on it and let you know.
Quick question; What do you mean twrp is not persistent? Does that mean I have to install it and install magisk and whatever rom from twrp on the first shot before rebooting? At what point does twrp disappear?
What other pitfall, tips or tricks should I be aware of?
Click to expand...
Click to collapse
It's not persistent as in it won't survive the flashing of the stock boot.img.
MackHoncho said:
Thank you in advance for answering about three questions as of yet forthcoming... done this b4? lol
BTW, yes, I intend to install magisk, root and AOSip 8.1.
Anyway, I got past the original problem, kinda.
My problem arose from having too many adb installations in too many places on my windows machine.
I deleted everything, installed a single instance, put everything in a single folder on my desktop, opened a windows powershell there and then adb/powershell was able to find the twrp file.
Next problem was a "no such partition" error which was solved by a google search and specifying the slot location in the flash command.
NOW I have twrp recovery installed but the touchscreen doesn't work so its useless. AAAAAARRRRGHH!
Should I post a new thread or is this still OP?
I'm still in the same boat as my goal is a working TWRP recovery....
please advise
Click to expand...
Click to collapse
I had the same issue with using an older version of Mata TWRP... You need to install TWRP-MATA_11
Solved
My Windows 10 machine isnt set to show file extensions.
was trying to fastboot twrp-11 as I named it; recovery.img
fastboot wanted recovery.img.img
please laugh hardily
aer0zer0 said:
@barteringram is right, no recovery partition.
Your command needed is this.
Fastboot flash boot whateveryounamedtwrp.img.
Click to expand...
Click to collapse
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!
vonstarr said:
Thank you, thank you, THANK YOU!! You would not believe how long I've been trying to solve this problem! Now I can get on with tweaking and personalizing my Oneplus 6T!
Click to expand...
Click to collapse
So op6t is easier (I just bought one)
Fastboot boot nameoftwrp.img
It'll boot twrp without flashing it to the phone. Makes life easier. Mata doesn't have this option.
This guide worked for every OREO version, and also is working for PIE ! :good:
You will enable camera2 on your phone, and keep it stock afterwards so it can receive future OTA updates. :victory:
1 - Unlocking bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
First of all, enable the Developer Option.
To do this go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled”.
Now go back to settings -> Enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging.
Now connect the phone with your USB cable, use USB port 2.0 on your computer.
It should appear on your phone screen an asking for access privileges of your PC (device, maybe Linux), allow it.
Download ADB if you don't have it.
https://drive.google.com/file/d/1yCdMyAAOD46T4B8haFuZVF57E4-WK8l2/view?usp=sharing
In ADB folder, double click "Open CMD here.bat".
AND FROM THIS TIME, YOU DON'T CLOSE THIS CMD AT ALL, UNTILL YOU FINISH THE WHOLE GUIDE
Code:
adb devices
Your device should appear with some random numbers like this
https://www.howtogeek.com/wp-content/uploads/2012/10/image34.png
If it does, go to next stage, if it's not, you are not installed usb drivers corectly or did not enabled usb debugging.
Link for USB Drivers for Mi A2.
http://dl.adbdriver.com/upload/adbdriver.zip
Code:
adb reboot bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
Code:
fastboot oem unlock
Phone will reboot, go to check developer options > usb debugging ON once again.
Code:
adb reboot bootloader
Again in fastboot we are unlocking critical partitions, and once again it will erase verything from the phone, so be sure to do the backup as needed.
Code:
fastboot flashing unlock_critical
Again when the phone reboot, check developer options > usb debugging ON.
2. Rooting the phone (temporarily)
Download stock boot and patched boot of android version you have, if you need versions for OREO, find somewhere in forum, here it is link for PIE.
10.0.9.0 https://drive.google.com/drive/folders/1ZP5jelFGT5z9EJvHRokzLJwAikKtWI8p?usp=sharing
10.0.8.0 https://drive.google.com/drive/folders/1XNE_veO_FvOLQ46oorUBa2g7TKA1PHRv?usp=sharing
10.0.7.0 https://drive.google.com/drive/folders/1kHLYXhaWFpjh58F79xnOkN3kjkuyEdHV?usp=sharing
10.0.5.0 https://drive.google.com/drive/folders/1qCIsk1MVVq_X-mR8BBWa2NeVLB_-4q5y?usp=sharing
10.0.4.0 https://drive.google.com/drive/folders/1piLD_9mQv0XgahyIZdxRqfdwaDbfx2_0?usp=sharing
10.0.3.0 https://drive.google.com/open?id=1uO3yfxHdTr4gv4DmCaLu-naIIt8mprBT
"It seems like 10.0.3.0 OTA is withdrawn by Xiaomi due to numerous bootloops in stock phones."
My recommendation is to skip flashing this version, until next stable comes up !
10.0.2.0 https://drive.google.com/drive/folders/1_cIM0ltKD_PU1mIiWwUE-nMba964NyvN?usp=sharing
10.0.1.0 https://drive.google.com/drive/folders/18tcBVaKwH9cy_RVczf-GSc_tAkFYvn15?usp=sharing
9.6.17.0 https://drive.google.com/drive/folders/1D9RlDZRupdriCyJM4p0ixvntPE2QPP9w?usp=sharing
Put the files in adb folder, both the stock boot.img and patched_boot.img.
NOW !
There are two methods, so you can choose between those two:
1. Faster and easier one with only booting patched boot
2. Slower with flashing, but this one will teach you how to flash and root your phone
1. ENABLING WITH BOOTING PATCHED_BOOT.IMG
In CMD type
Code:
adb reboot bootloader
Code:
fastboot boot patched_boot.img
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, just skip it, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop persist.camera.HAL3.enabled 1
For PIE and for using v6 Gcam ports three more commands, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3.enabled 1
Code:
setprop persist.camera.stats.test 5
Code:
setprop persist.vendor.camera.stats.test 5
Press ctrl+c to exit adb shell (windows) or just type "exit" and again "exit"
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, and the phone should start normaly without Magisk installed, and with camera2 enabled, because nothing was flashed, you are DONE !
2. ENABLING WITH FLASHING PATCHED_BOOT.IMG
In CMD type
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
Then when you see your active partition, flash the patched image.
Code:
fastboot flash boot_a patched_boot.img
OR if it was b partition active
Code:
fastboot flash boot_b patched_boot.img
Code:
fastboot reboot
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, just skip it, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop persist.camera.HAL3.enabled 1
For PIE and for using v6 Gcam ports three more commands, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3.enabled 1
Code:
setprop persist.camera.stats.test 5
Code:
setprop persist.vendor.camera.stats.test 5
Press ctrl+c to exit adb shell (windows) or just type "exit" and again "exit"
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, prepare and hold down the volume button when phone restarts, your phone will go into fastboot.
Type the command for active partition
Code:
fastboot getvar current-slot
Code:
fastboot flash boot_a boot.img
Or
Code:
fastboot flash boot_b boot.img
Code:
fastboot reboot
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
If you're using temp recovery, just fastboot boot patched_boot.img, no need to flash, and once done just reboot
if i flash boot.img back i get stuck in android one screen
idriff said:
if i flash boot.img back i get stuck in android one screen
Click to expand...
Click to collapse
On what android version were you ?
pie, i just flashed back the modified boot and it worked but now im rooted
What version google camera you guys using?
minnuss said:
This guide worked for every OREO version, and also is working for PIE ! :good:
You will enable camera2 on your phone, and keep it stock afterwards so it can receive future OTA updates. :victory:
1 - Unlocking bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
First of all, enable the Developer Option.
To do this go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled”.
Now go back to settings -> Enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging.
Now connect the phone with your USB cable, use USB port 2.0 on your computer.
It should appear on your phone screen an asking for access privileges of your PC (device, maybe Linux), allow it.
Download ADB if you don't have it.
https://drive.google.com/file/d/1yCdMyAAOD46T4B8haFuZVF57E4-WK8l2/view?usp=sharing
In ADB folder, double click "Open CMD here.bat".
AND FROM THIS TIME, YOU DON'T CLOSE THIS CMD AT ALL, UNTILL YOU FINISH THE WHOLE GUIDE
Code:
adb devices
Your device should appear with some random numbers like this
https://www.howtogeek.com/wp-content/uploads/2012/10/image34.png
If it does, go to next stage, if it's not, you are not installed usb drivers corectly or did not enabled usb debugging.
Code:
adb reboot bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
Code:
fastboot oem unlock
Phone will reboot, go to check developer options > usb debugging ON once again.
Code:
adb reboot bootloader
Again in fastboot we are unlocking critical partitions, and once again it will erase verything from the phone, so be sure to do the backup as needed.
Code:
fastboot flashing unlock_critical
Again when the phone reboot, check developer options > usb debugging ON.
2. Rooting the phone (temporarily)
Download stock boot and patched boot of android version you have, if you need versions for OREO, find somewhere in forum, here it is link for PIE.
https://drive.google.com/drive/folders/18tcBVaKwH9cy_RVczf-GSc_tAkFYvn15?usp=sharing
Put the files in adb folder, both the stock boot.img and patched_boot.img.
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
Then when you see your active partition, flash the patched image.
Code:
fastboot flash boot_a patched_boot.img
OR if it was b partition active
Code:
fastboot flash boot_b patched_boot.img
Code:
fastboot reboot
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, let him do it, install full zip, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop.persist.camera.HAL3.enabled 1
For PIE one more command, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3 enabled 1
Press ctrl+c to exit adb shell.
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, prepare and hold down the volume button when phone restarts, your phone will go into fastboot.
Type the command for active partition
Code:
fastboot getvar current-slot
Code:
fastboot flash boot_a boot.img
Or
Code:
fastboot flash boot_b boot.img
Code:
fastboot reboot
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
Click to expand...
Click to collapse
For me it worked, but in stock camera cant see any diferences, can someone link me a gcam apk to install?
minnuss said:
This guide worked for every OREO version, and also is working for PIE ! :good:
You will enable camera2 on your phone, and keep it stock afterwards so it can receive future OTA updates. :victory:
1 - Unlocking bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
First of all, enable the Developer Option.
To do this go to your Settings -> About -> Software Information -> More -> Now Tap on the Build Number 7-8 Times until you see a toast message “Developer option enabled”.
Now go back to settings -> Enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging.
Now connect the phone with your USB cable, use USB port 2.0 on your computer.
It should appear on your phone screen an asking for access privileges of your PC (device, maybe Linux), allow it.
Download ADB if you don't have it.
https://drive.google.com/file/d/1yCdMyAAOD46T4B8haFuZVF57E4-WK8l2/view?usp=sharing
In ADB folder, double click "Open CMD here.bat".
AND FROM THIS TIME, YOU DON'T CLOSE THIS CMD AT ALL, UNTILL YOU FINISH THE WHOLE GUIDE
Code:
adb devices
Your device should appear with some random numbers like this
https://www.howtogeek.com/wp-content/uploads/2012/10/image34.png
If it does, go to next stage, if it's not, you are not installed usb drivers corectly or did not enabled usb debugging.
Code:
adb reboot bootloader
Unlocking bootloader, this command will delete/reset your phone, so do backup of files as needed.
Code:
fastboot oem unlock
Phone will reboot, go to check developer options > usb debugging ON once again.
Code:
adb reboot bootloader
Again in fastboot we are unlocking critical partitions, and once again it will erase verything from the phone, so be sure to do the backup as needed.
Code:
fastboot flashing unlock_critical
Again when the phone reboot, check developer options > usb debugging ON.
2. Rooting the phone (temporarily)
Download stock boot and patched boot of android version you have, if you need versions for OREO, find somewhere in forum, here it is link for PIE.
https://drive.google.com/drive/folders/18tcBVaKwH9cy_RVczf-GSc_tAkFYvn15?usp=sharing
Put the files in adb folder, both the stock boot.img and patched_boot.img.
Code:
adb reboot bootloader
Code:
fastboot getvar current-slot
Then when you see your active partition, flash the patched image.
Code:
fastboot flash boot_a patched_boot.img
OR if it was b partition active
Code:
fastboot flash boot_b patched_boot.img
Code:
fastboot reboot
When the phone starts, wait for magisk to appear in apps, or if it's not there, find it in apkmirror site, magisk manager, download, install from phone it is easier.
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=magisk+manager
Then when you start magisk, it will ask you to download full zip, let him do it, install full zip, your phone will now be rooted.
3. Enabling Camera2 api (lvl3)
In CMD type
Code:
adb shell
Code:
su
(this time look at the phone screen, allow root access ONCE)
Code:
setprop.persist.camera.HAL3.enabled 1
For PIE one more command, for OREO it is not needed.
Code:
setprop persist.vendor.camera.HAL3 enabled 1
Press ctrl+c to exit adb shell.
4. Unrooting the phone
Start magisk again, go to UNINSTALL, choose full uninstall, magisk will reboot the phone in process of uninstalling, prepare and hold down the volume button when phone restarts, your phone will go into fastboot.
Type the command for active partition
Code:
fastboot getvar current-slot
Code:
fastboot flash boot_a boot.img
Or
Code:
fastboot flash boot_b boot.img
Code:
fastboot reboot
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
Click to expand...
Click to collapse
The post has some errors but I'm here to report you guys how I made it work.
adb devices
adb reboot bootloader
(I had the bootloader unlocked already so I didn't do those steps)
fastboot boot patched_boot.img
(Notice I didn't flash the patched image, you don't need to do that, my current partition was b, but that doesn't matter since I'm not flashing anything, I am just booting into the patched/rooted image)
(Installed magisk manager and rootchecker)
(magisk said it was rooted, so did root checker)
adb shell
su
(I gave the permission on my phone)
setprop persist.camera.HAL3.enabled 1
(If you check the post carefully, this line above is not the same one the OP has, that one is wrong, mine is right)
setprop persist.vendor.camera.HAL3.enabled 1
ctrl+c
adb reboot
(Notice I don't flash anything here as well, since I didn't flash the patched image, so if I reboot, it will boot into my stock boot image)
aaaaaaand it's done.
Thanks to the OP for his work, and please correct the line that is wrong. Cheers. :angel:
Google Camera working fine.
Jamesismo said:
The post has some errors but I'm here to report you guys how I made it work...
Click to expand...
Click to collapse
Hello, thanks a lot!
It's works perfect!
Best regards!!!
hugomoya said:
Hello, thanks a lot!
It's works perfect!
Best regards!!!
Click to expand...
Click to collapse
Please don't quote OP for a single line of comment.
@Jamesismo, thanx, I fixed the typo mistake, did not have the DOT in command line, it was not an error, just a typo, but thanx.
And yes, please guys, do not quote the first post.
In a guide, a neewbie can learn how to unlock bootloader, root the phone, enable cam2, and unroot the phone.
So he can choose, whether he wants to stay with rooted phone or not, or to unroot later if he wants...
I think that with this method, OTA will work even if he has Magisk installed, because nothing is changed in system, but that needs to be confirmed.
I noticed that many people want to lock the bootloader to recieve OTA. It is unnecessary you still receive OTA with an unlocked bootloader provided you have not changed the system folder etc.
Hey @minnuss good job! glad to see this.
I would change one thing i noticed: "Press ctrl+c to exit adb shell."
That's a Windows thing, doesn't work with Linux or Mac. Most people 'should' know how to exit a command prompt, but if not, safer to just say type 'exit' and hit enter. That works on all of the systems.
Cheers
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:[/QUOTE]
If may i ask what version of Gcam you recommend? I've tried
Arnova's v8.3b1 and the front facing camera doesn't work on photo mode, but work on video.
Thanks
@minnuss Hey bro, the post does still have a typo, after "setprop" there must be a space, not a dot. (First line)
---------- Post added at 06:09 PM ---------- Previous post was at 05:57 PM ----------
afajri said:
This is it guys, you have enabled lvl3 (camera2), and unrooted phone, ready for next OTA updates.
Install camera2 probe from gplay to confirm.
https://play.google.com/store/apps/details?id=de.weis.camera2probe&hl=en
Phone needs to stay with unlocked bootloader, because if you lock the phone, you will lose camera2, but do not worry, the future OTA updates will work.
If this guide helped you, please click the thanks button, that's all, cheers. :highfive:
Click to expand...
Click to collapse
If may i ask what version of Gcam you recommend? I've tried
Arnova's v8.3b1 and the front facing camera doesn't work on photo mode, but work on video.
Thanks[/QUOTE]
It does work in protrait mode 5mpx, and if you change it from 5mpx to 3mpx, normal selfie works as well.
@[email protected]
@AsItLies
@kishd
@Jamesismo
@afajri
Fix for front cam on Arnova 8.3b1 > go to settings > developer settings > camera.enable_micro UNCHECK (all the way down in developer settings)
Back, back, exit, remove cam from memory, restart the cam...done ! :fingers-crossed::good::laugh:
The google camera APK that I've used in oreo does not work in Pie. Any new suggestions? With night sight preferably! Thanks
@hugopg
There is no version 6 gcam mod that works for our PIE, but you can use this, it works nice, and do the fix for front cam, just a post up from this.
Arnova's v8.3b1: GCam-5.1.018-Pixel2Mod-Arnova8G2-V8.3b1.apk
minnuss said:
@[email protected]
@AsItLies
@kishd
@Jamesismo
@afajri
Fix for front cam on Arnova 8.3b1 > go to settings > developer settings > camera.enable_micro UNCHECK (all the way down in developer settings)
Back, back, exit, remove cam from memory, restart the cam...done ! :fingers-crossed::good::laugh:
Click to expand...
Click to collapse
Works perfectly!
setprop persist.camera.stats.test 5
According to a newly added thread this command makes the gcam 6 version work on pie.What specifically does this command do? The OP of the said thread didnt know.