I'm updated to DI09 and rooted.
I installed Ti Backup and Rom manager
and also did odin flashing CWM recovery.
I got aborted msg few times, and tried again while installing CWM.
When it went thru alright, CWM installed, then bluetooth not working.
it keeps saying turning on then goes back to off mode.
before CWM installed, (after rooted) bluetooth working fine but if I install CWM then bluetooth not working.
I had to flash original stock back then did all the steps again to go that point.
I'm now stuck here "currently not trying to install CWM because I need bluetooth working!"
Anyone has an idea?
PLEASE HELP!!
Not sure which CWM .tar file you flashed, but I would suggest you flash this one. It has been modified for DL09. Once in recovery, I would recommend that you wipe data and cache. Reboot and BT should work fine
wow i just tried it and BT and CWM both working fine!! THANK YOU!!! =]
OMG, another prob is coming up!
after I successfully installed CWM, I launched Rom manager and clicked "flash CWM recovery(?)" and then selected Samsung Fascinate.
then I clicked backup current rom, the screen went to recovery screen says
"Installation aborted" so I chose "apply sdcard:update.zip" then this coming up
"Istall from sdcard...
Finding update package...
Opening update package...
Verifying update pakage...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
What did I do wrong?
maybe I shouldn't have clicked flash CWM recovery from rom manager?
Can't backup current rom!!! =[
Nevermind! Find the solution from another thread!
Related
Hi,
I'm at my wits end. I had SlimRom installed for a week and all was fine, but I was curious about what new ROMs were out there so I backed up my phone using ROM Manager and did all the usual stuff to get a new ROM. I installed Gummy, but didn't like it; I installed one other ROM that I can't remember its name, but also didn't like that. I realized my comfy home of SlimRom was where I wanted to be, so I tried to flash the backup.zip that I had created but it kept saying installation aborted (Status 0).
After hours of countless attempts and just weird behaviour (sometimes boot loops, sometimes not booting into recovery, etc.) I finally got my phone back to stock.
I downloaded the latest SlimRom file 3 times to make sure it wasn't a corrupt zip (twice from my PC and once from my phone directly). Both the zip directly from Slim as well as the backup.zip that I made with ROM Manager give me the same installation aborted. The other error it gives is "E: Error in /data/media/0/slim....zip". I'm wondering if somehow my partition is screwed up. I tried using Odin's repartition, which just erased my recovery partition, but I got that back thankfully! When I wipe data/factory reset it says wipe complete (and the ROM does reset to factory) but it also says "E:unknown volume '/sdcard/.android_secure' "...I'm wondering if that relates to why the backup.zip file won't read properly. Maybe the partition got screwed up somehow?
I can flash a SU zip so it's not a flashing problem, per se. And thankfully Odin always works!
I think I may need the stock PIT file for the Telus S4 l337m
UPDATE:
I think I found the proper pit (SGS-I337_16GB) but my phone says "secure check fail: pit".
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.
hi,
i've just made a rooted, debloated stock rom with android kitchen.
when i try to flash it i get this error "E: error executing updater binary in zip"
ive tried TWRP recovery, versions 2.8.5.0 and 2.8.1 & Philz recovery.
any idea??
i can flash any other rom fine
Take the entire meta-inf folder from the original rom you started with, if you have it. I ran into the same problem the other day. It worked for me.
hi have a s4 i9505 had cm11 installed tried to install cm12 now got a screen that says cyanogen simply recovery . when tried to install getting install/storage/sdcard1
finding update package
opening update package
verifiying update package
e failed to verify whole file signature
e signature verification failed
installation aborted
any help greatly appreciated
thanks tony
Upgrading from CM11 to CM12 requires a full wipe. Before installing your Rom, try to wipe: -dalvik cache, -cache, -system. In most recoverys there is an option sounding something like "full wipe for rom flash", do this as well (though you have to install a rom after doing this).
Now you're ready to flash the Rom, however if your Recovery still says "installation aborted", something is wrong with your Zip file. Try redownloading it
thanks tried wiping but still coming up with same message
Download the zip file again because your zip file is corrupt. The recovery is trying to tell you this by saying that signature verification failed. Do NOT use your S4 to do the download. Download it using a PC.
Or you can disable the zip verification. But this may be dangerous as you can install incomplete software and brick your device.
thanks
now solved thanks for help
Hi guys. I'm having some weird problems with my Galaxy Note3. I tried installing custom rom, but i did something wrong, so now when i try to install a rom i get this "E: failed to mount /data (Invalid argument)".... What should i do? I got CWM Recovery V6.0.4.6, and i just tried to update it (unzip through CWM), but for some reason it won't let me open my sd card... What should i do? My phone has no rom right now.
Thanks.
EDIT:
I installed cwm 6.0.4.7, but i still have 6.0.4.6.... Weird?