What is this thread about?
There is a known issue where some N1 phones cannot be flashed via the PASSIMG method because their boot loader says "Main version is older!" and stops.
Why is this a problem anyway?
If your bootloader is locked, you cannot flash the stock ROM easily.
If your bootloader is unlocked, you still cannot flash all partitions via fastboot. (A lot of partitions are protected for writing).
What is the "Main Version"?
The Main Version is a string value read and used by the bootloader. It's stored either in the boot loader image itself, or in the misc partition.
You can see your phone's Main Version by bringing it in fastboot mode and executing the following command:
Code:
$ fastboot getvar mainver
mainver: 2.18.1700.1
$
And what is older than what?
Every PASSIMG.ZIP file contains a android-info.txt file that dictates to the bootloader, among other things, the main version that this PASSIMG will bring the phone to. For example, for the commonly used FRG33 PASSIMG file, the main version is 2.16.1700.1. So, the main version on the PASSIMG file is older than the main version of the bootloader on the phone.
So, the phone will be downgraded with that PASSIMG, what's the problem?
Ask HTC or Google that question. I give up on trying to understand why they do not allow downgrading on a dev phone that can officially be unlocked.
Why does this affect only a batch of N1 and not all of them?
I can only speculate on this. It certainly means different production batches with different bootloaders.
This could be due to SLCD vs AMOLED, or an other production differentiation that was never made public by HTC.
So, we need a PASSIMG file stating version 2.18.1700.1 or later, right?
Yes, that's correct. It also is your lucky day, I have digged up such a file online after a week of searching (yes, it was that hard to find it) and I have mirrored it.
Here you go:
PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed.zip
Happy flashing
I'll try it out, the main version is updated for all refurbished HTC Nexus One's from starting a couple of months ago, and I can confirm it.has nothing to do with AMOLED vs SLCD.
Sent from my Nexus One using XDA App
georgemv said:
[snip]
So, we need a PASSIMG file stating version 2.18.1700.1 or later, right?
Yes, that's correct. It also is your lucky day, I have digged up such a file online after a week of searching (yes, it was that hard to find it) and I have mirrored it.
Here you go:
PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed.zip
Happy flashing
Click to expand...
Click to collapse
Awesome find!!!!!
Sent from my Nexus One using XDA Premium App
Excellent news!!!
Great! Downloading it now.
FYI, I just checked my "Main Version" and it is 2.16.1700.1, which I guess is why I have never had an issue with my device recognizing the leaked FRG33 shipped ROM.
UPDATE
Didn't work for me for some reason. It completely skips over everything, like there was no PASSIMG.zip on the card on the first place...
I have the aforementioned MainVer (checked via fastboot) and I renamed it PASSIMG.zip
Tried it twice, downloaded it from the phone and from my computer.
If your phone skipping past, then it's likely that it's not seeing the file. Most common reason for this is because the file is named incorrectly (i.e. PASSIMG.zip.zip - because Windows may not display on of the zip extensions).
I know how extensions work
Will try again tomorrow, maybe from Ubuntu or different laptop. I simply rename the downloaded file PASSIMG as it is a ZIP file.
Sent from my Nexus One using XDA App
Great! Works for me!!!
saratry said:
Great! Works for me!!!
Click to expand...
Click to collapse
Were you having the Main Version problem before?
A simple question!
After installing this ROM FRG83, can I install FRG33 with a previous HBoot without problems?
Maybe I will have the same problem (about main version) when I try to install 2.2 (2.16.1700.1) over FRG83 (2.18.1700.1). Is it posible?
Thanks!! Works for me!!!
I had this problem with FRG83D version and it has been fixed
EDIT: I love you, I can't believe it actually worked!!!!!!
I guess I was using a bad file manager, this time I downloaded it from my phone and CUT AND PASTED (not copied) using ES File explorer and I renamed it using the same software. Worked like a charm!!!!!!!!!
How did you get a hold of this??? I want to find a Gingerbread version of this for safekeeping
might need some help here.
I did everything as said (downloaded, renamed and so on) after the loading the check. occurs but i dont get a message where i am asked if i want to flash the device. it just skipps to the hboot menu again.
anyone some ideas?
Does main version have anything to do with hboot?
My mainver is 2.15, but I'm still on the old hboot. I want to flash the new hboot but not if it's going to also change my main version.
Anyone know?
J.L.C. said:
Does main version have anything to do with hboot?
My mainver is 2.15, but I'm still on the old hboot. I want to flash the new hboot but not if it's going to also change my main version.
Anyone know?
Click to expand...
Click to collapse
I don't know, but I can tell you that I flashed the latest HBOOT, and I still had the earlier main version. Besides, why are you worried about main version. It's been shown in this thread that the FRG83 shipped ROM works even on the newer main version. And you can't run stock Gingerbread on the older HBOOT...
i just ran
Code:
fastboot getvar mainver
on my phone and it shows:
Code:
1.01.1700.1
is this good or bad?
C
good info!
cchhat01 said:
i just ran
Code:
fastboot getvar mainver
on my phone and it shows:
Code:
1.01.1700.1
is this good or bad?
C
Click to expand...
Click to collapse
Doesn't matter. It means you have device with older version of OS initailly, and you didn't use PASSIMG of higher version at all. (If you updated your OS with OTA or manual upgrade only, or flashed custom ROM, main version will remain as its initial value)
Related
Just in case you need it, here it is.
http://www.pcdphones.com/downloads/Eris MR1.zip
This is the Dec 11th update?
Yes but it is the full ruu not just the update if you use this you will loose all of you data and settings.
This may be a work around for those experiencing problems since the update.
this works great for the phone os issues caused by the update. but there are apps in the market that cause your phone to freak out. it's not the eris's fault or the apps fault. when upgrades happen like the way htc did this one it bound to cause some apps to freak out cause of the update. htc has no obligaton to support these apps either that's on the app creator to fix htc is only fixing it's own issues.
this is the reason why htc doe not like quick patches to thier phones. if you look at the history of the dream/G1 this is the first quick patch other than 1.30. because 1.29 allowed root level commands in the contacts area but that was to fix that problem not to fix customer complaints. i just hope htc goes back to the we'll get you a patch when we get you a patch mentality. cause it seems less problematic that way.
just my feelings
binny1007 said:
Yes but it is the full ruu not just the update if you use this you will loose all of you data and settings.
Click to expand...
Click to collapse
Thanks! I did the manual update using RUU as soon as it came out and actually have been pretty lucky...None of the freezing up etc issues that people are having.
Anyone have an updated link?
Hungry Man said:
Anyone have an updated link?
Click to expand...
Click to collapse
I've got the EXE if you have something/somewhere I can upload it to?
You could use megaupload? Or try uploading it to this site aka xda?
If I were to just install the 2.1 leak wouldn't that do basically the same thing? Or is this easier?
The RUU in this thread was for MR1, which is still Android 1.5. I think you're looking for the newer RUU: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe
Ok so if I download that what do I do with it to unroot?
Hungry Man said:
Ok so if I download that what do I do with it to unroot?
Click to expand...
Click to collapse
Attach your phone to your computer with the USB cable, and run the RUU program in Windows. It will wipe all data from your phone and return it to the stock 2.1 software, complete with the 1.49 S-ON bootloader, the default recovery image, and no root.
If you want to re-root from there, you'll have to use one of the new root methods, since your phone will be identical to the phones that Verizon is currently shipping out (with Android 2.1), not the original Android 1.5 version of the software.
Awesome, thanks a ton.
i am trying to use this to unroot my phone so i can send in for a replacement and it goes through all the checks and verifications. it rebbots to the bootloader then while updating signiture i get error 140 bootloader version error saying the rom update utility cannot update your android phone please get the correct rom update utility and try again?? if this doesnt work is there another easy way to unroot?
yamaha83 said:
i am trying to use this to unroot my phone so i can send in for a replacement and it goes through all the checks and verifications. it rebbots to the bootloader then while updating signiture i get error 140 bootloader version error saying the rom update utility cannot update your android phone please get the correct rom update utility and try again?? if this doesnt work is there another easy way to unroot?
Click to expand...
Click to collapse
same here, ruu fails
sleepyastronaut said:
same here, ruu fails
Click to expand...
Click to collapse
If you get a version error, you need to first run jcase's "Flash any RUU" hack.**
Note that (strictly speaking) jcase should have entitled his post "Flash any PB00IMG.zip ROM" because of another small complication: some ROMs do not have a compatible version of the "reboot" command (the RUU utility first uses the reboot command to put the phone into oem-78/RUU mode). If you insist on using the RUU utility, you can overcome this minor problem by first flashing a compatible ROM, such as PlainJane.
But, it is just as easy to flash the Leak-V3 PB00IMG.zip ROM, which produces the identical result as the "Official" RUU.
Note also that if you have used the RUU utility, them you already have USB drivers installed on your PC, and so getting adb running on the PC does not require setting up the full-blown SDK (you don't need Eclipse set up) : just download the SDK, unzip it, and you are ready to rumble.
To reiterate: if you get a version error, you need to run jcase's "Flash any RUU" hack first; after that, you can either run the HBOOT+Leak-V3 PB00IMG.zip install, or the RUU. The PB00IMG.zip method has no dependencies, and is somewhat easier.
bftb0
** Note there is a minor mistake in the instructions given in the OP of the "Flash any RUU" thread; be sure to read the first dozen posts or so - the correction is given.
thenestor said:
The RUU in this thread was for MR1, which is still Android 1.5. I think you're looking for the newer RUU: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe
Click to expand...
Click to collapse
This is the exe that I used to restore my Eris from Kaos Froyo to Stock 2.1. All I did was run the exe file and follow simple prompts. It took about 10-15 mins and the Eris was ready to return to VZW.
Very nice work, Thank you Devs!!!
Does flashing RUU replace the kernel and/or radio? Just wondering
jsuh said:
Does flashing RUU replace the kernel and/or radio? Just wondering
Click to expand...
Click to collapse
I'm pretty sure it replaces both. That's how people discover new kernel and radio versions.
Sent from my xtrSENSE Eris using XDA App
Any idea what I'm doing wrong here?
Windows 7 SP1 x64
mod: If this should be in DHD General, please move it
At the moment, sometimes current RUUs (ROM Update Utility) do not flash from the latest RUU exe - many times it will not recognise the Desire HD.
If you are having this problem, this is how to flash the latest stock RUU.
The latest RUU at the time of writing is 1.32.405.6.
You can download the RUUs from xmoo's thread or from mousey_'s site.
note: This is mainly for stock phones, for vendor-derived ones (e.g Vodafone DHDs in Australia) you will also need a goldcard.
Common Steps
Download the latest RUU (1.32.405.6).
Run it as administrator.
Tick the 'I understand the caution indicated above...' box, and click next.
At this point do not go any further.
Navigate to C:\Users\Ivo\AppData\Local\Temp (Replace my username with yours; AppData is a hidden folder)
You should see one or two folders like this:
{719CE201-7B12-4A13-9AF6-8F359FE69C7B}
Go into the one with dotnetinstaller.exe in it.
Open up the next folder.
Copy rom.zip into another folder (outside of temp).
At this point just Cancel and quit out of the ROM Update Utility.
A) Install through PC
Download and install HTC Sync 3.0 and restart.
Download the 1.15.405.1 Test RUU. It is the only one currently known to find the Android DHD.
Start it the same way as before, get to the
1. Connect the Smartphone to the USB Cable.
step. (but no further)
Again, go to the AppData local temp directory (same as above), and find the folder with dotnetinstaller.exe and inside that, rom.zip
You want to delete the rom.zip (which is the 1.15 version) and replace it with (copy back) the 1.32 rom.zip you copied out earler.
DO NOT UPDATE WITH 1.15 ROM, IT IS NOT DESIGNED FOR RETAIL DHDs.
Now click through the next buttons.
The 1.15 Utility should now be set to update with the 1.32 rom. You will see the version number of the rom at the final step.
Click update and watch the magic happen
B) or Install through Phone
With the rom.zip you copied out earlier, rename it PD98IMG.zip
Copy this onto the root of your microSD card through some means (disk drive, ftp, wireless).
Restart your phone and boot into the bootloader by holding power and volume down at the same time as it restarts.
It should go into the bootloader, take a fair while to check the zip on the sd card, and then ask you if you want to flash it.
Say yes!
Hope this can help some people for whom the 1.32 RUUs aren't working for them
Thanks for putting up this post! I was about to request one last night.
Now if only there could be a similar guide to flashing custom ROMs
To force unroot, I could reinstall RUU 1.32.405.6 from Win7 without problems, a bit longer than updating/reinstalling a WinMo 6.5.x rom (my former HD2), but it went through...
Thanks Ivolol this worked a treat
Appreciate your guide and efforts.
I am running Win 7 64. folowed 1.15 method now running latest 1.32.405.6
Howling Wolf said:
To force unroot, I could reinstall RUU 1.32.405.6 from Win7 without problems, a bit longer than updating/reinstalling a WinMo 6.5.x rom (my former HD2), but it went through...
Click to expand...
Click to collapse
Weird; I tested a couple of RUUs (not as many as xmoo did) and all of them couldn't connect to my phone (whereas 1.15 could).
It'd be interesting to find out what the factors are that cause this. ATM the guide above is what to do if someone finds themselves in the same situation (the current ROMs won't find the phone).
Howling Wolf said:
To force unroot, I could reinstall RUU 1.32.405.6 from Win7 without problems.
Click to expand...
Click to collapse
+1 here, went through the normal RUU process fine just for ****s and giggles. I've extracted the ROM.zip though in case it's needed for future use.
sorry for the noob question..just had my DHD for the last 5 days. I come from galaxy S, and in there whenever we flash a rom all the data gets wiped out.
is it true also when we flash a RUU??
also if I do that...would i still be able to get OTA updates??
nandihno said:
sorry for the noob question..just had my DHD for the last 5 days. I come from galaxy S, and in there whenever we flash a rom all the data gets wiped out.
is it true also when we flash a RUU??
also if I do that...would i still be able to get OTA updates??
Click to expand...
Click to collapse
I haven't got complete knowledge of the entire subject yet, but:
a RUU will completely wipe all user settings / apps. Won't do anything to the sd card though.
An update.zip is akin to an OTA update, it does not wipe user settings.
Flashing with a stock RUU will mean that you can still get OTA updates.
I've tried using the phone method and unable to flash successful. I believe you need a valid GoldCard to use this method.
Can you confirm if the GoldCard is required for doing it with the phone method?
In addition, once the unit (especially our Voda branded one) is flashed with the latest ROM, OTA may not run properly which will result in disabled functionality (as recorded in this thread: forums.whirlpool.net.au/forum-replies.cfm?t=1575514, wifi stopped working). Theory said you'll need a GoldCard to get OTA to work properly (from another thread in XDA).
Thanks.
Great Guide thank you very much. Now i know to flash back to stock now if something gose wrong as iam a noob to android it took some time to work it out even tho it is a simple guide now i wanna know after getting perm root how do i flash a custom rom ? do i need clockwork mod?
tleehm said:
I've tried using the phone method and unable to flash successful. I believe you need a valid GoldCard to use this method.
Can you confirm if the GoldCard is required for doing it with the phone method?
In addition, once the unit (especially our Voda branded one) is flashed with the latest ROM, OTA may not run properly which will result in disabled functionality (as recorded in this thread: forums.whirlpool.net.au/forum-replies.cfm?t=1575514, wifi stopped working). Theory said you'll need a GoldCard to get OTA to work properly (from another thread in XDA).
Thanks.
Click to expand...
Click to collapse
There is a big reason I decided to buy my DHD outright and not through Vodafone
I'm pretty sure that Vodafone's OTAs will be different from HTC's. In order to get OTAs from Vodafone you will need their image on it.
Also with vodafone's ROM installed, I wouldn't think it would accept HTC's vanilla ROM/RUU without going through the entire root process (it would only accept Vodafone signed ROMs). So in order to get onto HTC's ROMs I would think you need to follow http://forum.xda-developers.com/showthread.php?t=841076 before the phone will let you run a HTC RUU on it.
I haven't explored goldcards as I personally have no use for one, but you might also need one by the sounds of it for the Vodafone ROM to let you replace it. (edit: yes it looks like you need one to officially flash from a Vendor ROM to a generic one.)
So this guide is mainly for people with vanilla HTC phones. Although someone has posted a stock rooted Vodafone ROM on the phones so you might be able to use the same techniques outlined here with that.
ssimmmo said:
Great Guide thank you very much. Now i know to flash back to stock now if something gose wrong as iam a noob to android it took some time to work it out even tho it is a simple guide now i wanna know after getting perm root how do i flash a custom rom ? do i need clockwork mod?
Click to expand...
Click to collapse
clockwork mod is useful but not entirely necessary. You might be able to use this guide's method to flash a custom ROM onto it (haven't tried yet), but otherwise I think what you need is a recovery img that will let you upload custom/unsigned ROMs onto it. And also S-OFF I imagine.
ok so i have S-OFF and clockwork mod recovery...
if i have the rom.zip and rename it to PD98IMG.zip and run bootloader.
i shouldnt have any problems flashing this rom??
BTW am using Aus branded Vodafone HDH.
also..IF i flash this rom..would i loose S-Off and clockwork recovery mod??
would flashing this allow me to gain OTA???
nandihno said:
ok so i have S-OFF and clockwork mod recovery...
if i have the rom.zip and rename it to PD98IMG.zip and run bootloader.
i shouldnt have any problems flashing this rom??
BTW am using Aus branded Vodafone HDH.
also..IF i flash this rom..would i loose S-Off and clockwork recovery mod??
would flashing this allow me to gain OTA???
Click to expand...
Click to collapse
If you flash a stock RUU rom.zip then you will loose all custom apps, data, s-off, recovery, etc. It puts it to factory settings. If you are in the business of flashing ROMs then I wouldn't worry about OTA because the developers here will integrate HTC updates as they come out, if they come out
However yes I think if you flashed a stock RUU then you will be able to get OTA. You might still need a goldcard, I'm not exactly sure.
ivolol said:
mod: If this should be in DHD General, please move it
At the moment, sometimes current RUUs (ROM Update Utility) do not flash from the latest RUU exe - many times it will not recognise the Desire HD.
If you are having this problem, this is how to flash the latest stock RUU.
The latest RUU at the time of writing is 1.32.405.6.
You can download the RUUs from xmoo's thread or from mousey_'s site.
note: This is mainly for stock phones, for vendor-derived ones (e.g Vodafone DHDs in Australia) you will also need a goldcard.
Common Steps
Download the latest RUU (1.32.405.6).
Run it as administrator.
Tick the 'I understand the caution indicated above...' box, and click next.
At this point do not go any further.
Navigate to C:\Users\Ivo\AppData\Local\Temp (Replace my username with yours; AppData is a hidden folder)
You should see one or two folders like this:
{719CE201-7B12-4A13-9AF6-8F359FE69C7B}
Go into the one with dotnetinstaller.exe in it.
Open up the next folder.
Copy rom.zip into another folder (outside of temp).
At this point just Cancel and quit out of the ROM Update Utility.
A) Install through PC
Download and install HTC Sync 3.0 and restart.
Download the 1.15.405.1 Test RUU. It is the only one currently known to find the Android DHD.
Start it the same way as before, get to the
1. Connect the Smartphone to the USB Cable.
step. (but no further)
Again, go to the AppData local temp directory (same as above), and find the folder with dotnetinstaller.exe and inside that, rom.zip
You want to delete the rom.zip (which is the 1.15 version) and replace it with (copy back) the 1.32 rom.zip you copied out earler.
DO NOT UPDATE WITH 1.15 ROM, IT IS NOT DESIGNED FOR RETAIL DHDs.
Now click through the next buttons.
The 1.15 Utility should now be set to update with the 1.32 rom. You will see the version number of the rom at the final step.
Click update and watch the magic happen
B) or Install through Phone
With the rom.zip you copied out earlier, rename it PD98IMG.zip
Copy this onto the root of your microSD card through some means (disk drive, ftp, wireless).
Restart your phone and boot into the bootloader by holding power and volume down at the same time as it restarts.
It should go into the bootloader, take a fair while to check the zip on the sd card, and then ask you if you want to flash it.
Say yes!
Hope this can help some people for whom the 1.32 RUUs aren't working for them
Click to expand...
Click to collapse
As I am Newbie of Android and I have noob quesitons. Could you please explain what is RUU and use this for what purpose?
Yeah. I got a goldcard inside of my phone but the bootloader doesn't recognize the P98IMG on my sdcard even though its there for sure. No idea how to fix this
Dr. lele said:
Yeah. I got a goldcard inside of my phone but the bootloader doesn't recognize the P98IMG on my sdcard even though its there for sure. No idea how to fix this
Click to expand...
Click to collapse
How big is ur sd-card, and also what brand. Sometimes this is also a issue....
It's a kingston 8 gb class 4, but thanks for the tipp, I'll try another.
Yep, it was the sdcard xD. It's updating as I type
Carnt I just use the updater on the pc with the Rom? I have tried the method and I don't see a Rom file just a data1 file which is a ear file. I really would like stock ROM on my device
edit: i just used the exe and it installed perfect, so now it should be stock with no root,and sn
cxeka7 said:
As I am Newbie of Android and I have noob quesitons. Could you please explain what is RUU and use this for what purpose?
Click to expand...
Click to collapse
An RUU is an exe which contains the stock 'firmware' from HTC to flash to your device. Basically it will do a full factory reset of your device. It won't wipe your sdcard but it will overwrite everything else.
it didnt asked me for anything on option B) or Install through Phone. i didnt get the option to flash it.
Hi
I've been hammering at this problem for weeks now and its really frustrating. I'm hoping someone can help me out here.
I cant get my phone to update to Froyo. I'm dying to see if the update wil fix my missing wifi issue that I picked up with the last update.
Currently I'm at:
Firmware version: 2.1-update1
Baseband version: 47.26.35.04u_7.05.35.26L
Kernel version: 2.6.v29-e3993620 htc-kernel(at)and18-2 #1
Build number: 2.06.709.3 CL193617 release-keys
Software number 2.06.709.3
The phone is unbranded, bought in China. I'm not sure if it was tampered with.
My phone picks up the OTA update:
OTA_Legend_Froyo_s_hTC_Asia_TW_3.15.709.3-2.06.709.3_release_160364d6o5a2er5k3kbifl
this fails on install, red triangle at about 25%
Tried doing it manually:
renamed above file to update.zip and copied to root of SD card
In HBOOT there is an error something about "legedimg" missing flashes up
Selecting recovery mode gets me a red triangle
pressed (power+vol up)
gets me into system recovery, there is a warning at the bottom "Can't open >cache >recovery>command
selected apply sdcard:update.zip, it works for a little while
get a bunch of stuff about "ro.cid" and and finally "HTC__621". "error in >sdcard >update.zip" (status 7)
Also fails.
Can anyone tell me what's going on here? HTC support has been useless. I'm now really stumped. Do I need a goldcard?
Hi! Yes, you need a goldcard because of the different CID you have and the update.
You may look for an update for your CID.
Why not root it while you're at it?
Thanks!
What is a CID? Is this not the correct update for my phone?
Are you suggesting that if I find the correct update I wont need goldcard or root?Where might I look for an update that matches my CID?
Since I'm on a mac, and dont have easy access to a PC rooting and goldcarding is a bit of a pain...
CID is Carrier ID, a number that locks your phone to carrier-specific firmware...
And yes, you need an update for your CID, then you don't need GC...
thanks. so do I have this straight:
1. My phone is locked to take only carrier specific firmware (even though its not actually sim-locked since I can use any sim I want) Sooo... "debranding" wont actually help
2. an update with the correct CID would work - though I dont know which one I need.
3. a goldcard would let me install the latest update via update.zip despite the CID issue
When I spoke to HTC support they said something about my phone originally belonging to Vodafone Germany. It was strange since I definitely have the chinese version loaded. I could try loading the vodafone germany update but then wont my phone become sim-locked again?
Am I getting this right? Thanks you have been a great help!
1. SIM lock and CID lock are two different things...
2. Yes, if the HTC said Voda Germandy, they're probably right...I presume you have purchased it from someone who used it before?
3. Of this I'm not sure, but It wil definitely help you root your Phone...
If you don't want to root, you can try to find an RUU upgrade - that's and app that will upgrade your phone from PC - try www.shipped-roms.com. But again, you need one that matches your CID.
edit: If you flash the RUU, rooting will be harder
Dr.Romca said:
1. SIM lock and CID lock are two different things...
2. Yes, if the HTC said Voda Germandy, they're probably right...I presume you have purchased it from someone who used it before?
Click to expand...
Click to collapse
Eemm, no. It was "new". They probably did something dodgy to keep the price down. Somehow, despite the CID issue, they were able to install the chinese firmware. It doesn't make much sense.
Dr.Romca said:
3. Of this I'm not sure, but It wil definitely help you root your Phone...
If you don't want to root, you can try to find an RUU upgrade - that's and app that will upgrade your phone from PC - try www.shipped-roms.com. But again, you need one that matches your CID.
Click to expand...
Click to collapse
As far as I can see the latest for Vodafone Germany is "RUU_Legend_Vodafone_AT_GER_Mobilkom_1.31.177.3_Radio_47.26.35.04_7.05.35.26L_release_126862_signed.exe"
I dont think this is actually Froyo?
That might mean that a goldcard is the only option. I take it the goldcard would essentially allow me to bypass the CID check and install whatever update I wanted?
I tried to install the latest vodafone version via update.zip on the SDcard, no luck, "assert failed"... status 7...
Sorted!
Well, I managed to sort mine out and upgrade to Froyo. And I got my WIFI back too!
Very simple...
1. Create Goldcard: Droid Den - Android Guide: How To Create a Gold Card
2. Install RUU (Legend Froyo WWE): Index of /shipped/Legend/
Worked a treat and was actually very simple using the goldcard helper app they recommend on that post. You need access to PC.
I tried updating using update.zip through recovery but that didnt work.
Phone is now working 100%.
I suppose issues might come up when I try to update next time OTA (if there is another OTA for legend), but worse case scenario I will have to use another RUU.
glad it worked out for you... can't imagine going trhough the stress
that's why im waiting for the Official OTA
Good it worked
@Qksi1ver: why are you waiting for OTA?If you root now, you have a shot at S-OFF, If you update your HBOOT, you wont be able to S-OFF...just sayin...
Sent from my HTC Legend using XDA App
hey wat does updating the hboot do? do u have to like update it in order to install some of the roms or somethin?
An update in hboot can be diff. things. One being a radio update (which you never want to flash that same file twice or you'll brick you phone), but there are other things you can update as well. If you are getting the message to up date it when you are goint into revovery, there is more than likely and update.zip in your sd card. I would delete it if you aren't sure why it's there!
i was just asking because every one is like saying that they updated to 0.92 or something and i dont even know what version i have lol
andrix10 said:
i was just asking because every one is like saying that they updated to 0.92 or something and i dont even know what version i have lol
Click to expand...
Click to collapse
Not exactly sure what the updated versions do exactly, but I can tell you how to check which one you currently have. Power off, then hold volume down and press the power button. At the top it should say HBOOT something.somethingsomething. There you have it lol
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS5.3.
jackbtha1 said:
One being a radio update (which you never want to flash that same file twice or you'll brick you phone)
Click to expand...
Click to collapse
That is incorrect. A radio can be flashed over itself. What cannot be flashed twice is a radio patch file since they contain no error checking and simply overwrite what they please. Full versions, such as those contained in PB31IMG.zips are not problematic in that regard.
andrix10 said:
hey wat does updating the hboot do? do u have to like update it in order to install some of the roms or somethin?
Click to expand...
Click to collapse
Updated HBOOTs bring some "under the hood" enhancements that the end user really isn't going to notice. To answer your second question, though, some ROMs do require an updated HBOOT. A handful, for instance, won't boot unless you have HBOOT .92
najaboy said:
That is incorrect. A radio can be flashed over itself. What cannot be flashed twice is a radio patch file since they contain no error checking and simply overwrite what they please. Full versions, such as those contained in PB31IMG.zips are not problematic in that regard.
Click to expand...
Click to collapse
If that is true, you'll still never see me flash the same radio twice I don't like pushing my luck in hboot.
Sent from my CM7 Incredible.
Hello,
i've been reading a lot in this Forum since i've got my DesireZ and so far everything worked for me...when i got the Phone i installed CM7 and tested few RADIO's/RIL's....and until now everything worked for me (after some tries).
But since my batterylife seems kind of poor for me (i have a Mugen 1800mah battery and with 3G i have max 1 day) i'm playing around with a lot of RADIOs...one week ago i saw in someones signature that he was using kind of an old baseband (12.28b.60.140eU_26.03.02.26_M) with the ROM i like best (ILWT-CM7) so i downgraded...but the battery life did not really improve..so i wanted to try another radio but it simply does not work...when i did this before i just copied the PC10IMG.zip to the root of the sdcard, booted into hbot and installed (worked a lot of times for me) but now it's just saying that there is no image, downloaded different files, always checked md5...so i tried the fastboot method which ended up saying
$ sudo ./fastboot flash radio radio.img
sending 'radio' (24960 KB)... OKAY
writing 'radio'... FAILED (remote: not allowed
i've googled the error and saw that the cause is that i did not install eng-hboot...i will try to install eng-hboot and try again but i think i've done this when rooting the device...i will try to install eng-hboot (again) and try the fastboot method.....but i still don't understand why i can not install the radio through hboot....
any hints for me?
smokey_joe said:
Hello,
i've been reading a lot in this Forum since i've got my DesireZ and so far everything worked for me...when i got the Phone i installed CM7 and tested few RADIO's/RIL's....and until now everything worked for me (after some tries).
But since my batterylife seems kind of poor for me (i have a Mugen 1800mah battery and with 3G i have max 1 day) i'm playing around with a lot of RADIOs...one week ago i saw in someones signature that he was using kind of an old baseband (12.28b.60.140eU_26.03.02.26_M) with the ROM i like best (ILWT-CM7) so i downgraded...but the battery life did not really improve..so i wanted to try another radio but it simply does not work...when i did this before i just copied the PC10IMG.zip to the root of the sdcard, booted into hbot and installed (worked a lot of times for me) but now it's just saying that there is no image, downloaded different files, always checked md5...so i tried the fastboot method which ended up saying
$ sudo ./fastboot flash radio radio.img
sending 'radio' (24960 KB)... OKAY
writing 'radio'... FAILED (remote: not allowed
i've googled the error and saw that the cause is that i did not install eng-hboot...i will try to install eng-hboot and try again but i think i've done this when rooting the device...i will try to install eng-hboot (again) and try the fastboot method.....but i still don't understand why i can not install the radio through hboot....
any hints for me?
Click to expand...
Click to collapse
Is it possible that you flashed an "official" rom since your last radio flash? That might account for the loss of the eng hboot. What does it say in the bootloader menu? ship or eng?
EdKeys said:
Is it possible that you flashed an "official" rom since your last radio flash?
Click to expand...
Click to collapse
no i've just updated ILWT to the latest version
EdKeys said:
That might account for the loss of the eng hboot. What does it say in the bootloader menu? ship or eng?
Click to expand...
Click to collapse
now i see...it's really SHIP, but i'm quite sure that this is always been that way...so i never had an eng hboot...good to know...i will try the fastboot method after i've installed eng-hboot and then try again to update
smokey_joe said:
no i've just updated ILWT to the latest version
now i see...it's really SHIP, but i'm quite sure that this is always been that way...so i never had an eng hboot...good to know...i will try the fastboot method after i've installed eng-hboot and then try again to update
Click to expand...
Click to collapse
You don't need the eng hboot to upgrade with the pc10img.zip so that's kind of odd that you can't upgrade that way. Double check the naming of the file and make sure its PC10IMG.ZIP and not PC10IMG.ZIP.ZIP I've seen others mention that it can get named that way by accident.
I do like having the eng hboot however as it does give you more options.
EdKeys said:
You don't need the eng hboot to upgrade with the pc10img.zip so that's kind of odd that you can't upgrade that way. Double check the naming of the file and make sure its PC10IMG.ZIP and not PC10IMG.ZIP.ZIP I've seen others mention that it can get named that way by accident.
Click to expand...
Click to collapse
i've double and triplechecked this....the file is named correctly...(i am using linux to adb push the file so theres no way that i've disabled the file extension hide thingy in windows).
since the file was always named PC10IMG.zip with lowercase .zip i've tried to name it to PC10IMG.ZIP which did not change anything...still the file is not found by hboot.....
EdKeys said:
I do like having the eng hboot however as it does give you more options.
Click to expand...
Click to collapse
yes i thing it should not be needed to install eng hboot...but i see no chance to change my radio......and i don't get how to install the eng hboot...i read the howto and the only way i see is to use gfree which will not work since i need to load the wpthis kernel module...which is only available for 2.6.32er kernel and i am not sure if this will run with my android version...
hmmm that's quite interesting....i've been playing around...and when i go to recovery mount the sdcard and choose install zip from sdcard it lists all my Directorys on the card but not the zip files (there are 2, the PC10IMG.zip and the efs_wipe zip file) which i see when i look with the filemanager but not in recovery...and the hboot does not see it either.
Is there a relation?
EDIT: thats quite interesting...i tested with another sdcard..that worked....but sdcard seemes to be okay....md5sum is okay....just that zip files are not found in hboot and recovery...