yashsingh1/xdaforums huggingface dataset:
[G3 Q&A, Help & Troubleshooting] tomb007:
LG G3 D855, 16Gb UK Model with quickcase

I have earlier put on TWRP, and Cyanogenmod 12.1, and super su, quickcase view etc.

supersu had to be installed via twrp, as the app from playstore would not update the binary

then downloaded xposed 3.1 apk and installed that

now it asked to install xposed so

then downloaded xposed-v74-sdk22-arm-by-romracer-20150911.zip and saved into downloads

booted into twrp recovery, installed it, and rebooted

now it no longer boots, gets stuck at the blue face logo.

I have tried to go back into recovermode,

advanced , terminal and created /data/data/de.robv.android.xposed.installer/conf/disabled

but it is still getting stuck on reboot.

no idea what to do now.

I could consider complete wipe/reflash, but would like to recover this.

any help appreciated.

thanks.

Update:

copied xposed-v75-sdk22-arm.zip to sdcard, and used twrp to install that.

Seems to have fixed the bootloop problem. Now need to get xposed correctly installed.

Not sure why I had downloaded the romracer version.
[Galaxy S 4 Active Q&A, Help & Troubleshooting] tetatate:
Hi

I need to unroot my S4 Active to have it repaired under warranty – it has stopped charging.

I don’t have a custom ROM – it has had the official upgrade to Android 5

I’m having trouble I’ve tried various methods that aren’t working.

I first tried to reset the counter using triangle away but it isn’t working.

I thought this was maybe as I have cwm recovery I tried to reset to standard recover but I can’t get it to boot into the recovery mode , the button method isn’t working .

I installed quick boot and tried that but it doesn’t work either

Now SU has stopped working I would try reinstalling but can’t find a way.

Titanium isn’t working saying that it isn’t rooted – maybe because SU isn’t working it just keeps crashing.

If the warranty repair engineer can’t get into the recovery mode it perhaps doesn’t matter about the counter

But in settings it is saying Device status custom so they will probably say the warranty is void.

Has anyone any ideas how I can get the status to say standard?

I can’t use any PC method as well as not charging I can’t connect to a PC by cable.

Thanks!
[ZenFone 2 Q&A, Help & Troubleshooting] kanagawaben:
Have enabled soft nav keys and would like to try temporarily disabling the hardware keys. Is this possible?
[Windows Mobile Development and Hacking General] MrPloppy:
Hi chaps,

I've just got myself an O2 XDA Orbit - great device, and now I'm looking for developing for it - just simple things at first, like a Blackjack game, or a simple Today feature with the sun and moon times on it; this sort of thing.

I've got Visual Studio .NET 2003, but I see that in order to program the latest devices, you need VS 2005 (?). So, I've downloaded Embedded Visual Studio C++ v4 with all the SDK's and I'm hoping to develop for an earlier version of Windows Mobile, and hope that it works.

So while I've got all that, I'm now stuck as to where to start! Can anyone point me to a good book, or something online which will help me through a simple CE application? How you do get the Today screen working, for example? I realise that this might be asking a lot, but a couple of pointers would be great - if you could! :)

Many thanks,

MrP.
[Windows Mobile Development and Hacking General] hannip:
I'm just starting out myself with windows mobile programming. You can find a lot of info from msdn. Here is an example Hello app.

http://msdn2.microsoft.com/en-us/library/ms912017.aspx

You can find a lot of good stuff at the code project site also.

http://www.codeproject.com/ce/

eVC has wizards that will get you going. One thing I found out about using eVC is that you won't be able to debug your programs on a WM5/6 device since the SDK's are not compatible with them. It can be a bit of a challenge to fix bugs without a debugger. I can't get the debugger to work with the emulator either for some reason.

A question for other eVC developers out there. Is it possible to use the emulator to debug programs or do you all have an old PPC2003 device that you use to do your debugging? Or have you all moved on to VS2005?
[Windows Mobile Development and Hacking General] Jimm98y:
I've bought visual studio 2005 standard and it is great - it fully supports WM5/6 (with sdk) and runtime debugging - for .exe it works well but I have problems with .dll - I can't debug dll files - does anyone know how to make it?
[Windows Mobile Development and Hacking General] levenum:
Pleas look up threads started by vijay555.

He wrote a comprehensive article on the tools and possibilities to begin developing for these devices.

Just as a quick side note:

