- Register
- Help
- Remember Me?

1. If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Page 1 of 2 1 2 Last

- Jump to page:

Results 1 to 10 of 14

# Thread: HOW TO WORK WITH SEMC PDA PHONES

- ###### Thread Tools

  - Show Printable Version

- ###### Display

  - Linear Mode
  - Switch to Hybrid Mode
  - Switch to Threaded Mode

1. 02-05-2010, 12:51 PM #1
   the_laser
   - View Profile
   - View Forum Posts
   - Private Message
   Administrator

   Join Date
     Feb 2010
   Posts
     18,785

   ## HOW TO WORK WITH SEMC PDA PHONES

   > first, basics.
   > SEMC created few types of PDA:
   > db200x+nexperia (SYMBIAN OS)
   > m600,w950,w960,p1,p990
   > such phones have two security type - NEW and OLD.
   > Identify button will show security type - it will write "NEW SECURITY detected" with NEW security phones.
   > if is better to install PDA phone drivers and PDA flash drivers before any operation.
   > phone drivers:
   > for that you need to download phones.rar from support or from SEMC
   > turn on phone. in "connections manager->usb" select "normal mode".
   > now, attach cable.
   > windows will ask you for drivers, point it to corresponding folder within extracted phones.rar.
   > you must have "semc xxx usb modem" and "semc xxx application port" if drivers correctly installed.
   > now, turn phone off and detach it.
   > flash drivers:
   > power on smartphone in fw update mode.
   > - for p990/m600 press and hold "@" on TURNED OFF phone, then attach dcu60.
   > - for w950,w960,p1 press and hold "C" on TURNED OFF phone, then attach dcu60.
   > windows will ask you for a drivers. drivers in %setool2 dist%\drivers\Smartphone_Drivers
   > S1 OPEN (SYMBIAN OS) ( ti omap + db3xxx )
   > satio,vivaz,vivaz pro
   > S1 QUALCOMM,MT BASED (ANDROID OS)
   > all other models

   Reply With Quote

2. ## The Following 110 Users Say Thank You to the_laser For This Useful Post:

   > .:Zulfiqar:., admir82, adnann5, akaygsm, antoniolcrd, as8088, atashius, AwAdViCtOrY, aztech, badboy 57, bigboy85, biochemistali, cavalierks, ch arshad, clueless_gsm, cmphone, descarado, DeyviBox, dimetri, DUSK, eshcouza, Freezzby, GSM City, hari setyawan, hyber_99, irfanamin2, Jabbacks, jollen_9, jomafi, Jupz83, LIKI, mittto, Mr1X, myrwok, nihana, prasath_max, raazimobile, raie, ramin_le, rayvee, Rhyan, runner30, sapari, schemu, shami, shonarga_baradi, sobaro, soil2020, spyrakosa, sukizg, tirazhe, vertucio, xesar, xXx, zhieoem

3. 02-05-2010, 12:52 PM #2
   the_laser
   - View Profile
   - View Forum Posts
   - Private Message
   Administrator

   Join Date
     Feb 2010
   Posts
     18,785

   ##

   > FLASHING OF A1-BASED PDA PHONES
   > download needed firmware package.
   > add it to firmware area on PDA tab.
   > DO NOT UNZIP PACKAGE, JUST ADD IT AS IS.
   > on settings,check "signed mode"
   > press flash
   > note, if phone have BROWN domain, you must FIRST flash conversion packs:
   > for m600,w950,p990:
   > for brown cid 36: pda_ccpu_convert_red49_signed_brown36.zip
   > for brown cid 49: pda_ccpu_convert_red49_signed_brown49.zip
   > for w960,p1:
   > for brown cid 49: pda_ccpu_convert_red53_signed_brown49.zip

   Reply With Quote

4. ## The Following 68 Users Say Thank You to the_laser For This Useful Post:

   > .:Zulfiqar:., akaygsm, as8088, atashius, AwAdViCtOrY, bigboy85, biochemistali, ch arshad, clueless_gsm, descarado, dimetri, DR_MOOSAVI, fatehbey, hari setyawan, hyber_99, irfanamin2, jollen_9, jomafi, Jupz83, LIKI, maremestera, myrwok, Nadjombe, nihana, nomy7, raazimobile, raie, ramin_le, rayvee, Rhyan, rinkdroid, schemu, shami, shonarga_baradi, soil2020, spyrakosa, tirazhe, xXx, y3kt

