I think this question has not been answered, or it's my lack of searching skills.
Anyway, I have two HD2 phones(both running android) and use Wi-Fi all the time when I'm home.
The problem is that they have the same Mac address, so I can't use them simultaneously.
I tried flashing different roms, different android builds, but nothing seems to work.
Is there any way I can fix this problem?
Thank you in advance.
1.
Tmous HD2
WM: Miri_HD2_WM65X_23139_Sense25_V23.0_WithSwype
Android: FroyoStone Sense V3.1
MAC Address: 00 90 4c c5 00 34
2.
Tmous HD2
WM: CleanEx Core 3.5
Android: phireMOD_SkinnyEVO_v1.3
MAC Address: 00 90 4c c5 00 34
there should be no way at all for both of your devices to have the same mac address.
"00 90 4c c5 00 34" <--do you see this in windows or in android?
the thing is, last i checked, ALL android builds for the HD2 so far are UNABLE to use your device's ACTUAL mac address. instead, the developers have hardcoded a mac address into the HD2 android kernel(s) currently available. the android build i'm using hardcodes "00 11 22 33 44 55" as the mac address even though my device's ACTUAL mac address is much different (when viewed in windows).
i vaguely remember reading somewhere that this is one of the few "to dos" remaining for the developers...keep your fingers crossed, it might all be fixed soon.
finally, to verify, i suggest booting BOTH of your HD2s into windows and then make sure there is no mac address conflict. if so, then there is something really really fishy going on. if the problem occurs only when both HD2s are running android, then the above mentioned theory is probably in effect.
Thanks.
I used wifi on the stock rom with no problems.
Maybe I should try one with "00 11 22 33 44 55" and see if what happens.
Related
Hi,
I'm developing an application on SmartPhone SDK 2003.
I need to extract the cell ID from telephone.
How can I do?
If you have any suggetion, I'll be happy.
Thank you.
Bye
Andrea,
You might want to check out http://www.cell-profiler.de/
Maybe the developer would point you in the right direction
Regards
Keith Burke
I feel the XDA (I&II) badly need network monitoring software
Indeed
thanks, but the site is under costruction.
I don't have to buy but i've to deploy the software for my thesis.
I've downloaded from the site http://viewcvs.xda-developers.com/cgi-bin/viewcvs.cgi/xdautils/#dirlist the following class: debug.cpp, debug.h, ril.h, riltest.cpp, riltest.h, stringutils.h, stringutils.cpp, vectorutils.h, vectorutils.cpp.
I've create a new project and build it.
But RIL_GetCellTowerInfo response:
RIL_GetCellTowerInfo: 80004001
RES: 00000001 000000a6 10 00 00 00 03 00 00 00 02 00 00 00 02 00 00 00
RES: 00000001 000000a7 :shock:
I think that 80004001 (hexadecimal) mean that it don't work (not implemented)
I have no more idea how to do this. Could anyone to help me?
Thanks
Andrea,
Yes the site is under constuction, but their support email address is on that page.
He [dutty] also frequents this forum semi regularly. Maybe if you post a message for him, or even PM him. He's generally an approachable guy, he may help you.
Check topic
http://forum.xda-developers.com/viewtopic.php?t=8200&highlight=dutty
I haven't dabbled in the RIL myself, so can [EDIT : Should read "can't"] help you there, sorry. But you are developing for the XDA / XDA II, I take it. Not sure but I think the RIL applies to XDA and the like.
Thanks, but i'm developing on SmartPhone 2003 platform in eVC 4.0
It's possible that nobody know RIL for smartphone??? :?
for the xda2 you can get the cellid via a device specific API, 'RIL_DevSpecific, see RilClass.cpp
it is quite likely different for your smartphone.
to see if your device supports cell info notifications, you have to see if the string '+CREG=2' is somewhere in your rilgsm.dll.
you can extract rilgsm.dll from your rom using dumprom
Excuse me,
I don't understand how to use dumprom on smartphone!!!
Can you help me?
Thanks
I´m looking for a way to read cell ids for some weeks now and didn´t find anything valuable. Some working programs, but theyre all closed source...
I´m working with basic4ppc on win mobile 6. If there are any advances, PLEEAASE let me know ^^
Does at least, any program work?
Have you tried http://usuc.dyndns.org/tv/gsm/GSMCelluloz/ ?
Does it help ?
If you have problem, try the debug version and send me file files created in \Temp.
I may help if you have problem, but I don't do any basic4PPC...
Hello, readers.
I am about to receive a MT6577-based phone. My religion prohibits me from using windows :silly: and I am using Linux since good old 1993,
I have done a lot of reading during the past months. I have installed the Android SDK, and thus I have adb up and running and I believe
I won't have problem in rooting the phone (which I must do as first thing). I have found a terminal application. I believe it will be
reasonably easy for me to find myself at home.
The only big gap I still have is on how to proceed about flashing updated/modified roms to the phone. There is a very informative thread
on china-iphone.ru about the specific phone I will get. It is in Russian, but thanks to Babelfish I was able to understand a lot. Most
important, I got hold of the latest official rom for the phone I will receive.
But then, how to proceed with flashing? all tutorials I found describe the windows way of transferring this file's
contents to the phone. Use is made of one of two tools that Mediatek apparently released. This is a no-no for me. I mean: Android is
Linux. I should not have to downgrade to windows to deal with my Linux phone! And then, I simply have no windows whatsoever here.
I see three possible ways for me to proceed:
Find an equivalent software that runs under Linux
Try to run one of Mediatek's softwares under Wine
Obtain from Mediatek, or elsewhere, the precise specs about the USB protocol being used, and implement my tool
Reverse-engineer the protocol
The first item is, I believe, a dead end. I think my search has been exhaustive enough.
The second one is a path I'd rather not tread.
The third one would be a nice project, but I perceive that Mediatek is a bit opaque when it comes to providing technical specifications.
The fourth one would very quickly come to a dead end, I believe, with a bricked device.
Any suggestion on the above, or on other possible ways?
Also: I have come across some very vague mentions about flashing this sort of devices from recovery mode.
From what I have gathered, you put the rom file on a SD card, and then enter recovery mode and let the phone do its own flashing.
This would be ideal for me, but I came across no mention about this mechanism on threads that are specific to this class of phone.
Do MT6577-based phones come with recovery mode? How is it used?
I would be thankful to anyone who could provide details on this aspect.
So far I have only flashed a custom recovery into my MTK6577 phone and I did it with dd.
The full ROM is exposed on /dev/block/mmcblk0.
Once you have rooted your phone you can use dd along with the info in the scater file (from windows tool) or from Memory/eMMC in the EngineerMode (at least in my phone).
Good Luck
P.S.: In my phone the recovery can be booted into from the phone info in Settings.
Or pressing volume up when turning on the phone and releasing volume up once it vibrates (if not it goes to factory mode that has a bunch of tests in it).
Or using adb reboot revovery
FrankVM said:
The full ROM is exposed on /dev/block/mmcblk0.
Once you have rooted your phone you can use dd along with the info in the scater file (from windows tool) or from Memory/eMMC in the EngineerMode (at least in my phone).
Click to expand...
Click to collapse
Thanks a lot.
Indeed, I had found out about using dd plus the info in the scatter file. At first I completed the task of loading a different recovery image, and that was sufficient at the moment. Later on, I spent another weekend on this: I started working on a Ruby script that, by interfacing with the phone via ADB, would dump and upload any partition, and possibly do the reverse, too. The upload part sort-of worked, and I was able to get hold of the current booting partition. What I wanted to do was to modify the boot script to let me run at boot a script resident on one of the sdcards.
I got to the point of unpacking the data in the gzipped/cpio-ed root fs archive, and certainly I would not have had problems modifying the script. But I was blocked when I tried to find the data about the format of ROOTFS. I mean: I could find the start of the compressed material, but I could not find exact reference about those few bytes that preceed it. Must those bytes change if the actual content changes?
I only have one phone, and I certainly do not want to brick it (or have to pour half-days of work into blind-man debugging mode...)
The block is 512 bytes long, filled with 0xff's except for (in my case)
00000000 88 16 88 58 │ 9F 94 08 00 │ 52 4F 4F 54 │ 46 53 00 00 │ 00 00 00 00 . X ..ROOTFS......
00000014 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 │ 00 00 00 00 ....................
and it seems quite clear that the only data that may change are the first 8 bytes - presumably 4 shorts, which in my case would have the values:
5768
22664
38047
8
When I find out what these numbers are, and when I have another free weekend, I may go on in my exploring path.
I looked into modifying boot/recovery images a few weeks back but haven’t gotten around to fiddling with mine.
The initial data is the uboot header, if I remember correctly. It does need to change.
There is a tool out there in perl that does all the required to unpack and repack the boot images for MTK65xx phones.
Here is forum page with the tool info: http://forum.xda-developers.com/showthread.php?t=1587411
my way to do it on ubuntu
well I basically did it on ubuntu, but it was actually virtual box windows under ubuntu so...whatever
This thread is from 2012... 3 years later in 2015 and not a single mtk flash tool was developed for linux... i bet using a windows based phone it will be easyer to find that kinda tool
Now there is a flash tool for Linux available, (look for needrom.com -> sp-flash-tool-v5-1424-00),but I can't get it to work. I suppose there is a vcom driver missing. Unfortunately my phone (UMI Hammer) does not support adb flash, otherwise I would be very happy to do it that way.
I think it took so long that a linux flash tool became available because MediaTek didn't share their code with developers. They changed their policy about a year ago, though.
I wrote a tutorial for setting up the SP_Flash_Tool_Linux
It works
I have problem when i try to unpack boot.img from CM10.1.3 Stable version for I9100G.
I tried many time but It say can't find kernel or ramdisk.
Any body help me please?
Anybody help me please???????????????????????
Very few people post here these days, not even the mods seem to be around. If you want help with this, you're either going to have to be really patient (understatement, don't be surprised if you still don't have an answer in a week), or go ask in the CM discussion thread. Your question isn't exactly a 'Hlap mai fone borked ! Odin don't werk !' type query. There aren't many people who post to S2 forums anymore who can answer this type of question.
So you can either sit in this thread & not get the answers you're looking for, or you can be proactive & seek them out.
I tried to worked out with few boot images before. I dont know what is yours
can you upload it please.
If you have windows it will be easy for you to explore that image in hex editor
That what i know so far is. Open your image in hex editor and look for "error" phrase
and you will find several of that 'error' kernel error header error compression error
im my case it is last one before compressed file. You need to recognize magic of
compressed file it is just after 'error'
Ex.
for gzip is: 1F 8B 0B
for LZMA is: 5D 00 00 00 04 FF FF
you can look for that instead 'error' And then you need to cut of everything before
magic number. Make your file start of that magic number. If you do that you will be able to
decompress it. gunzip file.gz or unlzma file.lzma
or you can use your android to find archive in your boot.img
hexdump -C boot.img | grep '1f 0b 08'
and result is
000046b0 72 6f 72 00 1f 8b 08 00 00 00 00 00 02 03 ac bd |ror.............|
ant then you have hex address 46b0 witch is pointing on first byte of that line. Its 72
hex is not easy to count in your memory so we need to convert it to dec value
echo $((16#46b0))
result is
18096 but remember this addres is pointing on 72. We need address of next 4 byte 1f
so we need to count in a memory then. Addres of 1f is 18100
Its easy now. We need to extract archive from boot.img
dd if=boot.img of=archive.gz bs=18100 skip=1
And then decompress it. Thats not all it is just a clue i hope it will work out for you
Hello everyone welcome to my little guide on how to change the mac address of the mi pad 4.
Code:
IM NOT RESPONSIBLE FOR ANYTHING YOU DO WITH YOUR DEVICE! U KNOW THE RISKS
I plan to release a app or at least binary in the next few days to speed up the process for u
Requirements:
- Root
- a hex editor
- a Mi Pad 4
MAKE A BACKUP OF THE PERSIST FOLDER BEFORE!!!
Open the Hex editor
Open the file /persist/wlan_mac.bin (obvious name xiaomi)
The layout of the file is as follows:
It contains 3 mac addresses - one primary and two for fallback(s)
The addresses are displayed in HEX - every hex digit represent two numbers of the mac address
a possible content would be:
20 a4 0f 5b 34 24 20 a4 0f 5c 34 24 20 a4 0f 5a 34 24
To change the actual address simply change like a few bytes of the first address
20 a4 0f 5b 34 24 -> 21 a2 ff 4b 24 34
and reboot the phone.
DO NOT ADD ANY DIGITS THE FILE HAS TO BE 24 BYTES BIG!!
Thats all but be careful with changing the digits not ALL possible combinations are allowed by routers!
Remember that HEX digits are: a-f and 0-9
Feel free to leave a reply or leave a thanks if i helped u.
EDIT: This unfortunately doesn't seem to work for Windows 11. It worked reliably under Windows 10 for me, but on Windows 11 it's back to needing a USB 2.0 hub. I'll update again if I figure out another fix, but in the meantime, this should still be good for at least Windows 10 users.
This really isn't specific to the Pixel as it also solves the same issue for many other phones, but as I've seen the issue widespread in ROM threads here I thought I'd share it here.
First of all, while it is highly recommended to use Google's USB driver, for many of us that doesn't solve the problem - I don't know why it works on some systems, but it doesn't on either of mine. Fastboot and sideload would either error out and reboot the phone, or get some small percentage in and then hang. What does work is a small registry tweak. On both my laptop and my PC, this has enabled using USB 3.0 (and 3.1, 3.2, including USB-C) connections for fastboot and sideload with no errors and at full speed, and with no apparent downside.
I'm attaching a ZIP containing a simple .reg file you can run to automatically apply the fix - if you have any concerns applying a .reg file to your Windows install, feel free to open it up in Notepad and verify that it only does as described in the "Manual method" spoiler below.
Spoiler: Manual method
In regedit, under Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags:
* Create a key (folder) named 18D1D00D0100 if it doesn't already exist
* In that key/folder, create three Binary Values (REG_DWORD) named osvc, SkipBOSDescriptorQuery, and SkipContainerIdQuery (that's an uppercase i as in ID)
* Set osvc to 00 00
* Set SkipBOSDescriptorQuery to 01 00 00 00
* Set SkipContainerIdQuery to 01 00 00 00
You may need to reboot before the changes take effect, after either applying the .reg file or following the manual instructions above.
I've not seen any problems from making these changes, myself, but reverting them if so desired is as simple as deleting the entire registry key (folder): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100
Think i ran into this exact issue trying to flash the latest OTA via pixel flasher. On windows 11, using USB 3,0 the phone was detected fine via Adb but vanished once it rebooted to fastboot. Luckily I had a Linux laptop laying around and did my flashing on that that device just fine. Will bookmsrk this and will try it the next time i need to update. Thanks!