There is no need what so ever to pay M$ money for VS 2005 if you want to develop in C / C++.

Apps written in eVC++ 4 will work perfectly with WM 5 and 6 and if you need any missing API (not many of those) you have 2 choices:

1) Manually unpack the SDK and link to it.

2) Use implicit linking (that LoadLibrary and GetProcAdress).
[Windows Mobile Development and Hacking General] MrPloppy:
Sorry about the delay in replying...

Many thanks for the pointers.. Just a matter of starting now!
[Meizu MX] krikor1:
Device model Meizu MX5

OS version (android version 5.0.1)

I have that device, and i get error device is not supporting when i download app from store and try to launch the application.

https://play.google.com/store/apps/details?id=com.netvariant.banknizwa

Possible to know some reasons? and why?
[Meizu MX] krikor1:
The manifest

<uses-permission android:name="com.google.android.providers.gsf.permission.READ_GSERVICES" />

<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />

<uses-permission android:name="android.permission.ACCESS_MOCK_LOCATION" />

<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

<uses-permission android:name="android.permission.INTERNET" />

<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE" />

<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />

<uses-permission android:name="android.permission.WRITE_USER_DICTIONARY" />

<uses-permission android:name="android.permission.CALL_PHONE" />

<uses-permission android:name="android.permission.READ_USER_DICTIONARY" />

<uses-permission android:name="android.permission.READ_CONTACTS" />

<uses-permission android:name="android.permission.READ_PHONE_STATE" />

<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />

<uses-feature

android:name="android.hardware.location.gps"

android:required="false" />

<uses-feature

android:name="android.hardware.location.network"

android:required="false" />

<uses-feature

android:name="android.hardware.wifi"

android:required="false" />

<uses-feature

android:name="android.hardware.location"

android:required="false" />

<uses-feature

android:name="android.hardware.screen.portrait"

android:required="false" />

<uses-feature

android:name="android.hardware.telephony"

android:required="false" />

<uses-sdk

android:minSdkVersion="8"

android:targetSdkVersion="22" />

<uses-feature

android:glEsVersion="0x00020000"

android:required="true" />
[Meizu MX] RastHacker:
An xposed module disable device check on playstore just apply this module ;D
[Meizu MX] krikor1:
How would you do that?
[Ascend Mate 7 Original Android Development] hadid90:
can we just make a petition for huawei so maybe they will release the source code needed for developers ?
[Ascend Mate 7 Original Android Development] gabry3795:
I was thinking the same thing, it's the only hope we have. I really don't understand why they don't release these sources as Qualcomm did for snapdragon. If marketing reasons stand behind this I think that getting the sources will be very hard, but we can always try it.

I updated the post with the petition link.
[Ascend Mate 7 Original Android Development] PoisonNinja:
I think you should post it in the General forum, since that gets a lot more traffic there. I signed your petition! Hope it works!
[Ascend Mate 7 Original Android Development] jjrodri07:
Signed
[Ascend Mate 7 Original Android Development] Rascal74:
+1
[Ascend Mate 7 Original Android Development] ELV1ZARR0:
just released mtl09 kernel you use? plugin.php?id=hwdownload&mod=detail&mid=74
[Ascend Mate 7 Original Android Development] Cpasjuste:
Hi !

I just buy a mate 7 (TL09). I did some hard work in the past on some non-opensource devices (amazon hdx thor, tegra 4i ..), I'll try to join the (not) fun soon :)

Envoyé de mon Kindle Fire HDX 7 en utilisant Tapatalk
[Ascend Mate 7 Original Android Development] apopet26:
Repost in general section...

Send from Mate 7 using tapatalk
[Ascend Mate 7 Original Android Development] gabry3795:
Thank you for joining us :thumbup: you can find the sources in the first post ;)
[Ascend Mate 7 Original Android Development] gabry3795:
Sorry but that sources are incomplete and only for kitkat :(
[Ascend Mate 7 Original Android Development] gabry3795:
I'll do ASAP, do you know if can just move this post to the other section or I have copy it?
[Ascend Mate 7 Original Android Development] ELV1ZARR0:
ROM

there is a rom flyme you working on lollipop but is for use as a base Might TL10 sorry for mi bad English
[Ascend Mate 7 Original Android Development] Cpasjuste:
So gabry3795, for now we only have kk kernel sources for the m7 ? By the way I should receive mine in 2-3 days :)

