yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Q&A, Help & Troubleshooting] Rallerbabz:
The Note 3 does not have screen recording. It is not limited to hardware though, so it is possible in the future. Screen recording is built in with Android 4.4 and above, so you might see the feature in the upcoming 4.4 update for Note 3. However, it will probably not arrive until January sometime is my guess. It's also worth noting that especially Samsung is known for removing some of Androids core features and add some of their own. Therefore it's not sure that we will get screen recording with 4.4 for Note 3. With that being said, you can download an application that offers screen recording, however that require your phone rooted. Keep in mind that rooting will possibly break your warranty.

Sent from my Note 3
[Galaxy Note 3 Q&A, Help & Troubleshooting] stokedcrf:
Thanks for the info! Rooting Isn't a problem, and I'm ok with the warranty thing. I actually pay a monthly fee for an extended warranty because I drop phones a lot :)

I wish Samsung would be more like the Nexus series!

Any programs that record the screen that you guys recommend?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Rallerbabz:
I don't know any myself, I just know there are a few in the Play Store. I never had the need for it myself, so I haven't tried them out. I'd recommend searching in the playstore and looking for the most downloaded one as well as the one with most stars.

Sent from my Note 3
[Verizon Samsung Galaxy S 4] DFTBA7:
I've had a new custom ROM for a few week and everything is working fine, but out of no where I seem to have lost my root access. Nothing else is wrong with the phone and the custom ROM is all I have changed on the phone. I've tried to reroot it with various methods to no success. Does anyone have any solutions?
[Verizon Samsung Galaxy S 4] Mightycaptain:
More info... What rom? Are you mdk or Safestrap?
[Verizon Samsung Galaxy S 4] DFTBA7:
I'm using the PAC rom. Neither. Using TWRP.
[Verizon Samsung Galaxy S 4] -Lawless:
Try a 10 minute battery pull yet?
[Verizon Samsung Galaxy S 4] DFTBA7:
I just tried it and it didn't help.
[Verizon Samsung Galaxy S 4] hexitnow:
flash the zip in recovery

http://xdaforums.com/showthread.php?p=23427715

Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
[Verizon Samsung Galaxy S 4] DFTBA7:
It didn't work.
[Verizon Samsung Galaxy S 4] DFTBA7:
Should I try a full reset?
[Verizon Samsung Galaxy S 4] hexitnow:
Thats not going to make a difference. The recovery flashable zip should have worked which leads me to believe something else is up.

Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
[Verizon Samsung Galaxy S 4] DFTBA7:
Hmm, okay. Any ideas?
[Verizon Samsung Galaxy S 4] hexitnow:
Its hard to say but you could always flash the mdk stock image reroot then re rom. The motochopper method didnt work for you?

Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
[Verizon Samsung Galaxy S 4] k1mu:
When asked if you were running MDK or Safestrap, you answered "Neither". But you're using TWRP.

Is this a Developer edition S4? What build number shows up in Settings/More/About phone?
[Verizon Samsung Galaxy S 4] frow86:
This worked for me, Thanks for the help. I had root until I flashed pac man rom.
[Verizon Samsung Galaxy S 4] DFTBA7:
Sorry I misunderstood you, I'm running safestrap.

Build number is I545VRUAMDK
[Verizon Samsung Galaxy S 4] k1mu:
If you have MDK build, you're one of the very lucky people who can run arbitrary custom ROMs and don't need to use Safestrap. Please avoid upgrading beyond that as it will limit what you can do.
[Verizon Samsung Galaxy S 4] DFTBA7:
No, motochopper didn't work. I was going to try that but is there any way I wouldn't have to lose all my information? I use Titanium Backup, but since my root isn't working, I can't use it.
[Verizon Samsung Galaxy S 4] DFTBA7:
Okay. Thanks for the help.
[HTC Salsa] theschneidi:
Hey Salsa users and devs,

I try to build a clean CM 10.1 on my PC (Linux Mint 15 x64 on an Intel Core 2 Duo E8200 with 4GB RAM).

