Develop Bugs

my tytn is dead!!! plss help!!!

i have been lookin' around to find help to unlock my tytn. Unfortunately everything i have done with the instructions found here were not helpful!
i do have a HTC Tytn with the following version:
ROM version: 1.18.260.2
ROM date: 07/22/06
Radio version: 1.03.03.10
Protocol version: 32.34.7010.01H
ExtROM version: 1.18.260.105
Model: HERM200
IMEI: 357719006002855
I’m using a XP Home Edition, 2002 version, and for some reason the HTC_Hermes_SIM_CID_Unlock_v3a does not start automatically.
I’ve tried already the manual steps and on the tri-colour screen appears 1.09.ds (which i guess is the bootloader) and if i connect the phone to the pc by the USB cable does nothing! Then i must reset, so that it can start up and i'm able to run the RUU_Hermes.... and appears an error (200): invalid update tool. Although the error is different from the one u mention on the forum i ignore and carry on with the process.
i run Herm_Unlock, click unlock and check both boxes to unlock (sim/cid) wait and seen the success message.
i soft reset or turn off and turn on with a diferent sim card (from another company) and appears a new message saying "u have tried 13 times, plz wait until the waiting time will be exceed..." (did I exceed the number of time permitted?) and from there, there is nothing i can do!!! Neither put the code: 22051978 as u mentioned in ur forum because the OK button is unavailable!!!!
I’ve tried many times and the last one has yesterday at around 11am until this morning nothing happen. This message does stills there!!!!!!!
i am sorry for been so long but i really need ur very usefullll helppppppp.
thankssssss so much!!!!!!!!!!!!!!!!!!!!
waiting for ur replay!!!!
chears,
MESO-HTC

Cannot boot

