Hi, whenever I go to a file manager on my phone and select the root access, it says the test has been failed and does not grant me access. I have rooted my phone using hasoon2000's aio kit. I have supersu on my phone however whenever I press something it says 'installation failed'. Can anyone help? Thanks
do you have supersu installed on the phone or do you only have it on the phone as a zip file.. because the AiO toolkit does not flash super su, it just places the file on your phone for you to manually flash it in recovery... try flashing the file from recovery again and fix permissions after and see
Ninjistix said:
do you have supersu installed on the phone or do you only have it on the phone as a zip file.. because the AiO toolkit does not flash super su, it just places the file on your phone for you to manually flash it in recovery... try flashing the file from recovery again and fix permissions after and see
Click to expand...
Click to collapse
I have supersu installed on my phone. I installed it from twrp recovery. And fixing permissions? What do you mean?
i don't know how many times ive said this... but use 4ext for htc devices it was made for htc devices and most roms are tailored to flash flawlessly with 4ext... and your recovery should have an option somewhere to "fix permissions" i don't use twrp so i cant tell you where to find it...
Related
I've been trying to install a custom rom to my htc hero (gsm) but it seemes like i can't root it properly.. i've used androot to root with, and tjecked if the mobile was rooted through busybox and various apps, and it all tjecks out, it gives su permission to the android terminal, and i can delete obligatory apps that i dont need from the phone without a problem, but when i try to setup another recovery to install custom roms im stuck, the terminal can't go that far.. just trying to reboot from the terminal isn't allowed..
So have anybody experienced the same issue?
and idea what to try next?
There was the same thing with my phone
Then I found a thread which said there are several different ways to apply recovery.zip. some of them difn't work for me either. Now I can't remember which method worked for me, but I'll share tgat thread as soon as I get to my notebook just wait for it
Sent from my HTC Hero using XDA App
ok, this is how I have done.
put the recovery.zip in SD card
run Androot and do ROOT.
run Terminal Emulator.
execute the following commands
su (wait for superuser request and accept it)
flash_image recovery /sdcard/recovery.img
the reboot command won't work, so just turn off the phone and boot into recovery (Home+Power)
that's it.
If this method doesn't work, try this one
do Androot
run ROM Manager
press "Flash clockwork recovery"
grant superuser permissions
wait
boot into recovery
And another way to apply recovery via Droid Explorer
download and install Droid Explorer on your PC
USB Debugging must be turned on in the phone
connect via usb and run the program
coose Flash Recovery Image plugin and fill th path to recovery.img
It should do the job...
you sir. are awesome!
i've tried the two first methods before, they didn't work
but the last one did
another question now:
im in the system recovery and i've done everything i need to install a custom rom (cyanogenmod) but it stops installing:
E: No signature (775 files)
E: Verification failed
Installation aborted.
what to do now?
first of all, I'm not a Sir. I'm a Miss
and I'm glad I helped you
and third. Personally I haven't tryed cyanogenmod, so I'm not sure why the install package couldn't be verified. Try redownloading the zip. Maybe it is corrupt. If not, did you follow ALL these steps? I found it in this thread with the same question as yours. And he solved it this way.
Hope this will help...
hmh didn't expect that, and your quite smart too ^^
it's way my own fault, i repacked the zip that was the problem
cyanogenmod is damn nice
though it's the first rom ever to try out, it seems stable enough..
it's just good to fully control your own device
thanks
And yeah, cyanogen is nice
Sent from my HTC Hero using XDA App
FIX ::D
LMFAO was about to post that same thing arvan had (in my own words) till i actually read the whole threat.
THanks to Arvan its exactly how u fix this issue
]Verification issue
flash clockworkmod recovery 2.5.0.7 by installing rom manager and pressing on the option
to fix the signature issue press on install zip from sd, then on toggle signature verification on your clockworkmod recovery if u have this. if not try flashing this recovery image its very complete and useful
then choose form sd and as it says choose your rom and flash and reboot
there u go
have a good day
Wishhes the best for your hero
~Jseb
HEro deV
i'm quite confused. I believe my phone is partially rooted. I installed SuperSu but it says that i do not have the Su Binary installed. under root checker it says that supersu is not installed but busybox is. I successfully installed Root Explorer and am able to view system files but not edit them.
anyways, i got a verification error when trying to flash CWM-supersu in recovery. I followed al the steps and downloaded all the required recovery.img files etc. I am tempted to flash a custom rom. but afraid if it gets locked up during the process, as there is no back up option with the stock recovery.
Any suggestions?
swift2fly said:
i'm quite confused. I believe my phone is partially rooted. I installed SuperSu but it says that i do not have the Su Binary installed. under root checker it says that supersu is not installed but busybox is. I successfully installed Root Explorer and am able to view system files but not edit them.
anyways, i got a verification error when trying to flash CWM-supersu in recovery. I followed al the steps and downloaded all the required recovery.img files etc. I am tempted to flash a custom rom. but afraid if it gets locked up during the process, as there is no back up option with the stock recovery.
Any suggestions?
Click to expand...
Click to collapse
Update the binaries in superSU settings or reinstall root with CF-Root with Odin, see item 1 in my signature.
gee2012 said:
Update the binaries in superSU settings.
Click to expand...
Click to collapse
will not allow it. "It says that SuperSu can not install it. There is a problem"
I'm on Android version 4.0.4 firmware BULF1
swift2fly said:
will not allow it. "It says that SuperSu can not install it. There is a problem"
Click to expand...
Click to collapse
Yes, flash CF-Root with Odin.
Update your busybox to latest version.then update the su..it will work
Then cwm problem can be solved by using a manual cwm(new cwm from someone)...
gee2012 said:
Yes, flash CF-Root with Odin.
Click to expand...
Click to collapse
ok i will look into that. i gotta find a PC. I've successfully rooted 2 S3s with the method i use on mac but for some reason it's not working on this current phone i'm trying to root.
Really didn't want to make a new thread about this but honestly people just jumped to conclusions without being helpful in my previous thread.
Long story short I'm trying to manually get 4.4.2: http://forum.xda-developers.com/showthread.php?t=2664561
I saw that I needed to get s-off, which requires root. Bootloader was already unlocked and so did everything here: http://forum.xda-developers.com/showthread.php?t=2273376
I installed CWM. It said to install a superuser tool so I installed SuperSU.
"You're not out of the woods yet! The stock kernel is system write protected, so you still can't modify it (changes won't "stick"). You'll have to flash a custom rom or a kernel if you want stock instead." was the next line. <-- I saw that message. Installed a kernel that he recommended: http://forum.xda-developers.com/showthread.php?t=2255900
After reboot I get SuperSU error: There is no SU binary installed and SuperSU cannot install it. If you just upgraded to Android 4.3, you need to manually re-root- consult the relevant forums for your device etc.
Can anyone help me get the proper SU Binary installed? Not a beginner to rooting as I've had had several previous phones before. Never encountered something as annoying as this.
On 4.3, 3.17.502.3.
I had the same issue when I installed 4.4.2 on my international One.
What I done to root was;
- downloaded SuperSU v1.80 zip from here.
- download SuperSu from the Play Store
- in SuperSU, select the option to install binaries via TWRP/CWM. (If it doesn't reboot to recovery, manually enter recovery)
- flash the supersu v1.80 zip and reboot
- open SuperSu and install the binaries using the normal option.
That then enabled my root. I'd tried quite a few different variations and this was the only method that worked for me.
Sent from my HTC One or Note 3 via XDA Premium 4
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
mch277 said:
Thank you! Although I just managed to installed a custom ROM and managed to get root.
I followed this thread: http://forum.xda-developers.com/showthread.php?t=2664561
I flashed the Recovery_Cingular_US in fastboot. Unfortunately I'm unable to boot into stock recovery. I've been told right after you enter recovery from bootloader you press all three buttons simultaneously?
Is there a way to get into stock recovery from fastboot? Or better yet install the ROM from fastboot?
Click to expand...
Click to collapse
You seem very confused about the whole rooting process ... what was the point in flashing the stock recovery ? Are you trying to install the OTAPkg.zip ?
what Rom are you wanting to install and whats flashing stock recovery have to do with it ?
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
mch277 said:
Well, if you looked at the thread I linked, you'll see that it says to flash a stock recovery file in order to install the OTAPkg.zip
Click to expand...
Click to collapse
I wrote the thread you linked too
http://forum.xda-developers.com/showthread.php?t=2659374
and yes it is necessary to have stock recovery to take an OTA, but your post didn't mention taking OTA it said you had no SU installed.
to get into stock recovery
boot to bootloader
choose recovery
wait for black screen, hold vol up and then power
you will see something about sdcard fail .. ignore it till the menu comes up
then choose to flash OTAPkg.zip from sdcard
Just got a uhappy up580 mtk6580 5.1LP phone.
All sorts of problems with it if I try to do anything with it, as stock it works great, no issues. Install kingroot as thats the only way to root it, Ive tried them all... Cannot remove kingroot for super SU using ANY way including superSUme, all things on here and needrom etc... cant do it.
I cant unlock the bootloader using everything I've found on here, from simply selecting it in settings to ADB on the PC and terminal in root shell, says 'not permitted' or 'not allowed' or rewboots to a selection screen and the volume up button to select it wont work.
Cannot remove install.recovery.sh using an old esfile explore, root explore, adb root shell on PC and terminal etc... all say, not permitted or 'system is r/o' Used commands to r/w system but again, this isnt allowed/permitted.
Installed chainfires 'secureADB' I think it was called to allow ADB to to be used root in system, does nothing.
MTKdroidTools doesnt work on MTK6580 so cant get CWM recovery flashed that way.
Have downloaded numerous CWM/PhilzTouch/TWRP and tried to flash them with SPtools, and removing battery before rebooting recovery and that also, doesnt work.
MTKunpacktools cant unpack the recovery.img of stock rom....
Am really at the end of my tether now.
I have the full stock rom installed, and a full SPFlashTools stock back-up if anyone has any ideas? All I'm really wanting is Xposed installed, thats it, and know with another chainfire app I can flash a zip without a recovery, but needs super SU which I cant get installed....
Dont worry, sorted it.
I never post for help, but I am at my wits end.
I have a Vodafone tablet that's running 6.0 marshmallow that refuses to root. I did find a TWRP recovery compiled for the device, which I installed using SP Flash Tool.
TWRP seems to work as expected. I can make and restore backups, format partitions, mount system, delete files with the file manager and so on.
TWRP is also kept on every reboot. It never replaced by the stock recovery.
However, when I try and install the SuperSU zip 2.82 to root the device, it seems to be successful. However, when I boot into Android and open the SuperSU app, it says,"SU binary occupied" and closes.
That error is displayed when installing 2.82. When installing versions like 2.79, it shows the option to install the SU binary, again like normal, but it always fails to install the binary.
Using a root checker app from FDroid tells me the same thing, that root isn't avaliable. TWRP flashing should be working though, since I can flash busybox and it is detected correctly by the same root checker app.
Other root apps refuse to work.
Whilst in TWRP, I am able to browse the file system and the su file is located in system/xbin, again like it should be. Numerous other files from busybox are also located there, further signalling a successful flash. I can chmod 755 the su file without issue, but it doesn't fix anything.
The bootloader of the tablet is unknown to me. I can't boot into fastboot or bootloader mode. Trying to do so just reboots the tablet. Nothing is shown on the screen either, and it boots to Android again. I did enable ,"OEM Unlocking" in developer options.
Any ideas what I can do? I really want to give this device a thorough chance, since it is a surprisingly enjoyable device to use, and for the price I paid it's almost a total no-brainer.
I just want root so it can become a total no-brainer to own.
Thank you for your time.
I figured it out.
I tried installing Magisk by patching the boot.img within the app and flashing it via SP Flash Tool, and it worked perfectly.
I never thought of using that, but I am glad that I did.
So, yeah. Use Magisk.