Envoyé de mon Kindle Fire HDX 7 en utilisant Tapatalk
[Ascend Mate 7 Original Android Development] gabry3795:
Yes we have kk kernel sources but they're incomplete so you can't compile the kernel. There are missing .h files and also drivers/modem was a broken symlink to ../../vendor/hisi/modem/drv/acore/kernel/drivers/modem. So I took the folder vendor from h60 kernel https://github.com/codeworkx/kernel-huawei-h60 and I put it in drivers/. Now drivers/modem is symlinked to /drivers/vendor/hisi/modem/drv/acore/kernel/drivers/modem but the the kernel is still uncompilable. I think they just zipped their folder /kernel in their build evironment without coping everything you need to compile the kernel, I don't know if it's fair but they did it.

Okay let me/us know when you will get your hands on the mate! ;)
[Ascend Mate 7 Original Android Development] gabry3795:
Don't worry! Where did you find it? Did you try to install it on your device?
[Ascend Mate 7 Original Android Development] ELV1ZARR0:
in fact one time I brought my TL10 runs everything except the fingerprint, there is a link to the Chinese forum http://bbs.zhiyoo.com/forum.php?mod=viewthread&tid=9994445&mobile=yes
[Ascend Mate 7 Original Android Development] Cpasjuste:
As i don't have the device yet i didn't understand all yet but it seems we can have some brick when playing with the device or is it just some "noob" users reporting this ? Is the only problem the bootloader when trying to go from on version to another version ? Im asking because i think it would be better for me to start playing with cm13, but i dont want to be stuck on that version (MM) or worst brick the device, which is dont see yet how it would be possible by the way.

Envoyé de mon LG-D855 en utilisant Tapatalk
[Ascend Mate 7 Original Android Development] ELV1ZARR0:
there is a rom flyme with lollipop you can use as a base for CM12
[Ascend Mate 7 Original Android Development] gabry3795:
I really did heavy testing on this device, trying to install cm recovery and /system built on my own and I have always found a way to restore stock roms. A few months ago I also formatted /boot (which contains the kernel as you know, my mistake :silly:) /recovery and /system partitions at the same time and the device was stuck on huawei logo: so I could boot from the bootloader which allows you to reflash anything you want, this is the only pro of huawei devices I think.

P.S.: Are you replacing your LG G3 with the mate 7? I think it's a mistake! ;)
[Ascend Mate 7 Original Android Development] gabry3795:
I think that is a stock rom with flyme inspired theme :(
[Ascend Mate 7 Original Android Development] Cpasjuste:
Yeah like with every devices out there in fact :)

I guess people who think they "hard brick" is because they try to restore a boot/kernel that's not compatible with the bootloader (for example a 5.x ROM with a 6.x bootloader). I'll think I'll stay on 5.x at start and take a deep look at cm12 even if people (you and [MENTION=3208754]codeworkx[/MENTION]) think its impossible (which is maybe the case). It would not be the first time I hear this while I did succeed (well it took me maybe 6 month for the amazon hdx 7 :/)

Envoyé de mon Kindle Fire HDX 7 en utilisant Tapatalk
[Ascend Mate 7 Original Android Development] ELV1ZARR0:
not think it's an theme as it is a competition among several cooks , I brought one month and is a rom flyme 100 Original
[Ascend Mate 7 Original Android Development] Cpasjuste:
Hi,

I think we would need source code for this to be usefull.

Else [MENTION=6778430]gabry3795[/MENTION] yes i am replacing my g3 with this, but you stress me now :) That's said i do have minors problems with my touchscreen on my d855. I did broke the lcd a few month back, changed the sceeen twice and still have two screen touch rows not working properly. Also i like to change sometime .. Hope ill still enjoy the new one :/

Edit: so i just received the mate 7. I did unlock BL, update from kk to lollipop (b329), installed twrp then did a backup. I'll try to take a look at cm12 in the next weeks.

Envoyé de mon LG-D855 en utilisant Tapatalk
[Ascend Mate 7 Original Android Development] Cpasjuste:
This thread must be sticky.
[Ascend Mate 7 Original Android Development] gabry3795:
04/12 update

UPDATE

With the last sources released I managed to build the kernel together with the CM13, but the phone does not boot: I'm stuck as when I built the CM12 but the difference is that now the kernel compiles perfectly with the main rom source.

