Jump to content


Photo

Do we need newly recompiled recovery?

recovery xt926 status7 set_metadata_recursive some changes failed

  • Please log in to reply
14 replies to this topic

#1 NAKAMONIEL

NAKAMONIEL

    Member

  • Members
  • PipPip
  • 59 posts

Posted 25 January 2014 - 09:02 AM

OK, on my 2 favorite ROMs slim and Validus, I get status 7 error if I don't mount system. If i do I get  set_metadata_recursive: some changes failed error. I was reading up on both of the errors, and I found other people on other phones/roms had solved this errors, What I am trying to figure out is that whether there is some sort of update required for Recovery like mentioned in here,"

Please Login or Register to see this Hidden Content

" or is it the ROM makers need to implement the changes to the ROM like mentioned in here,"

Please Login or Register to see this Hidden Content

" Please someone more experienced elaborate. 

 

2nd xt926 issue I am facing with all kit kat roms is bluetooth. While bluetooth works, but with my (nissan) car pairing, when it tries to read phonebook and call history, it keeps crashing on all roms. Bluetooth would work just fine if I ignore request for phonebook/call history read from phone but if I accept the request it would crash right away. Can anyone fix it?

 

Thanks, With limited knowledge of technicality and huge itch of crackflashing,

 

-Nakamo

 

 



#2 cmh714

cmh714

    Tech Service & Beyond

  • Smod
  • 3,272 posts
  • LocationSoCal
  • Current Device(s):Nexus 6

Posted 25 January 2014 - 03:56 PM

I was using Validus for a while and didnt have to do any mounting, everything worked fine. I have an unlocked 926 and using TWRP 2.6.1.0.



#3 RikRong

RikRong

    Cap'n Slow

  • Superuser
  • 2,117 posts
  • LocationNoDak
  • Current Device(s):Pixel 7

Posted 25 January 2014 - 07:14 PM

You do need the latest TWRP to flash some of the newest ROMs.  I just flashed Slim 2 days ago with the latest TWRP that was posted by Avi in the HD forum on XDA.  I had no issues and didn't need to mount anything. 


R. Long: Pixel 5

 


#4 NAKAMONIEL

NAKAMONIEL

    Member

  • Members
  • PipPip
  • 59 posts

Posted 25 January 2014 - 07:56 PM

But I have most recent 2.6.3.0 twrp installed and yet it wouldnt install either of 2 roms, I will try going back to 2.6.1.0 and see if it helps



#5 RikRong

RikRong

    Cap'n Slow

  • Superuser
  • 2,117 posts
  • LocationNoDak
  • Current Device(s):Pixel 7

Posted 26 January 2014 - 07:36 AM

But I have most recent 2.6.3.0 twrp installed and yet it wouldnt install either of 2 roms, I will try going back to 2.6.1.0 and see if it helps

No offense, but it's either user error or a bad download.  I've had zero issues installing any of the 4.4 ROMs.  

 

Here's the link for the recovery I'm talking about:

Please Login or Register to see this Hidden Content


R. Long: Pixel 5

 


#6 cmh714

cmh714

    Tech Service & Beyond

  • Smod
  • 3,272 posts
  • LocationSoCal
  • Current Device(s):Nexus 6

Posted 26 January 2014 - 04:37 PM

did you do a nice cleanup when updating to the latest TWRP? go find all the TWRP folders and delete them, let TWRP recreate them.


  • pistacio and RikRong like this

#7 NAKAMONIEL

NAKAMONIEL

    Member

  • Members
  • PipPip
  • 59 posts

Posted 30 January 2014 - 01:22 PM

Let me try that and I will report it, seems like that might be cause



#8 Robdog

Robdog

    n00b

  • Members
  • Pip
  • 6 posts

Posted 30 January 2014 - 04:42 PM

I seem to be having this same issue. Cannot install Validus with either CWM or TWRP.

 

I have tried all versions of both recoveries, old and latest I can find. I can flash CM11 roms no problem but cant flash AOSP roms

 

The only thing I've come up with is something about a certain emmc chip in 16GB versions. Hascode and Pcarenza both had these issues as well

 

see here

Please Login or Register to see this Hidden Content

 

Im on an XT925 16GB


  • neckchop likes this

#9 cmh714

cmh714

    Tech Service & Beyond

  • Smod
  • 3,272 posts
  • LocationSoCal
  • Current Device(s):Nexus 6

Posted 30 January 2014 - 05:32 PM

Interesting.....I believe I did see a 16GB version of Twrp somewhere....maybe in Hashcodes goo folder



#10 Robdog

Robdog

    n00b

  • Members
  • Pip
  • 6 posts

Posted 30 January 2014 - 05:48 PM

Interesting.....I believe I did see a 16GB version of Twrp somewhere....maybe in Hashcodes goo folder

 

I have tried Dhackers 16gb noemmccheck version and that still does not work for me.

 

I haven't seen Hashcodes version



#11 Robdog

Robdog

    n00b

  • Members
  • Pip
  • 6 posts

Posted 30 January 2014 - 05:54 PM

In the link is posted earlier, if you read through the thread, Pcarenza was able to find what was causing the error and built a version of the specific rom that worked for him.

 

This leads me to believe that the rom makers need to change something that's affecting the install

 

But then again I could be completely wrong.



#12 cmh714

cmh714

    Tech Service & Beyond

  • Smod
  • 3,272 posts
  • LocationSoCal
  • Current Device(s):Nexus 6

Posted 30 January 2014 - 06:17 PM

I have tried Dhackers 16gb noemmccheck version and that still does not work for me.

 

I haven't seen Hashcodes version

It may have been dhackers that I was thinking of...



#13 icctech

icctech

    n00b

  • Members
  • Pip
  • 7 posts

Posted 01 February 2014 - 08:48 AM

I've been having the same issues the only rom i've been able to install is Nexesque . And the weird thing is before this i had been installing 4.3 and 4.4 roms without a problem. then i used the droid utility to reinstall 4.1 ( cant remember the reason its been a while now) and i've done the same with using different recovery's TWRP, CWM.



#14 Robdog

Robdog

    n00b

  • Members
  • Pip
  • 6 posts

Posted 04 February 2014 - 01:18 PM

I think I found a fix for this. Anyone having issues installing some 4.4 roms try this

 

Please Login or Register to see this Hidden Content

 

This has worked for me. Validus, here I come...


  • NAKAMONIEL likes this

#15 NAKAMONIEL

NAKAMONIEL

    Member

  • Members
  • PipPip
  • 59 posts

Posted 06 February 2014 - 12:14 PM

Thanks Robdog, that fix worked for me too, Was able to install both Slim and Validus just fine. However both of them have bluetooth bug like I have had on all other kitkat roms, it crashes upon calls/phonebook request by my car. Does anyone know if there has been fix for this?





Also tagged with one or more of these keywords: recovery, xt926, status7, set_metadata_recursive, some changes failed

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users