Search results

if you use "Greenify" and updated it.. maybe you get bootloop because of this.. when this is the case.. just uninstall greenify via adb in twrp.. if not.. i can't help

as described.. rom doesn't matter.. it's a bootloader-based problem on another partition.. just follow instructions

read the postings after this.. and use baord-search.. if you got question after this.. ask again

you have to use google to understand what fastbootmode, recoverymode and those commands are.. this thread is not for explaining basics, that are explained all over the internet...

maybe i should make a donate button, hrhr =)

as far as i know, it is compatible.. but i'm not 100% sure.. i did not test.. and i'm not involved into it... i would think that it is compatible, because it was made for 12.1 and was then made compatible for 13.. so why don't you just test it?

update... here is the working CameraBQ App für CM13 as attachment.. (just added file libarcsoft_panorama_burstcapture.so, as mentioned in here: http://www.android-hilfe.de/thema/rom-offiziell-cyanogenmod-13-fuer-das-bq-aquaris-x5-paella-nightlies.794870/#post-10052562) updated version of the...

Found a Solution.. just Download Camera App from here: https://s.basketbuild.com/devs/eloimuns/bq/piccolo/ (file: CameraBQ_signed_v4.1.0.zip) Unpack zip file.. go into folder: META-INF/com/google/android/ open file with texteditor: updater-script Replace every "piccolo" by "paella" "M5" by...

crash report on CM13: and logcat output: maybe this helps to get it working on CM13? seems to be a write-permission problem on dalvik?

does this fix your loop more then one time?

hehe.. you are all welcome.... should i make a donate button? *g*

and the world doesn't care about that you don't care... but remember: we are on a forum/board with many alternative firmwares and apps that mostly are developed/modified because of privacy concerns.. so, this is an essential topic on this forum/board... despite from your personal view

no change.. still tries to connect to *.1e100.net hosts (and for sure to some adblock.org hosts to update lists) after allowing to connect to adblock hosts.. gello also still wants to connect to 151.101.12.133

as i wrote a few pages before.. i use "firewall without root" to monitor which app is connecting to which host... i start gello-mod and for sure there is a google searchpage as startpage (why not blank page as default?).. then i go through every setting to get my privacy whishes reflected.. also...

startpage is set to blank a browser that is starting and that has not given any address nor any information is connecting to several hosts.. without information why it is connecting.. this let.me think about privacy problems

current release still tries to connect to google(*.1e100.net) and github host (151.101.12.133) on start.. why? what does gello try to send/receive there?

why is gello connecting to google when there is no page loaded.. no startpage configured.. no auto-completion or anything else activated? i deactivate all of this.. then kill gello.. start it.. and blank screen starts (as expected).. and my firewall tells me, gello wants to connect to...

you need to know what adb is.. and how to work with it... just google or use this forum... there are many many informations about it..

just boot twrp.. then send command via adb.. dd writes zeros into the partition "/misc".. as i wrote, this means to wipe this partition... but this info is in this thread.. written by me and cheppiroma.. that's the reason why i don't understand your question..

there is a detailed description.. please ask more in detail..

*bump*

on #cyanogenmod channel on freenode user spudowiar helped me.. the problem: partition /misc is fault.. and twrp (for example) does not mount this partition to wipe it correctly.. you can wipe it manualy by dd it.. but do a backup before! (just in case)

same here.. booting always into recovery by default.. tried different twrp versions (incl. 2.8.7), CWM and cyanogen recovery.. and also tried wiping the complete system.. reinstalling stock rom incl. bootloader, recovery, etc.. everytime the same boot into recovery by default using "fastboot...

[A] GAPPS crashing allways i was testing last night latest CM13 Nightly and got Problems with GAPPS crashing all the time.. the Problems are related to Permissions.. on the web i found this solution.. maybe this helps others: this grants the permissions needed for the "gapps setup wizard"...

Thx for your help.. but my question was, if anyone know, if these usb sticks fitt my needs.. i was reading the thread.. and i also read about those hdmi->spdif boxes..

hey.. anyone know, if this will work on nvidia shield (mainly on kodi)? http://www.terratec.net/details.php?artnr=10542 or this cheaper device: http://www.delock.com/produkte/G_61961/merkmale.html?setLanguage=en i also need optical audio.. and passthrough to get surround on my receiver.. (no...

could anyone confirm, that this is possible? how to inject this into a custom made kernel? possible as a mod? or only within the kernel, when it is compiled? (im new to this)

Hi, for a Project i want to start, i need USB OTG Host mode and Charging at the same time. I tried some self made cables like in this thread: http://forum.xda-developers.com/showthread.php?t=1822653 this website: https://sites.google.com/site/sonicboomworld/my-projects/otg-diagrams or this one...

it´s the first time im using this tool... im happy that i found your solution/fix for lolipop.. it works perfect on any website/host in the web.. but i got still a problem.. the routing seems to route everything through the tunnel.. except things that are adressing other services on the same...

maybe anyone is able to verify this: i downloaded another stock rom (asia xt1033 dualsim).. to extract those keymaster files of it.. and surprise.. those files have same md5 hash, as my files.. that means, those stock files are exactly the same as my files.. so its not a problem for me to...

mms not working in here.. is there a fix i did not find?

[HOWTO] Solution to fix SystemUI crash loop

Solution to fix SystemUI crash loop Hi, i was able to fix the SystemUI crashing loop on my moto g xt1032 via LogCat i found these two errors: E/QSEECOMAPI: ( 6008): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt E/QSEECOMAPI: ( 6008): Error::Cannot open the file...

added important info in first post!

Hi, problem: i can´t see any wifi networks, that im not connected to i´m able to add manuelly any wifi network without problems.. wifi on those manually added networks, works perfect notification of open networks is enabled.. and i got a notification that there is an open wifi network in...

nm

well.. i took a look at this jira thing... at regular cm builds im not allowed to post nightly issues.. on the nightly builds im not allowed to post things that i cannot verify working on a previous nightly.. so.. also i have to check the issues against wiped system.. that´s what i definitly...

hi i found the problem with system UI Crash at boot.. logcat repeated very often: E/keystore( 6007): keystore keymaster could not be initialized; exiting D/QSEECOMAPI: ( 6008): QSEECom_get_handle sb_length = 0x2000 D/QSEECOMAPI: ( 6008): App is not loaded in QSEE E/QSEECOMAPI: ( 6008)...

im currently using 20140603 without problems.. i just tried a few of the latest cm12 nightly builds.. and always got the sysmtemUI Crash.. so i read about installing one of the latest cm11 builds before installing cm12 build should fix this.. but i had no luck.. also booting into safe-mode...

thx for your upload but.. as you described.. same problem here with looping systemUI crash =(

im also interested in latest nightly build and 20141223 thx a lot

nevermind.. sorry =) (i tried to delete this post.. not able to?)