The CM 7/9/10 development thread seems a bit overloaded and I want to collect all neccessary facts, when I try to build CM 10.1.

What will be needed here?

- Manifest files for build a clean repository (which devicetree, linux kernel, display libs ...)

- Which patches were used?

- Kernel configs and additional kernel driver

What will be the aim?

- Get a functional CM 10.1 on HTC Salsa with most of the hardware features

Builds for testing pruposes will be posted here in this dev thread.

This thread is aimed for development purposes not for whishes like "Can you make feature xyz working?". It is the main task to get most of the things on Salsa working like front cam, camcorder, Bluetooth, GPS.
[HTC Salsa] vigoos:
Great Schneider!

In case you need the git here it is- https://github.com/vigoos/android_salsa_cm_10.1/

I've added front camera support, it must work now

Kernel version- Try this if you can- http://git.cryptomilk.org/projects/marvel/kernel_htc_msm7227-3.0.git

Feel free to tell me whatever you need, I'll provide.

Best Of Luck.
[HTC Salsa] theschneidi:
Thanks,

Still downloading all packages :eek:

Hope it will work :)

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />
<remote name="cryptomilk" fetch="git://git.cryptomilk.org/" />
<project name="projects/marvel/kernel_htc_msm7227-3.0.git" path="kernel/htc/msm7227" revision="master" remote="cryptomilk" />
<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="Ganster41/android_frameworks_av" path="frameworks/av" revision="jellybean"/>

<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>

<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="ProjectLlama/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/>
</manifest>
[HTC Salsa] theschneidi:
vendorsetup.sh needs to be changed ( marvel->icong ) :

add_lunch_combo cm_icong-userdebug

add_lunch_combo cm_icong-eng

BoardConfig.mk:

BOARD_VENDOR_QCOM_GPS_LOC_API_HARDWARE := icong

BOARD_EGL_CFG := device/htc/icong/egl.cfg

Error in Lunch, cannot find a file .. I know it is a mdpi phone but hdpi settings might work too

icong.mk:

# dalvik heap config for devices with 512MB memory

$(call inherit-product, frameworks/native/build/phone-hdpi-512-dalvik-heap.mk)

EDIT

libcamera/Android.mk:14: *** Leerer Variablenname

LOCAL_SRC_FILES := QcomCamera.cpp

:= mt9v113.c

needs to be

LOCAL_SRC_FILES := QcomCamera.cpp, mt9v113.c

EDIT2: in key/

marvel-keypad.kcm.bin -> icong-keypad.kcm.bin
[HTC Salsa] vigoos:
Thanks mate, I'll fix it once I get home.

EDIT 1- I'm getting a feeling front cam is gonna work this time around. If it doesn't I got one more way it can,
[HTC Salsa] theschneidi:
What does this error mean?

device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:50: error: Resource at config_networkLocationProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.

device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:53: error: Resource at config_geocodeProviderPackageName appears in overlay but not in the base package; use <add-resource> to add.

device/htc/icong/overlay/frameworks/base/core/res/res/values/config.xml:128: error: Resource at config_bluetooth_adapter_quick_switch appears in overlay but not in the base package; use <add-resource> to add.
[HTC Salsa] vigoos:
There's some problem in that XML it means, I'll study the XML from ma few other devices so I can get an idea where the problem is
[HTC Salsa] vigoos:
Fixed all these niggles.... I'll see the XML soon
[HTC Salsa] theschneidi:
In some threads I read that they deleted those lines in the XML. I will try that method first. Hope I'll get a build this evening. I got some other errors, which I post here in a few days.
[HTC Salsa] Olivier:
I don't mean to interrupt your conversation, but this kernel doesn't work (even on marvel) and the development has been dead for one year (or longer?) now. For CM10.1, 2.6 kernel can be used. We are even trying to get CM10.2 working on marvel using this kernel. :D

EDIT: You might want to check this and this out. :p

The manifest I'd suggest you to use... (remove my comments :p)

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />

<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />

<project name="Do not use 3.x kernel..." />

<!-- Fix framework -->

