Set metadata recursive problem - Xperia SP Q&A, Help & Troubleshooting

Hello
I'm trying to flash PacROM 4.4 and I'm encountering a problem with "set_metadata_recursive: some changes failed".
As I searched its because of old recovery tools, but I'm already uusing CWM 4.4.1 and I cannot find out what to do.
The way I tried to flash ROM :
1. Flash stock .254 ROM
2. Install TowelRoot and CWM
3. Flash with CWM 4.4.1 and this is where error come up (kernel 207 works)
Thank you for help
edit: I managed to install VANIR ROM, and later with the same method I managed to install PAC ROM too. I used CWR not Philz.

Your problem was most likely related to your recovery, which was probably outdated.
CM based ROMs sometimes have issues with older versions of CWM.
The reason why it worked after installing Vanir is probably because of Vanir's kernel which includes a more recent version of CWM.
Anyway, glad you got it working.

Related

[Q] Omnirom 4.4 help

On this Omnirom 4.4 for N7000. Am I supposed to have to flash CMW every time I update the nightly. Currently on 1Dec build. Also these night lies unrooted me and I can not figure out how to root again. I am kind of a noob. So that leads to my last question. Since you were working on the CM 11 builds you know what's going on and when I had beta 6 flashed it didn't unrooted me or uninstall CWM. So is there a way to get those codes from CM 11 into the new Omniroms so we don't have to constantly reflash CWM and reroot. Thanks
-Omni rom comes with twrp recovery. You can flash the update using this recovery itself.
-For rooting you will need to flash supersu after you flash the ROM. This zip can be downloaded from the ROM thread.
-CM 11 for n7000 stopped at beta 6 for now till may be if cm team publishes a nightly.
Thanks
nokiamodeln91 said:
-Omni rom comes with twrp recovery. You can flash the update using this recovery itself.
-For rooting you will need to flash supersu after you flash the ROM. This zip can be downloaded from the ROM thread.
-CM 11 for n7000 stopped at beta 6 for now till may be if cm team publishes a nightly.
Click to expand...
Click to collapse
I have flashed CWM but every time I flash a new nightly it overwrites CWM and I have t reflash before I can flash a new nightly. Thanks about supersu. But what I meant about CM features. Herna was working on the beta 6 so why can't those CWM and root features be moved to Omnirom?
I don't think cwm will be used in omni as they have gone with twrp recovery. Most of the features will be integrated slowly
You font need to flash cwm every time. You can flash the zip file using the twrp recovery also.
nokiamodeln91 said:
I don't think cwm will be used in omni as they have gone with twrp recovery. Most of the features will be integrated slowly
You font need to flash cwm every time. You can flash the zip file using the twrp recovery also.
Click to expand...
Click to collapse
Cool thanks I thought the thread said you couldn't flash the Omnirom zip with twrp.
You cannot flash omni rom with a cwm version lower than 6.0.43. I guess. Twrp is fine.

LiquidSmooth to Cynaogen resulted in bootloop

I had installed LiquidSmooth ROM on my Samsung Galaxy Note GTN7000 a while ago. I run Philz Touch recovery version 6.0.0.1 .
When I tried flashing CM11 , I got an error something like set_metadata_recursive .. .
I googled it up, and found that I need to update my recovery. SO, i downloaded the latest version of CWM from their website and tried flashing it through the recovery. And it is resulting in a sudden shut down and then in a bootloop when switching on .
What wrong am I doing? How can I rectify this?
Flash Raw Kernek r5:
http://forum.xda-developers.com/showthread.php?t=2397000
On our device the recovery is incorporated into the kernel, never flash a recovery or kernel that isn't meant for our device.
Once you have flashed that, reboot to recovery and perform a full wipe. Then proceed with the installation of CM.

[Q] KitKat fails to install

Hi. I am supporting my friend. Who has the i9305, via teamviewer so i am using the Universal android toolkit, and it worked ok.
I rooted it, and installed twrp 2.6.3.0 but here i failed. I could not install kitkat or anything else. So i had to revert to cm 10.1.3 and the camera does not work also the android keyboard from gapps 20130812 did fail to work. I had to push him a swiftkey apk, to work.
Now is my question what do i have to do to install cm 11 for i9305 ???
Just a new recovery?
Because every newer file just gets aborted and doesnt install, no liquid smooth or cm11.
Thanks.
My device was on 4.3 and I flashed Philz touch recovery and did a backup and restore. Then it stuck at Samsung logo when booting.
Wiping caches, resettings, fixing permissions, ...... non of them worked.
Finally I could get it booting by flashing 4.4.4 Stock Rom using Odin 3.07
http://forum.xda-developers.com/gal...ck-rom-4-4-4-gt-i9305n-i9305nxxufni4-t2886807
Its working PERFECT now
also rooted using this guide
http://forum.xda-developers.com/gal...covery-i9305-cwm-philz-twrp-versions-t2694249
(In this time I did not used any recovery mentioned in the post. I just rooted it)
:good:

