1.29.666.5 ROM from Bell Mobility - Useful for anyone? - One (M7) General

Ok so I came back to android after using an iPhone for a couple years. I had a Galaxy S that scarred me due to it's horribleness. I was into the whole custom ROM thing with it but largely have forgotten how to do all of that stuff.
Anyhow, while I bone back up on it, is anyone interested in me pulling off the 1.29.666.5 stock ROM? It seems to be a newer version than anything I see on the forum. If so, let me know how I can do it and I'll pass it along.
J

You will need to change apns-conf in htc framework, for use is it not in bell network only.

countfloyd said:
Ok so I came back to android after using an iPhone for a couple years. I had a Galaxy S that scarred me due to it's horribleness. I was into the whole custom ROM thing with it but largely have forgotten how to do all of that stuff.
Anyhow, while I bone back up on it, is anyone interested in me pulling off the 1.29.666.5 stock ROM? It seems to be a newer version than anything I see on the forum. If so, let me know how I can do it and I'll pass it along.
J
Click to expand...
Click to collapse
No its actually older. The 666 is regional (or operator), its the number after that indicated how old it is .5 is older than .12 for example. Its a 1.29 base, for 666 region, revision .5

Hey I have a bell HTC One that I already flashed..I would really appreciate it if you could find a way to upload the stock ROM in case I need to go back...
Thanks!

Interesting. So if I get this right. x.x.x.x is the way the firmware/software version is put together. so 1.29 is the base and doesn't change?
If so.. the 3rd octet. is the regional code?.. then the final one.. in my case is .7 is the revision?..
Which would mean that. 1.29.651.7 is older then 1.29.401.12?

DreadfullyDespized said:
Interesting. So if I get this right. x.x.x.x is the way the firmware/software version is put together. so 1.29 is the base and doesn't change?
If so.. the 3rd octet. is the regional code?.. then the final one.. in my case is .7 is the revision?..
Which would mean that. 1.29.651.7 is older then 1.29.401.12?
Click to expand...
Click to collapse
Yes its older latest is .12.

Okay. I don't mind doing the reading to figure out how to pull it off my device. Can someone save me a couple seconds and point me to a link that shows me how to do this...? It is a bit more complicated without and SD card correct?
Thanks,

countfloyd said:
Okay. I don't mind doing the reading to figure out how to pull it off my device. Can someone save me a couple seconds and point me to a link that shows me how to do this...? It is a bit more complicated without and SD card correct?
Thanks,
Click to expand...
Click to collapse
did you ever get a copy of this?

Rogers and Telus are now pushing .17
Sent from my HTC One using Tapatalk 2

Bell pushed out 17 as well.

Can u guys pls upload the stock radio?

Related

G1 1.6 official firmware