5. 02-05-2010, 12:52 PM #3
   the_laser
   - View Profile
   - View Forum Posts
   - Private Message
   Administrator

   Join Date
     Feb 2010
   Posts
     18,785

   ##

   > UNLOCKING OF A1-BASED PDA PHONES
   > if you want to UNLOCK NEW SECURITY phone -
   > check "use server" and enter your login/password.
   > please check FAQ article about credit consumptions for your phone.
   > press unlock button and insert cable to phone,while holding appropriate key on phone.
   > follow program directions.
   > if you want to UNLOCK OLD SECURITY phone -
   > UNCHECK "use server".
   > BE SURE you have latest REST files.
   > now, you need install drivers for flashing.
   > for that, poweron smartphone in fw update mode.
   > - for p990/m600 press and hold "@" on TURNED OFF phone, then attach dcu60.
   > - for w950 press and hold "C" on TURNED OFF phone, then attach dcu60.
   > windows will ask you for a drivers. drivers in %setool2 dist%\drivers\Smartphone_Drivers
   > now, when all preparations finished - press unlock button and insert cable to phone,while holding appropriate key on phone.
   > follow program directions.

   Reply With Quote

6. ## The Following 63 Users Say Thank You to the_laser For This Useful Post:

   > .:Zulfiqar:., adnann5, akaygsm, as8088, AwAdViCtOrY, bigboy85, biochemistali, CDMA_RASHID5, clueless_gsm, descarado, dimetri, gringos, hari setyawan, irfanamin2, jollen_9, jomafi, Jupz83, koperta4512, LIKI, maremestera, milkyctg, myrwok, nihana, prasath_max, raazimobile, raie, ramin_le, rayvee, rezasho, Rhyan, riteshgpt60, shami, shonarga_baradi, sm_shahzada, soil2020, SOSHAN, spyrakosa, tirazhe, xXx, y3kt, zartan

7. 02-05-2010, 12:56 PM #4
   the_laser
   - View Profile
   - View Forum Posts
   - Private Message
   Administrator

   Join Date
     Feb 2010
   Posts
     18,785

   ##

   > FLASHING OF S1-OPEN PDA PHONES (Satio,Vivaz,Vivaz pro)
   > download needed firmware package.
   > add it to firmware area on PDA tab.
   > DO NOT UNPACK .ZIP PACKAGE, JUST ADD IT AS IS.
   > on settings,check "signed mode"
   > press flash
   > connect turned off phone while holding "green" button.
   > FLASHING OF S1-ANDROID PDA PHONES (x10,x10 mini,x10 mini pro,etc)
   > download needed firmware package.
   > ( two main files,both REQUIRED. APP - OS kernel, radio part, FSP - user and android OS system data,
   > CDF - internal storage contents, eLabel - electronic label )
   > add it to firmware area on PDA tab.
   > Order is IMPORTANT - ALWAYS add APP part first, then FSP, then eLabel, then CDF
   > Some MT-based phones can be irreversible killed, if APP part is NOT first package to flash.
   > UNPACK package archive, if packed (unzip,unrar, but DO NOT unpack *.sin_file_set itself ), ADD *.file_set to firmware area
   > on settings,check "signed mode"
   > press flash
   > connect turned off phone while holding "BACK" button.

   Reply With Quote

8. ## The Following 75 Users Say Thank You to the_laser For This Useful Post:

   > adnann5, akaygsm, as8088, AwAdViCtOrY, aztech, bigboy85, biochemistali, chepito892, ching2-o, clueless_gsm, descarado, dimetri, facebook.com, Gracek, GsmServisi, hari setyawan, hatrun, Heddata, hijena81, Ionel, irfanamin2, joecheun, jollen_9, jomafi, Jupz83, katitous, LIKI, lolka, maremestera, moulaha, Mr1X, myrwok, nihana, nnaeem11, prasath_max, raazimobile, raie, ramin_le, rayvee, Rhyan, rosendohl13, shami, shoeb7, shonarga_baradi, soil2020, SOSHAN, tictac_m, xXx, y3kt

9. 02-05-2010, 12:56 PM #5
   the_laser
   - View Profile
   - View Forum Posts
   - Private Message
   Administrator

   Join Date
     Feb 2010
   Posts
     18,785

   ##

   > UNLOCKING OF S1-OPEN PDA PHONES
   > select USB as interface. that is REQUIRED.
   > select phone model
   > settings - check ONLY "signed mode (using server)", "do full unlock instead of usercode reset", fill your login details.
   > back to original tab, press unlock, "GREEN BUTTON"
   > if signature is calculated - you will receive 'SUCCESS' response, otherwise you will receive error code.
   > if calculation is success, then signature will be saved in backup\%imei% folder in your setool2 directory.
   > next, backup will be created so you will be able to restore phone if something will go wrong.
   > procedure will continue,phone will be switched off and unlocked.
   > remember, if something will go wrong - you have a backup of security units.
   > please check "credits consumption" FAQ post for info about number of credits.
   > UNLOCKING OF S1-ANDROID PDA PHONES
   > server based full official unlock method. Only available, when s1 signature server online
   > select USB as interface. that is REQUIRED.
   > select phone model
   > settings - check ONLY "signed mode (using server)", "do full unlock instead of usercode reset", fill your login details.
   > back to original tab, press unlock, hold "BACK BUTTON" and insert cable to powered off phone.
   > if signature is calculated - you will receive 'SUCCESS' response, otherwise you will receive error code.
   > if calculation is success, then signature will be saved in backup\%imei% folder in your setool2 directory
   > (following unlock attempts, if something had happen with phone - cable disconnect,etc - during unlock - will be free as long as signature remains there )
   > next, backup will be created so you will be able to restore phone if something will go wrong.
   > procedure will continue,phone will be switched off and unlocked.
   > remember, if something will go wrong - you have a backup of security units.
   > please check "credits consumption" FAQ post for info about number of credits.
   > server based full unlock method using alternative security bypass
   > please read that post
   > GESTURE LOCK/USER PASSWORD RESED FOR S1-ANDROID PDA PHONES
   > check signed mode only, press unlock.
   > hold "BACK BUTTON" and insert cable to powered off phone.
   > if phone has blocked attempts counter, then you need reflash phone after lock reset.

   Reply With Quote

