I've seen users lately with the low incall volume issue on our devices I have adjust the mixer paths to make the earpiece volume louder this is in beta stages and still testing and thought I would share with the community
BEWARE THIS CAN POTENTIALLY BREAK THE EARPIECE NIT SAYING IT WILL BUT HAVE TO PUT THE WARNING UP I HAVE TESTED FOR A VERY LONG TIME IF U DONT HAVE TO HAVE THE VOLUME UP ALL THE WAY IF U DINT WANT TO I KEEP IT TO ABOUT HAKF OR ALITTLE MORE ..
INSTRUCTIONS: EXTRACT THE ZIP FILE YOU CANNOT FLASH IT MAKE SURE U BACKUP THE MIXER PATH TASHA THATS IN SYSTEM/ETC SAVE IT SOME WHERE THEN TAKE THE MIXER PATH TASHA FROM MY ZIP AND REPLACE THE FILE AND SET PERMISSIONS TO RWRR THEN REBOOT. REMEMBER THIS ZIP CANNOT BE FLASHED AT THE MOMENT ENJOY .....
DOWNLOAD LINK V1: https://www.androidfilehost.com/?fid=529152257862718364
PLEASE GUYS LET ME KNOW WHAT U THINK THANKS
Thanks to @Nopppa for testing
STATUS....... UPLOADED
XDA:DevDB Information
EARPIECE FIX, Tool/Utility for the OnePlus 3
Contributors
genuine55, Nopppa
Version Information
Status: Testing
Current Beta Version: V1
Beta Release Date: 2017-04-10
Created 2017-03-26
Last Updated 2017-04-10
edit root/system/etc/mixer_paths.xml and change the value (default is 84). 95 is the new high value (look for <path name="speaker">).
<path name="speaker">
<ctl name="SLIM RX1 MUX" value="AIF1_PB" />
<ctl name="SLIM RX2 MUX" value="AIF1_PB" />
<ctl name="SLIM_0_RX Channels" value="Two" />
<ctl name="RX7 MIX1 INP1" value="RX1" />
<ctl name="RX8 MIX1 INP1" value="RX2" />
<ctl name="RX7 Digital Volume" value="95" />
<ctl name="RX8 Digital Volume" value="95" />
<ctl name="COMP0 Switch" value="1" />
</path>
Is there a similar solution for bluetooth streaming?
Vaibhunk786 said:
edit root/system/etc/mixer_paths.xml and change the value (default is 84). 95 is the new high value (look for <path name="speaker">).
<path name="speaker">
<ctl name="SLIM RX1 MUX" value="AIF1_PB" />
<ctl name="SLIM RX2 MUX" value="AIF1_PB" />
<ctl name="SLIM_0_RX Channels" value="Two" />
<ctl name="RX7 MIX1 INP1" value="RX1" />
<ctl name="RX8 MIX1 INP1" value="RX2" />
<ctl name="RX7 Digital Volume" value="95" />
<ctl name="RX8 Digital Volume" value="95" />
<ctl name="COMP0 Switch" value="1" />
</path>
Click to expand...
Click to collapse
What's weird is that didn't work for me I had to use mixer paths tasha XML I will be releasing the file shortly
Does this fix the weird distortion sound that we get on custom roms while calling someone.
The voice cut thing
genuine55 said:
What's weird is that didn't work for me I had to use mixer paths tasha XML I will be releasing the file shortly
Click to expand...
Click to collapse
Hi. Waiting on the file. Or, could you tell me what to edit in the mixer paths tasha file? I have the same file in my etc folder.
So no file?
Sorry my phone had broke just got back up and running will be releasing the file soon have to re do it being that i have a new device
help us by providing a flashable zip
toufiq47 said:
help us by providing a flashable zip
Click to expand...
Click to collapse
Are u on Oxygen Os one plus 3 device ? I need the mixer paths Tasha from system /etc if some one can provide that file this would help me get it out faster being that I don't have the one plus 3 any more thanks
genuine55 said:
Are u on Oxygen Os one plus 3 device ? I need the mixer paths Tasha from system /etc if some one can provide that file this would help me get it out faster being that I don't have the one plus 3 any more thanks
Click to expand...
Click to collapse
Sent you a link via private message. Contains mixer_paths_tasha.xml from OxygenOs 4.1.0
Nopppa said:
Sent you a link via private message. Contains mixer_paths_tasha.xml from OxygenOs 4.1.0
Click to expand...
Click to collapse
Thanks I will fix it up when I get off work and if my testers say it's cool will release it right after being that I don't have the device anymore.
As for me, my earpiece volume was very low for 3 or 4 days without any cause.
But it was back again to normal after that.
Link is now Live guys let me know what u think and if it helped u hit the thanks button again enjoy.....Thanks @Nopppa for testing
RohanAJoshi said:
As for me, my earpiece volume was very low for 3 or 4 days without any cause.
But it was back again to normal after that.
Click to expand...
Click to collapse
These phone be doing weird **** sometimes lol
Anyone tried this?
Sent from my OnePlus3 using XDA Labs
Disregard
Prattham said:
Anyone tried this?
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
@Nopppa tried it u can ask him he was my tester :good:
Prattham said:
Anyone tried this?
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
I tested this and it works.
Thanks
Can confirm this works. Can actually hear people now.
Related
I just discovered that the bootloader for the Photon Q xt897 can be (re)locked with Rsdlite and a couple small edits.
To do this you will need the newest version of Rsdlite (https://sites.google.com/site/motosbf/rsdlite), the firmware for your phone available here http://sbf.droid-developers.org/asanti_c and your unlock code that you recived from Motorola when you unlocked your device.
To be able to flash this firmware with Rsd you will need to delete the "getvar" lines and add lines for the "oem lock begin" & "oem lock" commands.
When you have finished editing your xml file it should look similar to the one I have attached below. The "0000000000000000" you need to replace with your unlock code.
Please edit your own, do not copy/paste this as the MD5's may change!
I am not responsible if you brick your device.
This WILL wipe your phone!!!
The "unlocked bootloader" warning will not go away, and your warranty is still void...
PS. You can still flash a new logo with a locked loader.
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="ASANTI_CFC" />
<software_version version="asanti_c-user 4.0.4 7.7.1Q-6_SPR-125_ASA-14 15 release-keysASANTI_C_BP_1139.000.18.09P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="partition" filename="gpt_main0.bin" MD5="6C05E70F1DCC59AD92B0BBEC4E6100ED" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="22143B801329D93CAFCF909AA7DACBCF" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="37F5C89BB439DDB5831F6A1EB7AE918F" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="7735EFCDFBC604F093045F72E44269F1" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="919D0B340CFDD5FC7C541803DB65C2D6" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="E7E984C848F0B46C8A9F8E06E10DAFA9" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="617658958400102A3CD5788F95D5D810" />
<step operation="reboot-bootloader" />
<step operation="oem" var="lock begin" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="313A4EC7B8DED02E135C8C676382D799" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="D9253046F7C7E6EE17B9B3327BB0F6BE" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="0c02867ba4e0baa941ba665c4b8efbfa" />
<step operation="flash" partition="boot" filename="boot.img" MD5="38EDDB640B6889AC668FE91817B7A7F6" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="4b25ebc4662edb8bb92e6c7eec9426c6" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="0D2D38BE5BCC0C3F84488B2FC77B64BE" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="364D33B631EBFAE1E46BB615B2690EA4" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="DA73A05D7188132BC27031BBC252E76C" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
<step operation="oem" var="lock 0000000000000000" />
</steps>
</flashing>
((Posted in General with no links because I am "new" and this is my 3rd post ))
Has anyone tried this successfully?
If so, I think this should be stickied...
Works for me, not sure if anybody else had any luck though. I could edit it to be a little easier to understand if needed, This was the only way I was able to re-lock my MofoQ.
Thanks though!!
Sent from my XT897 using Tapatalk 2
Is that the full phone image sbf? Ive been looking for an sbf to fullly set my phone to stock/relock/unroot/ delete everything... was availlable for the old photon...
Sent from my XT897 using xda premium
Yup, just not called SBF's anymore. Same result though.
Sent from my XT897 using Tapatalk 2
hfase said:
Yup, just not called SBF's anymore. Same result though.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Where can i get the file and how do i flash?
Sent from my XT897 using xda premium
bradleymaustin said:
Where can i get the file and how do i flash?
Click to expand...
Click to collapse
The recovery image you need can be downloaded here;
http://sbf.droid-developers.org/asanti_c
RSDlite you can get here;
https://sites.google.com/site/motosbf/rsdlite
Once you download your recovery image you need to extract it and edit the XML file to match the one I have posted in the OP.
There are a couple "getvar" lines that need to be deleted, and above I have added the "oem lock" lines.
As said in the first post, your "unlocked bootloader" warning will not go away, and your warranty is still void...
Sent from my XT897 using xda premium
hfase said:
As said in the first post, your "unlocked bootloader" warning will not go away, and your warranty is still void...
Click to expand...
Click to collapse
Hey there, I just followed your instructions from the first post with some slight variations... I did not put any code in the last line (where oem lock takes place), in other words, I just deleted the 0's... I also replaced the original logo.bin file with the one here and that 'removed' the unlocked bootloader screen!
cheers!
English:
Yeahhhhhhhhhhh on my Motorola Razr HD (XT925) worked but I had to change the code and put the firmware this topic: click
and the code is:
<step operation="oem" var="lock begin" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="partition_signed" MD5="9a6775e7a676e0a4cd82f05f4b0c4e2e" />
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="e07446f7ebc6985624a276bbbe39ed9e" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="43d4ca47a8f72ab974e3e587045c01b2" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="aa49e8361f5f14d5feabe2e7ef7554cb" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="da48c189336c7d8a420747ebbaf2d172" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="bd4d8cd7a5889aa75e8de7a323588250" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="ab0273c6600e8b031bc87456a48d9c96" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="b0069bec54160c6ed51b8685dbc71490" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="6e24a8be2c3102c0bd5c8158b47f8faf" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="e685220af2c119233b192f94182bfeb0" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="95521869ded3115a15b6b3a3e353cd14" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="d63e9f5dee9401feb873c7e29c5fcb7c" />
<step operation="flash" partition="system" filename="system_signed" MD5="0807e33253ec0b4a89dfada07dda7bd6" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="fa89d8b6eed33bad336351bdd6e76cce" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata"/>
<step operation="oem" var="fb_mode_clear" />
<step operation="oem" var="lock 00000000000000000000" />"oem"/>
Click to expand...
Click to collapse
after doing a firmware via RSD error gave the last part but was only re-enter the bootloader was locked and note that again there and so do the firmware is locked and ready soon again
sorry my bad english I'm Brazilian and I'm using Google Translator
Portuguese:
Yeahhhhhhhhhhh no meu Motorola Razr HD (XT925) funcionou mas eu tive de mudar o código e colocar a firmware deste tópico: clique
e o código é:
esta logo acima então não vou colocar de novo
depois de fazer a firmware pelo RSD e dará um erro na ultima parte mas só foi entrar de novo no bootloader e constatar que estava bloqueado de novo ai e só fazer a firmware da logo e pronto esta bloqueado de novo
Returned to original, re-locked and no warnig screen. Excellent! Thank you , to all of you!
Device is LOCKED. Status Code: 2
Wow. Thank you. :good:
I spent about 8 hours going from not booting with failed TWRP recovery install, to booting with TWRP installed (unlocked), back to stock XT897 Sprint and unlocked, and finally to stock and locked.
I did notice on the Fastboot screen, the message is now "Device is LOCKED. Status Code: 2" from the original "Device is LOCKED. Status Code: 0". Too bad we can't clear that second bit .
Regards,
vcharts
I need to take my Photon Q back to stock. I'm currently running CM11, cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl.zip. Is there anyway to take it back to stock and remove the "unlocked bootloader" warning yet? I might need to switch to T-mobile, they would buy my phone from me, but I want it to look like it hasn't been rooted.
EpicSaga said:
I need to take my Photon Q back to stock. I'm currently running CM11, cm-11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl.zip. Is there anyway to take it back to stock and remove the "unlocked bootloader" warning yet? I might need to switch to T-mobile, they would buy my phone from me, but I want it to look like it hasn't been rooted.
Click to expand...
Click to collapse
Why are you crossposting.
arrrghhh said:
Why are you crossposting.
Click to expand...
Click to collapse
I had more typed here, then I deleted it. My mistake.
tell me who is trying to build cm 11 for trebon i m thinking tomorrow to start downloading source code for trebon and tell me all about errors when compyling what version of linux are you using etc... i m trying to get some info
yjosipy said:
tell me who is trying to build cm 11 for trebon i m thinking tomorrow to start downloading source code for trebon and tell me all about errors when compyling what version of linux are you using etc... i m trying to get some info
Click to expand...
Click to collapse
i'm trying
im using ubuntu 13.10 with kernel 3.11
using any other kernels gives me errors that are solved by reinstalling grub but the other kernels can't be loaded as the grub is not updated
i complied just once and it broke because of no space
now im trying a new 250 gb hdd and if i manage to finnaly boot ubuntu now i will try the damn compilation
i have the source code already downloaded so i will be lucky (on a pentium dual core 2.20, 3 gb ram ddr2 it took 270 minutes to repo sync)
p.s. of course ubuntu 64 bit but as i have ddr2 ram its slow as hell
ShadowsDie said:
i'm trying
im using ubuntu 13.10 with kernel 3.11
using any other kernels gives me errors that are solved by reinstalling grub but the other kernels can't be loaded as the grub is not updated
i complied just once and it broke because of no space
now im trying a new 250 gb hdd and if i manage to finnaly boot ubuntu now i will try the damn compilation
i have the source code already downloaded so i will be lucky (on a pentium dual core 2.20, 3 gb ram ddr2 it took 270 minutes to repo sync)
p.s. of course ubuntu 64 bit but as i have ddr2 ram its slow as hell
Click to expand...
Click to collapse
f*ck i have amd athlon p320 dual core 2.10gHz and 2gb of ddr3 ram (laptop) i hope i can compile it wirh that can you tell me is it req to have 64bit os
yjosipy said:
f*ck i have amd athlon p320 dual core 2.10gHz and 2gb of ddr3 ram (laptop) i hope i can compile it wirh that can you tell me is it req to have 64bit os
Click to expand...
Click to collapse
well.....
64bit ubuntu is a must if you want to build cm and normally 64bit is for more than 2gb ram (4 gb recommendedm 3 minimum)
but... you can try
it will run very slow to you
ShadowsDie said:
well.....
64bit ubuntu is a must if you want to build cm and normally 64bit is for more than 2gb ram (4 gb recommendedm 3 minimum)
but... you can try
it will run very slow to you
Click to expand...
Click to collapse
i had 4 gb and one card died anyway i will try it:cyclops:
yjosipy said:
i had 4 gb and one card died anyway i will try it:cyclops:
Click to expand...
Click to collapse
the problem with 64 bit OS is that you sacrifice ram for a better cpu performance (almost 10%)
and sync repo takes a lot of cpu
but you need ram to sacrifice
ShadowsDie said:
the problem with 64 bit OS is that you sacrifice ram for a better cpu performance (almost 10%)
and sync repo takes a lot of cpu
but you need ram to sacrifice
Click to expand...
Click to collapse
and how much of source code do i need to download i mean how many gigabytes
yjosipy said:
and how much of source code do i need to download i mean how many gigabytes
Click to expand...
Click to collapse
i don't remember exactly but its something between 12-20 gb
anyway the download speed is slow but then is not only the download, is the proper position of the files
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
ShadowsDie said:
i don't remember exactly but its something between 12-20 gb
anyway the download speed is slow but then is not only the download, is the proper position of the files
Click to expand...
Click to collapse
if you manage to boot on ubuntu without any error (and im sure you will have errors) i could help you with the steps through skype or something
just saying because my ubuntu updates the kernel and then gives errors then i have to reinstall grub and then i have a nvidia drivers problem
hope you don't have nvidia
ShadowsDie said:
i don't remember exactly but its something between 12-20 gb
anyway the download speed is slow but then is not only the download, is the proper position of the files
---------- Post added at 09:21 PM ---------- Previous post was at 09:19 PM ----------
if you manage to boot on ubuntu without any error (and im sure you will have errors) i could help you with the steps through skype or something
just saying because my ubuntu updates the kernel and then gives errors then i have to reinstall grub and then i have a nvidia drivers problem
hope you don't have nvidia
Click to expand...
Click to collapse
i have one error at startup i think i can solve it easily i m using radeon hd4200 lucky me tomorrow i will install git and all other goodies
Edit:this is mine error kvm:disabled by bios
Edit2:that error hurts no one
yjosipy said:
i have one error at startup i think i can solve it easily i m using radeon hd4200 lucky me tomorrow i will install git and all other goodies
Edit:this is mine error kvm:disabled by bios
Edit2:that error hurts no one
Click to expand...
Click to collapse
did you have any unloaded kernel error?
anyway try do not update the kernel
if you are on 3.11 its ok
p.s.
i will help you with this
at obtaining the proprietary files this should do the trick
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
Then: brunch trebon
p.s. 2
the whisp has our cm11 drivers, i'm very happy
ShadowsDie said:
did you have any unloaded kernel error?
anyway try do not update the kernel
if you are on 3.11 its ok
p.s.
i will help you with this
at obtaining the proprietary files this should do the trick
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
Then: brunch trebon
p.s. 2
the whisp has our cm11 drivers, i'm very happy
Click to expand...
Click to collapse
tnx for that i think i can handle it
Edit:started to syncing
yjosipy said:
tnx for that i think i can handle it
Edit:started to syncing
Click to expand...
Click to collapse
sry, i came now from my holidays
how is it going? i want to know if i do it as well or you are ok
ShadowsDie said:
sry, i came now from my holidays
how is it going? i want to know if i do it as well or you are ok
Click to expand...
Click to collapse
well the good news is that there is still no errors and i asked help from user named Rox from ace 2 forum (who speaks my language and lives about 70km from my house ) he will help us out but the bad news is that i had to pause syncing so that means i m still downloading
yjosipy said:
well the good news is that there is still no errors and i asked help from user named Rox from ace 2 forum (who speaks my language and lives about 70km from my house ) he will help us out but the bad news is that i had to pause syncing so that means i m still downloading
Click to expand...
Click to collapse
Good job, let me know if something happens, i'll try to help as much as I can
ShadowsDie said:
Good job, let me know if something happens, i'll try to help as much as I can
Click to expand...
Click to collapse
nopeee its cheking files :victory: now tell me how to add thewisps repos to manifests
yjosipy said:
nopeee its cheking files :victory: now tell me how to add thewisps repos to manifests
Click to expand...
Click to collapse
initialize environment
$ . build/envsetup.sh
Then i think you have to get the missing repo by typing "breakfast trebon" but im sure it will not work
Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
then make the manifest look like this
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
save the file then repo sync again
hope it helps
Edit: can't we talk via any messenger? because i often check xda every hour and we cant communicate that fast
hopefully we will finish this soon...
ShadowsDie said:
initialize environment
$ . build/envsetup.sh
Then i think you have to get the missing repo by typing "breakfast trebon" but im sure it will not work
Then create a file with the name local_manifest.xml in the local_manifests directory. To see this directory, you have to press Ctrl-H in your file manager.
then make the manifest look like this
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- CM replacements -->
<remove-project name="CyanogenMod/android_frameworks_native" />
<project path="frameworks/native" name="omnirom/android_frameworks_native" revision="android-4.4" />
<!-- Local projects -->
<project path="external/webkit" name="legaCyMod/android_external_webkit" revision="cm-11.0" />
<project path="hardware/atheros/wlan" name="TheWhisp/android_hardware_atheros_wlan" revision="cm-11.0" />
<project path="hardware/qcom/display-legacy" name="TheWhisp/android_hardware_qcom_display-legacy" revision="jellybean-mr2" />
<project path="hardware/qcom/media-legacy" name="Dazzozo/android_hardware_qcom_media-legacy" revision="jellybean-mr2" />
<project path="device/samsung/msm7x27a-common" name="yazidkucrit/android_device_samsung_msm7x27a-common" revision="cm-11.0" />
<project path="device/samsung/trebon" name="yazidkucrit/android_device_samsung_s7500" revision="cm-11" />
<project path="kernel/samsung/msm7x27a-common" name="yazidkucrit/kernel_KeongBalap" revision="master" />
<project path="vendor/samsung" name="yazidkucrit/proprietary_vendor_samsung_msm7x27a" revision="cm-10.2" />
<!-- FM Radio -->
<project path="hardware/qcom/fm" name="legaCyMod/android_hardware_qcom_fm" revision="cm-11.0" />
<project path="packages/apps/FM2" name="legaCyMod/android_packages_apps_FM2" revision="cm-11.0" />
</manifest>
save the file then repo sync again
hope it helps
Edit: can't we talk via any messenger? because i often check xda every hour and we cant communicate that fast
hopefully we will finish this soon...
Click to expand...
Click to collapse
yes why not my fb name is joosipp
i invited someone with that name thell me if its you
ShadowsDie said:
i invited someone with that name thell me if its you
Click to expand...
Click to collapse
nope try this www.facebook.com/joosipp
yjosipy said:
tell me who is trying to build cm 11 for trebon i m thinking tomorrow to start downloading source code for trebon and tell me all about errors when compyling what version of linux are you using etc... i m trying to get some info
Click to expand...
Click to collapse
I have successfullly ported cm11 to our device!!
But I can't upload It and share It with you due to bad internet connection (upload speed~12 Kb/s).... :crying: :crying: :crying: :crying:
Hello,
First, sorry for my english i'm french, and i want help for my device xt925
i have, since few months a boot trouble, at first, device was bloqued on the motorola logo (sfr retail french firmware)
i try wipe, wipe cache ...
i try flash with rsdlite ...
i try flash with custom recovery with cyanogen mod
every time it's the same thing, device is blocked on boot
i try flash again with rsd lite, but now :
Device is unlocked, Status Code : 3
Batterie OK
Trafsfer Mode:
USB connected
Fastboot reason: Flash Failure
usb connected
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
i try :
9.8.2Q-8-XT925_VQU-27_USERSIGNED_S7_USAVANQUSFRLTEON031.0R_LSAVNQJBVFFR_P019_A018_S1FF_fb.xml
9.8.2Q-8-XT925_VQU-22_USERSIGNED_S7_UCAVANQU02NA02F.0R_LSAVNQJBRTFR_P007_A004_CFC.xml
9.8.0Q-97-XT925_VQU-18_USERSIGNED_S7_USAVANQUSFRLTEON027.0R_LSAVNQJBVFFR_P015_A013_CFC.xml
and
7.7.1Q_144_VQU_S3-35-1101_SIGNED_SIGNEMEA_USAVANQUSFRLTEOFF021.0R_LSAVNQICSVFFR_P043_A038_CFC.xml
every time the same bug at time i flash the device ...
i'm desperetate now, but i think there is a solution, but i don't find it
thanks so much for your help !
Try using the GPT fix here:
http://forum.xda-developers.com/showthread.php?p=51674838#post51674838
You just need to have it do the first step in the xml file. I would remove the others since I think they flash xt926 firmware.
killrhythm09 said:
Try using the GPT fix here:
http://forum.xda-developers.com/showthread.php?p=51674838#post51674838
You just need to have it do the first step in the xml file. I would remove the others since I think they flash xt926 firmware.
Click to expand...
Click to collapse
thank's for retry, i download it and i try
i have downoladed it but what i do now ?
i d'ont understant what you means that :
You just need to have it do the first step in the xml file. I would remove the others since I think they flash xt926 firmware.
58926968
eelyakusa said:
i have downoladed it but what i do now ?
i d'ont understant what you means that :
You just need to have it do the first step in the xml file. I would remove the others since I think they flash xt926 firmware.
Click to expand...
Click to collapse
I try with the : WindowsUtility, and i flash it, the phone reboot, but it freeze on the boot : at the android animation with the sound droid, there is 5 secondes of animation and after, freeze et reboot ...
are u sure i can use it for my xt925 device, i havnt xt926 ?
This is my movie to show you the trouble after use WindowsUtility to flash :
youtube.com/watch?v=BnGdLTxsMtk&feature=youtu.be
Hi i'm french too so sorry for my english.
I can say that i have tested a lot of rom and i was sometimes in your case.
You must install the stock ROM 7.7.1Q_144_VQU_S3-35-1101_SIGNED_SIGNEMEA_USAVANQUSFRLTEOFF021.0R_LSAVNQICSVFFR_P043_A038_CFC with RSD Lite but you must remove some line in the file .xml
This is my file.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="vanquish_u-user 4.0.4 7.7.1Q-144_VQU_S3-35-1101 1346291514 release-keysVANQUISH_U_BP_1045.711.53.60P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="e3ee7bc4dcc5229a92eafcd317e94bdb" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="177dde66798c444367465ec37d4195f3" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="827ad3ed25fb1cb3e46ede6c080a126c" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="0179643ecc8edb6ce3f1023f8a41a96a" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="9a6a65df2852ffc574f7fe6965dc68a4" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="04f7efbe6f2ce2e7414b92c25b19ca1e" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="80beb3705fecca20334de98d1cab99c6" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="d12bcccdce5aaef0c9de2110e0511e70" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7611e3380011d9e17e4dc6ea05eecc2f" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="b6beeb3d5b29eb48b1c1d6996b2e4884" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="d54d124558b81c089d43383f0fa8587c" />
<step operation="flash" partition="system" filename="system_signed" MD5="1edad4648a6fc89980ee945040c744ca" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="74ae9071ae8f3d08d599e7a6c5a9ddd1" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
That's always working for me.
Then i put a recovery CWM 6.0.2.8 for install 4.2 ROM
Then i put recovery TWRP v2.6.3.0 (The version for 16Gb no EMMC the only who works for me) and i install a 4.4 Rom
Actually i'm on the RemixPA Rom beta 2 she's awesome ! All is working fine and very good battery life.
MP me if you want more explanation on it.
CeBBe said:
Hi i'm french too so sorry for my english.
I can say that i have tested a lot of rom and i was sometimes in your case.
You must install the stock ROM 7.7.1Q_144_VQU_S3-35-1101_SIGNED_SIGNEMEA_USAVANQUSFRLTEOFF021.0R_LSAVNQICSVFFR_P043_A038_CFC with RSD Lite but you must remove some line in the file .xml
This is my file.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="vanquish_u-user 4.0.4 7.7.1Q-144_VQU_S3-35-1101 1346291514 release-keysVANQUISH_U_BP_1045.711.53.60P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="e3ee7bc4dcc5229a92eafcd317e94bdb" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="177dde66798c444367465ec37d4195f3" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="827ad3ed25fb1cb3e46ede6c080a126c" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="0179643ecc8edb6ce3f1023f8a41a96a" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="9a6a65df2852ffc574f7fe6965dc68a4" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="04f7efbe6f2ce2e7414b92c25b19ca1e" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="80beb3705fecca20334de98d1cab99c6" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="d12bcccdce5aaef0c9de2110e0511e70" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7611e3380011d9e17e4dc6ea05eecc2f" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="b6beeb3d5b29eb48b1c1d6996b2e4884" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="d54d124558b81c089d43383f0fa8587c" />
<step operation="flash" partition="system" filename="system_signed" MD5="1edad4648a6fc89980ee945040c744ca" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="74ae9071ae8f3d08d599e7a6c5a9ddd1" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
That's always working for me.
Then i put a recovery CWM 6.0.2.8 for install 4.2 ROM
Then i put recovery TWRP v2.6.3.0 (The version for 16Gb no EMMC the only who works for me) and i install a 4.4 Rom
Actually i'm on the RemixPA Rom beta 2 she's awesome ! All is working fine and very good battery life.
MP me if you want more explanation on it.
Click to expand...
Click to collapse
THANKS !!!!!!
It's good, i flash with this XML and it's good, i'm on the ICS rom but, if i try to download JB retail with the whone, the same bug at the boot, freeze ...
do you think there is an explication ??
eelyakusa said:
THANKS !!!!!!
It's good, i flash with this XML and it's good, i'm on the ICS rom but, if i try to download JB retail with the whone, the same bug at the boot, freeze ...
do you think there is an explication ??
Click to expand...
Click to collapse
Yes the xml with the JB ROM must be arranged. You must delete some line.
This is the xml for the JB ROM :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQU-27 1360044270 release-keysMSM8960BP_100700.250.66.01P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="0c3ecc0f49997bf49c1e0067cce9b050" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="0c31626579b5de9814187232a33b550e" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="0036df14a28b3eb242567594ae17f844" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="b10a918c890890e087e288bc3fa70ad7" />
<step operation="flash" partition="tz" filename="tz_signed" MD5="8057e2551c3a21c2765d48212464836c" />
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="b16d257741c8cb1577e6edfdd206f404" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="92612d2c83854dedf78696d1f7bd024c" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="5d445d5b3dfa7794e0f18ab97969341e" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="3439c9a742ba3be162e2e057a58c4475" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="28b4dcdfb43ce6778c21630ae67c05ee" />
<step operation="flash" partition="system" filename="system_signed" MD5="8f0a9f4c2e7b2ac9b117398a867ee2ba" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
</steps>
</flashing>
Hope this will help.
Hi,
Just tried to flash JB (retail brasil) back over updated KK and a downgrade protection message appeared, now it's stuck in fastboot mode. =/
Is it possible to unbrick it? How do I do it?
Thanks.
solved! =D
just unbricked it! =DD
if anyone ever need it:
delete the highlighted lines from xml and flash
Code:
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="VANQUISH_U" />
<software_version version="XT925_retbr-user 4.1.2 9.8.2Q-50-XT925_VQLM-21 1361658266 release-keysVANQUISH_U_BP_100700.220.65.33P" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
[COLOR="Red"]<step operation="getvar" var="max-download-size" />[/COLOR]
<step var="fb_mode_set" operation="oem"/>
[COLOR="red"]<step operation="flash" partition="partition" filename="partition_signed" MD5="9a6775e7a676e0a4cd82f05f4b0c4e2e" />[/COLOR]
<step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="e07446f7ebc6985624a276bbbe39ed9e" />
<step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="43d4ca47a8f72ab974e3e587045c01b2" />
<step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="aa49e8361f5f14d5feabe2e7ef7554cb" />
<step operation="flash" partition="rpm" filename="rpm_signed" MD5="da48c189336c7d8a420747ebbaf2d172" />
[COLOR="red"] <step operation="flash" partition="tz" filename="tz_signed" MD5="bd4d8cd7a5889aa75e8de7a323588250" />[/COLOR]
<step operation="flash" partition="aboot" filename="aboot_signed" MD5="ab0273c6600e8b031bc87456a48d9c96" />
<step operation="flash" partition="modem" filename="modem_signed" MD5="b0069bec54160c6ed51b8685dbc71490" />
<step operation="flash" partition="fsg" filename="fsg_signed" MD5="6e24a8be2c3102c0bd5c8158b47f8faf" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
<step operation="flash" partition="devtree" filename="devtree_signed" MD5="e685220af2c119233b192f94182bfeb0" />
<step operation="flash" partition="boot" filename="boot_signed" MD5="95521869ded3115a15b6b3a3e353cd14" />
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="d63e9f5dee9401feb873c7e29c5fcb7c" />
<step operation="flash" partition="system" filename="system_signed" MD5="0807e33253ec0b4a89dfada07dda7bd6" />
<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="fa89d8b6eed33bad336351bdd6e76cce" />
<step operation="erase" partition="tombstones" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata"/>
<step var="fb_mode_clear" operation="oem"/>
</steps>
</flashing>
found it by reading the errors that appeared on rsd lite during failed flash tries
Hello Developers,
I'm working on SLIM MM, but stuck on boot screen (i.e. MI logo).
Tried to capture logcat but while booting it says "waiting for device..."
local_manifests :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!--Ferrari Device-->
<project name="Ferrari-Dev-Team/android_device_xiaomi_ferrari.git" path="device/xiaomi/ferrari" remote="github" revision="cm-13.0"/>
<project name="Ferrari-Dev-Team/android_kernel_xiaomi_ferrari" path="kernel/xiaomi/ferrari" remote="github" revision="cm-13.0-new"/>
<project name="Ferrari-Dev-Team/android_vendor_xiaomi_ferrari.git" path="vendor/xiaomi/ferrari" remote="github" revision="cm-13.0"/>
<!--snapdragon stuff-->
<project name="CyanogenMod/android_external_stlport" path="external/stlport" revision="cm-13.0" />
</manifest>
Any suggestion ??
Built, if someone can look in that.
A HUGE Thanks @faizauthar12 for helping me in this.
1.
2.
@fire855 @Shahan_mik3 @haikalizz @Rohan purohit
@ƒεηιx @faizauthar12
Any Inputs ?
Toruk.Makto said:
@fire855 @Shahan_mik3 @haikalizz @Rohan purohit
@ƒεηιx @faizauthar12
Any Inputs ?
Click to expand...
Click to collapse
sorry, i have no idea with it
if possible, i will download slim rom source :fingers-crossed:
and give it a try
faizauthar12 said:
sorry, i have no idea with it
if possible, i will download slim rom source :fingers-crossed:
and give it a try
Click to expand...
Click to collapse
Great.
Instead of SLIM, could you please give a try to Mokee MM ?? Just saying..... it's upto you.
Remove the old boringssl and clone the aospa boringssl.
Sent from my MI 4i using XDA-Developers mobile app
ƒεηιx said:
Remove the old boringssl and clone the aospa boringssl.
Sent from my MI 4i using XDA-Developers mobile app
Click to expand...
Click to collapse
Already tried that..... but still no luck
@Toruk.Makto
How did you avoid these errors?
pastebin.com/ZctZeiza
pastebin.com/2AtdXL9h
https://plus.google.com/+Anbuchelva/posts/7zp2TkXX1aQ
Toruk.Makto said:
Already tried that..... but still no luck
Click to expand...
Click to collapse
Then pull the last kmsg through recovery as adb will work on recovery..
Sent from my MI 4i using XDA-Developers mobile app
ƒεηιx said:
Then pull the last kmsg through recovery as adb will work on recovery..
Sent from my MI 4i using XDA-Developers mobile app
Click to expand...
Click to collapse
Code:
adb shell cat /proc/kmsg > ABC.txt
Will it work ?? I'll be fetching logs on Windows 7 ???
anbuchelva said:
@Toruk.Makto
How did you avoid these errors?
pastebin.com/ZctZeiza
pastebin.com/2AtdXL9h
https://plus.google.com/+Anbuchelva/posts/7zp2TkXX1aQ
Click to expand...
Click to collapse
I didn't get any such errors.
anbuchelva said:
@Toruk.Makto
How did you avoid these errors?
pastebin.com/ZctZeiza
pastebin.com/2AtdXL9h
https://plus.google.com/+Anbuchelva/posts/7zp2TkXX1aQ
Click to expand...
Click to collapse
You could try from CM repo
ƒεηιx said:
Then pull the last kmsg through recovery as adb will work on recovery..
Sent from my MI 4i using XDA-Developers mobile app
Click to expand...
Click to collapse
Nopes, it didn't help as well. Tried below commands on Windows Machine.
C:\adb>adb shell cat /proc/kmsg > kernelmsg3.txt // It generated few o/p but I didn't reboot device after flashing ROM/Gapps, Mayb be it's capturing just flashing logs which are not useful for us.
C:\adb>adb shell cat /proc/kmsg
error: device '(null)' not found
C:\adb>
Toruk.Makto said:
Nopes, it didn't help as well. Tried below commands on Windows Machine.
C:\adb>adb shell cat /proc/kmsg > kernelmsg3.txt // It generated few o/p but I didn't reboot device after flashing ROM/Gapps, Mayb be it's capturing just flashing logs which are not useful for us.
C:\adb>adb shell cat /proc/kmsg
error: device '(null)' not found
C:\adb>
Click to expand...
Click to collapse
Build rom again with engineer mode so adb will work on this mode.
Sent from my MI 4i using XDA-Developers mobile app
i would appreciate if someone guide me what's wrong in this. thanks!!
http://pastebin.com/b9G3VyzT
pls ignore..
anbuchelva said:
i would appreciate if someone guide me what's wrong in this. thanks!!
http://pastebin.com/b9G3VyzT
pls ignore..
Click to expand...
Click to collapse
Can i see your manifest?
Seems you're using kernel 3.10.49...
Also,did you clone boringssl from ferrari dev team?
faizauthar12 said:
Can i see your manifest?
Seems you're using kernel 3.10.49...
Also,did you clone boringssl from ferrari dev team?
Click to expand...
Click to collapse
i got it fixed.. will be uploading the build soon. :good:
and the local manifest:
HTML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- BoringSSL fix -->
<remove-project path="external/boringssl" name="platform/external/boringssl" groups="pdk" />
<project path="external/boringssl" name="Ferrari-Dev-Team/android_external_boringssl" remote="github" revision="cm-13.0"/>
<!-- Device repos -->
<project path="device/xiaomi/ferrari" name="Ferrari-Dev-Team/android_device_xiaomi_ferrari" remote="github" revision="cm-13.0"/>
<project path="kernel/xiaomi/ferrari" name="Ferrari-Dev-Team/android_kernel_xiaomi_ferrari" remote="github" revision="cm-13.0-new"/>
<project path="vendor/xiaomi/ferrari" name="Ferrari-Dev-Team/android_vendor_xiaomi_ferrari" remote="github" revision="cm-13.0"/>
<!-- Snapdragon Stuff -->
<!--project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-13.0" /-->
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-13.0" />
<!-- remove darwin -->
<remove-project path="prebuilts/clang/darwin-x86/host/3.6" name="platform/prebuilts/clang/darwin-x86/host/3.6" groups="pdk,darwin" />
<remove-project path="prebuilts/gcc/darwin-x86/aarch64/aarch64-linux-android-4.9" name="platform/prebuilts/gcc/darwin-x86/aarch64/aarch64-linux-android-4.9" groups="pdk,darwin,arm" />
<remove-project path="prebuilts/gcc/darwin-x86/arm/arm-eabi-4.8" name="platform/prebuilts/gcc/darwin-x86/arm/arm-eabi-4.8" groups="pdk,darwin,arm" />
<remove-project path="prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.9" name="platform/prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.9" groups="pdk,darwin,arm" />
<remove-project path="prebuilts/gcc/darwin-x86/host/headers" name="platform/prebuilts/gcc/darwin-x86/host/headers" groups="pdk,darwin" />
<remove-project path="prebuilts/gcc/darwin-x86/host/i686-apple-darwin-4.2.1" name="platform/prebuilts/gcc/darwin-x86/host/i686-apple-darwin-4.2.1" groups="pdk,darwin" />
<remove-project path="prebuilts/gcc/darwin-x86/mips/mips64el-linux-android-4.9" name="platform/prebuilts/gcc/darwin-x86/mips/mips64el-linux-android-4.9" groups="pdk,darwin,mips" />
<remove-project path="prebuilts/gcc/darwin-x86/x86/x86_64-linux-android-4.9" name="platform/prebuilts/gcc/darwin-x86/x86/x86_64-linux-android-4.9" groups="pdk,darwin,x86" />
<remove-project path="prebuilts/python/darwin-x86/2.7.5" name="platform/prebuilts/python/darwin-x86/2.7.5" groups="darwin,pdk,pdk-cw-fs" />
</manifest>
What happened to this ROM. Please continue