Red triangle in recovery GT-N7000 - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

hi,
when i go into recovery I become the dead android with red triangle, and I cant install any custom rom because of : warning No file_contextsset_metadata_recursive: some changes failed (Status 7)
but I can install stock Rom via odin, but also when I go into recovery I had there red triangle, then flashed Fhilz kernel it works, but the error above
Please help me !

No need to worry of the dead bot. And you cannot flash anything using the stock recovery..

and how to install custom rom when I become Status 7?

The first step is make sure you install PhilZ kernel sucessfully. Then bootbinto PhilZ touch recovery. From there you can install a custom rom.
Sent from my GT-N7000 using Tapatalk 2

I had install Philz for XXLT5 via odin, boot into recovery and try to flash 4.4.2 rom and became error to CarbonRom : set_metadata_recursive (Status 7 )
to OmniROM: warning No file_contextsset_metadata_recursive: some changes failed (Status 7)

From Philz you need to install raw kernel, then install 4.4.2.
Sent from my GT-N7000 using Tapatalk 2

P_E_T_O said:
I had install Philz for XXLT5 via odin, boot into recovery and try to flash 4.4.2 rom and became error to CarbonRom : set_metadata_recursive (Status 7 )
to OmniROM: warning No file_contextsset_metadata_recursive: some changes failed (Status 7)
Click to expand...
Click to collapse
Before you flash.. you need to read more the OP of the rom you are flashing.

I have install the F***ing rom from sammobile because i want try some app..
I will try the raw kernel.. thanks

it works with raw thanks!!

P_E_T_O said:
it works with raw thanks!!
Click to expand...
Click to collapse
...

Related

[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!

Unable to install ROM.

Hi,
I have a brig problem. I cannot install custom ROM from recovery mod on my I9305. I tried install CyanFox and PAC-man, but both gave me a error, when i tried to run the zips via recovery.
I have root.
Is there anybody who has same problem like I have.
Any suggestions or advice? Thank you.
Have you followed the instructions faqs and guides posted .
This sound like fail to install cwm recovery from the bare information posted .
That is you have root but no custom recovery .
Stock recovery says 3e
I have CWM based Recovery v5.5.0.4 : : CF-v1.5
And YES I followed all the instructions and faqs.
First install the custom recovery on your device to flash custom ROMs. stock recovery doesn't allow you to flash custom ROMs even though you are rooted
Sent from my GT-P3100 using xda app-developers app
I updated to newer CWM 6.0.3.1.
and again i tried to install the rom.
There's a few words of log.
Installing update...
assert failed: getprop ro.product.device, getprop. ro build.product. getprop ro.product.device == GT-I9305
E: Error in /sdcard/pac-i9305-nightly-20131015.zip
(status 7)
Installation aborted.
It's look like its working! New CWM helped me.
I reply later if everything working.
Possible bad file download again.
Possible not for your phone as its failing on build prop.
Try Philz Recovery .
You can ask in the relevant rom threads as well .
Which is the best recovery for galaxy tab 2 p3100 with plenty of options. and how to find and flash it
Sent from my GT-P3100 using xda app-developers app

[Q] set_metadata_recursive: some changes failed please help !

Hello guys !
I have got set_metadata_recursive: some changes failed error when i started to install a new rom (kitkat aokp lastest)
I have tried :
1- i have the lastest cwm and philz too
2- tried cwm (lastest v6.21)
3- tried philz lastest
4- tried another cwm versions
5- tried to search for this problem and nothing fixed it
hope you guys can help me
thanks ^_^
First, you need to unlock your bootloader in order to flash CM, AOSP or AOKP roms.
The usual procedure is to extract the boot.img from the rom zip, flash it with fastboot, then use the included custom recovery to flash the rom. It should tell you which recovery to use in the installation instructions.
Sent from my C6603 using Tapatalk
thanks
kingvortex said:
First, you need to unlock your bootloader in order to flash CM, AOSP or AOKP roms.
The usual procedure is to extract the boot.img from the rom zip, flash it with fastboot, then use the included custom recovery to flash the rom. It should tell you which recovery to use in the installation instructions.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
thanks man
I will unlock bl
you really helped me thanks
will see if this will work or not

[q] custom rom failure

I Was trying to install a custom rom ''OMNI4.4.2-20140321COPPER nightly'' but after flashing my original rom when i tried to install it from my sd card i got following message
''E:ERROR IN/TMP/SIDELOAD/PACKAGE.ZIP
(STATUS 0)
INSTALLATION ABORTED''
plz guide me what to do.. thanks in advance..:crying:
iamgeek said:
I Was trying to install a custom rom ''OMNI4.4.2-20140321COPPER nightly'' but after flashing my original rom when i tried to install it from my sd card i got following message
''E:ERROR IN/TMP/SIDELOAD/PACKAGE.ZIP
(STATUS 0)
INSTALLATION ABORTED''
plz guide me what to do.. thanks in advance..:crying:
Click to expand...
Click to collapse
The rom file you are using might be corrupted. Can you redownload it again? What recovery mod are you using?
iamgeek said:
I Was trying to install a custom rom ''OMNI4.4.2-20140321COPPER nightly'' but after flashing my original rom when i tried to install it from my sd card i got following message
''E:ERROR IN/TMP/SIDELOAD/PACKAGE.ZIP
(STATUS 0)
INSTALLATION ABORTED''
plz guide me what to do.. thanks in advance..:crying:
Click to expand...
Click to collapse
my friend first you should flash the new recovery CWM 6 and then reboot to recovery then flash the omni rom
sent from my kitkat ACE

Categories

Resources