Database Develop

how to go from devil recovery back to cwm

I've recently flashed the devil kernel to mess around with the JB roms. I'm wanting to go back to ICS roms while the JB roms mature. I booted into devil recovery, wipe then installed the CWM zip but says "status 0" aborted.
I've tried doing it through ROM manager but gives me errors that way also.
What am I doing wrong??

blackinches said:
I've recently flashed the devil kernel to mess around with the JB roms. I'm wanting to go back to ICS roms while the JB roms mature. I booted into devil recovery, wipe then installed the CWM zip but says "status 0" aborted.
I've tried doing it through ROM manager but gives me errors that way also.
What am I doing wrong??
Click to expand...
Click to collapse
Your mistake
1) Using Rom manager
2)Devil kernel uses both cwm and twrp recovery no need to "flash recovery" anyways.
If you can still get in to recover just flash what ever ICS rom you want. I'd advice full wipe and formating /system.
Sent from my SGH-I897 using Tapatalk 2

Same Problem, but i tried to flash with devil recovery. First, with cm10 it says installation aborted. Second time with cm9 he rebooted after 5 sec. and now it's in a boot loop.
What can I do to flash cm9 or cm10?

Pad10 said:
Same Problem, but i tried to flash with devil recovery. First, with cm10 it says installation aborted. Second time with cm9 he rebooted after 5 sec. and now it's in a boot loop.
What can I do to flash cm9 or cm10?
Click to expand...
Click to collapse
CM10 and devil kernel don't always get along. Something about the partition layout with devil. Anyway when you tried CM9 and it rebooted it just means it succeeded in flashing the kernel that CM9 comes with. Pull and replace the battery and 3 button combo back into recovery which will probably not be devil anymore. I don't think you have to but I typically go through the wipe procedure again and then you should be able to reflash CM9 without trouble.

m1batt1 said:
CM10 and devil kernel don't always get along. Something about the partition layout with devil. Anyway when you tried CM9 and it rebooted it just means it succeeded in flashing the kernel that CM9 comes with. Pull and replace the battery and 3 button combo back into recovery which will probably not be devil anymore. I don't think you have to but I typically go through the wipe procedure again and then you should be able to reflash CM9 without trouble.
Click to expand...
Click to collapse
I just flashed the cm9 and it didn't work, so I flashed cm10 and it worked apart from the google apps. It says Installation aborted. I tried to install it once again but it didn't help out.
What can I do now?

Pad10 said:
I just flashed the cm9 and it didn't work, so I flashed cm10 and it worked apart from the google apps. It says Installation aborted. I tried to install it once again but it didn't help out.
What can I do now?
Click to expand...
Click to collapse
the google apps package you have... is it the one for JellyBean?

m1batt1 said:
the google apps package you have... is it the one for JellyBean?
Click to expand...
Click to collapse
It's called "gaps-jb-20120726". The link is in the description of the cm10 thread.

Any help?

Help
Those ROMS use a different partition layout. You have to flash an older ROM via ODIN and then you'll be able to go back.

PantherZA said:
Those ROMS use a different partition layout. You have to flash an older ROM via ODIN and then you'll be able to go back.
Click to expand...
Click to collapse
Okay and how can I do that?
:laugh:

Any help?

Pad10 said:
Okay and how can I do that?
:laugh:
Click to expand...
Click to collapse
By utilizing the sticky threads that have all the information you need.
Pad10 said:
Any help?
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=746

Problem flashing paranoid android..

Hello everyone. I used to work out most problems myself but seems like i ran into a problem i dont understand.. so would be nice if someone could help.
I like to try different roms. After staying with paranoid android. I went to a miui rom and then tw based again. Tried most of tw based jb roms am on sva now. Now the problem is:
When i tried to go back to paranoid flash in cwm installation stopps... tried utacka and standard several times even downloafed each again. I get error sth. Like ...emmc.. status 7 install abort. This isnt good hm ?
Can anybody tell what ....?
Also i get booting even before cwm a green message in left upper corner ...jpg. draw image failed. The same message i get when phone is off and i plug it in to load. Well dont know if its related.
as there are lots of clever people out there i hope someone could tell me what to do or if i messed it up. Btw. I can still flash any tw based rom. Thanks

