********** 11/17/18 sorry to say folks, this method of enabling cam2api does not, for some reason, work with stable PIE. Looks like root is the only option now ********
**** please note, the next comment, after this guide, has some 'condensed problem solving' tips from the 10 pages of comments - if you run into problems doing the following, look at the next comment for possible solutions *****
While this might sound similar to other 'guides', it's not the same. In this guide we'll enable Cam2API, not flash anything, and not install root then later uninstall it.
And we won't do it with a 'tool', that you have no idea what it's doing behind the scenes (they have their place, but not really needed for this imho).
Also, it's not my intention to knock Magisk. It's a great rooting app, and it has a lot of additional features besides root. But when deciding to use Magisk or not, if all you want to do is enable cam2API, and use none of it's other great features, it seems like overkill to me.
Prerequisites:
1) Your version of fastboot needs to be one that recognizes 'dual slot' phones (look at the version docs if yer not sure).
2) Your device needs to be bootloader unlocked, and adb debug enabled (research that if you don't know what it means).
3) You need the latest version of Tingyichen's TWRP, which currently is twrp-3.2.3-jasmine-20181020.img
https://forum.xda-developers.com/mi-a2/development/recovery-unofficial-twrp-recovery-mi-a2-t3825146
1) Connect the device with adb, and verify it's working with 'adb devices'. Assuming it works type:
Code:
adb reboot bootloader
2) Once in fastboot (the bootloader), find out which slot is current with:
Code:
fastboot getvar current-slot
Make a note of which slot is current.
3) If the current slot is NOT 'a', then we have to set it to 'a'. Do the following to accomplish that;
Code:
fastboot set_active a
4) With the current slot set to a, do the following command:
Code:
fastboot boot twrp.img
(or the actual name of your twrp.img if you didn't rename it to twrp.img - you don't *have* to rename it, seems most people do though.)
At this point, let the device start and go into twrp. You will have to use your 'pattern' if you have one set on the phone. Also, you do NOT have to hold vol up to boot into twrp.
5) Now we'll do the 2 (or 3 if u have Pie) commands to set cam2 enabled.
Code:
adb shell
Code:
setprop persist.camera.HAL3.enabled 1
note: only do the following command for Pie or newer versions.
Code:
setprop persist.vendor.camera.HAL3.enabled 1
Code:
exit
6) Our cam2 will be enabled the next time we reboot. So lets type this:
Code:
adb reboot bootloader
7) Now, if our original active partition was b, we have to set it back to b:
Code:
fastboot set_active b
8) Lastly, we simply reboot with:
Code:
fastboot reboot
That's it, boom, done.
Side Notes:
So why does this work? After so many have indicated TWRP didn't work for them? But it did for others? Wha Up? Simple, it seems twrp isn't very dual slot smart (and why should it be? it was originally written for single slot devices - it DOES give you an option to set the other slot active when you exit it, but all that's doing is running 'set active', nothing to do with installing it).
So I just verified this morning, even though I have cam2 working. My active slot is b, and 'fastboot boot twrp' would fail (even though others said Tingy's new version worked!). So what's different? Only thing I could think of was which slot was active. The active slot changes for ea device with updates, and thus we don't all have the same active slot!
But setting it to a, then doing boot twrp, works like a champ. setprop persist commands of course work also (I verified, even though mine are set). And simply going back to fastboot and doing reboot should avoid any trace of twrp having been used (we didn't 'flash' it, only booted it).
If anyone decides to try 'fastboot boot boot_a twrp.img', that *might* work, I didn't think to try it.
Cheers
updated 11/9/18
Some people have run into issues with twrp working as needed. The following are some of the solutions that have been found:
1) Some have used PBRP instead of TWRP, **BUT** it seems the most recent version of pbrp does NOT work.
2) Some have found that booting TWRP works okay but doing the 'setprop persist' commands didn't result in cam2api being enabled.
2 a) to fix the above, they went into the 'mount' section of TWRP and disabled the MTP option. They indicated they also enabled 'persist', but it's uncertain if that made a difference. (Special thanks to @lept_2014 for that!)
For most, it seems to work just by following the guide. I'd recommend this; ea and every time you go to fastboot, or to the device with adb, always be sure that fastboot and adb can see the device before proceeding. That narrows down the problems significantly.
If 'adb devices' does not show your device in the response, the problem is your PC and usb / adb drivers.
if 'fastboot devices' does not show your device in the response, the problem is with your PC and usb / fastboot drivers.
Thanks to all of the contributors. That's a big help to everyone.
Hello, perfect for me, like a charm.
My slot: A
Thanks a lot, best regards!!
PS: I use CMD. Problems in PowerShell with "fastboot flashing unlock_critical" command.
TingyiChens latest twrp from 20181020 works on my phone in both slots a and b. It just boots twrp into the active slot. I am running the October stock 9615 rom. Currently my active slot is b after the last ota.
When the hell would xiaomi enable cam 2 api by default
kishd said:
TingyiChens latest twrp from 20181020 works on my phone in both slots a and b. It just boots twrp into the active slot. I am running the October stock 9615 rom. Currently my active slot is b after the last ota.
Click to expand...
Click to collapse
Good to know. It's confusing why some of us get 'failed'. But it does work! As you point out also. I guess we can say that if you get a failed message, try setting the other slot active. It absolutely will work.
Yes, why don't they set cam2 by default sharingan, I wish I knew. But using twrp is pretty painless, so at least we have that.
Cheers
Can some pls make video tutorial for this...pls
setprop persist.camera.eis.enable 1 there is no need to knock
Is slot a and b contains same data inside by stock?
Edit: this is my first system ab phone so be gentle please
bojan1974 said:
setprop persist.camera.eis.enable 1 there is no need to knock
Click to expand...
Click to collapse
knock what? not making sense to me, sorry
nhmanas said:
Is slot a and b contains same data inside by stock?
Edit: this is my first system ab phone so be gentle please
Click to expand...
Click to collapse
Probably the 1st A/B phone for a lot of us.
But no, they don't have the same 'data inside by stock' (I'm not sure what you mean by that).
They use different partitions for many things such as; boot, system, vendor (the most important ones). But they do use the same one for data (is that what you meant?). The data one is where our apps, media files, etc are kept, and that doesn't change with an OTA update.
Another important difference is there is no longer a 'recovery' partition, which is what twrp use to be installed in. Now, with A/B, the 2 boot partitions and the rest of the 2 partitions are the old 'recovery'.
So what does the 'other' boot partition have in it? Well the old version of the OS before the OTA update. That doesn't change with an update. The other slot is updated and then made active. Then when a new update happens, the current one becomes the old one (again). And on and on.
the reason this works is because the setprop persist commands only change the data partition, not system. And since twrp mounts data (of course it does, it's a recovery tool), it can execute the setprop commands no problems.
good luck
When i boot twrp i get error: device '(null)' not found.
Ajakazema said:
When i boot twrp i get error: device '(null)' not found.
Click to expand...
Click to collapse
What is the exact command you are entering? What happens if you do 'fastboot devices' ? Does that command see your device?
AsItLies said:
What is the exact command you are entering? What happens if you do 'fastboot devices' ? Does that command see your device?
Click to expand...
Click to collapse
adb shell, but no i don't think it can see the device when it goes into twrp. I think it's a driver issue but i can't figure out why, tried it on 2 PCs and i get the same problem.
Edit: when i type fastboot devices it just says list of devices attached
Ajakazema said:
adb shell, but no i don't think it can see the device when it goes into twrp. I think it's a driver issue but i can't figure out why, tried it on 2 PCs and i get the same problem.
Click to expand...
Click to collapse
yes it may be a driver issue. did you just unlock the bootloader? if yes, you have to reboot the device and enable adb debugging in dev options?
AsItLies said:
yes it may be a driver issue. did you just unlock the bootloader? if yes, you have to reboot the device and enable adb debugging in dev options?
Click to expand...
Click to collapse
Did both of those things.
Ajakazema said:
Did both of those things.
Click to expand...
Click to collapse
Another thing it might be is the pin / pattern security being set. Twrp won't let you touch the device if you haven't entered the pin / pattern.
It might be a good idea to just disable them temporarily and then try again.
AsItLies said:
Another thing it might be is the pin / pattern security being set. Twrp won't let you touch the device if you haven't entered the pin / pattern.
It might be a good idea to just disable them temporarily and then try again.
Click to expand...
Click to collapse
Yea i tried that too, no luck.
Ajakazema said:
Yea i tried that too, no luck.
Click to expand...
Click to collapse
Are you using the version of twrp I mentioned in the first post? They aren't all the same, the one mentioned is specifically for this phone - Jasmine.
hard to imagine what else it could be...
AsItLies said:
Are you using the version of twrp I mentioned in the first post? They aren't all the same, the one mentioned is specifically for this phone - Jasmine.
hard to imagine what else it could be...
Click to expand...
Click to collapse
Yea. No idea what the problem is.
Related
Please note: This will not recover you from a bricked device. This applies to bootloops caused by modifications you made, AFTER successfully rooting.
So you changed your build.prop or deleted a system file you shouldn't have? Your phone is now constantly rebooting? Your variant doesn't have a KDZ available? Here's an easy, albeit time consuming method to recover. (without TWRP or KDZ and no data loss)
First off, if you haven't caused a bootloop yet and you are doing a lot of modifications, do the following. Go to SuperSU and allow su requests on boot. This will allow you to fix minor problems during the bootloop, such as restoring your backed up build.prop or other modified system file. Many times, people will forget to set permissions on a file, especially build.prop. This will cause a bootloop.
If you GRANTED su requests during boot in SuperSU:
Say you set the wrong permissions on build.prop:
While your phone is bootlooping, plug it into your PC, then execute the following commands:
Code:
adb shell
$ stop
$ su
# chmod 0644 /system/build.prop
# reboot
Say you screwed the build.prop up and need to restore a backup you made to your sdcard:
Code:
adb shell
$ stop
$ su
# cp /sdcard/build.prop /system/build.prop
# chmod 0644 /system/build.prop
# reboot
If you DID NOT grant su requests during boot in SuperSU (or if you have tried and failed other methods to recover):
While your phone is bootlooping, plug it into your PC, then do the following:
1. Locate the image you used to root your phone.
2. If the image is on your phone still, just re-root. Your phone will be fixed.
3. If you deleted it from your internal SD card continue to step 4.
4. Open command prompt in folder on your PC containing image, then issue the following command:
This will take a VERY long time (20-30 minutes)
Code:
adb push system_image_name.img /sdcard/system_image_name.img
Note: If you don't have adb mapped to your environment variables, move the image into your platform-tools folder, or whichever folder contains adb. Then run the above command.
5. Re-root
Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?
minirx7 said:
Can't wait to try this when i get home. I soft bricked my LG G4 with a bad system.img so i am trying to restore. Is this actually going to allow me to push the img file back to the phone even though i cant boot?
Click to expand...
Click to collapse
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app
Meibs81 said:
I KDZ back to stock, then re-rooted to fix mine. No data loss.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
That is a great method to use, but several variants don't have KDZs :crying:
I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?
pcrhckyman said:
I'm on the Sprint variant and am getting the Security Error loop. I have no system.img yet, however I can't seem to adb push anything (or see the phone with ADB at all)... am I doing something wrong?
Click to expand...
Click to collapse
That would not be considered a bootloop. That's a brick. I'm sorry, but in your case unless you already had a system image on your phone to flash, you are SOL until we get a TOT file.
tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!
minirx7 said:
Well i am able to access factory reset and i am able to get into download mode and see it from the send_command tool.. HOpe that means my odds are 100% instead!
Click to expand...
Click to collapse
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.
tabp0le said:
In your case I'd say 50/50. It depends if it at least gets to the part of the boot sequence which enables adb.
Click to expand...
Click to collapse
tabp0le said:
Not necessarily. Download mode and factory reset(recovery) are located on different partitions than boot and system. Do you at least get to the carrier boot animation while attempting to boot? If so, your chances are good. If not, your chances are bad. The initial commands, including adb push have to be run while the phone is attempting to boot. NOT in download mode or recovery.
Click to expand...
Click to collapse
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!
minirx7 said:
I get stuck on the LG logo where the light flashes on and off. While this happens if the phone is connected to the computer i hear the USB connection sound in windows. I will be trying it in a few hours.. hope it works!
Click to expand...
Click to collapse
You may be able to do it then. Let us know how it goes!
Delete
Peeptastic said:
Can I use this method to solve my particular problem (bypassing setup - I cannot move forward in the setup after a hard reset). Thanks (Can give you more info if you need it)
Click to expand...
Click to collapse
You may be able to. Does your phone boot? How far does it get in the booting process? If you get to initial phone setup, and can't get to the settings app to enable developer options and debugging, then you probably can't use this.. I'm not sure it would work, but you could try-During boot, debugging might enabled by default. (I'm not sure) Right when your bootanimation comes on you might be able to run the command:
Code:
adb shell stop
Then run the rest of the commands/follow this guide. It would be worth a shot.
Delete
Peeptastic said:
I will try it. I can get into the phone to the screen right after entering wifi, then it just stalls. It doesn't freeze, but it also doesn't go anywhere. This is with wifi and data (I left the phone on for a bit and data picked up). If it's related, I turned on Voice Assistance and when the phone gets to the first set up screen she says something about Google play services not working and then "Hangouts needs Google Play services". That could be why I can't move on.....
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
I hear windows chime when it starts up, and the computer charges the phone. Running your command tells me: error: device not found.
Click to expand...
Click to collapse
How did you get in this situation to begin with? Are you able to get into settings at all?
Delete
Peeptastic said:
Factory reset because of the Google play error. Only it looks like Factory reset didn't fix it. And nope, can't get into settings because I can't get out of the set up screen (setup like when you first turn on the phone out of the box). I can get to download mode and stock recovery. As far as I know, there is no way to skip the original LG setup (clockwise button press doesn't work).
Can I adb sideload the image and try that way
Click to expand...
Click to collapse
Unfortunately that will not work. adb sideload is only for flashing .zip files.
tabp0le said:
Unfortunately that will not work. adb sideload is only for flashing .zip files.
Click to expand...
Click to collapse
Delete
every time I run the command while in bootloop it says "Device not found"
sarwaria23 said:
every time I run the command while in bootloop it says "Device not found"
Click to expand...
Click to collapse
This is what is happening to me too. I can see that the phone during boot loop is recognized. I check the device drivers and it shows up under windows as LG.
Crap. not good.
This method here seemed pretty straightforward to upgrade to Nougat: https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
I was already unlocked so I figured I just need to flash the "Full" package then the "TWRP" package. TWRP is working, the bootloader still shows as unlocked in fastboot mode, but trying to boot just shows a Linux penguin and nothing else!
I just cleared everything in TWRP to see if that was somehow the issue then reboot, and TWRP says no OS installed! HOW?!
All this happened because I'm unclear on everything, and instead of a yes/no answer I get mocked. Someone please help.
Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.
tester2017 said:
Can you Boot in Fastboot?
When yes . load a Original Firmware update.zip and extract recovery.img from this . Do the recovery.img in Minimal adb and fastboot , open a command windows .
Type: fastboot flash recovery recovery.img ,before this boot the phone in fastboot mode.
After the flash recovery ,boot the phone in the recovery with Volume down (tick them 1 or two times ) reboot ist with power.
Put a SD Card in the Phone with the update zip in root folder of the SD Card.
In recovery tick with Volume down to the Point update via SD Card and wait the Process ist finished.
Click to expand...
Click to collapse
I have access to fastboot mode. However I'm still confused as to what is going on.
At least I've figured out where it goes wrong, at the TWRP step. The "no OS detected" made no sense so I tried flashing using the same method but just the "Full" package first. It eventually does boot and it appears Android 7 is working.
The bootloader shows as unlocked. However when I install the TWRP package after, TWRP is restored but then the phone is bricked and TWRP says no OS detected. I'm not sure if this is because I clicked "allow modifications" and if so why that causes it to go wrong and what I missed. I tried flashing TWRP manually using fastboot mode in case something was wrong with that EDL package, and the result is the same, after installing TWRP and clicking allow modifications the OS is no longer detected.
What am I missing? I must have missed a step.
ok. go to twrp and format data to ext 4 then flash new and restart.
tester2017 said:
ok. go to twrp and format data to ext 4 then flash new and restart.
Click to expand...
Click to collapse
When go to "Format Data", enter yes to allow it, it fails and says:
"mkfs.f2fs -t 0 /dev/block/sda9 process ended with
ERROR: 255
Unable to wipe Data.
Unable to format to remove encryption
Upadting partition details...
Failed to mount '/data' (device or resource busy)
... done"
Even if that went through I'm unsure what you mean flash new? Flash a new what?
When I enter repair/change it says the file system is ext4 anyway.
Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Cyrus D. said:
Well I tried starting at that point again since I didn't allow modifications in TWRP this time, and it actually booted Android but then asks for a password... what?
So something about allowing modifications in TWRP seems to be the culprit, but then I'm unsure why it would ask for a password to start the device when it boots after, it's obviously encrypted.
Flashing back to the "Full" package yet again to restore it working.
Edit: I thought double posts would be auto-merged...
Edit 2: "Format Data" left my device encrypted and the only way around it was a factory reset!
Edit 3: I read over the instructions in the TWRP thread again and I think I've found what I missed. If I don't update this thread again by tomorrow that means I've figured it out and everything should be fine.
Thank you everyone who tried to help.
Click to expand...
Click to collapse
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
This is clearly posted in the TWRP thread.
flyer_andy said:
Hi...I ran into your original issue and I believe it's related to dm-verify. For anyone that runs into this again, try flashing a dm-verify disabling zip and see if it'll boot again. This was the only way I could get the phone to boot after upgrading to nougat...not sure why this is an issue though as (I think) I had the stock bootstack in place along with stock System files.
Here is a link to the dm-verify disabling tool I used:
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Click to expand...
Click to collapse
Thanks, already read the TWRP thread and found what I was missing.
romeoh said:
Can you please give me instructions of what you did to upgrade to Nougat, I'm like you when started the upgrade on B29 Unlocked and rooted. I like the way of EDL process but It is a little vague and I don't want to brick my phone. Thanks in advance.
Click to expand...
Click to collapse
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Edit: Just to be clear, for step 2, when I said "or you can flash it from Fastboot" I meant TWRP in general, not the TWRP EDL package.
Cyrus D. said:
Thanks, already read the TWRP thread and found what I was missing.
I used the EDL method in the end. Part of the reason I set that up to begin with was just in case in the future I brick something, I'll have the ability to recover from anything prepared.
The step I missed which resulted in a brick was installing SuperSU (since I wanted root anyway, or you can disable dm-verity as the other fellow posted here) after allowing TWRP to be able to do modifications. Then I ended up with more bricks because I used SuperSU 2.79-SR2 and SR3, I thought it was fine since SR2 is what I was using with Marshmallow, apparently not, you have to use a non-SR version of 2.79 with Nougat.
So in summary, from EDL mode I:
1 - Installed the "Full" EDL package.
2 - Installed the "TWRP" EDL package, or you can flash it from Fastboot mode which might be more convenient since you'll have to restart EDL mode after flashing the first package to get it working/ready to flash in EDL mode again.
3 - Gave TWRP permission to do modifications and immediately (without rebooting/starting which would result in a brick) installed SuperSU 2.79 (non-SR), then rebooted (this could take a few mins as it says and can bootloop a few times).
If you said no to permissions for SuperSU and it's not giving you the option again you can reflash SuperSU then reboot to bootloader then reboot to recovery, that should make it show the option again. And in case you're not aware, to make changes to system files and such permanent when you have root, you have to enter a command in TWRP's terminal emulator or ADB shell. I think it was "reboot disemmcwp", it may need "SU" in front if you're doing it through an ADB shell in Windows, I'm not sure. Not quotes of course. Search the forums to find out for sure, it had to be in a guide somewhere.
Click to expand...
Click to collapse
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications. ???
romeoh said:
Many thanks body, As you said using EDL mode is great to unbrake your phone from any state plus it reminds me with Odin that's why I like this way it's very simple, but as you know this is not Samsung phone and it has so many complications.
Click to expand...
Click to collapse
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.
Cyrus D. said:
No problem. I threw in an edit to my last post to clarify point 2 in case you thought I meant you can flash the EDL package from Fastboot mode, I meant TWRP in general. In case you forgot the command to use in the ADB shell it's "fastboot flash recovery FileName.img" (twrp-3.0.4-1-ailsa_ii.img in my case).
If you already had the "reboot disemmcwp"/"SU reboot disemmcwp" step done you don't need to do it again.
And just some general information for you regarding my experience with Nougat so far:
1 - When I started it I selected Canadian English as my language. This apparently disables ZTE voice functions, or Nougat is missing it in general. It's missing from the menus and when I hold the back key it said "Only English and Spanish supported". Piss poorly done as usual, ZTE, since the pronunciation of Canadian and American English is nearly identical with very few exceptions, might as well have left American English enabled for voice commands. So I went into the menu and selected just "English" as my system language, and now the option to set Canadian English is missing entirely, and voice functions are still missing. Holding the back key just results in nothing now instead of the "Only English and Spanish supported" message. So I'm saying I don't know if ZTE voice functions are still there, someone else can answer this, or I guess you'll find out.
2 - Google's Timely alarm app (and possibly other alarms) still don't work properly and will be off by several minutes, so I'm stuck using the default sucky clock app until I find something else that works.
3 - The default apps are all still the exact same trash. If you really want to use the AKM "32 bit" (truncated to 16 bit output) Hi-Fi DAC and amp you're still stuck with the garbage laggy default music app, which now has some sort of bonus lag/stutter. People claiming that you can use the DAC with something like PowerAmp are sadly mistaken, that sounds so different and lower quality than when using the stock music app and even says it's using the SD 820's 24 bit DAC when set to Hi-Fi output. There's even a ridiculous rumour going around that the Axon 7 doesn't have the SD 820's DAC which is retarded, ZTE can't pick and choose components of SoCs supplied by Qualcomm, they just buy some of their stock of what's already made. It's definitely in there, whether or not it's enabled is another story.
4 - Battery life is worse, this is at least partly because there is no Xposed support for Nougat yet so I can't enable the Greenify module to allow really aggressive dozing and dozing on the go (which I thought Nougat was supposed to support?). It could also be partly due to my battery being rapidly degraded from Daydream mode being a firey hell inferno. It heated my battery up to 48C and over 42C in other cases even with my best efforts to keep it cool by enabling Ultra Power Saving Mode (which Daydream may be overriding) and shoving in aluminium foil to act as a heatsink. All phones from reports so far overheat horribly when using Daydream, especially the Pixel XL. It's not surprising that the Axon 7 rapidly overheats as well considering it literally uses the battery as a heatsink; a heatpipe carries heat from the SoC to the battery. I would have not bought the A7 if I knew this.
Edit: I forgot -
5 - ZTE locker no longer allows browsing all of their past content, only what they allow per day, which so far for me has only been the same crap and never anything new. Too bad, I liked some of their old content, though it was all 1080p and not 1440p. Oh well.
Click to expand...
Click to collapse
Omg bro, To be honest I hate the software experience on that phone. It is the only thing that turning me off from it. I played a little with my brother's S7 edge the other day, and believe me the software experience is extraordinary. However I noticed that the S7 edge overheats a lot too without even using the daydream. In my opinion I think Axon 7 lacks in hardware wise a bigger battery and the support of the new RCS messaging feature, and in software wise a whole new developed system.
Since the majority of the hardware between the devices is gonna be almost exactly the same, I'mma give a shot at rooting it. Picking up tomorrow, so hopefully it goes well
I just got this phone. Let me know how what happens please.
tge101 said:
I just got this phone. Let me know how what happens please.
Click to expand...
Click to collapse
Yeah, I'll keep a heads up. I'm sitting in metro now tryna see what's going on, small argument. Their commercials in Philly don't mention that you need to switch carriers for the rebates.
I'll probably be getting one next week. Says it has 7.1.2 an it weighs less? Cool
attempt
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
tribal1209 said:
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
Click to expand...
Click to collapse
Are you trying to root the aristo or aristo 2?
Aristo 2. Sorry, kind of diving in head first with this whole process. If im doing something obviously wrong go easy on me lol.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
Aristo 2
Hmm and you flashed the twrp that was for the aristo right?
Well the TWRP files i used were on *How To* forums posts and youtube videos for the original LG Aristo. Everything was going fine but the touch screen while in TWRP does not work. Maybe there os a different version I can try? Do any of you guys have any ideas, my understanding though is that TWRP has to be created for a specific device once released. Is thats whats going wrong?
you unlocked the bootloader and flashed the aristo 1 recovery thats what you did so far right?
The aristo 1 recovery will not work at all.
The screens are of the same build, but different composition.
That's why I wanted to test this myself before posting further on the subject.
I can risk my phone, most of you cant.
I figured as much. Thanks for the info! Just got mine today. Glad the aristo's battery works in the aristo2 as i bought a couple batteries for it. I still do like the aristo though it feels a bit better in my hand.
Well luckily It seems i have not screwed up my phone. Have reset and wiped it multiple times which was annoying, but seems to be ok. It sucks because it looks like the touch screen alone is whats screwing me over. If only i had a way around it. Then again im sure you guys have a better idea of whats going on. Guess ill just be patient until more is posted on subject.
We need a new recovery for this anyway. Since the aristo 2 isn't gonna have multiple versions (besides the Korean base model the 2 is built after), we should be able to build just one recovery using the model number as it's target, we can make it borderline universal if a new version were to pop up.
I decided against going the metro route, buying mine in bulk. So I'll have one to smash when this is all over.
The TWRP method works the same as the Aristo, and the TWRP recovery IS compatible. However the touch screen does not function.. Is there a way to get it to work?
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
brad2192 said:
@[email protected]@tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Not to sound sceptical but is this the real deal?
spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Please someone let me know! I want this phone rooted (Its an awesome phone) but want some verification before I start flashing and downloading random files.
spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Yes, it is. What I did was use LG firmware extractor and extracted the boot image, then I proceeded to patch the boot image with magisk manager. Enabling OEM unlock allows me to flash the boot image with the newly-created custom one. Remember though, you should create a backup of your device because enabling OEM unlock will completely erase everything.
brad2192 said:
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Supposedly the img you posted is simply a modified version of Magisk you posted. Someone please explain to me (Who is new to this whole process) why this supposed explanation does not involve any recovery program or requiring of wiping/clearing any cache or what have you?
Warning: This is dangerous! Even if you do everything according to the following description, your phone may end up damaged! There are no warranties!!
As we know we could change the single sim z play to dual sim by mod the "persist.radio.multisim.config" in TWRP, like showing below:
https://forum.xda-developers.com/moto-z-play/how-to/guide-to-enable-dualsim-singlesim-t3570601
However it will not be functional after you re-flash the firmware.
So inspired by the moto z dual sim mod thread of @benzinerwin:
https://forum.xda-developers.com/moto-z/how-to/guide-dual-sim-mod-signle-sim-moto-z-t3606528
I fingered out the same way on moto z play:
1, Pull the partition controls the "dualsim: false / true" flag:
Code:
adb shell "dd if=/dev/block/mmcblk0p50 of=/tmp/mmcblk0p50.bin"
adb pull /tmp/mmcblk0p50.bin
2, Use a hex editor to change "6661 6C73 6500" to "7472 7565 0000":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3, Write the partition back:
Code:
adb push mmcblk0p50_edit.bin /tmp/mmcblk0p50_edit.bin
adb shell "dd if=/tmp/mmcblk0p50_edit.bin of=/dev/block/mmcblk0p50"
adb reboot bootloader
4, Erase the partitions modemst1, modemst2 and cache, reboot again.
Code:
fastboot oem hw
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot reboot
After all above steps you can relock the bootloader, go back to stock again, this mod is compatible with future moto OTAs, and it will stay no matter which firmware you have.
Enjoy!
Do you need to be root?
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
I'm on Android Oreo Soak, do you think it would work?
No need to root, but you need to unlock the bootloader, use TWRP to dump the partition, modify it, write it back.
Then you can relock the bootloader.
Yes I was on 8.0 soka also, it works.
Basically you're changing something out of the rom.
Sent from my XT1635-02 using Tapatalk
Just did this on my Moto Z Play, works great on Android Oreo!
tutorial
I would like to know where I find a guide or video guide to perform the procedure without making mistakes, because I would like to leave my motorola z play dual sim
me gustaría saber donde encuentro una guía o vídeo guía para realizar el procedimiento sin cometer errores, porque me gustaria dejar mi motorola z play dual sim
Anything to back up to make this safe and avoid chance of wiping out IMEI like the other thread?
ralphodog said:
... and avoid chance of wiping out IMEI like the other thread?
Click to expand...
Click to collapse
What are you talking about? Why do you refer to another thread without linking it? Which wipe imei?
It just works fine. That's my experience. Did the mod, got two sim displayed.
Hi, @benzinerwin mentioned to backup the stock recovery partition in order to be able to flash the stock recovery after the modification.
I managed to unlock the bootloader and boot (not flash) into TWRP. However, the recovery partition is not among the partitions TWRP offers for backup.
Can anyone help?
will it restore everything after flash original firmware?
Thanks, this worked like a charm!
I didn't flash TWRP, just booted it from ram and then followed the guide
Code:
fastboot boot twrp-3.2.2-0-addison.img
Slightly off-topic, but could someone point me to a guide to re-lock the bootloader? I couldn't find anything that wouldn't require re-flashing a ton of images. I'm completely stock on Oreo, with this dual-sim mod being the only modification.
danton47 said:
..., but could someone point me to a guide to re-lock the bootloader? I couldn't find anything that wouldn't require re-flashing a ton of images. I'm completely stock on Oreo, with this dual-sim mod being the only modification.
Click to expand...
Click to collapse
For relock you need signed images. Procedure is, you say "start relock", then flash all important partitions with images signed by Lenotorola, then say "end relock". If signature is fine, relock will succeed.
This means you need signed images you want to flash for relock. It's a bad idea to downgrade, especially Moto devices which like to hard brick on OTA after downgrade, so you would need signed Oreo files for relock.
The Dual-SIM mod should be fine and compatible with relock, but that is just a guess by me.
Why do you want to relock? Afterwards you won't be able to start twrp and do Nandroid backup or restore, you are aware of this feature loss?
tag68 said:
Why do you want to relock? Afterwards you won't be able to start twrp and do Nandroid backup or restore, you are aware of this feature loss?
Click to expand...
Click to collapse
The only reason to relock would be to make some security-sensitive software like Google Pay happy. I'm using some corporate software which I thought might refuse to work on a device with an unlocked bootloader. Fortunately, this turned out not to be the case, so I'm good for now. Still, this may change with a future upgrade, so I'm a bit undecided. Maybe I should go through the pain of re-flashing/re-locking while signed images are still available for the OS version I'm currently running.
Anyway, thanks a lot for your detailed response, much appreciated!
You also may use Magisk and Magisk Hide which hides the unlocked state of your phone and usually makes SafetyNet (Pokemon Go, Google Pay etc.) happy. Your phone then is rooted, but if you never give any app the approval to make use of that power, it shouldn't do any harm.
danton47 said:
Thanks, this worked like a charm!
I didn't flash TWRP, just booted it from ram and then followed the guide
Code:
fastboot boot twrp-3.2.2-0-addison.img
Slightly off-topic, but could someone point me to a guide to re-lock the bootloader? I couldn't find anything that wouldn't require re-flashing a ton of images. I'm completely stock on Oreo, with this dual-sim mod being the only modification.
Click to expand...
Click to collapse
Hi, I tried to do the mod the way danton47 did it, which means by only booting twrp instead of flashing it. However, I did not manage to pull the mmcblk0p50.bin file. This is what I did so far:
Starting point:
- the phone runs on Stock-Android 8.0.0, Build number OPNS27.76-12-22-3;
- The Stock recovery was still in place
- the phone was NOT rooted
- the bootloader was locked
What I did then was:
- installation of adb, fastboot and the USB drivers on my computer (I am operating on Windows 7)
- enabling of the "developer options", "USB debugging" and "OEM unlocking" in the stock OS settings of the phone
- unlocking of the bootloader using adb and fastboot and getting the unlock key from the motorola website
-> Having done all this I assume that my adb and fastboot setup is complete and fully functional - otherwise I wouldn't have come so far. Please let me know if I am wrong with that.
- Download of twrp
- copy of the twrp bin file into the same directory in which the adb and fastboot exe files are
- reboot of the phone into bootloader
- boot of twrp from ram
Here the problems started. Initially I tried to use TWRP to backup the (Stock-) recovery partition so that I can then flash twrp, execute the dual-sim modification and then go back to stock-recovery (for the same reason as danton47: the only modification I want ot do to this phone is to enable the dual sim feature).
However, twrp does not offer the recovery partition for backup. I made quite some reasearch for that issue but did not find any solution.
Therefore I was very happy to see that danton47 managed to unlock the dual-sim functionality without flashing twrp. As I understood it this means that the modification can be executed without changing anything else than the affected bin file. So I booted into twrp (same version as danton47 used) again:
Code:
fastboot boot twrp-3.2.2-0-addison.img
However,
Code:
adb devices
does not show me any device! I also tried to enable the "adb sideleoad" in twrp, hoping that this would allow adb to access the phone while TWRP is running (just tell me if this is completely useless at this point). No success neither.
When activating the adb sideload, I get the options "Wipe Dalvik Cache" and "Wipe Cache". I didn't use these options as I don't know what would be wiped.
Can anyone help me with either
- getting twrp to backup my stock recovery so that I can try again by flashing twrp
or
- enabling adb to access the phone whil twrp is booted from ram?
Thanks in advance!
derBorg said:
- enabling adb to access the phone whil twrp is booted from ram?
Click to expand...
Click to collapse
For adb you do not start twrp. Just enter fastboot mode.
tag68 said:
For adb you do not start twrp. Just enter fastboot mode.
Click to expand...
Click to collapse
Thanks for the quick response!
However, I don't get ahead with it. What I read so far is that adb is not used in fastboot mode (which is the same as the bootloader, right?), but when android (or eventually twrp) is running. Please correct me if I'm wrong. At least it didn't work when I tried right now. When the phone is in fastboot mode <adb devices> does not show any device, while <fastboot devices> does.
Here the code I entered with the output I got (serial number edited), starting with android booted, the usb connection established and usb debugging enabled:
Code:
adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ZY12345678 device
adb reboot bootloader
adb devices
List of devices attached
fastboot devices
ZY12345678 fastboot
adb devices
List of devices attached
Allright, I got it done. Now I want to close my issue on this thread and share my experience.
I could solve the problem that adb did not work in TWRP by hints I found in this thread:
https://forum.xda-developers.com/galaxy-nexus/help/adb-twrp-recovery-t1968989
Apparently it was some sort of driver issue (on Windows 7). When the stock Android was booted, the adb driver worked perfectly and in the device manager I got an entry "Android device/Motorola ADB Interface". After rebooting into bootloader and booting (without flashing) into TWRP using the command:
Code:
fastboot boot twrp-3.2.2-0-addison.img
The phone did not show up at the same place in the device manager any more. Instead, it appeared as "Andere Geräte/ADB Interface", which translates to something like "Further devices/ADB Interface" (I don't know for sure the exact english wording MS uses at this place). Moreover, "ADB Interface" could not be installed properly. This was the reason, why ADB did not work with TWRP booted.
To solve this issue, I pushed Windows to find a driver for the ADB interface. It also found one but not quite the correct one. It found a driver from Samsung and the phone with TWPR booted appeared as "SAMSUNG Android Phone/Android Composite ADB Interface". With this driver installed and TWRP booted "adb devices" finally found my phone. However, I wasn't really comfortable using a not completely adequate driver for modifying my phone, so I uninstalled the driver again an tried to find the corresponding motorola driver. Unfortunately, the only one I found was the driver I already had installed and which allowed me to run adb on Android, but failed on TWRP. Finally, I let windows install the Samsung driver again and (after making a final backup of my contacts and data) executed the dualsim modification described above, which finally was the easiest part of all.
Thanks again to lanyao1920 and benzinerwin for posting how to do the modification and thanks to danton47 to point out that it is not required to flash TWRP for this purpose!
I finally got around to doing this mod. Started last night, and was struggling with things not going quite as described. Couldn't get adb push/pull to behave, screwed around with chmod'ing the files, and some other random crap. Was able to get the mmcblk0p50.bin out and hex edited, but every time I tried dd'ing it back to dev/block/ it wouldn't write correctly. mmcblk0p50 was nearly blank when I looked at it in Xplore's hex viewer. Phone seemed to be functioning fine in this condition, however, albeit with only one sim.
It might have been the couple of imperial stouts I was having, but when I woke up this morning I tried again. And everything worked exactly as described with no issues.
What was I doing wrong? I'll tell you - I was trying to do the ADB commands with the device fully running last night, rather than in recovery.
There is a brief mention in post 2 that apparently didn't click with me last night (maybe cause beer?) that you need to be in recovery. I might have caught this a few years ago when I was messing around more, but I haven't done much of this stuff for a while. I'd like to recommend to OP to add a comment in the OP to make sure others are aware all the adb commands must be done from recovery. Or maybe not needed since I'm the only one who seems to have had issues.
My experience so far: I am US user, using a carrier unlocked device on August 2018 security patch of RETUS stock software. I'm bootloader unlocked, and rooted. I happen to already have a dual-sim tray for my device sold as single sim - I ordered it a couple years ago for travelling abroad, just to have a non-usable place to stash my US sim safely while I was using a local prepaid one on my trip. I have so far tested only my postpaid ATT sim. It appears to be working for both data and calling in both sim slot 1 and sim slot 2, even though slot 2, as advertised, indicates IMEI of 0. My only testing so far, however, has been on my ATT microcell, so I'm not sure if that makes a difference or not. I was actually not expecting the device to connect to the microcell using slot 2, as all devices have to be manually registered to it using IMEI. I'll post back with any further info, as I've seen very limited info anywhere about what actually works and what doesn't in the US in this type of situation. I expect to be able to test a verizon sim and a freedompop sim shortly.
Big thanks to the OP for finding this solution!
For me it worked fine on first try, except that Dual SIM is not working as expected:
- If you activate "always use SIM1 for phone" - it still asks which SIM to use when calling someone
- If you click when calling "remember decision for this contact" when clicking SIM1, you STILL get asked which SIM to use on next call
- If you are using Android Auto and making a call, it displays the question which SIM to use on the phone display
I'm using Android 8.0.0 patch dated August 2018. Is there some possibility to correct the behavior?
tag68 said:
For me it worked fine on first try, except that Dual SIM is not working as expected:
- If you activate "always use SIM1 for phone" - it still asks which SIM to use when calling someone
- If you click when calling "remember decision for this contact" when clicking SIM1, you STILL get asked which SIM to use on next call
- If you are using Android Auto and making a call, it displays the question which SIM to use on the phone display
I'm using Android 8.0.0 patch dated August 2018. Is there some possibility to correct the behavior?
Click to expand...
Click to collapse
It appears that I am seeing the same behaviors so far. Not a huge deal in my use case, but I can see how that would be irritating in many use cases.
Complete wild guess here: firmware from an originally dual sim device might fix this? No idea if this would really work, or present other issues...
Hi All,
In the best interest to provide clarity I'm creating this quick and easy tutorial on how to root your Razer Phone 2 after the Pie Upgrade. Please send me any feedback to improve this post, we need to build up a strong community.
*As usual, I'm not responsible of any damage or brick to your phone, do it at your own risk.
Pre-Requirements:
-Be sure to have at least 70% of charges... or plug your phone to power
-Backup anything you consider important
-Already installed Pie Upgrade via OTA or Side Loaded
-Enable Developer Options
• Open Phone "Settings" and scroll down.
• You will see an option "Build Number".
• Simply tap on it 7 times to enable it on your Android Oreo based device.
• Your device immediately display a message on screen that will say "You are now a developer".
• The Developer Option is now available in the Settings>System>Developer Options. Enjoy!
- Install Android Drivers (https://developer.android.com/studio/run/win-usb) and ADB, I personally recommend -[TOOL]Minimal ADB and Fastboot [2-9-18] - https://forum.xda-developers.com/showthread.php?t=2317790
-Unlock Bootloader
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
• Using ADB commands reboot on bootloader
adb reboot bootloader
• After reboot completes follow phone menus and select "UNLOCK BOOTLOADER"; accept all warnings, after restart you have completed the unlock.
Root and Installing Magisk
Since our phone doesn't have a proven customer recovery fully working (Ex TWRP) Magisk needs to be installed by manually patching the device boot image.
Making leverage of Warrior1988 post [Root Magisk Pie Update For Unlocked Devices] all credits to him. Download the image from his post
• Boot in fastboot mode To boot into fastboot, press and hold the Power button + Volume Down Keys for few seconds; Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Install Magisk Download the apk and install it as usual on your RP2, that should be all.
DONE!!!! You now have a unleashed the beast! Please send me any recommendations to improved this guide.
chpimentelpr said:
Install Android Drivers and ADB
Click to expand...
Click to collapse
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
chpimentelpr said:
• To enable OEM unlock, go to Settings > Developer options and check Enable OEM unlock
Click to expand...
Click to collapse
I assume this is where we plug our phone into our computer?
chpimentelpr said:
• Using ADB commands reboot on bootloader
Click to expand...
Click to collapse
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
chpimentelpr said:
• Copy the image on the same folder as your ADB and Run the following commands:
fastboot flash*boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
AbsoluteContingency said:
Your link has everything necessary for this step, right? Direct link to version 1.4.3 is here: https://androidfilehost.com/?fid=746010030569952951
Or are drivers and ADB two separate downloads?
I assume this is where we plug our phone into our computer?
For anyone dumb and new like me, I think this is with cmd.exe in Windows. Win+S -> type "cmd" (without quotation marks) and hit enter. Once open, you want to navigate to ADB, which you've already installed via the above instructions.
So your cmd will say:
C:\Users\YourName>
And you want to get to ADB, so you'll type "cd" (without quotation marks) which means you want to change directories, and then "cd adb" (if its in C:\ directory) or "cd [whatever the path is to the ADB folder]\adb"
Assuming it was directly in C:, you should see something like:
C:\adb>
Now you want to type "adb devices" to make sure it sees your phone is plugged in. You should see: "list of devices attached - [model] device" or something.
Now you're ready to go with the instructions starting at "adb reboot bootloader." If I'm wrong about this, someone less new and dumb than I am please correct me.
I'm confused on this one. The first one has "flash*boot_a," but the second one has "flash boot_b" without the * symbol. What does the * do, and what happens if we mess it up? Sorry if that's a dumb question.
Click to expand...
Click to collapse
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Warrior1988 said:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot reboot
Click to expand...
Click to collapse
No asterisk. Cool. Got it. Thank you, dude.
The drivers are the regular ones for android nothing specific, they can be downloaded from their SDK https://developer.android.com/studio/run/win-usb
App root detection?
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Bounty33 said:
If I root my Razer phone 2 using this guide, will certain apps like banking apps, and rideshare apps be able to detect root?
Click to expand...
Click to collapse
You can use magisk to hide the root from those apps. In general banking app are not affected by root. Google pay could be affected, but I don't use it so can't be sure. And you can always unroot.
AbsoluteContingency said:
No asterisk. Cool. Got it. Thank you, dude.
Click to expand...
Click to collapse
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
chpimentelpr said:
Did you rooted? Anything missing on the guide? I want make it as useful as possible so feedback is welcome.
Click to expand...
Click to collapse
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
AbsoluteContingency said:
I have not, but I've been really sick and useless. I think I'll try tonight and let you know how it goes. Thanks for the guide, dude.
---------- Post added at 02:50 PM ---------- Previous post was at 02:45 PM ----------
Wait, yes, I do have a question. I download the drivers, and I download the Fastboot ADB thing. What do I do with the drivers? Do they just install in Windows like anything else, and that allows me to connect to the phone?
Click to expand...
Click to collapse
Yes, install them as any other driver.
After rooting can you relock the boot loader or will that brick the phone?
ndragon798 said:
After rooting can you relock the boot loader or will that brick the phone?
Click to expand...
Click to collapse
Not sure, but why you want to relock the boot.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Mostly to get rid of the startup message
Very nice. I've rooted a ton of phones over the years, but they had more established communities and had well-explained (and tested) methods of rooting. The previous guide posted (that you referenced) was fine enough, but it was very much lacking a couple prerequisites that I was wondering/concerned about. This guide has cleared all of that up for me, and I now feel confident about rooting this phone.
Just as soon as I charge up the phone and install the OTA I've been avoiding until now... lol. Hoping somebody will make a Magisk module to move the clock back to where it belongs (if they haven't already).
EDIT: Just wanted to add my success story to this. Only thing I had to do that wasn't listed in the instructions (but makes sense) is that fastboot didn't work until I enabled USB Debugging (again, after the wipe and reboot), and I had to very manually tell the computer which driver to use (ADB) after that. Didn't have that issue for the bootloader instructions beforehand (that time, the driver worked automatically), so I figured I'd mention it.
chpimentelpr said:
Not sure, but why you want to relock the boot.
Click to expand...
Click to collapse
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
ndragon798 said:
Also is there a way to turn back on the preboot authentication. Pretty much I just want to maintain full encryption and the built in security while having root.
Click to expand...
Click to collapse
I don't believe encryption is supported at the moment, and I don't encourage you to try it until TWRP is fully supported since you may end up in a boot loop. I'm eagerly waiting for the full encryption capability, so I will let you know as soon as something come up.
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
ChronosTrigger said:
This has to be......one of the most usefull and noob friendly guides i have ever seen.....
You sir....are a God
Thank You.
Click to expand...
Click to collapse
i'm glad it helps.
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
xttweaponttx said:
Alright so after fighting with windows for a few hours, I discovered that my ADB was severely outdated.... Lesson learned there.
After getting the new boot image installed, though, I hit another problem... WiFi refuses to work. The toggle switch in the statusbar, nor the toggle in the system settings, will bring my wifi to life. Which is weird! Because I got through setup just fine, connected to wifi and signed into google... Yet now all wifi functionality has vanished. I tried a factory reset, to no avail. I'm gonna have to restore the factory boot image and start all over... But for now, figured I'd ask if anyone else has run into this weird bug?
***update***
I've now gone and flashed the global image for 8.1.0 to the phone... and it's telling me the OS is up to date???? How do I get back to pie?? It's late here and I've got wifi back now... but I'm stumped. Any help would be so greatly appreciated!
Click to expand...
Click to collapse
I doubt the issue with the wifi is related with the image, since it doesn't have anything to do with it. If your phone doesn't detect the update you will need to sideload it. Then try the root guide again. Let us know how it goes, it the first time I hear something wrong with WIFI after rooting.