<remove-project name="CyanogenMod/android_frameworks_av" />

<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="jellybean"/>

<!-- Fix display -->

<remove-project name="CyanogenMod/android_hardware_qcom_display" />

<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>

<!-- Fix msm7k -->

<remove-project name="CyanogenMod/android_hardware_msm7k" />

<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="jellybean"/> androidarmv6 ones are newer, ProjectLlama is old.

</manifest>

You can use this kernel, but you'll probably have to add icong support.

Gesendet von meinem Xperia S mit Tapatalk
[HTC Salsa] theschneidi:
Ok, I will try it. Some things I had to change in kernel. When all things from 3.0 don't work I switch to the good old 2.6.x kernel.

OWL-Predator works with Salsa, the last CM10 for icong is built with it.

Vielen Dank DjOlivier :)
[HTC Salsa] vigoos:
Danke DjOlivier. It wasn't interrupting but it was rather a big boost.... So we will switch back to owl now. We are able to compile with owl properly, it is not a really big deal. And vielen dank for the XML. I'll fix it today.
[HTC Salsa] Olivier:
No problem... Here's CM10.1 git for marvel. I'm utterly convinced CM10.1 will work on icong. 3.x kernel has also been discontinued because the developer lacks time. There are many other devs who have tried to continue, but none of them has succeeded yet. If you need help with CM10.1, I'm here. Also [MENTION=5095490]Kevinjoa[/MENTION], [MENTION=4960614]thehacka1[/MENTION] or [MENTION=4749032]izi501[/MENTION] are experts from wfs fora... :)

Gesendet von meinem LT26i mit Tapatalk
[HTC Salsa] uberano26:
I got a Question if you dont mind me asking, how stable or bugfree is CM10.1 for WFS? Also since 4.4 got out why not just go directly for that as it seems to be running on a lot of the older devices.
[HTC Salsa] Olivier:
CM10.1 is 90-95% bugfree, there are some small bugs here and there but it depends on the user if he notices them or not. :p

As for CM11 (4.4), we are currently fighting with CM10.2 for WFS. I don't think it's possible to port it. Nah, wait: It's certainly possible, but that will cost you a huge amount of time and it will probably never run well. Support for ARMv6 was dropped long time ago and there are so many features that won't work on armv6. So let's better port CM10.1 and make it as stable as possible.

Gesendet von meinem LT26i mit Tapatalk
[HTC Salsa] theschneidi:
I would suggest the branch cm-10.1 instead of jellybean because it doesn't compile without error.

I try now airk000 instead of WinSuk.

The guys from AndroidARMv6 have a CM-10.2 and 11 branch too, so we can hope that maybe a device like Wildfire S or Salsa could run the newer Android versions. But that doesn't make sense, if only three or more people try to get these Android versions working. It is not very difficult but it takes a long time. I do that only in my free time as an engineer student.

EDIT:
[MENTION=4704398]vigoos[/MENTION]

device/htc/icong/libcamera/mt9v113.c:25:23: fatal error: linux/io.h: No such file or directory

I think media/mt9v113.h and mt9v113_regs.h could be the next error messages. I have to check this first, but mt9v113 is not in kernel 3.0.x. Switching back to an older kernel would be a better idea or I try to find the right files to integrate them into kernel.
[HTC Salsa] Olivier:
I totally agree with you, but why not using WinSuk's qcom display?

As I said above, 4.4 is possible. But I also lack time since I'm a student (who goes to school) and a build environment. Back to Kitkat, it may work, but if not, we have to accept that armv6 development slows down and it's only a matter of time until even devs abandon their projects and move along to other devices (if they haven't already). :D

Gesendet von meinem ODYS-Chrono mit Tapatalk 2
[HTC Salsa] Kevinjoa:
I made a CM10.1 build for icong but I am not sure if it will boot. I used marvel things and renamed them to icong. :)

Can anyone make a kernel config for icong based for this kernel :https://github.com/OWLProject/OWL-Predator-KERNEL