I have a question I've been trying to resolve looking through the threads and have been unable:
I have a g1 that's rooted running android 1.5, and from what I can tell its either on the official t-mobile firmware or the developers firmware... I want to upgrade to android 1.6 mostly just for the text to voice and the voice navigation in google maps. I don't really want to load custom roms though... Is there anyway to load into android 1.6 and keep root, but have everything else the standard firmware?
developer.htc.com/adp.html
You can grab the official ADP1v1.6 firmware and write that to your device for a stock-but-root system image. (note: stupid people will tell you that it doesn't have root. They are incorrect, it most definitely DOES.)
lbcoder said:
developer.htc.com/adp.html
You can grab the official ADP1v1.6 firmware and write that to your device for a stock-but-root system image. (note: stupid people will tell you that it doesn't have root. They are incorrect, it most definitely DOES.)
Click to expand...
Click to collapse
It just gives the impression of not having root by flashing the stock recovery (which many people consider root for some reason)
oh lovely, after following those steps. The radio went fine the phone rebooted fine, but after the recovery image, the phone hangs on the android screen for a long time, and then pops up with continues force close error messages. I also can no longer boot into recovery it gives me a picture of a phone with an exclamation point.
Anyone have any ideas?
oh n/m. That exclamation point screen was in fact the recovery screen, it was different before i installed this. I formatted the memory card and wiped the data, and that seemed to do the trick, I'm up and running in 1.6 developers build. thanks guys =-)
Yeah, when I read your previous message I was about to suggest that...
Newbie-ish question
Hey all,
I know this sound a bit amateur, but I was just wondering if it were possible to flash the same G1 Dev Rom onto my Rogers HTC Dream running the newest "perfect" firmware. I would imagine that the HTC one is officially signed so the phone wouldn't have any trouble accepting this...can anyone confirm? I just wanted to make sure before I go ahead and do anything as I'm new to the whole Android thing. Thanks!
n64_ali said:
Hey all,
I know this sound a bit amateur, but I was just wondering if it were possible to flash the same G1 Dev Rom onto my Rogers HTC Dream running the newest "perfect" firmware. I would imagine that the HTC one is officially signed so the phone wouldn't have any trouble accepting this...can anyone confirm? I just wanted to make sure before I go ahead and do anything as I'm new to the whole Android thing. Thanks!
Click to expand...
Click to collapse
You're right. You're definitely an amateur
1) There is *no such thing* as a "G1 Dev". There is an "Android Dev Phone 1" (aka "ADP1"). G1 and ADP1 are both HTC DREAM, as is the thing that was sold by robbers (although the robbers-crippled dream has some minor differences).
2) Though signed, it still won't write onto your phone since it is signed with a DIFFERENT SIGNATURE.
3) If you *did* manage to write it, you would be effectively bricked since the ADP1 kernel won't boot on the robbers-crippled-dream. At this point, it *might* be possible to write the same firmware that you already have on it again to fix the brick, but since nobody has gotten to this stage, it is unknown.
Haha glad I didn't go ahead and do anything stupid, then! Thanks for enlightening me!
Cheers
n64_ali said:
Haha glad I didn't go ahead and do anything stupid, then! Thanks for enlightening me!
Cheers
Click to expand...
Click to collapse
Don't worry, because of the incorrect signature, you couldn't have hurt it even if you tried.

Need info regarding 2.1 Official

has anyone done a ROM based on the RELEASED 2.1 yet? I know that the MD5 is the same, but files sizes are different and the "Leaked" one we got has BT and Audio issues. Just wondering if anyone has compared the two yet?
None of the leak based 2.1 ROMS will let my phone sleep unless I go into running services and Kill OBEX.
gunnyman said:
has anyone done a ROM based on the RELEASED 2.1 yet? I know that the MD5 is the same, but files sizes are different and the "Leaked" one we got has BT and Audio issues. Just wondering if anyone has compared the two yet?
None of the leak based 2.1 ROMS will let my phone sleep unless I go into running services and Kill OBEX.
Click to expand...
Click to collapse
Not yet.
Go make one.
Im a bit confused here. The sprint release is the same as the leak you guys had a week ago correct? So why is the leak rooted but the new release is not as of yet? Whats the difference between the two roms?
Damage pulled the bits out of the RUU and made them into an Update Zip. I was asking if anyone had done that with the Official yet.
gunnyman said:
Damage pulled the bits out of the RUU and made them into an Update Zip. I was asking if anyone had done that with the Official yet.
Click to expand...
Click to collapse
I don't think anything has been done with the official yet, i wonder why?
markus_del_marko said:
Im a bit confused here. The sprint release is the same as the leak you guys had a week ago correct? So why is the leak rooted but the new release is not as of yet? Whats the difference between the two roms?
Click to expand...
Click to collapse
The leak that was signed with release keys did not have root...period.
A dev patched it with root. 2 different roms there. K?
markus_del_marko said:
I don't think anything has been done with the official yet, i wonder why?
Click to expand...
Click to collapse
Big things are cooking...Can't you smell it.
On the MD5:
How the hell are file sizes different but the return the same check sum? WTF?
I wasn't aware they were different sizes. Maybe I don't understand how MD5 works as well as I should.
Download the new RUU, do NOT run it as an RUU, but instead, extract the rom.zip and flash it. You'll keep root that way.
HeroMeng said:
Download the new RUU, do NOT run it as an RUU, but instead, extract the rom.zip and flash it. You'll keep root that way.
Click to expand...
Click to collapse
Doesn't he still have to patch SU in? and SH?

