Database Users

Rogers and their mandatory ROM - Let's give them what they ask for ?

So Rogers is blocking internet for those who don't update to their crappy software, they check this most probably by asking our devices what version number they are using.
So why don't we just give them the version number they want? Isn't it easy to just modify a file somewhere and change the version number to match that of their latest rom ?
I'm not rom builder so I really don't know if what I'm suggestion is easy to achieve, but it sounds quite simple.
Can we do this?

That is essentially what cursordroid did in his rom

No cursordroid based his rom on the Rogers rom, what I'm suggesting is you take any 32a rom and change the version info to match that of the Rogers rom.

Naatan said:
So Rogers is blocking internet for those who don't update to their crappy software, they check this most probably by asking our devices what version number they are using.
So why don't we just give them the version number they want? Isn't it easy to just modify a file somewhere and change the version number to match that of their latest rom ?
I'm not rom builder so I really don't know if what I'm suggestion is easy to achieve, but it sounds quite simple.
Can we do this?
Click to expand...
Click to collapse
My suggestion is to just update your device! My Rogers HTC Magic (32A) was rooted prior to the installation of the new update. I ran into one problem while updating but if wasnt anything that was hard to fix. Basically what happens is that your SPL and Radio get wiped completely and then they are updated with the new Rogers HTC Magic SPL and Radio. There is no way for them to know what you are running because the update takes place in fastboot.

completely not necessary to update.
make a call to rogers, tell them you updated, but the 3g won't come back on, they'll tell you to take out the battery as they reset it for you.

cartar said:
completely not necessary to update.
make a call to rogers, tell them you updated, but the 3g won't come back on, they'll tell you to take out the battery as they reset it for you.
Click to expand...
Click to collapse
And your point being what.

FoTwoZero said:
And your point being what.
Click to expand...
Click to collapse
The 3G being enabled again..

Not sure if just getting the reset done will let you keep your data enabled as current belief is that they will continue scanning and blocking for the next while.
If you are already running a ROM with the 911 fix and want to keep it the following "seems" to work... I did this yesterday morning at still have data 24 hours later...
It is based on bcrook's work... I have seen reports that just changing out build.prop wholesale causes issues with the market so this is a smaller set of changes.
adb shell reboot recovery
***Wait for Magic to boot into recovery***
adb shell mount -a
adb shell
cd system
ls
***look for your build file, will be build.prop or build.sapphire.prop most likely***
CTRL-D ***to quit the shell***
adb pull /system/build.prop ***or whatever it was called***
***make a backup copy and edit the file***
adb push build.prop /system/build.prop
adb shell reboot
The actual changes you need to make to the file are:
ro.build.description=3.05.631.7 CL#118917 release-keys
ro.build.changelist=118917
ro.product.ua=
ro.build.fingerprint=rogers/htc_magic/sapphire/sapphire:1.5/CUPCAKE/118917:user/release-keys
ro.build.display.id=DRC92 3.05.631.7
Once you reboot your Magic, you should see the changes in Settings->About Phone under "Build Number".
Call into Rogers and get then to reset your network and you should be good.

http://www.rogers.com/HTCwaiver

FYI: OTA URL capture