Hi all,
I tried to flash new rom and the usb connection was broken while flashing.
Now my TP2 can not boot anymore.
I tried to hard-reset, but it did not work, can someone help me ?
I got this while booting:
RUNNBH
RHOD100 32MB SS-BC
SPL-0.85.OliNex
MicroP(LED) 0x0A
MicroP(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
511U536 708ROM2code error
802, 19D122 Please try again
216,846 Calibrated
(PLEASE SEE ATTACHED PICTURE - My error is SPL-0.85.Olinex instead of 000 in this picture)

hold your vol down button while reseting your device, then you should get to the bootloader and from there you can use task29 and then reflash your rom

Muhownage said:
hold your vol down button while reseting your device, then you should get to the bootloader and from there you can use task29 and then reflash your rom
Click to expand...
Click to collapse
Thanks God... and thank you... It seems working... will update the result soon.

WORKED !!! GOOD GOOD !!!
Thank you very much...
Stay in touch if you want...
Yahoo ID: nguyenngochieuthuan
Skype: nnhthuan
Google talk: [email protected]

Just would like to share after searching on xda-dev
i think the error says
"Upgrade ROM code error
Please try again "
try this and see if it works.
1. Download orginal rom from HTC.com
2. Remove HTC Battery
3. Remove SD-Card
3. Connect the Phone to USB-Computer
4. Start-up the phone in the Tree-color screen
5. If everything is right, in the bottom you will see USB
6. Start-up the update on your computer (rom you've downloaded from htc.com)
7. Run the Update
8. Your phone will boot after it succesfull install
9. Place the battery and SD-Cart back in the Phone

Enter BOOTLOADER mode
Hi,
A video how to enter the bootloader mode: HERE

Makes perfect sense to me. If you broke the USB connection, it didn't finish flashing the ROM. So it has nothing to boot. Same thing if you hard reset, there is nothing to hard reset too, if the ROM is messed up. But as long as you can get into bootloader, you can flash the ROM and recover.

bigchrizzieboy said:
Hi,
A video how to enter the bootloader mode: HERE
Click to expand...
Click to collapse
Thanks for your video. It's useful.

can't do anything from bootloader screen
I have been flashing ROMs for years, so not a total noob. For some reason, after running task29, rhodium won't connect to pc via activesync. I can enter bootloader and it says 'usb', however. I tried flashing ROM from SD card, but stays stuck in bootloader screen and goes nowhere. Please help?

[Q - Solved ] Error while flashing Moto Defy: internal error while programming phone

Hi dears
this is my first thread please help
I already flash and updated my Moto Defy to 2.2.2 with RSD lite 4.9 but i got problem with android market, that not work and I could not find a solution.
Then I try to factory reset but also not work , so I decide to back to 2.1 I install this ROM http://sbf.droid-developers.org/umt...SAJORDANRTGB_P035_A011_HWp3_Service1FF.sbf.gz
after flashing was completed my phone do not show any thing, no boot loader and recover work, just show white light over screen.
I'm try to flash again with different ROMs but RSD show error " internal error while programming phone " what does mean? is it bricked? or battery is low? any way to back or solve? should I bring to Motorola branch to fix it? I'm worry please help me.

Did you originally upgrade from 2.1 to 2.2.2 using RSD Lite. If so then you have lost downgradeability and cannot go back to 2.1.
A blank screen with the LED is a classic sign of this - don't worry I don't think the phone is bricked. Does RSD Lite still see your phone? If so then try and flash the 2.2.2 rom again and get the phone working again, then deal with the market problem.
Hopefully you have not flashed a Rom with a version 2.3 cos then you can't get back to 2.2.

Thank you for giving me some hope.
I was originally upgrade before 2.2.2, but my last upgrade was UK 2.2.2
mediafire.com/?op47dv8yo8iypj1 JRDNEM_U3_3.4.2_177-003_BLUR_SIGN_SIGNED_USAJRDNEMARAB1B8RTGB03A.0R_PDS03C_USAJRDNFRYORTGB_P019_A010_HWp3_Service1FF.sbf.gz that I got problem with Market.
Yes, the RSD Lite recognize my phone:
Status: connected...
IMEI/ESN/MEID: N / A
Technology: N / A
Software Version: N / A
Flex Version: N / A
Bootloader Version: v0x000910
DRM Version: N / A
AP Die ID: 25200317107660010000d8ff0100
BP Die ID: 0000000000000000000000000000
AP Public ID: 5c0f7ecc5488162da654c922a1d426cf543db4c9
BP Public ID: 0000000000000000000000000000000000000000
to make sure now I'm charging the battery with a universal charger, I will try to flash again.

Problem Solved.
OK! I solve my problem.
I would like to explain what did …. After charging the phone battery to I try to flash my phone again but no hope! I had same error before I got “ internal error while programming phone ”.
So I decide to find other way to flash, because RSD Lite not work for this issue.
I find out that can flash my Moto Defy trough Linux ” Ubuntu “, I run CD version of Ubuntu 10.04 and flow tutorial using sbf_flash app.
sbf_flash Download: blog.opticaldelusion.org/2011/02/sbfflash-updates.html
Use Terminal:
[email protected]:~$ chmod +x /media/90D07C6FD07C5D82/Motorola_Defy/sbf_flash
[email protected]:~$ sudo /media/90D07C6FD07C5D82/Motorola_Defy/sbf_flash /media/90D07C6FD07C5D82/Motorola_Defy/JRDNEM_U3_3.4.2_177-005_NORDIC_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTNORD_P003_A001_HWp3_Service1FF.sbf
SBF FLASH 1.23 (mbm)
opticaldelusion.org
=== JRDNEM_U3_3.4.2_177-005_NORDIC_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTNORD_P003_A001_HWp3_Service1FF.sbf ===
Index[1]: Unexpected chip 32
….
00: RDL03 0x82000000-0x8204CFFF 4035 AP
01: CG31 0xB0280000-0xB02847FF 9A68 AP
….
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> uploading CG31: 100.0%
-- OK
….
>> verifying CG31
-- OK
….
>> rebooting
[email protected]:~$
Then Finish! Every things Back!
But still I have my province problem, that android market show force close message “ Error downloading “…appname..”There is insufficient space on the device. ” but I have 10 GB free on my SD card!
Any suggestion please?

I moved many alps to SD card, and remove android market catch memory and unistall market update. so now I don't have error but when I tach bottom to download, download not start and bottom disabled. please given. me some suggest. should I factory reset? also I have to say that before I flash my defy. the factory reset do not work also hard factory reset!

My Market Problem also solved with hard factory reset!

Very interesting that you got it back to life using linux instead of rsd lite. Not long ago I had a problem where I couldn't get the phone back to life using rsd and took it to Motorola who charged me for a new motherboard but I wonder if your method may have worked, guess I'll never know. But good to know for next time, thanks for posting your solution.

aren't there any other methods to solve this problem with RSD lite? i've got the same problem. THX
EDIT: solved mine too after flashing JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf.gz under RSD lite and after JORDN_U3_97.21.51.sbf

S8500 stuck at Bada screen

I hope someone can help me. I tried almost everything. My wave just won't boot normally. It all started when I tried to downgrade from Bada 2.0 (S8500XPKH3) to 1.2 (S8500XXJL2) and got a security port error while flashing (used Multiloader 5.65). My wave wouldn't boot up so I got someone to repair it with JTAG. Good thing it was revived. It can now go to download mode, however, i tried flashing almost all firmware versions (Bada 1.0, 1.2, 2.0) in different regions from samfirmware but to no avail.
I browsed through the forums hoping I can get an answer but I didn't see any similar case. I'm sure I'm doing the flashing right 'coz I get "All files complete." when flashing is done. Only that, every firmware that I try, it just stays in the logo screen when it starts up.
I'm looking forward for any response.
Best regards.

I guessed you have done all well. But still try this process:
1. Download a fresh, full and original firmware for your region from samMobile.com
(The firmware version does not matter, but it has to be full and for your region).
2. Make sure your battery is fully charged
3. Remove SIM and memory card from phone.
4. Ensure that all kies drivers are successfully installed.
5. Use multiLoader v5.65
6. Cross-check that your USB plug is not damaged (if possible use another one)
7. When flashing, make sure you tick the FULL DOWNLOAD option in multiLoader.
Try the above and report back. Best of luck.

yeah you should tick boot change and full download for a complete fresh installation

Good thing it was revived
Click to expand...
Click to collapse
Depend on how it was repaired via JTAG...
Maybe NV items are overwritten... this could be bad.
It is not the best idea to use Fullflash from others...
I have RIFF Box experiences...
Best Regards
P.S.:
Try to flash some Rsrc2_S8500(Mid).rc2
Maybe Bluescreen tell you what is missing...

adfree said:
Depend on how it was repaired via JTAG...
Maybe NV items are overwritten... this could be bad.
It is not the best idea to use Fullflash from others...
I have RIFF Box experiences...
Best Regards
P.S.:
Try to flash some Rsrc2_S8500(Mid).rc2
Maybe Bluescreen tell you what is missing...
Click to expand...
Click to collapse
Thanks for the tips guys. I tried the routine checking. I've also tried different a different pc. Same thing.
I'm more inclined to this adfree. NV items might be corrupted. I just know the basics of flashing.I tried several Rsrc2_s8500 (Mid) and yes I got a blue screen with details. I don't know how to interpret it myself but I remember there was IMEI not active. Will post the details later. Hope you or someone can share your thoughts.
Best regards.

I tried S8500XPKH3 again with Rsrc2_S8500(Mid).rc2 and I got this from Multiloader 5.65:
Download Start Ch[0]
BootLoader 1703.9KB OK[0.7s]
Dbl 281.5KB OK[0.8s]
Wait reset !!
Amss 12740.3KB OK[5.0s]
Apps 26214.4KB OK[12.3s]
Rsrc1 37748.7KB OK[14.4s]
Rsrc2 2884.3KB OK[1.3s]
FFS 49217.5KB OK[111.8s]
CSC 36085.8KB OK[106.0s]
SHPAPP 203259.9KB OK[368.3s]
All files complete[638.0s]
Phone reboots and comes up with blue screen:
S/W version: S8500+XP+KH3
Modem: Q6270B-KPRBL-1.5.45t
SHP: VPP R5 2.1.1
Build Host: S1-AGENT08
Build At: 2011/08/16 20:56:16
Aoo Debug Level: 0
ASSERTION_ASSERT: 0 failed. (file SysSecureBoot.c, line 4193) BoAn4193
<Call stack information>
PC = 4000C8D3 OemDumpRegister
LR = 4000C8D7 OemDumpRegister
<Mocha Task Call stack>
_SysAssertReport
__SysSecBootReadNetLockInfoFromFile
ALL HW Information:
HW VERSION: S8500_rev07
IMEI VERSION: Not Active
RF CAL DATE: Not Active
Bad Block Information:
nNumBMPs: 0
nAge: 0
Run Time Bad Block Occurred:
Init BMPs - 2, Current BMPs = 0
Nucleus Task Information:
Running Task name - Mocha Slices = 0000001E Wait = 00000000
Signal = 00000000 Priority = 0
I've been working on this for a week now but no matter what firmware I flash, i can't get my wave to boot normally

Try qualcomm tools to activate imei
ask Adfree or use google to find the qualcomm tools program and then make your imei active using your pc.
what region was your 8500 originally?
remember that different region firmware use different boot files.
Try to use the boot files that was on your wave originally.

For some reason, it's showing "IMEI not active" when I get the blue screen after flashing with Rsrc2_S8500(Mid).rc2.
I read adfree's qualcomm tools guide and it was more on editing the product code. And, i can't access the configuration mode/hidden menu since I can't boot the phone normally.

IMEI is NV item 550 and ...
But it is secured by...
I have never tried on S8500...
Lost IMEI is enough evidence, that NV items are corrupt/missing/damaged...
I'll try to analyze your Error message...
.. will report later.
Best Regards
Edit 1...
SysSecureBoot
SysSecBootReadNetLockInfoFromFile
Click to expand...
Click to collapse
Maybe also Netlock? So maybe without IMEI Security check failes...

I think the guy who tried to resurrect my phone was using JTAG Medusa. Is there any possibility something went wrong during the process? I was just happy that the phone can go on download mode but didn't expect that whichever firmware I try, phone is just stuck on logo.
With regard to the IMEI, should i recover it, will it have a good chance to fix the problem? Can i use qualcomm tools even if the phone can only run on download mode?

if use medusa make this erase full flash after that write full from support stop writ flash in 6% in flash procedure after this flash full flash all files with boot after this pach wit z3x pachv2.Repair imei and al by ok
tested with s8500 whoo come in donload mode with 3 butons vol - lock and power
in first when try flash bada 1.0 soft after ffs write in screen see missing fota 2.0 please instal instal bada 1.2 after this

@OP:
Your SysSec data, which is closely related to NvData, has been damaged, probably by JTAG ovewrite. These data are encrypted by device-unique key.
It is possible to repair it without JTAG, through modified FOTA. But I don't think I'm the one to try this. Last time I played with that data I damaged my BL3. :\

Thanks for those who provided their insights. I kind of gave up last week and had to bring my phone to the service center. Fortunately or not, the tech had to replace the motherboard which cost around 170 USD including the "repair fee". My phone's back with a new motherboard and ready for some risky flashing again. Hehe.
Anyway, thanks again guys. Good day to y'all!

full erase flash only 6% from full after thath full flash with orginal flasher now read wit rj45 cable with z3x nvm from phone in 550 string see if imei is 359321654 need write 8a31391256 and write in phone now imei ok or select in z3x i 5500 put orginal imei and sn repair all come good and working
after all ok read full again from phone search s8500 and see you detail if need edit as your orginal string
ЄЇ~GT-S8500............їµ±№....................................TMU.....2010-06-01....АМАз±Х..................S8500BOJE7_TMOJE7...564C......9750......86210000114318......KAC007021M(S8500)...-

During my plays with RIFF JTAG and few stupid experiments with full erase I'm now facing same problem...
Strange, but this happens with my own JTAG dump...
Will see how long I need to repair this...
Best Regards

It seems no good idea to be. To erase whole NAND via JTAG...
Anyway... long time and luck... I was able to bypass Boot Cycle and then to Restore NV items via QPST...
Maybe 1 part of solution is, to use Firmware BOJE7 with Bootloader XXJEE...
Then maybe your handset start...
Now you can access menu to change to Qualcomm Diag Port for restoring NV items...
Best Regards

[Q] Help with unbricking XPeria Play r800i

Good day all,
I've recently done something rather stupid, and any assistance in reviving my r800i (bootloader locked, but network unlocked, was locked to Network Three UK before I unlocked it using Omnius Suite) What has happened is this, I had bought credits for Omnius to debrand my phone from Three UK so that I could use the phone with T-Mobile or Vodafone. This worked great, but I also wanted to unlock the bootloader so that I could use Flashtool for replacing Gingerbread 2.3.4 (Sony Stock version) with something like ICS or even CyanogenMod. Why I pressed the button in Omnius to repair s1 boot is beyond me, but it happened and now I have a completely bricked Xperia Play.
The phone will not enter recovery mode via the Back button + USB cable, and I cannot power up the phone at all. No initial vibrate or any LED / Display activity at all. It is essentially a plastic brick. The good news is, that I can still place the phone into Testpoint mode using the standard method for XPeria Play models. Doing this allows Omnius to identify my model log which is listed below:
Code:
Action journal
14:26:56 Identify
14:26:56 Shows detailed information about the connected phone.
14:26:56 Operating system: Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 64-bit
14:26:56 Application version: 1.38.4753
14:26:56 . The action name is 'Identification'
14:26:56 Selected phone type: R800
14:26:56 Selected connection method: USB ROM
14:26:56 i Instructions
14:26:56 i 1. Make sure the phone battery is charged to at least 50%.
14:26:56 i 2. Switch off the phone!
14:26:56 i 3. Remove the phone battery and wait at least 5 seconds, then insert the battery back to the phone!
14:26:56 i 4. Connect the testpoint to phone's ground (battery negative pole, metallic circuit shielding, GND) and leave it connected!
14:26:56 i 5. Shortly press the power button!
14:26:56 i 6. Disconnect the testpoint!
14:26:56 i 7. Connect the cable to the phone!
14:26:56 [picture]
14:26:56 . The action started waiting for the user
14:27:22 . The action finished waiting for the user
14:27:22 Connecting via Zeus USB Flash Device (USB1)...
14:27:22 Device driver version: 2.2.0.5
14:27:22 Qualcomm ROM ID: 06010100900000
14:27:22 Sending loader...
14:27:23 Waiting for loader response...
14:27:23 . The action started waiting for the user
14:27:24 . The action finished waiting for the user
14:27:24 Connecting via SEMC USB Flash Device (USB1)...
14:27:24 Device driver version: 3.0.0.0
14:27:24 Detected chipset: MSM7X30
14:27:24 Boot mode: ROM
14:27:24 Device ID: F9C9A248EBDBBE1B509F0D36326DE55E352776BF
14:27:24 Minimum loader AID: 0001
14:27:24 Phone rooting status is unknown.
14:27:24 Sending loader...
14:27:24 Waiting for loader response...
14:27:25 Phone model (from TA): R800i
14:27:25 Current CXC (from TA): 1245-8821_4.0.2.A.0.42
14:27:25 Current CDA (from TA): 1247-6199_R7D
14:27:25 Current FS (from TA): WORLD-1-8_4.0.2.A.0.42
14:27:25 i The phone is not locked to a network.
14:27:25 i Simlock origin: Unknown simlock origin, EC4B6B4A38BDDC0476229B3FB58222216CB21193
14:27:25 s Successfully done.
14:27:25 . The action entered shutdown phase
14:27:25 . The action reported success
Additional details
---
2F B4 6E 69 5C EB 9C F5 36 FD 40 C1 3A DB D8 84
D9 94
---
Obviously I think that my stupid action of hitting the 'Repair S1 Boot' action has overwritten the boot partition of my phone, but with it being Simlocked with origin unknown, prevents the phone from firing up. As mentioned earlier, I can't even enter recovery mode to reflash the stock software from Sony using PC Companion or SUS (downloaded also). The phone is recognized as ZEUS USB Flash device when I enter TP, but using any other method of powering up the phone via recovery buttons etc. do nothing.
So I would really appreciate any kind of assistance that I can have in getting my phone back up again. I've installed all of the following tools onto my PC. I'm running Windows 7 64bit incase there's issues with driver compatability.
a) SETool2 (no Smartcard or box though)
b) Remote USB Client.
c) Teamviewer 7
d) Omnius Suite
e) S1Tool
f) Octopus (without box)
Many thanks people, your help is greatly appreciated.
Paul.

