I rooted my ville c2 and installed twrp. And after that i downloaded OTA 4.1.1 and clicked the install button. But it ended up in twrp. And i can't even flash the ota.zip through twrp and fastboot. It always said error. status 7... So somebody show me a way and if you have stock recovery.img, share it please.
Little K said:
I rooted my ville c2 and installed twrp. And after that i downloaded OTA 4.1.1 and clicked the install button. But it ended up in twrp. And i can't even flash the ota.zip through twrp and fastboot. It always said error. status 7... So somebody show me a way and if you have stock recovery.img, share it please.
Click to expand...
Click to collapse
you need the stock recovery for installing OTAs,
flash the stock recovery and install the OTA (you dont need to relock your bootloader)
after installing the OTA you can flash your custom recovery back again.
It could be that you will loose your root after installing the OTA so you have to root your phone again.
I dont have any experience with root-keeper etc. so I cant tell you anything about it.
you will find the stock recovery for the One S C2 here:
http://forum.xda-developers.com/showpost.php?p=28087059&postcount=18
Hello,
I am referencing this a guide on how to root 4.1.2 Samsung Galaxy 3 Verizon from this site. (It won't let me post the link)
I had already installed TWRP from the goomanager app before I went to this guide. I did run the unlock bootloader only from Odin. My samsung logo flashes fast on boot like it should for an unlocked bootloader. I did not flash the VRALEC Bootchain.
I did a backup of my stock rom that was rooted. I did a wipe and factory reset of the device then tried to install CyanogenMod 10.1.3 from the zip. It gave me an error that it couldn't open the zip file. I did a restore from my backup and on boot it said it could not do a normal boot. I had to restore with a stock rom via odin.
Do I have to flash the VRALEC bootchain? Or was that just necessary for the TWRP to be installed? If so I'm thinking when I ran the install recovery script from the goomanager app it did that already. I did not flash any of the listed bootchains after listed in step 6.
Thanks for your help
Jeremiah
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Download latest recovery from http://forum.xda-developers.com/nexus-s/development/crespo-philz-touch-t2284670
Then try to flash the ROM. It seems your recovery is very old.
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
gunlok said:
Hi,
I've been using the same old rom for a year or so (slim rom or sth). Lately i tried updating it to something else, but I get this when I start installing rom in TWRP: Error executing updater binary in zip (...). It works the same way every rom i tried.
UPDATE:
Kinda looks like i can install slim rom 4.3 (so i suppose i could install any 4.3), but none of 4.4 works.
Best regards.
Tried to flash CWM recovery from rommanager app, but it said "Failed to flash recovery...".
please help
Click to expand...
Click to collapse
@smit.sanghavi is right.
You need KitKat compatible Recovery. Update your recovery and then try to flash the ROM.
K guys, wanted to try all you said, but there's another problem.
I discovered my nexus isn't rooted. Bootloader unlocked, but any root checker says its unrooted (of course it was before...). So I'm trying to reroot it but when im connecting my phone via usb in bootloader windows 7 doesn't recognize the device. When the phone is connected in recovery or in normal usb debugging mode it recognizes it as adb android, looks good to me. I go back to booloader and i get "Windows has stopped this device because it has reported problems. (Code 43)" in Devices.
Installed the drivers on few different ways.
So.... what now ?
UPDATE: solved
Hello Guys.
I want to install KitKat 4.4.4 but i need to install custom recovery and now it's problem becouse Odin shows "Success" but my phone shows "Verify signature failed". How i can fix it?
try with fastboot.
Check out this:
Flash-A-Holic said:
I had the same problem. My s6310N had S6310NXXAMK1 and I couldn't install CWM or TWRP. Then I just downloaded S6310NXXAMD1 firmware from Sammobile (LINK) and installed it with ODIN. Then I was able to install CWM.
Click to expand...
Click to collapse
I recently flashed the firmware N915GXXU1DPG2, installed twrp and rooted the device,
now out of the blue, I got a firmware update but I can't install it because of the custom recovery,
Is there a way to install this update with a custom recovery installed? trough an app maybe?
I searched around a bit but the only solution I found is starting from scratch, means flash the stock ROM
to get stock recovery....