Develop Bugs

[Q] reinstalling stock ROM on hboot 0.93.0001

My Desire recently had to be sent back to HTC for repair. Came back with hboot 0.93.001. When I got it back, I rooted it (using Unrevoked) and flashed LeeDroid 2.3b.
However, the phone has developed the common locking/rebooting fault and I need to send it back to HTC again, but before I can send it back I need to reflash the stock ROM (T-Mobile UK).
However, whichever method I try I can't get the stock ROM back on to the phone. If I try reflashing using HTC sync, then I get ERROR #140 or #170 (assuming the phone doesn't freeze during the process).
If I try extracting the ROM.zip and renaming it to PB99IMG and installing from the root of the micro SD then I get a message saying "CID incorrect! Update Fail!"
Does anyone have any ideas how I can get my piece of crap HTC Desire back to stock ROM?
P.S. if you haven't already guessed from the last statement or read any of my other posts about my Desire going wrong, I will NEVER EVER buy another HTC....their customer service stinks worse than a landfill site!!

The CID error indicates that you need a Gold Card, you could use the Gold Card tool in my sig below to create one quickly.
Sent from my HTC Desire using eMIUI

MasDroid said:
The CID error indicates that you need a Gold Card, you could use the Gold Card tool in my sig below to create one quickly.
Sent from my HTC Desire using eMIUI
Click to expand...
Click to collapse
OK, I've created the goldcard. Now, how do I get the rom image onto the card? When the phone boots with the gold card in, I can't select mass storage. I've also tried the card in a card reader...it wasn't recognised.
Help???

babblerx said:
OK, I've created the goldcard. Now, how do I get the rom image onto the card? When the phone boots with the gold card in, I can't select mass storage. I've also tried the card in a card reader...it wasn't recognised.
Help???
Click to expand...
Click to collapse
Are you able to mount your SD card in recovery?
Try the following, I am assuming that you are running Windows 7: Try to re-format the card as FAT32 (if present, right-click on the removable disk and select Format).
1) Check if the device is getting detected in device manager. Follow the steps to go to device manager:
- Click Start, type devmgmt.msc and press enter.
- Search for the name of the device
If the device is not getting detected in device manager, then check if it is hidden device.
- Click show hidden devices under View
- Expand all the nods under device manager
There would be many grayed out entries in device manager uninstall all the grayed out entries under all the nods and then restart the computer and plug the external device to the computer and check if it works
2) Install the latest drivers from the manufacturer website and even make sure the driver is compatible with the version of operating system installed on your computer. check if it works
Link: http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly
Install the driver in Compatibility mode: http://windows.microsoft.com/en-us/windows7/Make-older-programs-run-in-this-version-of-Windows
3) Check with any other another SD card if it is getting recognized or detected or you may even check if the same SD card is getting recognized or detected on other computer

I have the same prob

still having problems...
MasDroid said:
Are you able to mount your SD card in recovery?
Try the following, I am assuming that you are running Windows 7: Try to re-format the card as FAT32 (if present, right-click on the removable disk and select Format).
1) Check if the device is getting detected in device manager. Follow the steps to go to device manager:
- Click Start, type devmgmt.msc and press enter.
- Search for the name of the device
If the device is not getting detected in device manager, then check if it is hidden device.
- Click show hidden devices under View
- Expand all the nods under device manager
There would be many grayed out entries in device manager uninstall all the grayed out entries under all the nods and then restart the computer and plug the external device to the computer and check if it works
2) Install the latest drivers from the manufacturer website and even make sure the driver is compatible with the version of operating system installed on your computer. check if it works
Link: http://windows.microsoft.com/en-us/windows7/Update-a-driver-for-hardware-that-isnt-working-properly
Install the driver in Compatibility mode: http://windows.microsoft.com/en-us/windows7/Make-older-programs-run-in-this-version-of-Windows
3) Check with any other another SD card if it is getting recognized or detected or you may even check if the same SD card is getting recognized or detected on other computer
Click to expand...
Click to collapse
OK, I managed to create another goldcard with the goldcard tool in your signature. I then extracted the rom from the T-Mobile (UK) stock ROM and renamed it to PB99IMG.ZIP and dropped it onto the goldcard.
Rebooted with the goldcard in the phone and vol - pressed, got the boot menu. The rom image was detected and started to load (side bar in top right of screen showing progress). ROM loaded 100%, then got the 'checking ROM' message. Then..."CID incorrect! Update Fail!" message again.
I've checked and double checked the goldcard creation process and am convinced I'm doing nothing wrong.
Any other ideas? I'm beginning to think hboot 0.93.0001 can't be downgraded.
P.S. I'm running Vista 32-bit

