Develop Bugs

[Q] Error installing new rom: set_metadata_recursive

Hello,
from here: http://forum.xda-developers.com/showthread.php?t=2642605
Exciting new ROM I wanted to try but when I try to install it through CWM it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/aosb_kk_1.2.8_vision.zip
(status 7)
Installation aborted
The install instructions, step 2, specifically mentions update recovery, and googling for this error suggests that that solved it for others, but I have the latest CWM for the G2/Desire Z: I've tried both 5.0.2.7 and 5.8.1.0, non-touch and touch. There's no where else to upgrade to, unless I'm being completely obtuse. I've tried redownloading the zip to make sure it wasn't corrupted or anything, I've formatted my system and data partitions, all the usual stuff I could think of.
Can anyone provide a little bit of assistance? I've specifically got the G2, not Desire Z, but I don't think that's made a difference in the past but it's been a while since there was a new ROM I wanted to try so I'm probably forgetting something. What about this TWRP I've read about? First try couldn't get it to work but if I did get it to work think that might let me finish the install?
Thanks!

Yes, we'll go with "obtuse". I found the developer thread with a much more up to date CWM. Pity that only such an old version is available through official channels.
Thanks.

[Q] "Decryption Unsuccessful" when installing custom ROM to HTC One X

Hi there, I'm desperately hoping someone can help me with this issue as I have trawled through Google for solutions to no avail
I've followed the tutorials from all the lovely people on these forums to get quite far into installing a custom rom for my HTC One X (XenonHD). Unfortunately I've been greeted with the "Decryption unsuccessful" error which I have discovered to be a very persistent error - where many people have many different solutions for it (none have worked for me ) I'm greeted with a password box, and no matter what I type into the box over 4 characters long it says:
Code:
Decryption unsuccessful.
The password you entered is correct**, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
<Reset Phone>
** - It says this regardless of what I type into the password box.
There was no important data on the phone (it's an old phone) so I'm more interested in just getting this custom rom up and running, it doesn't matter to me if I have to wipe data.
Here are the approximate steps I took to reach this position:
Set up bootloader/fastboot
Installed twrp
Wiped the device (cleared every cache etc.)
Copied XenonHD zip and gapps zip on to sd card
Flashed boot.img to the device
Rebooted - XenonHD spinning logo appears, then after about 30 seconds it asks me to enter the password, and I get the Decryption Unsuccessful error.
If you need any more information from me please just ask!
I am so appreciative of how helpful this forum has been to me so far, so I have really high hopes you guys can help me

Just a quick update: I actually managed to install a different rom using the exact same method that I did for Xenon - no signs of the decryption error whatsoever. I'm a noob at this stuff so I'm not really sure of the relevance of this but it sounds like it could be helpful in pointing towards a solution?

Ollie1700 said:
Just a quick update: I actually managed to install a different rom using the exact same method that I did for Xenon - no signs of the decryption error whatsoever. I'm a noob at this stuff so I'm not really sure of the relevance of this but it sounds like it could be helpful in pointing towards a solution?
Click to expand...
Click to collapse
Wich rom you install? The answare will help

I said in my original post which rom I was installing (XenonHD) - but I've actually managed to fix it!
To anyone else who stumbles upon this thread, if you are getting the decryption unsuccessful error you have to format your phone. In my case, it was a case of updating to the latest TWRP which includes a Format option on the wipe screen. This got rid of the encryption on my phone and I was able to use the rom!

Ollie1700 said:
I said in my original post which rom I was installing (XenonHD) - but I've actually managed to fix it!
To anyone else who stumbles upon this thread, if you are getting the decryption unsuccessful error you have to format your phone. In my case, it was a case of updating to the latest TWRP which includes a Format option on the wipe screen. This got rid of the encryption on my phone and I was able to use the rom!
Click to expand...
Click to collapse
Yes offcorce you migrate from old layout to the new leyout the roms for this two layouts are different

dm-verity problems

Hello, this is my first post. First off thanks to the entire community for this wonderful forum and the ability to ask questions like the following here .
Phones background information: In my spare time I attempt to fix phones for family and friends. I recently received a sm-n910a (att note 4) that was on stock 4.4 kitkat and did (does) not have an active at&t mobile plan. Its function is to be used as a wifi phablet for web surfing/games and the user was interested in upgrading the Android system to 6.0MM if possible as well as SIM unlocking the phone for a future Straight talk prepaid plan.
1. Without full-root I was unable to make a complete backup initially but owner wasnt worried about a complete data wipe so I didn't think it would be a problem. (Dumb mistake I know now )
2. Used Odin to flash stock Android 5.1.1
3. Used Kingroot and/or Kingoroot to temp root. Pretty sure it was Kingroot, but not positive.
4. Used Z3x box program to simunlock (was successful)
5. Made complete backup using ADB
6. Downloaded stock 6.0 updates from xda forum post and loaded on sd-card.
7. Entered recovery to update to 6.0 but found errors:
E: failed to mount /efs (invalid aurgument)
DM verity verification failed // Did not display anything about the drk like other people mentioned online.
8. Used Z3x box program to wipe efs (was successful)
9. Entered recovery to check errors and the E: failed to mount /efs was gone
10. Researched online about Dm verity verification failed as much as possible and used the solution to wipe cache, wipe user data, flash stock 5.1.1 rom again, wiped cache agian.
11. At first startup the recovery system lets me access sd-card content and I can select the update file but as soon as it is done and attempts to update, fails with dm-verity problem immediately, and dm-verity verification failed persist after any reboot or wipe until I reflash.
12. After multiple attempts to reflash kitkat problem still persist and with the locked bootloader I am at a loss as to what to do next to rectify the problem.
Any help or suggestions would be greatly appreciated. I hope I posted in the correct forum thread. Thanks agian in advance. -CM

Nobody has any advice for me
Lol, just checking back in agian. Nobody has any suggestions or similar experiences with a situation like this. Any feedback is appreciated. Thanks agian in advance. -CM

perplexive said:
Lol, just checking back in agian. Nobody has any suggestions or similar experiences with a situation like this. Any feedback is appreciated. Thanks agian in advance. -CM
Click to expand...
Click to collapse
I have thé same problèm . But i have thé bootloop After flash Rom.do you have thé solution of your situation? Help me with it if you have.t hank

that requires you to do some modification
don't try it
i know this may seem off topic
but can you help me with something?

Stock rom for htc e9+

To whom may help me solve the issues I am facing,
My phone is stuck on the 'Setup wizard has stopped working' and I am not able to flash the original stock rom. Looking up the Setup wizard problem, I came across many posts but none helped. I suspect that the system files of my phone are corrupt. I can't exactly explain why, but it happened. I was trying to uninstall an app (apex launcher) which I had converted to system app. In the end, I had to do a factory reset through recovery.
On booting, I was shown the previously mentioned message and I can't go past it. I can't slide down the notifications nor click any of the soft keys. I tried every solutions posted by other users. This makes me suspect that the system files has become corrupt, and thus the Settings app cannot be opened.
I am new to flashing. I tried to flash the stock rom (RUU - 2gb zip) I found for my a55ml DTUL Europe J15, but it doesn't work. Maybe I need the recovery.img file for it to work? I need some guidance on this one. Can someone send me this recovery.img file?
My phone is rooted (kingroot), bootloader locked, S-ON. And, I can't detect it on ADB. Note: the phone is NOT on bootloop, and boots properly until the 'Setup wizard has stopped working'. I left the phone for flashing at a repair shop, but they tell me they are still trying.
And so, I seek help from anyone who can help me or point me towards someone else who can.

Updater process ended with ERROR 7- How can I fix this error?

Dear XDA-Developers,
After trying for many hours searching different forums and websites looking for help, I decided to make an account here and ask for help here.
I am currently on a Rooted OnePlus 5t with OxygenOs 9.0.3. I have not updated my phone in a really long time and decided to do so now.
I decided to dirty flash the full official ROM for OxygenOs 9.0.11 which was released recently with TWRP.
At first, I was on an older version of Blu_sparks recovery but replaced it with the newest TWRP from their website (Dumpling 3.3.1-0).
When I first tried to flash it, I got this error message:
failed: no space left on device
E1001: failed to update system image.
Updater process ended with ERROR 7:
Error installing zip file 'sdcard/download/Oneplus5Toxygen_43_OTA_054...
After trying multiple other recoveries, trying to flash with and without the compatibility zip and also trying to flash earlier versions of OxygenOS with different TWRP versions, I still get the same error message from TWRP as above.
Since it says that I supposedly don’t have enough free space, I looked for a way to change that and came across a thread which suggested to free some space by removing system apps that are not unnecessary, I tried doing that and flashing it again, but that also wasn’t successful.
My phone also has more than 10gb of free space.
I also tried to change the „assert“ line in the updater-script of the update, but I did not find any such line in the updater-script document in the zip file?
Does anyone know what causes this error message and what I can do to successfully update my phone?
And I was also wondering what would happen if I just let my phone regularly update it over settings?
It says that root is detected and my phone would be un-rooted once the after updating.
However, the update shown is only 1839mb so I’m very hesitant to do it.
But if I went through with this, would I just have to reroot my phone?
Will my recovery be replaced with the stock recovery, or will it remain TWRP?
Will my Bootloader get locked again?
Thank you so much for taking the time to read this, I appreciate it.
With kind regards,
Mutambo23