NFC question... - Honor 7 Q&A, Help & Troubleshooting

NFC question... - Honor 7 Q&A, Help & Troubleshooting

Hi guys,
i have a little question.
I know Honor 7 16 gb ( always EU and Cina versions ) it doesn't have NFC sensor ....
Someone who owns the phone 64 gb, can try to test if the sensor works to read the NFC tag ...
Tnx
N.

nwzah said:
Hi guys,
i have a little question.
I know Honor 7 16 gb ( always EU and Cina versions ) it doesn't have NFC sensor ....
Someone who owns the phone 64 gb, can try to test if the sensor works to read the NFC tag ...
Tnx
N.
Click to expand...
Click to collapse
It can't read NFC Tag. There are 3 functionality of NFC:
1. Card emulation mode, allowing the NFC device itself to act as an NFC card. The emulated NFC card can then be accessed by an external NFC reader, such as an NFC POS terminal.
2. Read/Write mode, allowing the NFC device to read and/or write passive NFC tags and stickers.
3. P2P mode, allowing the NFC device to exchange data with other NFC peers; this operation mode is used by Android Beam.
And Honor 7 (PLK-AL10) functions only as a NFC emulator.

Hardware of H7 is work with full function,but Huawei locked p2p & r/w func by system.
you can download Taginfo in play store and it will be work. The native android support is destoried by huawei in stock rom

Hi, I try to use the app taginfo but p2p & r/w don't work... Can you indicated any other app.
Thanks

holti said:
Hi, I try to use the app taginfo but p2p & r/w don't work... Can you indicated any other app.
Thanks
Click to expand...
Click to collapse
Patch to enable p2p & r/w at rooted phone
Code:
--- /system/etc/libnfc-brcm_PLK.conf.save
+++ /system/etc/libnfc-brcm_PLK.conf
@@ -308,7 +308,7 @@
# NFA_TECHNOLOGY_MASK_A_ACTIVE 0x40 /* NFC Technology A active mode */
# NFA_TECHNOLOGY_MASK_F_ACTIVE 0x80 /* NFC Technology F active mode */
# TURNS_OFF_POLLING_ON_PLK.
-POLLING_TECH_MASK=0x00
+POLLING_TECH_MASK=0xCF
###############################################################################
# Force P2P to only listen for the following technology(s).
@@ -322,7 +322,8 @@
# NFA_TECHNOLOGY_MASK_A_ACTIVE 0x40 /* NFC Technology A active mode */
# NFA_TECHNOLOGY_MASK_F_ACTIVE 0x80 /* NFC Technology F active mode */
# DISABLES_RW_&_P2P.
-P2P_LISTEN_TECH_MASK=0x00
+# P2P_LISTEN_TECH_MASK=0x00
+P2P_LISTEN_TECH_MASK=0xC3
PRESERVE_STORAGE=0x01

XBOCT said:
Patch to enable p2p & r/w at rooted phone
Code:
--- /system/etc/libnfc-brcm_PLK.conf.save
+++ /system/etc/libnfc-brcm_PLK.conf
@@ -308,7 +308,7 @@
# NFA_TECHNOLOGY_MASK_A_ACTIVE 0x40 /* NFC Technology A active mode */
# NFA_TECHNOLOGY_MASK_F_ACTIVE 0x80 /* NFC Technology F active mode */
# TURNS_OFF_POLLING_ON_PLK.
-POLLING_TECH_MASK=0x00
+POLLING_TECH_MASK=0xCF
###############################################################################
# Force P2P to only listen for the following technology(s).
@@ -322,7 +322,8 @@
# NFA_TECHNOLOGY_MASK_A_ACTIVE 0x40 /* NFC Technology A active mode */
# NFA_TECHNOLOGY_MASK_F_ACTIVE 0x80 /* NFC Technology F active mode */
# DISABLES_RW_&_P2P.
-P2P_LISTEN_TECH_MASK=0x00
+# P2P_LISTEN_TECH_MASK=0x00
+P2P_LISTEN_TECH_MASK=0xC3
PRESERVE_STORAGE=0x01
Click to expand...
Click to collapse
Hi XBOCT,
thank you so much for your reply. But can you explain how can execute these lines of code. Need root access?
Thanks in advance!

Does this whole thread mean, that the Honor 7 has a NFC chip inside, but it's just not enabled or rather limited by the OS?!

NFC
The 64 GB has one, not the 16 GB one
wormix500 said:
Does this whole thread mean, that the Honor 7 has a NFC chip inside, but it's just not enabled or rather limited by the OS?!
Click to expand...
Click to collapse

holti said:
Hi XBOCT,
thank you so much for your reply. But can you explain how can execute these lines of code. Need root access?
Thanks in advance!
Click to expand...
Click to collapse
FULL NFC FOR PLK-AL10 (rooted)
1. Go to /system/etc/
2. Copy and save file: libnfc-brcm_PLK.conf
3. In file libnfc-brcm_PLK.conf change:
POLLING_TECH_MASK=0x00 to POLLING_TECH_MASK=0xCF
and
P2P_LISTEN_TECH_MASK=0x00 to P2P_LISTEN_TECH_MASK=0xC3
4. Save file and restart phone.
NOW PHONE CAN READ NFC TAGS.
Tested on PLK-AL10 with 5.11.16 emui custom rom from:
http://club.huawei.com/forum.php?mo...=page=1&filter=typeid&typeid=2520&typeid=2520
Thanks to XBOCT
TO ENTER HUAWEI BEAM:
1. Edit /system/build.prop
2. Change:
ro.config.support_huawei_beam=false to true
3. Save and reboot phone
4. Look at SETTINGS-MORE-NFC
Thanks to tomssy:
http://club.huawei.com/forum.php?mod=redirect&goto=findpost&ptid=5449202&pid=118662160

waliej said:
FULL NFC FOR PLK-AL10 (rooted)
1. Go to /system/etc/
2. Copy and save file: libnfc-brcm_PLK.conf
3. In file libnfc-brcm_PLK.conf change:
POLLING_TECH_MASK=0x00 to POLLING_TECH_MASK=0xCF
and
P2P_LISTEN_TECH_MASK=0x00 to P2P_LISTEN_TECH_MASK=0xC3
4. Save file and restart phone.
NOW PHONE CAN READ NFC TAGS.
Tested on PLK-AL10 with 5.11.16 emui custom rom from:
http://club.huawei.com/forum.php?mo...=page=1&filter=typeid&typeid=2520&typeid=2520
Thanks to XBOCT
TO ENTER HUAWEI BEAM:
1. Edit /system/build.prop
2. Change:
ro.config.support_huawei_beam=false to true
3. Save and reboot phone
4. Look at SETTINGS-MORE-NFC
Thanks to tomssy:
http://club.huawei.com/forum.php?mod=redirect&goto=findpost&ptid=5449202&pid=118662160
Click to expand...
Click to collapse
will you explan more about this i m confused how to enter this in file many txt are there
this also have to copy?
--- /system/etc/libnfc-brcm_PLK.conf.save
+++ /system/etc/libnfc-brcm_PLK.conf
@@ -308,7 +308,7 @@
1. Go to /system/etc/
2. Copy and save file: libnfc-brcm_PLK.conf
3. In file libnfc-brcm_PLK.conf change:
POLLING_TECH_MASK=0x00 to POLLING_TECH_MASK=0xCF
and
P2P_LISTEN_TECH_MASK=0x00 to P2P_LISTEN_TECH_MASK=0xC3
4. Save file and restart phone.
NOW PHONE CAN READ NFC TAGS.