CM10.1 build is here: cm-10.1-20131115-UNOFFICIAL-icong.zip - 115.99 MB
[HTC Salsa] theschneidi:
In arch/arm/configs/cyanogen_msm7227_defconfig from OWL-Predator-KERNEL you find a config that works. Maybe CPU frequencies have to be changed.
[HTC Salsa] Kevinjoa:
Make me a icong.config and I will build rom again and you will tell me if it works :)
[HTC Salsa] vigoos:
mt9v113 is responsible for front camera. If the build compiles using mt9v113 files we got a good chance for front camera to work. I'll fork OWL kernel and see where do i need to add the .h files.

---------- Post added at 09:26 AM ---------- Previous post was at 09:21 AM ----------

Thanks for the build. I'll test it out. The size looks out of place to me because normal cm10 builds were 150MB . We have been managing all development just by renaming things from wildfire s.

I'll see the configs and report back.

EDIT1- I won't be having much time from this week because my college is going to reopen this week. I'll be getting time only on weekends or on holidays. So I will be a little late with replies.
[HTC Salsa] Kevinjoa:
Size is correct. Made a cm10 build for marvel. It is 145mb and cm10.1 builds should be 116 but I compiled with a defcobfig made for marvel and so I would like to know if it boots or not.

Gesendet von meinem Optimus G mit Tapatalk
[HTC Salsa] theschneidi:
Your build doesn't boot. Only whitescreen. I need to check if adb can show some messages why.

After I changed boot.img to one of my older CM10 it booted but showed every time force closes of android.phone and messaging. I tried to switch on bluetooth but phone crashed (maybe my kernel is responsible for that).
[HTC Salsa] Olivier:
When you replaced Boot.img, did you also change kernel modules?

Gesendet von meinem LT26i mit Tapatalk
[HTC Salsa] theschneidi:
No
[HTC Salsa] Kevinjoa:
Should I change defconfig to msm7227 one ? :)

I can make a new build if you want me too. ;)

I will at least compile kernel with this defconfig. :)
[HTC Salsa] Kevinjoa:
I have a github where I added manifest and device config for marvel and icong :)

The only thing we need to do is make kernel config for icong. ;)

So feel free to make any pull requests forks etc of my github see here: https://github.com/cm10-1-marvel
[HTC Salsa] theschneidi:
Latest config file I used is click me.

EDIT: sorry forgot to change frequency settings ... it needs to be

CONFIG_MSM_CPU_FREQ_ONDEMAND_MAX=800000

CONFIG_MSM_CPU_FREQ_ONDEMAND_MIN=122880

EDIT2: changed it
[HTC Salsa] theschneidi:
I get with that local manifests an error. :(

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<project name="CyanogenMod/android_device_htc_common" path="device/htc/common" revision="gingerbread" />
<project name="vigoos/android_salsa_cm_10.1" path="device/htc/icong" revision="jellybean-r2" />

<project name="OWLProject/OWL-Predator-KERNEL" path="kernel/htc/msm7227" revision="master"/>

<!-- Fix framework -->
<remove-project name="CyanogenMod/android_frameworks_av" />
<project name="androidarmv6/android_frameworks_av" path="frameworks/av" revision="cm-10.1"/>

<!-- Fix display -->
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<project name="WinSuk/android_hardware_qcom_display" path="hardware/qcom/display" revision="jellybean"/>

<!-- Fix msm7k -->
<remove-project name="CyanogenMod/android_hardware_msm7k" />
<project name="androidarmv6/android_hardware_msm7k" path="hardware/msm7k" revision="cm-10.1"/>

</manifest>

hardware/qcom/display/libgralloc/gpu.cpp: In constructor 'gralloc::gpu_context_t::gpu_context_t(const private_module_t*, android::sp<gralloc::IAllocController>)':
hardware/qcom/display/libgralloc/gpu.cpp:47:5: error: 'allocSize' was not declared in this scope
make: *** [/home/schneider/CYANOGENMOD/cm-10.1/out/target/product/icong/obj/SHARED_LIBRARIES/gralloc.msm7x27_intermediates/gpu.o] Fehler 1

EDIT: maybe fixed it

BoardConfig.mk needs in line 64 COMMON_GLOBAL_CFLAGS the flag -DQCOM_BSP
[HTC Salsa] Kevinjoa:
Use my manifest. I can build without errors. :)