10. ## The Following 66 Users Say Thank You to the_laser For This Useful Post:

    > adnann5, akaygsm, almprinsen, antoniolcrd, as8088, bigboy85, biochemistali, clueless_gsm, Dayline668, descarado, dimetri, hari setyawan, Ionel, irfanamin2, jollen_9, jomafi, Jupz83, koperta4512, LIKI, milkyctg, minotaur, mohamed23676, myrwok, orobas, prasath_max, raazimobile, raie, ramin_le, rayvee, Rhyan, saqibmobile, shami, shoeb7, shonarga_baradi, SOSHAN, xXx, y3kt

11. 02-07-2010, 11:37 PM #6
    the_laser
    - View Profile
    - View Forum Posts
    - Private Message
    Administrator

    Join Date
      Feb 2010
    Posts
      18,785

    ##

    > POSSIBLE PROBLEMS
    > DB200X+NEXPERIA
    > damaged SCRC (imei mismatch), damaged seczone, damaged gdfs,damaged CCPU EROM
    > 1. go to emptyboard tab
    > 2. select model
    > 3. on settings, check "signed mode", fill login details
    > 4. press reset, connect phone
    > 5. if gdfs structure okay, skip that step, otherwise add to firmware are gdfs in ssw format: one of
    > DB2001_G700_GDFS_IN_SSW_FORMAT.SSW
    > DB2001_M600_GDFS_IN_SSW_FORMAT.ssw
    > DB2001_P1_GDFS_IN_SSW_FORMAT.ssw
    > DB2001_P990_GDFS_IN_SSW_FORMAT.ssw
    > 6. add to firmware area correct EROM
    > for m600,w950,p990: pda_ccpu_convert_red49_BROWN_CID49_DB2001.software
    > for w960,p1: pda_ccpu_convert_red53_BROWN_CID49_DB2001.software
    > 7. press flash
    > 8. reflash phone on usual PDA tab if needed.
    > phone could not boot using dcu60, erom version timeout error,etc
    > ACPU EROM damaged, to restore it
    > 1. select correct PDA model
    > 2. find corresponding EROM in dist\eroms\, add it to firmware area
    > 3. select correct com port. ufs,usb can't be used for that operation.
    > 4. press recovery
    > 5. connect turned off phone
    > 6. reflash phone via USB with normal firmware
    > S1 OPEN
    > phone could not boot and blinks red, you CAN flash phone
    > unlock phone using full signature unlock
    > phone stuck on white screen
    > reflash clean file system files, then flash normal firmware
    > phone could not boot and blinks red, you CAN NOT flash phone
    > if phone aid 004 - that is brick, can't be repaired by known 3rd party tools
    > if phone aid 001,002,003 - you need to perform trim area repair process:
    > first, make flash readout with options: signed mode,use alternative security bypass.
    > start 80021000
    > len 00200000
    > MID 01
    > "read spare" UNCHECKED
    > "read as ssw" UNCHECKED
    > you will get trim area image readout.
    > now lets determine if hwconfig present and not mismatched.
    > get and hex editor (hiew, winhex or simular)
    > using editor search function, locate in readout bytes d3 07 00 00
    > now check attached picture.
    > if imei is your, then you can try to fix phone.
    > if imei is not your and you do not have backup - send phone to semc.
    > now, lets extract needed trim area units and build script.
    > 1.
    > you need to copy binary data from "data start" till "data end" (inclusive)
    > then convert binary data to its ASCII values (with same winhex)
    > trim_area_unit_example.jpg
    > add script command to data
    > example, from example file read_80021000_00200000_35681003102941.bin:
    > read_80021000_00200000_35681003102941.zip
    > Code:

    >     tawrite:000207d3

    > 2. using editor search function, locate in readout bytes da 07 00 00.
    > extract binary data ( method very same as shown on picture ), add script command
    > Code:

    >     tawrite:000207da

    > 3. using editor search function, locate in readout bytes 51 08 00 00.
    > extract binary data ( method very same as shown on picture ), add script command
    > Code:

    >     tawrite:00020851

    > 4. you have now 3 big string.
    > copy them into one file (each string should be on one line !)
    > add 4-th script command in the end of file
    > Code:

    >     tawrite:0002FDE800

    > you have own fixup file.
    > fixup_35681003102941.txt
    > proceed to http://support.setool.net/showthread...ll=1#post15855
    > notice, that is you will get simlock tampered message after fix procedure, you NEED to unlock phone using signature server.
    > tutorial video by Aishur: http://www.4shared.com/folder/RCU5KkCO/Satio_fixup.html
    > m_taheri written tool for automatic fixup creation.
    > S1 ANDROID
    > q:
    > i had unlocked my phone using alternative security bypass method, but phone not unlocked.
    > a:
    > you did not set all required settings.
    > you must check "signed mode", "alternative security bypass mode", "do full unlock instead of usercode reset"
    > q:
    > i had unlocked my phone using alternative security bypass method, my settings are correct, i lost 4 credits,
    > but phone not unlocked.
    > a:
    > just reflash phone with required firmware ( android 2.1 ) and repeat procedure.
    > no further credits will be required.

    Reply With Quote

