Welp...I was on the KVT49L CM Edition ROM (http://forum.xda-developers.com/showthread.php?t=2763102) and I was running OUDHS CWM recovery 1.0.3.4. Decided to try to get F2FS running, so I downloaded the custom TWRP that ktoonsez had made to enable F2FS and zip flashed from inside OUDHS 1.0.3.4, and then when I tried to install KVT49L, it gives me status 7. So, I decided to roll back and re-flash the OUDHS 1.0.3.4 .zip, which worked; but it now also now gives me Status 7, even for CM11. The only rom I can successfully install is http://www.slimroms.net/index.php/d.../10761-slim-jflte-4-4-2-build-5-official-4050
Any help would be appreciated as I am in the dark.
Status 7 basically means that cwm thinks you are flashing something not meant for your device. Try flashing after deleting the assert scripts in the Rom zip
Sent from my HTC One using Tapatalk
Related
I recently got a nexus 7 2012. I unlocked it and installed the custom recovery (CWM) according to the guides given in the forum and elsewhere. The problem comes when I install a custom ROM like CM10.2, It installs fine, but the boot does not resume after the CM animation. I tried another rom like AOKP and even TWRP as recovery, still the problem persists. My bootloader is 4.23 and flashing back to stock ROM works as normal. Please help.
What recovery you use. And what tool you use to root. For I use WUG toolkit. And install TWRP. And install CM 10.2 with no problem. Maybe you not really root. Update your superuser before that
Sent from my Nexus 7 using XDA Premium 4 mobile app
Stupid question: are you sure you are flashing grouper ROMs?
Tried a lot of combinations with ROMs and recoveries finally I solved it. CWM wasn't working with its wipe options and tried TWRP and gave the full wipe of all partitions before flashing CM and gapps and it worked!!!!
I'm rooted correctly and have the newest TWRP recovery installed. I've successfully flashed the update for a newer recovery than the stock one when you first put a custom recovery and I flashed an update for the radio on my d800.
I haven't tried flashing any stock roms only new 4.4.1 or.2 Roms. My question is did I miss a step, do i need to flash something else like the latest OTA then wipe again and go for AOSP. I'm by no means new to flashing.
When i try to flash it this is what I get
"error executing updater binary in zip "
Any tips?
Nvm. I switched recovery. Used the unofficial CWR and even though it holds up on clearing the cache it installed beautifully.
Hi my nexus 4 is unlocked and has cm10.2 installed on it. I decided to update to cm11 4.4 and i got the correct gapps and rom and i backed it up in cwm. When i tried to flash cm11, an error came up and it turned out to be my cwm not being updated. So i tried to restore it to and i got a md5 mismatch error. So now im stuck in cwm. HELP
You can always flash back to stock and start over.
http://forum.xda-developers.com/showthread.php?t=2010312
audit13 said:
You can always flash back to stock and start over.
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
is there any other way out?
I find going back to stock and starting over is best because there are excellent instructions for flashing back to stock, rooting, and installing TWRP.
Do you have any ROM installed? You could try installing an updated CWM, install CM10.2 again, and then try to restore your backup.
just download a updated cwm .img and flash using fastboot.
I have tried CM 10.2.0 and Calkulin's Nexus 4 v1.5 on my Nexus 4. I tried with both CWM 6.0.4.6 and TWRP 2.6. CWM wouldn't install the Calkulin ROM at all (Status 7 error), but TWRP would. However, when booting Calkulin's ROM for the first time it would hang at "Starting Apps"
CM 11.2 failed to flash through TWRP. CM 10.2.0 flashed successfully, but then would hang during bootup with the arrow circle loading screen.
I eventually had to go back to CWM and restore a backup (THANK GOODNESS FOR BACK UPS! )
Can anyone offer any clues to what might be going on?
Thanks.
Download GooManager and MAKE SURE you have the LATEST TWRP which supports SELinux
Sent from my Nexus 4 using XDA Premium 4 mobile app
Hey,
I'm new to this device. I use a OPO as my daily driver but I grabbed this phone as a replacement for my dad. I wanted to give him some Cyanogenmod or some other nice AOSP lollipop rom, so I rooted it with towelroot and installed safestrap 3.75. So far, so good. I made a backup of the stock rom. Tried installing Blisspop and GApps, seemed to go okay... at least I thought it did, maybe not. Anyway it didn't work on reboot it took me to the safestrap screen, I pushed continue, it rebooted and took me to the Android System Recovery, rebooted, back to the safestrap screen, pushed recovery to go back into safestrap recovery. I couldn't find my backup to restore. Tried wiping and reinstalling blisspop, tried slim, cm, each time now it gives me "error executing updater binary in zip" and "error flashing zip".
Any ideas?
Also, if more info is needed, let me know. Sorry if I left something out.
Gargoyle nargle said:
Hey,
I'm new to this device. I use a OPO as my daily driver but I grabbed this phone as a replacement for my dad. I wanted to give him some Cyanogenmod or some other nice AOSP lollipop rom, so I rooted it with towelroot and installed safestrap 3.75. So far, so good. I made a backup of the stock rom. Tried installing Blisspop and GApps, seemed to go okay... at least I thought it did, maybe not. Anyway it didn't work on reboot it took me to the safestrap screen, I pushed continue, it rebooted and took me to the Android System Recovery, rebooted, back to the safestrap screen, pushed recovery to go back into safestrap recovery. I couldn't find my backup to restore. Tried wiping and reinstalling blisspop, tried slim, cm, each time now it gives me "error executing updater binary in zip" and "error flashing zip".
Any ideas?
Also, if more info is needed, let me know. Sorry if I left something out.
Click to expand...
Click to collapse
Just did some more reading.... silly me... sorry for the stupid question.
For anyone that find themselves in my shoes, the AT&T variant g900a can use asop roms because the bootloader can't be unlocked.