Let's start over... shall we?
First, thanks to Bin4ry and NielDK for initial fix. This is the sequel if their work in another thread.
The fix will be considered complete when it'll be able to revive all phones: non-booting and radio-bricked, and enables fastboot on simlocked phones!
===
I think that SIM-lock is not signed anymore after bootloader unlock. If it was, then phone wouldn't boot even after flashing simlock.ta, because SE phones with bad/unsigned/damaged SIM-lock don't boot.
simlock.ta converted to ASCII:
Code:
���������������������
���
������������������������
����������������������4OP_ID="108";OP_NAME="Customized";CDA_NR="1241-4091";��� �00101-*���������������
������������������������
������������������������
������������������������
���������������������������������������������������������
Operator: 001-01-* meaning it's simlocked.
SIM-locked 7DA unit:
Code:
d—FÀB„›ü‡ÞydØ¥¾‡q�
���
–ƒµâMMCß!2P€®> Ö÷êBY(wêÿÕÄ«�l³V)v*‡f¨Ê˜¶ü¶½l©���
ÛðÔŠ�v–-|›SöíS«Ë±ë‘ ׌€Ò/pÀ»®uKؘ*[Eá c}ëÈø%£8�DOP_ID="162";OP_NAME="Rogers";CDA_NR="1247-6276";ROOTING_ALLOWED="0";�CSERVERID="bmcsecs01";AUTHCERT="UNKNOWN";TIMESTAMP="110412 01:30:10" �00101-*������302720-*�����������
—êFk#Üä¯y'?¶…ª˜ (êÚ÷’(xø¶âƒM¥Â*ßÙõ�WÝÈØ*„���
‘2=Ôs#8÷kÚŸœ"í IÙèhO®{à’¥ª|B΃iÃǹֶ
E„B[=—b���
t¼²föb±8§®@IjÚœ�\ ŽDR¦Sp"<¢ç¯‚¶í̽Ú)ïhâ+xÕ_‰���
`’ÇkùÁ|v�yìòYç_6Q qL¶`* Ý0©ª-©`\wŒPL(@™,ήjæþþ”*�6636209799586744������������������������ È‚V"s7Ïæw93æ=àFz¿~9Í¡®gÙÄ.??
Note the ROOTING_ALLOWED=0.
BL unlocked and working:
Code:
wñMpjEZ÷îlBÀ3øÛ^�
���
�¤*‘ƒ¡<i_{<Ž(B-Kÿà (?Dð/;©c$™ùÀ
˯¤uœ º;`”’`o²¨éG���
¤m ¶.úÑ
!°_Zª|ã_ »go£°TçðgDivT0½KH�RÍíý‡³e‚˜ãÿ�‘OP_ID="435";OP_NAME="Customized";CDA_NR="1247-6199";ROOTING_ALLOWED="1";;RCK_H="654E9886B5ECE33DDB814F5C7DC2D502FC07FBD1A872A013748964FC5D8281ED"CSERVERID="bmcsecs01";AUTHCERT="UNKNOWN";TIMESTAMP="110325 08:24:03"���
ÒÞ,€†ÌÓtda”qæmºØTrà ¦ôää¥ÌÆ-çý¤àŸ{¦l)N5ÑFÓ°{R“ùSÓ���
“m
F‡¡²ŽD¹$ìw‚v³µÑ´æ @ãKˆx¾®7à¡¥‚ûknóÚPÎ?í˜ø/“É`N8���
ºDJ6¿´”…¬yVfWÕ³d ‡*Ñ@ãõÝÊØ^ãPGsŸÜ½€nD_ŽF°€Ù¯|���
×|`ˆß9‰à¼ãö*e|°eM½ ”0cœêÕúlªÛž«3Z¼3€ùy*™rôsþðÑE+����������������˜Ä.9ÿY±º'ƒJÙ?" ƒä??
simlock.ta doesn't say is rooting allowed or not, so BL won't allow it.
Click to expand...
Click to collapse
TA Misc, 8FD from bricked, fastboot off, no network:
ta = 000008FD 00 00 00 00 05 00 00 00 03 00 00 00 08 00 00 00
TA Misc, 8FD from BL unlocked and BL locked device fully working:
ta = 000008FD 00 00 00 00 05 00 00 00 03 00 00 00 08 00 00 00
TA Misc, 8FD from non-booting phone:
ta = 000008FD 00
TA Misc, 8FD on SIM-locked phone:
ta = 000008FD 00
TA Misc, FreeXperia Team's fix:
000008FD 00 00
That's strange, on factory-fastboot-capable phones 8FD is same though one has got fastboot, and other not, and bricked fb capable and SIM-locked has got the same 8FD.
Looks like there is something in 8FD, but fastboot capability is somewhere else in TA Misc (partition 02).
FYI, TA Misc is where we should look for. 7DA is simlock unit and it might be worth investigating.
Click to expand...
Click to collapse
nice m8,, I would like to help but my phone's bootloader is unlocked and fully working.
I can only wish you luck
You got PM.
And thanks everyone for so good response!!!
Check the first post for update.
Do you now have everything you need?
Or is it a play locked to an original vendor you still need?
Thanks for looking in to this btw... if you need any help just shout
Best of luck!
Code:
Action journal
13:21:22 Identifier
13:21:22 Affiche des informations détaillées sur le téléphone connecté.
13:21:22 Systeme d'exploitation: Microsoft Windows 7 Ultimate Edition (build 7600), 64-bit
13:21:22 Version de l'application: 0.19.3593 (beta)
13:21:22 . Le nom de l'action est 'Identification'
13:21:22 Selectionnez le modele du telephone: Xperia™ PLAY
13:21:22 Selectionnez la methode de connexion: USB EROM
13:21:22 i Instructions
13:21:22 i 1. Assurez vous que le telephone est chargee au moins jusqu'a 50%.
13:21:22 i 2. Eteindre le telephone!
13:21:22 i 3. Enlever la batterie du telephone et attendre au moins 5 secondes avant de la remettre!
13:21:22 i 4. Appuyez et maintenez retourner au bouton precedent, puis connectez le cable au telephone!
13:21:22 . Action commence, en attente de l'utilisateur
13:22:20 . Action termine, en attente de l'utilisateur
13:22:20 Se connecte via SEMC USB Flash Peripherique (USB9)...
13:22:20 Version des pilotes peripheriques
13:22:20 Chipset detecte: MSM7X30
13:22:20 Boot mode: EROM
13:22:20 EROM version: 1241-3656 R9A021
13:22:20 IMEI:
13:22:20 ID de périphérique: 096EEC99EAD9606F592934A175B40131F690E47D
13:22:20 Chargement minimum AID: 0001
13:22:20 Couleur: Rouge SEMC
13:22:20 Envoi du chargement en cours...
13:22:20 Reponse du chargement en attente
13:22:22 Modele du Telephone (depuis TA): R800i
13:22:22 Courant CXC (depuis TA): 1245-8821_3.0.A.2.184
13:22:22 Courant CDA (depuis TA): 1247-6199_R6C
13:22:22 Courant FS (depuis TA): WORLD-1-8_3.0.A.2.184
13:22:22 Le telephone n'est pas verouille sur un reseau.
13:22:22 s Effectue avec succes.
13:22:22 . L'action est en phase d'arret
13:22:22 . L'action a ete realise avec succes
hi my phone is repair with tft tool and fatgsm for sim and fastboot disabled
ty
Check your PM
Sent from my R800i using XDA Premium App
I'll remind everybody that has this issue, that i have created a bounty for this problem.
If blagus fixes this, please donate some money, so he can buy a beer or two.
After all, he's doing us all a huge favour, if he fix it.
Good luck
waz000000 said:
whilst i don't want to take anything away from blagus for when he manages to help sort this don't forget everyone else along the way that made getting this far possible! and some even sacrificing their own to help!
Click to expand...
Click to collapse
Oh, sorry waz.
Ofcourse, I know u also have contributed alot asswell. (NielDK and Bin4ry also)
Thanks to you guys, all the bricked play's are working.
And i know u fuxxord your phone trying to help, so it's noted and remembered.
ill be writing back my TA backup tonight when i get home from work and will see if it locks my bootloader again
Right i flashed back my "locked" TA and can confirm it did "not" lock the bootloader again.
Wasnt going to unlock this one either :'(
So there is no progress?
waz000000 said:
Right i flashed back my "locked" TA and can confirm it did "not" lock the bootloader again.
Wasnt going to unlock this one either :'(
Click to expand...
Click to collapse
It WILL relock bootloader, but you need license!
Sent from my X8 using XDA App
Blagus said:
It WILL relock bootloader, but you need license!
Sent from my X8 using XDA App
Click to expand...
Click to collapse
I would count myself as pretty stupid if i didn't realise that but just for you to prove it WONT! re lock it
Code:
Action journal
21:28:54 Restore TA
21:28:54 Allows to restore the TA (Trim Area) content.
21:28:54 Operating system: Microsoft Windows XP Media Center Edition Service Pack 3 (build 2600)
21:28:54 Application version: 0.20.3622 (beta)
21:28:54 . The action name is 'Restore TA'
21:28:54 Selected phone type: Xperia™ PLAY
21:28:54 Selected connection method: USB EROM
21:28:54 i Instructions
21:28:54 i 1. Make sure the phone battery is charged to at least 50%.
21:28:54 i 2. Switch off the phone!
21:28:54 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
21:28:54 i 4. Press and hold the return back button, then connect the cable to the phone!
21:28:54 . The action started waiting for the user
21:29:02 . The action finished waiting for the user
21:29:02 Connecting via SEMC USB Flash Device (USB3)...
21:29:02 Device driver version: 2.2.0.5
21:29:02 Detected chipset: MSM7X30
21:29:02 Boot mode: EROM
21:29:02 EROM version: 1241-3656 R9A021
21:29:02 REMOVED
21:29:02 Device ID: 398DFEADD33273420EBECF2DE48E75548D851A8D
21:29:02 Minimum loader AID: 0001
21:29:02 Color: Red SEMC
21:29:02 i Waiting for connection to the server...
21:29:11 Receiving news...
21:29:13 i No news
21:29:19 Sending loader...
21:29:19 Waiting for loader response...
21:29:21 Loading data from file: Xperia PLAY_locked_20110518163651_TANormal_TAMisc.opd
21:29:21 Writing TA Normal...
21:29:21 Writing TA Misc...
21:29:22 s Successfully done.
21:29:22 . The action entered shutdown phase
21:29:22 . The action reported success
---
and to prove i have a license:
Code:
Action journal
21:31:26 User account details
21:31:26 Checks connection to server and shows the details about your user account.
21:31:26 Operating system: Microsoft Windows XP Media Center Edition Service Pack 3 (build 2600)
21:31:26 Application version: 0.20.3622 (beta)
21:31:26 . The action name is 'Info'
21:31:26 i Waiting for connection to the server...
21:31:32 Receiving news...
21:31:34 i No news
21:31:36 Current time licences
21:31:36 i Omnius Full 1 Day
21:31:36 i One day license for unlocking and flashing
21:31:36 i State: The licence is active
21:31:36 i Valid since 2011-May-21 09:31 until 2011-May-22 11:31
21:31:36 Credit info
21:31:36 i Supreme Credit
21:31:36 i Disponible amount: 0.00
21:31:36 i Locked amount: 0.00
21:31:36 i Used amount: 0.00
21:31:36 s Successfully done.
21:31:36 . The action entered shutdown phase
21:31:36 . The action reported success
Uploaded with ImageShack.us
-post deleted-
Blagus, do you think you'll be able to acquire a Play/Arc/Neo anytime soon? It'd probably speed up development, wouldn't it? Perhaps something could be done about acquiring it... a bit of help from the community's side?
Blagus said:
Hmm, it's strange, because with unlocked bootloader TA Misc area is smaller than with locked.
With SIM-locked phone TA Misc is also full of hashes, and much larger that on SIM-free phone.
And with simlock.ta file, Simlock unit was overwritten (07DA in TA Misc), so I'm not sure if something could be done about it (for free), but let's hope for the best
Click to expand...
Click to collapse
hope so would be good, I did some checking on the locked and unlocked ones myself and there are differnces according to the HEX the only thing i can think of is that omnius tool is able to backup at the moment but doesnt support writing back "properly" just yet.
waz000000 said:
hope so would be good, I did some checking on the locked and unlocked ones myself and there are differnces according to the HEX the only thing i can think of is that omnius tool is able to backup at the moment but doesnt support writing back "properly" just yet.
Click to expand...
Click to collapse
here i have decrypted opd backup in hex very similar to simlock.ta file's format, but i need to chat with Bin4ry about that and some other stuff... still waiting for his reply... it shouldn't be hard to implement this file support in FlashTool since fxtool and this one are almost identical (address:hex style)...
Sent from my X8 using XDA App
Related
Hi guys, think i've bricked up my x10
after SEUS update the phone wont boot.. it vibrates on power but then stays black.
tried to reflash using the SEUS..
SEUS "recognizes" the phone (says "firmware already installed blabla.. reflash?) but at the flash progress it hangs at the beginning and finally aborts with an error message.
any ideas?
This might work.
tried the flashtool too.. no success
log:
28/041/2011 21:41:26 - ERROR - Please plug you device in flash mode
28/041/2011 21:41:27 - INFO - Searching Xperia....
28/041/2011 21:41:27 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&284A1E07&0&5
28/041/2011 21:41:27 - INFO - Start Flashing
28/041/2011 21:41:27 - INFO - VER="R8A013";DATE="20100119";TIME="17:24:00";
28/041/2011 21:41:27 - INFO - Flashing loader
28/042/2011 21:42:33 - INFO -
28/046/2011 21:46:55 - INFO - Flashing kernel.sin
28/048/2011 21:48:10 - ERROR - Error flashing. Aborted
28/048/2011 21:48:10 - INFO - Now unplug the device and power it on
28/048/2011 21:48:10 - INFO - Then go to application settings
28/048/2011 21:48:10 - INFO - turn on Unknown Sources and Debugging
just tried the omnious for se v0.20 flasher.. same result
log:
Action journal
22:30:16 Flash
22:30:16 Allows to change languages supported by the phone and upgrade its firmware.
22:30:16 Operating system: Microsoft Windows XP Professional Service Pack 2 (build 2600)
22:30:16 Application version: 0.20.3728 (beta)
22:30:16 . The action name is 'Flash'
22:30:16 Selected phone type: Xperia™ X10
22:30:16 i Instructions
22:30:16 i 1. Make sure the phone battery is charged to at least 50%.
22:30:16 i 2. Switch off the phone!
22:30:16 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
22:30:16 i 4. Press and hold the return back button, then connect the cable to the phone!
22:30:16 . The action started waiting for the user
22:30:31 . The action finished waiting for the user
22:30:31 Connecting via SEMC USB Flash Device (USB1)...
22:30:31 Device driver version: 2.2.0.5
22:30:31 Detected chipset: QSD8250
22:30:31 Boot mode: EROM
22:30:31 IMEI: 35941903911402
22:30:31 Sending loader...
22:40:18 e Failed!
22:40:18 . The action entered shutdown phase
22:40:18 . The action reported failure
Error code
# FEF0FA7628628BE2
Error details
---
6E 4B 0E AC 0D 8F E5 78 57 5C C8 E9 35 0A CD 05
FF EE E1 9C 03 D2 1B 5F 59 BE 49 60 E2 A1 63 F7
B1 6A E1 B5 BD 4E 7B 96 F7 C6 E7 54 95 F8 E5 8B
31 07 7F 7C 6D 28 21 90 98 0F 47 6D BB A6 C3 3A
F1 30 F6 46 4D 8F DB 48 69 F8 0D 96 71 9E A3 21
C1 3A DF AE 9B 52 4C 2D 49 63 89 AC 5B CC 90 25
D5 23 5F E0 83 72 C5 26 C9 EE 59 B8 63 FD C0 73
---
Flash stock 1.6 rom with flash tools and all will be good
Sent from my HD2 using XDA App
another problem occurs.. its seems, that the battery wont be charged anymore.
i wanted to try the 1.6 stock but i cant "boot" up in the flashmode.
i press the "back"-button then plugin the usbchord but no green led..insted the red led blinks up every ~2sec for a short period.
blmn1337 said:
another problem occurs.. its seems, that the battery wont be charged anymore.
i wanted to try the 1.6 stock but i cant "boot" up in the flashmode.
i press the "back"-button then plugin the usbchord but no green led..insted the red led blinks up every ~2sec for a short period.
Click to expand...
Click to collapse
Red LED means that battery is drained, should wait and charge battery without booting and you should be fine. If it still doesn't charge then buy a new battery.
it's working again
i think it was a battery charging problem.
plugged in for charging in the morning and when i got home, the system was booted up and the battery fully charged.
now everything is normal again.
thx for support, mates
i found out, that the battery is charged normally.
the problem happened again.
when holding power on it vibrates and nothing else.. black screen, no bootup logo, no background-light
halp pls
Did you sort this I had the same problem
sent with a geordie kiss using wb 2.3.3
1.download the global 2.1 stock flashable file
2.put it inside your firmware folder in flash tool folder
3.dont connect ur phone
4.hit flash and select the global firmware and wait till the flash tool ask u to connect ur phone
5.now remove ur phone battery
6.connect usb cable into ur phone with the battery is removed and now press and hold the back button on ur phone and insert the battery
I had the same problem and I fixed it using the above procedure.
All the best buddy...
runaway_bunny said:
1.download the global 2.1 stock flashable file
2.put it inside your firmware folder in flash tool folder
3.dont connect ur phone
4.hit flash and select the global firmware and wait till the flash tool ask u to connect ur phone
5.now remove ur phone battery
6.connect usb cable into ur phone with the battery is removed and now press and hold the back button on ur phone and insert the battery
I had the same problem and I fixed it using the above procedure.
All the best buddy...
Click to expand...
Click to collapse
i've tried but doesn't work for me.. not able to flash anything
still have the problem
Hi is there a way I can bypass the "emergency call" screen for xperia x10? The phone was bricked after unsuccessful upgrade to 2.3.3. I was able to load 1.6 back (using flash tool and forum instructions), but now phone is stuck in Emergency Call Only screen. SEUS is not helping either, always getting the message that the SW is up to date ( however, still running 1.6). Attempted to flash with 2.1 and suggested baseband combo with no luck, x10 just wont boots at all. With 2.3.3 it goes in to constant bootloops.
The other weird thing is, is when I push the Emergency Call button and the dial pad pops up I can press and hold the back button and instantly I can get a glimpse of my actual menu but in that same second it flips back to the emergency call only page??? Super frustrating so please any and all advice would be greatly appreciated.
Me first....wrong section...
PS in SEUS (Or PCCompanion) allthough it says up to date, you can still hit update anyway and it will fix it
brutus* said:
Hi is there a way I can bypass the "emergency call" screen for xperia x10? The phone was bricked after unsuccessful upgrade to 2.3.3. I was able to load 1.6 back (using flash tool and forum instructions), but now phone is stuck in Emergency Call Only screen. SEUS is not helping either, always getting the message that the SW is up to date ( however, still running 1.6). Attempted to flash with 2.1 and suggested baseband combo with no luck, x10 just wont boots at all. With 2.3.3 it goes in to constant bootloops.
The other weird thing is, is when I push the Emergency Call button and the dial pad pops up I can press and hold the back button and instantly I can get a glimpse of my actual menu but in that same second it flips back to the emergency call only page??? Super frustrating so please any and all advice would be greatly appreciated.
Click to expand...
Click to collapse
standalone SEUS comes up with following message (see attached) there is no option available to hit update .One more thing from X10 service menu the SIMLOCK status is unknown....
I"ve attached service menu screenshots for your reference
Pick a firmware you want, 2.3.3 se ect, pull the battery on the phone, use FLASHtool, set up ur ftf files, start flashtool, connect usb to phone, put battery back in while holding back key down, flashing should begin.
P.S... MAKE SURE YOU HAVE FULL FIRMWARE FTF WITH KERNEL...
Best regards,
Chris
OK,
Before you try the method above this post try getting back to stock...
So, make sure you update SEUS (Uninstall and reinstall from SE site) and try again.
If that does not work, try the same thing with PCCompanion.
Thanks Chris,
It goes in to constant boot_loops with 2.3.3 and 2.1.71 baseband
---------- Post added at 12:07 PM ---------- Previous post was at 12:06 PM ----------
Thanks gregbradley,
Already tried with few PC's, still no luck
brutus* said:
Thanks Chris,
It goes in to constant boot_loops with 2.3.3 and 2.1.71 baseband
---------- Post added at 12:07 PM ---------- Previous post was at 12:06 PM ----------
Thanks gregbradley,
Already tried with few PC's, still no luck
Click to expand...
Click to collapse
Hmmm...Can you tell me what baseband you are on and kernel
EDIT: and lets move this to PM's only please.
I wont help further in this thread...please PM me
This is the wrong section....check your PM's or start it again in the Q&A section
Flash 2.1 x10 A firmware... ur phone mst be simlockd ... so first unlock ur simlockd phone after upgrading to 2.1 n then unlock ur bootloader... then upgrade it to 2.3
Sent from my X10i using XDA Premium App
phone is stuck in Emergency Call Only screen and I cant check the kernel rev. enable "USB debugging" and etc. Please have a look at attached service menu screen shots
---------- Post added at 12:24 PM ---------- Previous post was at 12:18 PM ----------
Thanks varshil,
I've used almost every avalable 2.1 with forum suggested base-bans - still no success, its not even posting SE logo. Can load almost every available 1.6 firmware but stuck in "Emergency Call Only" screen
Please don't replay to this threat its in wrong secton!!
@op post it in Q/A section!!
questionmarks at simlock info indicates damaged security zone.
please download omnius and perform identification.
Sent from my R800i using XDA App
Folks how to move this Thread to appropriate section? Please advice
brutus* said:
Folks how to move this Thread to appropriate section? Please advice
Click to expand...
Click to collapse
Contact a MOD like pilot
what do you mean? I'm new to this forum, can you help?
---------- Post added at 01:48 PM ---------- Previous post was at 01:33 PM ----------
ID dump from omnius
Code:
Action journal
13:39:41 Identify
13:39:41 Shows detailed information about the connected phone.
13:39:41 Operating system: Microsoft Windows XP Professional Service Pack 2 (build 2600)
13:39:41 Application version: 0.23.3995
13:39:41 . The action name is 'Identification'
13:39:41 Selected phone type: Xperia™ X10
13:39:41 Selected connection method: USB EROM
13:39:41 i Instructions
13:39:41 i 1. Make sure the phone battery is charged to at least 50%.
13:39:41 i 2. Switch off the phone!
13:39:41 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
13:39:41 i 4. Press and hold the return back button, then connect the cable to the phone!
13:39:41 . The action started waiting for the user
13:44:26 . The action finished waiting for the user
13:44:26 Connecting via SEMC USB Flash Device (USB2)...
13:44:26 Device driver version: 2.2.0.5
13:44:26 Detected chipset: QSD8250
13:44:26 Boot mode: EROM
13:44:26 EROM version: 1226-2253 LDS_QC_091023_1547_ISO
13:44:27 IMEI: 004401**********
13:44:27 Device ID: 5ADCE7D20F347C598A4D10C3271747B301A128CE
13:44:27 Minimum loader AID: 0002
13:44:27 Minimum software AID: 0001
13:44:27 Minimum EROM AID: 0001
13:44:27 Minimum customization AID: 0001
13:44:27 Minimum simlock AID: 0001
13:44:27 Serial number: CB511CWD9Q
13:44:27 Color: Brown
13:44:27 Phone model (from TA): X10a
13:44:27 Current CXC (from TA): 1227-4612_R1FA014
13:44:27 Current CDA (from TA): 1233-6929_R11A
13:44:27 Current FS (from TA): 1227-4607_R1FA014
13:44:27 e Failed!
13:44:27 . The action entered shutdown phase
13:44:27 . The action reported failure
Error code
# BC19D7F412BB5D61
Error details
---
3A E5 D1 81 28 3E E4 73 3E 27 47 6A 3E C9 EC 9E
FA F4 70 CF 05 54 5A EA CE 05 E8 7B 55 42 FC 1C
96 1E CE 20 66 01 FC 1D 5E 3A D8 EB E2 72 7D 82
74 5C B0 6F 2A 25 37 11 C3 1D 96 F6 8E 39 E4 81
7F B7 5A 9A E8 40 24 4D 82 81 E5 0E 39 16 82 C4
46 5D 30 05 BB 9C 3E 04 A0 A4 58 B7 92 D3 0D EE
87 8B 8E F3 DA 41 44 5D 9E 15 98 FD 60 AD C2 B5
---
Your phone is prototype, and brown so it's normal you can't update with SEUS. You can find prototype X10 firmware somewhere on this forum.
brutus* said:
what do you mean? I'm new to this forum, can you help?
---------- Post added at 01:48 PM ---------- Previous post was at 01:33 PM ----------
ID dump from omnius
Code:
Action journal
13:39:41 Identify
13:39:41 Shows detailed information about the connected phone.
13:39:41 Operating system: Microsoft Windows XP Professional Service Pack 2 (build 2600)
13:39:41 Application version: 0.23.3995
13:39:41 . The action name is 'Identification'
13:39:41 Selected phone type: Xperia™ X10
13:39:41 Selected connection method: USB EROM
13:39:41 i Instructions
13:39:41 i 1. Make sure the phone battery is charged to at least 50%.
13:39:41 i 2. Switch off the phone!
13:39:41 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
13:39:41 i 4. Press and hold the return back button, then connect the cable to the phone!
13:39:41 . The action started waiting for the user
13:44:26 . The action finished waiting for the user
13:44:26 Connecting via SEMC USB Flash Device (USB2)...
13:44:26 Device driver version: 2.2.0.5
13:44:26 Detected chipset: QSD8250
13:44:26 Boot mode: EROM
13:44:26 EROM version: 1226-2253 LDS_QC_091023_1547_ISO
13:44:27 IMEI: 004401**********
13:44:27 Device ID: 5ADCE7D20F347C598A4D10C3271747B301A128CE
13:44:27 Minimum loader AID: 0002
13:44:27 Minimum software AID: 0001
13:44:27 Minimum EROM AID: 0001
13:44:27 Minimum customization AID: 0001
13:44:27 Minimum simlock AID: 0001
13:44:27 Serial number: CB511CWD9Q
13:44:27 Color: Brown
13:44:27 Phone model (from TA): X10a
13:44:27 Current CXC (from TA): 1227-4612_R1FA014
13:44:27 Current CDA (from TA): 1233-6929_R11A
13:44:27 Current FS (from TA): 1227-4607_R1FA014
13:44:27 e Failed!
13:44:27 . The action entered shutdown phase
13:44:27 . The action reported failure
Error code
# BC19D7F412BB5D61
Error details
---
3A E5 D1 81 28 3E E4 73 3E 27 47 6A 3E C9 EC 9E
FA F4 70 CF 05 54 5A EA CE 05 E8 7B 55 42 FC 1C
96 1E CE 20 66 01 FC 1D 5E 3A D8 EB E2 72 7D 82
74 5C B0 6F 2A 25 37 11 C3 1D 96 F6 8E 39 E4 81
7F B7 5A 9A E8 40 24 4D 82 81 E5 0E 39 16 82 C4
46 5D 30 05 BB 9C 3E 04 A0 A4 58 B7 92 D3 0D EE
87 8B 8E F3 DA 41 44 5D 9E 15 98 FD 60 AD C2 B5
---
Click to expand...
Click to collapse
please delete, thread moved to q&a : http://forum.xda-developers.com/showthread.php?p=17519604#post17519604
Original post was opened in the wrong section and was moved from here: http://forum.xda-developers.com/showthread.php?p=17517279#post17517279
Just updating the new thread
Blagus Your phone is prototype, and brown so it's normal you can't update with SEUS. You can find prototype X10 firmware somewhere on this forum.
Originally Posted by brutus*
what do you mean? I'm new to this forum, can you help?
---------- Post added at 01:48 PM ---------- Previous post was at 01:33 PM ----------
ID dump from omnius
Code:
Action journal
13:39:41 Identify
13:39:41 Shows detailed information about the connected phone.
13:39:41 Operating system: Microsoft Windows XP Professional Service Pack 2 (build 2600)
13:39:41 Application version: 0.23.3995
13:39:41 . The action name is 'Identification'
13:39:41 Selected phone type: Xperia™ X10
13:39:41 Selected connection method: USB EROM
13:39:41 i Instructions
13:39:41 i 1. Make sure the phone battery is charged to at least 50%.
13:39:41 i 2. Switch off the phone!
13:39:41 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
13:39:41 i 4. Press and hold the return back button, then connect the cable to the phone!
13:39:41 . The action started waiting for the user
13:44:26 . The action finished waiting for the user
13:44:26 Connecting via SEMC USB Flash Device (USB2)...
13:44:26 Device driver version: 2.2.0.5
13:44:26 Detected chipset: QSD8250
13:44:26 Boot mode: EROM
13:44:26 EROM version: 1226-2253 LDS_QC_091023_1547_ISO
13:44:27 IMEI: 004401**********
13:44:27 Device ID: 5ADCE7D20F347C598A4D10C3271747B301A128CE
13:44:27 Minimum loader AID: 0002
13:44:27 Minimum software AID: 0001
13:44:27 Minimum EROM AID: 0001
13:44:27 Minimum customization AID: 0001
13:44:27 Minimum simlock AID: 0001
13:44:27 Serial number: CB511CWD9Q
13:44:27 Color: Brown
13:44:27 Phone model (from TA): X10a
13:44:27 Current CXC (from TA): 1227-4612_R1FA014
13:44:27 Current CDA (from TA): 1233-6929_R11A
13:44:27 Current FS (from TA): 1227-4607_R1FA014
13:44:27 e Failed!
13:44:27 . The action entered shutdown phase
13:44:27 . The action reported failure
Error code
# BC19D7F412BB5D61
Error details
---
3A E5 D1 81 28 3E E4 73 3E 27 47 6A 3E C9 EC 9E
FA F4 70 CF 05 54 5A EA CE 05 E8 7B 55 42 FC 1C
96 1E CE 20 66 01 FC 1D 5E 3A D8 EB E2 72 7D 82
74 5C B0 6F 2A 25 37 11 C3 1D 96 F6 8E 39 E4 81
7F B7 5A 9A E8 40 24 4D 82 81 E5 0E 39 16 82 C4
46 5D 30 05 BB 9C 3E 04 A0 A4 58 B7 92 D3 0D EE
87 8B 8E F3 DA 41 44 5D 9E 15 98 FD 60 AD C2 B5
---
Today 01:48 PM
brutus* what do you mean? I'm new to this forum, can you help?
---------- Post added at 01:48 PM ---------- Previous post was at 01:33 PM ----------
ID dump from omnius
Code:
Action journal
13:39:41 Identify
13:39:41 Shows detailed information about the connected phone.
13:39:41 Operating system: Microsoft Windows XP Professional Service Pack 2 (build 2600)
13:39:41 Application version: 0.23.3995
13:39:41 . The action name is 'Identification'
13:39:41 Selected phone type: Xperia™ X10
13:39:41 Selected connection method: USB EROM
13:39:41 i Instructions
13:39:41 i 1. Make sure the phone battery is charged to at least 50%.
13:39:41 i 2. Switch off the phone!
13:39:41 i 3. Remove the phone battery and wait at least 5 seconds before reinserting it!
13:39:41 i 4. Press and hold the return back button, then connect the cable to the phone!
13:39:41 . The action started waiting for the user
13:44:26 . The action finished waiting for the user
13:44:26 Connecting via SEMC USB Flash Device (USB2)...
13:44:26 Device driver version: 2.2.0.5
13:44:26 Detected chipset: QSD8250
13:44:26 Boot mode: EROM
13:44:26 EROM version: 1226-2253 LDS_QC_091023_1547_ISO
13:44:27 IMEI: 004401**********
13:44:27 Device ID: 5ADCE7D20F347C598A4D10C3271747B301A128CE
13:44:27 Minimum loader AID: 0002
13:44:27 Minimum software AID: 0001
13:44:27 Minimum EROM AID: 0001
13:44:27 Minimum customization AID: 0001
13:44:27 Minimum simlock AID: 0001
13:44:27 Serial number: CB511CWD9Q
13:44:27 Color: Brown
13:44:27 Phone model (from TA): X10a
13:44:27 Current CXC (from TA): 1227-4612_R1FA014
13:44:27 Current CDA (from TA): 1233-6929_R11A
13:44:27 Current FS (from TA): 1227-4607_R1FA014
13:44:27 e Failed!
13:44:27 . The action entered shutdown phase
13:44:27 . The action reported failure
Error code
# BC19D7F412BB5D61
Error details
---
3A E5 D1 81 28 3E E4 73 3E 27 47 6A 3E C9 EC 9E
FA F4 70 CF 05 54 5A EA CE 05 E8 7B 55 42 FC 1C
96 1E CE 20 66 01 FC 1D 5E 3A D8 EB E2 72 7D 82
74 5C B0 6F 2A 25 37 11 C3 1D 96 F6 8E 39 E4 81
7F B7 5A 9A E8 40 24 4D 82 81 E5 0E 39 16 82 C4
46 5D 30 05 BB 9C 3E 04 A0 A4 58 B7 92 D3 0D EE
87 8B 8E F3 DA 41 44 5D 9E 15 98 FD 60 AD C2 B5
---
Today 01:24 PM
sahibunlimited
Originally Posted by brutus*
Folks how to move this Thread to appropriate section? Please advice
Contact a MOD like pilot
Today 01:21 PM
brutus* Folks how to move this Thread to appropriate section? Please advice
Today 12:52 PM
Blagus questionmarks at simlock info indicates damaged security zone.
please download omnius and perform identification.
Sent from my R800i using XDA App
Today 12:27 PM
sahibunlimited Please don't replay to this threat its in wrong secton!!
@op post it in Q/A section!!
Today 12:24 PM
brutus* phone is stuck in Emergency Call Only screen and I cant check the kernel rev. enable "USB debugging" and etc. Please have a look at attached service menu screen shots
---------- Post added at 12:24 PM ---------- Previous post was at 12:18 PM ----------
Thanks varshil,
I've used almost every avalable 2.1 with forum suggested base-bans - still no success, its not even posting SE logo. Can load almost every available 1.6 firmware but stuck in "Emergency Call Only" screen
Today 12:13 PM
varshil Flash 2.1 x10 A firmware... ur phone mst be simlockd ... so first unlock ur simlockd phone after upgrading to 2.1 n then unlock ur bootloader... then upgrade it to 2.3
Sent from my X10i using XDA Premium App
Today 12:10 PM
gregbradley
Originally Posted by brutus*
Thanks Chris,
It goes in to constant boot_loops with 2.3.3 and 2.1.71 baseband
---------- Post added at 12:07 PM ---------- Previous post was at 12:06 PM ----------
Thanks gregbradley,
Already tried with few PC's, still no luck
Hmmm...Can you tell me what baseband you are on and kernel
EDIT: and lets move this to PM's only please.
I wont help further in this thread...please PM me
Folks Please help me to find prototype X10 firmware somewhere on this forum
anybody knows how to restore damaged security zone?
I need desperately the prototype software, please help
Operation: Read Codes
Selected model: SM-J710GN
Software version: 29.1
Searching Samsung modem detected COM31
Reading phone info OK
Model SM-J710GN
AP version J710GNDXU1API5
CSC version J710FOJV1APD7
CP version J710GNDXU1API1
Product code SM-J710GZDUXSG
Phone SN RF8HB3F8XDW
Unique number CAJ03EB415FE3A3
Reading IMEI OK
IMEI: 358447076448431 (SIGN: OK)
IMEI 2: 358448076448439 (SIGN: OK)
Please wait, generating hash codes file, this can take few minutes OK
Reading data from phone OK
Modem board SHANNON315
HWID: 0E 05 00 00 00 00 00 00 00 00 00 00 C0 DC 26 54
Reading NV data OK
Checking NV data OK
Calculating OK
Please wait, calculating codes OK (time - 00:00:05)
Freeze code 04208508
NET lock 68285393
SUB lock 00000000
SP lock 00000000
CP lock 00000000
SIM lock 00000000
For check lock status *#7465625#
hope be usefull
Code:
To XDA moderators : There's no sub-forum for these 4 models.
Nokia C2 Tava, Tennen and 2 V Tella are basically same device. Please move this topic when available, thanks.
Hi all,
Recently I got Nokia C2 Tennen and C5 Endi bootloader unlocked again.
If you guess I achieved that by utilizing prototype firmware, then you're right.
However I don't have other retail device to test, anybody would like to give it a try?
I would be definitely interested to try it out. I have a c5 needing bootloader unlock
Legendanubis said:
I would be definitely interested to try it out. I have a c5 needing bootloader unlock
Click to expand...
Click to collapse
Alright.
May I know if you're familiar with operating SP flash tool?
i wouldl love to try it. I have got a locked c2 tava that i am unable to factory reset. A friend brought the phone to me to FRP bypass (bought it cheap from someone that said it just needed to be charged, gave a false pin and here we are) That was a month ago. Im very new to all of this and while ive been studying bootloaders and root i havnt actually had the pleasure. Any advice is welcome on this TA-1218. I cannot find ANYTHING on the EXACT model. All help is appreciated. Thanks
jh
hikari_calyx said:
Alright.
May I know if you're familiar with operating SP flash tool?
Click to expand...
Click to collapse
I am not familiar with it, I currently use bugjaeger to flash my phone's. But would love to get this c5's bootloader unlocked so if I can't use my program to flash I would definitely learn the sp flash tool
Bootloader unlock done with Hydra Tools. Also put a work root and magisk root on as well.
Hydra MediaTeK Tool Ver 1.0.3 Build 77
Windows 10 (Version 10.0, Build 19042, 64-bit Edition)
Intel(R)Core(TM) i5-2410M CPU @ 2.30GHz
Intel(R) HD Graphics 3000
Ram Installed : 4 GB
Windows Access Right : Admin
Software Run As Admnistrator
******* Dongle Info *******
Version : Hydra Tool v 1.20
Serial : [removed]
Initialize : OKAY
Status : Activated
Life : [removed]
=====================================
Searching for MTK Device... Found
Port Identification : Flashmode BROM
FriendlyName : MediaTek USB Port_V1633 (COM10)
Device : 6&13d9c38d&0&3
SymbolicName :\\??\\USB#VID_0E8D&PID_0003#6&13d9c38d&0&3#\[removed]
Driver Ver : 01/22/2015,3.0.1504.0
Opened handle..
Handshaking... Ok
Identifying Hardware ID.....
Reading Device hardware info..
hw code : 0717 MT6761 [6761]
hw subcode : 8A00
hw version : CA01
sw version : 0200
Target config : E3
SBC : 01 (True)
SLA : 02 (True)
DAA : 00 (False)
SWJTAG : 02 (True)
EPP : 00 (False)
CERT : 00 (False)
MEMREAD : 20 (True)
MEMWRITE : 40 (True)
CMD_C8 : 80 (True)
Exploiting Device...
Exploit Sent..
Successfully Exploited...
Handshaking... Ok
\\HydraTool_FullPackage_08-01-2021\backup\\Preloader_dump\\prel.tmp
Handshaking...
Identifying Hardware ID.....
Reading Device hardware info..
hw code : 0717 MT6761 [6761]
hw subcode : 8A00
hw version : CA01
sw version : 0200
Target config : 00
SBC : 00 (False)
SLA : 00 (False)
DAA : 00 (False)
SWJTAG : 00 (False)
EPP : 00 (False)
CERT : 00 (False)
MEMREAD : 00 (False)
MEMWRITE : 00 (False)
CMD_C8 : 00 (False)
MEID : [removed]
Stage 1.. [Size:232216]
Sending : Please wait.. Accepted
Identifying Protocol...
Protocol : New
Synchronization... [ERROR]- NOT SYNC
=============================================
Reasons why it fails due to the following"
1. Harware problem/issues
2. If you did Testpoint Kindly check the parts you Touch/TP
3. Powershortage, try to connect Battery
4. Check or replace usb cable and plug directly to your pc usb port.
=============================================
SYNC
Preloader Initialization...
Parsing prel.tmp
Init : Accepted
Executing : SYNC
Reading Device UniqueID, RAM and Flash Chip Info...
UNIQUE ID : [removed]
ERAM Size : 0x0000000000039000 -228 KB
IRAM Size : 0x0000000080000000 -2 GB
eMMC BOOT1 : 0x0000000000400000 -4 MB
eMMC BOOT2 : 0x0000000000400000 -4 MB
eMMC RPMB : 0x0000000001000000 -16 MB
eMMC USER : 0x0000000747C00000 -29.121 GB
eMMC CID : [removed] - QD63MB
Executing : ACCEPTED...
Reading GPT0 -EMMC [0x00008000] 0 130 Items
0
Autobackup Partitions
-preloader [0x00000000] 512 KB -> preloader.bin...1 Ok0
-> Renaming Preloader.... preloader_armstrong.bin0
Creating Scatter file... \\HydraTool_FullPackage_08-01-2021\\\backup\\Auto\\0717__111921012459\\MT6761_Android_scatter.txt
-pgpt [0x00000000] 8 MB -> pgpt.bin...1 Ok
-frp [0x02D80000] 1024 KB -> frp.bin...1 Ok
-nvdata [0x04E80000] 64 MB -> nvdata.bin...1 Ok
-protect1 [0x0C51A000] 8 MB -> protect1.bin...1 Ok
-protect2 [0x0CD1A000] 10.898 MB -> protect2.bin...1 Ok
-persist [0x0E000000] 48 MB -> persist.bin...1 Ok
-nvram [0x1A900000] 64 MB -> nvram.bin...1 Ok
Done!!!0
\\HydraTool_FullPackage_08-01-2021\\\backup\\Auto\\0717__111921012459
MTK Phone Loader is NOW RUNNING.
Reading Device UniqueID, RAM and Flash Chip Info...
UNIQUE ID : 2 [removed]
ERAM Size : 2 0x0000000000039000 -228 KB
IRAM Size : 2 0x0000000080000000 -2 GB
eMMC BOOT1 : 0x0000000000400000 -4 MB
eMMC BOOT2 : 0x0000000000400000 -4 MB
eMMC RPMB : 0x0000000001000000 -16 MB
eMMC USER : 0x0000000747C00000 -29.121 GB
eMMC CID : [removed] - QD63MB
Reading GPT0 -EMMC [0x00008000] 0 130 Items
-------------------------------------
Operation : Unlock Bootloader
Processing...
-------------------------------
Bootloader Status...
Bootloader : Locked
-------------------------------
Verifying status after operation...
-------------------------------
Bootloader Status...
Bootloader : Unlocked
-------------------------------
Action Result : 0 Ok
Elapsed Time : 00:01:04
(its been a while. i know)
i successfully got my c2 tennen (ta-1218) bootloader unlocked and rooted.
im still running on stock tho.
plus no custom recoveries yet.
Quartzbreaker said:
i wouldl love to try it. I have got a locked c2 tava that i am unable to factory reset. A friend brought the phone to me to FRP bypass (bought it cheap from someone that said it just needed to be charged, gave a false pin and here we are) That was a month ago. Im very new to all of this and while ive been studying bootloaders and root i havnt actually had the pleasure. Any advice is welcome on this TA-1218. I cannot find ANYTHING on the EXACT model. All help is appreciated. Thanks
Click to expand...
Click to collapse
Have you ever found a solution to your problem? Im having same issue and cant seem to find a fix for it.
This may mot be the correct thread and if so please accept my apology but I'm trying to unlock the bootloader for a Moto g pure and neither Motorola or at&t will give the bootloader codes. I saw reference here to sp flash tool and wondered if someone could help me utilizing that. I do not have a desktop or laptop and all I have to work with is mobile. Mtkclient won't run because I can't get PySides6 dependencies to install in Termux. I was able to install NetHunter , the one for no rooted devices, but so far I can't find a way to force flash
hikari_calyx said:
Code:
To XDA moderators : There's no sub-forum for these 4 models.
Nokia C2 Tava, Tennen and 2 V Tella are basically same device. Please move this topic when available, thanks.
Hi all,
Recently I got Nokia C2 Tennen and C5 Endi bootloader unlocked again.
If you guess I achieved that by utilizing prototype firmware, then you're right.
However I don't have other retail device to test, anybody would like to give it a try?
Click to expand...
Click to collapse
SUCCESS! [BOOTLOADER UNLOCK] Nokia C2 Tava TA-1218.
[BOOTLOADER UNLOCK] Nokia C2 Tava TA-1218. I was actually approached by a person from XDA named @Soadeathdealer who gave me remote access to unlock his phone's bootloader. This phone bootloader was successfully unlocked using Unlock Tool which...
forum.xda-developers.com
cagedbadger said:
This may mot be the correct thread and if so please accept my apology but I'm trying to unlock the bootloader for a Moto g pure and neither Motorola or at&t will give the bootloader codes. I saw reference here to sp flash tool and wondered if someone could help me utilizing that. I do not have a desktop or laptop and all I have to work with is mobile. Mtkclient won't run because I can't get PySides6 dependencies to install in Termux. I was able to install NetHunter , the one for no rooted devices, but so far I can't find a way to force flash
Click to expand...
Click to collapse
I don't think the moto g pure has been unlocked yet. At least boost variant.