12. ## The Following 103 Users Say Thank You to the_laser For This Useful Post:

    > .::: dawah telecom :::., .::Liquid::., adnann5, agadir5241, akaygsm, almprinsen, anasshe, antoniolcrd, APPLE-LINKS, as8088, ashamsu, ashwani gupta, badrou22, belljoved, beto251172, bigboy85, biochemistali, bouchach1980, cellplus, cellularcpr, ch arshad, chatfan, clueless_gsm, con, dadybo, Dayline668, delux_gsm, descarado, desmond1214, dimetri, DR_MOOSAVI, EIGY, eshcouza, evasoft, gsm.magic, Guestâ„¢, hari setyawan, hijena81, irfanamin2, joecheun, jomafi, Jupz83, Lancer93, LIKI, manan_hanan, milkyctg, mohamed23676, myrwok, nihana, prasath_max, raazimobile, raie, ramin_le, rayvee, rezasho, Rhyan, rosta01, s1emens, SALES121, sapari, shami, shonarga_baradi, soil2020, SOSHAN, squallvai, sumatera, svmknee, tomlat, xXx, y3kt

13. 10-07-2010, 02:09 PM #7
    the_laser
    - View Profile
    - View Forum Posts
    - Private Message
    Administrator

    Join Date
      Feb 2010
    Posts
      18,785

    ##

    > script to change keyboard layout for u8 vivaz pro.
    > Code:

    >     // To set u8 keypad layout
    >     //
    >     // Values:
    >     // 00000000	= QWERTY
    >     // 01000000	= QWERTY for NAM
    >     // 02000000 	= QWERTZ
    >     // 03000000 	= AZERTY
    >     // 04000000 	= QWERTY
    >     // 05000000 	= QWERTY Sweden/Finland/Denmark/Norway
    >     // 06000000 	= Chinese Stroke/QWERTY
    >     // 07000000 	= Chinese Bopomofo/QWERTY
    >     // 08000000 	= Cyrillic/QWERTY
    >     // 09000000 	= QWERTY Brazilian Portuguese
    >     // 0A000000 	= Hebrew/QWERTY
    >     // 0B000000 	= Arabic/QWERTY
    >     // 0C000000 	= Greek/QWERTY
    >     // 0D000000 	= Thai/QWERTY

    >     tawrite:000213BA06000000

    Reply With Quote

14. ## The Following 54 Users Say Thank You to the_laser For This Useful Post:

    > 2net2, adnann5, AL-NAJAT, Amir-SkillZ, antoniolcrd, as8088, bigboy85, clueless_gsm, Dayline668, descarado, Dilip_Nath, dimetri, DR_MOOSAVI, EIGY, Guestâ„¢, hari setyawan, hijena81, irfanamin2, Jupz83, LIKI, milkyctg, myrwok, netlynx, nihana, POLACO, raazimobile, raie, Rhyan, rjsoo7, rosendohl13, sapari, shami, shonarga_baradi, soil2020, SOSHAN, tomlat, werbert, xXx, y3kt