https://github.com/cm10-1-marvel

I also made a device config there. It is fully cm10.1 compatible. ;)

Only thing is kernel. SO you have to make working kernel and you can use with my build. There are no cm updates anymore so no need for a new ful build. :P
[HTC Salsa] Kevinjoa:
Updated github :D
[HTC Salsa] Kevinjoa:
New Build.

Changes

Enabled icong board in kernel config. Changed max frequency to 800mhz.

DL: cm-10.1-20131118-UNOFFICIAL-icong.zip - 115.92 MB
[HTC Salsa] Kevinjoa:
Can anybody tell me if it boots ?

Gesendet von meinem Nexus 7 mit Tapatalk
[HTC Salsa] Darkorn:
It works.
[HTC Salsa] Kevinjoa:
Nice. :D

My source and manifest are linked here: github.com/cm10-1-marvel

So feel free to improve and send me pull requests. ;)

---------- Post added at 01:34 PM ---------- Previous post was at 01:11 PM ----------

Can you make a screenshot [MENTION=4860185]Darkorn[/MENTION] ,please. :D
[HTC Salsa] zeon321:
Wifi is not working. Except that everything looks good
[HTC Salsa] Olivier:
Can you please go to Settings -> about phone and make a screenshot? :D

Gesendet von meinem LT26i mit Tapatalk
[HTC Salsa] zeon321:
Here are the screenshots...
[HTC Salsa] Kevinjoa:
I will look on getting Wifi working at the weekend my friends. ;)
[HTC Salsa] Darkorn:
You need "-fno-pic" in wifi driver's flags, it's a known problem with the latest compiler version. This or the driver included in kernel doesn't work for our device.
[HTC Salsa] Kevinjoa:
You can do this, please. Just send me a pull request or give me moddified code because I am doing many exams at the moment. :)

My Github for this project: www.github.com/cm10-1-marvel.

Thanks. :)
[HTC Salsa] Darkorn:
You forgot to change this to icong

https://github.com/cm10-1-marvel/android_device_htc_icong/blob/cm-10.1/AndroidProducts.mk

And this too probably need a specific version for our phone https://github.com/cm10-1-marvel/an...ob/master/bluetooth/include/bdroid_buildcfg.h

For bluetooth we need this patch:

https://github.com/Luzifer1984/OWL-...mmit/e60b1b3bb5100b6f0d5b82fbed8244628df9d236

I already patched the file for you, it's board-icong.c

Ah, and this probably is not a good thing:

You need to change in icong_defconfig the lowest frequency to 122880.

Btw nice work.

I remembered the last time I tried OWL-Kernel I switched the bcm4329 directory with this one https://github.com/adumont/htc-kernel-msm7227/

I don't know why this works, anyway dmesg:

It just time out

Edit: Ah, and in your rom there isn't the system/lib/bcm4329.ko module
[HTC Salsa] Darkorn:
And probably we need this line too so apps can see we have a front camera, I tried but still can't switch camera.
[HTC Salsa] Darkorn:
-Gallery sometimes crashes when reproducing videorecorded video.

-Wifi works substituting old wifi driver from htc's kernel.

-Usb thethering doesn't work.

-Glitches in photo editing
[HTC Salsa] Darkorn:
Since karan128 asked me, I'll share the OWL-Kernel with the original icong wifi's driver and bluetooth fix until someone find a way to make the new driver works.
[HTC Salsa] vigoos:
I put those files in kevinoja s build and things work well, no problems. Only thing is music player lagged when screen was turned off. So I changed minimum frequency to 245 from 122. This one is all good. The keyboard wasnt coming when I Wanted to type something initially, reinstalling it worked.
[HTC Salsa] think-only:
failed install rom

hello, can you help me...

