Related
I have unbranded my vodafone htc desire and upgraded to froyo. Used goldcard for all that.
Now that vodafone 2.2 update is out I want to rebrand again. However I can not install the vodafone ruu 1.19.161.5. It says the bootloader is incorrect. It doesn't matter whether or not goldcard is inserted.
What do I need to do?
Thanks
Downgrade your bootloader...
Can you just point me in the direction of the right instructions to do that?
What bootloader you on now?
0.92, the one that comes with the latest wwe froyo rom.
I now downgrade the hboot to 0.80 by using PB99IMG.zip but I still get the same error. Anyone an idea?
is it possible to just apply the vodafone froyo update.zip?
Unfortunately not, just tried. Looks like verification passes but then installation aborts.
If you're now on the 0.80 HBOOT just run the Vodafone RUU without your goldcard and it should rebrand...tbh, there's no difference between the Vodafone and WWE FroYo ROMs so I don't see the point in going back (unless it's for warranty purposes)
Unfortunately it is not that easy.
I truely have hboot 0.80 (it says HBOOT-0.80.0000)
The Vodafone RUU gives me error 140, bootloader version error.
When I then pull out the usb cable the desire's screen says: "Main Version is older!"
r.boeters said:
Unfortunately it is not that easy.
I truely have hboot 0.80 (it says HBOOT-0.80.0000)
The Vodafone RUU gives me error 140, bootloader version error.
When I then pull out the usb cable the desire's screen says: "Main Version is older!"
Click to expand...
Click to collapse
Where did you get the RUU for the Vodafone froyo update?
Because it's not the already known:
OTA_Bravo_Vodafone_UK_2.10.161.2-1.24.161.3_releasejldotwm8uy2ohjmf.zip
That's merely the upgrade from 1.24.161.3 (someone still on Vodafone roms). If somebody is on the HTC unbranded Froyo rom, it will not upgrade that. You will need the full RUU.
There's the 1.19.161.x Vodafone RUU which you need to roll back to to then get the OTA update...
EddyOS said:
There's the 1.19.161.x Vodafone RUU which you need to roll back to to then get the OTA update...
Click to expand...
Click to collapse
A roll back which would be prevented by the updated bootloader included with the non-branded HTC Froyo update.
armadax said:
A roll back which would be prevented by the updated bootloader included with the non-branded HTC Froyo update.
Click to expand...
Click to collapse
Just to clarify things. I'm now on the stock android 2.1 Rom with hboot 0.80 and try to apply the Vodafone 1.19.161.5 RUU. That causes the bootloader version error.
Someone an idea?
You'll need to go back to 1.15.405.4 I think to get HBOOT 0.75 and then it should work. I don't know if this can be done though
It's not because of the bootloader, it's because you haven't done all of the downgrade steps - you need to apply the misc partition fix as well.
Unless you want to return your phone to Vodafone what you're doing will give you nothing extra, except possible future branding updates from Vodafone.
r.boeters said:
Just to clarify things. I'm now on the stock android 2.1 Rom with hboot 0.80 and try to apply the Vodafone 1.19.161.5 RUU. That causes the bootloader version error.
Someone an idea?
Click to expand...
Click to collapse
So, why not wait for the full RUU for the Vodafone Froyo update?
teppic74 said:
It's not because of the bootloader, it's because you haven't done all of the downgrade steps - you need to apply the misc partition fix as well.
Unless you want to return your phone to Vodafone what you're doing will give you nothing extra, except possible future branding updates from Vodafone.
Click to expand...
Click to collapse
Vodafone have removed ALL branding/apps in their FroYo ROM due to a HUGE protest from Vodafone users on their official forum. It has a newer radio too (which is up in the Dev forum)
I know about the PR slip, but that's not to say that future OTA updates from Vodafone won't contain branding. The newer radio version might have some improvements over the current stock ROM, but of course these will be included into the next unbranded OTA update.
Hi to all!
I have rooted Desire and custom rom.
Now I want official rom back and normally I downloaded ROM from this forum (from HERE WWE second one...)
I connected my Desire and do everything like before but now I got an error that there is mistake in my boot-loader version and that I should download RRU installation for my boot-loader....
This is info from my phone:
v. 2.2
radio 32.44.00.32U_5.09.05.30_2
build 2.10.405.2 CL226611
How is now the easiest way for me to return it to stock? Doesnt matter what version, I will do the update later...
Regards,
Ivo
Now I have downloaded and the first RUU ROM but the same problem...
Moved to Q&A as not development.
You need to get the 2.10.405.2 RUU from shipped-roms.com
EddyOS said:
You need to get the 2.10.405.2 RUU from shipped-roms.com
Click to expand...
Click to collapse
Under Bravo model, right?
Tried with that ROM but always getting USB connection error...
And my phone has HTC displayed on the screen
Follow this guide:
http://forum.xda-developers.com/showthread.php?t=768256
Once done, get the OTA to 2.10.405.2
Did it, thanks!!
I'm getting the 140 Error when trying to flash
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe.
Also tried some other RUUs, without success.
Need to unroot my phone, since it Restarts randomly and needs the board replaced.
Please someone help!
Having a generic (not branded) Desire, ROOT, latest LeeDroid ROM,
BRAVO PVT SHIP S-ON
HBOOT 0.80
AMOLED
5.09.05.30_2 Radio
SD Card Working
Access to SD via USB working.
One day I was trying to S-OFF this phone, but all I got was the ugly Joker splash screen, can this be the problem?
This phone has been rooted-unrooted-rerooted before without problems!
Thanks!!
Why not get the 2.10.405.2 or 2.29.405.2 RUUs? If they don't work either it might be because you have a branded handset
EddyOS said:
Why not get the 2.10.405.2 or 2.29.405.2 RUUs? If they don't work either it might be because you have a branded handset
Click to expand...
Click to collapse
where are these RUUs hosted? Didn't find any direct links here on xda. EDIT:Found your thread: http://forum.xda-developers.com/showthread.php?t=828519
And why aren't they in this thread? http://forum.xda-developers.com/showthread.php?t=695667
will try out and report.
the phone is for sure not branded, was preordere on amazon.de back in the good ol' days and is running Lee's ROM.
http://shipped-roms.com/index.php?category=android&model=Bravo
Check your build number, from there you can see if your phone is branded or not.
BTW: have you wiped everything during rom flashing?
for example,
I have (originally) : 1.19.161.5, and that is a vodafone UK branding.
I have to use : RUU_Bravo_Vodafone_UK_1.19.161.5_Radio_32.36.00.28 U_4.06.00.02_2_release_126338_signed.exe
aaa said:
Check your build number, from there you can see if your phone is branded or not.
BTW: have you wiped everything during rom flashing?
for example,
I have (originally) : 1.19.161.5, and that is a vodafone UK branding.
I have to use : RUU_Bravo_Vodafone_UK_1.19.161.5_Radio_32.36.00.28 U_4.06.00.02_2_release_126338_signed.exe
Click to expand...
Click to collapse
Why not use the 2.33.161.2 RUU in ROM Development?
http://forum.xda-developers.com/showthread.php?t=853937
SOLVED
SOLVED:
Thanks a lot Guys, that was easyier as I thought and saved me a lot of nerves.
I simply flashed 2.29.405.2 RUU and everything was fine!
I just dont unterstand why the stiky thread in the Development section is not being updated with these RUUs. It would have saved me many hours!
Because everyone goes to shipped-roms.com for their stock RUUs
EddyOS said:
Why not use the 2.33.161.2 RUU in ROM Development?
http://forum.xda-developers.com/showthread.php?t=853937
Click to expand...
Click to collapse
No problem with that one.
If I am not mistaken :
It is just that the one you posted will update to Android 2.2 and H-Boot 0.93, while my post ís still 2.1 and H-Boot 0.80.
For comfort reason during rooting, I choose the 0.80.
But seeing as rooting on HBOOT 0.93 has NO issues at all it makes sense to use it
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, I've read so many different threads about rooting/unlocking the Wildfire S that I am kind of confused if I can root mine or no.
The HBOOT screen reads:
MARVEL PVT SHIP S-O RL
HBOOT-0.90.0000 (I have read that many people have problems rooting with this version?)
MICROP-0451
RADIO-7.46.35.00
Apr 8 2011,17:45:10
Also have I read that people with my version have to "skip the RUU step and move to the 2nd step", what is the 2nd step? Where should I start from? I have really read a lot of threads but I'm kind of new to this and I dont want to mess my device up. Thanks everyone.
as i know u must have hboot-1.08.0099 to go trough the htcdev.com method. what is your android ver?
dopefiend said:
HBOOT-0.90.0000 (I have read that many people have problems rooting with this version?)
Click to expand...
Click to collapse
I've seen this too, but I don't know if its fair to say that all phones with HBOOT-0.09.0000 can't be rooted. Have you tried this yet?
[HBOOT] HBOOT update for EU users who's having problem with RUU
Unkheq said:
as i know u must have hboot-1.08.0099 to go trough the htcdev.com method. what is your android ver?
Click to expand...
Click to collapse
I'm Android 2.3.3, HTC Sense 2.1, Software number 1.33.401.2
Just update your android to 2.3.5 what will change soft number to the currect one ^^
Unkheq said:
Just update your android to 2.3.5 what will change soft number to the currect one ^^
Click to expand...
Click to collapse
That also updates my HBOOT? As much as I have read I have seen that updating the Android verison didn't help with the errors.
And I still would like to know what people mean when they talk about "skipping the 1st step (RUU) and move straight to 2nd" with my version?
If u update your android with RUU it can update anything ^^, i flashed my WFS to HTC EU 2.3.5 (as stock i got 0.90.0000 too, after flashing 1.08.0000), there's an tutorial how to do it with RUU.
About skipping, its to get rom_1 and rom_2 from Bootloader unlock Rom, to use it manualy, but i think its a bit dangerous to skip a some versions like from 0.90.0000 to just 1.08.0099. Also what brand your phone is? Orange. T-mobile. ?
I had 2.3.5 android on HBOOT 0.90.0000 (yea, HBOOT ver. didn't changed after new RUU,strange)
Just aplied the RUU from HTCdev.com (HTC EU 2.13.401.2), unlocked it through HTCdev manual, and then rooted using this TUT http://forum.xda-developers.com/showthread.php?t=1432074
dopefiend said:
That also updates my HBOOT? As much as I have read I have seen that updating the Android verison didn't help with the errors.
Click to expand...
Click to collapse
Updating from 2.3.3 to 2.3.5 will not update your HBOOT. That's what the process at HTC dev is for. Try that and if that doesn't work, use the link I posted above.
---------- Post added at 06:58 PM ---------- Previous post was at 06:55 PM ----------
nforester said:
I had 2.3.5 android on HBOOT 0.90.0000 (yea, HBOOT ver. didn't changed after new RUU,strange)
Just aplied the RUU from HTCdev.com (HTC EU 2.13.401.2), unlocked it through HTCdev manual, and then rooted using this TUT http://forum.xda-developers.com/showthread.php?t=1432074
Click to expand...
Click to collapse
Very useful information. This answers the OP's two questions:
1. Does the 2.3.5 RUU update HBOOT? NO.
2. Can some phones with HBOOT 0.90.0000 be unlocked and rooted? Yes.
Until the OP tries to unlock his phone, I don't know what else we can do to help him.
Well my bad
You just need actuall Android version to match the BT UNLOCK RUU.
I installed the 2.3.5 update and tried running the unlocker from HTCdev, i choosed the right version 2.13.401.2 and it says ERROR 190 Rom is not up to date, when i just updated it?
And when i try that trick from SD card, it says Main Version is older, update fail!
HBOOT still shows as 0.90
http://forum.xda-developers.com/showthread.php?t=1445497 here, we are fighting it together. just Check if version is OK