warriorsach said:
will you explan more about this i m confused how to enter this in file many txt are there
this also have to copy?
Click to expand...
Click to collapse
Install Root Browser.
Go to /system/etc/
Click on libnfc-brcm_PLK.conf and edit in RB Text Editor.
Change digital values and save (they are at the end of file)
With Huawei beam do the same.
Restart phone.
You do not have to copy these files.

does the above method work with PLK-L01 too? (EU version)

thermalboyz said:
does the above method work with PLK-L01 too? (EU version)
Click to expand...
Click to collapse
No - only PLK-AL10 have NFC.

On 6.3.16 huawei beam does no more work, but nfc read works well

Hi! To read nfc tag is strictly necessary to do the root?
i've tried to substitite libnfc config file with the modify one by means of twrp, but it seems that this solution dont work
Inviato dal mio PLK-AL10 utilizzando Tapatalk

doongoo said:
On 6.3.16 huawei beam does no more work, but nfc read works well
Click to expand...
Click to collapse
With 6.3.16
install file Patch_6.3.16_NFC_Volte.zip with TWRP from:
https://userscloud.com/go/itil21gg5p59/
end restart phone
Thank to http://4pda.ru
http://4pda.ru/forum/index.php?showtopic=678766

waliej said:
With 6.3.16
install file Patch_6.3.16_NFC_Volte.zip with TWRP from:
https://userscloud.com/go/itil21gg5p59/
end restart phone
Thank to http://4pda.ru
http://4pda.ru/forum/index.php?showtopic=678766
Click to expand...
Click to collapse
Thank you but I really do not need it (have no another Huawei device, where it could be useful - I mean Huawei beam). In a meantime I already updated to 6.4.1 and made the same modification for NFC-tag reading. I can confirm it works also on this version.

Does the enhanced version (32Gb version a.k.a. Honor 7 Premium) have NFC functionality? I've read various reviews and they claim there's NFC. But when I opened the phone I cannot see any NFC over there. So what gives?

Does Honor 7 have NFC and does it support wireless charging?

Related

[HOWTO] (+2.3.4) build cifs.ko (for stock kernel)

Complied cifs.ko and slow-work.ko
2.3.4 I9100-XXKG2-CIFS.zip
2.3.3 cifs-for-GT-I9100.zip
1. get the SHW-M250L kernel source from OSRC.
https://opensource.samsung.com/
2. copy files to fs/cifs folder.
kernel/slow-work.c
kernel/slow-work.h
3. add below codes to top of fs/cifs/slow-work.c (in kernel/timer.c)
Code:
static unsigned long round_jiffies_common(unsigned long j, int cpu,
bool force_up)
{
int rem;
unsigned long original = j;
/*
* We don't want all cpus firing their timers at once hitting the
* same lock or cachelines, so we skew each extra cpu with an extra
* 3 jiffies. This 3 jiffies came originally from the mm/ code which
* already did this.
* The skew is done by adding 3*cpunr, then round, then subtract this
* extra offset again.
*/
j += cpu * 3;
rem = j % HZ;
/*
* If the target jiffie is just after a whole second (which can happen
* due to delays of the timer irq, long irq off times etc etc) then
* we should round down to the whole second, not up. Use 1/4th second
* as cutoff for this rounding as an extreme upper bound for this.
* But never round down if @force_up is set.
*/
if (rem < HZ/4 && !force_up) /* round down */
j = j - rem;
else /* round up */
j = j - rem + HZ;
/* now that we have rounded, subtract the extra skew again */
j -= cpu * 3;
if (j <= jiffies) /* rounding ate our timeout entirely; */
return original;
return j;
}
unsigned long round_jiffies(unsigned long j)
{
return round_jiffies_common(j, raw_smp_processor_id(), false);
}
4. edit fs/cifs/Makefile
obj-$(CONFIG_CIFS) += cifs.o slow-work.o
5. make menuconfig
File systems > [*] Network File Systems > <M> CIFS Support
6. make modules
7. put files to your phone.
fs/cifs/slow-work.ko
fs/cifs/cifs.ko
8. insert modules.
insmod slow-work.ko
insmod cifs.ko
Done! Enjoy!

I'm on stock KE7+CF Root and I have some problems.
I've downloaded cifs-for-GT-I9100.zip, uncompressed it and put the two files in /fs/cifs
ROOT---cf---cifs---cifs.ko
..................... |__slow-work.ko
I've started ADB SHELL and I typed
Code:
$su
#cd fs
#cd cifs
#insmod slow-work.ko [B](no reply, so I think it goes well)[/B]
#insmod cifs.ko [B](I get two messages of error "[I]insmod: can't insert 'cifs.ko': unknown symbol in module or invalid paramete[/I]r" or "[I]insmod: can't insert 'cifs.ko': invalid parameter[/I]", it depends)[/B]
I'm doing something wrong? I'm sorry but I need this function but I'm not a good hacker

m_pascal said:
I'm on stock KE7+CF Root and I have some problems.
I've downloaded cifs-for-GT-I9100.zip, uncompressed it and put the two files in /fs/cifs
ROOT---cf---cifs---cifs.ko
..................... |__slow-work.ko
I've started ADB SHELL and I typed
Code:
$su
#cd fs
#cd cifs
#insmod slow-work.ko [B](no reply, so I think it goes well)[/B]
#insmod cifs.ko [B](I get two messages of error "[I]insmod: can't insert 'cifs.ko': unknown symbol in module or invalid paramete[/I]r" or "[I]insmod: can't insert 'cifs.ko': invalid parameter[/I]", it depends)[/B]
I'm doing something wrong? I'm sorry but I need this function but I'm not a good hacker
Click to expand...
Click to collapse
Download it again. I've just uploaded rebuilt modules and it worked on KE7 kernel.

Working for me.
Thanks
Just a quick question because I failed with it: did you do any config other than enabling cifs?
Sent from my GT-I9100 using XDA App

Now "insmod cifs.ko" command has been accepted but "insmod slow-work.ko" tell me that that module has been inserited.
If the actual module is the same of yesterday there are no problem because yesterday I inserited it, otherwise I need the command for to remove the old module.
Let's go for try this hack!!! Thanks!!!

The new version is working for me on stock KE2 (now Mount Manager isn't working with the Galaxy S II, but that's a different story -> CifsManager works fine). Thanks!
May I ask what was changed in the latest version to make it work?