15. 07-11-2011, 05:12 PM #8
    the_laser
    - View Profile
    - View Forum Posts
    - Private Message
    Administrator

    Join Date
      Feb 2010
    Posts
      18,785

    ##

    > q:
    > which s1 android based phones i can unlock using alternative security bypass ?
    > a:
    > you can use that method for
    > x10i,x10i,s0-o1b, e10,e15,e16,u20 phones.
    > lt15,mt15,r800 and other msm8255-based phones require very simple testpoint to perform alternative security bypass.
    > x10i,x10i,s0-o1b, e10,e15,e16,u20 phones can also use testpoint method (complex, but powerful ) for unlock/repair
    > q:
    > how to unlock s1 android based phones, based on msm7227,qsd8250 using alternative security bypass without testpoint ?
    > a:
    > Here is procedure.
    > 1.
    > make sure you have firmware with android 2.x, NOT 1.6.
    > flash required firmware, if needed.
    > 2.
    > power on phone without sim card, go to menu->settings->applications->development, enable "usb debugging"
    > connect phone to PC, install drivers from setool2 distr ( drivers\ADB_Drivers)
    > hint:
    > i suggest you to import DisableADBNumbering.reg (DisableADBNumbering.zip) , however this is not required.
    > 3.
    > select proper phone model.
    > select USB as interface
    > on settings check signed mode, use alternative security bypass, do full unlock instead usercode reset
    > press unlock
    > when prompted, detach phone, turn it on fully, connect it again.
    > ( or you can leave phone on cable, then power it on manually )
    > when program tells "warming up...", manually power on phone fully, cause it will automatically enter charging mode.
    > after you see "GETTING ROOT ACCESS ..." DO NOT TOUCH PHONE until procedure complete.
    > DO NOT DETACH PHONE FROM CABLE AFTER PROCEDURE STARTED, YOU CAN KILL YOUR PHONE.
    > DO NOT REMOVE BATTERY FROM PHONE AFTER PROCEDURE STARTED, YOU CAN KILL YOUR PHONE.
    > SUCH KILLED PHONES CAN BE REPAIRED WITH RESURRECTION CABLES.
    > possible problems:
    > problem:
    > you getting "Can't get ROOT rights", "err: 00000005","err: 00000002" during process
    > solution:
    > disable antivirus, especially if you using "kaspersky antivirus", i recommend Doctor Web
    > do NOT run setool2 from restricted accounts.
    > do NOT run setool2 from read-only media.
    > problem:
    > it can happen ( very unlikely, though ) that ADB server will not recognize phone after reboot
    > solution:
    > IF phone not detecting automatically and on status bar you can see "waiting for phone...", again - only in that case - disconnect phone from usb and connect it again, procedure should continue.
    > if not, well, repeat from start.
    > q:
    > how to unlock s1 android based phones, based on msm7227,qsd8250, using alternative security bypass using testpoint?
    > a:
    > Here is procedure.
    > FIRMWARE VERSION DOES NOT MATTER, WHEN USING TESTPOINT METHOD
    > 1.
    > prepare for testpoint operation.
    > check testpoints location for your phone model in dist\docs\s1_qualcomm_uart_cables or use GPG cable set
    > open testpoints for access
    > if you do not have GPG cable set, get some needle with wire, connect it to phone GND ( battery minus ) or to USB cable shield, etc.
    > Notice, that most of UART "boxes" for sony ericsson phones have 2 UARTs : DTMS/DFMS and CTMS/CFMS ( TX/RX ) on RJ45 connector.
    > you need to connect DTMS, noted on schematics, to TX ( CTMS ) pin on RJ45 connector, DFMS from schematics to CFMS ( RX ) pin on RJ45.
    > 2.
    > select proper phone model.
    > select COM as interface.
    > on settings check signed mode, use alternative security bypass, do full unlock instead usercode reset, use testpoint (gnd type)
    > fill login/password and check if account valid.
    > press unlock
    > when prompted, execute steps in EXACT order:
    > 1. remove cable from phone,
    > 2. remove battery from phone,
    > 3. attach testpoint ( turn on switch on cable set )
    > 4. insert cable to phone, HOLDING TESTPOINT ( cable set switch in "on" position )
    > 5. press "ready"
    > 6. when prompted detach testpoint
    > 7. press "ready"
    > 8. install drivers from dist\drivers\USBFlash_driver\ ( if asked )
    > إن شاء الله phone will be unlocked.
    > q:
    > how to unlock s1 android based phones, based on qsd8x55, using alternative security bypass using testpoint?
    > a:
    > Here is procedure.
    > 1.
    > prepare for testpoint operation.
    > check testpoint location for your phone model in dist\docs\
    > open testpoint for access
    > get some needle with wire, connect it to phone gnd ( battery minus ) or to usb cable shield, etc.
    > 2.
    > select proper phone model.
    > select USB as interface.
    > on settings check signed mode, use alternative security bypass, do full unlock instead usercode reset
    > fill login/password and check if account valid.
    > press unlock
    > when prompted, execute steps in EXACT order:
    > 1. remove cable from phone,
    > 2. remove battery from phone,
    > 3. attach testpoint
    > 4. press "ready"
    > 5. insert cable to phone, HOLDING TESTPOINT
    > 6. install drivers from dist\drivers\USBFlash_driver\
    >    make sure that driver for qhusb_dload ( device, which will appear after successful testpoint ) is installed from dist\drivers\usbflash_drivers and named "ZEUS Flash Device".
    >    Install driver manually, if testpoint driver named otherwise.
    > 7. when prompted detach testpoint
    > 8. press "ready"
    > إن شاء الله phone will be unlocked.

    Reply With Quote

