yashsingh1/xdaforums huggingface dataset:
[Xposed Framework Modules] KroenenPrime:
Looks interesting for MITM I guess.

Difficilement lisible mais essaie sans IMEI Changer déjà pour vérifier s'il y a bel et bien conflit ou pas.
[Xposed Framework Modules] Alain74150:
Bonjour, merci pour votre réponse, mais ça ne veut pas marcher sur mon S7 Edge avec Android 8.0 Oreo, j'ai viré

Imei changer, et pas plus de résultat, du coup , je me suis rabattu

sur Imei changer pro seulement pour l'imei. Merci quand même.

Désolé pour le langage du premier message, j'ai vu que tous les accents étaient transformés en langage codé ;)
[Xposed Framework Modules] pol-der:
Love free
[Xposed Framework Modules] b0rnc0nfuz3d:
This is an english only forum
[Xposed Framework Modules] pol-der:
+1 @Moderators should do something.
[Xposed Framework Modules] cjdandy:
thanks for your awesome work, there is a problem with premium version 4.2 it does not change the values but the free version does

i would like to change the imei only for an specific application using your filter in the premium version, would be grateful if you look into the issue thanks

i am using android nougat
[Xposed Framework Modules] mortez123:
hello, can you add one more feature? My phone is single sim, but I want to give two IMEI to an app, so that, that app identifies that my phone is dual sim. Is it possible?
[Xposed Framework Modules] negatyw001:
Does it work for you on android from 7 and higher? For me it works only for 6.
[Xposed Framework Modules] Gmx1987:
Wtf trash omg 1milon Ads and nothing more s cam

Dosnt work waist time

---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------

Change you head 3euro for what!!!!!????
[Xposed Framework Modules] delevic:
Just use version Hijack suite premium 1.3.4 its the best. 4.2 is bad. You can find it on net ;)
[Xposed Framework Modules] negatyw001:
This OLD version, works in android 7...???
[Xposed Framework Modules] KaaMyA:
Hi, [MENTION=7187595]shs94[/MENTION].

I have a question... My device is an Android 9 Xiaomi MiA1 with AEX ROM.

I could change WiFi MAC address, but now I'm not able to connect to WiFi anymore.

I Don't know if it's necessary to change Bluetooth MAC as well, since original MAC addresses were consecutive.

Also, I'm thinking this device uses fake+real MACs.

Do to have any recommendation in order to be able to connect to WiFi successfully with changed WiFi MAC, for this device?

PD: This reminds meI wanna ask you if you're planning to add Bluetooth MAC Changer feature.

Thanks in advance!
[Xposed Framework Modules] SmilingSword:
please add some more , i bought the premium

add some spoof like spoofing the cpu, fake sim card, wifi,
[Xposed Framework Modules] gsmtinkerer:
causes wifi not to work on android pie. stuck on "obtaining ip address".
[Remix OS for PC] libergm:
So, following jide's instructions here, for a full install on an older HP pavillion g6, 64 bit, I do an INSTALL=2. It makes the partitions and does a full install. Says remix install complete OK at end. When I power on says no OS to boot. I looked at the partitions with gparted and it has three partitions, FAT 32 boot EFI, a 1GB with OS and rest with data. Any help would be greatly appreciated.

V/R,

Gary
[Remix OS for PC] Bobcat22:
How about a version number for that OS?

The forum should be devised to accommodate separately, version 2x and 3x. Which version are you working?
[Samsung Galaxy Star] Hicham03:
I was trying to flash stock firmware (.tar.md5) with FlashFire directly on my Star 2+ (SM-G350E), everything went correctly, but suddently, after flashing modem and system, the phone rebooted, then stucked forever on splash screen... I went to download mode, and always find current bin and system status CUSTOM... I only have stock recovery...

Have anyone else faced that problem? Thanks ij advance.

PS: Almost the same problem occured to my S5 mini, just beginned flashing system and rebooted itself on sammy logo forever.. Fixed with odin..
[Samsung Galaxy Star] Sohammirikar:
-Use Odin to flash, it works on all Samsung devices.

