I had my phone rooted and and a few mods installed for the past while. I didn't like them so I went back to the origional Rogers ROM. I hated it, so I wanted to try out ICS for my phone. I can't get it to install CWM though. I've tried re-rooting it (and it completed, as far as I can tell). It should still be unlocked, again, as far as I can tell.
I've followed everything on http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
I've downloaded and isntalled Superuser repeatedly
and I've downloaded and isntalled CWM repeatedly.
when I try to "fix permissions" in CWM I get An error occurred while attempting to run privaleged commands!, but at the bottom it says complete.
Then when I try to restart in recovery mode I get
E:failed to verify whole-file signature
E:signature verification failed.
and then it shows that it's restarted in Samsung's recovery mode.
any ideas?
mac_angel said:
I had my phone rooted and and a few mods installed for the past while. I didn't like them so I went back to the origional Rogers ROM. I hated it, so I wanted to try out ICS for my phone. I can't get it to install CWM though. I've tried re-rooting it (and it completed, as far as I can tell). It should still be unlocked, again, as far as I can tell.
I've followed everything on http://forum.xda-developers.com/showpost.php?p=25526643&postcount=2
I've downloaded and isntalled Superuser repeatedly
and I've downloaded and isntalled CWM repeatedly.
when I try to "fix permissions" in CWM I get An error occurred while attempting to run privaleged commands!, but at the bottom it says complete.
Then when I try to restart in recovery mode I get
E:failed to verify whole-file signature
E:signature verification failed.
and then it shows that it's restarted in Samsung's recovery mode.
any ideas?
Click to expand...
Click to collapse
A couple of clarifications.
1. Rooting a phone only gives you access to root files (the OS). The superuse.apk, the su files.
2. Stock kernel do not give you the ability to flash insecure zip files. An insecure custom kernel is needed for this.
3. You don't need root to flash an insecure file in a modded cwm.
You are trying to flash an unofficial firmware or insecure *.zip with a secure stock kernel - not going to happen. There are two different ideas altogether.
To have the insecure cwm you are looking for, you need to flash the kernel on that post while in download mode.
Put your phone in DL mode. Flash the kernel then boot into modded cwm recovery
thanks for getting back to me. I had to step out to get some things before the stores closed.
doesn't Entropy's 4.4.2012 kernel do that though?
mac_angel said:
thanks for getting back to me. I had to step out to get some things before the stores closed.
doesn't Entropy's 4.4.2012 kernel do that though?
Click to expand...
Click to collapse
Yes it does. But you don't have it installed.
that's the SGH_I997 Entropy 4_4_2012-One-Click-Heimdall file that runs in Java? I've downloaded that and ran in repeatedly. Keeps saying completed and reboots the phone no problem.
I'm about to reboot in Samsungs recovery mode to try to flash the CWM-Superuser Busybox Root UCLB3 file. I'll wait for your response first.
mac_angel said:
that's the SGH_I997 Entropy 4_4_2012-One-Click-Heimdall file that runs in Java? I've downloaded that and ran in repeatedly. Keeps saying completed and reboots the phone no problem.
I'm about to reboot in Samsungs recovery mode to try to flash the CWM-Superuser Busybox Root UCLB3 file. I'll wait for your response first.
Click to expand...
Click to collapse
I don't remember if mac will flash the kernel correctly. If you check the CPU info and it shows entropy kernel and not the stock kernel, you should be able to boot into cwm recovery with the three finger technique. It will be a red recovery.
If cwm is blue, entropy is not installed.
If you are looking to install a different firmware, there is no need to root. Just flash the firmware you want in cwm. Chances are, the unofficial firmware is already rooted.
mac_angel was a nick I created about 18 years ago when I worked for Apple Canada. I haven't worked with a mac in God knows how long. My last IT job was IBM, lol.
Anyway, I'm not sure what happened. I went to restart in the Samsung's recovery mode again to flash with that file I mentioned and it booted in CWR. I cleared all the dev cache and everything, and flashed the ROM I had already moved over. Phone is still restarting, but it looks like I might be good. I didn't do anything from the time I first posted to now though, lol. I was about to try to flash that file and it worked. Only thing I can think of is that before I was always trying to restart the phone in CWR mode by selecting it to reboot in that mode from the application instead of the three finger salute (oh, wait, that's M$).
You got it going?
yes, thank you. Not sure if you can do it, but the thread can be closed now. Thanks for getting back to me, as well as your other great posts.
I did a factory image install of the latest from nVidia then let it update to 5.01. Made sure it was unlocked, put CWM on it, was able to go from bootloader into CWM, installed SuperSU, rebooted. No root. Went into recovery ... and it's the stock recovery ("No command"). Tried this multiple times in multiple ways and no matter what happens, once it boots into the system, CWM is gone.
Is this something I've done wrong or is this something to do with 5.01? I don't understand how it can be the latter given that I'm not seeing anyone else with this problem. Help!
Solved
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.
kmellis said:
Okay, I am an idiot. The problem is that I wasn't using the beta SuperSU (BETA-SuperSU-v2.42.zip) which is needed for Lollipop if you're not using a custom boot.img. I was doing neither.
Click to expand...
Click to collapse
can you help me out? Im getting the image of the android on its back with a red triangle and "no command" under it.
not sure if im even doing it correctly
EDIT: Never mind I got it working just had to use the cmd prompt to flash once I did "adb reboot bootloader" from there I followed the steps. thank you everyone who made this possible.
Everytime I attempt to flash from a zip file in recovery mode I get operation aborted and error message. I never abort it. I have unlocked my bootloader and s-off my phone. I noticed in recovery it says (Tamper) and ideas how to bypass this message. Its annoying and I am unable to install a custom rom due to this. I have been using weaksause to root while phone is on and SuperSU will not install continues to give error messages. I am not sure what I am doing wrong. I have googled and tried so many ways without luck. I am a noob at most of this but have used google a lot and understand quite a bit but I am lost.
I'm having some trouble guys. I got stuck in a bootloop when trying to install https://forum.xda-developers.com/oneplus-6/development/kernel-elementalx-op6-1-00-t3799054 this kernel, so I booted into TWRP and tried to flash the stock rom to fix it. However, it won't work and keeps giving me the error " Updater process failer with ERROR: 255 Error installing zip file '/sdcard/Download/OnePlus6Oxygen_22_OTA_009_all_1805172226_f7d1518e0 e704ca3.zip' ". How can I fix this? I read something about sideloading the OTA update, but it says it won't work if I'm rooted, which I am.
In you do not mind s fresh start lock your boot loder
Do NOT reboot then unlock your boot loader.
This will rest your phone back to stock.
You may have to sideload stock boot.img (maybe)
Hope this helps.
You can't flash OOS through recovery. Also since kernel only affects the boot partition, just flash stock boot and it should work.
Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance
nickglas said:
Hello,
My phone(Samsung galaxy s8) just had a crash and is stuck on the blue screen with "Installing update". After several seconds the screen goes away and boots straight into the recovery mode.
The log that i see in the recovery is :
Fail to open recovery_cause(No such file or directory)
Failed to mount /efs
Unknown volume for path /odm
dm-verity verification failed
I tried to install the stock firmware (I cant link to the webpage but im 100% sure its the correct one) but it wont boot and goes to the "Installing update" again and after that to the recovery.
I tried installing twrp but it wont install due a FRP lock. i read that you should wipe your data and factory reset. Also tried that but again no succes.
Can someone please help me.
Thanks in advance
Click to expand...
Click to collapse
I'm going to take a guess here, you had the device rooted and then you tried to apply an OTA stock update while the device was rooted? Tyically, stock OTA updates can't be applied to devices that have been rooted because the updates require the device to have an unmodified system partition(no root) and they require stock recovery instead of custom recovery. There are "some" devices that can apply stock updates while rooted, but those are few and far between.
If that is what you did, you need to do some searching for repairing failed OTA updates on rooted devices.
Sent from my SM-S767VL using Tapatalk