I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Sounds like you flashed the wrong recovery, possible that you installed the p3100 recovery.
Try reflashing the recovery.
miksol said:
I recently rooted my galaxy tab 2 P3110 with Odin and CWM recovery 6011 and i seemed to have wiped the stock android os as i cannot boot into it anymote - the Tablet automically boots into CWM all the time
Then when i try to install Slimrom or CM installer to flash and install a new OS but i getting an error 7 - unverified file so i cannot put any Os back on the device
Can anyone help?
Click to expand...
Click to collapse
Flashing KK ROMs on outdated recovery will get you a status 7 error. Grab the latest (I'd go with TWRP as CWM support will be ending soon) version from here...http://forum.xda-developers.com/showthread.php?t=2548257 update to the latest one you like (CWM is 6.0.5.0) Load up a ROM and give it a go. I put all my ROMs on an external card to be safe. Maybe do that and then just install from such.
p,s. CM installer never works, I dont think our tabs are compatible with it. At least I've never got it to work.But, you dont need it anyways.
Related
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
I had the latest version of CM11 on my Opo 64 GB, was also using Multirom and Miui 4.10.24.
Tried to install the 4.10.31 version, but i did it wrong (i did not go into TWRP, then Multirom, add zip and install, but i just selected install rom and flashed the 4.10.31 zip file).
Now, the main CM11 OS is lost, i cannot boot into it, and i cannot also boot into MIUI.
So, how can i get my CM11 back?
I tried flashing the official version but it gives me error while trying to install it through TWRP.
Also if i reboot the phone and try to choose the MIUI it says
"error, kexec-hardboot support is required to boot this rom.
install kernel with kexec-hardboot support to your internal rom.
Any help would be greatly appreciated!
kidstretch said:
I had the latest version of CM11 on my Opo 64 GB, was also using Multirom and Miui 4.10.24.
Tried to install the 4.10.31 version, but i did it wrong (i did not go into TWRP, then Multirom, add zip and install, but i just selected install rom and flashed the 4.10.31 zip file).
Now, the main CM11 OS is lost, i cannot boot into it, and i cannot also boot into MIUI.
So, how can i get my CM11 back?
I tried flashing the official version but it gives me error while trying to install it through TWRP.
Also if i reboot the phone and try to choose the MIUI it says
"error, kexec-hardboot support is required to boot this rom.
install kernel with kexec-hardboot support to your internal rom.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
I'm probably not understanding, but can you boot from off , into recovery then > TWRP?
JeffDC said:
I'm probably not understanding, but can you boot from off , into recovery then > TWRP?
Click to expand...
Click to collapse
Yes I can, managed to install MIUI only, latest version.
I also installed Multirom again (on MIUI) and it downloaded cm11s kernel).
Ok managed to go back to my old miui os, now I have 2 miui os and no cm11, also downloaded the Franco kernel 30. How can i check if the cm11 that i had before is still there, if not how can i install it again without screwing my already working miui?
update:
After some tests, this is what's happening.
I believe I have no CM11S on my phone, that is gone!
I have the MIUI V5 running, but when i flash the franco kernel, the phone is stuck on boot (1+1 logo), i have to flash the kernel_kexec_bacon_cm11s to make it boot in MIUI (working).
So, now i have a working rom that works through Mutlirom and I cannot flash a working CM11S rom on the phone.
Any help would be great guys!
Hi Buddy!
Greetings from a new guy here
Just basic question, few days back I'm trying to Install Slimkat ROM, I've done few steps below :
- Wipe data factory reset
- Wipe chache
- Wipe dalvik
- Format system
- Flash zip from Internal SD Card
But I'm getting status error 7 on installation proccess
I'm trying to Install another ROM (CM 10.3 Official & CM 12 Unofficial) its working just fine
Why I couldn't install Slimkat on my device?
Because you are using an out dated recovery, you need at least cwm 6.0.4.4 because KitKat requires selinux support and older recovery doesn't support it, get it from general section of tab 2 and flash it using existing recovery
Hope it works
shsagnik said:
Because you are using an out dated recovery, you need at least cwm 6.0.4.4 because KitKat requires selinux support and older recovery doesn't support it, get it from general section of tab 2 and flash it using existing recovery
Hope it works
Click to expand...
Click to collapse
Thanks! Its working now
But just wondering, I previously using CWM 6.0.2.8 but I can even install CWM 12 which lolipop based
Why it doesnt work on slimkat which based on kitkat? Kitkat is even lower than lolipop
aliarroughi said:
Thanks! Its working now
But just wondering, I previously using CWM 6.0.2.8 but I can even install CWM 12 which lolipop based
Why it doesnt work on slimkat which based on kitkat? Kitkat is even lower than lolipop
Click to expand...
Click to collapse
If you read what I typed carefully, KitKat uses selinux, lollipop doesn't,
So you can use any recovery made for your device to flash a lollipop based ROM,
But anyways people are getting trim bug that causes infinite Boot loop without any reason, that's why our supper hero Andi protects us with patches that prevent those things.
I've had my Galaxy tab 2 10.1 flashed with CWM recover and CM10RC3 for a while. i finally found the tablet again recently and decided to update. I couldn't flash any experimental CM (nightlies), so updated my recovery to TWRP 2.8.5.0.
I still can't flash any ROMs. OS won't boot, I can only access download mode and my recovery.
When I tried flashing with CWM, i got an error 7 code, and it also said that the ROM was built for X, Y, and Z model, and mine was espresso10rw. I can't find any information on this model anywhere, all i see are the p51xx.
I had some issues with ROMs, so managed to revert back to stock. Now using TWRP, but only after trying with CWM, all ROMS get error 7, "can't install this package on top of incompatible data", and CWM said something about it being the wrong firmware for a "note4" or something.
I don't know what to do, can you flash roms through ODIN? Please note this is an N8010
Thanks for your help
NOTE 4 suggests you are flashing a wrong file for another model .
TWRP CWM and Philz Recovery and High On Android recovery work on N8010 tested all within the last month .
can you flash roms through ODIN? >> Custom roms no only stock tar files .
I've tried the CM 11, the CM 12 and Android revolution ROM, all supposedly work with the N8010. Revolution Rom was the first, installed but made a boot loop after I applied the N8010 compatibility flash. After that the file structure seemed to double - there was a new folder with all the other android directory inside it. I deleted the doubleup, but now I don't know what to do, it's back on stock.
JJEgan said:
NOTE 4 suggests you are flashing a wrong file for another model .
TWRP CWM and Philz Recovery and High On Android recovery work on N8010 tested all within the last month .
can you flash roms through ODIN? >> Custom roms no only stock tar files .
Click to expand...
Click to collapse