Ok. So I have a Rogers Dream. I rooted it and flashed to cyan froyo. All was well. Long story short I need to send the phone back to rogers. I tried the first unrooting procedure I found and am stuck now. I tried the Dream/G1 unrooting method. I am now stuck with a T-Mobile G1 bootloader and cannot load any images from here.
I have spent the last 2 days seraching every rogers unrooting thread I could find with no success.
I am looking to get back to the rogers 911 update so I can send the phone back.
I hate to post when i'm sure it has been covered. But any help would be awesome. Any info you need I can provide asap
Sounds like you tried to install a T-Mobile ROM in a Rogers phone. You would have to use a gold card to make that work, but you would be left with a tmo branded phone. Try searching Rogers' site for their latest full ruu, probably the one with the 911 patch.
I have that. But I need to be able to boot up fully to run that. I have the t-mobile bootloader.. and thats it
You will need to reflash the T-Mobile rom with a goldcard until it will boot, root it via telnet after signing into Google (via a wifi hack?) then install 1.33.2003 spl, that will let you use fastboot to install 1.33.2005 and thus the rogers rom.
Hope the defect isn't going to interfere with this..
Ok. Now I just read a procedure on creating a gold card. This requires a running phone? This phone.. does not run. I can get into the bootloader and thats about all.
You can see if you can boot and wipe from recovery. If then android boots you may be able to skip the gold card.
However you are I assume stuck on HBOOT-0.95.0000
If you download the rogers nbh, rename it to DREAIMG.nbh, place it on the root of your SD and try to flash by turning the phone on holding camera, you will likely receive an error (if not it will flash the Rogers rom)
If you get the error you will need to flash rc29 the only DREAIMG.nbh known to work, the problem is its signed for the us T-Mobile region and you have a phone for the rogers Canada region.. the way to skip the region check is you make a goldcard and use that to flash the nbh.
This requires you to know the Cid of an SD card.. and the easiest way to find that is a working android / winmo phone (does not need to be the broken phone, you can make the goldcard on a friends phone and use it in yours). This is because most USB sdcard readers don't provide access to the cid.
With the goldcard you can try to flash rc29 again, hopefully boot android, root it like a T-Mobile phone, reinstall (carefully) dangerspl allowing you to at last safely flash the rogers rom.
Short of time travel and preventing your past self from installing a T-Mobile stock rom on a Rogers phone.. I'm short on alternative ideas.
I am stuck with HBOOT-1.33.0009
The RC29 DREAIMG.nbh wont flash.
skylinegts said:
I am stuck with HBOOT-1.33.0009
The RC29 DREAIMG.nbh wont flash.
Click to expand...
Click to collapse
That is not the T-Mobile bootloader.. that is an older rogers one (and other HTC branded dreams)
And here is the rogers unroot instructions
http://forum.xda-developers.com/wik...Branded_EBI1_Dreams#Returning_to_Stock_Rogers
And on the topic what isn't working that you are thinking the phone requires to be returned?
that worked! thanks!
Related
Ok so here's the problem...
I was able to root my Rogers Dream but then I messed up with trying to partition the sd card. It was then that it would not go past the rogers screen. After A LOT of reading I downloaded what I thought would the files I need to simply restore the phone to factory. Long story short, if I just turn the phone on it sits at the Rogers screen, I no longer have recovery mode and my fast boot goes to a RGBW screen with Serial0.
Also on the FastBoot screen it states:
DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.2.19.26I
I really just want to return the phone to the state it was before rooting it (store bought state). But because I can't access the fastboot through USB or even get to the Engineering SPL I'm really..really stuck!!
If I can get the proper FastBoot loaded somehow I think I can restore the rest.
Any help would be greatly appreciated.
no it is not bricked, try removing the sdcard
Still nothing.
Also if I press Home+Power or Camera+Power it still ends up at the same RGBW screen.
No, it isn't bricked
You are stuck at the stock SPL. I'm not sure about rogers but for tmobile you would want to put dreaimg.nbh on the root your SD card, load up the SPL. Flash dreaimg.nbh. Then it should boot into rc29 (I believe). Get root access, flash whatever flavor of recovery you want. Then boot into recovery and flash whatever SPL you want. Then you can get back into the SPL and restore whatever nandroid backup you had.
Again, this is what I would do on tmobile. Not sure about rogers, but I would assume since you would be loading your own backup everything will be peachy.
Ya I hear what you're saying. The problem is I can't seem to find an original Rogers DREAIMG.nbh file anywhere. I think I might be SOL and have to take into Rogers to get it fixed. I'm just not sure if I've voided the warranty or not.
I'm stuck at the exact same place - Rogers phone same, settings, screwed up somewhere along the way.
HTC told me (over the phone) that I can call Rogers and request service on my phone for them to flash it back to the original Rogers ROM because they're the carrier, but this would mean sending the device in..... Whether they'll do it or not, I do not know, but right now I'm trying to simply update to the engineering SPL and go from there. Stupid 0.95.0000 version is screwing everything up.
And I haven't been able to find any Rogers .NBH files ANYWHERE that would allow me to get back to factory settings. At this point, I'd be happy to know that I"m getting 3G and can install a custom ROM on my phone so that it'll at least work the way I want it to.
try here >>>>>> http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream/Magic32B_Firmware_to_CyanogenMod
dl the rc7 for europe and see if the fastboot recs it. if not try and find the system.img for rogers and ill tell you how to flash it via fastboot. if you had the system img it would already be good. no use of the nbh. also what is dif from dream and g1 besides apns and a small other few things?? if nothing then why not flash the g1 dreamimg?? once thats good then root and get it finalized? just wondering.
EDIT: I searched more for you. dont try my idea. im kinda dumb lol. i forgot that rogers and tmobile have dif boards. so this wont work and might brick you. so dont listen to me. sorry for missleading. im use to g1's in the usa sorry. ill keep searching for anything for you thou.
EDIT2: in fastboot can you >>>>> fastboot boot "name_of_your_recovery.img" ???
try that in fastboot to see if you can get into recovery. if you have no idea what i mean let me know so i can give some sdk instructions.
Unfortunately I can't because even though I can fastboot it won't allow me to connect to the laptop via usb. Basically the phone never gets to that point.
losingmyself said:
I'm stuck at the exact same place - Rogers phone same, settings, screwed up somewhere along the way.
HTC told me (over the phone) that I can call Rogers and request service on my phone for them to flash it back to the original Rogers ROM because they're the carrier, but this would mean sending the device in..... Whether they'll do it or not, I do not know, but right now I'm trying to simply update to the engineering SPL and go from there. Stupid 0.95.0000 version is screwing everything up.
And I haven't been able to find any Rogers .NBH files ANYWHERE that would allow me to get back to factory settings. At this point, I'd be happy to know that I"m getting 3G and can install a custom ROM on my phone so that it'll at least work the way I want it to.
Click to expand...
Click to collapse
I know! I can't believe out of every bit of information on how to root an Android phone there is basically nothing on how to fix it. At least for anyone using Rogers.
DO what I did, I had the same issue (T-mo) I used a micro Sd "converter" if you will...........and plugged it into my laptop's SD reader, copied the files over, and VIOLA!
I actually thought I bricked it 5 times.
TinBasher77 said:
Unfortunately I can't because even though I can fastboot it won't allow me to connect to the laptop via usb. Basically the phone never gets to that point.
Click to expand...
Click to collapse
I think you've misunderstood.. fastboot mode on the phone enables you to use the fastboot program on your pc to send commands. You can use it to boot a recovery image and flash the files you need to fix this. There's a sticky thread detailing how to set up and use fastboot in Q&A.
Does anyone...anyone at all know where I can get the official Rogers HTC dreaimg.nbh file? I have searched high and low and can't seem to find it anywhere. I'm pretty sure if I can get my hands on it I can fix the phone.
Thanks in advance.
TinBasher77 said:
Does anyone...anyone at all know where I can get the official Rogers HTC dreaimg.nbh file? I have searched high and low and can't seem to find it anywhere. I'm pretty sure if I can get my hands on it I can fix the phone.
Thanks in advance.
Click to expand...
Click to collapse
there is no rogers dreaimg.nbh
Hi,
How did you root your phone?
can you still boot into the recovery img? (home+power)
If you cant, try get back the recovery img (e.g. cm-recovery-1.4.img) and then home+power again. From there you should be able to update your spl to hardspl
Unfortunately I can't boot into fastboot any longer I just get the red/green/blue/white screen. This happens with both Home+Power or Camera+Power so I can't even use adb to force the images onto the phone.
Thanks for the help though.
Well problem solved (sort of).
I contacted Rogers and they're going to send me out a new phone and have me return the "defective" one.
Thanks for all your help and suggestions.
Hi Just got a Rogers Dream from a friend in the following tree color state:
DREA210 PVT 32B RUUNBH
BOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
Serial0
1) I tried safely to install Rogers rom for the htc dream but PC does not detect my USB port failing with error 170.
2) Read Forum for 2 hours, and tried stock firmware, made sure SD card formatted FAT32, DREAIMG.nbh and update.zip it did boot, loading... and error 0002802 not allowed showed.
Can someone point me to the right direction for the next steps?
What kind of more information can I provide? And how to get it? Thx
what are you trying to achieve? That dream is running the 1x radio with a stock T-Mobile spl, thus ought to be used like a T-Mobile g1,
You could run a true rogers nbh via SD card.. but this is probably not going yo give you the phone you wish to use.
Tell me the end state you want to be in we can help you get there.
My goal was to use the damn phone, after 12 hours of struggling I was able to install Haykuro Rogers dream, after that I want to SPL 1.33.2005, Rooted my phone and I installed cm-5.0.7-DS-test5 Rom.
All is fine now thanks for the response.
Ive got exactly the same issue, formatted SD to FAT32 and copied DREAIMG.nbh (RC7) to it. I get the not allowed error and then drop to the multi colored screen with:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.261
Sep 2 2000
Serial 0
I am trying to follow the instructions on the cyanogen wiki to install Cyanogen 5.0.7 on a stock Dream purchased in Australia.
Any pointers will be appreciated, I have tried to reformat, different SD cards without any success.
chocko said:
Any pointers will be appreciated, I have tried to reformat, different SD cards without any success.
Click to expand...
Click to collapse
Because the nbh is for T-Mobile in the states.. thus fails the carrier checks elsewhere in the world.
To get around these checks a goldcard is needed.
But before looking into that.. make sure you can't root by flashreq first. (I can't say I've used the Australian rom so I'm not really sure of your phones state.. the gold card will let you flash that nbh.. but if you can install recovery by flashreq that is safer)
It's usually best to search for people who have rooted the same stock rom as is installed on the phone.
i have a tmobile g1 its giving me the same error code"0002802" when i try to flash the DREAIMG.nbh file from bootloader. so i cant downgrade to rc29. i want to root the phone.any solution?
Haad said:
i have a tmobile g1 its giving me the same error code"0002802" when i try to flash the DREAIMG.nbh file from bootloader. so i cant downgrade to rc29. i want to root the phone.any solution?
Click to expand...
Click to collapse
I answered this best I could here
With both a potential solution:
Did you try a goldcard yet? what was the result?
And a question to help understand why:
Did you answer my question last time of when your phone was jtagged was it with my solution in the wiki or Omnia's solution?
Okay I have the same problems as the op and I have the same radio, spl everything is exactly the same. The phone cannot boot into recovery whenever it starts it goes directly to bootloader. Any help would be appreciated. Thanks in advance.
Not even downgrading
Hello guys,
I tried already one goldcard, made all the procudures to get one and also didnt work, with the gold card says that no IMG not found, with the DREAIMG from USA and EU says that is 'not allow'. I tried as well the DREAIMG.nbh from USA and EU. I bought my phone in Holland, and his configuration is:
DREa110 PVT 32B
HBOOT-0.95.000
CPLD-4
RADIO-1.22.12.29
If you can help me another way out. I'ven been try and I am stucked on this for 3 days.
0002802
strange, in my case I got a phone which I did not know if it was from Europe or the US. I just happened to get the "0002802" error when using what I assume to have been the wrong firmware (European in my case) as when I tried the US version everything worked fine.
Though for the Rogers phone the whole process seem slightly more complicated (check the Cyanogmode wiki for it under Full_Update_Guide_-_Rogers_Dream_EBI1 -- sorry Im new here and I cant post a link =D)
I previously had this phone running Cyanogenmod 6 so skip the n00b bashing. I know wtf I'm doing.
My situation is pretty unique.
I came to Israel from Philadelphia with a myTouch3G about a week ago with Cyan Recovery and Cyan 6 installed. No problems. I put in an Israel SIM Card into my phone and no matter what I tried it would keep crashing the phone process.
Thinking the problem would be fixed if I flashed stock, I did just that and unrooted my phone completely.
The phone is now running stock recovery with 1.6 stock. Israeli SIM card STILL crashes the phone process.
I can't get past the intro wizard because I don't have service. Four corners doesn't work. I would have one click rooted days ago if I could get past it.
My SPL is 1.33.0006 (SAPP300000).
I am trying to get a different SPL onto the phone without a Goldcard so I can root it. I attempted to make a gold card already many times but I had to use a Windows application to get the CID so I don't think it worked because after it analysis the update.zip I get a "Version Mismatch" error.
If someone could recommend a signed SPL that my phone will accept that would then allow me to move on from there I think I'd be able to get past this issue. If I could simply get a custom recovery on this phone I could get back to Froyo where the 4 corners trick does work (or just restore from nandroid back Cyan 6).
The only way I have to copy stuff to an sdcard at the moment is through a working blackberry pearl I have lying around.
Drop me any suggestions. I'll be glad to try them.
Simple... take out your sim-card... then finish the reg part(just skip most of it).. then root... flash custom recovery.. flash eng spl... Full control again :0)
You can also finish the reg part using a wifi :0)
Just take the sim out!
Just tried that. Once I turn the phone on I see the Android intro logo and when I tap it I get a new screen that simply says "No SIM card in Phone" and the only button there is for Emergency calls.
It doesn't let me do anything from that point at all. I can't move past this screen.
Its only going to be a matter of time before people will need to send phones back under warranty for whatever reasons so a guide for unrooting will be needed.
Any takers?
G2 already has one, but obviously we will need different rom/hboot etc to go back to our stock.
Not just unrooting, but going completely back to stock, i.e. S-ON and stock ROM.
As you say, we should be able to base it on this - http://forum.xda-developers.com/showthread.php?t=835971
Although we have several different stock ROMs, e.g. European, Asian, Vodafone UK, etc.
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
gtrab said:
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
Click to expand...
Click to collapse
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
steviewevie said:
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
Click to expand...
Click to collapse
It does say to flash an RUU to S-ON which in the past I would have said would work, but seeing how the G2 forums are not suggesting that its that simple my guess would be that its not that simple.
I had to flash the PC10img thing taken from the stock ROM to restore root and s-on. But no idea how to extract that PC10img thing, not that I have looked into it either.
That info was from one of the guides in the dev section I'm sure.
Sent from my HTC Vision using XDA App
What might work now will probably not work once an OTA update comes out for the DZ though, as per the problem on the G2 they've had which has led to quite a few semi-bricks (possibly full bricks in some cases ?).
Done some research, it would seem that flashing an RUU would work fine for those of us already rooted, if an OTA were to come out those who rooted after the OTA would have issues unless an RUU for the same OTA was released as well. (this is basically because the RUU's currently available will be older than the software the phone is on so the RUU would fail leaving you with a semi-bricked phone as described above, basically it would flash stock hboot and recovery then fail to flash the /system so you would be left with no root or recovery and no rom.
Flashing the ruu would give rise to accepting the OTA too, if you really wanted to do that, but it might block root.
you just need the RUU for your correct original phone version
OR use a gold card
eg. I have debranded mine from bell NAM 1.34.666.5 to euro generic 1.34.405.5
To go back to stock, I can:
1.- grab the bell 1.34.666.1 RUU (its slightly previous, but is the correct original version for my phone)
OR
2.- run the euro generic 1.34.405.5 with a golcard inserted
gtrab said:
you just need the RUU for your correct original phone version
Click to expand...
Click to collapse
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
steviewevie said:
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
Click to expand...
Click to collapse
Yes thats what I was getting at in my post above, any RUU you flash needs to be of the same or newer version of what your previously flashing. You cannot GoldCard to flash an RUU to S-ON or you get left with the semi-brick where you have stock recovery and hboot, but no rom installed.
So if an OTA comes out, you can't accept it, s-off then use an older RUU to s-on again. You would have to flash an RUU of that OTA version (if one is released).
Basically its best to not accept any OTA if you can avoid it and just wait for a custom rom of the same, that way we can always use the older RUU's to s-on if we need it.
I successfully downgraded my rooted/S-OFF'd phone to an earlier ROM last night. I simply followed this method - http://forum.xda-developers.com/showthread.php?t=832503
I'm of the firm belief that this is the onyl way to do it if you are at S-OFF. If you have S-OFF, then flashing an older RUU will probably brick your phone.
Well yesterday I perm root and s-off my european Desire Z with World/Euro generic 1.34.405.5. Somehow everything went bad after flashing recovery mode, so I decided to unroot it and bring it back to original settings.
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Then entered to bootloader, and the phone recognize the archive, I simply apply it, and now I am back again to original stock.
However now I tried again and I am happily root, and S-Off following the amazing gtrab guide (http://forum.xda-developers.com/showthread.php?t=835777)
buzmay said:
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Click to expand...
Click to collapse
That's the thing I keep saying though, flashing the original RUU worked for you because you weren't trying to downgrade the ROM, it was the same version that you already had on (just S-OFF etc). If you had a later version on your phone (e.g. via an OTA update) and were trying to flash to an earlier one, you would have bricked it trying the straight RUU method.
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
By the way - that's a fake RUU
DanWilson said:
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
Click to expand...
Click to collapse
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
steviewevie said:
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
Click to expand...
Click to collapse
I hate HTC.
Love the phones, love the Sense, hate the security.
Why not give us a command like the N1? WHY!?
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
DanWilson said:
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
Click to expand...
Click to collapse
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
steviewevie said:
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
Click to expand...
Click to collapse
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Nice
DanWilson said:
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Click to expand...
Click to collapse
Following that guide that I linked worked for me. Yes, I turned my SD card into a gold card and edited the misc partition. Then it is fooled into thinking you're restoring a ROM of the same version that it already is running, so it lets you do it.
Actually, I do wonder whether both steps are necessary (i.e. gold card *and* editing misc), because I thought the whole point of the gold card was that it avoided those checks, so perhaps you can do one or the other ? I am only thinking out loud here, and may well be missing something, so I don't suggest trying it other than as in that guide.
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