I have updated the gits and the main post, everyone that can contribute to this project is ever welcome.
[Ascend Mate 7 Original Android Development] blackhawk_LA:
If you need beta testers, just let us know!

Sent from my Mate
[Ascend Mate 7 Original Android Development] gabry3795:
UPDATE

UPDATE

I just managed to build the kernel and repack it to the stock Android 6.0 B551. For now it's not useful but it's a big step towards a full build.

Screenshot http://imgur.com/4MGuzUN.png
[Ascend Mate 7 Original Android Development] Skorpi58:
these are very good news .... wish you good luck .... and it would also like to test
[Ascend Mate 7 Original Android Development] Jayz2K:
Good luck ! Congrats for the great job. I'm following Mate7 threads since ages and running CM11 ATM but really wish to see upgrades pointing there. Thanks for your time trying to push things further.
[Ascend Mate 7 Original Android Development] Cpasjuste:
In fact this a a really nice progress :)

Yesterday I synched your sources but I got some error when building cm13. There is definitely some problems on your github, I think it was related to the kernel build. I'll try to take a look but it would save some time if you fix your repos ( I mean sync cm13, pull your repos then go).

Envoyé de mon JAZZ en utilisant Tapatalk
[Ascend Mate 7 Original Android Development] gabry3795:
Yes, I have already fixed that. Please sync your fork with my repo and you will able to build ;)

There was a bad .gitignore that excluded some files when committing [emoji28]

Also look into the folder _useful, you will find lots of infos that I gathered from imgs.
[Ascend Mate 7 Original Android Development] Cpasjuste:
Hehe so nice. I'll try that in a few minutes/hours.

Envoyé de mon JAZZ en utilisant Tapatalk

---------- Post added at 07:08 PM ---------- Previous post was at 07:06 PM ----------

By the way, what was the problem with the kernel not booting ? (I was stuck at the same place a few weeks ago)

Envoyé de mon JAZZ en utilisant Tapatalk
[Ascend Mate 7 Original Android Development] gabry3795:
Okay [emoji6]

I have never faced this issue, does your kernel not boot? How have you re-packed the boot.img?

There was a problem with an #include but my kernel didn't bootloop even commenting that include! Now thanks to [MENTION=5127555]acbka[/MENTION] we have also the .h that was missing, I have already updated the kernel repo.
[Ascend Mate 7 Original Android Development] Cpasjuste:
Well, i always ends up with this error :

/home/cpasjuste/android/system/kernel/huawei/mt7_l09/scripts/Makefile.build:104: scripts/Makefile.lib: No such file or directory
make[3]: *** No rule to make target 'scripts/Makefile.lib'. Stop.
GEN /home/cpasjuste/android/system/out/target/product/mt7_l09/obj/KERNEL_OBJ/Makefile
/home/cpasjuste/android/system/kernel/huawei/mt7_l09/Makefile:499: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
make[2]: *** Waiting for unfinished jobs....
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/cpasjuste/android/system/kernel/huawei/mt7_l09'

There's definitively a problem with your repos.
[Ascend Mate 7 Original Android Development] gabry3795:
Fixed now. Other files skipped by .gitignore resync your fork [emoji6]
[Ascend Mate 7 Original Android Development] gabry3795:
04/17 update

UPDATE

Cyanogenmod recovery is working.

http://imgur.com/TYRQafc
[Ascend Mate 7 Original Android Development] pjdpinheiro:
Really excellent news.

Enviado do meu HUAWEI MT7-L09 através de Tapatalk
[Ascend Mate 7 Original Android Development] Cpasjuste:
I think there's still a problem with your repo (sepolicy).

