I'm running OmniRom on my AT&T S3 ... i updated my recovery from standard CWM to Philz Touch to take advantage of the OpenDelta updating. However, after it has gone through two updates using OpenDelta (02-24 and 02-25), i can't boot into recovery without it automatically trying to apply the 02-25 update again. I removed the 02-25 file and now when i boot into recovery it tries to apply the 02-25 update, which is missing, and errors out and reboots back to normal. Is there a script file somewhere i need to delete?
Related
I got my S3 today, and of course set out to root it immediately. Everything went fine until I went to install google apps. I inadvertantly chose the wrong zip and installed the ones for my Skyrocket. Now it boots fine, but is stuck in an error notification loop where it says gapps has closed and setup has failed. If I could get back to the recovery panel, I'd know exactly what to do, but I can't get there with this phone for some reason. When I reboot with down volume, it boots into "safe" mode, but still gets stuck in the loop. If I reboot with down volume and home, I go to the Downloading screen. Could someone please help me get back to the recovery panel???:silly:
workingmomjd said:
I got my S3 today, and of course set out to root it immediately. Everything went fine until I went to install google apps. I inadvertantly chose the wrong zip and installed the ones for my Skyrocket. Now it boots fine, but is stuck in an error notification loop where it says gapps has closed and setup has failed. If I could get back to the recovery panel, I'd know exactly what to do, but I can't get there with this phone for some reason. When I reboot with down volume, it boots into "safe" mode, but still gets stuck in the loop. If I reboot with down volume and home, I go to the Downloading screen. Could someone please help me get back to the recovery panel???:silly:
Click to expand...
Click to collapse
So close, Volume up home and power, and it should get to to recovery.
If you can't boot into recovery, but you can boot into download mode just flash a stock ROM through Odin then flash the correct version of gapps sand you should be good
m0cha5hake said:
If you can't boot into recovery, but you can boot into download mode just flash a stock ROM through Odin then flash the correct version of gapps sand you should be good
Click to expand...
Click to collapse
I can now get into recovery (thank you!) but it's a hobbled recovery, not the touch recovery I installed when I originally rooted. It only gives me four options, including install zip from external sd. When I try to install CM or gapps I get a failed to get permission message and the installation aborts. Unfortunately, fix permissions is not one of the four options I'm presented with
So now I'm trying to flash clockwork mod touch from odin, but it hangs at the Samsung Galaxy boot screen when it goes to reboot. Any ideas out there?
workingmomjd said:
I can now get into recovery (thank you!) but it's a hobbled recovery, not the touch recovery I installed when I originally rooted. It only gives me four options, including install zip from external sd. When I try to install CM or gapps I get a failed to get permission message and the installation aborts. Unfortunately, fix permissions is not one of the four options I'm presented with
So now I'm trying to flash clockwork mod touch from odin, but it hangs at the Samsung Galaxy boot screen when it goes to reboot. Any ideas out there?
Click to expand...
Click to collapse
I managed to flash a new cwm via odin and got into my familiar cwm. From there I was able to reinstall cm10 and gapps (the right one this time!) and it no longer hangs at the samsung galaxy boot screen, and is FIXED. Thank you so much for your help!!
This is my second Samsung. I have put over a dozen different ROMs on my old Exhibit II 4G. Having said that, I realize many of you know more than I could ever hope to know. That is why I'm posting here. I have searched, but most of my searches take me to announcements of new CWM and TWRP recoveries.
I've had a Samsung Galaxy S4 Google Play Edition for over a month and still did not have a nandroid backup, so last night I installed ClockworkMod ROM Manager with the intention of flashing CWM Recovery. The app did not list my phone, so I told it to show all devices, where I found the i9505 (I don't remember if it was the i9505g or not). I told it to flash ClockworkMod Recovery, and selected the option that I had not yet flashed CWMR. I then used QuickBoot to reboot into recovery, where I performed my first nandroid to the microSD card.
When I rebooted after making that nandroid, it went right back to ClockworkMod Recovery. Subsequent reboots did the same thing. I could get into Odin mode with VolumeDown+Home+Power. Using Odin v3.09 I was able to flash the stock recovery. This did not resolve the boot-loop issue. Now it boots into the stock recovery, which is less functional than CWM. To me it is behaving as if the recovery tools were flashed to the /boot/ partition, or something is telling it to always boot from the recovery partition.
-In stock recovery, it will download ADB installations (from "apply update from ADB"), but every attempt fails it's signature verification. I have tried 6+ files, all have failed. I believe that the device has USB debugging enabled, but I cannot check while in this state.
-Stock recovery does not mount the microSD card, so I cannot install from there. CWM would mount the microSD card, but I did not think to try installs from the microSD at that time. Is it possible that I installed the wrong stock recovery?
-I do not know how to perform an ADB "push" with my phone in this state. To be honest, I have never done an ADB push. If I get to that stage, where on my S4 should I send a pushed file? "/system/bin"?
-If I try an adb push in this mode
-How do I get my phone to boot from the proper partition?
-If I have the wrong data in that partition, how do I get the correct information onto that partition?
Here is what it does when I try to sideload from stock recovery:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify while-file signature
E:failed to verify while-file signature
E:signature verification failed
Installation aborted
Thank you in advance for any help!
Solved - i9505g soft-brick/boot-loop
My problem was resolved by flashing a stock recovery and ROM, found here: http://forum.xda-developers.com/showthread.php?t=2569510
The package named "I9505GUEUBML4_FULL_ROOTED.tar.md5.gz" flashed from Odin is what worked.
So my phone downloaded the Lollipop OTA, which I didn't want to install. Thinking I'd gone into the cache partition and deleted it, I went ahead and let the phone reboot -- apparently I hadn't deleted it after all. So now every time I start up my phone, it boots into stock recovery and wants to automatically start updating to Lollipop.
Is there any way to boot to recovery while *skipping* the system upgrade process? I tried the regular VolUp/Home/Power thing, and that doesn't seem to do it.
I was rooted and unlocked, I downloaded the update, flashed stock recovery then selected install local update in the updater app. After installing the phone boots to the Huawei logo, then reboots and gets stuck at the the same logo.
I have a TWRP backup so can get back to B170, does anyone know how I can update without getting stuck at boot?
I have the same problème...
beardedwonder said:
I was rooted and unlocked, I downloaded the update, flashed stock recovery then selected install local update in the updater app. After installing the phone boots to the Huawei logo, then reboots and gets stuck at the the same logo.
I have a TWRP backup so can get back to B170, does anyone know how I can update without getting stuck at boot?
Click to expand...
Click to collapse
Are you sure you installed again a stock recovery?
You need a stock recovery for ota updates.
May try download the full rom and unzip it on your pc. The full rom is almost 2 GB.Copy the update file in
the dload folder on your sdcard. The dload folder should be on top lvl of sdcard.
Switch on the p8 pressing volume+,volume- and power buttom at same time till it vibrates. Now the installation should work.
But after this root is gone
I did revert to stock recovery before updating. I have tried both the incremental update and the full update.
Have managed to update. I downloaded the full update and put it on my external SD card. Backed up with titanium backup, then nandroid backup in TWRP.
Switched to stock recovery, ran local update from the updater app and the new version installed with no data loss.
Then flashed TWRP and rooted.
Yesterday I wanted to update my Nexus 4 to the latest nightly cm-13.0-20160221-NIGHTLY-mako.zip using the built-in update tool. The old build was cm-13.0-20160209-NIGHTLY-mako.zip.
But after hitting reboot, the screen went off and on repeatedly (just plain black). I let it like this for the night. In the morning it was still turning the screen on and off. I was able to reboot to the bootloader. Apparently, the update deleted TWRP and installed Cyanogenmod Recovery. I re-flashed twrp.img, and now I'm stuck there: booting ALWAYS goes to TWRP (or the bootloader), I can't boot the system anymore. I tried re-flashing the old nightly, retried the new one, tried sideloading an even newer one (cm-13.0-20160222-NIGHTLY-mako.zip), wiped cache, wiped data - nothing helped.
What can I do to unbrick my phone?
Do u have a back up to your stock Rom or any other Rom aside from CM?
Flash back to stock and start over with twrp, cm, and gapps.
I just flashed back to stock, the problem persists: bootloop, the lying android with a red warning sign is showing up very briefly, then it reboots.
My first attempt to go go back to stock was manually. Now I tried again using the Nexus Root Toolkit. (Note: both time I flashed build LMY48T
After it finished flashing, the error message (lying android with red warning sign) appeared again, but this time it stayed - no bootloop anymore.
Then I rebooted into revovery mode, and there was some output:
Code:
Finding update package...
Opening update package...
E:unknown volume for path [/storage/emulated/0/cmupdater/cm-13.0-20160221-NIGHTLY-mako.zip]
E:failed to map file
Installation aborted.
OTA failed! Please power off the device to keep it in this state and file a bug report!
So, despite all flashing, apparently it is STILL looking for the - now missing - cm13 update. Where is this coming from? There must be some flag somewhere, some config file or whatever.
So, after the next reboot, the ominous boot parameters seem to be gone - I'm on a fresh 5.1.1, build LMY48T.
I'm still curious what happened here. I guess the whole flashing wasn't necessary, I just needed to get rid of the malicious boot parameter. Maybe a file or a file system was readonly?
Any idea how this happened?