Bootloop for any Custom ROM Except Lollipop Stock ROM

I updated the Moto G 2014 to Lollipop Stock ROM
in order to do so, updating of the bootloader was necessary.
It was told on the Cutsom ROM pages, that in order to install a custom lollipop,
you first have to flash a stock rom, in order to not get into a bootloop.
after installing the stock ROM,
I got the error: -> Cant unmount /data, no such volume
this was done in PhilZ CWM Recovery.
May this is due to an old version of CWM?
some pages recommend the TWRP Recovery, but users reported the same trouble anyway.
Which is the latest version of CWM and are there issues with lollipop custom roms with Philz CWM?
thanks.
I found out that this has to do with
error unmounting /system so such volume.
I am working on this for days now. Just can't find it...

i9305 stuck on boot logo

Hello XDA Developers!
I'm trying to install a custom rom om my i9305 bought in Denmark.
So far I have gotten the TWRP and Cyanogenmod recoveries to work, and through those I have successfully installed the two last versions of CM11 nightlies for the i9305 and the two last versions of AOSB 4.4.4 for the i9305. Yet I can't get any of them to boot past their respective logos (the phone moves nicely past the Samsung Galaxy S3 logo).
I have tried full system++ wipes, multiple Dalvik cache and cache wipes and Factory resets etc, but whatever I do my phone never gets past the CM / AOSB logo. I have waited for 20 minutes once for CM11 and once for AOSB, and 5+ minutes multiple times on both. Nothing changes.
Is there anyone out there with a 9305 that successfully installs custom ROM's that can help? Any help is greatly appreciated as I'm currently without a working phone
PS: Sorry if this is already an answered question. I googled extensively and looked at all the suggested threads before clicking "Submit" and couldn't find an answer.
Technical info:
Heimdall (latest unofficial from developer to get it working with OS X El Capitan)
Android Studio 1.4 with Platform Tools installed today
TWRP 2.8.7.0
Two latest nightlies from the official Cyanogenmod page attempted (I'm not yet allowed to post links), through TWRP as well as the recovery
Two latest versions from the AOSB website (still not allowed to post links, sorry)
MaHo_66 to the rescue
I was able to bring my phone back using the 9305N ROM posted on /galaxy-s3/development-i9305/rom-samsung-stock-4-4-4-rom-collection-t3124027
Still curious why it didn't work with the others, but at least now I have a phone again.
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
maultasche said:
your issue is TWRP 2.8.7.0
several users, including me, had issues with the updated version as it's messes up with partitions etc. You experienced what we were having issues with. After installing the new recovery the installed ROM won't boot up anymore. The only way to fix this was to install stock ROM or a custom ROM based on stock.
I recommend to stay on TWRP 2.8.5.0 till the new version is fixed. Some users are working on a fixed updated TWRP recovery.
Click to expand...
Click to collapse
Thanks for the reply! I also tried with the CyanogenMod Recovery, which ended the same way.
But installing a custom ROM based on stock worked, and is both way faster and pulls way less battery than the original ROM. So it all worked out in the end (until I can't resist the temptation and try to do it all again).
kamikaze702k said:
if you have made a nandroid backup of any previous rom that boots then try that, if that also fails to load then you need to install stock firmware again and start from the beginning again, stock firmwares can be found on samfirmware,
i have been flashing phones for several years, yet the other day i faced the exact same issue, not sure what caused it, it was also for the same device, stock firmware fixed all issues.
good luck
Click to expand...
Click to collapse
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
elysium7 said:
Custom ROM based on stock worked, thanks!
Were you able to install any custom ROMs after fixing your issue, or are you also "stuck" on a stock based ROM?
Click to expand...
Click to collapse
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
kamikaze702k said:
I flashed carbon rom 4.4.4, twrp recovery is user friendly but on this particular device the recovery was cwm, I don't like stock based roms
Click to expand...
Click to collapse
Nice, thanks! I'll try cwm next time then

Categories

Resources