Grrrr!!!! I've installed Astro and his SMB module but, when I click on wifi button in the program, Astro crashes.
On Galaxy S I had the same problem.
Is there another program for to try this cifs.ko with pc?
Question 2: With this hack is possible to stream videos from pc to SGS2, viceversa, or both the directions? And It's the same for http/ftp connections?

m_pascal said:
Grrrr!!!! I've installed Astro and his SMB module but, when I click on wifi button in the program, Astro crashes.
On Galaxy S I had the same problem.
Is there another program for to try this cifs.ko with pc?
Question 2: With this hack is possible to stream videos from pc to SGS2, viceversa, or both the directions? And It's the same for http/ftp connections?
Click to expand...
Click to collapse
You don't need the SMB module - that's the whole point of the cifs module, so you can mount your shares within the phone's file system. Try CifsManager from the market, it will mount your shares to /mnt/cifs/<share> by default so you can access it with any file manager, and yes, any video player. It can also load the modules - put in the following to load both (my modules are in /sdcard/):
Code:
slow-work.ko;insmod /sdcard/cifs.ko

I've used Android Terminal and Cifs Manager to get this working. And really works!
Can we increase the read ahead buffer for cifs, does such a thing even exists? I need this because i've tried to play a 480p avi with mobo player and it was choppy because of constant buffering.
Thank you.
This is what i've used with Android Terminal after i've extracted the contents of cifs-for-GT-I9100.zip (from first post) to the root of my internal sdcard (/mnt/sdcard):
$su
#insmod /mnt/sdcard/slow-work.ko
#insmod /mnt/sdcard/cifs.ko
Click to expand...
Click to collapse
Note: After i have disabled wifi and put the phone in standbay for 30 minutes, it was very hot so i have restated it. Any ideeas?

nls_utf8.ko for Galaxy SII?
Hi I have some files/folders in Chinese. Where can I find the nls_utf8.ko for Galxay SII, thx?

jackleung said:
Hi I have some files/folders in Chinese. Where can I find the nls_utf8.ko for Galxay SII, thx?
Click to expand...
Click to collapse
Should not be necessary, AFAIK the kernel has this built in. You do need to use the mount option 'iocharset=utf8' though.

mdalacu said:
Can we increase the read ahead buffer for cifs, does such a thing even exists? I need this because i've tried to play a 480p avi with mobo player and it was choppy because of constant buffering.
Thank you.
Click to expand...
Click to collapse
I am interested in this as well, any video with a high bit rate seems to be jumpy.

All of this quiet over whelming is there a simpler way to enable this for stock kernel?
the *nood* way. Just wondering, not trying to piss anyone off.

jps1974 said:
Should not be necessary, AFAIK the kernel has this built in. You do need to use the mount option 'iocharset=utf8' though.
Click to expand...
Click to collapse
I am root and using stock KE7 kernel. Once I use this option in CifsManager, it reports segmentation fault error. Without such option, I can mount ok but with garbage characters for those Chinese named folder.
edit: you are right. It's built-in and I can mount properly with CLI. Probably something wrong with CifsManager. Someone already report this issue to the developer (http://forum.xda-developers.com/showpost.php?p=13480264&postcount=351)

adverse said:
All of this quiet over whelming is there a simpler way to enable this for stock kernel?
the *nood* way. Just wondering, not trying to piss anyone off.
Click to expand...
Click to collapse
This is all really simple(requires root) - download the cifs. ko and slow-work.ko files and put them on your sdcard. Then just download "terminal emulator" from the market and "cifs manager". Now open up the terminal and input the following:
$su
# insmod /mnt/sdcard/slow-work.ko
# insmod /mnt/sdcard/cifs.ko
(remember to click "Allow" at the root privlidges popup)
Then open cifs manager and click "Add new share.." and input the ip adress and folder for your share and voila you're done! Shouldn't take you more than a minute or so!
Note: I got an input/output error when I tried mounting a shared folder on an account without a password(Windows 7 64-bit).

adverse said:
All of this quiet over whelming is there a simpler way to enable this for stock kernel?
the *nood* way. Just wondering, not trying to piss anyone off.
Click to expand...
Click to collapse
Copy the two files to the sdcard and use cifsmanager from the Android market. Add the line "/mnt/sdcard/slow-work.ko:/mnt/sdcard/cifs.ko" to the advanced settings. Activate the "load per insmod " and the load on start options.
Sent from my GT-I9100 using XDA Premium App

Many thanks this made very simple for me too.
However for me I have to type the the following in cisfs manger to get it to work
/sdcard/slow-work.ko:/sdcard/cifs.ko
Many Thanks
Slick_42 said:
Copy the two files to the sdcard and use cifsmanager from the Android market. Add the line "/mnt/sdcard/slow-work.ko:/mnt/sdcard/cifs.ko" to the advanced settings. Activate the "load per insmod " and the load on start options.
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse

Great Stuff, thanks for tegrak!
Thought is it me or streaming files is laggy on the other hand plex works great, odd :/ Also on the same network my XOOM streams just fine via cifs itself.
Cheers.

The only solution for the lag I found so far is using the rock player in software mode.
Sent from my GT-I9100 using XDA Premium App

huzz said:
Great Stuff, thanks for tegrak!
Thought is it me or streaming files is laggy on the other hand plex works great, odd :/ Also on the same network my XOOM streams just fine via cifs itself.
Cheers.
Click to expand...
Click to collapse
You're welcome XOOM.. my address is.. I'm waiting to arrive your zoom to me.

[Q] GPS-Fix CM 10.1(Android 4.2) for Atrix (Epinter)