my X10a isnt updated to latest build number?

hello
from what i have been reading build number should be R2BA026.
mine is still R2BA023, is this normal?
i have ran SEUS, and the "software update" on my phone and they all show its updated
Are you branded or unbranded
Sent from my X10a using XDA App
Yes its normak if you have a brandet version. That means your carrier need to send out the firmware to seus. They maybe just eaitet fir the android 2.1 update. Instead of rolling 26 aswell
Sent from my X10i using XDA App
i have a X10a through telstra, its also rooted.
wonder if i'll ever get updated?
aussiesausage said:
i have a X10a through telstra, its also rooted.
wonder if i'll ever get updated?
Click to expand...
Click to collapse
mate, u will either need to debrand completely, or flash your phone with a different ROM
(or is that basically the same thing !) i flashed my optus branded x10 with global generic (i think its UK or Nordic) and all is good.
another benefit of this is that u wont have to wait for Helstra to get their finger out and have a 2.1 branded ROM for you. if you have a generic rom, then you get the 2.1 update as soon as its available (via seus obviously)
cheers, tim
edit: when you run SEUS - it checks what version you have (telstra) and then looks in the dB for the latest telstra rom available. telstra have only published/released up to the version you are running, therefore "no updates available". If you were running a generic version, when you connected up to SEUS it would be looking for a different version. hope that is a bit clearer
if i completly debrand it, and something happens to it, can i just brand it again and send it back, kinda like. rooting then un-rooting ect
?
mrtim123 said:
mate, u will either need to debrand completely, or flash your phone with a different ROM
(or is that basically the same thing !) i flashed my optus branded x10 with global generic (i think its UK or Nordic) and all is good.
another benefit of this is that u wont have to wait for Helstra to get their finger out and have a 2.1 branded ROM for you. if you have a generic rom, then you get the 2.1 update as soon as its available (via seus obviously)
cheers, tim
Click to expand...
Click to collapse
I'm also with optus, do I need to flash mine? or is optus quick with releasing updates.
Also does you optus My account widget works in your phone, coz mine doesn't show data usage.
I contacted optus to find out why and they had no idea that we got a widget in the first place
aussiesausage said:
if i completly debrand it, and something happens to it, can i just brand it again and send it back, kinda like. rooting then un-rooting ect
?
Click to expand...
Click to collapse
sure can mate, look at the decrypted ROMS page in the DEV section. But unless something serious goes wrong, you will never load a telstra rom on it again
HQXU said:
I'm also with optus, do I need to flash mine? or is optus quick with releasing updates.
Also does you optus My account widget works in your phone, coz mine doesn't show data usage.
I contacted optus to find out why and they had no idea that we got a widget in the first place
Click to expand...
Click to collapse
I found that optus were the quickest of the Aussies, but still they would be a few weeks behind. You will NOT get the update within the same day as it gets released - put it that way.
re: widget - yeah mine never worked but now im on generic i dont have it anyway
wow, i just had a look through that thread, and theres pretty much nothing that would walk me through it, so basically i think i would screw my phone
unless ofcourse you feel like helping me, it sounds good!
could you help me out with what i need to get started or a tutorial or something?
aussiesausage said:
wow, i just had a look through that thread, and theres pretty much nothing that would walk me through it, so basically i think i would screw my phone
unless ofcourse you feel like helping me, it sounds good!
could you help me out with what i need to get started or a tutorial or something?
Click to expand...
Click to collapse
right, im gunna want a bit of confirmation from others here....been a while since i did this.
using Bin4ry's post http://forum.xda-developers.com/showthread.php?t=711907 i grabbed the latest files from the fileshare websites listed. basically the files that Bin4ry and the other guys have created are a script (batch files) that prompt you step by step. i know the method is called ROOT but its the same process. To ROOT in this original method, you had to flash back to an older revision of the firmware and then update. When you flash back to the older version, it is a generic version. Then you can simply use SEUS to update to newest. KEEP IN MIND that doing ANY kind of firmware update will completely erase anything on the internal memory. This is NOT the sd card, so pics and such will be ok but contacts - msgs - settings will all be gone. might be best to do the one-press root, install titanium backup first and then backup your phone book and other important apps that you may have.
main thing is to ask questions. there are sh!tloads of ppl on here with heaps of knowledge. be safe in the knowledge that you cannot, CANNOT completely screw your phone. you can always flash another firmware back onto it using SEUS. once ppl hack the bootloader, this will be a different story but until then just get in there and have a go
good luck and happy modding!!
mrtim123 said:
right, im gunna want a bit of confirmation from others here....been a while since i did this.
using Bin4ry's post http://forum.xda-developers.com/showthread.php?t=711907 i grabbed the latest files from the fileshare websites listed. basically the files that Bin4ry and the other guys have created are a script (batch files) that prompt you step by step. i know the method is called ROOT but its the same process. To ROOT in this original method, you had to flash back to an older revision of the firmware and then update. When you flash back to the older version, it is a generic version. Then you can simply use SEUS to update to newest. KEEP IN MIND that doing ANY kind of firmware update will completely erase anything on the internal memory. This is NOT the sd card, so pics and such will be ok but contacts - msgs - settings will all be gone. might be best to do the one-press root, install titanium backup first and then backup your phone book and other important apps that you may have.
main thing is to ask questions. there are sh!tloads of ppl on here with heaps of knowledge. be safe in the knowledge that you cannot, CANNOT completely screw your phone. you can always flash another firmware back onto it using SEUS. once ppl hack the bootloader, this will be a different story but until then just get in there and have a go
good luck and happy modding!!
Click to expand...
Click to collapse
thankyou, but my phone is already rooted, does that mean i can install a diffrent ROM? or has other stuff gotta be done to isntall a diff one?
mrtim123 said:
I found that optus were the quickest of the Aussies, but still they would be a few weeks behind. You will NOT get the update within the same day as it gets released - put it that way.
re: widget - yeah mine never worked but now im on generic i dont have it anyway
Click to expand...
Click to collapse
a few weeks thanks I will try to flash it.
aussiesausage said:
thankyou, but my phone is already rooted, does that mean i can install a diffrent ROM? or has other stuff gotta be done to isntall a diff one?
Click to expand...
Click to collapse
main reason that you would root first is so you can use titanium backup to backup your apps and settings. You will still need to flash to a non branded firmware, jerplea has a few ROMS on his posts, probably best to have a look in those threads and ask the masters
i am by no means an expert, i just fumbled my way through it
mrtim123 said:
main reason that you would root first is so you can use titanium backup to backup your apps and settings. You will still need to flash to a non branded firmware, jerplea has a few ROMS on his posts, probably best to have a look in those threads and ask the masters
i am by no means an expert, i just fumbled my way through it
Click to expand...
Click to collapse
heh, i just bricked my phone trying the SEUS way lol, fixed it though
i got no need to back up, nothing on there as its a pretty new phone anyway
trying that flash tool thing from the decrypted roms thread
confusing as hell
oh man, i give up. i got no idea how to do this from any of the posts.
just tryed the flash tool thing and it wont work either.
i give up
aussiesausage said:
oh man, i give up. i got no idea how to do this from any of the posts.
just tryed the flash tool thing and it wont work either.
i give up
Click to expand...
Click to collapse
when you say wont work....what do you mean? When running the flash tool are you following the prompts on screen? you need to have USB Debugging enabled on the Settings=>Applications=>Development enabled. let me kow where it is failing and we might be able to get it working for ya....if you are still keen anyway
just been reading through the original post from Bin4ry again (the flashing/rooting one)....i think that you should post on it exactly where the problems are, where it is failing and what you are doing. There are several active users on there that are very knowlegable on flashing
http://forum.xda-developers.com/showthread.php?t=711907
i have debugging enabled.
i turn my phone off, hold down back, plug it in. and the green light lights up ( as it says in the read me ), i start X10flash.bat, and then it says C:/andrew/downloads/X10flash.jav -jav. ( or something like that ) is not a valid internal or external command, press enter to exit
aussiesausage said:
i have debugging enabled.
i turn my phone off, hold down back, plug it in. and the green light lights up ( as it says in the read me ), i start X10flash.bat, and then it says C:/andrew/downloads/X10flash.jav -jav. ( or something like that ) is not a valid internal or external command, press enter to exit
Click to expand...
Click to collapse
it sounds like a java problem actually.....do you have java installed?
what OS are you on? if its Win7 64bit (or Vista 64bit), there is a 64bit java fix that you need to run also. have a look at this thread - http://forum.xda-developers.com/showthread.php?t=713457
if you are on a 32bit machine then chances are its a deviceID issue but from what you have posted above - it looks like the java problem.
win64 bit, and i think i got java cant remember lol.
will check it out though soon thanks

