guys...still having fun trying to unlock my xda...i will get there! been advised to downgrade 6.25.02 radio down to 6.24 radio as XDA UNlock doesnt work on 25...any idea where to download?
Try this:
http://www.lumpistefan.de/tools/RSU_V6.24.20_PPC.zip
But downgrading RSU is very dangerous.....
Stefan
Thanks
Thanks S...it wouldnt let me do it.
http://www.yorch.net/downloads/ROMS/TMOradiostackupgradeR624 .zip
t-mobile RSU 6.25 SIM unlock prolbem, final solution. XDA I
Error getting connection type
Error getting unlocking code
Upgrade RSU (Radio Stack)
RSU 6.25, RSU 6.24
Those are the keywords I have been using for about a day to get to the bottom of unlocking a t-mobile XDA I (siemens SX56).
I have started with being unable to flash the device with Special Edition ROM, then XDAUnlock unable to unlock the device etc..
Thanks to http://lumpistefan.dyndns.org/tools/ , they guy did a great job showing in details how to evenutally unlock this wild device with RSU 6.25. So look no futher, this is the holy grail! :idea:
I'm quoting from Lumpistefan website:
How to unlock your Device ....
The PDA side of the ppcpe and the radio/phone/gsm side are two totally different animals (not a surprise to some). When you refer to the 'operating system' you're talking about the ROM like the XDA Developers special edition or any of the ROMs from the ROM kitchen at http://lumpistefans.dyndns.org/. The Radio or RSU (for Radio Stack UPgrade) is totally separate from this. The other variable is the bootloader version (Wallaby in my case).
Now my goal was just to use the XDAunlock program. When I ran the program right from the defaults I got 'error getting unlock code.' All the posts I read said put on the Special Edition ROM and you'll be fine but that did not do the trick. Still got the same error message.
Here's what I started out with:
ROM: 4.01.16 ENG
Radio: 6.25.02
Wallaby booatloader: 5.22
What finally worked:
Radio: 6.24.00
ROM: 3.17.03 ENG (XDA special edition)
then upgraded back to 4.01.16 ENG
Wallaby boot loader 5.15
How I did it
--------------
I meandered my way through this to eventual success and since the dratted device now works fine I'm leery about putting it all back to the old way and doing it all over again. Therefore use this process as a guide only, not a definitive instruction set. Also I walked through this as a troubleshooting exercise so some steps may not have been necessary. I eventually succeeded but maybe went the long way around to do it.
References
----------
- Bootloader utilities: Get to this by holding down the power button and pressing soft reset. You may have to hit the contacts button to get into the menu if you don't see it right away (like if you see a simple GSM OK message at the bottom of the bootloader display.
- Cold boot: the reset swtich on the right side bottom of the device with a picture of a red battery with an \ through it. This disconnects the batter from the mainboard and trashes all the data on the device except the Operating System in ROM.
What I grabbed
------------------
- XDAtools
- XDArit
- ActiveSync (I used 3.7.1) and connection by USB cable
- Wallaby bootlolader version 5.15 files
- XDA Developers Special Edition ROM
- RSU 6.24.00 files
- XDAUnlock.exe
- SD Card (mine is 128 MB but I think as long as it's bigger than 64MB or your current memory in the device you're OK)
- pnewbootflash_40116.exe
All of these files are available here, just search for them.
First back up everything. Not just using the sda backup tool, from the boot loader. You can do the SD backup if you want, consider it backing up your data. You can also do the ActiveSync backup if you want to save your data.
Second I'm doing ALL of this with no SIM chip in the device. This may or may not be necessary.
Stick your SD card into the PDA. If it complains about wanting to format it go ahead and let it format the card unless you have stuff on it you want. I'd recommend dropping anything you want from the card onto safe media and just working with it as a blank the rest of the way through because it's easier to just wipe the card in between some steps.
Go to the bootloader utilities. Hit Contacts button and you'll get the boot loader option stuff. If the bootloader utilities you get to right away takes you to a menu with things like Boot+CE-->SD then you don't have to worry about hitting the contacts button. You only need Contacts button if when you get to the bootloader screen you see nothing more than some nice colors, the bootloader version and "GSM OK" message.
Take the Boot+CE-->SD option to back everything up. This will take a few minutes.
Once it's done pull the SD out ofthe ppcpe and stick it into your SD card reader. Bring up XDArit and chose your removeable device.
If you have more than one MMC slot select the different ones until you get one that says 'Wallaby' in the hex codes at the bottom of the XDArit screen. You'll be writing out two files, the first is the NB0 file (which is the bootloader) and the second is the NB1 file (which is the OS or ROM). Name these something like original.nb0 and 1.
Wipe the SD card (format FAT). Stick the SD card back into the pda and soft reset, then cradle it.
Go to a DOS prompt and CD to where you put 'pnewbootflash_40116.exe.' Type 'pnewbootflash_40116 nbl515.nb0' to write the Wallaby 5.15 boot loader to the device. If when you downloaded the 5.15 bootloader you called it something else (like 'wallaby_boot_loader_V5.15.nb0' you should of course use that name instead!
The output looks like this:
D:\XDAtools\binaries>pnewbootloader_40116 bl515.nb0
Copying D:\XDAtools\binaries\itsutils.dll to WCE:\windows\itsutils.dll
in FindFlashInfoOffset
protection found at 8c0d60f8
result: 00000000 00000000
Now..why did I downgrade the bootloader? At this stage I'm troubleshooting why I get the 'error getting unlock code' message running XDAunlock. I've got three variables I know of, bootloader, ROM and Radio Stack. I chose to start with the bootloader because some posts out there say boot loaders 5.17 and higher have some checksum that keeps certain ROMS from working properly. Perhaps if I'd started with the radio stack I'd have been done right away and saved a few hours but all the posts about possible device destruction made me start with the bootloader! Again, your results may vary!
Next I changed the ROM to the XDA Developers special edtion.
Make sure the SD card is in the PDA and cradle it. Run OSIMagetool and load the ROM file in the first box, chose SD Card in the second box.
If you downloaded the Special Edition ROM you might have some luck using the Installer that comes with it but apparently that does not work with ActiveSync 3.7.1. I got messages that said it could not access the device or no connection etc. Instead I used OSImageTool to load the NK.NBF file included in the distribution. Note that to get to this file you DO have to unzip the EXE file you download!
Once complete pull the pda out of the cradle.
Hold power+soft reset to get the boot loader menu. This should show up as 5.15 now. It will automatically detect that the SD card contains a ROM that can be flashed to the device. If for some reason it does not automatically detect this maybe you have to hit Contacts. I did not have to do that, it just told me to hit Action to download the ROM.
Hit Action button (aka the jog button) to write it to the device. This will take a few minutes, go grab a beer or two or three. I took the safe route and connected power to the device while writing the flash.
Once it's finished cold boot the device. I waited 2-3 minutes before re-engaging the battery.
Here's a gotcha. On the right side of the SIM there is a little switch. If the rubber door for the SIM is not totally closed you can't get the device to boot. This switch is real small so it's very possible to miss it. You can see it fine if you take the back off the device (which I determined from a post here that told you how to get the battery out).
When it boots you should have the 5.15 Wallaby booting the XDA special edition. Follow the instructions to calibrate the screen and you're ready to move on.
Now if the radio is 6.25.02 XDAunlock won't work, it just generates the 'error getting unlock code' message. You have to downgrade the radio to have this work.
There's lots of posts around here that say don't screw with the radio because if it errors you've got a fried device. I imagine this is true so balance how bad you want to unlock the device against the possibility of totally frying the device. I've done two radio upgrades in my life on the PPCPE, both were OK but again, caution is advised.
Grab the 6.24 radio zip and unzip into a folder on your computer. Use ActiveSync to copy the files to \windows on the device.
Execute the rsupdate.exe program to reprogram the radio to 6.24. WHen completed soft reset the device and go into start-settings-system-device info to make sure you're at 6.24 radio vesion.
Copy the xdaunlock.exe to the device and execute. It should say 'you're device appears to be SIM Locked, would you like to remedy this?" click Yes to unlock the device.
Now the device is unlocked. You can change the ROM to WM2003 now if you want (which I did). I imagine you can re-upgrade your bootloader and radio stack if you want but I'm leaving well enough alone for now!
End
Thanks
DaKanadian
As a result of a failed update (failed at 60%) why Vario II is now not very well. When I power the unit on it hangs on the HTC screen. If I power the unit on and hold the power & OK key to enter the update screen things seem to get better.
The update process starts, the device is recognised, the update starts and on the Vario the screen shows 0% Upgrade, at which point the PC update fails with the 262 Update Error. Prior to the update there is a screen that shows the software version on the device and the upgrade, version, my unit no longer shows any version, it blank.
Any suggestions, is there a way to recover this?
Thanks
a18041967 said:
As a result of a failed update (failed at 60%) why Vario II is now not very well. When I power the unit on it hangs on the HTC screen. If I power the unit on and hold the power & OK key to enter the update screen things seem to get better.
The update process starts, the device is recognised, the update starts and on the Vario the screen shows 0% Upgrade, at which point the PC update fails with the 262 Update Error. Prior to the update there is a screen that shows the software version on the device and the upgrade, version, my unit no longer shows any version, it blank.
Any suggestions, is there a way to recover this?
Thanks
Click to expand...
Click to collapse
Have a look at this error list I posted.
http://forum.xda-developers.com/showthread.php?t=298640
Thanks for the post, I'd done a search and come across the same page, however whatever I do the update fails.
The upgrade appears to be OK, clicking next , next etc the device is recognised, but not version number, every time it gets to the point of uploading the firmware and displaying the % complete it fails, with no progress.
Any other suggestions, is it possible to flash the device using an memory card?
Thanks for any suggestions
UPDATE !!!
I've found the details regarding flashing using SD card (http://wiki.xda-developers.com/index.php?pagename=Hermes_SDCardFlashing) but this seems to be failing.
When the bootloader starts it recognises the SD image, the screen goes white and displays 'Loading' after a few seconds '00068002' in red is displayed and the SPL bootloader screen is displayed.
Further fun and games, I seem to be able to use mtty utility and have sucessfully downgrade to SPL 1.01 and back upto 1.04 neither of which improved the above.
If I'm able to do this, can I use mtty to load OS.nb, if so where can I get hold of a valid OS.nb file for my Vario II
I'm having a mare....my Artemis has died after a hard reset - just sits at bootloader. I can't flash any rom at all using RUU. All cooked roms fail after 3% with a "image corrupt" error and all original roms (wm5 and wm6 for o2 orbit) fail after 5% with "Flash Write" error.
I've also tried flashing from SD card....starts...but then fails on the validating certificate with an "SD FAT error" or sorts.
I know it's probably salvagable as I can get into bootloader....any ideas? People on forums are telling me to unlock using USPL...but because i cant get into the os to get activesync....it won't work.
a simular thing happens to me my one sits in a rgb screen and says ipl 3.04.0001 and spl 3.04.0000. none of the roms i used work ive just decided to leave it. if your ipl and spl is lower than mine i guess you will be more likley to get working again as people with the same ipl and spl as me cant get their one working
Try to go to bootloader and try to use it :
http://forum.xda-developers.com/showthread.php?t=311403
If it work try to flash with any custums roms.
If you don't have this , you only can flash with officials roms. That's why you can't flash with custums roms
Qui-Gon Ginn said:
Try to go to bootloader and try to use it :
http://forum.xda-developers.com/showthread.php?t=311403
If it work try to flash with any custums roms.
If you don't have this , you only can flash with officials roms. That's why you can't flash with custums roms
Click to expand...
Click to collapse
Thanks for this however I;ve been directed to that thread before and each time it's pointless. There is no point me attempting to USPL my device when I can't get an activesync connection due to the fact it has no OS bootable.
As for the official Roms...I've tried the ones that have been touted as official for the Orbit but with no effect.
My IPL SPL is currently 1.25.0001/1.25.0.000 but when i attempt to flash with official rom (!) it moves to the same as spikez - ipl 3.04.0001 and spl 3.04.0000
Anyone with any further help - ordered a new Touch HD but I need to get this one up and running
Thanks
have you tried sd card flash
make sure you put the orignal rom on the root of a none sdhc card (1gb or smaller) and is renamed to "Arteimg.nbh"
official wm5 rom
official wm6 rom
Simply put the phone in bootloader with your 'boot' card inserted and follow the instructions.
Spikez.....I've tried that before. It reads from the SD card....goes through the motions, and then provides an error after about 5-10mins saying "SD FAT update failed"
Any ideas...please reply if only to say "no chance mate"
Thanks for any help you can give me.
i still guess yours is more likely to be fixed than mine as mine just goes straight to the rgb screen can you take a picture of what appears on your screen.
Try use an none offical rom and does your artemis ask you to "update sd image press this key to start download"
unfortunately i've left my digi cam at work I can explain rather well though, bear with me:
I reset the device with SD card in and I get a white screen saying "Checking SD Card" - there is then an arrow asking me to hit volume key to flash...I do that.
I get 5 mins of "Reading from SD" at the bottom of the white screen. Following that I get a "verifying certificate" message and then about 10seconds later a "SD FAT update failed!!!" message...it then just sits there until I press a key on the device and then it falls back to bootloader (multi coloured screen)
this MUST be fixable by somebody who isn't a noob like me - any ideas?
either try add these files into root of sd card
Enterbootloader.exe
rapitool.exe
RomUpdateUtility.exe
RUUGetInfo.exe
RUUREsource.dll
RUU_USPL_Signed.nbh, and
"Arteimg.nbh"
or try once in bootloader plug in usb and try using a ruu
files didn't work...just went straight through to bootloader as opposed to reading SD card. As for launching the RUU through windows...didn't work either. Bombed out after 5% with a "FLASH WRITE " error
Wiggz said:
My IPL SPL is currently 1.25.0001/1.25.0.000 but when i attempt to flash with official rom (!) it moves to the same as spikez - ipl 3.04.0001 and spl 3.04.0000
Thanks
Click to expand...
Click to collapse
as your ipl and spl is so high i guess you may have a Brick i cant seem to get my one working either as i earlier stated it is very common that people with this ipl and spl cant seem to get theirs back working.
spikez93 said:
as your ipl and spl is so high i guess you may have a Brick i cant seem to get my one working either as i earlier stated it is very common that people with this ipl and spl cant seem to get theirs back working.
Click to expand...
Click to collapse
True but as can be seen from that post...mine shifts from 1.25 to 3.04 depending on the flash attempt?
my best suggestion to you is stick with it. Try read through this sign up and post here andrew, bill, [email protected] and noney82 very helpful read through see if that post is any use.
Upgrade to Hard-SPL Olipro 1.20 - USB or SD Just Added SD Card Method at Bottom of this Post
10 Step Program
Pulled from Website dated: Monday August 06, 2007 by ??? if someone knows, I'll give credit.
Recovered and Updated Monday October 27, 2009 by SuperSport
because the WiKi has vanished
Hard SPL will allow you to flash cooked ROMs without SuperCID’ing your device and also will protect your device from being bricked in a bad flash. If a bad flash occurs it should remain in bootloader, and you can re-flash another ROM.
Caution!!! Flashing Hard-SPL will Probably Hard Reset your device!!!! Backup all data FIRST!!!
Before you proceed, check which SPL is on your device:
*** Enter Tri Color Screen ***
--Unplug your phone from USB - Helps to avoid freezing USB Ports
--Hold down the Power & Camera Buttons
--While still holding them down, press the Reset Button using the Stylus
--Release the Reset Button, but continue to hold the Power/Camera buttons until you see the Tri Color Screen
*** Enter Tri Color Screen ***
If your SPL is 1.30.Olipro, 1.20.Olipro, or 9.99 CP, then you already have Hard-SPL on your device and can skip flashing HardSPL, although, I recommend using Olipro 1.20 to avoid problems.
If you want to continue flashing Olipro HardSPL 1.20:
Press the Reset Button using your Stylus. Wait for your phone to start back into Windows. Plug the USB Cable into your phone and PC. Verify ActiveSync or WMDC is connected properly. Now you can Flash.
1. Download "Olipro HardSPL 1.20.zip" in attachment below
2. Unzip the Files, and Run the Program "Olipro HardSPL 1.20.exe" This is a small AutoFlash file I created using Olipro 1.20
3. Windows Vista and Windows 7 may confirm you want to run the program. Choose YES.
4. Check the check box, click ‘Next’
5. Also Check this check box, click ‘Next’
6. In the next window, click the ‘Update’ button
This will show the version number of the ROM, radio, or in this case bootloader that you are about to flash.
7. After the version number has appeared, click 'Next'
8. In the following window, click ‘Next’, your phone may ask if it's ok to run the program, Tap 'Yes'.
(After you click this, the flash will begin, so do not disconnect your device or do anything on your computer)
9. A Progress bar will appear on your computer screen, and your trinity will display a grey screen with progress bar. Be patient while your device is being updated. This will only take a moment.
10. Once your device is finished updating, if it did not automatically soft reset, Press the Reset Button with the Stylus. Click the ‘Finish’ button to exit the RUU program.
To confirm Hard-SPL is on your device, re-enter Tri Color Screen following directions above. You should see the following:
Hard SPL 1.20.Olipro
TRIN100
IPL-0.50 (your device may show IPL-1.00)
TRIN100 MFG
SPL-1.20.Olipro
CONGRATULATIONS!! You have now installed Olipro's Hard-SPL 1.20 on your device using USB Method!! Press the Reset Button with your Stylus to restart.
**********************************
Alternate SD Card Method
**********************************
For those who would rather use their SD Card for this (Maybe your USB Port is not functioning). For this method, the way I'm describing, your phone must be running a version of Windows Mobile. Can be any Version, 5-7. If your phone does not currently run, flash back the OEM ROM that came with it Originally. You can find some in my signature.
Caution!!! Flashing Hard-SPL may Hard Reset your device!!!! Backup all data FIRST!!!
1. Be sure you have a, Non-SDHC, SD Memory Card.
2. Be sure the card is formatted Fat32 and Without a Label.
3. Download the attached HardSPL SD.zip file and extract it's contents. Copy both files, SSPL-TRIN.exe and TRINIMG.nbh, to the Root of your SD Card.
4. On your phone, use File Explorer to browse to the Root of your SD Card.
5. Tap the SSPL-TRIN.exe file. This should run the file.
6. On some phones, you will see a security message come up. Select 'Yes' to run the program.
7. You should now see a Grey screen with Blue Lettering. It will be asking you to Press power button. Go ahead and press the power button.
8. You will see the update progress for a short moment, it will restart, and update again, then show "Update Complete - UPDATE SUCCESS" If you see this message, it has worked.
9. Press the Reset Button with your Stylus to Restart
10. Delete the two files from your SD Card (TRINIMG.nbh, SSPL_TRIN.exe). To confirm Hard-SPL is on your device, Enter Tri Color Screen following directions above. You should see the following:
Hard SPL 1.20.Olipro
TRIN100
IPL-0.50 (your device may show IPL-1.00)
TRIN100 MFG
SPL-1.20.Olipro
CONGRATULATIONS!! You have now installed Olipro's Hard-SPL 1.20 on your device using SD Method!! Press the Reset Button with your Stylus to restart.
Maybe if this could be Stickied?
Thanks, it's a very nice guide for Trinty users, clean and detailed, I also recommand using Olipro 1.20 and not 1.30 to avoid problems, especially with 6.5 roms the annoying "WLAN ERRROR" sometimes seen in bootloader mode ...
Yes, make this "Sticky"
Brds,
nAr
Thanks narshorn! Someone else posted this a long time ago on a WiKi I believe, and I just recovered what I could of the original web page and then rewrote it to work with my files. The original page was removed from it's server, so I grabbed as much of the cached version of it as I could, thus, I don't know who did the original.
Also, thank you for the confirmation of using Olipro 1.20 and not 1.30. That was my belief, and I've heard others, but I'm glad you confirmed.
noob here, need help on flash HardSPL.
i encounter error when trying to update my hardSPL. when i try to flash when my phone is tri color screen mode, this error pop out.
ERROR [270]:UPDATE ERROR
The image file is corrupted. please check your update utility.
info update:
at last i manage to flash my phone to hardspl 1.20, i boot my d810 in normal mode, establish active connection with window, then the flash carry on without any error. but the phone hard reset
but, i wonder y i cant flash to hardspl in tri color screen ???
update to 1.20 spl Olipro true sd card not USB
hi and Thanks for so nice explanation. there is a way to update spl with sd card? my USB connection is faulty. if s/o know please let me know how.
tzuki1 said:
hi and Thanks for so nice explanation. there is a way to update spl with sd card? my USB connection is faulty. if s/o know please let me know how.
Click to expand...
Click to collapse
Just added SD Method to bottom of post #1. Good Luck!
thongkh said:
noob here, need help on flash HardSPL.
i encounter error when trying to update my hardSPL. when i try to flash when my phone is tri color screen mode, this error pop out.
ERROR [270]:UPDATE ERROR
The image file is corrupted. please check your update utility.
info update:
at last i manage to flash my phone to hardspl 1.20, i boot my d810 in normal mode, establish active connection with window, then the flash carry on without any error. but the phone hard reset
but, i wonder y i cant flash to hardspl in tri color screen ???
Click to expand...
Click to collapse
Because stupid me forgot that if you don't have HardSPL on your phone, then TRI COLOR SCREEN flashing is not possible. Doh! FIXED above.
Thank you for bringing this to my attention. When I physically went through the steps, I forgot I still had HardSPL on my phone from previous.
I just went through the steps AGAIN after removing HardSPL, and verifed it works correctly as listed in Post #1.
thankz for promptly reply
btw, what d diff between HardSPL 1.20 and 1.30?
thongkh said:
thankz for promptly reply
btw, what d diff between HardSPL 1.20 and 1.30?
Click to expand...
Click to collapse
I've seen many reports that 1.30 caused issues. Olipro, 'the guy who made our Trinity's safe for Flashing', stopped updating the thread, but if you read it, you will find many users reporting problems and asking for the thread to be updated to go back to 1.20.
I've been using 1.20 since it was released, and have NEVER had a problem with it. And believe me, I Flash a LOT!!! I'm expecting my poor Trinity to catch fire any day now.
Oh... Thx for the tutor...that what i need now...
Good job someone remembered howto
Thanks for the reminder - managed to forget how to enter tri-colour screen in the three months since I last reflashed.
I need help here
I have tried each of the methods.
though your explanation and step by step instructins are very clear, istill can't seem to get Olipro's HSPL on my phone. in the case of using active sync, after it enters the tri color screen nothing happens again and the i get an error message (ERROR 260).
When i tried using the SD method, when i tapped the SSPL_TRIN file, it goes stright to the tri color screen ths is the information i have there
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
and for this reason i can seem to flash any rom with success each time it only gets to the tri colou screen and i get the ERROR 260 message.
Anyone with any idea on how i can fix this.
thanks in advance
redoxy said:
I need help here
I have tried each of the methods.
though your explanation and step by step instructins are very clear, istill can't seem to get Olipro's HSPL on my phone. in the case of using active sync, after it enters the tri color screen nothing happens again and the i get an error message (ERROR 260).
When i tried using the SD method, when i tapped the SSPL_TRIN file, it goes stright to the tri color screen ths is the information i have there
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
and for this reason i can seem to flash any rom with success each time it only gets to the tri colou screen and i get the ERROR 260 message.
Anyone with any idea on how i can fix this.
thanks in advance
Click to expand...
Click to collapse
Did you copy the TRINIMG.nbh file to your SD Card also? Was your SD Card formatted FAT32 and No Label?
Using the SD Method, you do not need to be connected to your Computer. Copy both files to SD and do all work from phone.
Let me know if that works or not.
Remove the HARDSPL...
Hi,
How can I remove the HARDSPL from my Trinity and go back to the original?! Thanks!
sergiopedro said:
Hi,
How can I remove the HARDSPL from my Trinity and go back to the original?! Thanks!
Click to expand...
Click to collapse
Only do this if you do not plan to flash any more Custom ROMs, and would like to stick with the OEM ROM (You may Brick your Phone if you flash from the Stock SPL):
Download the "HardSPL SD.zip " file from the first post.
Extract the files
Copy ONLY the "SSPL_TRIN.exe" file to your SD Card.
Run the "SSPL_TRIN.exe" file from your SD Card (This puts your phone into a special mode that will allow the HardSPL to be overwritten)
Now, your phone should be in bootloader mode with:
TRIN100
IPL_SSPL by Des
TRIN100
SPL_1.07.ds
At this point, you can flash your OEM ROM that includes the Original SPL and IPL.
I use this one: http://www.mediafire.com/?v5yjt1zvgjm
Hi all
I have tried to flash with usb but i'm having a problem
i'm using active sync and after i click 'execute' at the mobile screen it enters the tri color screen and it disconnects the usb port. I get an error message (ERROR 246) that says the device is not responding.
I've tryed several times and it has the same behavior...
The tricolor screen shows this message:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
i havent try the sd method because i dont have a sd card right now...
Thank you
rcpamr said:
Hi all
I have tried to flash with usb but i'm having a problem
i'm using active sync and after i click 'execute' at the mobile screen it enters the tri color screen and it disconnects the usb port. I get an error message (ERROR 246) that says the device is not responding.
I've tryed several times and it has the same behavior...
The tricolor screen shows this message:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
i havent try the sd method because i dont have a sd card right now...
Thank you
Click to expand...
Click to collapse
Your mobile screen is showing the correct information, with the exception of USB not showing. As soon as you get to the Tri Color Screen, try removing then reconnecting the USB connection and see if that makes any difference.
Also, when the Tri Color Screen comes up, does your computer ask to install a driver? If it does, be sure to allow that.
SuperSport said:
Your mobile screen is showing the correct information, with the exception of USB not showing. As soon as you get to the Tri Color Screen, try removing then reconnecting the USB connection and see if that makes any difference.
Also, when the Tri Color Screen comes up, does your computer ask to install a driver? If it does, be sure to allow that.
Click to expand...
Click to collapse
Well i just trying all steps again and it worked just fine...go figure!
Thank u anyway
rcpamr said:
Well i just trying all steps again and it worked just fine...go figure!
Thank u anyway
Click to expand...
Click to collapse
Glad to hear you are going. Now you are safe to flash custom ROMs.
Also, remember that each time you flash back to the OEM ROM for any reason, it replaces the HardSPL with the stock one. You will then need to flash the HardSPL back again. At least this is the case for the OEM that I use.
SuperSport said:
Glad to hear you are going. Now you are safe to flash custom ROMs.
Also, remember that each time you flash back to the OEM ROM for any reason, it replaces the HardSPL with the stock one. You will then need to flash the HardSPL back again. At least this is the case for the OEM that I use.
Click to expand...
Click to collapse
ok. thank u so much!