16. ## The Following 154 Users Say Thank You to the_laser For This Useful Post:

    > ..::HITU::.., .:Zulfiqar:., @@@_@@@, Aamir Zia, ABI-GSM, abuqatadh, adilosse, akaygsm, amr_ibrahim, anasshe, Arenas, arthur, as8088, ayubalikhan, aztech, ban_alven, Beermenâ„¢, bigboy85, bluerays, bouchach1980, cavalierks, cellplus, cheikh-gsm, chepito892, chronic0128, cilian, clueless_gsm, coolmfarshard, dadybo, Dayline668, dimetri, djlangel, DR_MOOSAVI, EIGY, ekvinoks, electrolandgsm, F@RUK S, FARZIN-GSM, hamidraja, hari setyawan, hasni 02, hatrun, hijena81, homeros10, icejack, iki, iqa_shaheen, irfanamin2, jawad8305, jeanbrume, Jupz83, kanwalgee, koperta4512, kris.sg, LIKI, M-taheri, maremestera, Master_X, mcalister, mianjabbar, minotaur, mnaouar, mobail.saba, Mr1X, myrwok, nasirns, nomy7, nori2007, omar, orobas, petrmo, Pizz, prasath_max, protons, psa47, raazimobile, raie, reignsmart, Rhyan, ROpa-SK, rosendohl13, rumisunqu, SALES121, sassa, SE MAN, sed, serpas007, shami, sharaz191, SHOEB AHMED, shonarga_baradi, simlock, soil2020, SOSHAN, spyrakosa, sravan, sudsud, sumatera, tontonflach, werbert, wrecks, wuwei, xXx, xxxman, y3kt, yassinov, yjese, zcorpion10, zombie1982

17. 08-23-2011, 01:35 PM #9
    the_laser
    - View Profile
    - View Forum Posts
    - Private Message
    Administrator

    Join Date
      Feb 2010
    Posts
      18,785

    ##

    > q:
    > my semc 8x55-based smartphone can't be detected by PC or detecting as "QHUSB_DLOAD".
    > my semc 7227-based smartphone can't be detected by PC.
    > my semc 8250-based smartphone can't be detected by PC.
    > a:
    > at least semc boot damaged
    > step I.
    > for 8x55-based phones select USB as interface, then
    > 1. pda tab, select corresponding phone model
    > 2. options tab, check : signed mode, alternative security bypass
    > 3. pda tab, press "recovery"
    > for 7227,8250-based phones select COM as interface, then
    > 1. pda tab, select corresponding phone model
    > 2. options tab, check : signed mode, alternative security bypass, use testpoint ("GND" type)
    > 3. pda tab, press "recovery"
    > important notice:
    > for msm7227 phones, insert battery in phone after you attached testpoint.
    > for x10 phone connect RED dot to GND permanently during entire testpoint procedure
    > if you get next output
    > Code:

    >     MINOR ERROR [ MISC_CLASS: MISC_ERROR, TA_invalid,_format_may_be_required ]
    >     MINOR ERROR [ MISC_CLASS: MISC_ERROR, TA_invalid,_format_may_be_required ]

    > and do not have trim area backup, thats bad, but you still can fix phone : check next post
    > step II.
    > 1. pda tab, select corresponding model
    > 2. options tab, check : signed mode
    > 3. pda tab, add needed firmware files ( DO NOT UNPACK ) ( BOTH APP and FSP) to fw area
    > 4. press "flash"
    > q:
    > during second stage of testpoint unlock procedure i made testpoint wrong/disconnect phone/etc - my phone dead, but i have security units backup.
    > a:
    > that can be fixed easy enough.
    > step I.
    > for 8x55-based phones select USB as interface, then
    > 1. pda tab, select corresponding phone model
    > 2. options tab, check : signed mode, alternative security bypass
    > 3. pda tab, press "recovery"
    > for 7227,8250-based phones select COM as interface, then
    > 1. pda tab, select corresponding phone model
    > 2. options tab, check : signed mode, alternative security bypass, use testpoint ("GND" type)
    > 3. pda tab, press "recovery"
    > if you will get output like
    > Code:

    >     MINOR ERROR [ MISC_CLASS: MISC_ERROR, TA_invalid,_format_may_be_required ]
    >     MINOR ERROR [ MISC_CLASS: MISC_ERROR, TA_invalid,_format_may_be_required ]

    > then and only then perform next step, otherwise skip to step IV
    > step II.
    > 1. pda tab, select corresponding model
    > 2. options tab, check : signed mode, alternative security bypass, format gdfs during write
    > for 7227,8250-based phones select COM as interface and
    > 2. options tab, check : signed mode, alternative security bypass, use testpoint ("GND" type), format gdfs during write
    > 3. pda tab, select trim area package files for your phone model ( DO NOT UNPACK, DO NOT UNZIP, DO NOT TOUCH IT IN ANY WAY ) in misc. edit
    > 4. press "write gdfs"
    > step III.
    > 1. pda tab, select corresponding model
    > 2. options tab, check : signed mode, alternative security bypass
    > for 7227,8250-based phones select COM as interface and
    > 2. options tab, check : signed mode, alternative security bypass, use testpoint ("GND" type), format gdfs during write
    > 3. pda tab, select YOUR BACKUP SCRIPT
    > 4. press "write script"
    > step IV.
    > 1. pda tab, select corresponding model
    > 2. options tab, check : signed mode
    > 3. pda tab, add needed firmware files ( DO NOT UNPACK ) ( BOTH APP and FSP) to fw area
    > 4. press "flash"

    Reply With Quote

