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.
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Kleo2 said:
Hi guys,
I'm running my Moto G 16GB on Kitkat 4.4.2 system version 175.44.1.falcon_umts.Retail.en.DE. Today it offered to download and install the latest OTA update (called 176.44.1.en.DE). I started the download and tried to install it.
After downloading the update was placed in /cache. The file name was 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE.zip', which surprised me. I was expecting something like 'Blur_Version.176.44.1.falcon_umts.Retail.en.DE.zip'.
When I tried to install it without removing root and without going back to stock recovery it ended with a signature error in CWM. Installing the untrusted zip manually didn't work as well - as expected.
Then I tried to follow advise from other threads and went back to stock recovery (extracted from a full install package 'Blur_Version.175.44.1.falcon_umts.Retail.en.DE' - 444MB) That seemed to work and the install of the OTA update went fine before getting stuck on the boot animation on the first boot. It sat there for 10 minutes before I rebooted and restored a CWM backup.
I'm running out of ideas. Some say it's sufficient to go back to stock recovery temporarily. Others say you need to go back to full stock.
I have to repeat that I'm rooted and that I've de-activated a few unused apps (mainly harmless google stuff (hangout, search, music and so on) and Motorola Assist, Migrate and 'Context Services') .
Are there further findings about what stops the OTA from succeeding?
Many thanks in advance,
Kleo2
Click to expand...
Click to collapse
If your phone is rooted or there is a CWM installed or there is any change in system files then ota will fail till you flash stock rom. You can't just bring back stock recovery. You have to "delete" root as well.
There is some info http://forum.xda-developers.com/showpost.php?p=47495650&postcount=6
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
CromoPT said:
I will post my case here, I had the same problem, I had CWM and root and when I rebooted to update I get installation failed and boot loop.
Then I just flashed stock recovery (only) rebooted and now I already have the update installed
Click to expand...
Click to collapse
Hi, thanks for your replies. Because of your report and others, who state the same (installing stock recovery only to get the update working) I was hoping to get around going back to full stock. It always takes a lot of time to configure the phone the way it was configured before essentially wiping.
Just to repeat what I did: when I try to install the OTA while CWM is installed there's just an error message in CWM, the update fails, but the phone is working normally afterwards. It's just not updated.
When I try with stock recovery the update process finishes without errors, but the phone get stuck during the boot animation.
Maybe there's a way to fix the boot loop?
Looking forward to any suggestions
Cheers, Kleo2
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Kleo2 said:
I tried again and found a way without going back to full stock.
Click to expand...
Click to collapse
Thanks. :good: Did 1 to 3 and phone booted just fine (not stuck on boot animation)
My phone: No logo fix, root, Xposed Framework
After update root was still there, Xposed needed a new install
total noob
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Papshmir said:
i would so much like to update my rooted moto g.. because of my card reader.
does anyone know a step-by-step-for-complete-noobs-post and could provide a link?
i'm just starting.. and so happy and proud that i got my phone rooted.. and that i got rid of this rebooting problem by erasing the cache.
but i'm already lost when i read "flashed stock recovery".. yeah i know: that much noob!
help would be much appreciated!
Papshmir
Click to expand...
Click to collapse
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Thanks!
Kleo2 said:
I tried again and found a way without going back to full stock.
1. flashed stock recovery from full 175.44.1 image
2. let the phone download the OTA and restart to install it
3. ota install in stock recovery went fine
4. reboot -> stuck on boot animation again
5. flashed CWM and wiped cache AND dalvik cache
6. next boot took longer than normal but got past the boot animation
7. android optimized/cached my apps and then started normally
8. version is now 176.44.1 and the phone seems to work normally (after 30 minutes of usage)
Hope that helps someone and that I won't have issues going forward because I did it this way.
Cheers, Kleo2
Click to expand...
Click to collapse
Thanks,
Wiping cache and dalvik cache did the trick for me. You saved my day
Please please help
I have the same problem. I've tried to update the new OTA and failed. After restoring full stock rom, the system simply doesn't boot!
I had Faux Kernel and GravityBox but I didn't revert anything. I thought that a full stock rom would clear all system settings.
This is my version of stock (Blur_Version.174.44.9.falcon_umts.Retail.en.GB) and I tried to flash it several times now. No success. I get stuck on the boot logo.
I tried to downgrade to 4.3 using version Blur_Version.14.71.8.falcon_umts.Retail.en.GB. I was able to boot and see the initial setup but I have no WIFI! I was trying to install 4.3 then try to update via OTA but OTA only works with WIFI so I'm stuck.
I also tried installing the 24th Feb nightly build of Cyanogen and the device also booted but with no WIFI.
I really don't know what to do! Please help me. I've tried other stock images out of despair but none with sucess.
Does anyone have a clue to what might be to problem and how to revert it?
Thank you
draco259 said:
So I am trying to put back my stock recovery so I can take the OTA, but after I flash the recovery and try to reboot to it, it says "No Command". I have reflashed TWRP and then the stock recovery again with the same result. The phone itself will boot fine, but I can't install the OTA as it gets an error part of the way into the install. Any ideas? I have the 1034.
EDIT: Well I remembered I did the H+ mod, so after reverting that the OTA flashed I had Faux Kernel before hand, but after reflashing it my wi-fi wont enable, any ideas?
Click to expand...
Click to collapse
Before flashing stock ROM try to clear/format all your partitions with a custom recovery!
Sent from my XT1032 using xda app-developers app
I installed the OTA update using the CWM recovery but not root, I changed the update-script to not give error during installation
Hui91 said:
I UPDATED my rooted Kitkat Tesco version SUCCESFULLY! and still rooted.
What I did:
1. install Motorola Device Manager (RESTART computer and telephone)
2. downloaded MotoTool
3. Made a Nandroid backup in CMW, made a backup with MotoTool too. Just in case
And deactived (did not uninstall) my Xposed framework modules (if you dont have it, you dont need to)
I have some system apps disabled, but didnt re-activate it. (was too lazy haha)
4. downloaded the correct ROM from: http://sbf.droid-developers.org/phone.php?device=14 (Tesco UK 4.4.2)
5. unzipped the ROM and rename and overwrite the recovery.img to the exact name as in the MotoTool All In One 2.6\Data\KitKat\StockKitKatrecovery.img (Just for sure it's the same as my ROM, I dont know if all the ROMs have the same recovery sooo )
6. started MotoTool, unplug&replug device. Checked KitKat option in the program, did a connection check, it was okay. Did a NORMAL restart via progam. You have to grant permisson on your phone.
7. after reboot, rebooted the phone to FASTBOOT.
8. Checked Stock Fastboot in the program, it flashed succesfully. Then I went into recovery (1×down volume, then 1× up volume) checked if the recovery was working. It was working (android logo+ no command error message)
9. reboot (long press power button)
10. Updeted OTA, settings/inf./update.. blabla okay okay next next. Wait until it downloads (only 7.9 MB )
11. wait for the update to be done, then it reboots, then apps are being updated. Everything looks fine and working
+1 flash CMW or other recovery again.
Hope this helps! I was afraid to do it too. I'm not used to MotoTool and other Motorola stuff because I had a HTC Desire, it was much simplier with that. But no risk here either! Good luck!
Click to expand...
Click to collapse
At part 8, I am getting an image of the android guy with his stomach open with a big red '!'. That's 'no command' right?
Any ideas? I have no idea what I am doing
Guys, a really easy way to update is:
1. Install Philz recovery - http://forum.xda-developers.com/showthread.php?t=2639583
2. Reboot and then download the OTA update when prompted - select Install when prompted
3. It will now reboot into Philz recovery, install the update and reboot
4. You'll see Android is Upgrading...
5. Re-boot back into recover and re-install faux kernel
I have just upgraded my XT1032 on 174.44.9 en GB (rooted + faux008) to 176.44.1 using this... worked like a dream! All I had to do was re-install faux kernel as that was overwritten by the OTA, but Root was in-tact...
i have root, twrp recovery and faux kernel, the problem is only faux kernel? Or I must remove all? (root recovery etc)
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.
I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
I figured it out
planb234 said:
I am having some serious troubles with upgrading my Galaxy Note 4 SM-910P (Sprint). All was well in rooting, un-rooting, etc... I have the original 4.4.4 and the new 5.0 backed up and now I can't use anything other than the firmware the original firmware package through Odin. The problem started when I installed the [ROM]ViSiON-X N4 SPR 5.0.1 [Android L 5.0][N910PVPU1BOB7-R1][03-11-15]. It installed fine but when ever I was not watching it a problem occurred such as getting locked out of ny ext SD, or just plain un-rooting itself. It finally came down to it just kicked my device into download mode and would not reboot. I did used chains Odin root method and installed TWRP, which I can still do but can not flash or restore from TWRP or CWM recovery. It will take the firmware package fine and download the 5.0 update but always gets stopped from any other upgrade at recovery be it stock or custom. I have even used Kies to try and upgrade a few time. It will upgrade from NK1 to NK2 but still will not upgrade anything else past recovery. Every time I reboot I lose my WIFI password. After every boot it takes a minute for any network to be able to reach the device. It is paused until I re enter my WiFi password then it will say that Android is done upgrading and there is a toast message that says "device is set to factory mode some items won't work on this mode set device to user mode". Can someone please tell me how to set my device to user mode or erase what ever is lockled in my device between download and recovery. The issue I described with the device wanting to stay in download mode and how to handle it is described her http://forum.xda-developers.com/showpost.php?p=59372208&postcount=3 but as I mentioned I can't get passed anything that is not firmware through Odin. If I had to be locked in one version forever I would have preferred it be 5.0
Click to expand...
Click to collapse
I fianlly figured out the deal with TWRP not flashing.
The change between file systems is what TWRP won't flash.
To flash into the new, the old, or back up property check the file type.
Ext 2, Ext 4, F2FS, etc ...
To get recovery to load install from odin with auto boot disabled, remove battery, than vol + - menu and power.
the steps below..
1. Power off (complete) boot to download.
2. Load Odin, uncheck auto reboot, PDA TWRP. after it installs pull battery to exit.
3. Boot to recovery - wipe- advanced wipe -Repairor Change File System - Check System (go thruough each)
4. Repair and change each to the file type you want to flash
5. repair and or change the files for the zip you are going to flash
6. you have done all the rest before ....
Issue resolved, thread closed, thanks.
I hope someone reads this as I'm lost for ideas. First time trying to root a device, I'm using an s8+ and somehow managed to mess up installing twrp using Odin.
Now when I try to re flash twrp it comes up with error, 'only official released binaries are allowed to be flashed'. Also I think I managed to erase the recovery program that comes with the phone as when I try to boot in recovery it now comes up with error message 'No command'.
I have reinstalled the stock firmware using Odin but that hasn't fixed anything.
Anyone got any ideas or insite into this problem. Any advice would be very appreciated as I'm so keen to discover rooting!!
Philnicolls89 said:
I hope someone reads this as I'm lost for ideas. First time trying to root a device, I'm using an s8+ and somehow managed to mess up installing twrp using Odin.
Now when I try to re flash twrp it comes up with error, 'only official released binaries are allowed to be flashed'. Also I think I managed to erase the recovery program that comes with the phone as when I try to boot in recovery it now comes up with error message 'No command'.
I have reinstalled the stock firmware using Odin but that hasn't fixed anything.
Anyone got any ideas or insite into this problem. Any advice would be very appreciated as I'm so keen to discover rooting!!
Click to expand...
Click to collapse
Seeing No command is normal, with an icon of a dead android lol, thats stock recovery, blue screen, i got that all time, but after waiting about 30 seconds and pressing the buttons, i got the mnue to pop up to reset cache, reboot phone, wipe data etc.
As for TWRP, are you flashing the correct one, dream2lte??, download the latest one, the dream2lte.img .tar file, from the TWRP official website - - https://dl.twrp.me/dream2lte/twrp-3.3.1-0-dream2lte.img.tar.html.
I had this issue trying to flash TWRP with standard odin, i had to use a modded version of odin to flash it, even prince cosmy version didnt work for me.
I have attatched the ODIN i use, its a 7zip file.
Thank you, after trying a few more things the twrp file you gave me worked. I now have a fully rooted s8!!!! Your a legend.