How to root Orange Rise 52 (Alcatel) - Android Q&A, Help & Troubleshooting

Hello, I'm new here.
I would like to ask you if someone has rooted this phone (Orange Rise 52 (Alcatel)) because it has 1GB RAM and with Orange carrier bloatware runs really slow and I would like to root it to remove all that software and maybe use as multimedia device or something like that.
How can I root this phone? What tools I need and steps must I take?
Regards and thanks for your time and patience!!

---

@knopfler1980
If not done yet, on PC install the appropriate USB-drivers and re-boot PC
Connect phone and PC via USB-cable, check whether you can access phone via ADB: on Windows command prompt run
Code:
adb devices
If OK, download SuperSU Pro.zip and flash the ZIP
DL & How-to: https://www.supersupro.co/supersu-zip.html
If OK re-boot phone, then on phone install Link2SD app
DL: https://play.google.com/store/apps/details?id=com.buak.Link2SD&hl=en_US
If OK run Link2SD and uninstall all unwanted apps

---

jwoegerbauer said:
@knopfler1980
If not done yet, on PC install the appropriate USB-drivers and re-boot PC
Connect phone and PC via USB-cable, check whether you can access phone via ADB: on Windows command prompt run
Code:
adb devices
If OK, download SuperSU Pro.zip and flash the ZIP
DL & How-to: https://www.supersupro.co/supersu-zip.html
If OK re-boot phone, then on phone install Link2SD app
DL: https://play.google.com/store/apps/details?id=com.buak.Link2SD&hl=en_US
If OK run Link2SD and uninstall all unwanted apps
Click to expand...
Click to collapse
@ jwoegerbauer Thanks, I will try it!!

---

jwoegerbauer said:
@knopfler1980
If not done yet, on PC install the appropriate USB-drivers and re-boot PC
Connect phone and PC via USB-cable, check whether you can access phone via ADB: on Windows command prompt run
Code:
adb devices
If OK, download SuperSU Pro.zip and flash the ZIP
DL & How-to: https://www.supersupro.co/supersu-zip.html
If OK re-boot phone, then on phone install Link2SD app
DL: https://play.google.com/store/apps/details?id=com.buak.Link2SD&hl=en_US
If OK run Link2SD and uninstall all unwanted apps
Click to expand...
Click to collapse
Hello, I installed both drivers but when I run adb devices it says "adb is not recognized as a internal or external command or bat"
Following the steps of manually installing driver I see some kind of warning in windows device management as you can check in this screenshot: https://ibb.co/gzVPbKQ
I tried to look for adb.exe but the one I found belongs to Xiaomi Mi9 phone which I used to remove Xiaomi Mi9 applications. I tried to run that adb executable but only detects Xiaomi phone and doesn't detect Orange Rise 52 phone.
What am I doing wrong?
EDITED: After installed those drivers, computer didn't recognize Xiaomi MI 9 phone, in some way destroyed Xiaomi Mi 9 drivers so even with system restore didn't work to recover a working Xiaomi Mi 9 connection so I had to restore a Aomei backup image so next try will be on a virtual machine where it doesn't affect these drivers installations to the ones I have or windows has. Is there any reason adb command is not working after installing adb usb driver for orange rise 52?
Regards and thanks.

---

knopfler1980 said:
Hello, I installed both drivers but when I run adb devices it says "adb is not recognized as a internal or external command or bat"
Following the steps of manually installing driver I see some kind of warning in windows device management as you can check in this screenshot: https://ibb.co/gzVPbKQ
I tried to look for adb.exe but the one I found belongs to Xiaomi Mi9 phone which I used to remove Xiaomi Mi9 applications. I tried to run that adb executable but only detects Xiaomi phone and doesn't detect Orange Rise 52 phone.
What am I doing wrong?
EDITED: After installed those drivers, computer didn't recognize Xiaomi MI 9 phone, in some way destroyed Xiaomi Mi 9 drivers so even with system restore didn't work to recover a working Xiaomi Mi 9 connection so I had to restore a Aomei backup image so next try will be on a virtual machine where it doesn't affect these drivers installations to the ones I have or windows has. Is there any reason adb command is not working after installing adb usb driver for orange rise 52?
Regards and thanks.
Click to expand...
Click to collapse
Sorry I didn't have usb debugging enabled. I will follow next steps, thanks a lot!!

---

knopfler1980 said:
Sorry I didn't have usb debugging enabled. I will follow next steps, thanks a lot!!
Click to expand...
Click to collapse
Hello again, I'm trying to reboot in fastboot but it doesn't work, phone boots normally.
I also tried a article I found that says you can also can start fastboot pressing up volume and power and stop pressing when bot appears but bot dissapears really fast that it's imposible stop pressing up and power, I only can see a menu in the phone that says recovery, is that fastboot? Also when I run command "fastboot devices" it doesn't detect anything because the phone didn't boot as fastboot using:
Up and power
adb reboot bootloader
Do you have any idea why is happening this?
I installed drivers from https://gsmusbdriver.com/orange-rise-52 but it doesn't seem to work with fastboot (computer detects it normally but not fastboot because I guess is not a driver problem but fastboot booting that is not happening)
Regards and thanks in advance!!

---

@knopfler1980
If no su binary is found on Android, then you have no root. So all you at least have to do is to install su binary in Android's /system partition. This can be achieved using ADB.
The command sequence is as follows
Code:
adb devices
adb disable-verity
adb reboot
adb devices
adb shell "mkdir -p /data/local/tmp > 2/dev/null"
adb push c:\su /data/local/tmp > nul
adb shell "chmod 0777 /data/local/tmp/su"
adb shell "-c '/data/local/tmp/su'"
adb shell "setenforce 0"
adb shell "mount -o rw,remount -t auto /system"
adb shell "cp /data/local/tmp/su /system/bin"
adb shell "mount -o ro,remount -t auto /system"
adb reboot
adb devices
adb enable-verity
adb reboot
The su binary is downloadable from here: download it and extract the version that matches your phone's CPU-architecture to root of computer's drive C:

---

jwoegerbauer said:
@knopfler1980
If no su binary is found on Android, then you have no root. So all you at least have to do is to install su binary in Android's /system partition. This can be achieved using ADB.
The command sequence is as follows
Code:
adb devices
adb disable-verity
adb reboot
adb devices
adb shell "mkdir -p /data/local/tmp > 2/dev/null"
adb push c:\su /data/local/tmp > nul
adb shell "chmod 0777 /data/local/tmp/su"
adb shell "-c '/data/local/tmp/su'"
adb shell "setenforce 0"
adb shell "mount -o rw,remount -t auto /system"
adb shell "cp /data/local/tmp/su /system/bin"
adb shell "mount -o ro,remount -t auto /system"
adb reboot
adb devices
adb enable-verity
adb reboot
The su binary is downloadable from here: download it and extract the version that matches your phone's CPU-architecture to root of computer's drive C:
Click to expand...
Click to collapse
Thanks for the help. I had a warning with the second step:
"Disable-verify" only works for userdebug builds
{
"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"
}
I will check on google.
Thanks a lot both for your support. I want to try sell my Xiaomi Mi 9 and Kospet Prime and buy a Ryzen 3900x and a motherboard, that's the reason I want to root the crap (sorry if someone has this phone) of Orange rise 52 because it's really slow.
Regards.

---

knopfler1980 said:
Thanks for the help. I had a warning with the second step:
"Disable-verify" only works for userdebug builds
I will check on google.
Thanks a lot both for your support. I want to try sell my Xiaomi Mi 9 and Kospet Prime and buy a Ryzen 3900x and a motherboard, that's the reason I want to root the crap (sorry if someone has this phone) of Orange rise 52 because it's really slow.
Regards.
Click to expand...
Click to collapse
I found this link https://stackoverflow.com/questions/38304435/how-to-enable-and-disable-dm-verity-on-android-devices that says:
"adb disable-verity will work only with adb version 1.0.33 and above. so upgrade your adb version"
So I'm going to try upgrade adb version in my virtual machine.
Thanks for the help guys!!

---

knopfler1980 said:
I found this link https://stackoverflow.com/questions/38304435/how-to-enable-and-disable-dm-verity-on-android-devices that says:
"adb disable-verity will work only with adb version 1.0.33 and above. so upgrade your adb version"
So I'm going to try upgrade adb version in my virtual machine.
Thanks for the help guys!!
Click to expand...
Click to collapse
Hi again.
I downloaded the latest SDK with latest adb version from here https://developer.android.com/studio/releases/platform-tools
I'm still getting the error
C:\platform-tools_r30.0.4-windows\platform-tools>adb disable-verity
disable-verity only works for userdebug builds
My adb version is as follows:
C:\platform-tools_r30.0.4-windows\platform-tools>adb version
Android Debug Bridge version 1.0.41
Version 30.0.4-6686687
Installed as C:\platform-tools_r30.0.4-windows\platform-tools\adb.exe
Is there anything else I'm not realizing?
Thanks in advance, I will keep searching.
Regards

---

knopfler1980 said:
Hi again.
...
I'm still getting the error
C:\platform-tools_r30.0.4-windows\platform-tools>adb disable-verity
disable-verity only works for userdebug builds
...
Click to expand...
Click to collapse
Signals that phone's Android isn't a user-debug build. Looks that phone's Android can't get rooted. But I'm not sure of this: all the phone's I had/have in use had/have a user-debug type Android OS.
FYI: You can query build type of your phone's Android OS
Code:
adb devices
adb shell "getprop ro.build.type"
BTW​: Android OS comes as one of these 3 builds
eng - Engineering build comes with default root access.
user - User build is the one flashed on production phones. Has no root access.
user-debug - User debug build does not come with default root access but can be rooted.

---

jwoegerbauer said:
Signals that phone's Android isn't a user-debug build. Looks that phone's Android can't get rooted. But I'm not sure of this: all the phone's I had/have in use had/have a user-debug type Android OS.
FYI: You can query build type of your phone's Android OS
Code:
adb devices
adb shell "getprop ro.build.type"
BTW​: Android OS comes as one of these 3 builds
eng - Engineering build comes with default root access.
user - User build is the one flashed on production phones. Has no root access.
user-debug - User debug build does not come with default root access but can be rooted.
Click to expand...
Click to collapse
Hi, thanks for your answer. I don't know what has happened but virtual machine is not detecting phone anymore, vmware workstation 15 pro problem. I was unable to see which's the problem. First started like 2 hours ago when physical machine without any changes didn't detect any of the phones, Xiaomi Mi 9 and Orange Rise 52. I checked windows device management and I saw that there was a problem with MTP driver, so I had to "update" (that's it's called in windows but I guess it installed it again) MTP driver for each phone. Now physical machine is detecting both but not vmware workstation 15 pro. I will keep checking it and I will try to run the command you adviced me.
In case Orange rise 52 is using a not compatible build, I will try again supersu method, but at the moment any of both will work until I get virtual machine detecting usb phone connection in VM -> Removable usb devices (it only appears 2 when I have 3 usb hard drives, one yubikey (hardware authentication) and identification card reader so it should detect 5 devices and it's only detecting 2).
Thanks for your time and help.