1. Open Odin and select firmware in PDA Column.

2 (IMPORTANT) Tick on "Nand erase all"

3 After firmware flash completed phone will aromatic rebooted.

4. (IMPORTANT STEP) now to to "recovery" and then do a wipe data/factory reset in recovery.

5. Reboot system and enjoy!

- IT'S NASSESARY TO DO A FACTORY RESET.
[Samsung Galaxy Star] Hicham03:
Thanks for your reply, but I already know how to flash a firmware in Odin :D

I mostly want to know FROM WHERE the problem came, not how to solve it ;)
[Samsung Galaxy Star] Sohammirikar:
You need to tick "Nand erase all" to erase your phone and install firmware.
[Samsung Galaxy S II Plus] AnDyX:
Hi,

I have S2 plus phone from friend with stock 4.2.2 ROM installed. Can someone recommend me tutorial I can follow and ROM that is stable enough for daily usage?

Thx,
[Samsung Galaxy S II Plus] :
Rooting process:

1. Download Odin,CWM recovery and SuperSU zip from the following links:

https://www.androidfilehost.com/?fid=95916177934547981 - Odin

https://download.chainfire.eu/696/supersu/ - SuperSU zip

http://d-h.st/bq8 - this is CWM for GT-I9105 model(the one without NFC)

http://d-h.st/II4 - this is CWM for the GT-I9105P model(the one with NFC)

2. Next copy the SuperSU zip to your phone and reboot it into download mode(Hold Volume Down,Home and Power)

3. Open Odin and select PDA and choose your downloaded recovery and un-check auto restart

4. Press Start and when it finishes take out the battery

5. Enter recovery by holding down volume up,home and power

6. Once you are in recovery install the SuperSU zip and reboot your phone

Yay you are now rooted!

And the ROM I would recommend using is either XOSP 6.3 or Resurrection Remix
[E 2015 Q&A, Help & Troubleshooting] battle_hardened:
I am curious what is placed in the unused space of the non dual-sim variants of our phone.

If you take the rubber bumper off the phone you'll see:

for xt1506, xt1514, xt1521, xt1523:

sim1 slot --- sdcard slot --- sim2 slot

for xt1505, xt1511, xt1524, xt1526, xt1527, xt1528:

sim1 slot --- sdcard slot --- plastic flap

I tried to take the plastic flap off my xt1524 but I can't manage to loosen it without damage. What is behind this flap? If it's just empty space i'd like to use it for storage, if it's a boarded up extra sim slot I'd like to activate and use it.

has anyone disassembled his or her non dual-sim variants and seen what is in there? Please post results and your exact model.:good:
[E 2015 Q&A, Help & Troubleshooting] xtermmin:
https://www.youtube.com/watch?v=4QTQGzJHFYI

It looks like the metal bracket for the SIM2 slot is there, but I don't see any pins for reading the SIM.
[E 2015 Q&A, Help & Troubleshooting] battle_hardened:
So weird that they would go into the the trouble of soldering a metal bracket on it.:rolleyes:

The video doesn't tell what version it is besides Moto E 4G LTE.
[E 2015 Q&A, Help & Troubleshooting] xtermmin:
Most likely one of the US models, as CNet is a US media company. The US models were only offered as single-SIM variants.
[Nexus 6P Q&A, Help & Troubleshooting] rudra_666:
Hey guys, I've been using CM13 builds on my Nexus 6p for last few months. Generally, i flash new builds after 3/4 days from the last one. Everything's works fine, no big issues; but recently from last months build which ever update i flash on the device, the WiFi seems not working. It shows, it's on - Searching for Networks; but not able to connect or even find any network at all. And i tried to flash back to the older builds of CM13, the WiFi works fine on those builds quite fine. Beside this, I've tried Paranoid Android ROM on this device, WiFi works fine on that rom. So, have any of you faced such problem on CM13? And, please can anyone help me out on this matter?... Thanks in advance... :)
[Nexus 6P Q&A, Help & Troubleshooting] blitzkriegger:
I've been successively flashing the nightlies from 07/24 until today and have had no issues with Wi-Fi. Sounds like yoh crossed over drom June to July build. Flash the July vendor image then re-flash latest cm and you should be good to go. If you use a custom kernel also make sure you are using the latest version made for this month.
[Nexus 6P Q&A, Help & Troubleshooting] rudra_666:
Thanks a lot, brother. I've just flashed the latest vendor image, and it's working smoothly... :D
[Samsung Galaxy Nexus] musical_chairs:
Builds can be found at: http://dl.omnirom.org/toroplus/