New to Epic/Android -- quick ROM flashing questions

Hi there,
I just sold my iPhone and got an Epic 4G and I am already rooted but I am looking to flash to a Froyo ROM. I see that you need to flash the modem as well as the rom, and you cannot back up the modem. If something happens after the flash and I need to roll back, how do I go back to 2.1?
Also, There is only 1 Froyo leak, right? Is that the DK17 that I see mentioned? Is there a chart of these build #s and what they have?
Thanks
algorhythm said:
Hi there,
I just sold my iPhone and got an Epic 4G and I am already rooted but I am looking to flash to a Froyo ROM. I see that you need to flash the modem as well as the rom, and you cannot back up the modem. If something happens after the flash and I need to roll back, how do I go back to 2.1?
Also, There is only 1 Froyo leak, right? Is that the DK17 that I see mentioned? Is there a chart of these build #s and what they have?
Thanks
Click to expand...
Click to collapse
1st: good move, such a better phone.
2nd: you can almost always return your phone to stock, AS LONG AS a) you can boot into recovery and 2) you have the proper files to flash.
Having said 2(2), you should look here. There you can find fully stock ROMs that are rooted as well as links to posts that can show you how to remove the root. Also check the developer's forum for stock roms like this DI18.
bilestoad said:
1st: good move, such a better phone.
2nd: you can almost always return your phone to stock, AS LONG AS a) you can boot into recovery and 2) you have the proper files to flash.
Having said 2(2), you should look here. There you can find fully stock ROMs that are rooted as well as links to posts that can show you how to remove the root. Also check the developer's forum for stock roms like this DI18.
Click to expand...
Click to collapse
Thanks for the help
I saw the Wiki, but what I'm confused about is the ROM version numbers floating around... i.e. DI18, DK17, DJ29, etc. Is there some sort of schema to decode these?
algorhythm said:
...what I'm confused about is the ROM version numbers floating around... i.e. DI18, DK17, DJ29, etc. Is there some sort of schema to decode these?
Click to expand...
Click to collapse
Sure is, not sure what the D stands for but the second letter corresponds to the month in which it was released. "I" meaning the 9th month of the year because it is the 9th letter of the alphabet, and so on. The digits are the day of the month it was released. The titles of the ROM's, however, appear to be linear. First 'E'clair, then 'F'royo, 'G'ingerbread, etc.