No, flashing an old RUU over a new HBOOT won't work. The issue you've got is there isn't a 2.2 T-Mobile UK RUU available so unless you've got an AMOLED screen the only thing you can do is flash the stock HTC RUU

it is an AMOLED screen
EddyOS said:
No, flashing an old RUU over a new HBOOT won't work. The issue you've got is there isn't a 2.2 T-Mobile UK RUU available so unless you've got an AMOLED screen the only thing you can do is flash the stock HTC RUU
Click to expand...
Click to collapse
Cheers Eddy. However, as far as I can tell, it is an AMOLED screen. All I want to do is get it back to T-Mobile stock ROM so I can send it back to HTC again.
Can't understand why there isn't a 2.2 T-Mobile UK RUU available yet.
It's damned infuriating!! Stuck with a phone I can't use at the minute...and getting desparate!

T-Mobile UK Stock 2.2 RUU anbody???
***BUMP***

I still need help
Anyone managed to re-install a stock ROM on an hboot 0.93.0001 device yet. If so, how did you do it?

babblerx said:
Anyone managed to re-install a stock ROM on an hboot 0.93.0001 device yet. If so, how did you do it?
Click to expand...
Click to collapse
Im in the same boat. Cant get mine back to t-mobile uk stock either
Sent from my HTC Desire using Tapatalk

EddyOS said:
No, flashing an old RUU over a new HBOOT won't work. The issue you've got is there isn't a 2.2 T-Mobile UK RUU available so unless you've got an AMOLED screen the only thing you can do is flash the stock HTC RUU
Click to expand...
Click to collapse
I know t mobile would know that the rom has changed from there own one to the htc one, but are the any differences apart from that if the htc rom was installed?
I mean would it run normally and recieve the normal updates ota, and would that affect if the htc was simlocked or anything?
Sent from my HTC Desire using Tapatalk

It'd run normally but would get HTC OTA updates not T-Mobile ones. Seems the latest OTA doesn't work on debranded phones, though

EddyOS said:
It'd run normally but would get HTC OTA updates not T-Mobile ones. Seems the latest OTA doesn't work on debranded phones, though
Click to expand...
Click to collapse
@Eddy,
Since he has AMOLED, there's a multistep procedure he can try.
1. Prepare the goldcard correctly with a Format in Fat32 (and deleting any extra partitions. Only 1 partition should exist-It should be a Fat32 Primary). If Goldcard is correct, phone should not give CID incorrect error.
2. Download the WWE 2.29 PB99IMG.zip, and put it in the goldcard and run it.
3. Run Teppic74's downgrader with goldcard. At the last step, choose to use this PB99img (Run this RUU while monitoring your Temp folder for changes. When the RUU loads and displays a window, search temp for Rom.zip. Rename it to PB99IMG.zip and put it in the root of the sdcard) instead of the Teppic one.
4. At this point the phone will have a completely working 2.1 Android OS branded to TMO.
5. Check for and update with OTA (You will get TMO OTAs at this point). Now your phone will have the latest TMO ssoftware and be as good as any other!

But they'd have to extract the PB99IMG file out of the RUU, the RUU on it's own won't do

EddyOS said:
But they'd have to extract the PB99IMG file out of the RUU, the RUU on it's own won't do
Click to expand...
Click to collapse
Yes indeed, but quite doable. The result would be a perfectly unrooted T-Mobile branded phone.
Edit: Added instructions for extracting the PB99IMG.zip from the TMO RUU

thanks for all the advice.....
...but I've given up on my Desire.
I can't use it for more than 2 minutes at most without it freezing up!! This is nowhere near long enough to do any of the above! I've even tried resting it on a bag of ice to keep it cool, but even that was no good!
I'm just gonna sell it to one of the recycle companies and put the money towards buying myself out of my contract.
Shame really because when it was working, it was a brilliant phone!!
HTC seriously need to get their house in order QC-wise. I know they have been making phones for a good few years now, but people still say "HTC, who??" and while they're QC remains as bad as it seemingly appears to be then that situation will persist!!
Think I'm gonna take a risk on the LG Optimus 2X when it comes out!! Why? because I love Android...I love bleeding edge...only now I hate HTC with a passion!!!