Hey there,
first I have to say - I'm new here - and yes, I have searched for my issue in this forum and elsewhere, but I didn't find a solution. So I decided to register here and ask you experts about helping me to fix my problem:
I'm on Epinters-Rom CM 10.1(Android 4.2) (26/08 Built) and having a problem with a fast GPS-Fix. Always when I use GPS the first time a day it lasts about 5-10Min to get a Sat-Fix. I have done some research about this problem and found this:
In a post on a german forum (I'm from Germany) for Defy Froyo and GPS bug I encountered that there are system files that contain specific configurations for GPS or direct downloading instructions of "ancillary data" (such as A-GPS Data). However, there are no configuration files with the name "location" in Epinters-Rom as they are mentioned in this thread, but I noticed a file in my system folder (system / ect / ) called "gps.config".
Doing more research about this file, I found a post here on XDA in epinters CM10.1 thread from August. Here is mentioned, that Epinters "gps.config" has no entry to an so called "NTP server. He made this entry and now the GPS fix is quick. I didnt really see that Epinter commented this, but a year before, Epinter said (at another Rom) that the NTP server entry is no longer necessary (without further explanation).
Then I remembered (coming from Neutrino-Rom) that Neutrino has had an "GPS-Addon" that was separate flashable - a fix for every single country. So I looked at the the GPS addon of Neutrino (Germany) and behold: When flashing this GPS addon it seems, that just the "gps.config" will be fixed with the following entry for Germany:
Code:
NTP_SERVER de.pool.ntp.org
NTP_SERVER = 0.de.pool.ntp.org
NTP_SERVER = 1.de.pool.ntp.org
NTP_SERVER = 2.de.pool.ntp.org
NTP_SERVER = 3.de.pool.ntp.org
NTP_SERVER = 0.europe.pool.ntp.org
NTP_SERVER = 1.europe.pool.ntp.org
NTP_SERVER = 2.europe.pool.ntp.org
NTP_SERVER = 3.europe.pool.ntp.org
XTRA_SERVER_1 = http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2 = http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3 = http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS : 0 - none , 1 - Error , 2 - Warning , 3 - Info
# 4 - Debug , 5 - Verbose
DEBUG_LEVEL = 0
# Intermediate position report , 1 = enable , 0 = disable
INTERMEDIATE_POS = 0
# Accuracy threshold for intermediate positions
# Less accurate positions are ignored , 0 for passing all positions
ACCURACY_THRES = 0
# Report supl ref location as position , 1 = enable , 0 = disable
REPORT_POSITION_USE_SUPL_REFLOC = 1
# Wiper ( wifi positioning ), 1 = enable , 0 = disable
ENABLE_WIPER = 1
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# # # # # AGPS server settings # # # # #
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
# FOR SUPL SUPPORT , set the Following Following
SUPL_HOST = supl.google.com
SUPL_PORT = 7276
SUPL_NO_SECURE_PORT = 3425
SUPL_SECURE_PORT = 7275
SUPL_TLS_HOST = FQDN
SUPL_TLS_CERT = / etc / SuplRootCert
# FOR C2K PDE SUPPORT , set the Following Following
C2K_HOST = c2k.pde.com
C2K_PORT = 1234
CURRENT_CARRIER = common
DEFAULT_AGPS_ENABLE = TRUE
DEFAULT_SSL_ENABLE = FALSE
# TRUE for " User Plane " , FALSE for " Control Plane "
DEFAULT_USER_PLANE = TRUE
In comparison to that, Epinters "gps.config" is only:
Code:
XTRA_SERVER_1 http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2 = http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3 = http://xtra3.gpsonextra.net/xtra.bin
SUPL_HOST = supl.google.com
SUPL_PORT = 7276
Do you think I could risk simply replace the two files? Or is it better to flash the file of neutrino? Or to edit the file by Epinter right? Or at least nothing at all? I do not even want to fabricate a Brick ...
So you techies from this forum! Can you help me?
Thanks for reading this and sorry for my poor english... its not my native language!
Regards,
Asmaron
PS: The Germany.zip in the appendix contains the files that would be flashed with neutrinos Rom (including the "gps.config"). The other single "gps.config.zip" is that of Epinters Rom. Simply open it in Editor/TextEdit or similar programs and you can see the above entries.

asmaron said:
Hey there,
first I have to say - I'm new here - and yes, I have searched for my issue in this forum and elsewhere, but I didn't find a solution. So I decided to register here and ask you experts about helping me to fix my problem:
I'm on Epinters-Rom CM 10.1(Android 4.2) (26/08 Built) and having a problem with a fast GPS-Fix. Always when I use GPS the first time a day it lasts about 5-10Min to get a Sat-Fix. I have done some research about this problem and found this:
In a post on a german forum (I'm from Germany) for Defy Froyo and GPS bug I encountered that there are system files that contain specific configurations for GPS or direct downloading instructions of "ancillary data" (such as A-GPS Data). However, there are no configuration files with the name "location" in Epinters-Rom as they are mentioned in this thread, but I noticed a file in my system folder (system / ect / ) called "gps.config".
Doing more research about this file, I found a post here on XDA in epinters CM10.1 thread from August. Here is mentioned, that Epinters "gps.config" has no entry to an so called "NTP server. He made this entry and now the GPS fix is quick. I didnt really see that Epinter commented this, but a year before, Epinter said (at another Rom) that the NTP server entry is no longer necessary (without further explanation).
Then I remembered (coming from Neutrino-Rom) that Neutrino has had an "GPS-Addon" that was separate flashable - a fix for every single country. So I looked at the the GPS addon of Neutrino (Germany) and behold: When flashing this GPS addon it seems, that just the "gps.config" will be fixed with the following entry for Germany:
Code:
Removed long code
Do you think I could risk simply replace the two files? Or is it better to flash the file of neutrino? Or to edit the file by Epinter right? Or at least nothing at all? I do not even want to fabricate a Brick ...
So you techies from this forum! Can you help me?
Thanks for reading this and sorry for my poor english... its not my native language!
Regards,
Asmaron
PS: The Germany.zip in the appendix contains the files that would be flashed with neutrinos Rom (including the "gps.config"). The other single "gps.config.zip" is that of Epinters Rom. Simply open it in Editor/TextEdit or similar programs and you can see the above entries.
Click to expand...
Click to collapse
For me, epinter's cm10.1 was the first time gps lock in in about 5 to 10 seconds, even if i was inside my house...
perhaps is better (previous backup) to edit the file and change the ntp servers to match your coutry's pools. then try,..
on cm7 i use an app called gps status to force calibration of the compass and to force inject fresh agps data, which helps a little

andresrivas said:
perhaps is better (previous backup) to edit the file and change the ntp servers to match your coutry's pools. then try,..
on cm7 i use an app called gps status to force calibration of the compass and to force inject fresh agps data, which helps a little
Click to expand...
Click to collapse
Hey!
Thanks for replying!
I use the GPS Status App too (and tried many other GPS Apps in market) and resetted agps-data many times an refreshed it. It helps a little but just for the moment and after one day not using GPS the fix lasts really long...
I would try to edit the "gps.conf" file but I use the Atrix as my main device, so I dont wanna brick it... Do you think, that editing this file will not force an brick? And what do you think is the best:
a) Editing Epinters "gps.conf" (of course after backing up the org. file, and everything else),
b) Exchange Epinters file with Neutrinos, or
c) Flashing Neutrinos "Germany.zip"?
Or even an absolute other solution?
Regards,
Asmaron

asmaron said:
Hey!
Thanks for replying!
I use the GPS Status App too (and tried many other GPS Apps in market) and resetted agps-data many times an refreshed it. It helps a little but just for the moment and after one day not using GPS the fix lasts really long...
I would try to edit the "gps.conf" file but I use the Atrix as my main device, so I dont wanna brick it... Do you think, that editing this file will not force an brick? And what do you think is the best:
a) Editing Epinters "gps.conf" (of course after backing up the org. file, and everything else),
b) Exchange Epinters file with Neutrinos, or
c) Flashing Neutrinos "Germany.zip"?
Or even an absolute other solution?
Regards,
Asmaron
Click to expand...
Click to collapse
Humm.. I edited the file and had no problems, I think edit is the safer option due to Neutrinos' files are for Gingerbread and we don't know what changed in the middle

andresrivas said:
Humm.. I edited the file and had no problems, I think edit is the safer option due to Neutrinos' files are for Gingerbread and we don't know what changed in the middle
Click to expand...
Click to collapse
Hmm... yeah thats true... so you have edited the file by yourself? What entries did you add? I thought Epinters settings worked for you?

