Hi,
FYI. A list of all the AT commands the I9000 can handle.
AT&H
#, &A, &B, &C, &D, &E, &F, &H, &I, &K, &M, &R, &S, &V,
&W, &Y, A, B, E, H, I, L, M, O, P, Q, S0, S10, S12,
S19, S2, S3, S4, S5, S6, S7, S8, T, V, X, Z, \Q,
+BINP, +BLDN, +BRSF, +BVRA, +CACM, +CAEMLPP, +CALA,
+CALD, +CALM, +CAMM, +CAOC, +CBC, +CBST, +CCFC, +CCHC,
+CCHO, +CCID, +CCLK, +CCUG, +CCWA, +CCWE, +CEER, +CFUN,
+CGACT, +CGANS, +CGATT, +CGAUTO, +CGCLASS, +CGCMOD,
+CGDATA, +CGDCONT, +CGDSCONT, +CGED, +CGEQMIN, +CGEQNEG,
+CGEQREQ, +CGEREP, +CGLA, +CGMI, +CGMM, +CGMR, +CGPADDR,
+CGQMIN, +CGQREQ, +CGREG, +CGSMS, +CGSN, +CGTFT, +CHLD,
+CHUP, +CIMI, +CIND, +CLAC, +CLAN, +CLCC, +CLCK, +CLIP,
+CLIR, +CLVL, +CMEC, +CMEE, +CMER, +CMGC, +CMGD, +CMGF,
+CMGL, +CMGR, +CMGS, +CMGW, +CMMS, +CMOD, +CMSS, +CMUT,
+CMUX, +CNAP, +CNMA, +CNMI, +COLP, +COLR, +COPN, +COPS,
+CPAS, +CPIN, +CPLS, +CPMS, +CPOL, +CPUC, +CPWD, +CPWROFF,
+CR, +CRC, +CREG, +CRES, +CRLA, +CRLP, +CRSL, +CRSM,
+CSAS, +CSCA, +CSCB, +CSCS, +CSDH, +CSGT, +CSIM, +CSMP,
+CSMS, +CSQ, +CSSN, +CSTA, +CTFR, +C
+CUSD, +CUUS1, +FCLASS, +FDR, +FDT, +FKS, +FMR, +GCAP,
+GMI, +GMM, +GMR, +GSN, +ICF, +IFC, +IPR, +NREC, +SATE,
+SATR, +STKENV, +STKLBR, +STKPRO, +STKPROF, +STKTR,
+TRACE, +VGM, +VGR, +VGS, +VGT, +VTD, +VTS, +WS46, +XACT,
+XADDTRACE, +XALS, +XALSBLOCK, +XAPOXI, +XAPP, +XAUTOPLMNSEL,
+XBANDSEL, +XBARRPW, +XCALLREFUSE, +XCALLSTAT, +XCAOC,
+XCBS, +XCCBS, +XCEER, +XCELLINFO, +XCFC, +XCGCLASS,
+XCGEDPAGE, +XCHNSIM, +XCIND, +XCIPH, +XCONFIG, +XCOPS,
+XCOREDUMP, +XCRSM, +XCSIM, +XCSP, +XCSPAGING, +XCSSMS,
+XCTMDR, +XCTMS, +XDATACHANNEL, +XDEV, +XDEVICE, +XDIAG,
+XDNS, +XDRXSET, +XDTMF, +XEMC, +XEONS, +XETFT, +XGAUTH,
+XGCNTRD, +XGCNTSET, +XGENDATA, +XGPRSERRMAP, +XHANDSFREE,
+XHOMEZR, +XHSDUPA, +XIMS, +XL1SET, +XLCAPS, +XLGASSIST,
+XLGCPL, +XLGINFO, +XLGLOGLEV, +XLGMODE, +XLGNAV, +XLGNMEA,
+XLGNVRAM, +XLGPOS, +XLGTEST, +XLGTIME, +XLIN, +XLOG,
+XLOOPBACK, +XLQOS, +XLRMT, +XLRSUPL, +XLRTA, +XLRV,
+XLSR, +XLSRSTOP, +XMAGETBLOCK, +XMAGETKEY, +XMER, +XMULT
+XMUX, +XNMI, +XPIN, +XPINCNT, +XPOW, +XPPP, +XPROGRESS,
+XPWROFFDELAY, +XQNEG, +XRAT, +XREDIAL, +XREG, +XREL,
+XREMFPLMN, +XRFS, +XRLCSET, +XRRSET, +XSCELLLOCK, +XSECSTATE,
+XSELFRXSTAT, +XSERVICE, +XSIMCHG, +XSIMLG, +XSIMLOOPBACK,
+XSIMSTATE, +XSIMVALID, +XSIO, +XSLN, +XSMS, +XSTK,
+XSYSERR, +XTDEV, +XTERM, +XTESM, +XTFILTER, +XTOS,
+XTRACECONFIG, +XTRACEIP, +XTRACESYSTIME, +XUICC, +XUSBFLASH,
+XVTS
OK
I9000 modem access
I'm trying to access /dev/ttygs0 and test an AT command
with all possible serial speeds directly from a root console , but
modem seems dead... i cannot find informations how to enable it
Hi guys,
I have following problem with I9000 - when new SMS arrives there is no notification to serial port.
With command AT+CNMI=2,3,0,1,0 there should be such notifications, but they don't arrive to the serial port.
Can you advice me someting?
For people who have asked me.
I accessed the AT commands by putting the I9000 phone PDA/MODEM setting on MODEM and then connect a USB cable. The phone causes new COM/tty ports to appear on the PC when running Linux.
sending AT commands to my Galaxy S
Hi there,
Im trying to access my My Galaxy S (Android 2.3.4 XXJVQ) as a GSM modem and send it AT commands.
Im using Windows 7, I cant seem to get this to work, whether through a cable or Bluetooth i can see in the phone in devices & printers dialog and it does list its modem as a feature and tells me on which port its connected, for USB its COM4 for BT its COM6.
However if i use Hyperterminal it wont let me type anything into the textbox, it just doesnt respond.
I also wrote a small C# app based on code samples i found online but it never seems to respond to the commands i send to it. If i use COM3 for my "Thinkpad Modem Adapter" and i type into my console app: "AT" or "AT+GMM" for example i get a response back. if i use the port for the phone (COM4) i get nothing back...
I tried the trick with setting the phone from PDA to Modem using *#7284# but then when i connect the phone to the PC it wont recognize it and in the device manager it shows me a device called 7CDCs which it cannot find a driver for.
Ive also tried PDANet, i got the computer and phone connected together but i still cant issue an AT command at the modem...
Not sure whats the problem here...
If anyone can help me with id really appreciate it.
thanks!
Yoav.
You need linux to make it work.
You might be able to find a windows driver for it, but i don't have windows so i can't help there.
Can't test this just now as I'm at work, I did get through to the modem on windows 7 via usb. I'm sure I had to issue a reset command before I could do anything else.... ATZ maybe? I'll check it out when I get home.
Yeah, with the phone in Kies mode for usb connection and using PuTTY instead of hyperterminal (no longer provided with Win7) I got through to the modem on COM3. Whether the phone responds to all commands as expected seems to be another matter.
Thanks fahzat,
Ill give it a try again with Putty but i did try Putty yesterday as well as Hyperterminal and got to the same situation where it seems to be connected to the phone over the port but then it wont allow me to type anything into the command prompt... You chose the "Serial" type connection in the Putty initial screen right?
Correct, serial connection on COM3 (obviously your port may differ) with speed at 921600 (9600 seemed to work too). In the "Terminal" section set "Local echo" to "Force on" or you won't see what you're typing, only the response.
fahzat said:
Correct, serial connection on COM3 (obviously your port may differ) with speed at 921600 (9600 seemed to work too). In the "Terminal" section set "Local echo" to "Force on" or you won't see what you're typing, only the response.
Click to expand...
Click to collapse
Or make the first command you type ATE1
Thanks guys, it works. now im able to send commands to my Galaxy S.
What i really wanted to do was to manage to send SMS messages and see incoming messages but following the commands shown on a few tutorials dont seem to work with my phone.
Wondering if anyone knows how to do that with the SGS (I9000)???
[EDIT]
All info moved to here: http://forum.xda-developers.com/showthread.php?t=1471241
Thanks.
Achieve AT Command from Android
Hi All
I read that is not possible use directly in Android AT Command to debug the modem, but I was thinking to write an APP that using the USB Serial Virtual port in Android could send the AT Command directly to the modem. I read about external API to use serial communication.
Do you think this is possible??
alextreme said:
I read that is not possible use directly in Android AT Command to debug the modem,
Click to expand...
Click to collapse
ATdebug.apk is the answer : http://forum.xda-developers.com/showpost.php?p=19485757&postcount=1
mai77 said:
ATdebug.apk is the answer : http://forum.xda-developers.com/showpost.php?p=19485757&postcount=1
Click to expand...
Click to collapse
I know this...but it s not working with Samsung phones. Should I change the ROM with a Cyanogenmod version??
All you need to know here:
How to talk to the Modem with AT commands:
http://forum.xda-developers.com/showthread.php?t=1471241
how can we put the phone in modem mode?
thanks in advance
midas5 said:
For people who have asked me.
I accessed the AT commands by putting the I9000 phone PDA/MODEM setting on MODEM and then connect a USB cable. The phone causes new COM/tty ports to appear on the PC when running Linux.
Click to expand...
Click to collapse
Hi Midas5,
Could you be more specific?
a) So you set it to use: UART as MODEM and USB as MODEM??
(Those PhoneUtils settings are confusing!)
b) Which exact devices/ports appeared on your local machine?
c) Which exact devices/ports appeared on your phone?
d) Can you say anything about the device driver that you're using?
Thanks.
---------- Post added at 07:20 PM ---------- Previous post was at 07:14 PM ----------
yoavniran said:
If i use COM3 for my "Thinkpad Modem Adapter" and i type into my console app: "AT" or "AT+GMM" for example i get a response back. if i use the port for the phone (COM4) i get nothing back...
Click to expand...
Click to collapse
This is probably the wrong modem. It's most likely your laptop's built-in FAX/modem!
I tried the trick with setting the phone from PDA to Modem using *#7284# but then when i connect the phone to the PC it wont recognize it and in the device manager it shows me a device called 7CDCs which it cannot find a driver for.
Click to expand...
Click to collapse
This is THE problem!!
a) What (PC/linux) drivers to use when using your phone in "modem mode"?
b) How to send AT command from your phone terminal/shell? (I.e. what device is the right one(s)?
Hi, i was happen to wander around the forum to find a method to root my HD 8 2017, and seems that my tablet has automatically update to the point where root is not possible (the current version was 5.6.4.0 build 636559820), therefore i tried to downgrade to 5.6.0.1,since the root method only covers the 636558520 build version, and after using adb sideload, i found out that the device has been totally bricked and can't be turned on, after a few googling. i've found the post about debricking, but requires me to short the TP28 circuit (which i don't know where it was after removing the cover), so i use amonet and it still didn't work, please help!!
--- and here is the log of the terminal:
[email protected]:~/Downloads/amonet$ sudo ./bootrom-step.sh
[2019-11-04 14:00:27.420553] Waiting for bootrom
[2019-11-04 14:00:43.250282] Found port = /dev/ttyACM0
[2019-11-04 14:00:43.287246] Handshake
* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 256, in <module>
main()
File "main.py", line 129, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/lubuntu/Downloads/amonet/modules/load_payload.py", line 123, in load_payload
dev.write32(0x10007008, 0x1971) # low-level watchdog kick
File "/home/lubuntu/Downloads/amonet/modules/common.py", line 163, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/lubuntu/Downloads/amonet/modules/common.py", line 90, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch
Dkhanh0412 said:
Hi, i was happen to wander around the forum to find a method to root my HD 8 2017, and seems that my tablet has automatically update to the point where root is not possible (the current version was 5.6.4.0 build 636559820), therefore i tried to downgrade to 5.6.0.1,since the root method only covers the 636558520 build version, and after using adb sideload, i found out that the device has been totally bricked and can't be turned on, after a few googling. i've found the post about debricking, but requires me to short the TP28 circuit (which i don't know where it was after removing the cover), so i use amonet and it still didn't work, please help!!
--- and here is the log of the terminal:
[email protected]:~/Downloads/amonet$ sudo ./bootrom-step.sh
[2019-11-04 14:00:27.420553] Waiting for bootrom
[2019-11-04 14:00:43.250282] Found port = /dev/ttyACM0
[2019-11-04 14:00:43.287246] Handshake
* * * If you have a short attached, remove it now * * *
* * * Press Enter to continue * * *
b''
b'\x00\x01'
Traceback (most recent call last):
File "main.py", line 256, in <module>
main()
File "main.py", line 129, in main
load_payload(dev, "../brom-payload/build/payload.bin")
File "/home/lubuntu/Downloads/amonet/modules/load_payload.py", line 123, in load_payload
dev.write32(0x10007008, 0x1971) # low-level watchdog kick
File "/home/lubuntu/Downloads/amonet/modules/common.py", line 163, in write32
self.check(self.dev.read(2), b'\x00\x01') # arg check
File "/home/lubuntu/Downloads/amonet/modules/common.py", line 90, in check
raise RuntimeError("ERROR: Serial protocol mismatch")
RuntimeError: ERROR: Serial protocol mismatch
Click to expand...
Click to collapse
Wow my PM
Please don't pm me for this things, create a thread as you done or ask in the UNBRICK thread.
So about your error..
Mean that you're in Preloader Mode instead of BootROM Mode:
Code:
RuntimeError: ERROR: Serial protocol mismatch
Be sure to have modemmanager disabled.
Try to short again, it can take a lot of tries (For me like 20+).
If still no, change the object that you're using to short.
If thse same, try other USB cable and other USB port (BETTER 2.0 instead 3.0).
If after try all the suggestions still the same error, do the process with the battery disconnected, that worked in most cases.
Cheers!
Rortiz2 said:
Wow my PM
Please don't pm me for this things, create a thread as you done or ask in the UNBRICK thread.
So about your error..
Mean that you're in Preloader Mode instead of BootROM Mode:
Code:
RuntimeError: ERROR: Serial protocol mismatch
Be sure to have modemmanager disabled.
Try to short again, it can take a lot of tries (For me like 20+).
If still no, change the object that you're using to short.
If thse same, try other USB cable and other USB port (BETTER 2.0 instead 3.0).
If after try all the suggestions still the same error, do the process with the battery disconnected, that worked in most cases.
Cheers!
Click to expand...
Click to collapse
Thanks for replying! But can you be more specific about the short process? since i don't know where is the CLK test point of the board, the original guide showed that it is near the the emmc, it would be nice if you can show me the image of where to short on the motherboard? And about the Preloader mode? So i have to use the brick-9820.sh to confirm the brick then proceed to bootrom-step.sh?
Dkhanh0412 said:
Thanks for replying! But can you be more specific about the short process? since i don't know where is the CLK test point of the board, the original guide showed that it is near the the emmc, it would be nice if you can show me the image of where to short on the motherboard? And about the Preloader mode? So i have to use the brick-9820.sh to confirm the brick then proceed to bootrom-step.sh?
Click to expand...
Click to collapse
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one) (thanks @<br />)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
I
Rortiz2 said:
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
Click to expand...
Click to collapse
Again, thanks bro, you saved my day
Rortiz2 said:
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one) (thanks @<br />)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
Click to expand...
Click to collapse
Seems like i've ran into some problems,i still get that same error after numerous times of shortening the circuit,
ModemManager disabled
USB 2.0 port used
A bare-ends wire used to short the circuit
But it still display the serial protocol mismatch error (
Here is the image: https://imgur.com/a/D4JTYhJ
Dkhanh0412 said:
Seems like i've ran into some problems,i still get that same error after numerous times of shortening the circuit,
ModemManager disabled
USB 2.0 port used
A bare-ends wire used to short the circuit
But it still display the serial protocol mismatch error (
Here is the image: https://imgur.com/a/D4JTYhJ
Click to expand...
Click to collapse
Disconnect the battery then.
Rortiz2 said:
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one) (thanks @<br />)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
Click to expand...
Click to collapse
Rortiz2 said:
Disconnect the battery then.
Click to expand...
Click to collapse
Well the code did run, but after that nothing happens, i press the power button then the tablet plays a sound, but it still didn't boot up
here is the near end of the log:
[2019-11-05 16:01:19.097336] Force fastboot
[2019-11-05 16:01:19.406864] Flash preloader header
[4 / 4]
[4 / 4]
[2019-11-05 16:01:19.857129] Reboot
Dkhanh0412 said:
Seems like i've ran into some problems,i still get that same error after numerous times of shortening the circuit,
ModemManager disabled
USB 2.0 port used
A bare-ends wire used to short the circuit
But it still display the serial protocol mismatch error (
Here is the image: https://imgur.com/a/D4JTYhJ
Click to expand...
Click to collapse
Well i disconnect the battery and have successfully executed the bootrom-step.sh, and now it still remains bricked, for the first time, when i hold the power button, the tablet plays the start up sound but did not boot up, what should i do now!?
Rortiz2 said:
No, you don't need to run any brick.sh since you already bricked but in the WRONG WAY, so you need to short TP28.
If you search a bit, you can find the TP28 image
https://imgur.com/9ThIUqK (The Light blue one) (thanks @<br />)
You need to short that point with something conductive as a paper clip or a little or a small cable with bare ends.
One end of the object you put in TP28 and the other in any place with metal that is on the motherboard (a screw for example).
At same moment that you're doing this the script should be executed and waiting for handshake the bootROM:
Code:
sudo ./bootrom-step.sh
After that short the point as described and connect the tablet into the computer AT SAME TIME. If all goes OK it will ask to remove the short. Remove it and press enter, the script will do the magic
If you still getting the Serial Protocol error, use my suggestions of my previous post.
That's all, a bit tricky but has solution
Cheers!
Click to expand...
Click to collapse
Well since the method here is almost unusable, i was thinking of flashing the .bin file of my Fire using MiracleBox, maybe this could help with my problem: https://www.google.com/amp/s/ifindhub.com/flash-bin-firmware-files-mediatek-device.html/amp
Dkhanh0412 said:
Well since the method here is almost unusable, i was thinking of flashing the .bin file of my Fire using MiracleBox, maybe this could help with my problem: https://www.google.com/amp/s/ifindhub.com/flash-bin-firmware-files-mediatek-device.html/amp
Click to expand...
Click to collapse
Dude...
That box comunicates with Preloader which is patched on Amazon tablets.. If it were that easy we would have rooted this tablet many years ago.
About your problems, seems like a LCD cable problem. Unmount again the tablet and check all cables, specially the LCD one.
Cheers.
Rortiz2 said:
Dude...
That box comunicates with Preloader which is patched on Amazon tablets.. If it were that easy we would have rooted this tablet many years ago.
About your problems, seems like a LCD cable problem. Unmount again the tablet and check all cables, specially the LCD one.
Cheers.
Click to expand...
Click to collapse
Hmmm, i'll make sure to double check everything again to keep things intact, thanks a lot bro