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.
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 have a quite strange problem on my HTC Hero (GSM).
Quite a while ago I flashed a backup of my stock 2.1 onto the phone because I forgot to titan-backup some apps, but in the process I seemingly somehow broke my recovery mode. Also since that point in time my superuser was ranting I should install an update of the su binary.
Now lately I tried some way to flash to cyanogenmod because of all the bloatware in stock HTC Éclaire. In this process I tried installing clockwork rom manager and titan. clockwork didn't have the rights to install recovery, regardless of the generally working root (universal androot states the device as rooted and at that point superuser worked as it should e.g. for ghost file manager and quikboot). So I googled and found that there was an alternative to superuser called supersu. I installed that after uninstalling superuser and that only gave me errors. Now I seem to have no working su bin, supersu only tells me anything I do fails and superuser gives me the following when trying to update the su bin (translated from German):
Downloading manifest... okay
Analyzing manifest... okay
Latest version = 3.1.1
Checking installed Version = legacy
Repairing database... okay
Unzipping sutools... okay
Checking current install path... /system/xbin/su
Downloading new binary... okay
Aquiring root access...
Remounting /system as rw... legacy
Copying su to /system... okay
Button saying "that was cool, do it again"
Click to expand...
Click to collapse
After that seemed not to work I tried flashing the recovery from fastboot, but that "remote operation" is "not permitted". Same goes for system remount via adb.
This means also, that in the current state I cannot flash a new su via update.zip as I don't have a recovery mode anymore.
Someone on the net suggested to install an OTA-update to fix most system files and reset root. Sadly the following update for my hero is buggy. It's a patch for the peep twitter client that broke my boot partition a couple of times before and every time I had to reset to Android 1.5 again via recovery - so I won't try it as I know I don't have recovery (only the red triangle of death)
Does anyone have any trick up their sleeves that could help restoring either the su bin or the recovery mode?
[edit]
just noticed I wrote a question about the semi-brick from the mentioned peep-update some time ago - including a solution. I will try that later on, but if someone figures something else so I can still backup my data before wiping everything I'd still be thankful for a hint.
[edit2]
I did reset the handset with a 2.1-RUU via hboot, but seemingly the recovery partition is still broken and I could not find a Clockworkmod Rom Manager-version that is a) running on 2.1 and b) actually working on my device to flash recovery and thus achieve anything... But at least I seem to have SU again, even though it is noted as outdated and I am unable to patch it.
Hello there,
Im not a expert for android devices but i have some basic knowledge.
My phone is a huawei g510 aka U8951...And i strongly suggest never buying these models,
So anyway i was trying to put a custom recovery and every time i did that was a failure, first off tried CWM it
doesnt show the supported list of my device so i went to choose other models, doesnt work.Tried it manually put and change in system folder with recovery doesnt work.TWRP ,used the goomanager through openscript doesnt work, the app is down and not in use anymore, tried manually same thing , got a pink screen in process.Tried for ages to make this work, searched google youtube everything doesnt work, cant get rid off the 3e recovery.Am i doing something wrong? The phone is rooted, the system is corrupted(No UI, missing gapps),
I just need any custom recovery for this phone to flash a custom rom , cant do anything
Any hackers/crackers/experts etc. with tips are helpful
Thanx in adv.
komplexphones said:
Hello there,
Im not a expert for android devices but i have some basic knowledge.
My phone is a huawei g510 aka U8951...And i strongly suggest never buying these models,
So anyway i was trying to put a custom recovery and every time i did that was a failure, first off tried CWM it
doesnt show the supported list of my device so i went to choose other models, doesnt work.Tried it manually put and change in system folder with recovery doesnt work.TWRP ,used the goomanager through openscript doesnt work, the app is down and not in use anymore, tried manually same thing , got a pink screen in process.Tried for ages to make this work, searched google youtube everything doesnt work, cant get rid off the 3e recovery.Am i doing something wrong? The phone is rooted, the system is corrupted(No UI, missing gapps),
I just need any custom recovery for this phone to flash a custom rom , cant do anything
Any hackers/crackers/experts etc. with tips are helpful
Thanx in adv.
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Official unlocking site: http://en.club.vmall.com/emotiondownload.php?mod=unlock&action=apply
TWRP 2.8 for Huawei G510: http://teamw.in/project/twrp2/170
komplexphones said:
Hello there,
Im not a expert for android devices but i have some basic knowledge.
My phone is a huawei g510 aka U8951...And i strongly suggest never buying these models,
So anyway i was trying to put a custom recovery and every time i did that was a failure, first off tried CWM it
doesnt show the supported list of my device so i went to choose other models, doesnt work.Tried it manually put and change in system folder with recovery doesnt work.TWRP ,used the goomanager through openscript doesnt work, the app is down and not in use anymore, tried manually same thing , got a pink screen in process.Tried for ages to make this work, searched google youtube everything doesnt work, cant get rid off the 3e recovery.Am i doing something wrong? The phone is rooted, the system is corrupted(No UI, missing gapps),
I just need any custom recovery for this phone to flash a custom rom , cant do anything
Any hackers/crackers/experts etc. with tips are helpful
Thanx in adv.
Click to expand...
Click to collapse
Do you have an unlocked bootloader?
If yes you can try to install a recovery by using adb.You can find the correct partition and install it with dd command from root shell.If you have a working shell give those commands:
Code:
adb shell
su
cat /proc/mtd
If the last command doesn't work try this:
Code:
cat /proc/emmc
After that copy paste everything it prints.
Check here how to make the proccess right.
You can find a twrp recovery here and a cwm recovery here.
Hi . Ive already unlocked my E2312 , and rooted with an app . But the problem is i cant seem to get into adb fastboot mode to flash the custom recovery
any ideas ?
Which app you use for rooting? There is good topic in forum for rooting and installing of TWRP (Recovery) - you need to follow all steps inside. Before this check that all adb drivers are successfully installed and working on PC.
Ive read what i can to open at least into adb mode but to no avail haha
I cant open into bootloader mode , no recovery mode even if i already unlocked it.
I tried rooting it with the one click app roots since i cant get into recovery mode, i used kingoapp . got my root , and tested some rooted apps like titanium backup and flashify . All seem to work normally
I tried using flashify to flash the recovery.img but as soon as i tried to pick the image inside my internal phone , the app got stuck . But besides that if i were to pick any other settings it would be just fine .
P.S M4 Aqua E2312
If you can't open adb then maybe drivers are not installed correctly on PC. Which operation system you use - if it's windows 10 then there is special procedure for installing. You need to disable drivers checking by windows to be able to install them - use Google to find how. After successfully installed drivers you need to approve connection with PC on your phone - message will appear on the screen of phone. After this you can install kernel and TWRP via adb.
This is the only way to root our phones. I also try Kingroot and one click root app at the beginning but it won't work properly.
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.