Related
Hello,
I tried posting this to the development forum, however since it's my first post I ended up here, so I'm sorry if this seems a bit off topic. Anyway, hi and thanks for having me
Now, what I've been trying to do is load a (backed-up) stock Xperia X10 Mini Pro (U20i) 2.1.1.A.0.6 system.img into the Android SDK Emulator. The problem is I get a corrupted image like the one in the screen shot, here:
imageshack.us/photo/my-images/32/u20iscreen.png
I'm not sure what's causing this, I can only guess that it's a bad screen configuration parameter, so I hoped someone here might have the solution.
I know it's not the system.img, cause I've tried several of them and ended up with the same results, and it's not my OS/SDK/... setup, because without the system.img the emulator works fine.
Here's my avd config:
Code:
hw.dPad=no
hw.lcd.density=160
hw.camera.maxHorizontalPixels=2592
hw.cpu.arch=arm
sdcard.size=512M
hw.camera=yes
hw.gpu.enabled=yes
hw.touchScreen=yes
skin.path=platforms\android-7\skins\QVGA
hw.keyboard.lid=yes
hw.keyboard=yes
hw.lcd.depth=16
hw.ramSize=176
hw.sensors.magnetic_field=yes
hw.sdCard=yes
hw.mainKeys=yes
hw.accelerometer=yes
hw.lcd.height=320
skin.name=QVGA
abi.type=armeabi
hw.audioOutput=yes
hw.trackBall=no
hw.camera.maxVerticalPixels=1944
hw.battery=yes
image.sysdir.1=platforms\android-7\images\
hw.audioInput=yes
hw.sensors.orientation=yes
hw.gps=yes
hw.lcd.width=240
vm.heapSize=24
So, do you see anything wrong with this? Maybe the LCD parameters are wrong? I really don't know
Anyway, ask if you need any more info and thanks in advance
Partially solved
Well, after another hour of trial and error I managed to get it working
Setting the resolution to 320x480 fixed the graphics corruption problem and, although stretched, the emulated screen is now usable. Also, setting the LCD density to 320 really improved the image.
For my purposes (safely testing themes) this is close enough, but I would really appreciate it if someone found the right way of doing this.
Here's the working adv config in case anyone needs it. I'll keep trying, but please let me know if you find the correct screen parameters.
Code:
hw.lcd.density=320
hw.dPad=no
hw.camera.maxHorizontalPixels=2592
sdcard.size=512M
hw.cpu.arch=arm
hw.camera=yes
hw.gpu.enabled=yes
hw.touchScreen=yes
skin.path=320x480
hw.keyboard.lid=yes
hw.keyboard=yes
hw.lcd.depth=16
hw.ramSize=176
hw.sensors.magnetic_field=yes
hw.sdCard=yes
hw.mainKeys=yes
hw.accelerometer=yes
skin.name=320x480
abi.type=armeabi
hw.audioOutput=yes
hw.trackBall=no
hw.camera.maxVerticalPixels=1944
hw.battery=yes
image.sysdir.1=platforms\android-7\images\
hw.lcd.backlight=yes
hw.audioInput=yes
hw.sensors.orientation=yes
hw.gps=yes
vm.heapSize=24
Hello friends, I need my counter 0 life time of the galaxy s2, have tried a lot but not found
USB jig, please read.
Sent from my GT-I9100 using XDA App
Yep as already mentioned you want the USB jig.
Here is a good thread
http://forum.xda-developers.com/showthread.php?t=1402286
Sent from my GT-I9100 using XDA App
I spoke of this life time is the total time of phone calls, I thought the jig only served to counter Odin Reset / Reset custom binary counter
atylla11 said:
I spoke of this life time is the total time of phone calls, I thought the jig only served to counter Odin Reset / Reset custom binary counter
Click to expand...
Click to collapse
Are you talking about when you go to Call Logs > Menu > Call duration? If you press menu from there, the only option is "Reset". Resets all timers.
Otherwise, if you're talking about a different timer/log of calls, where are you talking about?
is a secret menu which displays the amount of time all calls
atylla11 said:
is a secret menu which displays the amount of time all calls
Click to expand...
Click to collapse
Ah. Well, I don't know how to reset that counter. Why would you want to reset this? Aside from trying to misrepresent how much use your phone has had? Sorry, not trying to imply anything, but this sounds shady.
because my phone came with the problem of echo in the call, I was trying to change the store and did not exchange because the call time was longer than one hour
atylla11 said:
because my phone came with the problem of echo in the call, I was trying to change the store and did not exchange because the call time was longer than one hour
Click to expand...
Click to collapse
Echo on your end, or the other person's end? There is a couple fixes if the echo is on the other person's end. You can find them with a search. I'm mobile right now, so couldn't link if I wanted to. Per forum rule #1, please search before posting.
Sent from my GT-I9100 using XDA App
EDIT: Here's another post I did just yesterday about this same topic, linking to solutions to the echo problem. If you are not on wanam's ICS ROM, then ignore the last link, that is specific to that ROM.
Before posting the solution tested editing the phone.apk <bool name="has_in_call_noise_suppression"> false </ bool>. but only disables the option, the echo still, also saw the opening post to fix the phone and putting the speaker protection, can not do this because the phone still has warranty and is only 4 days of purchase, the other solution was http :/ / forum.xda-developers.com/showthread.php t = 1332137 I did not have to do for my rom is odexed and do not intend to change the rom because the phone is new, I'm looking for another solution.
atylla11 said:
Before posting the solution tested editing the phone.apk <bool name="has_in_call_noise_suppression"> false </ bool>. but only disables the option, the echo still, also saw the opening post to fix the phone and putting the speaker protection, can not do this because the phone still has warranty and is only 4 days of purchase, the other solution was http :/ / forum.xda-developers.com/showthread.php t = 1332137 I did not have to do for my rom is odexed and do not intend to change the rom because the phone is new, I'm looking for another solution.
Click to expand...
Click to collapse
#1, That "solution" (editing phone.apk <bool name="has_in_call_noise_suppression">false</ bool>) doesn't work, as you discovered.
#2, The other solution you mentioned (http://forum.xda-developers.com/showthread.php?t=1332137) does work, EXCEPT for the very first call after a reboot. Even if the phone.apk is deodexed, it doesn't matter if your ROM is odexed or not. If your ROM is odexed, just back up phone.apk and phone.odex to somewhere safe, then DELETE phone.odex, and replace phone.apk with the deodexed phone.apk.
However, like I said, the #2 solution will have NR turned on for the first call. So an imperfect solution at best.
ALSO, if you read my my links a bit more carefully, NEITHER of these solutions is mentioned. Please read my links a little more thoroughly.
And finally, I also had mentioned a HARDWARE solution, but you have to work up the nerve to actually crack open the case of your phone and do a bit of surgery. I've not actually gone to this length yet, as NR defaulted to off works for me just fine so far, but others have reported success doing this. You say you don't want to do this due to warranty purposes... but to do the other solutions, you need root, which also voids your warranty. Also, you said the store refused your return, so... I guess I'm confused. If you're concerned about warranty at this point, just bypass the store, and send it back to Samsung for warranty then.
ctomgee said:
#1, That "solution" (editing phone.apk <bool name="has_in_call_noise_suppression">false</ bool>) doesn't work, as you discovered.
#2, The other solution you mentioned (http://forum.xda-developers.com/showthread.php?t=1332137) does work, EXCEPT for the very first call after a reboot. Even if the phone.apk is deodexed, it doesn't matter if your ROM is odexed or not. If your ROM is odexed, just back up phone.apk and phone.odex to somewhere safe, then DELETE phone.odex, and replace phone.apk with the deodexed phone.apk.
However, like I said, the #2 solution will have NR turned on for the first call. So an imperfect solution at best.
ALSO, if you read my my links a bit more carefully, NEITHER of these solutions is mentioned. Please read my links a little more thoroughly.
And finally, I also had mentioned a HARDWARE solution, but you have to work up the nerve to actually crack open the case of your phone and do a bit of surgery. I've not actually gone to this length yet, as NR defaulted to off works for me just fine so far, but others have reported success doing this. You say you don't want to do this due to warranty purposes... but to do the other solutions, you need root, which also voids your warranty. Also, you said the store refused your return, so... I guess I'm confused. If you're concerned about warranty at this point, just bypass the store, and send it back to Samsung for warranty then.
Click to expand...
Click to collapse
You would send me the Phone.apk Phone.dodex edited? I tried to change mine, did not find .smali
atylla11 said:
You would send me the Phone.apk Phone.dodex edited? I tried to change mine, did not find .smali
Click to expand...
Click to collapse
You're clearly not reading my links above. The solution I linked does NOT involve editing a .smali file. Please try reading again. Follow my link in post 9, that will lead you to another post; look at the first link in THAT post.
Besides, you haven't even told me what version you're on. My phone.apk and/or phone.odex may well not work on your phone.
Sent from my GT-I9100 using XDA App
ctomgee said:
You're clearly not reading my links above. The solution I linked does NOT involve editing a .smali file. Please try reading again. Follow my link in post 9, that will lead you to another post; look at the first link in THAT post.
Besides, you haven't even told me what version you're on. My phone.apk and/or phone.odex may well not work on your phone.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
If this is the solution could not find this sequence 2F 32 84 00 12 13
For Odex ROMs:
Download the file Phone.odex
Open in hex editor
Search for the bytes: 32 84 00 12 13 2F (Should there be only one match)
Change the last byte to 03
Save and upload to Phone.odex / system / app
reboot
Friend use a translator so sometimes it is not clear to me what you say I am posting my files to you try to edit.
http://www.4shared.com/rar/tCgBNMdy/s2_online.html
My rom GT-I9100_ZTO_I9100UHKI1_I9100UHKI1_I9100ZTOKI1 Android 2.3.4
atylla11 said:
If this is the solution could not find this sequence 2F 32 84 00 12 13
For Odex ROMs:
Download the file Phone.odex
Open in hex editor
Search for the bytes: 32 84 00 12 13 2F (Should there be only one match)
Change the last byte to 03
Save and upload to Phone.odex / system / app
reboot
Friend use a translator so sometimes it is not clear to me what you say I am posting my files to you try to edit.
http://www.4shared.com/rar/tCgBNMdy/s2_online.html
My rom GT-I9100_ZTO_I9100UHKI1_I9100UHKI1_I9100ZTOKI1 Android 2.3.4
Click to expand...
Click to collapse
You have to use a hex editor, and you have to search for the string as hex, not as text.
ctomgee said:
You have to use a hex editor, and you have to search for the string as hex, not as text.
Click to expand...
Click to collapse
I did not find it anymore, I think it must be due to rom.
atylla11 said:
I did not find it anymore, I think it must be due to rom.
Click to expand...
Click to collapse
Huh. I just downloaded your files and looked, I can't find it either.
What ROM are you on, and what phone model do you have??
ctomgee said:
Huh. I just downloaded your files and looked, I can't find it either.
What ROM are you on, and what phone model do you have??
Click to expand...
Click to collapse
Samsung Galaxy s2
atylla11 said:
Samsung Galaxy s2
Click to expand...
Click to collapse
I meant specific model. There are about a dozen different phone models, all marketed as the Samsung Galaxy S2.
But I see above in an earlier post you already gave this information as "GT-I9100_ZTO_I9100UHKI1_I9100UHKI1_I9100ZTOKI1". Did the phone come with this, or did you install it after you got it? I'm guessing you installed it? ZTO means you're in Brazil, I think?
So I don't know what to tell you. I guess the phone.apk and odex are different for that version of firmware.
ctomgee said:
I meant specific model. There are about a dozen different phone models, all marketed as the Samsung Galaxy S2.
But I see above in an earlier post you already gave this information as "GT-I9100_ZTO_I9100UHKI1_I9100UHKI1_I9100ZTOKI1". Did the phone come with this, or did you install it after you got it? I'm guessing you installed it? ZTO means you're in Brazil, I think?
So I don't know what to tell you. I guess the phone.apk and odex are different for that version of firmware.
Click to expand...
Click to collapse
This is the original firmware of the phone, I'm in Brazil. what could I do?
Sorry if wrongly posted but I need some help,
Today I lost my WhatsApp chat history somehow and I am trying to restore it, did all the tricks I could find.... but no success.
My wife died the 22th of April and I really want her msgs back :crying:
I Have no Key file (searched for it but can't find it
Tried xTract butcouldn't open my files
Tried a bunch of websites...
I got one msgstore.db.crypt file
7 msgstore.db.crypt7 files with dates (the last 7 backups I guess)
1 msgstore.db.crypt7 file
1 msgstore.db.crypt5 file
Who can help me out ?
Sorry to hear about your wife passing. I can't even imagine...
I'm not really familiar with Whatsapp but thought I'd give a crack at getting to help nevertheless. So, to get your key, you have to be rooted. But it seems like this
http://forum.xda-developers.com/showthread.php?t=2689911
might have a lot of useful info on how to decrypt them and I'm sure someone there knows how to get the key too.
Thnx, I tried the web-version from WhatsCrypt but liked said I am unable to get a keyfile.... it's not in the folders, tried the App version now too... it decrypts a DB but also unable to get a Keyfile (file isnt there)
I will not give up tho
*edit* Saw you are running a rom, so am assuming you are rooted. Duh...
But I see you posted over on that thread. They would obviously know more about it than I would. I wish you well!
I dunno if this might help at all:
https://play.google.com/store/apps/details?id=com.tricrypt
And I guess you should be able to find your key in the /data/data folder for Whatsapp.
I've tried all those tools but did not got any msg back, there is no keyfile located in that folder I've checked like a thousands of times.
Well, guess I need to write support
Ok. So here's the deal:
My SGS3 I9300 exynos phone did the famous IMEI 0049 and SN null trick.
I cannot say what precipitated it but is simply stopped registering on the network, so no calling or data. All other functions operational.
After much searching and reading, I settled on flashing the stock 4.3 back. This succeeded only in doing absolutely nothing to alleviate this issue. I wiped the entire phone. Maybe I missed a critical section wipe, but since the stock ROM overwrites all? the CSC/BL/MODEM functions I thought it would set the default for EFS (which I believe is where these critical data live). I'm not a programmer so I cannot say diddly about the architecture and interrelationship of OS files, but I am technical and I know how SW and HW does what it does.
This phone is my own and I have all the rights to it.
I had loaded RRemix ROM a loong while ago and it was functioning fine. Probably a corruption of the EFS due to battery contact being loose. This is in my mind the most likely cause as the system may be accessing the EFS files, say making a call, or accessing data, and the power drops out and voila! Corruption. But again this is theoretical.
Needless to say I tried the usual hocus-pocus out there with no avail.
Getting to understand the system better it seems obvious that these critical identification numbers are hard-coded into the chips on the phone. Which explains the ability to 'fix' them with JTAG and other cable/box solutions and SW. However, I cannot see how the SW loses the ability to read the IMEI/SN that is hard-coded (fused?) into the main-board.
All my research pointed to the EFS files having something to do with this.
Way back when I loaded the custom ROM I did not come across the 'backup your EFS' as a necessary step, so I had nothing to go back on.
And loading the stock 4.3 ROM back on and not having that fix the issue, led me to believe something else was up.
Somewhere in the guts of this phone something is screwing up the layer between reading the registers where the numbers sit and the software layer that reports the numbers.
So, much searching led to the nv_data.bin file being a key component in all this fiasco.
Now, before I say any more, I believe that describing the next steps could be a big no-no here.
Now, understand, all I want to do is get MY personal device working again. I have the SN and IMEI numbers on the physical device.
Sure, I could have stolen it and am attempting to change these to avoid prosecution. Anyone can say anything online.
Therefore, before I can proceed, I need advice from moderators and VPP to either say 'Yes you may post this info' or 'No. Go away'.
Am I allowed to do the following:
1) Describe how I restored my IMEI (Not changed, overwritten, or subverted to my limited knowledge)
2) In the case of 1 not allowed, post the link to where I found the info to achieve this.
3) Submit the 'fix' to a moderator or developer to check whether this is indeed and restoration or a change.
If it's a restoration of existing functionality, I cannot see how this could be a problem. If its changing something, then it's a whole other sack of ferrets.
My reasons for posting are that xdadevelopers has given me years of joy with my SG devices. (Yes, I have the whole range exclusively) Many ROMS, customs, fixes, hints and saves deserves something back, and the difficulty in achieving this particular fix, warrants it.
But I don't want to break any rules, this being my first post.
So, please let me know what I can do to help others stuck in this position...
You can find it if you have the correct search parameters. Perhaps I can say that instead?
Thanks.
And thanks to all who have helped over the years.
T
[Edit] Just to clarify, the solution requires no special HW or 'boxes'. You do need root, however, and a hex editor. I had a reply explaining the use of Octoplus, which requires credits and registration. You will need none of those.
I can't speak English but I will try.
1- flash stock firmware.
2- root your device s3 .
3-in the web download " octuplus crack box"
4-in youtube see how install " octuplus crack"
5- before install stop your antivirus PC
6- open octuplus and connecte your phone with PC
7- chose your device i9300 .
8 click repair imie
9 click read info and do what OCTU said to do.
10- click repair or write the true imie in your device ( remove battery to see)and click repair.
11- restart phone .
12- see: call work fine
13- in phone go to mobile network\ access point names\ apn's
14- write your network.
TrinityTrip54 said:
Ok. So here's the deal:
Repair is ok Change or Modding is now:good::good::good:
Click to expand...
Click to collapse
How to restore corrupted or null 0049 IMEI on SGS3.
Right.
Thanks to the moderators for agreeing to let me share the solution. :good:
Thanks to the reddit poster who found this solution. I don't know how the hell you figured this out, but big-ups to you. For privacy I will not mention names or addresses.
You do need a rooted phone and I cannot assist anyone without root as I have not tried it.
Whether this only works to restore a corrupt IMEI or change it, I cannot say, but it managed to restore my existing one.
Preparation: Get your IMEI number from under your battery compartment. Say your IMEI no. is: 123456789101213, write/type it in the following fashion: 1 23 45 67 89 10 12 13
Now some funky transposition: Excluding the first number, transpose the subsequent pairs of numbers so that you have: 1 32 54 76 98 01 21 31. Can you see it? Swap 23 to get 32. 45 to get 54 and so on.
Now add 08 to the beginning and add A after the 1 so that the completed number is: 08 1A 32 54 76 98 01 21 31
Now you will need:
Rooted Galaxy S3 (This may work for all android devices that have an EFS folder. If anyone can confirm that would help others.)
Hex editor (PC based or Android app) - PC is faster and easier. I used hex workshop trial version but I'm sure any editor will do. I used the default install configuration.
USB Data cable (if using PC editor mentioned above)
You should probably back up the EFS folder entirely, just to be sure.
Using your favorite root explorer browse to root/EFS folder and copy the nv_data.bin file to an accessible area in sdcard. I use a /sdcard/Downloads folder.
Either open the file with your hex editor app or transfer the file to PC where you can open it with your hex editor program.
Open the file and jump to address 00550.
Now, get your modified IMEI number from the prep steps above and enter the values in the ASCII TEXT window to the right, NOT the HEX values window to the left. This may be different for other editors but hex workshop works like this.
Double check your address and entered data. When satisfied, save the file and transfer back to the phone if copied to PC.
Now, place the phone in Airplane mode, turning off the cell radios.
Go to the EFS folder and rename the original nv_data.bin file to something else. I used nv_databak.bin.
Copy the modified nv-data file into the EFS folder.
Turn off Airplane mode and do a full reboot.
Your IMEI number should be restored and cellular functions should work.
My previously garbled serial number was also restored.
I hope this works for you. I have no knowledge of any other method as I did not delve further into trying other numbers or such. I can't assist any more other than further clarifying the steps above if you don't understand something.
If anyone can decipher what is going on here, I would love to hear about it. I suspect something between the HW and SW layers is getting garbled or corrupted and this kick starts the process to get the correct data again.
Maybe.
May also contain nuts.
Hastalavista.
T
THANKS FOR POSTING THIS HERE!
I have this Samsung Galaxy S3 that I bricked 4 years ago and never wanted to sell it or even try to give it away. I searched for months for a frekin solution to this problem. Yesterday night i decided i wanted to try and install custom roms on it and so i wanted to give another shot at this stupid issue i had with the lost IMEI before doing so...and BAM! Today it's fixed!
I'm so thankfull I wanted to post here so that you know that you helped at least one person with this
Thanks a bunch!
@TrinityTrip54
Hi,
can you confirm that this is a permantent solution and remains when flashing new (custom) ROMs? Or is it just for the current installed ROM?
And I am having an issue with "jump to address 00550" in Hex Workshop. There is no address like this, just 540 and the next one is already 558. When inserting 00550 in the goto search field of Hex Workshop it jumps to 210. Any idea?
thanks anyway.
bert
Background information:
Ever since Android Nougat roms came out, google started using the sim card to set the WiFi region code on the device, and for some countries, this completely breaks the WiFi functionality, some details about the subject here : WiFi_regional_problem_on_Android.
This was possible to fix on Nougat by following this tutorial : WiFi Country Problem Solving for AOSP, MIUI & others , but when Oreo roms started coming out, they we odexed out of the box, which meant to actually apply this fix you needed to deodex the rom and then apply the fix, a bit of headache.
Once Xposed became available for Nougat & Oreo, an xposed module was created that fixed the issue and allowed us to use WiFi normally : Wifi region fix
Recently, Pie based roms started showing up for the Z2, and with them came back the same WiFi issue, and while there's a sort of working Xposed solution, EDxposed, it works through magisk and atm does not support resources hooking, which means the xposed module can't work it's magic.
Solutions and Status:
I've been trying to find a fix for this, and I have followed various guides on the internet, but they don't seem to work.
First of all I've deodexed the /framewrok folder using TOAD (The open-source Android Deodexer), then have followed these suggested fixes.
Method 01 (Failed)
WiFi Country Problem Solving for AOSP, MIUI & others
Method 02 (Failed)
WiFi region fix for android N & O
These 2 methods required modifying the telephony-common.jar file
Method 03 (Failed)
wifi country code fix requires root
This method modifies the wifi-services.jar , which is the same way the xposed module works, so I'm hoping to focus on it, another method that uses the same method is on another forum, but basically offers the same directions MIUI wifi region fix
My problem with these 2 methods is the config files they show seem to use ".registers" command, while the files to modify for our Z2 use the ".locals" command, and from what I can see both define the number of variables we can use inside the ".method" with a slight difference, for example a ".registers 3" will allow you to use 4 total variables, like v0, v1, p0, p1, while ".locals 3" will allow you to use 4 of each variable, like v0, v1, v2, v3 and p0, p1, p2, p3. This is my personal observation, since I wasn't able to find any specific info on this matter using google.
Update: it seems this is related to how I was decompiling the jar file, if I used apktool with the -d switch, I get the files using the ".locals" version, but if I decompile using "BatchApkTool" i get the files using the ".registers" version, although making changes and recompiling/decompiling reflects the results in different ".registers" & ".locals" changes.
But there's still another difference, in those guides they show :
Code:
.method public setCountryCode(Ljava/lang/String;Z)V
.registers 9
const-string[COLOR="Blue"]/jumbo[/COLOR] v2, "WifiService"
and the fix is to add another line after that :
Code:
const-string[COLOR="blue"]/jumbo[/COLOR] v6, "US"
I'm not sure what is the /jumbo thing is, but it doesn't exist in our version of that file, in the Z2 file we have:
Code:
.method public setCountryCode(Ljava/lang/String;)V
.registers 5
.line 2174
const-string v0, "WifiService"
and my change was:
Code:
.method public setCountryCode(Ljava/lang/String;)V
.registers 6
.line 2174
const-string v0, "WifiService"
const-string v3, "US"
flashed the resulting file, but it's still not working, I really feel I'm close but still somehow doing something wrong, so any insights/guidance/help would be Very Much appreciated.
Update:
Working with wifi-service.jar didn't give any results, tried multiple modifications but once WiFi was gone, that was it, even airplane mode didn't allow me to see any networks, so I went back to work on telephony-common.jar , and there seems to be some progress.
Right now, if I use the modified version, put the phone in airplane mode and reboot, I'll have WiFi working as long as the phone remains in airplane mode, once airplane mode is disabled and the phone detects the sim, WiFi will stop working until I activate airplane mode again AND reboot.
I'll do more testing tomorrow, that's it for tonight.
Updates:
i'm currently stuck at the airplane mode & reboot point, which is achieved by doing the following changes in the MccTable.smali file inside telephony-common.jar :
.line 199
:cond_1
goto :goto_0
then comment out line 225
I feel I need to do something about the following part
.method private static setWifiCountryCodeFromMcc(Landroid/content/Context;I)V
in one thread it is suggested to change .locals 3 to .locals 13, but this is a useless change as it simply increases the number of variables the can be used and is not related to the "local" of the rom.
Maybe this will help you out. I'm using this to access 5GHz networks on Oreo/Pie
Yoxxel said:
Maybe this will help you out. I'm using this to access 5GHz networks on Oreo/Pie
Click to expand...
Click to collapse
Sorry for the late reply, and thanks for your suggestion, but it doesn't work.
Originally we could disable the auto region function by modding the code, but now even removing the entire method isn't enough, it seems there's something new to find out and learn, then we can stop this feature
Made a post here let's see if it gains any traction with the Ed Xposed people
ali6944 said:
Made a post here let's see if it gains any traction with the Ed Xposed people
Click to expand...
Click to collapse
Of EdXposed gets the resources hook function then it'll work, until then no.
Hi Guys, ANY recent update on the wifi regional problem in the Android pie?
So uh, this guy on the AOSP Extended thread posted this https://forum.xda-developers.com/showpost.php?p=79245747&postcount=157
just tried it with the same rom, it works just fine.
ali6944 said:
So uh, this guy on the AOSP Extended thread posted this https://forum.xda-developers.com/showpost.php?p=79245747&postcount=157
just tried it with the same rom, it works just fine.
Click to expand...
Click to collapse
I tried it, and it doesn't work for me, can you provide more details, like your device model?
I'm looking for the WiFi region fix, not 5ghz fix, is this the same for you?
ticktock666 said:
I tried it, and it doesn't work for me, can you provide more details, like your device model?
I'm looking for the WiFi region fix, not 5ghz fix, is this the same for you?
Click to expand...
Click to collapse
Yes, we're both looking to solve the same problem, from my understanding of the module thread, it sets your wifi code based on your device language, mine was US English, when i installed the module through magisk the last line of the output was (your wifi country code is set to US), the rebooted and it was working fine.
you might want to mess around with your device language and give it a try
i'm using a D6503 btw
ali6944 said:
Yes, we're both looking to solve the same problem, from my understanding of the module thread, it sets your wifi code based on your device language, mine was US English, when i installed the module through magisk the last line of the output was (your wifi country code is set to US), the rebooted and it was working fine.
you might want to mess around with your device language and give it a try
i'm using a D6503 btw
Click to expand...
Click to collapse
From what I was told by someone who understands code better than myself, this module modifies the /system/vendor/bcmdhd.cal and sets the ccode inside it from the ROM local, for example I was using great Britain English, so it was at to GB, but it didn't work. I've tried changing the code manually, but nothing I tried worked for now.
Someone in the extended aosp thread also reported the issue being fixed without using anything, so I'm downloading it to test, as I've been testing using the carbon ROM beta.
ticktock666 said:
From what I was told by someone who understands code better than myself, this module modifies the /system/vendor/bcmdhd.cal and sets the ccode inside it from the ROM local, for example I was using great Britain English, so it was at to GB, but it didn't work. I've tried changing the code manually, but nothing I tried worked for now.
Someone in the extended aosp thread also reported the issue being fixed without using anything, so I'm downloading it to test, as I've been testing using the carbon ROM beta.
Click to expand...
Click to collapse
Interesting, I'm back on CR oreo now and I wanted to check if it works on it so I can finally uninstall xposed, but it did not, i still remember booting AOSP Ex without magisk while flashing it for the first time after finding out about the module and having no wifi till after I flashed it. Let me know what you find!
ticktock666 said:
From what I was told by someone who understands code better than myself, this module modifies the /system/vendor/bcmdhd.cal and sets the ccode inside it from the ROM local, for example I was using great Britain English, so it was at to GB, but it didn't work. I've tried changing the code manually, but nothing I tried worked for now.
Someone in the extended aosp thread also reported the issue being fixed without using anything, so I'm downloading it to test, as I've been testing using the carbon ROM beta.
Click to expand...
Click to collapse
I wrote that script, but to be honest I didn't test it for every language.
Are you sure the module did output "Your ccode has been set to GB" ?
AFAIK Great Britain should be UK, not GB.
You could try to edit bcmdhd.cal manually and set CODE="UK" , save and reboot.
marcogiannetta said:
I wrote that script, but to be honest I didn't test it for every language.
Are you sure the module did output "Your ccode has been set to GB" ?
AFAIK Great Britain should be UK, not GB.
You could try to edit bcmdhd.cal manually and set CODE="UK" , save and reboot.
Click to expand...
Click to collapse
Yes the output was GB, and I checked the file too, it wasn't UK.
Somehow this issue is fixed in the latest aosp extended build, so I'm hoping the Dev will share his fix with us, and then maybe we'll be able to come up with a universal fix method that can be applied to any ROM.
ticktock666 said:
Yes the output was GB, and I checked the file too, it wasn't UK.
Somehow this issue is fixed in the latest aosp extended build, so I'm hoping the Dev will share his fix with us, and then maybe we'll be able to come up with a universal fix method that can be applied to any ROM.
Click to expand...
Click to collapse
I tried that magisk module on android pie cr7 (Xperia z3) and it changed the ccode to US, It didn't work for me (My phone language is English (United state)). You said that this issue was fixed on a custom ROM that you Installed. Can you upload your bcmdhd.cal file (in \system\vendor\firmware folder) to see the difference between yours and mine? maybe we can figured it out what causes this issue.
Tnx
Maxine76 said:
I tried that magisk module on android pie cr7 (Xperia z3) and it changed the ccode to US, It didn't work for me (My phone language is English (United state)). You said that this issue was fixed on a custom ROM that you Installed. Can you upload your bcmdhd.cal file (in \system\vendor\firmware folder) to see the difference between yours and mine? maybe we can figured it out what causes this issue.
Tnx
Click to expand...
Click to collapse
I saw your post in the aosp ex thread, but I'll share what info I have with you:
The region setting is something Google is doing even if the device has no SIM card in it, just getting the "emergency calls only" signal is enough to break WiFi.
I was getting help from @Darkonizer who builds and maintains the pie carbon ROM, and the best results we could get was this, you'll need to switch airplane mode on, enable WiFi, then switch airplane mode off. You'll have to do this every time you turn your WiFi off, it's not ideal, but you don't have to set the entire ROM region to US.
ticktock666 said:
I saw your post in the aosp ex thread, but I'll share what info I have with you:
The region setting is something Google is doing even if the device has no SIM card in it, just getting the "emergency calls only" signal is enough to break WiFi.
I was getting help from @Darkonizer who builds and maintains the pie carbon ROM, and the best results we could get was this, you'll need to switch airplane mode on, enable WiFi, then switch airplane mode off. You'll have to do this every time you turn your WiFi off, it's not ideal, but you don't have to set the entire ROM region to US.
Click to expand...
Click to collapse
Thanks. I know that method but it's kinda annoying to do that every time when wifi is turned off. I decided if the contributer of cr7.0 doesn't decompile that framework.jar , I'll do that by myself.
Is there any success with regional wifi issue? Is there any definite fix?
did it work @ali6944 ?
pls tell me it worked
Bro_toyota said:
did it work @ali6944 ?
pls tell me it worked
Click to expand...
Click to collapse
It unfortunately didn't work and I stopped looking into it after AEX Pie was stable enough for daily use, as the developer implemented a fix into the rom itself.