Maybe this is the final decision, flash ur XPlay using Flashtool.
After that doing from step by step very carefully.

Take a look at this may need to pm dev http://forum.xda-developers.com/showthread.php?t=1252038

tallman43 said:
Take a look at this may need to pm dev http://forum.xda-developers.com/showthread.php?t=1252038
Click to expand...
Click to collapse
Many thanks for the link, I've PM'd Alejandrissimo with details etc.

APEXnow said:
Many thanks for the link, I've PM'd Alejandrissimo with details etc.
Click to expand...
Click to collapse
No prob's let us know how you get on:fingers-crossed:

Hi folks,
Unfortunately, I am still in the same situation. I've attempted to PM and email contact alejandrissimo but I've had no response so I assume that they're unavailable or not online. Is there anybody available that has the SETools with the box available that would help me out in repairing the s1 boot area of my phone?
Any help would be greatly appreciated as I'm struggling without my phone presently.
Thanks,
Paul.

APEXnow said:
Hi folks,
Unfortunately, I am still in the same situation. I've attempted to PM and email contact alejandrissimo but I've had no response so I assume that they're unavailable or not online. Is there anybody available that has the SETools with the box available that would help me out in repairing the s1 boot area of my phone?
Any help would be greatly appreciated as I'm struggling without my phone presently.
Thanks,
Paul.
Click to expand...
Click to collapse
Really alejandrissimo is really busy. Make sure your online when he gets on (Mexico timeframe). Hes the only one who use SETools and he has second knowledge about xperias. Sorry contact him again and make sure you add him in gtalk.