...
/home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts: line 287 has invalid context u:object_r:authpass_prop:s0
libsepol.context_from_record: type goldeneye_prop is not defined
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert u:object_r:goldeneye_prop:s0 to sid
/home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts: line 288 has invalid context u:object_r:goldeneye_prop:s0
libsepol.context_from_record: type cameradump_prop is not defined
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert u:object_r:cameradump_prop:s0 to sid
/home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts: line 291 has invalid context u:object_r:cameradump_prop:s0
libsepol.context_from_record: type cameradump_prop is not defined
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert u:object_r:cameradump_prop:s0 to sid
/home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts: line 292 has invalid context u:object_r:cameradump_prop:s0
libsepol.context_from_record: type cameradump_prop is not defined
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert u:object_r:cameradump_prop:s0 to sid
/home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts: line 293 has invalid context u:object_r:cameradump_prop:s0
libsepol.context_from_record: type cameradump_prop is not defined
libsepol.context_from_record: could not create context structure
libsepol.context_from_string: could not create context structure
libsepol.sepol_context_to_sid: could not convert u:object_r:cameradump_prop:s0 to sid
/home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts: line 295 has invalid context u:object_r:cameradump_prop:s0
Invalid context file found in /home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts
external/sepolicy/Android.mk:237: recipe for target '/home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts' failed
make: *** [/home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts] Error 5
make: *** Deleting file '/home/cpasjuste/android/system/out/target/product/mt7_l09/obj/ETC/property_contexts_intermediates/property_contexts'
[Ascend Mate 7 Original Android Development] gabry3795:
Yes, I'm working at these files now just comment BOARD_SEPOLICY_DIRS on BoardConfig.mk and you're ready to compile.

I'm sorry for these issues but I'm working a lot on the code so even the repo it's not stable :/
[Ascend Mate 7 Original Android Development] Cpasjuste:
No no, there's no problem don't worry. I just don't want to reinvent the wheel :D
[Ascend Mate 7 Original Android Development] Skorpi58:
you'll do it already...i believe you:good:
[Ascend Mate 7 Original Android Development] Cpasjuste:
That's strange, i'm unable to boot the compiled kernel/recovery, it hangs on the logo without any usb inited. Maybe the problem is i'm using a B513 rom and the DTB is not compatible ? (i think you guys are using B551)
[Ascend Mate 7 Original Android Development] gabry3795:
I don't think it depends on boot, I have the B511 boot.img and cyano recovery works very well, it's weird..
[Ascend Mate 7 Original Android Development] Cpasjuste:
Well, then there's still a problem with your repo :)
[Ascend Mate 7 Original Android Development] Skorpi58:
Dear [MENTION=6778430]gabry3795[/MENTION]....What's your opinion? Can we expect a functioning ROM towards the end of this month?

i see and follow, that you are corperating with [MENTION=503571]Cpasjuste[/MENTION]...and are you also in contact with [MENTION=3208754]codeworkx[/MENTION] and [MENTION=5127555]acbka[/MENTION]
[Ascend Mate 7 Original Android Development] gabry3795:
Well, it's difficult to talk about "time" in these cases and I don't want to promise anything because there's nothing certain, I cannot guarantee that we will see a cm for the mate yet. The only things that I can say are:

- I succesfully built the cyanogenmod recovery and it's working

- I succesfully built the the system but it's not booting and I'm investigating why this happens

- I am working a lot on this project even if I am studying in the meanwhile

- I will post any update and any achievement in this thread

I really hope that we manage to build a complete and working cm for this device.

As you can see here we're trying to cooperate and anyone who has a minimum of time and acknowledge is welcomed here.
[Ascend Mate 7 Original Android Development] Skorpi58:
Thank you very much...i'm not technical, but you have my full respect...and if i can help you to test anything, pls let me know...
[Ascend Mate 7 Original Android Development] Cpasjuste:
Finaly it's booting fine when using commit #e2a9df9 (got twrp 3.0 working). I'll try to take a look at boot/system.
[Ascend Mate 7 Original Android Development] acbka:
touchscreen work good ?
[Ascend Mate 7 Original Android Development] gabry3795:
Yes! It works fine in cyano recovery
[Ascend Mate 7 Original Android Development] Cpasjuste:
Works fine on twrp too.

Envoyé de mon JAZZ en utilisant Tapatalk
[Ascend Mate 7 Original Android Development] acbka:
Strangely enough, I do not work in touchscreen twrp 3+

show u dev tree on github
[Ascend Mate 7 Original Android Development] Cpasjuste:
I'm using gabry repos, i didn't push to my own repo yet but here are my twrp patches :

- device/huawei/mt7_l09 : http://pastebin.com/Dfd7hRE2 + twrp.fstab : http://pastebin.com/CRyhSEYG

- bootable/recovery : http://pastebin.com/ZZtzM6pi

Unfortunately there's still a problem (i think) with "data/share/0" (internal sdcard) which is included in data backup..
[Ascend Mate 7 Original Android Development] acbka:
I know fix data/media/0 to data/share/0
[Ascend Mate 7 Original Android Development] Cpasjuste:
And what's the fix ? :)