18. ## The Following 58 Users Say Thank You to the_laser For This Useful Post:

    > adilosse, agentot, alex_030385, as8088, aztech, ban_alven, beto251172, cellplus, cilian, damha2nd, Dayline668, DemiMontana, dimetri, doctor_asangsm, fraz, hari setyawan, hasni 02, himihicham, I am Back, ikkks1, Jupz83, kennethtse, kiman, koperta4512, Lancer93, MA7MOD_GSM, magicphone1, maremestera, marvz_tech, Master_X, mcalister, myrwok, prasath_max, raazimobile, raju0657, Rhyan, sapari, SeTool.net, shonarga_baradi, soil2020, syswind, werbert, xXx

19. 10-23-2011, 08:32 PM #10
    the_laser
    - View Profile
    - View Forum Posts
    - Private Message
    Administrator

    Join Date
      Feb 2010
    Posts
      18,785

    ##

    > q:
    > how to repair totally damaged s1 android phones, based on msm7227,qsd8250, using alternative security bypass using testpoint?
    > a:
    > Here is procedure.
    > okay, here is example how to resurrect totally dead x10 phone.
    > so, we have x10 phone with totally erased semcboot and trim area.
    > phone does not turn on, does not connect to pc anyhow.
    > lets resurrect it.
    > run setool2, select x10 as model, select com port as interface
    > ( one where GPG resurrection cables connected )
    > 1.
    > on options set signed mode,altbypass mode, use testpoint (gnd type)
    > 2.
    > connect GPG x10 resurrection craddle to phone, press RECOVERY
    > follow program instructions.
    > important notice:
    > for msm7227 phones, insert battery in phone after you attached testpoint.
    > for x10 phone connect RED dot to GND permanently during all testpoint procedure
    > btw, as phone has erased semcboot, you do not need apply testpoint that time.
    > however, that is very special case, so for simplicity lets apply testpoint all time.
    > here is operation output:
    > Code:

    >     SIGNED MODE (USING SERVER)
    >     ALTERNATIVE SECURITY BYPASS ENABLED
    >     CFG:110010000010

    >     DETACH USB CABLE FROM PHONE
    >     REMOVE BATTERY FROM PHONE
    >     ATTACH TESTPOINT
    >     ATTACH USB CABLE TO PHONE,THEN PRESS "READY"

    >     PROCESSING ...
    >     REMOVE TESTPOINT NOW, THEN PRESS "READY"

    >     RUNNING S1_LOADER VER "R4A024"
    >     SWITCHING TO "USB" ...
    >     PLEASE ATTACH TURNED OFF PHONE NOW

    >     RUNNING S1_LOADER VER "R4A024"
    >     LOADER AID: 0001
    >     FLASH ID: "002C/00B3"
    >     LOADER VERSION: "r4A024"

    >     WRITING SEMCBOOT ...
    >     Checking TA ...
    >     MINOR ERROR [ MISC_CLASS: MISC_ERROR, TA_set_config_failed ]
    >     Writing config ...
    >     MINOR ERROR [ MISC_CLASS: MISC_ERROR, TA_invalid,_format_may_be_required ]
    >     Formatting ...
    >     Checking MISC TA ...
    >     MINOR ERROR [ MISC_CLASS: MISC_ERROR, TA_invalid,_format_may_be_required ]
    >     Writing config ...
    >     MINOR ERROR [ MISC_CLASS: MISC_ERROR, TA_invalid,_format_may_be_required ]
    >     Formatting ...
    >     SUCCESS

    > now we recovered semcboot and prepared trim area for loading.
    > if phone only had erased semcboot, it will already work after that step.
    > but our phone TOTALLY damaged, so lets proceed with second step:
    > we need now load trim area.
    > Please skip this step, if your phone do not have damaged trim area ( errors like: "TA_invalid,_format_may_be_required" )
    > options are same for step1 + "format gdfs when writing" checked,
    > select x10.zip in misc.edit and press "write gdfs".
    > ( any trim area, read from corresponding model live phone will work )
    > follow program instructions.
    > here is operation output:
    > Code:

    >     SIGNED MODE (USING SERVER)
    >     ALTERNATIVE SECURITY BYPASS ENABLED
    >     CFG:110010000110
    >     Will write GDFS now.

    >     DETACH USB CABLE FROM PHONE
    >     REMOVE BATTERY FROM PHONE
    >     ATTACH TESTPOINT
    >     ATTACH USB CABLE TO PHONE,THEN PRESS "READY"

    >     PROCESSING ...
    >     REMOVE TESTPOINT NOW, THEN PRESS "READY"

    >     RUNNING S1_LOADER VER "R4A024"
    >     SWITCHING TO "USB" ...
    >     PLEASE ATTACH TURNED OFF PHONE NOW

    >     RUNNING S1_LOADER VER "R4A024"
    >     LOADER AID: 0001
    >     FLASH ID: "002C/00B3"
    >     LOADER VERSION: "r4A024"

    >     Can't get IMEI
    >     will write 1010 units
    >     done
    >     will write 53 units
    >     done
    >     Phone detached
    >     Elapsed: 23 secs.

    > finally, we need rebuild imei and security zone.
    > for that, check same options as for step1 + "do full unlock instead of usercode reset","allow to change imei when unlocking" checked,
    > press "unlock/repair", follow program instructions
    > here is operation output:
    > Code:

    >     THAT ACTION IS ILLEGAL,IF YOU DOING IT
    >     FOR ANY PURPOSE, OTHER THAN REPAIR PHONE

    >     SIGNED MODE (USING SERVER)
    >     ALTERNATIVE SECURITY BYPASS ENABLED
    >     CFG:110010010010

    >     DETACH USB CABLE FROM PHONE
    >     REMOVE BATTERY FROM PHONE
    >     ATTACH TESTPOINT
    >     ATTACH USB CABLE TO PHONE,THEN PRESS "READY"

    >     PROCESSING ...
    >     REMOVE TESTPOINT NOW, THEN PRESS "READY"

    >     RUNNING S1_LOADER VER "R4A024"
    >     SWITCHING TO "USB" ...
    >     PLEASE ATTACH TURNED OFF PHONE NOW

    >     RUNNING S1_LOADER VER "R4A024"
    >     LOADER AID: 0001
    >     FLASH ID: "002C/00B3"
    >     LOADER VERSION: "r4A024"

    >     Can't get IMEI
    >     REQUESTED : 359419030xxxxx
    >     Checking for HWConfig ...
    >     Waiting for calculation process ...
    >     RESPONSE: "SUCCESS" [826]
    >     Checking for signature ...
    >     signature found, skipping calculation
    >     WRITING SEMCBOOT ...
    >     WRITING HWCONFIG ...
    >     Unlock DONE
    >     Elapsed: 20 secs.

    > from now on, phone is full repaired, testpoint cradle not needed.
    > reflash phone with any suitable firmware.
    > q:
    > how to repair totally damaged s1 android phones, based on qsd8x55, using alternative security bypass using testpoint?
    > a:
    > operation is very same, just select usb as interface and do not check "use testpoint (gnd type)"

    Reply With Quote