This OP was shamelessly copied from the official maguro thread: http://xdaforums.com/galaxy-nexus/development/rom-omnirom-04-16-t3360596

-----------------------------------------------------------------------------------------------------------------------

Google Apps can be found at http://opengapps.org/?api=6.0&variant=nano - beware that if you choose OpenGApps, only the nano version will fit! Also, starting from M, it's recommended to install gapps before the initial boot so the permissions are properly set up.

Bugs:

- Sometimes, quiet speaker pop sounds can be heard at the beginning and/or end of some audio streams (ie. touch sounds - the workaround is to disable them). For some reason, this isn't affecting everyone.

FAQ:

Does this ROM has CMA?

- Yes!

Does this ROM supports F2FS?

- Yes, on /data.

Does this ROM uses DDK 1.9?

- Yes, with all the camera issues (ie. pink lines, rare crashes) resolved.

Why does the initial boot take so long, and where are my live wallpapers?!

- To make room on the system partition for the (bigger) M gapps packages, I had to sacrifice dexpreopt and the live wallpapers. This can result in pretty long initial boots or upgrade boots, and dexpreopt might run during the first time setup wizard as well, slowing down the system for an additional couple minutes.

XDA:DevDB Information

[ROM][6.0.1][OFFICIAL] OmniROM, ROM for the Samsung Galaxy Nexus

Contributors

musical_chairs, Ziyan

Source Code: https://github.com/omnirom/

ROM OS Version: 6.0.x Marshmallow

ROM Kernel: Linux 3.0.x

Based On: OmniROM

Version Information

Status: Nightly

Created 2016-07-31

Last Updated 2016-08-03
[Samsung Galaxy Nexus] musical_chairs:
Please test! We would like to turn on official nightlies soon.

Soon we will have more ROMs that users for this phone. :p
[Samsung Galaxy Nexus] Ckpe4:
Great!

Can we expect for a official TWRP builds?

As far as I know, they must be based on omni, and if there will be official omni nightlies, it should not be a problem.
[Samsung Galaxy Nexus] musical_chairs:
That's the whole point of this exercise. ;)
[Samsung Galaxy Nexus] Max Frost:
I'll give it a shot and see how it does . I've been running 4.4.4 lately since LTE came to our area . I haven't had any luck getting LTE up on Lollipop or MM roms for this device . Does Omni use their own device tree or CM's ?
[Samsung Galaxy Nexus] musical_chairs:
Omni uses their own source code, including device trees and vendor trees. I did the bringup on both of those, so I would be surprised if LTE works. The telephony stack is a good bit different that cm's, though, so who knows?
[Samsung Galaxy Nexus] Max Frost:
Installed Omni today . Seems fast and snappy . I'm not in an LTE area today but will be soon . Is there no way to install themes on Omni ? I'd really like to customize it . Am I overlooking something ? Thanks .
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
So, I am in a 4G area, and I've switched my preferred network from 3G/CDMA to 4G/LTE but, I'm not getting a connection. What information do you need to help diagnose this?

EDIT: Is the device encryption in OmniROM decryptable by TWRP? I want to enable device encryption but, I still need to be able to update my device and the last time I did it (on CM 12.1) TWRP couldn't decrypt my partitions so it couldn't actually update my device.
[Samsung Galaxy Nexus] tomm1e:
If you have the debugging tools installed on your PC, save the radio log after it fails to connect to 4G:

adb logcat -b radio > radiofail.log