Droidzone are you based in the uk, as i dont know how to do what you have said. If you are and can do it for me that would be great and i would pay for your services.
Sent from my HTC Desire using Tapatalk

digo21 said:
Droidzone are you based in the uk, as i dont know how to do what you have said. If you are and can do it for me that would be great and i would pay for your services.
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
Same here. If anyone can get my T-Mobile (UK) Desire (rooted, hboot 0.93.0001) back to stock ROM then I'd be willing to pay (within reason). Bearing in mind you'd first have to solve the problem of it not being usable for any more then 2 minutes even from 'cold'.

No software problem should fail to be repaired by running a ruu. If if freezes or loops while running ruu, that confirms a hardware fault which necessitates a return if the device.
No I'm not in UK. I know that what I described may seem overwhelming, but believe me, if you run the procedure I mentioned, step-by-step and with the files I linked, there is no reason why you can't have your phone up and running in under 45 mins. See the unrooting guide I've written, linked in my signature, for the step-by-step method of running the pb99img from an ruu. It's easy enough. Only things you need for a smooth sailing is a working goldcard and the file extracted from the ruu correctly.
Note that I can't confirm that this method will work for Slcd , and it is quite dangerous running a 1.20 ruu on slcd. Proceed only if you're sure that yours is an amoled desire
Sent from my HTC Desire

Bricked evo..help please

ok so i just tried rooting my evo. I used an out dated rooting method not compatible with the version of my phone. I have 3.30, hboot 2.02, and radio 2.15.00.09.01. When i turn the phone on it gets stuck at white htc screen. I can boot into the bootloader. I have tried running the ruu but when i do it doesnt recognize my phone is connected. I have htc drivers installed...i dont know what to, do please help

Does the hboot says s-on or s-off? If your s-off try flashing a rom through recovery or a pc36img ruu through the boot loader.
Sent from my PC36100 using XDA App

Lukez123 said:
ok so i just tried rooting my evo. I used an out dated rooting method not compatible with the version of my phone. I have 3.30, hboot 2.02, and radio 2.15.00.09.01. When i turn the phone on it gets stuck at white htc screen. I can boot into the bootloader. I have tried running the ruu but when i do it doesnt recognize my phone is connected. I have htc drivers installed...i dont know what to, do please help
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Well one, if you can get to the bootloader, you most likely aren't bricked, so breathe! What root method did you try to use? How far in the process did you get? How long did you let it stay at the HTC screen? Sometimes it takes a good long while. If I was in your situation, since your computer won't recognize phone, is take your SD card out of the phone. Download a stock ruu zip. Rename it to PC36IMG.zip. put it on your SD card, put SD card back in phone, and boot into the bootloader. It should find the zip, and you select to flash it. Give that a try.
EDIT: Damn,I'm always too late! And yea, as he said, if you are s off, and did successfully flash a recovery image, try flashing a Rom first. Id be surprised if you are s off with recovery if you used an old method with the 2.02 hboot. What happens when you select recovery from bootloader?

Find and download RUU_SuperSonic_S_Sprint_WWE_3.30.651.2_Radio_2.15.00.09.01_NV_1.77_003_release_154209_signed
That's the one that worked on a hardware 004 Evo I used the old method on

Any luck getting your phone back up?

my s is still on..when i go to recovery it shows the evo with the red exclamation mark. I will try putting the ruu zip on my memory card..i need to go get a usb for my hero as it seems i cannot find it and have no other way to put a file on my sd card. any ideas if that doesnt work? i am a little confused as why it will let me issue adb codes in the command prompt but htc sync does not pick up the phone

Yup your still not rooted. Try to get a way to put a file on your usb card so you can load a PC36IMG.zip ruu of your 3.30 rom so you can get back to stock and start your process over with unrevoked.
http://forum.xda-developers.com/showthread.php?t=884060&highlight=shipped+roms

