Hi all,
I have a little or it could be a big problem so I'm hoping you can help me here. I have 2 HTC Wildfire's one is Red the other is Brown. (Both on BUZZ)
Now I have debranded the brown one first and it worked a treat and I was able to update via WIFI and now it's up to 2.2. So then I decided to do the red one but that caused me nothing but problems started off will touchscreen not working but I found the kernel to reconnected the touchscreen. When I go in to HBOOT the touchscreen codes are different to each other, anyway once I got it working I tried to update via WIFI and it found the update but it would not procced to finish it so I had to root it via the sdcard and it worked but I can't tell if the WIFI update will work.
Now the problem is I have lost all my wallpapers on the Red one but not the brown one as it is still there. So how can I replace the wallpaper thats gone missing and how can I be sure that the WIFI update will work?
When I go through the screens they all match the same including the build numbers etc what has happened?
If this is any help I used ClockworkMod v3.0.0.1 (I think) but I can't get to it now without doing it all again. I don't mind doing it again if needed.
Plus another thing I remember is, I did some tests on both phones when I ring them it shows a different screen to each other, is that possiable?
I hope someone can help as we in need to use these phones.
Many thanks John
Did you use Revolutionary to gain S-OFF on the Red one? In that case, losing wallpapers, and the setup wizard is a known bug. The fix can be found here:
http://forum.xda-developers.com/showthread.php?t=1156713
Also, Revolutionary works when you are on Android 2.2.1 (On the updated HBoot). So, even though it may have shown that the update failed, it must have been installed successfully for it to work.
3xeno said:
Did you use Revolutionary to gain S-OFF on the Red one? In that case, losing wallpapers, and the setup wizard is a known bug. The fix can be found here:
http://forum.xda-developers.com/showthread.php?t=1156713
Also, Revolutionary works when you are on Android 2.2.1 (On the updated HBoot). So, even though it may have shown that the update failed, it must have been installed successfully for it to work.
Click to expand...
Click to collapse
They have both got S-OFF, and done by Revolutionary.
Thanks for the link I give it ago later and report back.
Many thanks for replying.
Long last, Many thanks 3xeno for your help, Now I have both phones matching with all apps doing as it ment to do, I also had to do the brown one as that had setup problems so I ran the same program for both and it worked a treat. So many thanks for all the posts and I sure will be staying on and learn more about these phones.
Many thanks to you all.
JJ
Related
Hello All,
I am used to flashing my HTC Touch Pro 2 and other windows mobile devices, but i have just moved onto a desire and am having a nightmare.
I bought the Desire on PAYG from 3 in the UK as they were up to a point supplying unbranded phones, but just my luck I had to have one from the new batch which is branded and cost me £18 to get an unlock code to use the phone on T-Mobile.
So as I stand I have an Sim Unlocked Desire thats branded to 3 UK.
The Rom version is 1.22.771.1 and Hboot 0.80 which I believe is an issue with rooting so that I can use other Roms.
To be honest I am quite happy with 1.22.771.1, but have a strange issue that on some occassions when someone calls me the ringtone starts, but then cuts out and there is no further sound, although they are still calling and I can answer the call.
So I really want to root and then switch roms.
I have read and read and read, and I believe my best chance is unrevoked, as I have seen a couple of posts which say it works with 1.22.771.1, can anyone confirm this?
Also if I flash to a custom rooted Froyo 2.2 rom, will I still be able to return to 1.2x roms should I not like it? As I have also read that unrevoked, does not work with 2.2, or is this just if you use the OTA roms?
If anyone out there can give me a do this 123 guide to get myself sorted I would really apparciate it.
Thanks
Stephen.
Hi
The issue with the ring tone is due to a setting,
Setting > sound > quiet on pick up
In check this option
sent from my C64
SeArch for a guide, its easy.
But you can return to any Rom you like, as long as your rooted.
I mention this due to if download the new ota you will lose root, and I don't think a method has been found to root the new 2.2 Rom yet.
sent from my C64
Sorry on my desire, but if you install a 2.2 Rom from xda you won't lose root.
But if download via ota and install you will lose root.
sent from my C64
So are you confirming I can root 1.22.771.1 with unevoked? Then install a rooted 2.2 rom?
Regards the Setting > sound > quiet on pick up should that be on or off? to cure the sound issue as i have that set as off.
thanks stephen.
can anyone confirm, so i can have a go at sorting this today please
CyberActive said:
can anyone confirm, so i can have a go at sorting this today please
Click to expand...
Click to collapse
I can confirm that you can't, and I wouldn't recommend that you try. The clockwork recovery image that unrevoked uses never loads, so the phone can't be updated in any way.
What I tried was slightly more extreme. I attempted to downgrade the HBOOT version, so I could flash a lower version generic RUU ROM. Unfortunately, whilst this worked as far as I can tell, the screen simply stopped working. I could actually receive phone calls, but nothing would come up on the screen.
The bad news is that even after flashing back to the original Three RUU ROM, the screen remained blank. The good news for me is that I'm due to get a replacement phone under warranty.
Personally, I can't even tell if this is a software issue or a hardware issue unique to me (I think it might be hardware as I should at least be able to boot into the bootloader), although this time I'll wait for Three to push the update, as I'm not prepared to take the risk of not being able to use my phone again.
CyberActive said:
can anyone confirm, so i can have a go at sorting this today please
Click to expand...
Click to collapse
I had Hboot 0.80 on my Desire with 1.21.405.2 and I used the Unrevocked3 method to root. But mine was unbranded from Three.
I now have 2.2 (http://forum.xda-developers.com/showthread.php?t=741775) with 32.43.00.32U_5.09.00.20 Radio.
All works great.
Hi everyone
I posted earlier asking for help on rooting and flashing custom roms. I was kindly given the link to the complete guide in the desire development section.
I followed all the steps and successfully created a goldcard and flashed the device with the stock rooted desire rom, however that's as far as I got as now my phone's screen won't work at all. This is what makes me think it's an SLCD model as I've heard such problems as well.
I've tried using unrevoked to flash the slcd modified recovery image, that doesn't work either. I've all drivers installed correctly and followed everything precisely.
Any help will be greatly appreciated.
What rom exactly did you flash with?
I followed this guide theunlockr.com/2010/06/07/how-to-root-the-htc-desire
Basically I got as far as applying a stock Desire rom that was rooted. After that the screen no longer works. The phone itself works as unlocking and locking prompts the phone to light the hard buttons and also receiving calls work.
At this pointI'm not fussed if someone can tell me how to put a rom on there that will work whatever it be, i'll ust have to do it blind as I can't use the screen. I've got the goldcard ready.
A ROM guaranteed to work is the official Froyo. It cannot be rooted:
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
An earlier ROM may work but it would depend on which ROM you flashed.
Thank you for replying, I will try this in the morning as I need sleep
Can you let me know if this will fix the problem with my screen not working?
Yes, that's the point of it...
You might want to view teppic74's FAQ as well...
http://forum.xda-developers.com/showthread.php?t=749551
My situation was a bit different.
I got an Asian ROM & wanted the European ROM. I followed 1 of the guides here & somehow i got a black screen (SLCD brick), possibly because I got the wrong RUU.
Found this link http://forum.xda-developers.com/showthread.php?t=748498
I followed method 1, didn't work.
But method 2 is a cure.
dsymbol said:
My situation was a bit different.
I got an Asian ROM & wanted the European ROM. I followed 1 of the guides here & somehow i got a black screen (SLCD brick), possibly because I got the wrong RUU.
Found this link http://forum.xda-developers.com/showthread.php?t=748498
I followed method 1, didn't work.
But method 2 is a cure.
Click to expand...
Click to collapse
That thread is out of date now. See the FAQ instead.
Thank you ever so much for that link teppic I had come across other stock ROMs however I hadn't come across that one, this has sorted all my problems and got me 2.2.
Thank you ever so much
Sent from my HTC Desire using XDA App
Hi Everyone,
Been lurking here a long time... first on my Moto Droid and now the Incredible. Ran into my first unsolvable (by me) issue. I've had the Incredibly since beginning of December (SLCD). I rooted it via unrevoked, ran SkyRaider for a while changed roms, back to SkyRaider. I've had no issues. Last week I started getting random reboots... phone would reboot, then reboot multiple times from Incredible logo... then finally start up and my icons and wall paper would all be screwed up. Needless to say I've searched a ton and the only answer I've found is this points to a defective phone. So now I'm trying to get it back to stock - which I haven't been able to find a how-to or any info for anything as new as the current Roms. I was able to install a stock rooted rom, get s-on but then I can't figure out how to un-root it and get the stock recovery on as the only stock rom I found was rooted and that doesn't help me on the stock recovery.
Any suggestions?
Thanks,
Jon
There should be pb img you load up in hboot. I've used it worked like a charm. I'll see if I can find it and put the link up. Since you have an slcd screen also don't use any ruu's that downgrade to 2.1 it was made for oled screens it will brick the slcd screen incredibles.
just found it
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
check that out.
shawn328 said:
There should be pb img you load up in hboot. I've used it worked like a charm. I'll see if I can find it and put the link up. Since you have an slcd screen also don't use any ruu's that downgrade to 2.1 it was made for oled screens it will brick the slcd screen incredibles.
just found it
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
check that out.
Click to expand...
Click to collapse
Thats the version I edited from this original post found on this forum
http://forum.xda-developers.com/showthread.php?t=786436
Has all the files that are that are in the first link. Both threads unroot you to the 3.26 build and thats a good thing.
Thanks, that's the one I had followed originally and it wasn't working for me (but I had an unstable rom on there). Once I got something stable enough to boot I did the RUU method and it did the trick. Off to the verizon store today!
Thanks,
Jon
Google brings back a lot of people who have this problem but no-one seems knowledgeable enough to have a fix for it hence my post here. Since I followed the How to downgrade, Easy S-Off and the tried and tested radio.img flash guides and flashed Leedroid (13/01 epic stable build) I've had an infrequent (i don't reboot much) problem with my DHD freezing on the HTC screen during boot. I've solved this in the past by reflashing (as I can still enter the bootloader and Clockwork Mod) from an SD card but this is getting annoying.
The people on Google who are having this problem have said they've returned their phones however If I were to do that I would have to go straight to HTC as I got mine from eBay, are HTC going to helpful in this situation?
So Is there a known fix for this that I'm missing? Maybe the latest Leedroid?
On a side note if there is no fix is it even possible revert my DHD to level of stock such that HTC won't know I've been mucking around with it? I took to easy S-Off route that apparently can be reversed and I didn't SIM Unlock it but due to my over confidence I can't be sure I kept all the backups of the stock stuff that I should have kept.
Anyway, thanks guys. I'll just hang out here with no phone for a bit hoping there is a way to get it to boot because I'd really hate to lose some of the MMS message I've been sent .
You should do a full wipe and try a new rom, for example the newest LeeDroid or Android Revolution HD.
It is possible to revert to stock so that HTC will never know, just follow the S-ON instructions in my Radio Tool thread.
jkoljo said:
You should do a full wipe and try a new rom, for example the newest LeeDroid or Android Revolution HD.
It is possible to revert to stock so that HTC will never know, just follow the S-ON instructions in my Radio Tool thread.
Click to expand...
Click to collapse
Many thanks for the reply. I did a ClockworkMod wipe and went for the new Leedroid (I've no idea if its the best but it was the first I spotted after rooting my phone), guess I'll have to wait and see if it happens again but touch wood no problems so far.
I've just been looking through the Revolution thread and spotted your wipe tool so if it does happen again I'll try that. I'd also like to say many thanks for your s-off thread, its very well written and easy to understand, and your work supporting the DHD is outstanding.
Hi all,
I love this forum as it's got so much useful info so have just joined as I'm a little unsure of a few things and would really appreciate any help/advice.
Firstly, the big question, can I downgrade from 2.2 to 2.1 on a T-Mobile UK branded device without risking losing the warranty (only got the phone in March - just in case any hardware defects as I had the camera break a month after I got the phone!). I have read numerous guides and they seem to be associated with rooting and what confuses me is the stock roms I'm finding are for 1.14 not 2.1?
The reason is because (there may be an answer to this somewhere but have searched loads and can't find it) the Webkit browser on 2.2 seems to constantly crash. I didn't have the issue on 2.1 and have had the phone repaired twice, the issue occurs straight after a factory reset and is definitely an issue with 2.2 on T-Mobile UK branded firmware at least. T-Mobile UK assured me it was fixed but it certainly isn't as it crashed twice (just disappeared) within 5 minutes of browsing and later in the evening came up with the 'force close' error when browsing.
I loved using the stock provided browser over Opera/Skyfire etc and it was fine on 2.1...
So I am wondering whether T-Mobile UK have just bodged the firmware and whether rooting/debranding would give me a very stable version of webkit?
I had this with my first Wildfire after upgrading in December 2010, after two repairs they couldn't fix it so swapped for a new phone in March. The new phone was fine on 2.1 and this issue occurred again straight after the OTA update of 2.2 last night.
I'm really hoping someone can help with the above?
Many thanks in advance
1.14 is the ROM version number, and, is actually Android 2.1. But, you will not be able to downgrade without root. (Atleast easily).
If you wish to take the complex way out to downgrading to 2.1 without rooting and stuff, you can refer this guide here:
http://forum.xda-developers.com/showthread.php?t=921752
Excellent, many thanks 3xeno. I'll have a go at that. I am tempted to try unbranded 2.2 firmware as by the sounds of it the browser crashing issue might be specific to T-Mobile UK. I can't find other people reporting this issue anywhere and its happened to me with two phones, after 2 repairs with ota updates twice and after multiple factory resets.
Do you use webkit and get any crashes at all? I've tried other browsers but prefer the webkit one when it works, would be great if it played flash content like YouTube etc but I'll do some more research on that...
try dolphin browser HD(has many add-on's) or opera Mobile ,these are the best in the line & opera min for more data saving efficiency
Thanks all, I am having a lot of trouble with the SuperOneClick part though.
I have S-ON on boot and the boot loader that ends in 001 does that affect the ability of SuperOneClick to do Temp Root?
All I get is:
Killing ADB Server...
* server not running *
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
cannot stat 'C:\Documents and Settings\Marty\Desktop\HTC Downgrade\SuperOneClickv1.5.5\rageagainstthecage': No such file or directory
OK
chmod rageagainstthecage...
Unable to chmod /data/local/tmp/rageagainstthecage: No such file or directory
OK
Running rageagainstthecage...
It just says the last part for ages and never seems to go any further...
Do I need to do S-OFF using Unrevoke or similar?
It shouldn't, since the procedure was performed on an official Froyo release on HBoot 1.01.0001. BTW, You have to press 'Shell Root', not 'Temp Root'. Further make sure USB Debugging and all is on, as the author states.
Hi 3xeno,
I can confirm debugging is on and it is Shell Root I am trying but it just seems to stick on that last stage for ages.
I have the goldcard in, does that matter?
I have also tried unmounting the SD Card as mentioned on another thread?
It shouldn't matter. But, I think this should help you out:
http://forum.xda-developers.com/showpost.php?p=16634853&postcount=139
If you check the 2 posts above it, the user was experiencing similar problems as yours. So, I believe that solution should help.
(That guide is to downgrade to a WWE (Non Branded ROM) with HBoot 1.01.0001, and the 1st step is essentially the same as what you are attempting to do - Downgrade Misc Partition and flash an 'older' ROM)
Good Luck
Thanks 3xeno, I ended up doing the revolutionary thing in those steps and it says S-OFF now with Revolutionary at the top.
I was then able to use a stock RUU and install 2.1 on the phone but it looks different in that the clock widget and icons on the main screen weren't there? It's supposed to be the T-Mobile UK v2.1 firmware I thought?
I thought I might as well use unrEVOKed to root it anyway but I wondered if it was possible to revert it back to the way it was using the factory RUU if I needed any warranty repairs? Would reverting back then change the bootloader screen or is that permanently changed by Revolutionary?
martyp78 said:
Thanks 3xeno, I ended up doing the revolutionary thing in those steps and it says S-OFF now with Revolutionary at the top.
I was then able to use a stock RUU and install 2.1 on the phone but it looks different in that the clock widget and icons on the main screen weren't there? It's supposed to be the T-Mobile UK v2.1 firmware I thought?
I thought I might as well use unrEVOKed to root it anyway but I wondered if it was possible to revert it back to the way it was using the factory RUU if I needed any warranty repairs? Would reverting back then change the bootloader screen or is that permanently changed by Revolutionary?
Click to expand...
Click to collapse
Revolutionary introduces a new userspace issue. It can be fixed by flashing this (Needs Clockworkmod, I hope you had selected Yes to installing Clockworkmod to Revolutionary) -
http://forum.xda-developers.com/showthread.php?t=1156713
To change your bootloader from the Revolutionary one, you will need the HBoot.nb0 file from your TMobile Eclair RUU. Once you obtain that, you will need to follow this guide:
http://forum.xda-developers.com/showthread.php?t=1160251
So, essentially, once you perform this, you are back to factory stock, on a T-Mobile 2.1 ROM. (Essentially summing up my first post, its far easier to root and downgrade. )
Oh, and dont touch Unrevoked. Its not needed at all.
Many thanks 3xeno, really appreciate your help and such quick responses
I actually ended up with root (I think) as the super user icon is in there and I was able to do a nandroid backup on bootup.
Nice to be back to 2.1 though, I might leave it how it is at the moment and keep this info in mind to revert if needed for a warranty claim (fingers crossed it won't be a screen fault!).
One thing I'm really pleased about so far is that it doesn't seem to sync up immediately with my google account and fill my people list with a load of random e-mail addresses which is something I didn't like before.
So far so good, I'll have some fun playing with root now...
Thanks again
Cheers mate.
BTW, You can go to People > Menu Key > View > Check 'Only show Contacts with Phone Numbers'. It may not have synced immediately, but, it will, sooner or later.
EDIT: Did you flash the Sense Fix? If not, then, HTC Setup Wizard (The startup guide which greets you first thing when you boot up after a factory reset) will not work, implying that your Google Account is not setup on the phone. (Or, you'll have to do it manually.) Probably, that's why, its not syncing.