asmaron said:
Hmm... yeah thats true... so you have edited the file by yourself? What entries did you add? I thought Epinters settings worked for you?
Click to expand...
Click to collapse
Sorry, that was on Gb, I edited the ntp servers to the ones off my country (Argentina). I was using root explorer at the time, but in cm10 the stock file manager can do it without problems (I used it to edit touchpad.cfg to fix raindrop bug). Only thing is you need to give it access via the app settings (can't remember as I'm back on cm7)

Hey!
Meanwhile I flashed the ROM from "Zn7mkUKzN1r8aCIV" where the flash is working. The fix lasts also very long and wasnt even stable. The entries of the "gps.conf" of "Zn7mkUKzN1r8aCIV" are exactly the same as the ones of epinter. So i tried to edit the "gps.conf":
- Editing the strings from the neutrino file (check OP), had the result that i didnt get a fix in even a half an hour.
- Restoring the "gps.conf" has the result of getting a fix after some minutes but not very stable.
- Now I have a edit of the "gps.conf" with the strings nlabrad mentioned in the post i told you before and the NTP-Server-Entries of Neutrino for germany (without blanks between the "="). Now i get a fix after some minutes that is stable, but the accuracy gets not better than 100 meters (328 feet). It stucks here and gets not better even after more than half an hour having a stable fix. To be exact it gets not better and not even worser. It stucks exactly at 100 meter accuracy.
Now i will test the GPS fix from that is mentioned here and i will report later!
Regards,
Asmaron

Did it!
Hey there!
I did it!
First it didn't work to exchange the "libnmea.so" from Krystian mentioned in the post above using the integrated file explorer. I allways got an Error when editing/copying/deleting the orig. "libnmea.so" in the "system/lib" folder. After that error somtimes GPS didn't work anymore at all (cant start it) or nothing was changed to the accuracy of the GPS. Well I have seen that by exchanging the file you have to set the permissions new (chmod 644) but I wasn't able to change it without getting an error.
So I tried another way: I extracted the Files of Zn7mkUKzN1r8aCIV's ROM and exchanged the "libnmea.so" org. file with the file from Krystian. I also replaced the "gps.conf" with an modified "gps.conf" containing the Neutrinos Strings from the Germany "gps.conf". Than I ziped and signed the modified files with LambOfGods Zip Signer Tool (v1.1) and flashed it (wiped Cache & Dalvik).
And now: Get a GPS-Fix (indoor) in about 45 sec with an accuracy of about 4 meters! YEAH! :victory:
Thanks for helping! Esp. thanks to you andresrivas and of course Zn7mkUKzN1r8aCIV and Krystian and so on!
Regards,
Asmaron

[/COLOR]
asmaron said:
Hey there!
I did it!
First it didn't work to exchange the "libnmea.so" from Krystian mentioned in the post above using the integrated file explorer. I allways got an Error when editing/copying/deleting the orig. "libnmea.so" in the "system/lib" folder. After that error somtimes GPS didn't work anymore at all (cant start it) or nothing was changed to the accuracy of the GPS. Well I have seen that by exchanging the file you have to set the permissions new (chmod 644) but I wasn't able to change it without getting an error.
So I tried another way: I extracted the Files of Zn7mkUKzN1r8aCIV's ROM and exchanged the "libnmea.so" org. file with the file from Krystian. I also replaced the "gps.conf" with an modified "gps.conf" containing the Neutrinos Strings from the Germany "gps.conf". Than I ziped and signed the modified files with LambOfGods Zip Signer Tool (v1.1) and flashed it (wiped Cache & Dalvik).
And now: Get a GPS-Fix (indoor) in about 45 sec with an accuracy of about 4 meters! YEAH! :victory:
Thanks for helping! Esp. thanks to you andresrivas and of course Zn7mkUKzN1r8aCIV and Krystian and so on!
Regards,
Asmaron
Click to expand...
Click to collapse
hI! I'm having hard time to understand exactly what you did to fix GPS accuracy. I'm the guy who asked Zn7mkUKzN1r8aCIV about the bug and I tried to overwrite the libnmea.so but it didn't work.... (I've had to flash again the rom to get back to 100m accuracy) Can you explain in a easier D) way how to fix it? I understand that you made a flashable zip maybe can you share it?

Hey there!
Well what I did exactly is:
1) Downloaded Zn7mkUKzN1r8aCIV's ROM (from 10/10/13) and extract it
2) Downloaded "libnmea.so" from Krystian
3) Replaced Zn7mkUKzN1r8aCIV's original "libnmea.so" in folder "system/lib/" with Krystian's one
4) Edited the "gps.conf" of Zn7mkUKzN1r8aCIV in folder "system/etc/" with the strings of Neutrinos "gps.conf" for germany (!) mentioned above *
5) Ziped and signatured the GPS-modified ROM files with "LambOfGods Zip Signer Tool (v1.1)" mentioned above
6) Wiped Cache & Dalvik - Flashed and GPS worked
I've uploaded my GPS-modified ROM with the german (!) "gps.conf" here:
Based on Zn7mkUKzN1r8aCIV's ROM 10/10/13 wich is based on Epinters ROM with modified GPS files for Germany from Krystian and Neutrino
Click to expand...
Click to collapse
with
a) "Standard"-Kernel:
CM10.1_Android4.2_GPSmodified.zip - 166.48 MB
b) "Hporch32-"Kernel (when Screen-Tearing occurs):
CM10.1_Android4.2.2_GPSmodified_hporch32.zip - 166.48 MB
I can't edit the "gps.conf" for every single county. Thats to much work. But you can do that on your own! I uploaded the files of Neutrionos "gps.conf"-Tweak here so you can download it and take the strings that you need for your country. In your case, I would do the following:
1) Download my GPS-modified ROM
2) Flash it, reboot and try out GPS - I will not take any responsibility for defects of your hardware! You flash it on your own risk!
2.a) If it works fast, its proofed that Neutrinos Strings in the "gps.conf" has no real effect - you can go to step 8
2.b) If it doesn't work (fast) you go to step 3
3. Download Neutrino GPS-Files and extract them
4. Choose the "gps.conf" that is related to your country (always stored in "system/etc/" folder of the zip-file of your country) and open it with editor
5. Edit the strings in the "gps.conf" on your Atrix (folder "system/etc/" - you will see, there are the german strings) with the ones of your country from the Neutrino File (make sure that there are no blanks between the " = " of each string**)
6. Save your edited "gps.conf" of the folder "system/etc" & check (imperative!) that the rights of the file are set on chmod 644!
7. Reboot and try out GPS
8. (Hopefully) Enjoy!
I hope it works! Looking forward to hear your report!
Regards,
Asmaron
* It is not proofed that this has any effect, but I think so, and now I have a GPS-Fix in almost a half minute.
** The effect of this is also not proofed! What I mean is type e.g.
Code:
NTP_SERVER=0.de.pool.ntp.org
instead of
Code:
NTP_SERVER = 0.de.pool.ntp.org