Lukez123 said:
ok so i just tried rooting my evo. I used an out dated rooting method not compatible with the version of my phone. I have 3.30, hboot 2.02, and radio 2.15.00.09.01. When i turn the phone on it gets stuck at white htc screen. I can boot into the bootloader. I have tried running the ruu but when i do it doesnt recognize my phone is connected. I have htc drivers installed...i dont know what to, do please help
Click to expand...
Click to collapse
I have dealt with this issue before. It is difficult to get an ruu to run but I think it is worth it. Find the right ruu for your phone to get you back to stock. Once you have this get your phone in to bootloader and use the fastboot command I believe it is. This will help your computer recognize your phone. Then run the ruu after you have done this, may take a few tries but im positive it works. Good luck.
Sent from my PC36100 using XDA App

Lukez123 said:
my s is still on..when i go to recovery it shows the evo with the red exclamation mark. I will try putting the ruu zip on my memory card..i need to go get a usb for my hero as it seems i cannot find it and have no other way to put a file on my sd card. any ideas if that doesnt work? i am a little confused as why it will let me issue adb codes in the command prompt but htc sync does not pick up the phone
Click to expand...
Click to collapse
Do you have a card reader? that would also work. Would probably also be cheaper than a usb cable I would think, not sure though. (unless of course you still use the hero and want a new cable anyways)

Thanks guys your awesome...was able to get the stock ruu pc35img on my sdcard..time to give rooting it a second go..with the right procedure this time..haha..thanks again

http://forum.xda-developers.com/showthread.php?t=865204

[Q] HTC desire T-Mobile wont boot

Hi guys,
I'm stuck with an HTC desire that doesn't want to boot.
I used to restart by itself once in a while and sometimes it would loop the loading screen a couple of times.
I managed to recover it before by using the recovery option on the bootloader but not this time...
What I've been trying to do is to install a clean ROM to see if that will make it boot, but it's proving difficult since I don't have a Gold card and the phone is Branded (T-Mobile UK) and not rooted.
Would you please advise some steps that I can try?
I read some threads in multiple forums but usually people cant even access boot menus properly, I can access both Bootloader and fastboot it's just that I'm not having any success in re-flashing / solving the problem.
PS: current ROM seems to be 2.12.110.2
Thanks in advance!

Update
I have found this thread which is a very similar problem to mine.
The differences are:
- I can actually run HBOOT;
- The phone is not rooted;
But i think the most important is:
- I can't seem to find the PB99IMG image of my current ROM so I could try and load via Gold card as suggested on the thread: "...flash the right (matching hboot, provider and version) RUU, by using the PB99IMG method..."
Any ideas how I can try to fix this? Thanks.

this is the TMO that you reported. http://shipped-roms.com/download.ph...00.32U_5.10.05.17_2_release_143754_signed.exe
good luck

Hi mariosraptor, txs for the reply.
From the other thread I think I need the PB99IMG.zip file. Is there any way to convert one to another?
I've tried the RUU before but it fails since I'm not really upgrading to a newer version...

i will upload the file for you in a few minutes.
edit: http://www.megaupload.com/?d=QBKRGBDF
md5sum 67961916d8d87998d1fa564c4eda4442
cheers
kashppo said:
Hi mariosraptor, txs for the reply.
From the other thread I think I need the PB99IMG.zip file. Is there any way to convert one to another?
I've tried the RUU before but it fails since I'm not really upgrading to a newer version...
Click to expand...
Click to collapse

Thanks a lot mariosraptor!
I will try this today by uploading it to the SD card, hope it works!

Tried it just now. It does find the PB99IMG.zip file and loads it, then it says [CHECKING] but it reverts back to HBOOT screen
Any ideas why this may be? I'm not using a Gold Card, can that be a problem? I thought it was okay since this ROM is signed...

It should not be needing a goldcard as long as it is your original rom. But if you can create a goldcard it shouldn't do any harm.
Sent from my LeeDroided Desire HD

[Q] Can't boot up. Stuck on HTC logo.

This may sound familiar to you but..
Some background. Got my Desire repaired (replaced the motherboard because of a well-known reason..). Previously I had a root access and my SD card divided to FAT\EXT. So I got my phone back, it worked perfectly but today it suddenly turned off while it was charging. Now it won't boot up. I see the darn HTC logo all the time. Did the wipe and..restore. It seems that I don't have any update.zip on my card. I have no idea what should I do. Any suggestions? Thanks in advance!

is your phone rooted? Were you have a custom rom or just a standard one?