status 7 is usally a bad download / corrupted file, I think you should redownload it and check the md5 before flashing.
Also, flash over a full wipe (safe kernel obviously ) and see how it goes, As for the green jpg message, I believe thats the charging animation, So long as the phone is charging i wouldnt worry too much, Its probably been corrupted inside the ROM, so flashing a new one *could* replace the dodgy jpg image. :good:

what is the name of the file you downloaded for PA? are you getting this error ? assert failed: getprop("ro.product.device")
try a different kernel. The phone might not boot with that but you can install a new rom from recovery

Hello
I had your problem before, I found out it is a bad download (corrupted file)
First, I would like to explain that (EMMC) means the zip files i located on your internal storage
Status 7 can mean either you're using a version not optimized for your phone (so be sure you're downloading from N7000 forums) or it is a corrupted file
To conclude that, do a checksum on the zip file on your phone (There's a free app on play store called Checksum) and compare the checksum that is generated by the app to the checmsum on Utacka thread.. if they differ, then re-download the file from the forum (& repeat the checksum check before you flash it)
Best of luck

irgendeinname said:
Hello everyone. I used to work out most problems myself but seems like i ran into a problem i dont understand.. so would be nice if someone could help.
I like to try different roms. After staying with paranoid android. I went to a miui rom and then tw based again. Tried most of tw based jb roms am on sva now. Now the problem is:
When i tried to go back to paranoid flash in cwm installation stopps... tried utacka and standard several times even downloafed each again. I get error sth. Like ...emmc.. status 7 install abort. This isnt good hm ?
Can anybody tell what ....?
Also i get booting even before cwm a green message in left upper corner ...jpg. draw image failed. The same message i get when phone is off and i plug it in to load. Well dont know if its related.
as there are lots of clever people out there i hope someone could tell me what to do or if i messed it up. Btw. I can still flash any tw based rom. Thanks
Click to expand...
Click to collapse
Try flash Abyss kernel first and from Abyss kernel flash the paranoid android. It happened to me and it turns out not the rom is not corrected but I cannot flash directly from the Phil kernel.

irgendeinname said:
...emmc.. status 7 install abort.
Click to expand...
Click to collapse
That's a known issue of some of the new PhilZ kernels/recoveries, nothing to get worried about.
Flash either a CM10 or HydraCore kernel, reboot recovery, do the wipes and flash away.

Hello,
I've the same problem like u.
Currently I'm still on ultimate 4.1.2 v5 which based on LSA. Everytime I tried to flash another ROM...the emmc status 7 error will appear.
So I guess we have similar problem.
To all expert guys here,
So if I installed the hydracore kernel and reboot to recovery, I can directly flash any new ROM that I want to flash?
Coz, last night my friend said by opening the zip file and edit the updater script on ro.build prop will help me to solved this status 7 error..but after i tried to reedit that script. It won't work. I still got that issue.
Let me try this method by flashing this HC kernel tonight..n i'll update u what I get. Btw I can use any kind of HC kernel right? Or I must use the latest version...which mean the version 7...
Regards
Sent from my GT-N7000 using Tapatalk 2

Any version can be used. Just keep in mind that the phone won't boot after installing hydracore. Only recovery and download mode. So make sure to have all the necessary files preloaded before installing HC

nokiamodeln91 said:
Any version can be used. Just keep in mind that the phone won't boot after installing hydracore. Only recovery and download mode. So make sure to have all the necessary files preloaded before installing HC
Click to expand...
Click to collapse
What do u mean with preload files?
Is it these one?
- zip rom file
- hc kernel
Are there any other files do i need to prepare before flashing that kernel?
Sent from my GT-N7000 using Tapatalk 2

Yes. Rom file and gapps file of cm rom. And hydracore

nokiamodeln91 said:
Yes. Rom file and gapps file of cm rom. And hydracore
Click to expand...
Click to collapse
Ok
Thx for ur help
Sent from my GT-N7000 using Tapatalk 2

Thanks
chasmodo said:
That's a known issue of some of the new PhilZ kernels/recoveries, nothing to get worried about.
Flash either a CM10 or HydraCore kernel, reboot recovery, do the wipes and flash away.
Click to expand...
Click to collapse
Worked for me. Your a reassuring voice in forums. Now off to try CM10.1!
Thanks

please help me, clockworkmod problem ?

I've tried to restock my tab many times with teamovercome guide, and then I got CWM 3 but it can't flash any of my roms. It always say assert failed, get.prob .... (status 7)
I understand that the cause is from the old version of CWM, so I tried to flash AOKB Kanged Gummy kernel which has CWM recovery 6. in it. So the CWM 6 can flash my desired roms easily. But the problem keep happen again, after I flash that kernel and install my rom, the tab keep rebooting to the CWM recovery instead of OS.
So i tri to find other kernel which has CWM > 6 but none of that exist, I I'm really frustrated right now :crying: please someone help me. Thanks a lot

Dnt knw much about Samsung but if u had made a nandroid back up restore it from recovery ... Or try to flash the stock Rom for ur tab with stock kernal n stock firmware..
If I hve helped you press the thanks button ...
sent from HTC sensation

Team ovecome guide give you cwm 5.
If your guide and files are too old, follow my signature to new one.
Sent from my GT-P1000 using xda app-developers app

priyana said:
Team ovecome guide give you cwm 5.
If your guide and files are too old, follow my signature to new one.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
thanks alot. I follow that instruction but still, I can't flash the rom I want. It look like my tab want CWm 6 to flash those (humberos cm 10.1)
The problem is after i use cwm 6 it keep restart to the cwm 6 i don't know how to force it to boot to the OS it just stuck at the CWM recovery each time i reboot

Try CMW 6 while install it? I have same on CM9 I use CM 5 status 7 while try to install CM9
Sent from my GT-P3100 using xda premium

Pengodam said:
Try CMW 6 while install it? I have same on CM9 I use CM 5 status 7 while try to install CM9
Sent from my GT-P3100 using xda premium
Click to expand...
Click to collapse
yup, could you give me the kernel or anything which has CMW 6, thanks a lot. I've been searching for that all day but nothing

Dud just download CWM 6 in install via ODIN again. Just search on this forum.
Sent from my GT-P3100 using XDA Premium

If you follow overcome method to the letter (from page 7 of the guide, skip the rooting and bootloader patach and backup, etc), I guarantee you a CWM that is good to install CM9, CM10, Sapir, AOKP, Paranoid, etc, etc, etc..
Been doing it for over 100 times if you count those done by those who asked and I replied to.
One thing to remember, when you flash CM10, it first upgrades your kernel/CWM to CWM 6.0
so it seems to reboot to CWM but it isn't
It is a normal bootloop.
You need to flash the ROM zip at least 3 times to get the process going progressively.
First round, CWM upgrade, second round, BML to MTD conversion, and 3rd round ROM install.
You just have to read the message on the screen when it scrolls, don't just assume you get a bootloops and meaning it doesn't do a thing.

nhatsky said:
yup, could you give me the kernel or anything which has CMW 6, thanks a lot. I've been searching for that all day but nothing
Click to expand...
Click to collapse
Dude, need to install CWM 6 ( Download )
than copy & paste your custom ROM to SD card.
i'm not doin on same kernel, i just install CWM6 using ODIN

priyana said:
If you follow overcome method to the letter (from page 7 of the guide, skip the rooting and bootloader patach and backup, etc), I guarantee you a CWM that is good to install CM9, CM10, Sapir, AOKP, Paranoid, etc, etc, etc..
Been doing it for over 100 times if you count those done by those who asked and I replied to.
One thing to remember, when you flash CM10, it first upgrades your kernel/CWM to CWM 6.0
so it seems to reboot to CWM but it isn't
It is a normal bootloop.
You need to flash the ROM zip at least 3 times to get the process going progressively.
First round, CWM upgrade, second round, BML to MTD conversion, and 3rd round ROM install.
You just have to read the message on the screen when it scrolls, don't just assume you get a bootloops and meaning it doesn't do a thing.
Click to expand...
Click to collapse
No no, i read but my problem is when i follow your signature's link to the guide until I install the Overcome 7 4.1.0, but the recovery said that "can't open, ... the rom bad" so I try to flash custom rom like CM9, and it say assert failed (status 7) all the time I try to flash. The bootloop is not here
So i flash a kernel called "Kanged Gummy p1" which has CwM 6, this is when the bootloop problem occur. So I think my solution now is the new kernel which has Cwm 6
Pengodam said:
Dude, need to install CWM 6 ( Download )
than copy & paste your custom ROM to SD card.
i'm not doin on same kernel, i just install CWM6 using ODIN
Click to expand...
Click to collapse
So are you sure this is compatible with GT-P1000, it's Galaxy Nexus.

Search : How to flash ClockworkMod Recovery for the Galaxy Tab P1000 via androidauthority
- You need to run on original stock & just flash back to orginal stock rom..
- You need to run Clockworkmod 5
P/S, why you play around custom ROM on unsupported device? daaa

You didn't follow correctly.
After GB stock safe v5, if you flash overcome kernel 4.0 tar via odin, then boot to cwm 5, and flash cm, impossible to get assert failure.
Sent from my GT-P1000 using xda app-developers app

Get some outside air, before proceed.
From GT-P3100 via XDA Premium

Dont flash it..it is for nexus, as you said...our device supports only modded cwms
Sent from my GT-P1000 using xda app-developers app

priyana said:
You didn't follow correctly.
After GB stock safe v5, if you flash overcome kernel 4.0 tar via odin, then boot to cwm 5, and flash cm, impossible to get assert failure.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
I don't know why, my GT-p1 may have been damaged lately or sth, I followed step to step that guide, then i boot to cwm 5 and flash this -> Overcome_7_Series_v4.1.0_NoWipe.zip Mediafire <-- but it say "can't open the .."directory of the file"... the rom is bad ..."
So I didn't follow it, I flash cm9.0.0 stable rls and get "assert failed ... status 7"
My tab may be different somehow cause I have tried many method but it get error unlike the instruction
So I think I just need cwm 6 kernel individually to flash, could you help me
Pengodam said:
P/S, why you play around custom ROM on unsupported device? daaa
Click to expand...
Click to collapse
huh, what do you mean ? I have been used CM10.1 for Galaxy Tab just a couple days ago

probably both your overcome wipe rom and cm9 are bad downloads

priyana said:
probably both your overcome wipe rom and cm9 are bad downloads
Click to expand...
Click to collapse
maybe the overcome rom is bad, but i'm still able to flash cm9 it with cwm 6 via kernel called Kanged Gummy from http://forum.xda-developers.com/showthread.php?t=1747128 . But error and error occur again. U see, though I flash it successfully with Cwm 6. but i got cwm recovery bootloop too bad.

any update on this.
Using GT-P3100 via XDA Premium

CWM3 = chainfire kernel
CWM5 = voodoo kernel
CWM6 = AOSP and AOKP kernel thats mean CM9/10 and parandroid
Until now theres "no release" kernel with CWM6 for stock/custom rom but its easy for kernel dev like humberos to add that on stock kernel..

Pengodam said:
any update on this.
Using GT-P3100 via XDA Premium
Click to expand...
Click to collapse
hmmm no, I'm still stuck with Overcome 4.1.0 rom which I really don't like, but I can't do anything :
savie said:
CWM3 = chainfire kernel
CWM5 = voodoo kernel
CWM6 = AOSP and AOKP kernel thats mean CM9/10 and parandroid
Until now theres "no release" kernel with CWM6 for stock/custom rom but its easy for kernel dev like humberos to add that on stock kernel..
Click to expand...
Click to collapse
Wow, I hope that would release soon, do u know that guy, can u help me to make one for all of us
i don't know why I can't install AOKP, CM10.1 custom rom with CWM 5. It always said assert error, stt 7 can't open emc/..../... even after I restock

[Q] how to identify my problem with flashing roms?

i have been flashing roms now since january this year. I've already flashed a lot for both the Gio and the Ace.
Now I'm running into this same problem again with several roms:
when I want to flash the rom, it returns me a status 7 error. Why? I don't know. I've tried already so much: md5 checksum, downloading again, formatting my sdcard partition
I have it with many roms (cm 7 blackhawk / firekernel, cm 10.1.1 mardon, cm10 maclaw etc etc).
I would like to find out what the problem is and possibly how I can solve it.

Maybe there is a problem with your recovery install. You could try to install that again.

Try to toggle signature verification in cwm. Or just reflash the recovery.
Sent from my Galaxy Ace GT-S5830 using xda premium

Venomous Viper 119 said:
Try to toggle signature verification in cwm. Or just reflash the recovery.
Sent from my Galaxy Ace GT-S5830 using xda premium
Click to expand...
Click to collapse
should i download a new recovery or the same i already had? (file name: recovery-clockwork-5.0.2.6-galaxyace-fix.zip)

DutchArjo said:
should i download a new recovery or the same i already had? (file name: recovery-clockwork-5.0.2.6-galaxyace-fix.zip)
Click to expand...
Click to collapse
Just download the same file again. I use the same one.

nikwen said:
Just download the same file again. I use the same one.
Click to expand...
Click to collapse
thanks. I've tried this but even reflashing my cwm file returns a status 7 error
but flashing my px-cwm v2.zip recovery completed.
I managed to install cwm 6.0.3.2 (although it still says 5.0.2.6) and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?

DutchArjo said:
thanks. I've tried this but even reflashing my cwm file returns a status 7 error
Click to expand...
Click to collapse
Ok. In that case there is an error with your recovery.
@The Others: Would it help to flash a Samsung Firmware via Odin? Would that replace the recovery?

I managed to install cwm 6.0.3.2 and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?

DutchArjo said:
I managed to install cwm 6.0.3.2 and still i'm getting all these status 7 errors.
the error is " assert failed". Is it possible that cwm isn't able to "read" the several getprop requests from my phone?
Or should the line in script update be changed with removing the spaces between the getprop for cooper and the getprop for gt-s5830?
Click to expand...
Click to collapse
Try it if you know what you are doing.

nikwen said:
Ok. In that case there is an error with your recovery.
@The Others: Would it help to flash a Samsung Firmware via Odin? Would that replace the recovery?
Click to expand...
Click to collapse
Hi nikwen, yes, to flash via Odin will replace the recovery with the stock recovery. Cheers.
Sent from my GT-S5830 with TouchWiz UX 5.0 by NaTHaN

BajoPrimate said:
Hi nikwen, yes, to flash via Odin will replace the recovery with the stock recovery. Cheers.
Sent from my GT-S5830 with TouchWiz UX 5.0 by NaTHaN
Click to expand...
Click to collapse
i've flashed a stock rom with mobile odin.
After that: i've tried to flash the cm10.1.3 rom from mardon. It returned a status 0 error. After that, I've flashed cwm 6.0.3.2 and tried to flash the rom again. Still a status 7 error.
Is it possible that maclaw's cm9 or cm10 have changed something in my Phone which causes that i'm unable to flash anything anymore? I only get status 7 errors. When i follow the suggested steps at XDA to get rid of these errors (read: delete the assert lines in updater script) the status 7 errors are replaced by status 6 errors.
when i'm in cm9 and execute getprop in terminal, the ro.product.build / devide / model = cooper (no gt-s5830).
the label on my Phone (which is located underneath the battery) says gt-s5830.
How do I get rid of the maclaw history and return to the completely Original rom to see if I can flash from there?

DutchArjo said:
i've flashed a stock rom with mobile odin.
After that: i've tried to flash the cm10.1.3 rom from mardon. It returned a status 0 error. After that, I've flashed cwm 6.0.3.2 and tried to flash the rom again. Still a status 7 error.
Is it possible that maclaw's cm9 or cm10 have changed something in my Phone which causes that i'm unable to flash anything anymore? I only get status 7 errors. When i follow the suggested steps at XDA to get rid of these errors (read: delete the assert lines in updater script) the status 7 errors are replaced by status 6 errors.
when i'm in cm9 and execute getprop in terminal, the ro.product.build / devide / model = cooper (no gt-s5830).
the label on my Phone (which is located underneath the battery) says gt-s5830.
How do I get rid of the maclaw history and return to the completely Original rom to see if I can flash from there?
Click to expand...
Click to collapse
Are there differences between Odin and Mobile Odin? If there are some, flashing using the desktop one might help.
Cooper is the codename for our Ace. So that is ok.

I've tried 2 stock roms now. Neither can boot. I've reflashed the 5.0.2.6 cwm recovery because that one is the only one that can restore my cm9 backup. I'm lost... I don't know what to do now because there is simply no way of getting a different rom on this Phone and i would really like to know why.
What did maclaws rom do that f*ck*d up my Phone?

DutchArjo said:
I've tried 2 stock roms now. Neither can boot. I've reflashed the 5.0.2.6 cwm recovery because that one is the only one that can restore my cm9 backup. I'm lost... I don't know what to do now because there is simply no way of getting a different rom on this Phone and i would really like to know why.
What did maclaws rom do that f*ck*d up my Phone?
Click to expand...
Click to collapse
You could send them an email.

Flash stock via PC using odin. You will be stuck in a bootloop. Reboot into recovery & factory reset. Reboot & phone boots. Now, important , you cannot flash custom Roms via stock recovery. Place the cwm 5.0.2.6 zip on sd card. Reboot into recovery , select " install update from sd card ", select the zip file, select yes & reboot. Again reboot into recovery, do full wipes & select " install zip from sd card " & NOT " install update from sd card " & flash any stock based Rom like Touchwiz 5 by Nathan. If you follow this, everything must be fine.
Sent from my Galaxy Ace GT-S5830 using xda premium

nikwen said:
You could send them an email.
Click to expand...
Click to collapse
YEs... I managed to flash px recovery 0.4 (again: I still had to delete the assert lines from updater script). Now I was able to flash the cm 10.1.3 rom from Mardon. Just booted for the first time. Hopefully my status 7 errors are now history... (i don't know if I can restore my cm9 backup from maclaw but we will see).

DutchArjo said:
YEs... I managed to flash px recovery 0.4 (again: I still had to delete the assert lines from updater script). Now I was able to flash the cm 10.1.3 rom from Mardon. Just booted for the first time. Hopefully my status 7 errors are now history... (i don't know if I can restore my cm9 backup from maclaw but we will see).
Click to expand...
Click to collapse
Great.
Do you want to restore it? I prefer 4.2.2.

i prefer not. But it depends on how satisfied I am on this cm 10.1.3 rom. And how many bugs / errors I experience, How smooth/fast it is etc.
When I'm not satisfied, I can Always return to this rom I was most satistied off so far. But I wanted another rom because I have a lot spontaneous reboots when turning on Wifi again....

DutchArjo said:
i prefer not. But it depends on how satisfied I am on this cm 10.1.3 rom. And how many bugs / errors I experience, How smooth/fast it is etc.
When I'm not satisfied, I can Always return to this rom I was most satistied off so far. But I wanted another rom because I have a lot spontaneous reboots when turning on Wifi again....
Click to expand...
Click to collapse
In case like yours a fresh often install helps, too.

nikwen said:
In case like yours a fresh often install helps, too.
Click to expand...
Click to collapse
it might, but it also means reinstalling all my apps again. And I do not want to do that
hopefully, this cm10 rom is satisfying enough. I will then stick to it...

[Q] N7000 CWM Recovery Upgrade to Latest Version

Hi, i have installed SlimBean ROM on my Note and CWM Recovery 6.0.3.2.
I read on forums that for latest CyanogenMod 10.2 i need newer CWM Recovery(ccurrent version 6.0.3.8).
I search how to upgrade to latest CWM Recovery and i found this:
http://forum.xda-developers.com/showthread.php?t=2201860
And here is link for download latest version for N7000:
http://d-h.st/users/philz_touch/?fld_id=25295#files
But i'm confused now, is on that link only CWM Recovery or is that Kernel with CWM?
Can i flash that file through current CWM Recovery (zip file) and get latest CWM Recovery Version?
Or can you tell me how to get latest CWMR Version.
I don't want use Custom ROM's based on Samsung firmware, i prefer CM based Custom ROM's (SlimBean and Bam Andorid),
so that's reason why i'm confused most about upgrading CWMR.
Thanks

You will have to use a kernel which has updated recovery.

please send me xda clockworkmod recovery for galaxy gt-n7000 for omni and tell me how to install

fantasy24 said:
please send me xda clockworkmod recovery for galaxy gt-n7000 for omni and tell me how to install
Click to expand...
Click to collapse
This has been told to you in a lot of threads.

Not able to install 4.4.2 it says error 7 n7000
Hi,
I installed cwm PhilZ-cwm6-XXLTA-ATL-5.15.0-signed recovery from your post which works fine the touch etc. but after when in try to install 4.4.2 in recovery mode, it says (SET_METADATA_RECURSIVE: SOME CHANGES FAILED E: ERROR IN /EMMC/N7000-STABLEv1.zip (STSTUS 7)) and cannot install. the same message for Google app too. is there any thing else i have to do. I have n7000 and i am not very good in gadgets but you know i want to try kitkat.
My phone is not rooted. so in just installed PhilZ-cwm6-XXLTA-ATL-5.15.0-signed. and I have downloaded N7000-STABLEv1 but always get the same message above. I thought just by installing PhilZ-cwm6-XXLTA-ATL-5.15.0-signed i can install any custom rom.
I need help. thanks

rajdeep.sandhu said:
Hi,
I installed cwm PhilZ-cwm6-XXLTA-ATL-5.15.0-signed recovery from your post which works fine the touch etc. but after when in try to install 4.4.2 in recovery mode, it says (SET_METADATA_RECURSIVE: SOME CHANGES FAILED E: ERROR IN /EMMC/N7000-STABLEv1.zip (STSTUS 7)) and cannot install. the same message for Google app too. is there any thing else i have to do. I have n7000 and i am not very good in gadgets but you know i want to try kitkat.
My phone is not rooted. so in just installed PhilZ-cwm6-XXLTA-ATL-5.15.0-signed. and I have downloaded N7000-STABLEv1 but always get the same message above. I thought just by installing PhilZ-cwm6-XXLTA-ATL-5.15.0-signed i can install any custom rom.
I need help. thanks
Click to expand...
Click to collapse
Read how to on flashing kitkat roms... hint: raw kernel

Raw Kernel
nokiamodeln91 said:
Read how to on flashing kitkat roms... hint: raw kernel
Click to expand...
Click to collapse
Hi,
Did installed raw kernel but still getting same error status 7. even enabled toggle signature verification but still.
thanks

rajdeep.sandhu said:
Hi,
Did installed raw kernel but still getting same error status 7. even enabled toggle signature verification but still.
thanks
Click to expand...
Click to collapse
after installing raw kernel , did you reboot recovery or still doing it on touch one?

nokiamodeln91 said:
after installing raw kernel , did you reboot recovery or still doing it on touch one?
Click to expand...
Click to collapse
LOL

Done flashing "PhilZ-cwm6-XXLTA-ATL-5.15.0.tar.md5" and after reboot to recovery, its only black screen, but I can feel the vibrate when touch the screen. What to do now?

CWM dowload link for Note 1 is not work !!
Hi,
the download link for the CWM Note N7000 is nor working!!
Any help please !!!

links are full of virus and ads but no files ...

Please update the links!
Please update the links when I click on them it gets me to a page but the file is not available! Please update the links!