Hey! Did it work for you?
If not i have another suggestion:
Download my modified GPS-ROM, flash it (on your own risk), download the app "faster GPS" from playstore, choose your country settings in the app. It will modify the "gps.conf" and will set the NTP-Server settings for your country and region.
Maybe it helps... would be glad if you report here!
Regards,
Asmaron

libnmea.ko hack works on ICSROM (and related, I imagine)
asmaron said:
[...] Now i will test the GPS fix from that is mentioned here and i will report later!
Regards,
Asmaron
Click to expand...
Click to collapse
Came across this searching for a fix on my recent ICSROM update. I had to do the same thing when I first root/unlocked to install MROM, so that certainly helped. I noticed that the files sizes were identical, and not to the GB files, as one would expect. Anway, the issue manifested as GPS apps showing 0 accuracy, and WiFi-disabled Google Maps showing 1200m accuracy. After updating the file and chmod, it was showing ~7m accuracy.

Yup works a-ok...
jeremywh7 said:
[...] After updating the file and chmod, it was showing ~7m accuracy.
Click to expand...
Click to collapse
I meant '7ft accuracy' above. Anyway, I tested on my way to work this morn; locked at 5ft. I did see a couple times when it lost the lock and jumped around the map, but was brief. And I recall seeing that happen on the GB rom too.

How to change touch configuration of a device in the kernel.

Hello everyone.
I have a Japanese S6 Edge (404SC). So I tried to install a custom rom in this phone as the support has ended. I can install the rom with no problem and it would boot up until the initial welcome screen.HOWEVER the touchscreen would just not work. So I asked the developer and he told me that the touch configs of my phone is different than the other S6’s. So can someone please explain to me how to change the touch configuration of this phone while compiling the kernel to make the touchscreen work again.BTW,I also couldn’t find any guide regarding this issue. Thank you.

@mikel05
You don't have to compile anything.
Built-in embedded devices, particularly touch screens, almost always require input device configuration (.IDC - plain text ) files to specify their behavior.
Input device configuration files are located by USB vendor, product (and optionally version) id or by input device name.
The following paths are consulted by stock Android in order
/odm/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/vendor/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/system/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/data/system/devices/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/odm/usr/idc/Vendor_XXXX_Product_XXXX.idc
/vendor/usr/idc/Vendor_XXXX_Product_XXXX.idc
/system/usr/idc/Vendor_XXXX_Product_XXXX.idc
/data/system/devices/idc/Vendor_XXXX_Product_XXXX.idc
/odm/usr/idc/device-name.idc
/vendor/usr/idc/device-name.idc
/system/usr/idc/device-name.idc
/data/system/devices/idc/device-name.idc
Example of an .IDC file
Code:
# This is an example of an input device configuration file.
# It might be used to describe the characteristics of a built-in touch screen.
# This is an internal device, not an external peripheral attached to the USB
# or Bluetooth bus.
device.internal = 1
# The device should behave as a touch screen, which uses the same orientation
# as the built-in display.
touch.deviceType = touchScreen
touch.orientationAware = 1
# Additional calibration properties...
# etc...

jwoegerbauer said:
@mikel05
You don't have to compile anything.
Built-in embedded devices, particularly touch screens, almost always require input device configuration (.IDC - plain text ) files to specify their behavior.
Input device configuration files are located by USB vendor, product (and optionally version) id or by input device name.
The following paths are consulted by stock Android in order
/odm/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/vendor/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/system/usr/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/data/system/devices/idc/Vendor_XXXX_Product_XXXX_Version_XXXX.idc
/odm/usr/idc/Vendor_XXXX_Product_XXXX.idc
/vendor/usr/idc/Vendor_XXXX_Product_XXXX.idc
/system/usr/idc/Vendor_XXXX_Product_XXXX.idc
/data/system/devices/idc/Vendor_XXXX_Product_XXXX.idc
/odm/usr/idc/device-name.idc
/vendor/usr/idc/device-name.idc
/system/usr/idc/device-name.idc
/data/system/devices/idc/device-name.idc
Example of an .IDC file
Code:
# This is an example of an input device configuration file.
# It might be used to describe the characteristics of a built-in touch screen.
# This is an internal device, not an external peripheral attached to the USB
# or Bluetooth bus.
device.internal = 1
# The device should behave as a touch screen, which uses the same orientation
# as the built-in display.
touch.deviceType = touchScreen
touch.orientationAware = 1
# Additional calibration properties...
# etc...
Click to expand...
Click to collapse
Thank you @jwoegerbauer for your explanation.
So now to install the custom ROM where must I change these values. Like where are these files located
I'm really so sorry for asking this as I am still new to this.

@mikel05
Search the device for a file with extension idc: if not present then it got deleted when you flashed a new ROM and you're out of luck.

jwoegerbauer said:
@mikel05
Search the device for a file with extension idc: if not present then it got deleted when you flashed a new ROM and you're out of luck.
Click to expand...
Click to collapse
Actually the touchscreen works in the stock rom properly. It only doesn’t work in custom rom and kernels.
@ jwoegerbauer
Sorry for not informing earlier. My bad.

[VENDOR] [surya/karna] Unified - All Custom ROMS [10] & [11]

PHP:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
FEATURES
. The first, the one and the only custom vendor for dynamic partition in the world : I challenge you all to show me who did it before !
. If you find any custom rom with similar work since the first release of this one : it is just a copied and a stolen work [fake Google roms +++] !!!
. Compatible with all regions / basebands / firmwares / device variants
. Works with All AOSP/CAF based ROMs [10] & [11], Experimental, Official & Unofficial [TESTED]
. May works on fake Google roms but i don't take any responsibility
. Mount RO/RW available with no bootloop after reboot ! [Magisk/SU required]
. SafetyNet passed
. Full test passed : audio, ril, wifi, bt, fm radio, camera, sensors, fp scanner, nfc, ...
. All known hardware issues on custom roms are fixed : camera, wifi, bt, hdr playback, chrome ... and overheating !
. Custom Kernel with stock zImage [untouched +++]
IMPORTANT !
. NO firmware change is needed from the user side, so don't repeat this question many times ... just read up again !
. Formatting /data is required when you flash this vendor the first time +++
. Never go back to the previous versions due to the possible build.fingerprint change [Old releases are automatically removed] +++
. Dirty Update : always delete with file/root explorer or in TWRP this folder :
/data/property and reboot
You must delete these files & folders in /product partition from your custom rom
[File/Root explorer needed] :
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx
&
/product/vendor_overlay/29/etc/wifi
/product/vendor_overlay/29/overlay
& finally
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_huaxing_fhd_video_mode_dsi_panel.xml
/product/vendor_overlay/29/etc/qdcm_calib_data_nt36672c_tianma_fhd_video_mode_dsi_panel.xml
Already included in this vendor ... and since i'm the original author !
[ OPTIONAL ]
If you have the madness and the paranoia with security like Google, you can still relock /vendor again to the stock RO state ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.zip again !
How to [terminal or adb shell] :
su
tune2fs -O verity /dev/block/dm-1
*******
!!!
MIUI Users : sorry for you, but this is for custom ROMS " ONLY "
TROLLS & NOOBS, stay away ... Please !
!!!
Prerequisite:
POCO X3 NFC = surya
POCO X3 [no NFC] = karna
No matter where you live : india, china, russia, europe, usa or africa ... !
Kernel Source [Prebuilt] : Here
Created : 2021-02-27
Latest Update : 2021-03-21
DOWNLOAD