I don't know how useful this will be, since many of the devs have probably gleefully pounced on the 2.1 leak (and can't roll back now to Cupcake), but...
The OTA update process (1.16.605.1 -> 1.17.605.1) is completely different than the RUU/HBOOT methods... it actually boots into android and performs file-by-file binary patching on all sorts of stuff as well as installing new files and other miscellany - controlled by an "update-script" (not a shell script, but quite readable).
The OTA .zip files which are downloaded from a Google server are not signed the same way as the RUU "rom.zip" files - they use the app .apk manifest signing method. (manifests and certs a la "jarsigner").
If you are interested in looking at the process that HTC/Verizon uses for the OTA updates, you can get the URL for the OTA zip the following way:
Run logcat on the pc and accept the update on the phone
$ adb logcat > logcat_accept.txt
This will sit like this (it continues to log output into the output file) until the phone reboots. At that point, the adb logcat job will terminate, and the name of the zip file will be indicated in the logfile in a message similar to:
W/SystemUpdateHelper( 64): !!! REBOOTING TO INSTALL /cache/desirec-ota-104882.7b1e5cca.zip !!!
Then, take the name of the file and paste it on the end of android.clients.google.com/updates/partner, for instance, for the Eris 1.17.605.1 OTA, the complete url is:
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
Note: because the 2.1 release is so vastly different than the 1.5 release, an OTA (if that's the way VZW/HTC rolls it out) for that will probably be very different than a patch release like this example ... but it would still be very useful for anyone who gets notice of an update to capture the URL using the "logcat" method shown above. There might be "interesting" tools included that could be exploited.
I don't think this will help get an "early OTA" - I'm not sure that hboot/fastboot methods can make use of an "update.zip" with an unrooted phone. Someone can correct me if I am wrong about that.
bftb0

Can someone tell me if this has been captured? I just received a replacement device with 1.5 and am prompted to install the OTA. I am about to root and can capture if needed.
Please let me know as soon as you can. I will probably "play" with 1.5 root for a little bit.

pharaohmd said:
Can someone tell me if this has been captured? I just received a replacement device with 1.5 and am prompted to install the OTA. I am about to root and can capture if needed.
Please let me know as soon as you can. I will probably "play" with 1.5 root for a little bit.
Click to expand...
Click to collapse
I'm not sure where the posted link is, but we've had the 2.1 OTA download link for a while.

nindoja said:
I'm not sure where the posted link is, but we've had the 2.1 OTA download link for a while.
Click to expand...
Click to collapse
Thanks...thought so but wanted to check...I tried to search but there have been so many */*/*/etc posts it's a bit confusing.
(edited out the example search terms so as NOT to contribute to the mess with this post...)

can sombody do this with the Update that just started pushing tonight?

iornslave said:
can sombody do this with the Update that just started pushing tonight?
Click to expand...
Click to collapse
Since so many of the XDA members are rooted, we're going to have to count on one of the "leakers" to capture it. We've confirmed (on android forums dot com) that it's coming to those on leak v3, which makes sense since that's up-to-date with the RUU and OTA.

No one has captured this yet ? Hoping that whatever "fix" or "fixes" are in this update can be applied to our rooted phones.

hallstevenson said:
No one has captured this yet ? Hoping that whatever "fix" or "fixes" are in this update can be applied to our rooted phones.
Click to expand...
Click to collapse
I'm sort of wondering if VZW had some customer problems with it and pulled the plug on it. In the past, there have been claims that VZW starts the rollout in very small groups - several hundred at a time - and then ramp it up if they don't see complaints coming in from their customer support channels.
Sure does seem like there's very little chatter about it.
I've got my phone running OTA-2.1 to try and intercept it, and I also hacked a custom recovery that doesn't automatically erase files in /cache (basically, a recovery boot that doesn't run /sbin/recovery at all). That way I can just pull it out of /cache as soon as it is downloaded via OTA.
Nevertheless - to anybody reading this - please post up the URL to the zip file download if you capture it.
bftb0
[Edit] For references, PRIOR OTA URLs were
1.17.605.1 (aka "MR2") OTA: https://android.clients.google.com/packages/desirec/desirec-ota-104882.7b1e5cca.zip ( md5sum: f6bd240c726874e3922767979ecc6b32 )
2.36.605.1 (aka "OTA-2.1") OTA: https://android.clients.google.com/packages/desirec/OTA_Desire_C_Verizon_WWE_2.36.605.1_1.17.605.1_release_0420.79112f65.zip ( md5sum: 9a3a82e4b5afb4e885b41d28085b9adc )
Note: both these links verified working w/ correct checksums as of 2010-07-01.

hallstevenson said:
No one has captured this yet ? Hoping that whatever "fix" or "fixes" are in this update can be applied to our rooted phones.
Click to expand...
Click to collapse
I agree I have been hoping someone would have posted it considering that several have claimed to have received it. Oh well, hopefully soon.

Maybe all the people who are "smart" enough to do this are already rooted?

Stonent said:
Maybe all the people who are "smart" enough to do this are already rooted?
Click to expand...
Click to collapse
Nothing about root prevents you from running a copy of OTA2.1 for a couple of days in order to capture the URL; that's what Nandroid backups are good for. S'pose you could run Plain Jane or Ivanmmj's Official and add back in the updater apps & certs if you really needed root in the meantime.
OTOH, it's been mighty quiet the past few days; I'm starting to wonder if there was a problem with the new OTA, and VZW pulled the plug on it.
bftb0

How to install

I downloaded [OFFICIAL ROM UPDATE] Gingerbread 2.3.3 Update for HTC EVO Shift 4G from here http://forum.xda-developers.com/showthread.php?t=1127499
and I cant figure out how to install it. I put the file in the root file of my sd card then went into bootloader and nothing.

I'm going to ask this, but I'm pretty sure I already know the answer: are you rooted?
If not, and you don't care about root at this time, just go to HTC Software Updates, under Menu, settings, system updates, htc software update, and click check now.
Otherwise, two things disturb me about the link. The size of the file only shows 9.5 mb in the parenthesis next to the file name. It's actually 248 mb. Also, it's not in the correct name format, to just update from the bootloader. It needs to be PG06IMG.zip. But you can't just rename the file in the link above to PG06IMG.zip. It just won't work.
Or just go to shipped roms (shipped-roms.com) and download the latest ruu, and then connect the phone to your computer, and run the exe.

I tried the htc updates in setting and it said there were no updates for my phone. I gave up I found an ruu file and did it like you said and it worked great thanks. I was rooted but i only did it for wireless teather and i never used it so unrooting was not a problem.

By the way i used this ruu http://forum.xda-developers.com/showthread.php?t=1128410 to update and it work great

[Q] Can't update to Mango

Hi,
Here is my problem, i have HD2 device:
Error:
Update device 7079645b - b554a543 - 6dfa84f0 - d945b9cb Complete with error code: 80180089, error message: Disaster recovery plugin error: Couldn't create a backup because your phone's registry settings are incorrect.
Failed with code: 80180089
Thanks

Your problem is, that you cant read or think
You have a hd2, thats not an official windows phone 7 device.
you can either search for the dft-build of mango (very early version) or wait for someone to build a full functional rom for our hd2.

mideel said:
Your problem is, that you cant read or think
You have a hd2, thats not an official windows phone 7 device.
you can either search for the dft-build of mango (very early version) or wait for someone to build a full functional rom for our hd2.
Click to expand...
Click to collapse
short an too the point, love it!

Sometimes it really surprises me how some people even manage to turn their devices on never mind flash WP7 to their device.
@ OP
Ofoucrse you cant update, You dont have a WP7 device so how on earth do you expect to get teh correct files you need via update?????
What you have is a modified version of a rom designed to boot on your device you need to manually add a new rom to your device. How do you think you are going to get teh correct files vis official update, magic fairy dust???

HTC Hero GSM - Cyanogen 7.2

Cyanogen has released the 7.2 version OS for HTC Hero GSM. I've seen a lot of people talk over the CDMA version, but none on the GSM one. Has anyone tried it out? I wanna hear the bad and good remarks that you have to say about it , by "you" I mean those who have tried it.
To be sure, this is the tipe of HTC Hero I'm referring to: spinei.hotnews.ro/wp-uploads/2009/10/htc_hero.jpg

I runned it for a week or two. As for stability it's the same as CM7, CM7.2 just has some ICS backports, nothing bad

What do you mean by ruining it?
People who own the CDMA version claim that on their phone it's a performance improvement from 7.0 to 7.2.
I have 2.1 official version on it. It's stable and somewhat ok in terms of flow in the menus. Will 7.2 be an improvement over the the official 2.1 version on my phone?
P.S. I didn't test any other version of Android, it never used anything except the stock version.

cata3092 said:
What do you mean by ruining it?
People who own the CDMA version claim that on their phone it's a performance improvement from 7.0 to 7.2.
I have 2.1 official version on it. It's stable and somewhat ok in terms of flow in the menus. Will 7.2 be an improvement over the the official 2.1 version on my phone?
P.S. I didn't test any other version of Android, it never used anything except the stock version.
Click to expand...
Click to collapse
It;'s not ruined, I had it on my device for a week or two. I thing it will beat your 2.1 official. It will not have HTC Sense. You get 2.3 version of android some ICS goodies. I didnt run official 2.1 on hero so i dont know how it is

What does HTC Sense has and cyanogen 7.2 doesn't have as equivallent?
From what I saw in youtube videos, cyanogen pretty much has something almost equal to HTC Sense as GUI. Are you referring to the HTC specific apps and widgets?
P.S. I misread "runned" for "ruined" )

Yup that fancy weather widget and all that stuff, but you wont miss it trust me, that raw android look is way better

One more question.
How functional are these:
- WIFI
- Bluetooth
- Camera
- basic phone functions(calling, messages)
- sound
? Did you have any problems with these in terms of errors or functionality(loss or low of signal, automuted, etc.)? And did you had any random restarts issues?

Nope they all work awsome, it's a stable release, those releases dont have problems with that. And you shouldnt be too scared to flash your device. So far I had 4-5 android devices that are rooted and flashed a million times without any losses, you may encounter a soft brick sometimes but you can fix that easily. You cant know how good is a ROM until you test it. So stop being a girl and flash it . No offence If you dont like it, there is a lot more ROM's on this forum, you dont have to choose CM7.2....

First time to install Cyanogenmod was not entirely easy
Hey all,
I just created an account to be able to post my experience with CGM 7.2 on the HTC Hero GSM. Everything I checked so far works fine, however there's a slight jaggedness in scrolling.
For me as a complete newbie it took about 6 hours to get it to run, mainly because I had to get straight what I actually have to do. There is no paucity of TO-DOs, just no individual one worked for me - I got it sorted out only by combining all kinds of posts from everywhere. That's why I want to share my viewpoint on this - without all kinds of different people airing their piece of the puzzle I would surely have given up!
The specs were as follows; starting with the "fastboot-info":
HERO CVT SHIP S-ON
HBOOT-1.76.0007 (HERO10000)
MICROP-010f
TOUCH PANEL-SYN0104
RADIO-6.35.15.11
Aug 4 2009,19:43:30
And software-information:
Firmware-Version 2.1-update1
Baseband-Version 63.18.55.06PU_6.35.15.11
Kernel-Version 2.6.29-7527f009 [email protected] #1
Build-Nummer 3.36.405.1 CL199109 release-keys
Software-Nummer 3.36.405.1
Browser-Version WebKit 3.1
So here's what I did:
0) I wrongly assumed that I need to unlock my bootloader directly, i.e. using the software from HTCDev. As I am using Ubuntu Linux, this meant quite a hassle in itself, and I did not manage it after all. The reason was due to an error when trying to get the Identifier Token needed by HTC to send you some clearance-file to unlock the bootloader:
Code:
fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
I found no solution to this problem, but tried to up- or downgrade my HBOOT-version. Luckily that wasn't necessary after all. A side-effect of it was that I installed adb and fastboot, which I happened to use later on (but are not necessary either).
Let me assure you: Unlocking the bootloader directly (in the HTC-way) is NOT necessary!
1) Getting root access:
I used UniversalAndroot-1.6.2-beta5.apk to do that, and conveniently installed it using
Code:
adb push, adb install
though if you don't want to install this nice utility, you can just install a File Browser and then install the package.
Now here's a quirk that cost me about an hour: Using the default settings, UniversalAndroot only claimed to successfully get root-access, but left everything unchanged! Only after finding a comment on some website did I try to check both check-boxes (log and temporary install) - this time it worked (it installs yet another app called SuperUser)! (I then ran it again without the temporary setting enabled, which at least did not revoke the SuperUser-Account). Anyways, adb is handy in this case again because you can just log in with
Code:
adb shell
and check if
Code:
su
gives you root access or says "Permission denied".
2) Deleting /system/etc/install-recovery.sh I got that idea from androidforums.com, and will probably never know whether it was really necessary. That just shows how desperate I became after 3 hours of poking around in the dark.
3) Installing ROM Manager from Google Market There's probably a quicker way to install recovery images, which does not involve a damn Google account! Or maybe it is not even neccesary.
4) Downloading and installing ClockWorkMod Recovery I did this using the ROM Manager. Again, there might be a more direct way. In any case, I was paranoid enough to install it twice, as it was recommended that way somewhere.
5) Downloading cm-7.2.0-hero.zip and putting it on /sdcard/ Again, I just used
Code:
adb push cm-7.2.0-hero.zip /sdcard/
to accomplish this, but my guess is you can just as well do it via USB.
6) Format cache, /data/factory, /boot and /system By that, I mean do this in ClockWorkMod (you get there by booting up with HOME+POWER). The last two locations to reformat are "hidden" in the menu partitions. This step is very important because without it, Cyanogenmod did only loop infinitely (for more than 10min) in its loading screen! I got this idea from the more detailed description at droidforums.
7) Install Cyanogenmod using ClockWorkMod That's straight forward; just select the image from sdcard and you're done!
Hope I didn't forget a vital step, and maybe it is helpful to somebody; at the very least my future ME will maybe find it useful again .