Orea beta is great but battery drain so much.
for 30 min of screen use it used 11%, is it normal ?
and I am looking to go back to Nougat, could any one please tell me how can I go back.
Thank you.
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Yup those are them, I just did it yesterday.
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
vjyrdy said:
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Click to expand...
Click to collapse
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
swagglepuff said:
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
Click to expand...
Click to collapse
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
tech_head said:
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
Click to expand...
Click to collapse
I have ran both unlock commands successfully and still get permission denied
swagglepuff said:
I have ran both unlock commands successfully and still get permission denied
Click to expand...
Click to collapse
And you checked the OEM unlock in developer options?
Hmmmm
tech_head said:
And you checked the OEM unlock in developer options?
Hmmmm
Click to expand...
Click to collapse
The issue has something to do with Mac and the platform tools. I was able to downgrade with no problem using a friend's Windows PC.
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
trizon2016 said:
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
Click to expand...
Click to collapse
Nothing confusing about that statement for Windows, MacOS or Linux.
A command path needs to exist so that when you type the command it can be found.
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Let me link you my ingenious, allmighty Axon 7 Companion Thread.
Try to install twrp with MiFlash if you can enter edl mode
macerf said:
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Click to expand...
Click to collapse
Your phone works normally
You don't have fastboot
You have stock recovery
If this is the case then most surely you have EDL working...
Install TWRP from EDL mode:
This is taken from Controllerboy's guide
BE SURE THAT WINDOWS SHOWS FILE NAME EXTENSIONS!
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
macerf said:
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
Click to expand...
Click to collapse
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Choose an username... said:
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Click to expand...
Click to collapse
Hello and thanks for the advice. Unfortunately it does not change anything.. I have done exactly as you say but the result does not change anything...io have connected the device, Open command window, type "adb devices ", is viewed as "Cd07b2e9 device ", I type "adb reboot EDL ", it restarts in EDL, then go to management Devices and is viewed as "QUSB_BULK ", Run command "Axon7tool-r GPT boot recovery " but it says "Failed to connect ", then I'll return to Device Manager, hold volume up & Down & Power, Icon disappears and returns after a few seconds, close window and launch command "Axon7tool-r GPT boot recovery " but still give "failed to connect "...
So, recapping: I have bootloader unlocked, I can get into EDL but PC does not see device although on Device Manager it exists...
I now launch device into the wall... problem solved.
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
kitcostantino said:
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
Click to expand...
Click to collapse
Of course I'm kidding... have just purchased this device, have a great hardware but the software does not go well for nothing. I have had a dozen phones, I changed about 60 ROMs, so for me it is not difficult to change the software...ma in this case have problems. Is it possible that I fail to solve this problem? Be a way to reset everything and start from scratch? Okay, the bootloader be unlocked but not be any other way to go back? I have seen many guides but not able to solve the problem. I fail to make flash of TWRP, fail to do downgrade to MM....io hope someone help me... thanks.
are you using a USB 2.0 or 3.0 port? it may not apply to this scenario, but with Motorola and RSD Lite, I always had to use usb 2.0 ports or it wouldnt see my device when flashing.
also, the steps @choose an username listed out are the best way to start from scratch, but obviously you have to be able to have your computer see the phone in the desired mode.
@DrakenFX has several guides in the axon 7 forums that should help once the computer sees the phone as well.
I use USB 3.0 with original cable ... but if you now tell me that maybe this is my problem, then I use USB 2.0. Thank you...
Good morning...
Nothing to do... I put the original cable on USB Port 2.0, have redone procedure from window PowerShell, on command "adb devices " Everything OK, on command "adb reboot EDL " It enters EDL mode, but then all the procedures are failed... if command "Axon7tool-R recovery GPT boot "I always get out of the inscription " Failed to connect ", it remains in EDL and I just have to reboot... I replaced the drivers with Zadig 2.3 but did not change anything... are there any other moors to make flash of TWRP? exist lthough an app that do this? I remember that for LG G3 I'll fix everything with an app...
I just received a system update for build PPR1.180610.091 but I am rooted with a custom kernel.
I think it should be ok to take the system update if I restore my /boot to a stock image but I want to make sure before I take the update.
The rom is stock and has Magisk and ElementalX. Bootloader and Critical are unlocked.
Would it be ok if I restore my boot.img to the stock one and then accept the update via the system updater? or is there something else I need to do?
xNotta said:
I just received a system update for build PPR1.180610.091 but I am rooted with a custom kernel.
I think it should be ok to take the system update if I restore my /boot to a stock image but I want to make sure before I take the update.
The rom is stock and has Magisk and ElementalX. Bootloader and Critical are unlocked.
Would it be ok if I restore my boot.img to the stock one and then accept the update via the system updater? or is there something else I need to do?
Click to expand...
Click to collapse
Just reboot to stock recovery, apply update from adb, in terminal on pc, adb sideload, then drag and drop the ota zip from essential site, hit enter, it will update and u keep data
jacksummers said:
Just reboot to stock recovery, apply update from adb, in terminal on pc, adb sideload, then drag and drop the ota zip from essential site, hit enter, it will update and u keep data
Click to expand...
Click to collapse
If I sideload the Ota, do I need to flash the stock boot first?
xNotta said:
If I sideload the Ota, do I need to flash the stock boot first?
Click to expand...
Click to collapse
Nope. After the flash and reboot, u gotta re root though
jacksummers said:
Nope. After the flash and reboot, u gotta re root though
Click to expand...
Click to collapse
I just did the sideload but I got an error:
Code:
adb> adb sideload .\PH1-OTA-PPR1.180610.091.zip
opening '.\PH1-OTA-PPR1.180610.091.zip'...
connecting...
serving: '.\PH1-OTA-PPR1.180610.091.zip' (~94%) * failed to read command: No error
but the recovery said it was completed successfully. My phone booted fine and is running Pie.
Is this a normal error?
xNotta said:
I just did the sideload but I got an error:
Code:
adb> adb sideload .\PH1-OTA-PPR1.180610.091.zip
opening '.\PH1-OTA-PPR1.180610.091.zip'...
connecting...
serving: '.\PH1-OTA-PPR1.180610.091.zip' (~94%) * failed to read command: No error
but the recovery said it was completed successfully. My phone booted fine and is running Pie.
Is this a normal error?
Click to expand...
Click to collapse
I got the same error, but haven't had any issues.
I have been using this thread as my reference for how to take updates so I wanted to add some instructions and links that I found useful/necessary for completing the process.
Hopefully someone else can find this useful.
IMPORTANT! Remove screen lock pin before continuing!
TWRP will prompt for a password if you do not remove your lockscreen pin/pattern! There is no password!
This is caused due to Android encrypting the /data/ partition.
Settings > Security & Location > Device Security section > Screen Lock. Set it to None.
You can also search in settings for "Screen Lock"
Stock boot images:
https://drive.google.com/drive/folders/1iayS6YHYZvqkD1Y8oYV3ewzW5aAPe8C2
TWRP (twrp-mata_11.img) images:
https://download.invisiblek.org/mata/
Essential Phone downloads:
Download the OTA file for Sideloading
https://www.essential.com/developer/current-builds
Sideloading using stock recovery(my preferred method):
Ensure USB debugging is enabled on your Essential Phone. To do so, follow step four above.
Plug your Essential Phone into your computer with a USB cable.
Open a command window in the folder where you have ADB and fastboot installed.
In your command window, type adb devices and press enter. Your device’s serial number should appear in the command window.
If you see a notice on your phone asking if you’d like to allow USB debugging on this computer, check the box and select OK.
Reboot your phone into recovery mode. To do so, type adb reboot recovery into your command window. Your phone will reboot into recovery mode. You should see a little green bugdroid with a caution symbol. Despite your gut reaction, this is good.
Open the recovery menu on your Essential Phone. To do so, hold the power button and press the volume-up button once.
Scroll down to Apply update from ADB with your volume-down button, then press the power button to confirm.
Ensure that your phone is still being recognized by your computer. To do so, type adb devices in your command window and press enter. Your device’s serial number should appear in the window.
In your command window, type adb sideload update.zip (or whatever you named your file).
Source: https://www.androidauthority.com/how-to-install-android-p-essential-phone-863668/
Sideloading using TWRP:
Reboot your Essential Phone into Fastboot mode by restarting the phone and pressing and holding volume down and the power button at the same time. Once you’re in Fastboot mode, flash TWRP with the following ADB command: fastboot flash boot twrp.img
From within the Fastboot menu, select and boot into “recovery mode.” Once TWRP has booted up, type in: adb shell twrp sideload
Then type in: adb sideload magisk.zip
Once Magisk finishes installing completely, reboot back to Fastboot. You can do this via: adb reboot-bootloader
When you’re back in Fastboot mode, grab the modified boot.img (making sure to select the right one) and flash it via fastboot flash boot boot.img
Now reboot! You should now have root via Magisk!
Source: https://www.xda-developers.com/how-to-root-essential-phone-ph-1/
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.