I cannot install this rom via cwm v5.0.2.6. my devices unlocked but still s-on.

when i wanna to install is failed (status 7). can you explaint its.. :)
[HTC Salsa] theschneidi:
Status 7 .. the first line (getprop ...) in updater-script has to be removed or cwm needs to be changed
[HTC Salsa] theschneidi:
Something new in development?
[HTC Salsa] vigoos:
Nope, nothing new :(
[HTC Salsa] zeon321:
Anyone started working on cm11 ?
[HTC Salsa] Olivier:
No, we're still working on CM10.2 which keeps rebooting to recovery instead of booting normally. If there are any developers interested, PM me and I'll add you to a dev hangout on G+. Once this boots on the Wildfire S, it can be easily ported to the Salsa.

But I have a new CM10.1 build for you guys with some fixes and a LZMA-compressed kernel. Please give feedback.

Download: http://goo.im/devs/djolivier/icong/MarvelMod/cm-10.1-20140323-UNOFFICIAL-icong.zip

Gesendet von meinem Xperia S mit Tapatalk
[HTC Salsa] think-only:
Thanks... good works.:good:
[HTC Salsa] Olivier:
Can you please post screenshots (Settings/about phone)?
[HTC Salsa] zeon321:
Unable to flash it. Getting status 7 in cwm
[HTC Salsa] Olivier:
Read the previous page, there's a fix.

Are there actually any Salsa devs out here BTW?
[HTC Salsa] theschneidi:
Thanks, I will try it on the weekend and send you my feedback if bugs appear.

I had not so much time to do something on CM10.1 sorry. :( My HTC Salsa is now two years old (lost all its HTC letters on the back :P ) and maybe I buy a new phone soon.
[HTC Salsa] Olivier:
I actually want to get CM10.2 to work on HTC MSM7227 devices... As already mentioned above you can contact me so I can add you to the hangout if you want. :)

Gesendet von meinem Xperia S mit Tapatalk
[HTC Salsa] Olivier:
Alright we have an (almost) fully working CM10.2, CM11 will follow soon. If you guys are interested in CM10.2 and CM11 too, let me know. Before I can build it, I have to know the partitions (do have have the same as the Wildfire S?).

EDIT1: Here's my device config.

EDIT2:
[HTC Salsa] BigBearEvo:
exactly the same setup as wildfire s. only difference is we have a faster cpu.

im happy to test it out if built.

i use my salsa as a spare phone and for satnav purposes while away on camps etc.
[HTC Salsa] Olivier:
Okay, here's a taste of KitKat for you guys. Please test and give feedback.

cm-11-20140501-UNOFFICIAL-icong.zip - 122.33 MB
[HTC Salsa] BigBearEvo:
will test this weekend when i get my phone
[HTC Salsa] BigBearEvo:
This pacakage if for "icong" deivices; this is a "marvel".

status 7 error
[HTC Salsa] Olivier:
Just remove the first few lines in the updater-script, this problem has already been fixed in the sourcecode.
[HTC Salsa] BigBearEvo:
ill have a look when i get my pc running and amend it
[HTC Salsa] Olivier:
Why amending it? And how come it says your phone is a marvel?
[HTC Salsa] BigBearEvo:
im not on my setup to remove the lines from the updater script and unknown, was this a straight copy from the wildfire?
[HTC Salsa] theschneidi:
CWM is maybe ported from Wildfire S.
[HTC Salsa] Olivier:
No. This has been compiled from source. android_device_htc_icong

Hmm. Just try to remove that assert line and flash it. If that doesn't work, grab the marvel build from the Wildfire S forum and flash it lol.
[HTC Salsa] BigBearEvo:
installing.............failed

set_metadata_recursive: some changes failed.

will take another look later on
[HTC Salsa] Olivier:
If marvel recoveries work for you - try TWRP 2.7. It's in our dev section...

Gesendet von meinem Xperia S mit Tapatalk
[HTC Salsa] BigBearEvo:
the only marvel recovery we got working are cwm 5.0.2.6 and raidzero not managed to get any others to work for us