Hi there,
I have rooted Desire with a Gingerbread ROM. It is still S-ON, but I would like to have it S-OFF. I've looked at Revolutionary, but it requires a stock ROM.
The last time I tried to install a stock ROM, it crashed on that warning screen (/!\). I sent it to get fixed (had some other issues as well) and received it with a stock ROM.
Correct me if I'm wrong, but discussion around here has led me to believe that RUU's come with hboot and hboot can't be downgraded. And so I figured the problem might have been that I was trying to install a RUU with a lower version hboot.
So this time I want to be sure the RUU comes with hboot 0.93, but the RUU descriptions don't mention this.
TL;DR:
I could be completely wrong, but I think I need a RUU with hboot 0.93. Anyone?
hi im using this one but you need to be unbranded or you need to use a goldcard... see bortak's guide for more info
Thanks. Worked great!
Related
I have this strange problem.
I did the s-off using the alpharev. Once that was done, I experienced random reboots and phone lockups.
So, I decided to revert back and used the 2.29.405.2 ruu to get back to stock htc image.
Now, I am unable to root my desire using un-revoked. The phone freezes after doing the hboot and pre-boot sequence. I tried downgrading my hboot and I continue to experience the same problem.
Is there a way to get the phone to factory conditions ? I use a MAC. Can I use the RUU exe instead of the PB99IMG.zip ?
Has anyone faced a similar problem before ?
Any leads/pointers would be appreciated.
And yes, I am not a newbie and can find me way out through the adb forests !
Thanks
Shyam
bootloader should not change things about rooting.
have u checked hboot what does it tell now?
Thread moved to Q&A.
0.93.0001 S-ON is the hboot version that I get.
RUUs are Windows applications. You could just get the 2.29.405.5 PB99IMG and flash that to go back to the latest stock ROM
I am unable to root the stock 2.29.405.2 using unrevoked too !! The phone freezes after doing the pre-boot sequence.
Shyam
Are you using the current version of unrevoked or just some old version you found on your harddisk? Older versions could not root froyo based roms.
€: Perhaps they also patched something in 2.29.405.2 that prevents this rooting method.
I've had no issues with 2.29.405.2 using unrEVOked 3.22 - not tried since going back to 2.29.405.5
Hey Guys,
I've got an HTC Desire, from 3 - it came with all the Three UK stuff on it (like the boot screen etc), but I rooted it, and flashed it with OXYGEN MOD, the latest one...but I'm now sending my phone in for a small repair job, and need to reflash it to stock.
I've made the goldcard etc, and am trying to flash it with an RUU H3G_UK rom, which I downloaded (RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed.exe). However, when I try to update it using PB99IMG.zip method, it says:
Code:
'Main Version is older!'
'Update Fail!'
'Do you want to reboot device?'
'<VOL UP> Yes'
'<VOL DOWN> No'
Any ideas as to what I should do?
Cheers. Phil.
Oh, and I thought I should post this too:
Code:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.00001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.14
AUG 10 2010, 17:52:18
Yep this happens because you will not be able to downgrade the hboot with this official update, and because it is an old 3 rom, it contains an old bootloader.
You will either have to find a newer 3 rom with something like 0.93 bootloader or a newer wwe rom(3/htc won't care).
You might also be able to somehow flash an older bootloader using an s-off bootloader and fastboot, and then run the update afterwards, but that is way too complicated.
Which part of this?:
Code:
RUU_Bravo_H3G_UK_1.22.771.1_Radio_32.36.00.28U_4.06.00.02_2_release_127568_signed.exe
...contains the HBOOT version?
It doesn't, but the branded official roms are always that old, and as the rom version is 1.xx i know it is an android 2.1 rom, which means hboot 0.75 or 0.80.
Also your error message state the problem quite clearly.
And to clarify my last answer.. No you will not be able to find a 3 branded rom with a 0.93 hboot, so go for a wwe instead.
What about this?
http://forum.xda-developers.com/showthread.php?t=768256
Don't use that - your Desire didn't come on that 3 UK RUU so no idea how it'll behave as you have a PVT4 Desire
There isn't a newer RUU and those old ones are for AMOLED Desire's only - you're kinda stuck
That might and might not work. It depends on the hboot included. The topic you link to uses a hboot version 0.83, because it works with all slcd phones as well. So if the 3 ruu contains 0.83 as well, this should work, and if it doesn't, you wont be able to install it anyway.
Now for gods sake please listen to me when i tell you that neither 3 nor htc will care whether your phone contains a branded rom.. They might not even care if it is rooted. So please just flash the damn wwe 2.2 rom...
My last post in here i think you get what i think you should do and i cant/wont help you risking doing something stupid.
Good news fellows
I flashed it using this:
RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed
and it worked no problem, I'm now back running Froyo 2.2 woop. cheers!
I need to send my phone back for warranty but I'm having trouble returning to stock.
I had a branded T-Mobile UK desire, I rooted it and it was running Redux v 1.1.1, alpharev s-off and amon recovery.
I have not created any goldcard and am unsure if this is necessary as some guides say so and others say just to flash the provider RUU.
I tried to run the tmobile uk ruus from here (both RUU_Bravo_TMO_UK_1.15.110.11_Radio_32.30.00.28U_4. 05.00.11_release_122755.exe and
RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.0 6.00.02_2_release_127570_signed.exe) but I got "Error 140 bootloader version" after it runs - it also asks if I want to update the ROM version from 2.10.405.2 to 1.15.110.11 (I'm not sure if this is a problem and I need to downgrade?)
I then reflashed redux as it wasn't booting, I now notice that bootloader is showing:
Bravo Unknown ship s-on (though I still have alsharev s-off splashscreen)
hboot 0.75
Radio-4.05.00.11
Can someone advise me on how to return to stock from here please?
If you're now on that bootloader you should be able to run the RUU again and it might take. Use the 1.21 one - but bare in mind unless you have an AMOLED screen it will leave you with a black screen as the ROM doesn't support SLCD screens
Thanks,
I'm pretty sure my phone is not AMOLED (Can't see any sign of it on the box), is there a RUU I should run instead or any way of restoring functionality if I try this and the screen does go black?
EDIT: I tried to run the RUU and came up with the same error? Any advice?
I believe you get that error when hboot in ruu is older than the one you currently have. Check if there is a newer ruu.
If you are still s-off hboot couldn't have been reflashed. Weird...
Is it definitely a branded one? Try running them RUU's again.
Thanks, I think it's s-on, but for some reason the splash screen has stayed. I've downloaded the RUUs (for T-Mobile) from here: http://forum.xda-developers.com/showthread.php?t=695667
It's definitely branded (or at least it used to be). I did use this unlocker tool as well, I'm not sure if that will have de-branded it stopping me from using the tmobile uk ruu (in which case do you know is there any way to rebrand before sending back for warranty?)
I think I might try to run a WWE RUU (RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed)
You'd need a gold card to use the stock WWE RUU
If you're on HBOOT 0.75 that's the very first HBOOT version, any ROM newer than that will work as the bootloader will be newer. No idea why it's not working but it's the issue with having a phone that doesn't have a modern RUU available for it
I haven't got a clue! I've created a goldcard using goldcard tool 0.0.5 which said I have successfully created one. I have a partition on the card, but as far as I can tell that shouldn't be a problem.
The WWE RUU won't run (error 170 - usb connection error) and when I put the PB99IMG.zip from the Tmobile RUU on the sd root (goldcard) and run bootloader, it doesn't detect it.
If I try to run the TMobile RUU it gets so far and then gives the error 140 bootloader version.
If anyone can suggest anything to try I'd really appreciate it as I'm getting nowhere!
Ok, I managed to get the WWE RUU to work by putting the PB99IMG.zip on the goldcard.
I guess that will have to do when sending back for warranty.
Thanks for the help in any case. If anyone knows why I wasn't able to run the TMobile RUU please let me know.
Hi, apologies for creating another thread for something that is probably very simple, but the information I’ve found can be conflicting sometimes
I've a rooted HTC Desire with a (very old) LeeDroid ROM installed.
Phone is going, so I want to revert back to the office UK T-Mobile ROM.
Current configuration:
Bravo PVT1 S-ON
HBOOT - 0.80.0000
Radio - 5.09.05.30_2
Clockwork Recovery v 2.5.0.7
I've never messed about with S-OFF or anything?
Is it simply a case of getting the correct RUU (which I think I have, RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed) and running it?
I realise that this is probably a stupid question, but any assistance would be appreciated?
Thanks
Put the 2.2 one on, not the 2.1
http://shipped-roms.com/download.ph...00.32U_5.10.05.17_2_release_143754_signed.exe
Or better yet put the unbranded 2.3.3 from htcdev.com.
I'm not 100% sure, but I think you need to install a rom with sense, plug USB in HTC Sync mode and then run the RUU.
Then the official RUU should take care of everything (boot, radio).
But again, never done myself.
Thanks guys, installing the official RUU from the website worked perfectly
Thanks for the advice
Hi All,
Apologies in advance... I'm a noob.
Well for a long time I was a happy camper running the excellent Marange MIUI ROMs on my HTC desire (which had been replaced by a PVT4 motherboard version). This was S-OFF and running HBOOT 0.93... but then one day a couple of months ago I got into a boot loop where all I got was the MIUI boot logo... not really a loop more just stuck at the logo.
So I tried several clueless attempts to reimage using the TeamWin TWRP boot loader... but nothing I did worked. So after several failed RUU attempts and random PB99IMG boots and one successful run of:
RUU_Bravo_Telstra_WWE_1.15.841.14_R4_Radio_32.30.00.28U_4.05.00.11_123851
I had what I imagined was a stock phone running an ancient Telstra release (it is a Telstra branded phone - the other world wide English RUUs refused to recognise the phone - 130 error).
I tried re-flashing the baseband radio, ClockworkMod v2.5.0.7 Recovery and MIUI... and wound up back to square one stuck in the MIUI logo and the RUU I used to get back to stock is now refusing to do anything) and this time I noticed my phone reports:
BRAVO UNKNOWN SHIP S-ON
HBOOT 0.75.0000
MICROP-051d
TOUCH PANEL-SYMT0101
RADIO-5.17.05.23
Mar 5 2010, 21:12:15
So somehow my PVT4 S-OFF 0.93 changed to the above. Which I don't understand... I thought that only a Goldcard could do something like that. None of the recovery tools seem to want to deal with HBOOT 0.75 and the fact that I'm S-ON would appear to be a pain.
The other thing that really confuses me is that how come if the phone is S-ON it lets me wipe everything and install the latest Marange MIUI ROMs ? Surely if it's S-ON then these would have to be signed (maybe they are for all I know).
Finally, if I use adb when the phone is stuck in it's MIUI boot logo I'm amazed I can get a root shell.
Anyone got any advice on how my phone got into such a mess, how to fix HBOOT and get a decent ROM running again ?
Any help hugely appreciated. The more detail the better.
Many AtDhVaAnNkCsE
Cheers,
Doug
"The big print giveth and the small print taketh away..."
How where you s-off, with hboot 0.93? Alpharev hboots have 6.93 etc.
Anyways, did you try the 2.3 RUU? Check my sig.
You can flash roms with s-on, but you can't change recovery.
Hi abaaaabbbb63
abaaaabbbb63 said:
How where you s-off, with hboot 0.93? Alpharev hboots have 6.93 etc.
Anyways, did you try the 2.3 RUU? Check my sig.
You can flash roms with s-on, but you can't change recovery.
Click to expand...
Click to collapse
To be honest I couldn't quite remember the state of my HBOOT I just new that it had been newer than 0.75, possibly 0.80, and that I had S-OFF and PVT4.
Your suggestion worked perfectly! I ran the RUU without issue to upgrade to 2.3 which gave me a new 1.x HBOOT and then I ran revolutionary and was then able to install MIUI. Smooth as...
Thank you so much!
I find the howto guides out there have lots of how but not too much why. I like detail on why things work or don't. Like why did that RUU work when so many others I tried didn't... did HTC make RUU 2.3 more forgiving in it's identification of supported phones ?
Anyway, once again many thanks for your kind help.
Cheers,
Doug
dscoular said:
Hi abaaaabbbb63
To be honest I couldn't quite remember the state of my HBOOT I just new that it had been newer than 0.75, possibly 0.80, and that I had S-OFF and PVT4.
Your suggestion worked perfectly! I ran the RUU without issue to upgrade to 2.3 which gave me a new 1.x HBOOT and then I ran revolutionary and was then able to install MIUI. Smooth as...
Thank you so much!
I find the howto guides out there have lots of how but not too much why. I like detail on why things work or don't. Like why did that RUU work when so many others I tried didn't... did HTC make RUU 2.3 more forgiving in it's identification of supported phones ?
Anyway, once again many thanks for your kind help.
Cheers,
Doug
Click to expand...
Click to collapse
the 2.3 ruu is not supported by htc but is there if u wanted it. so they just made a 1 for all update if u like, basically any brand (o2 etc) any region and so on.