Okay, someone explain to me why people can't update to FroYo

If you've debranded, you can't upgrade...? Is that the issue?
I've read through the big thread and it doesn't really explain much to me
From what can be gathered so far:
The non-branded HTC Legend FroYo up date checks the phones CID to a list that HTC know are debranded. If the CID is not on that list of the update script, it fails the update. Vodafone and other carrier phones that have been de-branded still have the original CID. In my case, mines is something like VODAF001. This is not on the installer scripts list. Hence the update fails even if we have a debranded 2.1 ROM.
We cannot change, yet, the orginal HTC Update Script as the *.zip file has a signature that cannot be re-signed without knowing HTC's private key. Think of it as encryption - the files are visable, however, the phone checks the signature against what it should be for the contained files. If the files are changed (like changing the supported CID's) then the signature does not match and the phone fails to continue with the update.
There's no way way to change your phones CID or re-sign the FroYo installation rom to accept the diffierent CID's.
So far, we're stuck.
YoungPretender said:
There's no way way to change your phones CID or re-sign the FroYo installation rom to accept the diffierent CID's.
So far, we're stuck.
Click to expand...
Click to collapse
Very helpful information there m8 and granted there is no free way to change your phones CID but it is very possible do a quick search for riff box you can change the legend CID with that. Not much use to most people due to it costing £100. Maybe some devs would work on a software CID change, not even sure if it is possible with just software but you never know.
Or what about changin the file in the update to accept your CID then using a goldcard to flash it? Does a goldcard not let you flash unsigned zips?
So corrrect me if I am wrong, I have my Bell Legend Rooted with MCR I also have Rom Manager installed, so, If I edited the froyo update to include my cid, then flashed the rom with Rom Manager, that, as I understand things, should work, since we can flash unsigned roms with Clockwork. Or am I way off base?
bwilliams1 said:
So corrrect me if I am wrong, I have my Bell Legend Rooted with MCR I also have Rom Manager installed, so, If I edited the froyo update to include my cid, then flashed the rom with Rom Manager, that, as I understand things, should work, since we can flash unsigned roms with Clockwork. Or am I way off base?
Click to expand...
Click to collapse
Im not sure I dont even have a phone atm waiting on my legend to turn up but it sounds about right to me. That doesnt mean it will actually work tho best off waiting for someone with more experience with these thhings to post.
I bought a Vodafone Spain one, and have debranded it. I use a Cyanogen mod froyo. So i can't update to the official one ? If i put the 2.1 From Vodafone Spain, can't i update to the Vodafone Spain Official 2.2 ?
xnotte said:
I bought a Vodafone Spain one, and have debranded it. I use a Cyanogen mod froyo. So i can't update to the official one ? If i put the 2.1 From Vodafone Spain, can't i update to the Vodafone Spain Official 2.2 ?
Click to expand...
Click to collapse
From what I understand if you put the vodafone rom on you can update to vodafone 2.2 but people are having problems getting the wwe 2.2 on de branded handsets
I've got a single idea that I'm trying the now to get working.
Not going to post any details until I know wether it'll fail or work. Fingers and toes crossed through :O
YoungPretender said:
I've got a single idea that I'm trying the now to get working.
Not going to post any details until I know wether it'll fail or work. Fingers and toes crossed through :O
Click to expand...
Click to collapse
Good luck let us know how you get on.
FeaRThiS said:
Good luck let us know how you get on.
Click to expand...
Click to collapse
Not very well
I'm pretty new to all this anyway, but I thought my techie background would help playing catchup.
Basically, I found my CID of my phone. VODAF001.
Then I went through the official unbranded FroYo rom and replaced supported CID's in the installation script and the android.info text file in the frimware.zip folder with my CID. Resigned the package.
I then rooted my phone (took a few hours - never did it before, but it was a success) then attempted to install the modified and resigned package.
It verifies ok, but I get a Status 7 error. I think this was the same error I had when trying to install the FroYo update from the very start.
Not too happy, but I had to give it a go. Anyone have any other ideas at modifying the original rom file? At least I got the thing to verify after modding it onto a rooted rom. Maybe, just maybe we're 30% there.
YoungPretender said:
Not very well
I'm pretty new to all this anyway, but I thought my techie background would help playing catchup.
Basically, I found my CID of my phone. VODAF001.
Then I went through the official unbranded FroYo rom and replaced supported CID's in the installation script and the android.info text file in the frimware.zip folder with my CID. Resigned the package.
I then rooted my phone (took a few hours - never did it before, but it was a success) then attempted to install the modified and resigned package.
It verifies ok, but I get a Status 7 error. I think this was the same error I had when trying to install the FroYo update from the very start.
Not too happy, but I had to give it a go. Anyone have any other ideas at modifying the original rom file? At least I got the thing to verify after modding it onto a rooted rom. Maybe, just maybe we're 30% there.
Click to expand...
Click to collapse
At least you ruled out one possibility I think the best way would be to change the phones CID that way you would never have to worry about it again and all updates would work as if it was a sim free phone. I remeber a few years back there was a app for the original iphone that would allow you to change the imei (i know this is illegal in most places) the point is the CID needs the same level access. If we have enough access a dev could probably make an app or script to run to change the phones CID to one of a sim free phone. I have posted the question in the dev section no replys yet.
FeaRThiS said:
At least you ruled out one possibility I think the best way would be to change the phones CID that way you would never have to worry about it again and all updates would work as if it was a sim free phone. I remeber a few years back there was a app for the original iphone that would allow you to change the imei (i know this is illegal in most places) the point is the CID needs the same level access. If we have enough access a dev could probably make an app or script to run to change the phones CID to one of a sim free phone. I have posted the question in the dev section no replys yet.
Click to expand...
Click to collapse
Agreed. It would be the best solution.
I'm still looking at this script file. I reckon that re-writing the entire thing could also be a possibility - and probably quicker to a solution to the CID problem in the short term.
Trying again taking all the checks out at the begining of the script... see what happens, lol.
Well, different error. Status 4 - whatever that means...
It could be anything. My ROM version currently installed could be too old for the update as well (V.1.xxxx).
Anyway, it's twenty to two here, time for my bed I think...
YoungPretender said:
Trying again taking all the checks out at the begining of the script... see what happens, lol.
Click to expand...
Click to collapse
good luck im sure there is a way as with clockwork mod you can flash unsigned roms so just a case of trying as many ways as possible. As for the CID change im guessing that would be a lot of work and would take a long time but would prevent future problems with new updates ect ect.
Not sure why people are freaking out about this. So the Voda Phone one came out early.. I'm sure it's just a matter of days or weeks before the WWE is released. Just chill
skinnypupp said:
Not sure why people are freaking out about this. So the Voda Phone one came out early.. I'm sure it's just a matter of days or weeks before the WWE is released. Just chill
Click to expand...
Click to collapse
I think you are missing the point a legend that was locked to vodafone can not be updated to the wwe. the voda legend has a different cid which is stopping people who debranded there phones from getting the wwe 2.2 update.
skinnypupp said:
Not sure why people are freaking out about this. So the Voda Phone one came out early.. I'm sure it's just a matter of days or weeks before the WWE is released. Just chill
Click to expand...
Click to collapse
So you mean the official FroYo update for non-branded phones? it is! We know the Vodafone one is out.
The problem lie in people who have de-branded. They can't update to the non-branded FroYo that was released today.
(And Yes, I'm still up because I'm a persistant little bugger, lol)
YoungPretender said:
So you mean the official FroYo update for non-branded phones? it is! We know the Vodafone one is out.
The problem lie in people who have de-branded. They can't update to the non-branded FroYo that was released today.
(And Yes, I'm still up because I'm a persistant little bugger, lol)
Click to expand...
Click to collapse
haha still tryin post up everythin you try just so people dont have to try things we know dont work.
FeaRThiS said:
From what I understand if you put the vodafone rom on you can update to vodafone 2.2 but people are having problems getting the wwe 2.2 on de branded handsets
Click to expand...
Click to collapse
but if i put the vodafone rom back again, it's no longer debranded! right ?
So i can update to the Vodafone ROM 2.2 via OTA right ?

Categories

Resources