Related
Ok so I trashed my ppc doing the radio update. Since I did the exact thing that Freshster did here is a cut and paste of my problem
" So, I tried running this TMO 4.00.10 upgrade in order to upgrade the radio stack to 6.24.00. While it was doing the radio stack upgrade, it failed at 13% complete. The error told me to "reset the device normally, wait for the radio stack to repair itself, reset the device again normally, then try to run the upgrade again."
After I did the normal reset that it told me to do, my screen got stuck on the ROM Kitchen boot screen and only showed a G, R, and 4.00.05 at the bottom corner, without showing a radio version or protocol version number. The led would not light up anymore. It did not flash green to show that it had signal, and it would not even show orange when it was connected to a charger. "
At this point Im SOL until tomorrow b/c I dont have a SD reader, my question is, can I upgrade the radio via the SD and hopefully get things going again? Or do I just attempt to reload a whole new rom and rsu via the SD card tomorrow. Thanks in advance for your help.
This is just a suggestion, I don't know if it will work.
1. Bootup in the Wallaby Boot Loader (hold power button while soft reset)
2. Press Calender button to bring up radio stack selections
3. Select turn off GSM
4. Reset and see if it will boot up when it doesn't have radio turned on
5. If it will, then set in active sync in guest mode
6. copy the RSUpgrade files to your window directory on the device using the explorer option in active sync
7. copy the two monitor files monitor_ul_bs.map and .m0 to the windows directory
8. reomove the device from the active sync
9. using the explorer on the device find the RSUpgrade executable in the windows directory and double click
10. this should start the radio upgrade going again
GOOD LUCK!
Thanks for the suggestion, I tried it but now luck. The pda stays stuck on the rom kitchen boot up screen. Thanks again.
OK, I had the exact same problem. You have to be patient, when you reset the device you'll get the R blank / G blank because the existing radio stack has now been trashed. eventually the PPC OS will boot. At this point reset again, wait for CE to boot & then reset again, The point is keep resetting the PPC every time you get the R Blank & G blank screen and wait for CE to boot. ON each reset the radio stack upgrade is working in the back ground. After 4 or 5 resets mine came up with R 6.24. at this point I connected the PPC back to Activesync & reran the upgrade & it went through just fine & installed the T-Mobile WM2003 ROM
Pdageek1 is right on the money! But I'll add one more step, remove your SIM card. HTH
I will try this on my way to work. I have another question, is the unit still charging when its on the base even though the charge light is not on? Thanks
I had same problem, if you flash with old t-mo rom it boots up everytime and will allow you to reflash radio stack.
http://www.t-mobile.com/pocketpcupgrade
hello pdageek and thanks for the suggestions. I have left my unit on at the splash screen with the blank g and r for about 5 2 minute sessions with no luck. Im hesitant to leave it on too long and have it eat up my battery. How long in total did it take your pda to boot up with the corrupt radio upgrade?
Sirseymore, the problem I have right now is that I cant even get it past the splash screen, since the OS is not booting up I cant see the unti via active sync.
You can't just it leave setting there with the blank screen you have to keep
doing the soft resets, until it boots!
Also to speed things up a bit during some of your soft resets try holding the volume control button, it similar to holding the hand of a sick person.
I know it sounds funny but hey what the hell, I did it! :wink:
One last note it also might help if you do a hard reset while holding the volume conrol buttom. I know that also sounds funny but hey I did that too! :wink:
HTH
Thanks for all your suggestions everyone. I ended up loade the latest tmobile rom via the loader, I let the pda sit at the Tmobile splash screen for 15 minutes until it booted into CE. Next I copied the necessary files for the RSU into the windows folder, ran the executable and all is working now.
Once again thanks for all the great people in this forum.
bimmer10 said:
Thanks for all your suggestions everyone. I ended up loade the latest tmobile rom via the loader, I let the pda sit at the Tmobile splash screen for 15 minutes until it booted into CE. Next I copied the necessary files for the RSU into the windows folder, ran the executable and all is working now.
Once again thanks for all the great people in this forum.
Click to expand...
Click to collapse
When you say Latest tmobile rom do you mean the 4.00.10 or the latest rom off of Tmobile's Website?
I got the same problem as you did blank g and r
Let me know Thanks, Allen
I'm in the same boat. I was running 4.00.05/stock 6.18 RS on T-Mobile USA.
I decided to try to do the Radio Stack upgrade by copying the extracted rsupgrade and monitor files to the device, and running them. It hung at 13%, so I soft-reset, and it hung at the blank G, blank R, 4.00.05 screen.
I tried turning GSM off in the bootloader, and have removed my SIM card. No luck.
Then, I flashed to the 4.00.10 ROM via bootloader, and I'm still sitting at the G/R screen. I have soft reset a few times, but that hasn't gotten me anywhere. I haven't left it for longer than 3 minutes or so before I get so anxious that I try another soft reset.
There seem to be two bodies of opinion here - those that say you should keep soft resetting until CE boots, and those that say just to leave it and wait for CE to boot (15+ minutes).
Is there any consensus among those that have recovered from now-infamous blank G/R screen? Should we wait, or should we keep soft-resetting?
JoshB said:
I'm in the same boat. I was running 4.00.05/stock 6.18 RS on T-Mobile USA.
I decided to try to do the Radio Stack upgrade by copying the extracted rsupgrade and monitor files to the device, and running them. It hung at 13%, so I soft-reset, and it hung at the blank G, blank R, 4.00.05 screen.
I tried turning GSM off in the bootloader, and have removed my SIM card. No luck.
Then, I flashed to the 4.00.10 ROM via bootloader, and I'm still sitting at the G/R screen. I have soft reset a few times, but that hasn't gotten me anywhere. I haven't left it for longer than 3 minutes or so before I get so anxious that I try another soft reset.
There seem to be two bodies of opinion here - those that say you should keep soft resetting until CE boots, and those that say just to leave it and wait for CE to boot (15+ minutes).
Is there any consensus among those that have recovered from now-infamous blank G/R screen? Should we wait, or should we keep soft-resetting?
Click to expand...
Click to collapse
Well i just got mine working FINALLY, what i did was flashed the rom to 4.00.10 and then did a soft reset let it sit for 15 minutes and then it came to the Align screen blah blah blah So just be patient and let the device sit for 15 minutes or so
Good Luck
Reflect said:
Well i just got mine working FINALLY, what i did was flashed the rom to 4.00.10 and then did a soft reset let it sit for 15 minutes and then it came to the Align screen blah blah blah So just be patient and let the device sit for 15 minutes or so
Good Luck
Click to expand...
Click to collapse
I let mine sit, and after about 15 minutes, it did finally come back up. I was able to copy the files and manually run the 6.24 RS upgrade, and I think everything is going to be OK now.. *crosses fingers*
I let mine sit, and after about 15 minutes, it did finally come back up. I was able to copy the files and manually run the 6.24 RS upgrade, and I think everything is going to be OK now.. *crosses fingers*
Click to expand...
Click to collapse
Well mine is working very good i havent came acoss any errors yet All i did was do the regular upgrade to 4.00.10 and got to 13% on Radio Stack Upgrade when it errored so i took it out did a few Soft Reset's no luck so i flashed the 4.00.10 Rom through the wallaby bootloader got it up waited patiently for CE to load... loaded after about 15 minutes at that time it was running terribly slow and when i got it up i had no service because i had no Radio Stack so i then loaded up this old radio stack well not so old but it was version 4.21 i then soft reset the device started the 4.00.10 install it went through the Radio Stack then the Rom update with absolutley NO errors or conflicts so everything is working great..
Heres something to keep in mind DONT Upgrade To Tmobile Rom 4.00.10 With the radio stack version A.20.10 Or you will be doing what i had to do!
i want to say thanks to all the great people out there posting
Thanks, Allen
JoshB said:
There seem to be two bodies of opinion here - those that say you should keep soft resetting until CE boots, and those that say just to leave it and wait for CE to boot (15+ minutes).
Is there any consensus among those that have recovered from now-infamous blank G/R screen? Should we wait, or should we keep soft-resetting?
Click to expand...
Click to collapse
My suggestion is this when you're in deep dodo, try it all! :wink:
Because as your seeing what works for some doesn't always
work for others.
Reflect, sorry I wasnt able to answer the specifics of the rom earlier, I was talking about th 4.00.10 version. Im glad you were able to fix the problem. :wink:
After waiting the 15 minutes to recover from the blank G/R screen, and successfully upgrading the Radio Stack to 6.24 and the ROM to 4.00.10, I've been using it for a day or so now, and I am pleased with the new ROM and radio stack.
Biggest plus for me is that GPRS now stays "always-on", even when the unit is turned off/suspended. I also like the fact that AIM 2.0, and PDF/PowerPoint viewers are included in the ROM.
As far as stability, I have had a couple of lockups (cleared by soft resets), and one spontaneous soft reset, but these could have been caused by software that I have installed (SpB GPRS Monitor, StocksAndWeatherToday, Journal Bar, Battery Bar, PocketNav, AE Uptime, Fonix VoiceDial Premium, Resco Explorer 2003).
I have had a couple of instances where the GPRS connection stops transferring any data, but still shows as connected. Since there's no way to turn off GPRS (SpB GPRS Monitor has a Disconnect button, but it doesn't seem to work), I can clear this condition by turning the phone off (not the unit, but the phone/radio) then turning it back on and reconnecting GPRS.
Thanks to everyone on this forum for your help, support, and ideas! This is a great amateur developer community.
JoshB
P.S. - Reflect, sorry I didn't answer your IM. I was in bed...
OK, I am going to try this once more since I can't stand having a useless phone...lol
I *had* the 4.00.05 ROM and the newest at&t radio stack on my T-Mobile phone (with TM service).
Attempted to install the T-Mobile 4.00.10 rom and associated radio stack via the .exe method over that, and it failed.
After that, I tried reverting back to the old T-Mobile 3.14 rom, via the sd card method. That seems to have loaded, but the GSM is still screwed.
Currently, when I start up the phone, I get the Welcome to T-Mobile startup screen, with 3.14 in the bottom corner. After a minute the G with no number after it is there, and below that, instead of an R is a U? (Maybe because I don't have the sim card in?) With no number. Then I get the "bing" sound, and it goes to a blank screen.
Reading through the posts here, it sounds like I should write the 4.00.10 ROM to the unit with the SD card, then wait for it to start up?
Should I have the sim card in?
When should I try the soft-resetting?
Just as an update, so far so good. I wrote the 4.00.10 rom to the unit with the sd card. Did a hard reset like it told me to. Now starts up with the T-Mobile Test only Not for sale screen. Shows 4.00.10, G with nothing after it, and R with nothing after it. It now stays at this screen though, instead of going to the blank screen. I guess this is a good sign, I am in a position others have been in. Yay! Waiting on it now to do something...anything, and I will attempt the radio fix.
Turned on my 8125 today and it stays on the screen with the verison of the
rom(etc) showing. I did a soft reset ... same thing.......I did a hard reset and it said format fail...... can anyone tell me what is going on here. am i lost ......can someone tell me an alternate way to get to the bootloader so that I can re-flash the rom........ I can't even get the phone to go into windows.... please please help. or am I out of 400 bucks for this phone. .....
Get into bootloader by with the device off - press and hold camera button and press power on. Multicolored bootloader screen should appear. Connect via usb - as long as you have a small usb symbol bottom left of screen you can reflash phone. (does not need to be connected via activesync to do this)
okay now look what happned
Okay thank you it worked and I was able to flash the rom. The flashed completed but it still freezes at the start up screen it says the following:
IPL 2.25
SPL 2.25
GSM 02.25.11
OS 2.25.11.1
its stuck onthe Cingular logo screen. When I try to do a hard reset it give the error message
format has failed.....
Can this device be saved?
I gather the device has been upgraded to the leaked aku2 rom. You may have a corrupt rom.
I would try downgrading to the original stock rom ftp://[email protected]/Wizard/Roms/Cingular/Cingular_RUU_1.8.11.1.WWE.ship.exe
more errors
it wont do the rom flash says something about wrong nbk
Your device is still cid locked then with that rom version you have to goto http://www.imei-check.co.uk/ and get it cid unlocked - cost £20 though. Your rom is too new to use faria's method that only works on rom's 2.21 and below.
May be an idea to post on wizard upgrading forum as they may have more ideas before paying out your money.
here is what i did
Well still no reply from the seller so I called the credit card company and dispute the charge. i have copies of the guys ad... and copies of the rude emails he sent me. The credit card company told me just hold on to the defective phone and the emails and they will take care of it.. Apparantly the seller was working from a Post office box he was pay apal verified. I just hope no one else falls victim to this guy.
Hi Profs,
there are some problems with a Artemis Update SPL (USPL) v.01. I've found this problem is several topic but there was no solution for it.
#1:
http://forum.xda-developers.com/showpost.php?p=1739577&postcount=413
#2:
http://forum.xda-developers.com/show...44#post1745844
#3
http://forum.xda-developers.com/showpost.php?p=1713596&postcount=1
The problem:
use USPL to get rid of the CID....count goes up to 100% screen shows black with green text, then pops to white. I need to do a soft reset to get it running again.
Then i use ROM Update Utility to update my p3300....and it still keeps hanging on 3%....damn. i get mad...!! Have read almost all here online...no virusscanner, no firewall....I use win XP.
i even tried without memory card and phone card....and nothing seems to work.......
ipl 1.14.0001
spl 1.14.0000
gsm 02.07.90
os 1.14.0.0
Who has any clue...?
With other words:
I've just got back my P3300 from repair, they changed the main board. With the previous main board I was able to upgrade the device and I was using the B&B versions.
But with this new board I'm not able to upgade the SPL. When I try to upgade the device after and start the start_uspl .exe the 10...20... ....100 my device become an interresting "blue screen" status and only the reset help to get out from this status. If I start the RomUpdateUtility.exe after the upgrade I got the error message #270
IPL: 3.13.0001
SPL: 3.13.000
GSM: 02.94.90
ROM version: 3.13.405.1.WWE
ROM date: 8/28/07
ExtROM version: 3.12.405.102
This is not the solution for the problem. I've tried it:
Plug in USB cable. Hold voice recorder button and press reset button. Bootloader will appear (Three color stripes). Then you may flash up ROM. (This works only for RUU installation types, not for PDAmobiz modified installator) Original english HTC P3300 ROM you may download form here: http://wiki.xda-developers.com/index...temis_Upgrades ....
Please help us to solve this problem....
Probably the same problem
This should be the same:
Hello POF,
I was directed to this link by Rudegar because I want to change the french ROM to English ROM.
The relevant data of my PDA is:
The version of the ROM: 1.14.406.1 FRE
Date of ROM: 9/27/06
Radio version: 02.67.90
Protocol version: 4.1.13.28
ROM extension version: 1.14.406.101
I tried exactly the way you described in the USPL_manual and everything went well till I got to a stage where I was asked to click the update button which I did. After then there was a window which showed "updating from current version to version 9.99". I was confused at this point but clicked "continue" and after this stage I got an error message and there was no longer a connection bw my PDA and my computer.
Thanks,
Jonat
Reply With Quote
http://forum.xda-developers.com/showpost.php?p=1784337&postcount=430
Also the same
Problem "lost connection PDA-PC"
Hi,
first I would like to thank you for goooood job to many people here !
Back to my problem. I have HTC Artemis (T-Mobile MDA Compact III), OS WM6 T-Mobile Czech version.
I ran start_uspl.exe on my computer. The part in DOS based screen seems to finish everytime OK, but finally the connection with PC is lost. Therefore when the PDA Phone ROM Update Utility starts cheking version the error "lost connection with PC" appears . PDA stay in "black screen" mode and only hard reset start it again as usual.
Does anybody have the same problem? Any idea, how to solve it ?
Thanks
http://forum.xda-developers.com/showpost.php?p=1773030&postcount=426
When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me
Unfortunately it not a white screen, it a black one, connenction lost with the PC, and only the reset PDA helps to restart the unit again....
lenocs said:
then pops to white. I need to do a soft reset to get it running again.
Click to expand...
Click to collapse
What im saying is when it pops to white, dont soft reset it, just start the upgrade.
Anthony2oo5 said:
When the screen goes white, don't restart. Just start flashing to the new ROM. Worked for me
Click to expand...
Click to collapse
that what i also do When the screen goes white, don't restart. Just start your RUU
lenocs said:
Unfortunately it not a white screen, it a black one, connenction lost with the PC, and only the reset PDA helps to restart the unit again....
Click to expand...
Click to collapse
Same situation as above. Depending on the Artemis, the screen might go white or black. Just don't freak out and keep on flashing the USPL. It WILL work and then reboot. Then you can flash the actual ROM you want.
Hello from an absolut newbie trying his first upgrade,
And I have just experienced the same problem than lenocs.
I have run start_uspl.exe, but when the screen is suposed to become white or dark, it becomes dark and the artemis is in fact totally off and connection is lost.
Anyway I supossed that it was because the scrren got black and I tried to run the update utility, but I´ve got an error (the terminal is disconnected or similar) and nothing happens.
I have had to soft reset the terminal and fortunatelly it seems that I still have my previous ROM and it seems that it works. But, do you know if there could be some "side effect" because the first step of start_uspl script?
Anyway I would like to move to WM6, so, any suggestion would be really appreciated.
Thank's a lot
When you restart, what is the USPL number?
Ooopppssss!
I didn't pay attention.
As I've said, I'm a newbie, so I was just woried because I thought I had "bricked" my new atemis.
How can I know now the USPL number?
Anyway I tried the star_uspl again (I'm a crazy newbie) and it failed. The artemis went off almost inmediately.
Thank you very much for your help
SpiggyTopes said:
When you restart, what is the USPL number?
Click to expand...
Click to collapse
solved ... at least for me
I think the problem is in SPL version 3.13 (or maybe anyone newer than 1.11).
Try different Artemis USPL - for me worked version from this page:
http://wiki.xda-developers.com/index.php?pagename=Artemis_DumpedRoms
It's very confusional, because file sizes and also dates are the same as in unfunctional version, but this one worked.
Hope it'll help you as it helped to me.
Maybe this can help you
I bought a 8gb card the week before, so I needed to update the rom in order to have my new SDHC working. But whn I was trying to update the rom, through UPSL 1.1, I had an error. This was the first time I had an error because I have modified the room many times before. My error was about a CMD.EXE issue, something like Error code line 26 "can´t spawn cmd.exe" so I was not able to change my rom. What I did was to copy CMD.EXE from Windows/System32 and put in the same folder where I had the start_uspl file, and finally works!
Do not ask me why, but this was the only way I could make works the update process.
Just try.
Rocheau said:
I bought a 8gb card the week before, so I needed to update the rom in order to have my new SDHC working. But whn I was trying to update the rom, through UPSL 1.1, I had an error. This was the first time I had an error because I have modified the room many times before. My error was about a CMD.EXE issue, something like Error code line 26 "can´t spawn cmd.exe" so I was not able to change my rom. What I did was to copy CMD.EXE from Windows/System32 and put in the same folder where I had the start_uspl file, and finally works!
Do not ask me why, but this was the only way I could make works the update process.
Just try.
Click to expand...
Click to collapse
do u have ur card in the phone while updating
you are suppose to remove the card
Problem solved (for me)
Hi,
i had the same problem error 270, 3% and lost connection with Activesync.
IPL: 3.13.0001
SPL: 3.13.000
GSM: 02.94.90
ROM version: 3.13.405.1.WWE
ROM date: 8/28/07
any way to upgrade was wrong ->> error 270
My good way was:
1. Downgrade to WM5 - original shipped ROM 1.12.405.1(link found on Wiki pages)
2. Under WM5 run USPL to unlock CID (now without any errors)
3. Final STEP - Upgrade to new ROM Artemis Touch 3.01 (without any errors by upgrade)
))
Now my Artemis seems to be OK.
I ran USPL with storage card inside the device...
no problem
switch SD card back to 2GB or smaller before USPL
Hi,
for me USPL did not work with my SDHC 8GB card but then I switched back to my previous 2GB SD card and then it works.
Perhaps the SDHC driver blocks USPL in some way.
Cheers,
Markus
i have been trying for 3 months
once i have upgraded my artemis to wm 6.0 everything seemed to be OK for two days... then the screen started to go black when i restart... şi downgraded to 5.0 but nothing changed... when i remove battery for a while, my arte works... when i try to do anything with it, the screen slowly goes black as if it is broken... please DO HELP ME! i am going to go mad... i have a new iphone, ihave i kaiser as well... but i miss my artemis very much...
Hello:
I have the same problem and realized hundereds have too. I have been checking in all forums and no asolution to it
The issue that happens to me is that I used USPL for upgrading to WM6 and worked, but now for the Touchflo it does not. Tried with all USB ports, tried with different computers and no good news.
The USPL msdos screen indicates that there is no connection at all in all percentage levels, then it bocomes dark and the 260 error whne installing the rom.
please help us soon !!!
we are in trouble!!
Same Problem : Screen shut down
Anybody can help us on this point ?
The only way to solve it is to remove the batterie during 30 min., then put it back and pray...
Then, for no reason, the screen shut down, a few minutes or days after
I've upgrade from WM5 to WM6 with the original Rom of HTC, it seems a little more stable but it shut down every 2 days when i'm lucky
My son dropped his 8525. It is now stuck on a display of red, green, blue, and white bars. A reset and a battery removal do nothing to get it to boot. Is it toast or is there something I can do to get it to boot?
considering this is your 1st post I'm assuming that you didnt have olipro 2.10 as your SPL.....What is your IPL and SPL as this may get you the help you are looking for... And if you do get it going again PLEASE install Hard SPL, Here : http://forum.xda-developers.com/showthread.php?t=296722
Good luck.
P.S. try reading through this, it may help... : http://forum.xda-developers.com/showthread.php?t=369434
The IPL:
IPL-1.04
The SPL:
SPL-2.03
I hope this helps someone.
Someone said they had success with this problem in this thread http://forum.xda-developers.com/showthread.php?t=355884
Read a bit and see if it works but please understand that this really just trying out everything in a last ditch effort to get it working. There may be no hope, so no promises...
If you do manage to get it going again I'd suggest Hard SPLing your phone so it is easier to fix. Hard SPL isn't a guarantee, mind, but it does provide a safety net for when things like this happen...
All the best...
hermes 100 8525 flash problem
hi, i was trying to upgrade a cingular 8525 in the process of unlock,
and it stopped at 1%, and did nothing,
now the phone just go to the 3 color screen,
and says
herm100
ipl-1.00
hem100
spl-1.40.olipro,
what can i do to restore it to normal please,
lacasapc, try to Hard Reset, hold down both soft keys and reset with stylus. If that doesn't work then try this : Flash it to you device while it in tricolour screen. Make sure that your activesync disable & use the latest RUUwrapper.
Open Activesync, select connection settings and untick "Allow USB Connections".
Run the RUUwrapper.exe file for the os you want after connecting the hermes via usb. Chose SPL 1.40 then HARD SPL and then flash the new OS. This should work.
Cheers...
Hi, all.
I've been reading a lot through these forums and I've learned a lot, but I don't seem to be able to fix this by myself. I have a Dutch T-mobile MDA Vario (WM5) that's over 3 years old so I'm not worried about voiding warranties.
A few weeks ago, my phone didn't want to boot anymore. I don't know if it's related, but around a week before the crash it had problems with finding the SIM card.
When I boot, it quickly gets stuck at the white background with gray/pink squares and the T-mobile logo. This is the data that's given (after a few factory resets):
IPL 2.21
SPL 2.21
GSM 02.19.11
OS 2.21.2.5
After that, it... just... hangs..., no matter how long I wait.
I tried to reset it to factory defaults (holding the three buttons + power button). The resetting seems to work, but then it gets stuck at the same screen again.
I came along forum.xda-developers.com/showthread.php?t=298613 <-- this thread, and I figured that I might as well try to flash it. I mean, if it doesn't work, well then at least I've tried. As you notice I'm new at this. I'm not afraid of electronics but flashing phone roms is new to me.
I can startup to the bootloader menu (photobutton + power) which tells me:
IPL 2.21
SPL 2.21
So, I've got a G3 device.
When I connect the USB cable to my pc (Win XP SP3), my PC gives the normal sound when a USB device is connected. the MDA nicely adds the text USB to the lower left of the screen. Nice. ActiveSync doesn't recognize it, but that seems to be normal, or so I read.
Following the thread's advice, I've downloaded the needed files and want to install them as ordered. First in the list is the Wizard_Love rom, so I go ahead and try to install it (from c:\XDA\final\). The first download link is broken, but at the end of the tread there is another link( to Wizard_Love_2.26.10.2_WWE_Novii_CF2.rar). The installer is in Spanish(?) but if it can give me back my phone, I'm fine with it. Besides, the readme is in English...
Then, after a short while, it gives me the following error:
ERRORE [300]: STRUMENTO DI AGGIORNAMENTO NON VALIDO
and some more text. I don't speak Spanish, but strumento will translate as instrument and non valido will undoubtedly be 'non-valid'.
It seems somehow that the communication still has some issues. I have just charged the battery, so that's not a problem here.
Do I have a wrong wizard_love rom? If yes, where can I get a proper one?
If not.. What else can I do?
Thanks in advance. You'll be my hero
You could always try to flash the original ROM and see if that gets you past the boot screens.
The installer language translates to Italian, ERROR [300]: INVALID UPDATE TOOL.
Try a different No ID Installer package, not the whole ROM just the No ID Installer.
Thanks! You have no idea how happy you made me..
Your comment on installing the original ROM sent me in the right direction. I went to t-mobile.nl and looked for updates (I shoud've done this much earlier). Where the hard reset failed, the official update worked flawless. I have yet to do the radio update, but I have my phone back! phew, 3 weeks with my old (by now- fossil) Samsung X100 made me realize how much I love this phone.. The QWERTY keyboard to begin with, my agenda, programs...