Related
I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Drunknasty said:
I am a little confused. I have been trying to get WM6 on my T-mobile Wizard and actually got TNT 1.1 loaded and was working fine. I found that I could no longer view my contacts. The page would appear and then as quickly as it appeared it disappeared.
So I figured, I at least got it this far. I will just reload this rom and see if perhaps something did load right. Well after the reload. The phone boots up to the splash screen with IPL\SPL numbers and just sits. NOTHING.
I left it there for like 2 hours and still nothing. But I can still get into the BootLoader.
My questions to you gurus is:
Is the phone fubared?
Can I do some kind of master reset?
Why would it tell me "Invalid Vendor ID" when trying to flash the orginal T-mobile rom?
Are there any tools that can help me out? Paid\free?
Please help!!! Seriously! Please HELP!!!
Very much appreciated.
Thanks
Click to expand...
Click to collapse
if your device is G3, unlocking is required to flash any rom, before upgrade your device, it is recommended to flash an official WM5.0 rom (in your case T-Mobile rom) with IPL and SPL 2.xx then flash again.
in general there are many probabilities for your issue.
((Where is TNT1.1?? did you mean 1.0?? ))
My Bad meant 1.0
So to get it straight.... I will need to unlock my phone each time?
Oh and to correct myself again, when flashing with the T-mobile ROM it says UPGRADE ONLY. And the read me file says its the wrong RUU. But it is the same file from Tmobile I used when I first got the phone. But I will try again.
Are there any other suggestions?
You need to read the "how to flash" sticky.
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Try another ROM.
Sounds like you need the "Wizard Love" rom. I dont have the link handy but I am sure someone else does.
Drunknasty said:
I did. I am not any expert or anything but I believe the phone is unlocked already since I once had WM6 on my phone. The real issue I am having is that it wont boot past the splash screen after flashing.
And that is true when re following the steps in guide. After flashing to the button rom it will not boot past the splash screen.
Click to expand...
Click to collapse
Already got it. Thanks I am trying to load it now. But the only thing is that the last time it failed and I can understand what the error says. I know the number is 300 but can read the language.
But I will let you guys know when this load completes.
Thanks again for all the assistance.
No worky worky. The load completed and then boots the splash screen shows and then stays there.
Any ideas?
Try to remove the battery and let it out for at least half an hour. Then put it back in and see what it does then.
I thought the same thing too. So when it got done last night, out of frustration, I removed the battery and left it there to wait on when I get off work today. I will report back on what happens.
Again I would like to thank you guys for helping me. I really do appreciate it!
STEP 1 install the original manufacturer ROM
T-mobile UK
http://www.tm-phonedownloads.com/download_manager_mda_vario.html
T-mobile US
http://www.t-mobile.com/wmupgrade/
Search for the original rom for any other
instructions on how to use the original rom can be found here
http://support.t-mobile.com/knowbase/root/public/tm23294.htm?&A2L.SERVICE=AboutUpgrading
Put it in the bootloader mode.. ( three color screens )
hope this helps..
cheers
Praneet
Ok I did that and it gave me ERROR 296: UPGRADE ONLY
Then it tells me that the NBF file cannot be used for my PDA Phone. Please get newer NBF file.
Is there any way I can get the Tmobile splash and IPL\SPL number back to original, it doesnt need to boot all the way into WCE but atleast show the same numbers and splash during boot up?
Or any other way to get this thing to work?
Thanks guys
BTW it is a HTC Wizard from T-mobile.
If you are getting an error 300 you need a newer rom update utility, and regardless if your phone is a G3 or G4 it needs to be unlocked before you flash any rom.. LOAD a OFFICIAL cingular ROM onto your device before going any further, then unlock your phone either via www.imei-check.com or through some of the tools offered here...
Which one should I down load from Cingular? Even though I have a Tmobile phone?
what ipl and spl are you using and what radio are you using. Just post all the numbers from the bootloader
As soon as I get home, I will post them.
Thanks
Ipl 1.01
Spl 3.08
Thanks
Drunknasty said:
Ipl 1.01
Spl 3.08
Thanks
Click to expand...
Click to collapse
uh oh. someone tell me if I'm wrong, but I think this is bad. it's the result of flashing a g4 with g3 or the other way around... keep searching, and good luck.
flash the original t-mobile rom. your phone doesn't appear to be unlocked. good luck
It seems I'm just another one of the masses who rushed in to flashing their ROM/Radio/etc and now my Tilt is stuck at the bootloader. I've run through the "recover" process and every time I re-power the phone back on, I'm stuck in the red/green/blue/white screen with KAIS1*0, SPL-3.56.0000, CPLD-8 in the red section.
I would greatly appreciate any help in getting my phone back into working order.
You can get me on AIM at ygafip or msn at [email protected].
Thanks in advance.
Sorry - posted in ROM development. Can you move to the appropriate forum?
And you can disregard this ... I was able to successfully flash back to a stock ROM that I downloaded from HTC's website - I then followed the noob guide step-by-step and it seems to be working. I guess what I did wrong was I didn't install the HardSPL thing ... that seems to be the only thing I did differently. I have successfully installed the HardSPL, successfully unlocked my SIM thing, I'm currently installing the new ROM and then should be able to successfully install the new radio ... I guess that's the 4 steps I need to do.
Glad it's sorted.
Dave
Many people complain that they have "bricked" their phones when they really haven't. This thread will hopefully help reduce the questions on all of our useful threads.
How to tell if your phone is bricked:
1.) When you try to turn it on, nothing happens?
2.) Camera+Power does nothing.
3.) Home+Power does nothing.
4.) You flashed the SPL BEFORE the radio
If you answered yes to any of the above 4, you are bricked. You probably need a new board in the phone. Read more here: http://forum.xda-developers.com/showthread.php?t=516440 It has been confirmed that you WILL brick your phone if you attempt to downgrade your radio after flashing the new SPL. Not sure why you would want to anyways...
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
2.) Your phone is stuck in a boot loop
3.) Home+Power boots into recovery
If you answered yes to the above then you are NOT bricked. You have the G1 Night Light. This is (usually) a very easy fix.
The usual scenario is: You just upgraded your radio and/or the SPL on your phone and now you are trying to turn it on with no luck.
How to fix: After you upgrade your radio and/or SPL, you need to wipe a rom on the phone. For a plain almost stock feeling rom, checkout http://jf.andblogs.net/2009/05/24/jfv151-images-are-out/ if you are looking for hero, checkout the tutorial at g1upgrade.com.
I have also noticed when you flash hero, it will stay on the g1 logo for 5 or 6 minutes and then it'll finally start loading. Make sure your not being impatient and give it several minutes if you have just flashed a rom.
Last step:
If you have installed a new radio, then spl, then a new rom and you STILL get the g1 screen. Try it all over again. You probably didn't do something right. You don't need to ask questions in 30 different threads, your issue is not unique. You just need to search for some answers.
*Saved for future posts*
Edit:
Thanks! Updated.
I flashed the SPL before the radio whenever Haykuro released the Hero ROM and I didn't brick my device. Guess that I just got lucky. Thank goodness I know better now. haha
it's possible you flashed the radio prior to the SPL, only a loooong ways back.
Another thing to try if you are having issues is:
su
rm -r /system/sd/*
I was stuck in a boot loop and a quick ext3 wipe did the trick. The command should be able to be ran from console or terminal. You may need to mount /system with:
mount -t -rw,remount -o yaffs2 /dev/block/mtdblock3 /system
You would need to type that in between the commands above . I ran across this in another post but i think this is a good spot for it too .
Duplicate post...
thanx
At least I know now how to tell if I bricked my phone or just flashed it badly thanks for this.
youneek said:
How to tell if you just need to re-flash:
1.) Your phone is stuck on the g1 logo
Click to expand...
Click to collapse
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
alapapa said:
many people who flashed the new SPL before the radio are stuck at the G1 splash logo, but cannot get to recovery or spl bootloader / fastboot mode regardless of what they do, so this bit might be misleading...
they aren't technically "bricked" b/c it's loading the radio rom, but it never hands off to the SPL, so there is currently no way of reloading either of those to make the device do anything useful -- essentially a brick
Click to expand...
Click to collapse
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Good Job
Sorry this is off topic. But...
Thank you for this thread!
Ok,
By the way, has anyone figured out what The difference in the baseband is?? I have a U in mine...
youneek said:
I have fixed 2 phones that had no recovery and stuck at the g1 screen. If someone has this problem message me and I'll help you fix.
Click to expand...
Click to collapse
really? if it can't get to recovery / fastboot mode nobody has published a fix w/o a hardware swap.
what's your method?
I will buy a bricked one off ebay and post the steps I do to get it back. I can only fix the "Night Light", I can't fix a truly bricked phone (yet).
digital006 said:
This is exactly what happened to me, it was a brick, sent for repair and they replaced the mainboard.
Click to expand...
Click to collapse
How and where did you sent for repair and how much does it cost? I have a bricked MyTouch3G at this moment. Did HTC took it?
not bricked just weird!
ok been reading on here ,not sure if i need to just reflash everything or sd issuse?i put the new raidio,then spl on !then put jacxrom on my phone worked great!then ran for a day.then tryed cyanogenmod 4.0 and loaded fine but got force closed issues at the google sign in so i wipe and went to jachero 1.2 loaded fine went to logo android and then htc ,but then the screen went to blank .like the as said g1 night light .so i went back to jacxrom 1.3 it loaded fine got stuck in t mobile g1 screen .ok i flashed again same thing. but this is the part if i take my memory card out it will boot up just fine!then put memory card back in but lol all apps are missing have reinstall them. i wipe every time.i have the latest raidio 22.19.26I).,spl 1.33.2005 .also the jacxrom is running fine when phones on .so any help please thanks .also when i put the spl on it loaded then said reboot so i did. after went back to recovery at the bottom it said formatting cach... but was setting there for a while so took battery out then booted phone .was it suposse to say done or not ! hope dont make any mad thanks for the info
bump
hey help me plz i have big problem
i forget hit alt+w when i install SPL then i press alt+s when SPL install i out battery then i put it my mobile don’t want open and when i holding down the Home and Power button don’t open recovery mode and i holding the End key and the Camera button don’t open boot loader plz help me plz
You aren't going to get any help with sentences that atrocious. Can you be more clear?
Hi,
My phone was working fine till i tried to revert to old radio and spl to use the superD rom. Ive used many roms and all works fine. When i did the revert my recovery stopped working, so i tried going back to the higher radio and spl and still my recovery doesnt work, i press home and end call and insteasd of going to recovery it just sits there with the htc magic logo for 5 mins then reboots and loops. I have no OS on the phone now so I cant boot into O/S or recovery so I thought id try to install an RUU that I know lets me change the SPL and radio. I thought the only way would be in fastboot so I went into fastboot and loaded the RUU in windows and get the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". Now my fastboot has a little picture of a processor(I think) with a red cross through it and now I cant even change the SPL or radio as I keep getting the error "FAILED (remote: signature verify fail)" this is so frustrating and I really need my phone . I am not smart enough to fix this so if someone could PLEASE help i would be greatly appreciative, thanks.
In fasboot I have the little processor photo with a red cross and the following info.
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.008(SAPP10000)
CPLD-12
RADIO-6.35.08.29
Nov 3 2009, 15:56:29
***Update***
Now I can only get into fastboot, even when I just turn the phone on. Please view this link of the photo of my phone to see what I mean, thanks.
http://i43.tinypic.com/2n1ylwk.jpg
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
MicroMina said:
I dont think you bricked it as long as you can enter fastboot..
Actually I dont know what you should do.. hopefully someone can help you.
Good luck
Click to expand...
Click to collapse
Hi MicroMina,
Thanks for the reply. I hope someone can help me too im really stuck here. I have attached a photo in my first post, not sure its even fastboot anymore I can access
kbeezie said:
Screwing around with different radio versions almost guarantees a bricking if you don't know what you're doing.
I got your fastboot info, but what exact phone is it?
Click to expand...
Click to collapse
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
ddmmh said:
Hi kbeezie,
Its a HTC Magic 32A. I got it on a plan from Three(hutchinson) Australia.
My phone was working fine up until I used the radio and SPL for this topic
http://forum.xda-developers.com/showthread.php?t=605239
I was trying to downgrade(revert) when the problem happend. Updating/reverting had the same outcome which is where I am at now, thanks
Click to expand...
Click to collapse
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
kbeezie said:
Well you can probably try to revert the phone back to it's original RUU:
http://forum.xda-developers.com/showthread.php?t=659403
There's a Hutchinson, Au one on the list.
Click to expand...
Click to collapse
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
ddmmh said:
Hi kbeezie,
Thanks for the reply but I already tried to do that but i keep getting the errors "the ROM update utility cannot update your android phone" and
"please get the correct ROM update utility & try again". . Long story short up until 3 days ago I was using the Aus hutching RUU from that post. It was unhackable up until 2 days ago when there was a solution for the spl.0009-0010. I applied the method to revert to a non perfected SPL( i believe its called) i had root/recovery.. i even played around with a few roms but ultimatley i wanted to use the superD rom so I had to revert back to an old radio and SPL and thats when all this nightmare began, any other suggestions?? or any other info I can provide for you? Thanks.
Click to expand...
Click to collapse
If you had it working... why did you bother to flash the radio?
kbeezie said:
If you had it working... why did you bother to flash the radio?
Click to expand...
Click to collapse
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
ddmmh said:
Because to run the superD rom you need to have old radio and spl. As soon as I went to revert i started having the problems of not getting into recovery and the phone hanging on the htc magic and rebooting in a loop. At that point in time the fastboot didnt have a lock on it(see picture in first post) When i tried to use the RUU is when I REALLY started having big problems and the fastboot had that little lock image and now the only thing the phone does is go into fastboot no matter if i power on or hold home and power or volume and power... hope this sheds a bit more light on the situation thanks
Click to expand...
Click to collapse
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
kbeezie said:
I never had to deal with the RUU screen, and googling isn't revealing any new info. There's a good chance you effectively bricked the phone. The only other thing I can think of in regards to RUU images, is if perhaps the phone wasn't originally intended for Australia (as such would be a different RUU image).
Click to expand...
Click to collapse
Hmm i see, does the SPL or radio determine this? Because like i said earlier I was using the latest RUU for hutchinson AUS which installed fine so I believe thats not the issue, the only problem was the perfected SPL which was finally cracked a few days ago. I never thought id actually brick my phone. Do you think theres nothing I can do? I tried googling a locked fastboot with no results either, is this the first problem of its kind that you know of?
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Carlos1970 said:
While in fastboot; can you see the device from adb devices?
The safest thing to do would be to go back to the provider's code... just make sure it is the one for your model.
Click to expand...
Click to collapse
Hi Carlos,
No I cannot see any devices when i CMD adb devices
When you say go back to the providers code do you mean the RUU? If so then ive tried this without success(last one not original). If not can you explain what you mean? thanks
...and you have the SDK and USB drivers installed; correct? I run WinXP and the ADB driver was not automatically installed; had to be installed manually.
"fastboot devices" should work; does that one show anything?
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
eyegor said:
Wow, amazing. Don't try to help when you yourself are not completely sure about what you are saying.
ADB will NEVER recognize your phone in fastboot mode - hence FASTBOOT commands were created!
do "fastboot devices" while in fastboot , not "adb devices"
Click to expand...
Click to collapse
The problem of course is those who don't know what they're talking bout wouldn't know that?
And yet they talk. (not directed at Carlos, he did in fact tell the OP to try fastboot devices as well, only later)
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Carlos1970 said:
OK so I mispoke... The point I was trying to make was that the USB drivers had to be properly installed to get any output out of ADB.
Either through adb devices or fastboot devices it would be good to know if there is any comm over the usb port. If so; the best thing to do might be to reflash the provider's code.
So back to the issue. I found this thread from earlier in the year; I didn't go through all the messages but it is your same problem.
"My HTC Magic Stuck in RUU Screen after failed ROM upgrade"
Search for thread 625604
Hope it helps.
Click to expand...
Click to collapse
Hi Carlos and everyone thanks for your input.
I read through that post and all related posts but there wasnt really much of a solution.
I CAN access fastboot devices so i tried to flash a recovery via fastboot it starts to write then I get an error "FAILED (remote: 12 signature verify fail).
I think because I have S-ON? So i was thinking if there was a way to turn S-OFF would I be able to flash a custom recovery via fastboot??? Cheers
BUMP ^ ^
$20 into paypal account for anyone can give me a solution to fix this 100%.
Hi,
I installed Installing S-off, ClockWork accroding this tread as preparation to ROOT my device. Actually i did not ROOT it.
Today i downloaded new OTA Android 2.3.4, backup and prepare to install. After reset installation process started but never finished. progress bar disappeared and only little green android body and warning sign in triangle stayed for for long time and nothing to happens.
I am not know about install something else to my device except Revolutionary.io mentioned in tread.
I can ONLY finish this state only by get off battery. :-( so i cant instal new Android 2.3.4 to my device.
Any hints how to install? or how to continue.
thanx so much,
Ondrej
Hi
I had exactly the same problem as you.
The simplest solution is to go back S-ON
Put on the update and then go back to S-Off
Simples
(BTW: If I am wrong then please let me know just don't be too angry )
iftikar666 said:
Hi
I had exactly the same problem as you.
The simplest solution is to go back S-ON
Put on the update and then go back to S-Off
Simples
(BTW: If I am wrong then please let me know just don't be too angry )
Click to expand...
Click to collapse
hmm, truly believe that other solution is possible redo to S-ON is like way to Mordor, insurmountable...
but thanx so much for hint! i try to place our problem to tread in my question
Ondrej
I'm not sure if You can go back to S-ON if the mobile stops at boot and ther's no recovery installed yet.
@roul174: as far as I read Your post: You did a nandroid backup ? Or what kind of backup ? Can You start into recovery by pressing volume-down when switching on ? If so, can You restore Your backup ?
Thomas
roul174 said:
hmm, truly believe that other solution is possible redo to S-ON is like way to Mordor, insurmountable...
but thanx so much for hint! i try to place our problem to tread in my question
Ondrej
Click to expand...
Click to collapse
If you use this thread - http://forum.xda-developers.com/showthread.php?t=1192300 - it details going back to S-ON (I used it and it really is n00b proof)
And then it's dead easy to go back
TcG71 said:
I'm not sure if You can go ack to S-ON if the mobile stops at boot and ther's no recovery installed yet.
@roul174: as far as I read Your post: You did a nandroid backup ? Or what kind of backup ? Can You start into recovery by pressing volume-down when switching on ? If so, can You restore Your backup ?
Thomas
Click to expand...
Click to collapse
Hi thomas,
I did NaNdroid backup by revolutionary HBoot.
Fortunately, after get back battery and turn on, device started normally with no damage!
Yap i can start into HBOOT by volume down and sw. on. ;-)
and lastly i do not need to restore anything, thank the Lord!!
O.
It's good to have a backup already
And now Your mobile still shows 2.3.3 and if You try to update You get the message that there's no update available ? (would be the same as I'd got after going back to stock rom even if this version was much older)
update is @ my SDcard, version is sill 2.3.3
iftikar666 said:
If you use this thread - http://forum.xda-developers.com/showthread.php?t=1192300 - it details going back to S-ON (I used it and it really is n00b proof)
And then it's dead easy to go back
Click to expand...
Click to collapse
my opinion is to better ask Revolutionary producers to help with this... it should doesn't matter if there is Revolutionary or stock HBoot in device. this could happens any time new OTA will be dispatched, so solution to redo to SON and smth, and smth and roll back to stock ROM and ... no... there should some more elegant solution.
O.
Try to ask them, but maybe the only thing for You to do is to be patient...
After setting my mobile back to stock rom (VF RUU including HBOOT and Radio), and even after switching back to S-ON, I coudn't catch the update to 1.35.xxx in the next our.
But I choosed not to wait any longer. The only reason for me to do this was to try, if going back to stock rom (for repair or replacement) was possible. My problem to catch the update again was the old radio, which was installed by 1.27.xxx stock rom. So I updated the radio manually and installed InsertCoin again...
As long as the bootloader is working, you can always install ClockworkMod recovery through PG58IMG.zip method and install any custom ROM you like. You don't require a working system - or any system at all - for that. You can also install a stock ROM using the 'fastboot oem rebootRUU' method from the bootloader. There's never really any reason to go back to S-ON except for warranty.
roul174 said:
Hi,
I installed Installing S-off, ClockWork accroding this tread as preparation to ROOT my device. Actually i did not ROOT it.
Today i downloaded new OTA Android 2.3.4, backup and prepare to install. After reset installation process started but never finished. progress bar disappeared and only little green android body and warning sign in triangle stayed for for long time and nothing to happens.
I am not know about install something else to my device except Revolutionary.io mentioned in tread.
I can ONLY finish this state only by get off battery. :-( so i cant instal new Android 2.3.4 to my device.
Any hints how to install? or how to continue.
thanx so much,
Ondrej
Click to expand...
Click to collapse
Yesterday the same happened to me - HTC Sensation branded by T-Mobile Czech. I did S-Off, installed ClockWork, rooted phone and debranded. OTA update to 2.3.4 ended as you describe.
What helped me was installation of stock ROM 1.35.401.1 and then do OTA update. This time instalation was OK and bootloader says '*** LOCKED ***' and S-OFF. I did not try to install clockwork again.
kacer said:
Yesterday the same happened to me - HTC Sensation branded by T-Mobile Czech. I did S-Off, installed ClockWork, rooted phone and debranded. OTA update to 2.3.4 ended as you describe.
What helped me was installation of stock ROM 1.35.401.1 and then do OTA update. This time instalation was OK and bootloader says '*** LOCKED ***' and S-OFF. I did not try to install clockwork again.
Click to expand...
Click to collapse
okay, my problem is, that I am afraid about loose data. did you backed up you phone? if yes how. and next think is how did you choose right version of stock ROM for you device?
Thanx for advice,
O.
Once you install ClockworkMod recovery, the OTA updates won't work. You need to go back to stock recovery and OTA updates should work fine.
---------- Post added at 05:03 AM ---------- Previous post was at 04:55 AM ----------
How to Remove Custom Recovery
see
http://forum.xda-developers.com/showthread.php?t=1201773