Hey, no. After the repair the root was gone. Had the last OTA update installed. I just don't quite get it. Since I don't have that update.zip on the card, that means I can't really get it restored, right? So if i.e. I change my SD-card to another one. How do I get a restore image file? I'm confused..

If your phone is branded you need the goldcard to run again ruu but if it's not just download the latest software and try. maybe it'll help

try running logcat while the phone is hanging on the htc logo
it may give a clue of what is wrong

kluzik1 said:
If your phone is branded you need the goldcard to run again ruu but if it's not just download the latest software and try. maybe it'll help
Click to expand...
Click to collapse
By branded you mean OEM'ish? No, it's the regular one. By software you mean SDK?.. Or you mean that official .exe? (from i.e. shipped-roms.com)
edofic said:
try running logcat while the phone is hanging on the htc logo
it may give a clue of what is wrong
Click to expand...
Click to collapse
You think it's connected to the PC at that moment? I can't access SDcard at that moment..

Downloads from shipped-roms.com freeze after a while. So I've found a PB00IMG.zip file in some other place. Bootloader checks the file and goes back to the main screen. No errors, no update options - nothing.

Murrzeak said:
Downloads from shipped-roms.com freeze after a while. So I've found a PB00IMG.zip file in some other place. Bootloader checks the file and goes back to the main screen. No errors, no update options - nothing.
Click to expand...
Click to collapse
check this it may help you. Step by step how to install ruu
http://forum.xda-developers.com/showpost.php?p=12516573&postcount=6
the latest ruu wwe you can find here http://forum.xda-developers.com/showthread.php?t=869048
step by step and your desire will be fine

If you're on Vodafone and it's on a Vodafone ROM then here's the latest RUU:
http://www.multiupload.com/K0FR1OK301
And here's the latest WWE RUU:
http://www.multiupload.com/LEJCW182AH
Gold card would be needed to run the WWE RUU if you have a branded handset

Thank you guys. As I've mentioned before my Desire isn't branded. It was bought in Lithuania unlocked and sim-free. So theoretically I don't need a gold-card. But one .img I've tried to feed em returned wrong CID error. I've downloaded that RUU and tried to run it. Phone's plugged-in but the setup drops an error (170), says it can't see the phone. Tried to do it with in the bootloader mode. Same stuff. I'm kinda messed up.
HTC says they can take it for the repair so I don't need to send it back to Lithuania, but I still think it should be fixable..

Wohoo! I've managed to get the rom.zip out of the latest RUU and fix the whole problem. Thanks guys! You made my day! We can close the thread now.

[Q] RUU restore for warranty fails: error 140. Anyone can help?

Hi guys,
I own a Fastweb branded desire and back key isn't working anymore.
So I'm tring to restore the branded official rom for warranty.
I got s-off and root and my gold card is in.
I've flashed the old modaco r6 rom to avoid main version is older and flashed downgrade hboot(alpharev) too.
When I start the ruu hboot 0.75 and old radio are flashed properly, but I still have custom splash and cwm recovery also system is untouched.
Ruu stops with error 140 bootloader problem.
I'm still able to flash custom roms and I can s-off again, but I really don't know what to do.
Any help?
Thanks.
Best regards.
Jus

You're in the wrong section dude, read the rules.. all questions go to q&a section
This sections is set aside for development only
Sent from my HTC Desire using XDA App

Sorry mate, is there a way to change section?

jussy,
I had exactly the same problem so I'll answer even tho this is the wrong thread. You have to start first by extracting the zip file from the RUU. Run the RUU until it gets to the first screen then leave it there (don't close it).
Go to Start -> Run and type %temp%.
Find the temporary folder folder that's just been created (sort based on date) and find a file called 'rom.zip'. Copy this file into another location and close the RUU.

FreshNClean said:
jussy,
I had exactly the same problem so I'll answer even tho this is the wrong thread. You have to start first by extracting the zip file from the RUU. Run the RUU until it gets to the first screen then leave it there (don't close it).
Go to Start -> Run and type %temp%.
Find the temporary folder folder that's just been created (sort based on date) and find a file called 'rom.zip'. Copy this file into another location and close the RUU.
Click to expand...
Click to collapse
Thanks for replay.
I've extracted rom.zip and renamed to PB99IMG.zip. tried to flash it in fastboot.
Flash process start but stops before finishing leave me in the same situation as before. If I want to flash it again gives me main version is older.
I've s-off it 10 times today and made many try.
EDIT: I've also tried to flash via fastboot commander the .img files in rom.zip but after that I could only access fastboot.
Now I've flash a generic ruu to make it boot.