Or you can install the CatLog app from Play store, but root is required to read the logs, in CatLog go to Settings (bottom right menu button on app, under "More"), and in Log Buffers make sure only Radio is checked. These logs can get HUGE so best way to take a clean log snapshot is set the preferred network mode to 4G/LTE, reboot the phone, then save the logs after a few minutes of running

The most repeated error in the logs:

08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info

08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): findApnInfo() no apns in apn_info

08-09 23:46:22.401 E/use-Rlog/RLOG-RIL[C](256): getAttachCid(): Unable to find attach apn info

Wild guesses:

- Internal problem with loading the APN during 4G and not necessarily a missing/misconfigured APN? (although 3G APNs work)

- Android 5.0+ RIL Library / Kernel incompatible with the toroplus' LTE radio, due to some change in code?

On 4.4, when Preferred network was set to LTE/CDMA auto, if LTE was out of range it would fall back to 3G, I think that's what eHRPD network is for, to switch between 4G/3G.

On 5.0+, it just gets stuck trying to connect to LTE, the network ends up showing either eHRPD or 1xRTT, and seems like it retries over and over, instead of stopping and connecting to 3G, you can feel the performance of the phone drop when it's trying to connect to LTE, some function keeps running in the background
[Samsung Galaxy Nexus] Roman20:
I install this rom today but a couldn't receive text message, when i tried to authenticate my Gmail i never get the text message notification. when i change back the rom to cyanogenmod all notification arrive to my phone. i send a text message from another phone too and it never arrive.
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
So, here's a log from a few minutes of being unable to connect to 4G. It ends with me receiving a phone call which, of course, ended my testing cycle. Tell me if you need a longer sample. Also, this is using yesterday's (2016-08-09) nightly, if that changes anything.
[Samsung Galaxy Nexus] musical_chairs:
Both are realistic possibilities I think. I know on toro, we need to use older APNs - although there, data won't connect at all with the stock APNs. I'm used to seeing the logs filled with APN info, it's strange that it totally fails to load any APNs at all. I highly doubt the kernel is to blame, but there have been plenty of changes in the RIL code since 4.4.

That log should be long enough, it looks like your phone got bored and quit trying about two minutes before you got your phone call. In addition to the log snippet posted by socialentry, I find this sequence interesting:

08-10 19:23:24.232 1088 1088 D DCT : [0]setInitialApn: defaultApnSetting=[ApnSettingV3] null, 0, null, null, null, null, null, null, null, 3, default | mms | supl | hipri | fota | ims | cbs, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, ,

08-10 19:23:24.232 1088 1088 D RILJ : Set RIL_REQUEST_SET_INITIAL_ATTACH_APN [SUB0]

08-10 19:23:24.232 1088 1088 D RILJ : [3770]> RIL_REQUEST_SET_INITIAL_ATTACH_APN, apn:null, protocol:IP, authType:3, username:null, password:null [SUB0]

08-10 19:23:24.242 266 299 D secril-shim: onRequestShim: got request RIL_REQUEST_SET_INITIAL_ATTACH_APN: forwarded to RIL.

08-10 19:23:24.242 266 299 E use-Rlog/RLOG-RIL[C]: CreateAndPushRequest CreateRequest() Failed.

I'd venture to guess that the APN info failing to appear is a problem, though whether it is the main problem or just a result of something going wrong earlier in the chain, I don't know.
[Samsung Galaxy Nexus] Max Frost:
Great post and it's the same with all the L and M roms . I feel like it's so close to being there . The sprint variant is the only one not getting LTE , right ?
[Samsung Galaxy Nexus] tomm1e:
Correct, users reporting LTE working on verizon's toro

I've attached some radio logs, maybe they are overkill, although the 6.0.1 logs were not in a strong LTE area hopefully it will help explain why it's not falling back to 3G if 4G fails?

On 6.0.1 logs, I've used the 4.4 APN that was working with LTE, and I deleted the OTA sprint APN, sometimes it was selected as default apn. Once I can get in a stronger LTE area I'll post new logs.
[Samsung Galaxy Nexus] tomm1e:
Today I replaced the default apns-conf.xml (attached) in /system/etc with the CM11 apns file, went to Access Point Names, and "Reset to default", now I can switch between 3G and 4G in the menu. However, when I select 4G it successfully connects to the eHRPD network to 3G if theres no 4G (takes about 30 seconds), but the 3G icon has the exclamation point, and it says Network is unreachable