RESERVED for "Changelog"
Update : [2021-03-21] Highly Recommended !
- overlay folder [/vendor] : secure & total remove ... R.I.P forever !
You can now remove it from here too ... with no issue :
/product/vendor_overlay/29/overlay
[As always : no /data formatting is required if done in the previous builds !]
Update : [2021-03-20]
fix compatibility with all custom roms [10] & [11] +++ :
- build : preserve AVB structure [R/W still available in root mode]
- tune2fs : restore some stock feature flags [dir_index, huge_file, extra_isize]
- fstab [kernel & vendor] : small update
- vendor selinux : property_contexts fix
- build.prop : clean-up
Update : [2021-03-18]
clean-up & rework from scratch :
. all audio config [over 20 files +++]
. all media_codecs config
. new mixer_paths
[=> Exclusive]
- true resampling fix : r.i.p audio crackling and all audio issues in UX, Dialer, emulators ... etc [forever]
- improve audio & camera recording
- audio/video playback [Speaker, Headphones & BT] : Hi-Fi quality, loud & noiseless
[but first, you must delete these files with your File/Root Explorer:
/product/vendor_overlay/29/etc/audio
/product/vendor_overlay/29/etc/audio_policy_configuration.xml
/product/vendor_overlay/29/etc/audio_policy_engine_configuration.xml
/product/vendor_overlay/29/lib/soundfx
/product/vendor_overlay/29/lib64/soundfx]
Update : [2021-03-12]
- move to global 12.0.8.0 as firmware base [boot & vendor]
- ramdisk :
. disable mi_thermald and re-enable again thermal-engine
[on all custom roms : mi_thermald breaks the proximity sensor & suspend service in deepsleep => avoid hand wave gesture & AOD to work properly !]
. clean up & update
- vendor_selinux : add more camera permissions in property_contexts
- media_codecs : remove unused .xml
- ueventd.rc : rework from scratch
Update : [2021-03-07]
- ramdisk :
. update cpuset & schedtune settings
. improve memory multitasking
. make that "damn" fingerprint truly responsive
. enable UFS powersaving
. some clean-up & disable MIUI audio service
- media_profiles :
. rework from scratch
. add slow motion profile support : up to 1080p/120 fps & 720p/960 fps
. front video camera : add 4K support
- build.prop :
=> update parameters for : camera, ril, performance, playback ... and more
Update : [2021-03-05]
- rework from scratch : init.qcom.sh & init.qcom.post_boot.sh
- ramdisk : clean-up and add init.qcom.power.rc
. fix CPU instability : set 300 mHz as CPU minimum frequency for all cores / update schedutil governor parameters
. cpu_boost : improve touch responsiveness
. add built-in display power saving [for both huaxing & tianma panels]
- vendor permissions : rebuild from scratch / fix wronlgy settled paths (by Xiaomi) in some qti.xml
- camera : rework from scratch ISO/lowlight config
- remove dummy hbtp folder ... since there is no binary to load or device specific config
- targetconfig : update CoreCtlCpu to [0,6]
- build.prop : clean up and move NFC parameters to build_surya.prop
- [Bonus] : Wi-Fi signal improved (x2) !!!
. 2.4 Ghz : 144 => 300
. 5 GHz : 433 => 866
[but first, you must delete this folder, with your File/Root Explorer :
/product/vendor_overlay/29/etc/wifi ]
Update : [2021-03-01]
- update msm_irqbalance.conf
- update audio_effects.conf & remove audio_effects.xml
- universal vbmeta & vbmeta_system added
Update : [2021-02-27]
- initial release
- rework all build.prop (vendor & odm) from scratch
- debloated from unused MIUI folders, files & configs
- Kernel :
. enforcing selinux by default
. workqueue enabled in cmdline => better dynamic refresh rate handling by the CPU & stellar deep-sleep
. fstab reworked from scratch

the image you made is for enable rw or not?
my phone is poco x3 nfc surya

janhammer504 said:
To make things clear :
POCO X3 NFC = surya
POCO X3 (no NFC) = karna
No matter where you live (india, china, russia, europe, usa or africa) ... Choose the right vendor.img for your device !
[Both images were tested by me]
Click to expand...
Click to collapse
please share the surya image

aallii2 said:
please share the surya image
Click to expand...
Click to collapse
check the DOWNLOAD link up !

janhammer504 said:
check the DOWNLOAD link up !
Click to expand...
Click to collapse
tnx bro i'm downloading n i'll test

its not working after restart didnt boot n just go to recovry

aallii2 said:
its not working after restart didnt boot n just go to recovry
Click to expand...
Click to collapse
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!

janhammer504 said:
PREREQUISITE
- adb enabled (developer options)
- root (Magisk/SU)
- adb for Windows (Minimal ADB and Fastboot, provided)
- USB cable always connected
LIVE Flashing :
adb shell
su
dd if=/sdcard/vendor.img of=/dev/block/dm-1
View attachment 5232189
Reboot your phone right away ... then use your File/Root Explorer to test the mount RO/RW option and reboot again to check that there is no bootloop !
(Optional)
If you have the madness and the paranoia with security like Google, you can still re-enable AVB/Verity again ... But you will not be able to mount /vendor RW again even with root until you reflash the provided vendor.img again !
tune2fs -O verity /dev/block/dm-1
Check the full tutorial here to build your own custom vendor ... if you want !
DOWNLOAD
Click to expand...
Click to collapse
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...

jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
i use adb shell because terminal is too small for me, and for making tutorial.
the benefit ??? well there are a bunch of fixes to do in /vendor... check here for example
(the images i provided are clean with no modification, so i let developers or users doing their own modifications)

janhammer504 said:
Wich firmware version you had just before flashing ???
The vendor provided must match the firmware version that you have !!!
Click to expand...
Click to collapse
india 12.0.9
magisk 21.4

jeryll said:
... so, I can confirm that this is indeed working nicely, flashed RW vendor for Surya, just for the sake of the functionality, because I'm not sure about benefits I can get from writeable vendor (forgive my ignorance)...
... Thank you very much for your hard work...
just FYI I did flash it in Ofox recovery in built-in terminal, and also directly from running Android via Termux, so you don't need PC for it, just saying...
Click to expand...
Click to collapse
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found

aallii2 said:
hey bro how you flashed in orangefox?
i tried but this happened:
sh: adb: command not found
Click to expand...
Click to collapse
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1

now i cant install any rom :
updater process ended with error 7
pls help

aallii2 said:
now i cant install any rom :
updater process ended with error 7
pls help
Click to expand...
Click to collapse
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell

janhammer504 said:
O.M.G
it looks like you never used terminal
this is not a flashable file, it's a command line.
open terminal in your recovery to do that.
or use adb shell
Click to expand...
Click to collapse
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted
jeryll said:
in recovery adb not needed, just use
dd if=/sdcard/vendor.img of=/dev/block/dm-1
Click to expand...
Click to collapse
Now this came:
write error: Operation not permitted

Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !

aallii2 said:
india 12.0.9
magisk 21.4
Click to expand...
Click to collapse
wtf man, you should pick vendor.img from karna folder not surya !

janhammer504 said:
Use Minimal ADB and Fastboot.zip, it's the simplest and the fastest way.
Unzip and click on Minimal ADB and Fastboot.exe
type :
adb shell
su
It works like terminal in Windows. You can't go wrong !
Follow the instructions (1 post) !
Click to expand...
Click to collapse
i installed 12.0.7.0 global with magisk 22.0 then flashed vendor.img v12.0.7.0 but when restarted it stucked n i pressed power .phone boot but root explorer can't mount rw n just added shell in magisk

[RECOVERY][UNOFFICIAL][ABADONED] TWRP-3.5.2_10 [guamp] [Moto G9 / G9 Play / G9 Power]

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Bugs:
- you tell me
G9 Play - Ilitek (Work)
G9 Play - Himax (Dead)
G9 Play - Goodix, Chipone (untested)
G9 Power - Novatek (Work)
G9 Power - Focaltech (Untested)
E7 Plus - goodix,himax,chipone (Untested)
Install guide (Might not work):
To flash:
Code:
fastboot flash vbmeta_a vbmeta.img
fastboot --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity flash vbmeta_a vbmeta.img
fastboot flash recovery_a twrpname.img
fastboot flash recovery_b twrpname.img
To boot:
Code:
fastboot boot twrpname.img
Download:
GUAMP: MEGA
CEBU: MEGA
GUAM: soon
Reccomended ADB and Fastboot binaries:
platform-tools
Source code:
https://github.com/omnirom/android_bootable_recovery
https://github.com/100Daisy/android_device_motorola_guamp
Kernel source: prebuilt (for now)
Join our device chat in Telegram !
no link xda will remove anyways
gitdaisy applause circle:
https://t.me/GitDaisyShitposting
Donations:
paypal.me/100Daisy
Credits:
I want to say a big thanks to the testers @borraz

Hi! not work touchscreen in HImax.

condor323 said:
Hi! not work touchscreen in HImax.
Click to expand...
Click to collapse
contact me on Telegram @GitDaisy

Congratulations on your work. @GitDaisy this is the most complete TWRP for guamp I have used so far.
I have a Chipone touchscreen and your ROM titled twrp-3.5.2_10-guamp-270420211220... did not work for me.
However, I managed to get it to work by adding the following lines to the /system/bin/load-modules.sh:
Code:
#!/system/bin/sh
# two new lines
firmware_path=/vendor/firmware/ICNL9911.bin
flash_path=/sys/chipone-tddi/cts_firmware
insmod /vendor/lib/modules/chipone_tddi_mmi.ko
...
# wait extra time just in case
wait 3
# new line
echo $firmware_path > $flash_path/update_from_file
# wait extra time just in case. Not sure if necessary
wait 3
...
exit 0
It is a step I saw in another 'load modules' shell script that updates the firmware by updating the sysfs update_from_file chipone entry
I hope it helps other owners of this fabulous Moto G9 Play phone

jarchig said:
Congratulations on your work. @GitDaisy this is the most complete TWRP for guamp I have used so far.
I have a Chipone touchscreen and your ROM titled twrp-3.5.2_10-guamp-270420211220... did not work for me.
However, I managed to get it to work by adding the following lines to the /system/bin/load-modules.sh:
Code:
#!/system/bin/sh
# two new lines
firmware_path=/vendor/firmware/ICNL9911.bin
flash_path=/sys/chipone-tddi/cts_firmware
insmod /vendor/lib/modules/chipone_tddi_mmi.ko
...
# wait extra time just in case
wait 3
# new line
echo $firmware_path > $flash_path/update_from_file
# wait extra time just in case. Not sure if necessary
wait 3
...
exit 0
It is a step I saw in another 'load modules' shell script that updates the firmware by updating the sysfs update_from_file chipone entry
I hope it helps other owners of this fabulous Moto G9 Play phone
Click to expand...
Click to collapse
I will cover that issue in next release, then i will focus on bringing one image for all bengal devices released with A10 (G30 has vendor_boot and dt seems to not be compatible and kernel may be not compatible too)
currently i need to ship different prebuilts for all devices

Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...

Mauricio Oliveira said:
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Click to expand...
Click to collapse
@Mauricio Oliveira , you have the correct smartphone model (guamp). It is the same as mine.
However, there are several touchscreen variants and your application (cpu-z) does not show which variant you have.
Can you install the 'Device Info HW' application? Your touchscreen will show in the 'General' tab.

Mauricio Oliveira said:
Hello Everything is fine? Mine did not work the touch ... follow the attachment of the photo of my device. thanks to everyone who contributes to the growth of this forum, which is simplifying maginifico ...
Click to expand...
Click to collapse
Another way to find out your touchscreen manufacturer is by connecting to your mobile using the ‘adb shell’ command.
From your desktop, run:
Code:
adb shell
and then
Code:
getevent
the command will show output like the following:
Code:
guamp:/ # getevent
add device 1: /dev/input/event2
name: "chipone-tddi"
add device 2: /dev/input/event0
name: "qpnp_pon"
add device 3: /dev/input/event1
name: "gpio-keys"
In this case, ‘chipone-tddi’ is the touchscreen manufacturer.

ok, obrigado pelo feedback .

Hello everyone on the forum... Thanks again my friend jarchig. I noticed that my screen variant is the same as yours... Read in your posts that you have successfully added commands to enable it. Could you teach step by step how to do this?

Thank you in advance.

I have a guamp device and I want to install this recovery.
Where can I find the vbmeta.img file for the device? It seems that the MEGA link only have twrp-3.5.2_10-guamp-270420211220-unofficial.img image.
It is possible to install AOSP, or image from https://mirrors.lolinet.com/firmware/moto/guamp/official/ right now? It seems do not exist LineageOS or other roms yet for this device.

did twrp work for anyone?

piperoman said:
I have a guamp device and I want to install this recovery.
Where can I find the vbmeta.img file for the device? It seems that the MEGA link only have twrp-3.5.2_10-guamp-270420211220-unofficial.img image.
It is possible to install AOSP, or image from https://mirrors.lolinet.com/firmware/moto/guamp/official/ right now? It seems do not exist LineageOS or other roms yet for this device.
Click to expand...
Click to collapse
I see that nobody respond to you...
I use the image from the link that you share, specifically RETLA. You must download the zip file, decompress it and you can see the vbmeta.img file

GitDaisy said:
contact me on Telegram @GitDaisy
Click to expand...
Click to collapse
it doesn't work for me too, the himax touchscreen ,guamp version, can you help me?
If the android version is 11 how does it work? mine has android 11 sorry i think there is no solution for me

Better Mobile App

welcome