Tbh mate I'm not sure how to change it lol.. mayb delete and repost in q&a..
Just beware of flames coming your way lol
Sent from my HTC Desire using XDA App

jussy said:
Thanks for replay.
I've extracted rom.zip and renamed to PB99IMG.zip. tried to flash it in fastboot.
Flash process start but stops before finishing leave me in the same situation as before. If I want to flash it again gives me main version is older.
I've s-off it 10 times today and made many try.
EDIT: I've also tried to flash via fastboot commander the .img files in rom.zip but after that I could only access fastboot.
Now I've flash a generic ruu to make it boot.
Click to expand...
Click to collapse
Dude, don't flash the zip, just put it in the root of your SD, then switch phone off, hold vol down button and reboot into recovery, your phone will recognize the pb99img.zip and some options should come up. Follow the on screen instructions and you should be unrooted in 15 mins max.
Traced from a Reflex S Desire

3f1f37 said:
Dude, don't flash the zip, just put it in the root of your SD, then switch phone off, hold vol down button and reboot into recovery, your phone will recognize the pb99img.zip and some options should come up. Follow the on screen instructions and you should be unrooted in 15 mins max.
Traced from a Reflex S Desire
Click to expand...
Click to collapse
Sorry for my bad english but what you said is what I've done.
1-root and s-off.
2-flash downgrade hboot(alpharev).
3-put PB99IMG.zip (extract as said from my branded ruu) on sd card root.
4-boot power + vol down.
5-It starts, step 1 goes well then at the end of step 2 screen became black and came back with 0.75 hboot s-on and if I try again it gives me main version is older.
So I can only reboot, reflash a rom and s-off it again.
Never ending loop...
Thanks anyway.

You are using wrong RUU.use the RUU with 5.11.05.27 , I am on mobile so can't give you the exect link.I will post it tomorrow for you, if you can't find.
And it is better to create a goldcard if you havent yet
Sent from my HTC Desire using Tapatalk

jhonybravo4u said:
You are using wrong RUU.use the RUU with 5.11.05.27 , I am on mobile so can't give you the exect link.I will post it tomorrow for you, if you can't find.
And it is better to create a goldcard if you havent yet
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
I've got my gold card already in.
Sadly there's only one ruu for my carrier.
I can flash a generic froyo ruu but it's not good for warranty.

I can't really help in terms of your issue.
If I remember right, I booted into the bootloader and switched on fastboot, then ran the RUU EXE making sure my phone was connected to my pc.
It eventually came right.
Saying that, after I got the stock ROM back on, my phone went ape (and to this day I have no idea why). Random restarts. Freezing. It was crazy. I had to upgrade the RUU for it to stay on properly. Was really weird.
There are so many threads about rooting for warrantee purposes, perhaps search them or go through thier instructions, cause I'm sure someone may have had the same issue.
Wish I could help you though.

mr_norris said:
I can't really help in terms of your issue.
If I remember right, I booted into the bootloader and switched on fastboot, then ran the RUU EXE making sure my phone was connected to my pc.
It eventually came right.
Saying that, after I got the stock ROM back on, my phone went ape (and to this day I have no idea why). Random restarts. Freezing. It was crazy. I had to upgrade the RUU for it to stay on properly. Was really weird.
There are so many threads about rooting for warrantee purposes, perhaps search them or go through thier instructions, cause I'm sure someone may have had the same issue.
Wish I could help you though.
Click to expand...
Click to collapse
It seems you didn't got the problem.
Thanks anyway.

I did it!!!!
Thanks to this guide http://forum.xda-developers.com/showthread.php?t=821809
and all of you.
So many thanks.

Sorry guys I got an other problem...
Now this is the second time I bring it to assistence (last time was for vol down) and when they give it back to me it was updated to froyo.
I'm facing problem with 1.15=>1.21 OTA, installation is aborted due to status 7 (if some one can help I'll post the full error message).
Unfortunetly the ruu I've used is the only one from my carrier.
Will they know that my phone was updated by them and I'll lose my warranty?
Any idea about fixing status 7?
Many thanks.
Best regads,
Jussy