Hi I just bought a iHTC One 4G+ Android 2.3.6 Kernel 2.6.35.7
Build number HTC One 4G+ 20120402-111302
I am trying to root my phone but so far unsuccessful. I have tried many rooting apps eg Superoneclick, Unlock root, HTCSupperToolV3, etc Please advise how I can root my phone.
Also do I need to do S=off ? If so please advise how to do it .
Thanks
Updates : I have also tried to use adb commands to root the phone. When I tried to push the Gingerbreak_V1.20.apk into the phone /data/local/tmp , it is unsuccessful. The msg I go is that permission denied. The tried to use adb command to mount the system partition as RW. The error I got is mount operation not permitted.
Have also been trying SuperOneClick many times. It fails on pushing Busybox to phone /data/local/tmp. I notice the error msg says Permission Denied. No such Directory. Using Total Commander cannot open the Data directory. On checking permissions shows Owner : RWX ; Group : RWX ; World : X only
Also have found somewhere in this forum saying that Gingerbread 2.3.6 cannot be rooted. Is this true ?
Please advise
Related
Hello,
Thank you for the tips form the Leagoo Lead 3 forum: I wasn't able to post there so I do it here;
I don't know how to relate my own tasks to achieve this:
At least I followed steps 1 and 2: Step 1 was never finished: hangs or failed error message:.
With Kingo Root, always ended up with failure message except the last time:
I was able to root successfully;
Before to successfully root with Kingo Root:
- After several trials with steps 1 and 2. I ended up with Lead3 being rooted as displayed on Kingo Root status, But I wasn't able to use su;
- Once Kingo root status was root, I launched mtkdroidtools 2.5.3, freshly reinstalled(ie I renamed my former version installation), Lead3 was correctly detected with green light, No Root button but ADB. I made a backup and installed SuperSu with this tool:
I clicked on ADB. Type adb shell, it gave me # root access inside Lead 3.
But on standalone, Lead 3 stayed as not rooted (default.prop ro.secure=0). Secure mode. Thank you to the Insecure forum: And the guy who explained clearly on one his article, just google 'android insecure mode' and ' Root any Android device - Whiteboard Web'.
- Last trial with Kingo Root: Root was successfull.
And I still don't understand ,,,,
- I checked Lead3, it's rooted. SuperSu, Xposed framework work Ok, and su in the terminaluf.
ps: The device manager shows android device with Alcatel ADB driver. and sometime Android ADB, depending on which tool I used.
NB:
I forgot to mention that during the rooting trial, with adb and terminal, I saw busybox was installed, at leat links in the filesystems I was able to mount -o remount, rw /system and / in order to change default.prop content (sed ,,,,). Strange isn't it ?
Baffled ,,,
But as curiosity is still here and pocket minded, I'll shop more of those phones.
Leagoo Lead 3 is really nice phone. As long long as I can control ...
Hi,
I've been trying to root my Argos Bush MyTablet 10.1" running Android 4.4.4 for a while now, but all the rooting methods I have tried didn't work.
Framaroot (The exploit didn't work)
Key Root Master (I don't understand, since it's Indonesian, but some kind of error popped up.)
Root Master (Failed to root.)
iRoot (Failed to root.)
TowelRoot (device not supported. I tried using different modstrings, but they all turned my screen gray and rebooted my device.)
I have no access to a computer.
Argos ac101bu
Hi,
Really struggling to root this tablet. I have spent around 4 days trying.
I first altered the boot.img and set it up for adb.
ro secure = 0
allowmock location = 1
constant usb device = adb
ro debuggable = 1
This stops the "cant use adb root on production builds".
However, when I do adb root, it just says restarting adb as root.
It disconnects and then adb cant see the device, I have checked the drivers and its still there.
The device changes to "class for rk device", I tried lots of different drivers, but nothing seems to work after using "adb root".
I then also altered the system.img and made these changes.
ro factory location = 2 <-- which should use external SD (also added media,rw to permissions).
ro rkadb root = 1
ro secure = 0
I also manually installed SuperSU and set all the correct permssions. chown 0.0 and 06755 (in both xbin and bin).
SU works but SuperSU apk cant see the SU binary for some reason and doesnt show grant permission option. So its bassically useless.
Very frustrating, can anyone help?
EDIT:-
Got it rooted now, adb root still wont work. However I managed to manually root by following SuperSU v1.93 update script. Had to mount system.img in linux and edit that way.
Hi .. I also have got one of these... how did you manage to get it rooted???
Cheers
tron1275 said:
Hi .. I also have got one of these... how did you manage to get it rooted???
Cheers
Click to expand...
Click to collapse
Sorry for not answering sooner. I have the custom system image, if you still need it.
Its around 1.6gb, you have to flash it via rockchip flash tools. I also tweaked it some more and added init.d support.
I had rooted Celkon Q 500 with some method, I do not remember exactly. May be Root Genius. For some reason I unrooted using SuperSu. I wanted to re-root. But I am finding it difficult. ( I have not got any OTA update after rooting)One root checker says it is rooted, another says it is not. I can explore files in root explorer of ROM Tool Box Pro I had installed earlier. But I can not reboot through ROM Tool Box Pro. One root checker provided me this information : subinary available via $PATH null null, then in the next line it says : -rwsr -sr -x root root, subinary location is system/bin/su. Second thing it says : I have installed two busybox one at (a) data/local/busybox and another at /system/xbin/busybox. I had tried to un-install and re-install SuperSu and Busybox 2/3 times. Then after opening Supersu I got an erratic message : su binary needs updating and when Itried to update it , it failed several times. One root checker app says ADB root is available, Root Genius says root available. So, I am quite confused. I do not know how to go about it. I will be thankful, if somebody guides me in right direction.:crying: (I also found a root checker app said SELinux enforcing.)
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Eversmile23 said:
After rooting we instal busybox and SuperSU (or Superuser) and avail the benefits of rooting. When we unroot through SuperSU, is it possible that 'su' still remains inside '/system' folder? I came across a strange phenomenon : I rooted my Celkon Q 500 ( by Root Genius or One-click method or something else, I do not remember) and installed many root apps. After somedays, I decided to unroot, I uninstalled super su, busybox. Then, I tried to root it again. But, I noticed that one root checker says ur device is rooted(specifically through Root Genius PC software I got the message rooted and pressed the 'unroot' button, but it said failed), 2nd root checker says it is non-rooted, 3rd one says it has root access through ADB. I checked 'su' is present in some folder inside '/system', which could not be deleted , because I think, I do not have RW privilege. I had tried many method to root it again, but all failed. When I open Supersu, it throws an immediate message that 'su binary' needs to be updated and when I try it fails everytime. Can anyone meke me understand, what is the real proble.? Celkon Q 500 is Broadcom chip based, running android 4.4.2. Also I found One message in the root checker that "SELinux enforced".
Click to expand...
Click to collapse
reinstall super su from play store go to settings in super su app and unroot there
selinux enforced means that your kernel is not permissive. has nothing to do with root
Hello,
I need some help on rooting my minnowboard max turbot base on Android 5.1.1
I followed the Intel tutorial to root minnowboard max from here "https://01.org/android-ia/user-guides/rooting-android-ia-user-debug-builds-minnowboard-max"
I have an error "Binary su not found" when I copied it in /system/xbin.. So I moved it on /system/bin ; when I execute, Android finds the binary but does nothing.
here is the output :
[email protected]_max: su
1
[email protected]_max: (I was expecting a '#' here...)
Also when I try to update the binary with SuperSU, it tells me that "no binary found, it's a problem..."
If anyone can help me on this... I really don't know how to do it:crying:
Thank you all