Related
I have a branded (UK) Vodafone Desire that I loaded a stock Froyo ROM onto, now I need to get back to the branded Vodafone image (so I can return it for repair)
I have been trying to do this with the correct (Vodafone UK) RUU listed on thread 695667, but I keep getting a ERROR 140 : BOOTLOADER VERSION ERROR.
I'm guessing this was because the HBOOT was 0.93, so I then successfully downgraded to Android 2.1 taking HBOOT back from 0.93 to 0.83 using the details in thread 768256.
My HBOOT is now 0.83 but the RUU still fails - same ERROR 140 : BOOTLOADER VERSION ERROR.
So, is there a way to downgrade my HBOOT to 0.8 again (hoping that the RUU will work correctly with that version) ??
Or is there a way to extract the ROM image from the RUU exe and apply it using another method. ??
Thanks .. Ken
The problem is not HBOOT. Run the downgrade utility again, but -don't- install the downgrade in the bootloader (as described in the post), just select no, and then you can install the Vodafone RUU.
That worked a treat - thanks teppic74 !!
HTC bravo- t.mo uk
hboot 0.93.001
1. phone recovery corrupted[not amon ra or clockwork mod]
2. since hboot 0.93 older stock ruu wont work[1.15 and 1.21 dont work tried both]need a rom with a newer hboot
3. tried to rip .zip and renamed as pb99img but still didnt work. it wont update as it is an older version
4. does not boot into rom, stops at htc logo
5. no goldcard.
6. no HTC service centre, this country [freakin doesnt service outside home devices]
Is there any possible solution to recover the phone and make it functional?
Download RUU and create a Goldcard.
this ruu will not work because it is an older version. I require hboot 0.93 or higher. also cant create a goldcard as revskills has stopped making gold cards from cid..
Any other solution?
That MoDaCo tool works fine, and just get a stock WWE RUU such as this:
http://www.multiupload.com/LEJCW182AH
will surely try out and post back in some time
tried creating a goldcard with another device. got the cid , created goldcard image but get an error when patching.
"obj ref is not an obj" something like that. and it doesnt patch. any idea why is this happening. antivirus is disabled and htc sync is installed
ok so now i have a goldcard. used a different card-patched and successful. so now i tried to load pb99img.zip and it says
"CID incorrect"
update fail...what did i do wrong
oh man what the **** is their problem.
my desire is tmo uk spec..: but currently i have hboot 0.93 htc wwe 2.29 on it..corrupted and ****ed.
so i created goldcard and tried with wwe 2.29 again but it says cid error.
tried with tmo uk 1.21[latest] and it says bootloader error.
somebody please help me out here.
any help on this guys?
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.
For a few weeks my Desire has been playing up and unpredictably reboots, seemingly at random. Initially I thought it might be a software issue with the ROM I was using, but the same thing happened with various other ROMs I've tried since. So I'm thinking it's a hardware issue and I'll need to send my Desire in for service.
Normally I'd thoroughly read the forums and work out how to go back to a stock ROM, but I'm running out of time - only a few days left under warranty. Therefore this cry for help...
When I got the device it came with a 2.29.405.2 ROM and a 32.49.00.32U_5.11.05.27 radio ROM. I used unrevoked3 to root the phone and have been using custom ROMs since.
I've downloaded RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe, but every time I'm trying to flash it, the process aborts during 'updating signature...' and I end up with:
Code:
ERROR [131]: CUSTOMER ID ERROR.
The ROM Update Utility cannot update your Android phone.
Please get the correct ROM Update Utility and try again.
Not sure what I'm doing wrong. Maybe I'm using an RUU for the wrong area? I'm pretty sure the original ROM was WWE though (it definitely was 2.29.405.2 / 32.49.00.32U_5.11.05.27). I've read somewhere that you can't just flash an RUU if it has a lower HBOOT version... Do I need a goldcard or what's the best way to go back to the stock ROM?
Any help would be much appreciated...
Just in case, here's what my bootloader info:
BRAVO PVT4 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.27
Aug 10 2010,17:52:18
You only need a goldcard if you are branded right now..
So is your phone branded with a carrier rom, then you must make a goldcard.
I think customer id error is due to incorrect goldcard.
There is a newer version, 2.29.405.5 I dont know if that's gonna work but worth a try.
You can also try to put the zip on your sd card instead of running an exe on your pc, assuming that you run the exe.
Thanks for the quick response.
My Desire was unbranded, so I guess I won't need a goldcard then.
I've downloaded the newer RUU version you mentioned, but got the same error message...
So far I've only tried the .exe, but I'll see if I have more success with the .zip.
Could the issue be that my current HBOOT version is higher than that of the RUU?
You can try to flash 2.3.3 from htcdev.com it's works for all hboots and without goldcards
boy_in_oz said:
My Desire was unbranded, so I guess I won't need a goldcard then.
Could the issue be that my current HBOOT version is higher than that of the RUU?
Click to expand...
Click to collapse
Since you get a CID error, I would definitely try a goldcard.
You can also try flashing the downgrader from alpharev first.
ETA: I think the latter would help.
from alpharev site: said:
# Downgrade protection, these HBOOTs cannot be overwritten by an OTA or RUU, unless you flash a downgrader HBOOT first.
Click to expand...
Click to collapse
-Jobo
@MatDrOiD (vv post below) Good point. I failed to notice that.
@touch of jobo:
Flashing downgrader from AlphaRev is not possible, the OP is S-ON.
@OP:
Check bortak's guide to bring your phone back to stock.
Have you tried step 7 in Bortak's guide? (http://forum.xda-developers.com/showthread.php?t=1275632) It was the solution for me! I skipped the downgrading part (had the same hboot as you have, so that shouldn't be a problem) and went on with phase 2.
If your phone was indeed unbranded, the goldcard should not be a problem as I understood..
Thanks guys. I'm at work at the moment but will give Bortak's guide a shot when I get home tonight and report back then.
The definition of unbranded is a bit different. Unbranded does not exactly mean that there isnt a carrier logo. HTC manufactured and sold phones in India as an example is for all intents a branded Device. It's the INFOCID property that defines whether branded or unbranded.
fastboot oem gencheckpt
Click to expand...
Click to collapse
Inside an RUU zip is a small text file. Open it and see if your INFOCID value is included. If not, you cant flash that RUU without a goldcard. See my sig for the unbricking guide, which explains this.
From my Guide:
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code (Customer ID) which prevents you from flashing a ROM meant for any other brand and also blocks a Generic WWE RUU. If you're from India, it is branded with HTC_038. If you're unbranded, things are looking much easier for you, as generic WWE RUUs for SLCD are easily available. Run the following code from the sdk folder to find out if your device is branded
Code:
fastboot oem gencheckpt
This displays the CustID Code as HTC__ (and a number). If these numbers are the same as included in the cidnum value in the file android-info.txt, your device is unbranded. I have noted the following cidnums are unbranded: HTC__001, HTC__E11, HTC__N34, HTC__203, HTC__102, HTC__K18, HTC__405, HTC__Y13, HTC__A07, HTC__304, HTC__016, HTC__032. I'm not sure whether it is an exclusive list. To find out if an RUU is compatible for your ROM, the value displayed by fastboot oem gencheckpt has to be included in the cidnum list of the RUU. If it isnt included, you will need to use a goldcard to bypass the cidnum checks done by the RUU.
Check if you have made a goldcard (A goldcard is a normal microsd card modified to become special while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA or allow you to switch between software meant for different regions). The purpose of a goldcard is that when apparently incompatible ROMs are flashed with a goldcard inside the device, the flashing process skips certain checks like the Customer ID check (and hence no CID error). Note however that you cannot ordinarily install software of a lower version just because you have a goldcard. Note also that it is the software version which is important, and not the Bootloader version. Note that if you want to downgrade your software to a lower version, it is easiest to use Teppic74's utility (Link1 or Link2), and downgrade to his version of the RUU (1.21), then upgrade to your version of RUU. If your device is SLCD, always make sure the software you're about to flash does support an SLCD screen. As a general rule of thumb, flashing any version <2.0 may be dangerous. Teppic74 assures us that the version 1.21 his utility comes with, is compatible with SLCDs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Wow, I would have never guessed this... With fastboot oem gencheckpt I found that the CID is T-MOB101... i.e. my Desire is actually branded! I bought it from mobicity in Australia as an imported unlocked phone and *assumed* that it was unbranded... So it's not surprising that the RUU gave me a customer ID error. (This also explains why the OTA update failed while I was still using this ROM).
What's really weird though is that the version of the ROM that the phone came with was definitely 2.29.405.2 with baseband ROM 32.49.00.32U_5.11.05.27... I did some googling today, but couldn't actually find a T-Mobile ROM with these version numbers
My guess is that mobicity imported the phone and flashed a stock HTC WWE ROM so they could sell it in Australia...
Any thoughts on this? I'm assuming that means that I do need a goldcard after all to go back to the stock ROM?
Ok, as I couldn't find a T-Mobile ROM with the aforementioned version numbers, I eventually decided to make a goldcard and flash RUU_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed.exe. The whole process worked fine without any error messages and the RUU reported success at the end.
Unfortunately my bootloader still displays the same info as in post 1, i.e. I'm still on HBOOT 0.93.0001. I would have expected this to revert back to 0.93... Did something go wrong with the updating procedure?
The issue is obviously still that the original ROM seemed to be a T-Mobile ROM (in fact I think a German one as fastboot oem gencheckpt reports the carrier as TMD), so I'm not sure if the service point will accept the unbranded WWE ROM I flashed.
The other option might be to flash the official HTC Desire Android 2.3 Upgrade from www.htcdev.com, but I think it's not compatible with T-Mobile Germany Desires... If I could flash this, it would at least be an official release and the service point shouldn't complain. Does anyone know how easy it is to root/S-OFF/install custom recoveries/ROMs afterwards? From what I read, I would need to use revolutionary, right?
Any alternative suggestions would be much appreciate...
Your are totally fine with 2.29 RUU. Hboot would only update if you flash 2.3.3 RUU. Did not read about guys who "bricked" their phone by using 2.3.3 RUU on a desire by T-Mobile.
Sent from ICS with Transparent XDA App
Hello .. from a couple of days I recieved a desire hd but came with a custom rom and that is hd revolution 7.3 ,i respect alot the man who create this rom but I want to revert to stock rom,I know that htc's is a pain in the *** when come to software and I want some help on how i could revert it to stock(I tried with ruu and get 155 error with unlocked bl or 131 even on my cid) So the details are
build number: 10.05.401.4
Baseband:12.65.60.29U
And from hboot:
ace pvt ship s-on rl
hboot:2.00.0029
radio:26.14.04.28_m
Bootloader is curently unlocked.
Please tell my how can I revert to stock ,..i don't know what ruu should i get and other staff,i also tried with goldcard created by xtc and stuck when installing.
Phone is sim unlocked but cid appear t-mob101
Thanks in advance!
to return your phone to stock...firstly you must re-locked your bootloader from fastboot "fastboot oem lock"
because i can't found your RUU...then i think you must using a goldcard to flashing a different RUU (like this RUU or else that are had a higher or the latest version than yours) ..if your goldcard made by xtc had fail fashing that RUU...you can try create a new one with this goldcard tool by glevitan in here..
good luck..
JJeamy said:
to return your phone to stock...firstly you must re-locked your bootloader from fastboot "fastboot oem lock"
because i can't found your RUU...then i think you must using a goldcard to flashing a different RUU (like this RUU or else that are had a higher or the latest version than yours) ..if your goldcard made by xtc had fail fashing that RUU...you can try create a new one with this goldcard tool by glevitan in here..
good luck..
Click to expand...
Click to collapse
I create gold card with that tool but when boot to hboot don't start anything
andreibadea said:
I create gold card with that tool but when boot to hboot don't start anything
Click to expand...
Click to collapse
Latest news ... I lock bootloader and run aahk after flashing radio it hangs ... after that i boot in fastboot and run a ruu and now it seem that ruu is writing for the first time I'm so happy but in hboot still shows s-on.