chery2k said:
Really alejandrissimo is really busy. Make sure your online when he gets on (Mexico timeframe). Hes the only one who use SETools and he has second knowledge about xperias. Sorry contact him again and make sure you add him in gtalk.
Click to expand...
Click to collapse
Brilliant, many thanks for that. He's emailed me to add gtalk contact so I'll sort that out today. Much appreciated
Paul

Have you tried to flash .ftf via flashtool?
Sent from my R800i using xda app-developers app

olokos said:
Have you tried to flash .ftf via flashtool?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
It can't be flashed that way because the phone will not respond to plugging the USB cable in while holding the Back button. It will only fire up into Testpoint mode and that's it.
Paul.

I am so happy!!! Alejandro, you are one in a million my friend, one in a million. Fixed my phone, refreshed the OS, and unlocked the bootloader all in the spate of an hour, including my dodgy tweeser handywork for Testpoint. Seriously, thank you so much my friend, you've made me a happy man!. Top marks!
100% Recommended
Paul.

APEXnow said:
I am so happy!!! Alejandro, you are one in a million my friend, one in a million. Fixed my phone, refreshed the OS, and unlocked the bootloader all in the spate of an hour, including my dodgy tweeser handywork for Testpoint. Seriously, thank you so much my friend, you've made me a happy man!. Top marks!
100% Recommended
Paul.
Click to expand...
Click to collapse
Glad to see it workedYep like you said one in a million.

help me i bricked my xperia r800i ..same problem with you