20. ## The Following 85 Users Say Thank You to the_laser For This Useful Post:

    > .:Zulfiqar:., adilosse, AL-NAJAT, ali586, allal123, ban_alven, cellplus, cilian, coolmfarshard, Dayline668, DemiMontana, dimetri, DjAlfskie07, DjaniB, Douhal, DR_MOOSAVI, falah1, foo_men, gsmsikar, hari setyawan, hasni 02, himihicham, I am Back, irfan99, Jupz83, kenjiyan9128, kiro, koperta4512, M-taheri, magicphone1, mamo_mogon03, mcalister, meysam.karaji, mimounts, mobile mart, mobitec, myrwok, nelsky, prasath_max, protons, raazimobile, Rhyan, rosta01, shami, SHOEB AHMED, shonarga_baradi, soil2020, sravan, subrata, werbert, Xtreme, xXx, xxxman, yjese, zcorpion10

Page 1 of 2 1 2 Last

- Jump to page:

Quick Navigation F.A.Q. Top

- Site Areas
- Settings
- Private Messages
- Subscriptions
- Who's Online
- Search Forums
- Forums Home
- Forums
- SETool2 Official support (English)
  1. News & Updates
  2. F.A.Q.
- HMD Tool Official support (English)
  1. News & Updates
- Other
  1. Offtopic & Trash

« Previous Thread | Next Thread »

#### Similar Threads

1. ###### HOW TO WORK WITH A2-BASED PHONES

   By the_laser in forum F.A.Q.
   Replies: 6
   Last Post: 04-27-2012, 05:11 PM

2. ###### HOW TO WORK WITH SEMC ODM PHONES

   By the_laser in forum F.A.Q.
   Replies: 7
   Last Post: 03-25-2011, 05:03 PM

3. ###### HOW TO WORK WITH A1-BASED PHONES

   By the_laser in forum F.A.Q.
   Replies: 5
   Last Post: 02-06-2010, 09:04 PM

#### Bookmarks

- Digg
- Google
- del.icio.us
- StumbleUpon

#### Posting Permissions

- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts

- BB code is On
- Smilies are On
- [IMG] code is On
- [VIDEO] code is On
- HTML code is Off

Forum Rules