CM11 APN settings:

Old APN settings:

Deleted:
[Samsung Galaxy Nexus] musical_chairs:
Interesing, so it's something in the apns that is causing them to fail to load when 4G is selected? Maybe the bearer is the issue. I don't think our ril's like the bearer_bitmask part that was added in 6.0. That wouldn't explain why 4G fails in 5.1, though there have been some reverse-engineering ril blob updates for 6.0, so it's not out of the realm of possibility that we could get things working on 6.0 and the fix may not work on 5.1.

Some little ideas to try:

- Try setting the protocol to IPV4 only - obviously the attempts at IPV6 aren't going well in your log.

- Try deleting "default" from the 'Type' field in the Sprint LTE internet apn.

- Try deleting "bearer" from the eHRPD apn. (I got that idea from here: https://github.com/CyanogenMod/android_vendor_cm/commit/0c80c8c3e7bb4224cecc7a1ee579e60ea1a69079)
[Samsung Galaxy Nexus] tomm1e:
So I renamed n.ispsn back to sprint

Now the eHRPD network transfers to the EvDO-A network successfully when preferred network type is set to 4G/LTE. I have not tested in a LTE area though.
[Samsung Galaxy Nexus] tomm1e:
Well, I had a few minutes in a LTE area, The LTE apn wasn't working, so I renamed the apn back to n.ispsn and set the "LTE only" network setting, it immediately showed 4G icon but with the exclamation point :confused: Then when I removed "default" from the types, it wouldn't show 4G anymore, only a bare icon. I didn't have time to remove the bearer in the file but next time I will try it.
[Samsung Galaxy Nexus] musical_chairs:
It shows that it's connected:

08-12 23:43:01.820 D/CDMALTEPhone(1017): getDataConnectionState apnType=default ret=CONNECTED

Also looks like a route is set up:

08-12 23:43:01.772 D/DC-1 (1017): REQ_GET_LINK_PROPERTIES linkProperties{InterfaceName: rmnet1 LinkAddresses: [29.234.83.179/32,] Routes: [0.0.0.0/0 -> 29.234.83.1 rmnet1,] DnsAddresses: [66.1.68.132,66.1.64.132,] Domains: null MTU: 1422 TcpBufferSizes: 524288,1048576,2097152,262144,524288,1048576}

For reference, the equivalent line on toro with 4G connected looks like this:

08-13 06:26:34.958 1271 1421 D DC-2 : REQ_GET_LINK_PROPERTIES linkProperties{InterfaceName: rmnet1 LinkAddresses: [100.111.33.101/32,2600:1002:b004:65eb:0:5b:c4bb:d601/64,] Routes: [0.0.0.0/0 -> 100.111.33.1 rmnet1,::/0 -> 2600:1002:b004:65eb::1 rmnet1,] DnsAddresses: [198.224.188.236,198.224.189.236,2001:4888:15:ff00:194:d::,2001:4888:14:ff00:196:d::,] Domains: null MTU: 1500 TcpBufferSizes: 524288,1048576,2097152,262144,524288,1048576}

Thanks for your work on this!
[Samsung Galaxy Nexus] tomm1e:
The pings test would still fail. I'm still thinking the LTE apn settings are wrong, I'll try more out next time.
[Samsung Galaxy Nexus] Cardcaptor_RLH85:
I'm having a strange issue with my Bluetooth headset disconnecting randomly during calls. I don't have any issues maintaining a connection while listening to music but so far, at least once on any call that runs more than 3 minutes, it disconnects and reconnects. I've tried re-pairing it to no avail.

This is a pretty strange issue for me and one I haven't seen before. Normally when I have Bluetooth issues they affect media and phone audio not just one. Thanks for any help you may be able to provide with this issue. I'm running the 2016-08-14 Nightly using SuperSU for root.
[Samsung Galaxy Nexus] tomm1e:
Main log shows route problem when 4G has the exclamation mark:

Back home where I don't have LTE, only eHRPD or EvDO, I figured out how to add the route if it failed to setup. Now eHRPD data works with the apn n.ispsn from CM11 apns-conf.xml, instead of switching over to EvDO-A like when it was set to "sprint"

adb shell

su

ifconfig

When connected to eHRPD or LTE with the exclamation point, we will see a couple of interfaces named "cdma_rmnetX" or "lte_rmnetX" which are bridges to "rmnetX", you must use the rmnetX interface name, and use the IP address associated with the interface.

Verify the routing table:

ip route show

If it returned nothing, we need to add a route. If we got assigned 1.2.3.4 and interface name is rmnet1

ip route add table main 1.2.3.0/24 dev rmnet1 proto kernel scope link src 1.2.3.4

ip route add table rmnet1 default via 1.2.3.1 dev rmnet1 proto static

* Note how we end the IP with 0/24 on the first IP in the first line and 1 on the last line

After this, internet should work, verify by running

ping 8.8.8.8

This is only a temporary fix, it will go away if you get a new IP assigned or restart the phone. Sometimes the routing info disappears after a while, ip route will return blank, but there is still a table, as long as the table is there it still works, you can see all the tables with ip route show table all

First 4 lines of a working table look like this:

When it's not setup but an IP is received, its missing the default and first route

Also, I noticed there was recent APN change in CM13

https://review.cyanogenmod.org/#/c/154612

Sounds like a cosmetic thing but maybe it will help with our issue
[Samsung Galaxy Nexus] tomm1e:
LTE confirmed working with the route table fix and CM11 apns-conf.xml settings.

- It's only EvDo networks that setup a route, when on eHRPD or LTE it tries to add the route too early and fails.

- The settings menu 4G/LTE selection sets the preferred network to "LTE/CDMA (auto)" which only ever connects to 3G

LTE Preferred network types that work (Dial *#*#4636#*#*):

- LTE/GSM (auto)

- LTE only

Attached the script I made to quickly add the routes through a terminal emulator as root. Extract routefix.zip your /sdcard directory.

Example:

cd /sdcard/routefix

su

sh fix.sh

*** This is not a permanent fix, routes are cleared when a new IP is assigned or Wifi is connected. ***
[Samsung Galaxy Nexus] musical_chairs:
This could be our issue. LTE/GSM (auto) is android band 7, LTE/CDMA (auto) is android band 8. Our RIL's have a bug in them where the mapping of these bands is reversed. Or, they had that bug - toro's RIL has been fixed by reverse engineering. The guy who fixed that, [MENTION=3390093]MWisBest[/MENTION], said he found the same bug in toroplus's RIL and fixed it too. But toroplus's RIL didn't completely break from the bug like toro did, maybe something else is was remapping the bands on toroplus, so that since the 'fix' they are actually now reversed? Or maybe his fix on toroplus is incomplete?

I will do some digging and see if I can find a toroplus RIL blob with the LP/MM fixes but without the band 7/band8 fix. Or maybe I can get ahold of MW and ask him to undo that part of the fix.

Edit: It looks like he's got all the various versions of toroplus's RIL blob here. I'll make a test build of the ROM with your APN's, an RIL blob without the band translation edit, and with the overlays changed back to calling band 7 for LTE/CDMA. We'll see what happens then I guess. It may be a few days before I can get to building this.
[Samsung Galaxy Nexus] Max Frost:
Sounds great . I'll definitely try it out with our LTE here whenever its ready .
[Samsung Galaxy Nexus] musical_chairs:
...informed me that LTE/GSM (auto) is actually band 9, which is really bizarre that you have LTE working on that. In any case, I've got a test ROM building, will try to get it uploaded tomorrow.
[Samsung Galaxy Nexus] musical_chairs:
Here's a test build: https://www.androidfilehost.com/?fid=24686679545610568

It includes [MENTION=7500155]socialentry[/MENTION] 's APNs and a libsec-ril_lte.so blob without the band mapping fix. Let me know if it behaves any differently.