Number format - Galaxy S III Mini Q&A, Help & Troubleshooting

How do I change the number format ?
From xxx xxxx xxx to xxxx xxx xxx ?
I couldn't find .

Related

How to backup ROM for the SPV M3000

I tried to use the 'tera term pro' and send the command : r2sd all
I got the message :
Cmd>r2sd all
***** user area size = 0xF140000 Bytes
R2SDBackup() - Download type = 6
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
You didn't get the proper security level to download a specific image
I need the password for the command password [password] to be able to dump the rom
Any ideas ?
Thx a lot for help

[HOWTO] USB Unbrick

First of all many thanks to IEFtm from Modaco forum for the solution and the how to !!
Here a copy/paste of instructions with some additions ( i can't be more clear than him )
/!\ IMPORTANT /!\ : only your device will see your sdcard before the end of the unbrick process !!!
As most of you know, people have been hard at work to fix the USB issues we've been seeing due to recovery setting us into USB debugmode.
After unsuccessful attempts to change the kernel commandline , eg. to:
disable_uart3=0
usb_h2w_sw=0
we've been successful in discovering (with the help of XDA-developers) that these switches are stored in the first NAND partition, mtd0, or 'misc'.
You must be rooted to try the following, it seems you can't write to mtd0 without root.
Do step 1 again if you have to.
Also, SD card functionality has to work. For this, go into fastboot mode ( device off : volume down + power, select FASTBOOT) , and do:
fastboot oem enableqxdm 0
( you must have android sdk installed, open a command prompt MSDOS under windows, navigate into 'tools' folder and type this command )
Steps involved:
1. Find out your CID. Go into fastboot mode ( device off : volume down + power, select FASTBOOT) , and do :
fastboot oem boot
( you must have android sdk installed, open a command prompt MSDOS under windows, navigate into 'tools' folder and type this command )
The log will say something like the following:
Code:
#INFOTAG:Ramdisk OK
#INFOTAG:smi ok, size = 0
#INFOTAG:hwid 0x0
#INFOTAG:skuid 0x21F04
#INFOTAG:hero panel = 0x0
#INFOTAG:engineerid = 0x0
#INFOMCP dual-die
#INFOMCP dual-die
#INFOTAG:mono-die = 0x0
#INFODevice CID is not super CID
[B][SIZE="3"]#INFOCID is HTC__E11[/SIZE][/B]
In this specific case, the CID is HTC__E11.
2. Get the following mtd0.img from here or from here: mirror provided by SgtDavePwnage.
Edit this image to the CID you found above with a hex editor.
3. Get flash_image from here or from here: mirror provided by SgtDavePwnage.
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator ( you must do this on your device with Connecbot for exemple ) :
In the terminal emulator ( like connecbot ) you will be at prompt beginning with a $ , type 'su' ( without the quote ) 2 times and you will normally see # at the beginning of the ligne ( or anything else with # ). In this case you are logged as root. You can check it with this command : ls ( check screenshoot to see what's look like )
Now type the following
cat /sdcard/flash_image > /data/flash_image "type enter"
cat /sdcard/mtd0.img > /data/mtd0.img "type enter"
chmod 755 /data/flash_image "type enter"
/data/flash_image misc /data/mtd0.img "type enter"
( repeat last command 2 times to be sure and ignore output errors that you will see )
4. Repeat step 3 a couple of times if it doesn't seem to work well.
5. All done! Reboot, you should have normal usb connectivity. Post your 'fastboot oem boot' log and intermediate steps if it fails.
In case of you get 'permission denied' for 'su' command , you can try to do the same thing as Deffe on modaco forum :
P.S.
before i have reroot my legend make step1 and use fake-flush and not step2. So the phone became rooted and i can use connectbot!
Click to expand...
Click to collapse
Credits:
-kubino @ XDA for providing us with the 'misc' information
-TheProfessor @ irc.freenode.net #modaco for being the first test subject + debugging
-adam235 @ irc.freenode.net #modaco for being a test subject as well + debugging
-SgtDavePwnage @ irc.freenode.net #modaco -> moral support + debugging
-DrMon @ irc.freenode.net #modaco -> being brave enough to test on his non-bricked device!
You can also check this :
http://forum.xda-developers.com/showthread.php?t=747030
and
http://forum.xda-developers.com/showthread.php?t=748813
and here
http://forum.xda-developers.com/showthread.php?t=733713
to get some information on your situation.
You can go to the original thread http://android.modaco.com/content/h...com/309961/usb-brick-rickrolled-b0rked-fixed/
to get your mtd0.img already modified for your CID ( if someone has posted it )
Click here to DONATE for them !
Thank You, Ilos. Was waiting for this. Your effort is much appreciated.
Hope our Moderator Sir will put a link to this thread in the first post in this section.
I read through the remedy everyday so I understand a little more each day but I sure hope you will be around when get usb bricked !
Can I practise this on my good device to get a hang of it or will it mess up things big time !
Thread Stuck.
Hi Ilos,
Thanks for the better detailed information so far, about usb problems.
After obtaining super user access i wrote the following commands as you said.
cat /sdcard/flash_image > /data/flash_image
cat /sdcard/mtd0.img > /data/mtd0.img
After writing the above commands in connectbot and giving the enter, the terminal mentioned that they could not find the files.
I placed them om my sd card. is it necessary to place them in a certain file?
The other commands went well and I rebooted but my telephone was not recognized by the computer.
in the below line you mention that the output errors should be ignored, what do you mean with that, because I receive errors.
" repeat last command 2 times to be sure and ignore output errors that you will see )"
I also wrote the last command two times but with no success.
Thanks in advance.
you must put both files at / of your sdcard and you received error at the end of the process ( 0X0000112331 or something like that )
ilos said:
you must put both files at / of your sdcard and you received error at the end of the process ( 0X0000112331 or something like that )
Click to expand...
Click to collapse
No error like that but can't find the flash_image and mtd0.img file.
when your logged as root under connecbot, please type that
ls
and tell me what you see
more or less what you see in img. device2 in one of your comments above posted on today 10.25am
you must see your sdcard when you type ls
if you see it, type :
cd sdcard
and type again ls
check if you see flash_image and mtd0.img that you put on your sdcard
Ilos I managed it with your great help.
I unfortunately had renamed the file mtd0.img which gave the output in the terminal ls mtd0.img.img. and therefore the command could not be read correctly. So I changed the filename and repeated the steps with SUCCESS.
Thanks again.
happy to see your success
Enjoy flashing again !!
ok edited the img and moved them into the sdcard.what to do now how can i move them in the legend data?
kdma said:
ok edited the img and moved them into the sdcard.what to do now how can i move them in the legend data?
Click to expand...
Click to collapse
pls read the "how to" before asking....
ilos said:
You can move both mtd0.img and flash_image by putting it on your sdcard, and issueing the following command in a terminal emulator ( you must do this on your device with Connecbot for exemple ) :
In the terminal emulator ( like connecbot ) you will be at prompt beginning with a $ , type 'su' ( without the quote ) 2 times and you will normally see # at the beginning of the ligne ( or anything else with # ). In this case you are logged as root. You can check it with this command : ls ( check screenshoot to see what's look like )
Now type the following
cat /sdcard/flash_image > /data/flash_image "type enter"
cat /sdcard/mtd0.img > /data/mtd0.img "type enter"
chmod 755 /data/flash_image "type enter"
/data/flash_image misc /data/mtd0.img "type enter"
( repeat last command 2 times to be sure and ignore output errors that you will see )...
Click to expand...
Click to collapse
how should i use connecbot if i cant boot my phone?
i can only use fastboot
maybe
Maybe Froyo will be gentler on our devices and roms as probably there will be no need to use app2sd + which has been considered, albeit not conclusively, to be one of the major causes of usb bricking (?)
Anyone know what causes the USB bricking?
Sent from my Legend using XDA App
Hi all
People that I do?? I can not determine the USB, only in boot mode is determined, I have a new hboot and I can not do step1, can someone help me ka??
Poligon:/mnt/winda/tmp/android/r4-legend-root# ./fastboot-linux oem gencheckpt boot
... INFOsetup_tag addr=0x60000100 cmdline add=0x9D079570
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x22F00
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__A07
INFOsetting->cid::HTC__A07
INFOserial number: HT03DNX01548
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =443
INFOactive commandline: board_legend.disable_uart3=1 board_legen
INFOd.usb_h2w_sw=1 board_legend.disable_sdcard=0 diag.enabled=0
INFOboard_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false androidboot.baseband=7.08.35.21 androidboot.c
INFOid=HTC__A07 androidboot.carrier=HTC-Russia androidboot.mid=P
INFOB7610000 androidboot.keycaps=qwerty androidboot.mode=recover
INFOy androidboot.serialno=HT03DNX01548 androidboot.bootloader=0
INFO.43.0003 no_console_suspend=1 console=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw 15E 1000
FAILED (status read failed (Protocol error))
izya12 said:
INFOactive commandline: board_legend.disable_uart3=1 board_legen
INFOd.usb_h2w_sw=1 board_legend.disable_sdcard=0 diag.enabled=0
Click to expand...
Click to collapse
look at these lines
it has :
board_legend.disable_uart3=1
board_legend.usb_h2w_sw=1
acording to android.modaco.com/content/htc-legend-legend-modaco-com/309961/usb-brick-rickrolled-b0rked-fixed/ these values should be 0
so your Legend is USB-bricked ( like mine was , do not worry it is solvable )
follow the modago unbrick howto an have fun with your legend !!
Sorry for the choppy link but my account is not jet enabled for outside links
izya12 said:
Hi all
People that I do?? I can not determine the USB, only in boot mode is determined, I have a new hboot and I can not do step1, can someone help me ka??
Poligon:/mnt/winda/tmp/android/r4-legend-root# ./fastboot-linux oem gencheckpt boot
... INFOsetup_tag addr=0x60000100 cmdline add=0x9D079570
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x22F00
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__A07
INFOsetting->cid::HTC__A07
INFOserial number: HT03DNX01548
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =443
INFOactive commandline: board_legend.disable_uart3=1 board_legen
INFOd.usb_h2w_sw=1 board_legend.disable_sdcard=0 diag.enabled=0
INFOboard_legend.debug_uart=0 smisize=0 userdata_sel=0 androidbo
INFOot.emmc=false androidboot.baseband=7.08.35.21 androidboot.c
INFOid=HTC__A07 androidboot.carrier=HTC-Russia androidboot.mid=P
INFOB7610000 androidboot.keycaps=qwerty androidboot.mode=recover
INFOy androidboot.serialno=HT03DNX01548 androidboot.bootloader=0
INFO.43.0003 no_console_suspend=1 console=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw 15E 1000
FAILED (status read failed (Protocol error))
Click to expand...
Click to collapse
USB bricked.... pls follow the HOWTO in the first post...
when the phone Brick is always possible to solve the problem?

[Q] Lost IMEI after upgrade

Hi all!
I were in the process to upgrade to 10b on my phone, but during the upgrade the phone stopped responding on upgrading S/W. Please wait. And after some time on that screen, I removed the battery and cable, and tried the different solutions provided by the LG B2C Support Tool.
After that I tried to flash the phone with smartflash and the latest software. And that worked perfectly, but now the phone has no IMEI. Have tried to install the backup I had via CWM but still no IMEI.
I was looking forward to use the 2x this easter, but if noone has a good solution in getting the IMEI back, the phone needs to go on a easter holiday to the service centre.
You did the same thing with me. When using smartflash, DO NOT check option "Erase CAL data" but I did. My SU660 now has serial number = 0000000. P990 will lost IMEI.
Sent from my LG-SU660 using XDA Premium App
I had the same problem, you need to flash the baseband firmware as it is gone.
I think that it was during updating the baseband as part of the V10b mine stopped flashing.
Look here: http://forum.xda-developers.com/showthread.php?t=1008070
It worked with mine o2x.
I managed to solve the situation.
I applied the 10b firmware using nvflash. And then flashed the 10a fw with smartflash, checked that the IMEI were back in business. And then did a new update using smartflash to 10b and now everything is back as normal
restore IMEI (From Modaco)
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Hi mohicanrat,
I tried to set 'Port Setting' -> 'CP USB', but in the device manager (i'm using win7), this device then shows up as 'Other Devices' -> 'Unknown device'.
What should I do now? Where can I get the device driver for this?
hello,
please where i go to "Start hyperterminal, in COM settings"
HyperTerminal was binned after Windows XP, if you have Vista onwards you'll need to download an equivalent.
mohicanrat said:
1. Connect phone by usb
2. Enter 1809#*990# in dialer
3. Select port settings -> select cp usb
4. Start hyperterminal, in com settings select same port like in devide manager -> lge mobile usb serial port, 115200
5. Type at if response is not ok, change port number
6. Type at%imei, it should display your current imei
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... Is your orginal imei number
8. Reset
Click to expand...
Click to collapse
thank you very much. I did as you said and finally got my imei back
thank you a million.
mohicanrat said:
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Click to expand...
Click to collapse
It gives error on running at%imei, might it be because phone driver not installed on windows?
at%imei
ERROR
I instaled driver from LG site LGUnitedMobileDriver_S498MA22_WHQL_ML_Ver_2.2.exe
when i type ATI4 for instance it shows same info as from log.
Here's log from modem i removed my IMEI though.
PHP:
11-26-2011 01:29:11.420 - File: C:\Windows\system32\tapisrv.dll, Version 6.1.7600
11-26-2011 01:29:11.420 - File: C:\Windows\system32\unimdm.tsp, Version 6.1.7600
11-26-2011 01:29:11.421 - File: C:\Windows\system32\unimdmat.dll, Version 6.1.7600
11-26-2011 01:29:11.421 - File: C:\Windows\system32\uniplat.dll, Version 6.1.7600
11-26-2011 01:29:11.430 - File: C:\Windows\system32\drivers\modem.sys, Version 6.1.7600
11-26-2011 01:29:11.430 - File: C:\Windows\system32\modemui.dll, Version 6.1.7600
11-26-2011 01:29:11.438 - File: C:\Windows\system32\mdminst.dll, Version 6.1.7600
11-26-2011 01:29:11.439 - Modem type: LGE Mobile USB Modem
11-26-2011 01:29:11.439 - Modem inf path: oem29.inf
11-26-2011 01:29:11.439 - Modem inf section: LGSI.Install
11-26-2011 01:29:11.439 - Matching hardware ID: usb\vid_1004&pid_6000_modeminterface
11-26-2011 01:29:11.470 - 460800,8,N,1, ctsfl=0, rtsctl=1
11-26-2011 01:29:11.488 - Initializing modem.
11-26-2011 01:29:11.488 - CD is high while initializing modem.
11-26-2011 01:29:11.498 - Send: AT<cr>
11-26-2011 01:29:11.504 - Recv: <cr><lf>OK<cr><lf>
11-26-2011 01:29:11.504 - Interpreted response: OK
11-26-2011 01:29:11.514 - Send: ATE0V1&D2&C1S0=0<cr>
11-26-2011 01:29:11.526 - Recv: <cr><lf>ERROR<cr><lf>
11-26-2011 01:29:11.526 - Interpreted response: Error
11-26-2011 01:29:11.527 - Session Statistics:
11-26-2011 01:29:11.527 - Reads : 15 bytes
11-26-2011 01:29:11.527 - Writes: 20 bytes
ATQ0V1E0 - OK
AT+GMM - 0
AT+FCLASS=? - +FCLASS: (0-1)
AT#CLS=? - COMMAND NOT SUPPORTED
AT+GCI? - COMMAND NOT SUPPORTED
AT+GCI=? - COMMAND NOT SUPPORTED
ATI1 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI2 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI3 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI4 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI5 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI6 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
ATI7 - Manufacturer: QUALCOMM INCORPORATED
Model: 0
Revision: M6600A-SCAUTNZ-2.0.9720T 1 [JUL 15 2011 10:00:00] MP:TRULGE_08.09.02R_MDM
IMEI: < removed >
+GCAP: +CGSM,+DS,+ES
help!!
i can connect but cant type anything in the terminal.. can anyone help .. i ve never done this before.. using win7 x64
Same Problem here....
I've the same problem
IMEI is gone
Baseband is "Unknown"
Battery shows 999%
And like the poster above me, I cant type anything in the Hyperterminal
PLS, who got his IMEI (and with this his loved Optimus) back, help us!!
Thx in advance,
sleep
mohicanrat said:
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Click to expand...
Click to collapse
Today i was flashing LG Optimus Black P970 with SmartFlash and accidentaly i checked "Erase entire CP". In a result my IMEI has changed...
With this tutorial I managed to recover my IMEI successfully!
It took me 2 minutes and worked at first time.
i'm trying this method but not working
when type At...i get ok
but when i type imei i get error
What error? Paste screenshot or log.
What firmware version do you have in your LG?
You must type exactly this: at%imei - (% symbol is very important) it will display your current IMEI, then
at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x (, (comma) is very important too)
Hi,
I had one time that when i change ril. After backup my old ril all work fine.
I tried this method but i get "IMPL ERROR".
Stock ROM V10c
Tried to downgrade baseband from
1035.21_20110405
to
1035.21_20110315
but still same error...
Any idea?
Can you please tell me exact software version on what this method worked?
any solution for su660 i have the same problem
I expect the same thing would work.
mohicanrat said:
1. Connect phone by USB
2. Enter 1809#*990# in dialer
3. Select Port Settings -> Select CP USB
4. Start hyperterminal, in COM settings select same port like in devide manager -> LGE mobile USB Serial Port, 115200
5. Type AT if response is not OK, change port number
6. Type at%imei, it should display your current IMEI
7. Type at%imei=x,x,x,x,x,x,x,x,x,x,x,x,x,x,x , where x,x,x... is your orginal IMEI number
8. Reset
Click to expand...
Click to collapse
Anyone know how to perform this with an Optimus L3 device? Apparently i can't have acces to "Port Settings"

Share how to switch from version g to Chinese version.

I've broken the Chinese version and can't swipe the Chinese version, which causes the partition table error. I found a Chinese version firmware shared by a post in the forum. Modify the rawprogram0.xml file line 16 in the file filename = "UserData. Img" label = "UserData" to filename = "" label = "UserData", and then use miflashpro to swipe in successfully. Miflash should be OK, and you can try if you are interested.
https://androidfilehost.com/?fid=4349826312261610710

Mi-verification and S/N - possible modify : setprop ro.serialno or setprop ro.boot.serialno (build.prop) ?

Hi to all,
found a phone and I had a choice : put it in trash or keep it, I decided the 2nd choice,
1st. attempt: Formatted whole phone (with spflash tool), flashed global_rom, IMEI blank, open wifi, mi-verification lock device back again
2nd & 3rd. attempts: Fixed Imei, with original and not original (modem-meta), mi-verification lock device back again
I guess Mi-verification read not IMEI for locking, but serial number ?
Question is, should I trhow this device to trash or is there a way to be used, by then removing Mi-verification ?
I read along the forum, and the solution seems to be to change the serial-number :
Code:
adb shell "getprop | grep serial"
[ro.boot.serialno]: [050505050505]
[ro.serialno]: [050505050505]
[vendor.gsm.serial]: []
to change it :
Code:
adb shell "setprop ro.serialno 060606060606"
adb shell "setprop ro.boot.serialno 060606060606"
but it return not possible, I guess read only
Is there a way to change serial number, and change configuration of build.prop ?
very good question !
It seems to be a dead argument !! not so much interest on it ..
Pulled build.prop but no trace of ro.serialno or ro.boot.serialno inside,
on a post of 2 years ago, I read that after android 10 there is no possibility to change S/N, is it real ?

Categories

Resources