Related
So I've caved in to temptation and rooted my Magic. Now I'm looking for a suitable ROM - I've been into the Sapphire wiki and looked at the ones listed in there but they don't really explain what is on the ROMs.
What I am looking for is a ROM that contains Exchange sync, multitouch and browser with Flash, and most importantly - stability!
Also a few more questions - can I use the Android market if I have a custom ROM? I ask because in the ROM discussions I've noticed a lot talking about adding and removing software using the adb tool. Are there any other pitfalls I should be aware of, seeing as this my first time applying a new ROM.
TIA
Firstly what version of the magic do you have, 32A or 32B.
It's best to check out the rom development section and read what each rom is about there.
And yes you can still use the android market, the icon is still in all the custom roms.
Mine is the 32B - UK Vodefone.
The problem is the threads for those ROMs are sometimes more than 100 pages long with little or no descriptions about what is contained on them ... unless I am missing something
Well the ROMs will always be updated on the very first page, there's usually some kind of description as well of what is and whats not included.
As with all these things it's best to try each one out for yourself and see what you do and don't like.
As long as you use nandroid to backup your phone then you can always go back to the rom you were using before you falashed a new one.
I've tried installing Fatal1ty's 32B ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=531617
(Fatal1ty-Hero-Full-v1-4-zip)
Rename it in update.zip
copy to sd
reboot (pressing home+power)
wipe
apply update
Click to expand...
Click to collapse
It said the update.zip was bad ...? Thank god for the nandroid backup (cheers for the advice on that one), I was restored and working again straight away on my old config ... but what went wrong? From doing a bit more reading, is it because the ROM isn't signed? Or should I just download the file again and try again - perhaps it corrupted somewhere along the way?
Can you provide the exact error you got?
st0kes said:
I've tried installing Fatal1ty's 32B ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=531617
(Fatal1ty-Hero-Full-v1-4-zip)
It said the update.zip was bad ...? Thank god for the nandroid backup (cheers for the advice on that one), I was restored and working again straight away on my old config ... but what went wrong? From doing a bit more reading, is it because the ROM isn't signed? Or should I just download the file again and try again - perhaps it corrupted somewhere along the way?
Click to expand...
Click to collapse
I've been caught out with something like this before - make sure the zip you are downloading is the actuall update zip! Open it and check it only has the 3 folders and boot.img in it.
The update.zip maybe in the zip you have downloaded
But on a side note - the Hero Roms aren't suitable (yet) for the 32B's as the RAM is too small - wait until they cut it down a bit.
I would recommened either Nk2 or CyanogenMod [v3.6.8] && Palm Pre theme [1.5] ported
The second being the fastest i've used (rapid infact)
Cheers - I tried downloading the rom again and this time used adb push to copy and rename it to the sd card, tried again and it worked.
I agree with what you're saying about the hero rom needing some work though. I can't use touchflo or the weather app as they are too slow. Browser is also quite a lot slower than on the stock Voda UK firmware.
I really like HTC Peep and the facebook integration into my contacts, and the HTC keyboard is a lot better.
On your advice I'll give the CyanogenMod rom a try. I would like to find one good one and stick to it rather than become addicted to flashing the latest roms every week!
I am trying to update from cupcake (1.5, CRC1) to donut (1.6, DCR83) using the zip from http://code.google.com/p/android-roms/wiki/Donut.
Installation fails - please see below
xxxxxxxxxxxxxxxxxx
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Error in applypatch (Status 256)
E:Failure at line 28: run_program PACKAGE:applypatch -c /system/app/DownloadProvider.o dex fc.....<a lot of letters>......dee
Installation aborted.
xxxxxxxxxxxxxxxxxx
What is wrong with this update.zip? Or something other is corrupted?
Thanks in advance.
radio and spl versions ?
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Just checking..
You are trying to upgrade from a US T-Mobile stock cupcake build??
If you go into your phone settings -> About Phone -> what does it say under Build Number??
>>> You are trying to upgrade from a US T-Mobile stock cupcake build??
yes
>>> If you go into your phone settings -> About Phone -> what does it say under Build Number??
it says Build Number = CRC1
You could try and verify the integrity of the file you downloaded, using the checksum
SHA1 Checksum: c41b93c1067d733f04a7b1014b97cab4d7cf460a
If you're not familiar with this you could find a free Program to verify @
http://download.cnet.com/MD5-amp-SHA-1-Checksum-Utility/3000-2092_4-10911445.html (using windows)
OR
Code:
sha1sum signed-kila-DRC83-from-CRC1.c41b93c1.zip | grep "c41b93c1067d733f04a7b1014b97cab4d7cf460a"
(using linux)
jackslim said:
Just checking..
You are trying to upgrade from a US T-Mobile stock cupcake build??
If you go into your phone settings -> About Phone -> what does it say under Build Number??
Click to expand...
Click to collapse
But slim the phone will auto update to a newer version by tmobile since he's not rooted.
Ace42 said:
But slim the phone will auto update to a newer version by tmobile since he's not rooted.
Click to expand...
Click to collapse
This is true, however most ppl lack the patience to wait for the actual OTA
jackslim said:
This is true, however most ppl lack the patience to wait for the actual OTA
Click to expand...
Click to collapse
I tried auto updates (Settings->System Updates) before: it says "Your system is currently up to date"
That is why I am trying to do a manual update.
NeDen said:
I tried auto updates (Settings->System Updates) before: it says "Your system is currently up to date"
That is why I am trying to do a manual update.
Click to expand...
Click to collapse
You might consider root and get enom's base rom or cyanogen...Your on 1.5 which has root exploit(one-click)....That is up to you though, if your good with hacking and know a good deal about following directions the trip might be worth it.However if common-sense isn't one with you then you would mostly messup even on the simplest parts.
@OP there was a prob with 1.6 that had some sort of wifi bug or Bt bug. And 1.6 is extremely laggy...Seems like the muppets couldn't get the job done correctly.
But if the rumors or whatever of 2.0 for G1 you should wait a bit longer...I feel that users are obligated to root/mod their phones if they are here being that is the point ot XDA...Make your hTC device better and smoother,faster.
Thanks for your answers.
But I will have to flash my G1 (IMHO) because:
1) I have this issue: http://forum.xda-developers.com/showpost.php?p=5230455&postcount=9
2) From time to time my g1 goes to some strange state: jumping from "ANDROID" screen to desktop screen. During this period it is disconnected from network as well. In desktop state it is very very slow. I can fix it only via wipe.
P.S. I have one more G1 (actually my girlfriend) - it is 1.6, and it woks perfect in comparison with mine.
I know this thread is old, but I ran into this same problem when unrooting my G1 and I wanted to share my solution in case any body else runs into this problem and stumbles on this post.
When you start from scratch (dreaimg.nbh) and you upgrade to cupcake, there is patch to cupcake that you must apply first before you can move on to donut. I was trying to go to donut from a stock cupcake image on the G1 and was receiving a similar error as OP. Doing the CRB43 FIX image flash allowed me to then flash donut. The proper flash order is
DREAIMG.NBH <<< Android 1.0
signed-kila-ota-148830.de6a94ca.zip (CRB43) <<< Cupcake1.5
signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip (CRC1) <<< Cupcake 1.5 patch (This is what I flashed so that I could move on to donut)
signed-kila-DRC83-from-CRC1.c41b93c1.zip (DRC83) <<< Donut 1.6
You can find detailed instructions and download links for all files mentioned on Cyanogen's wiki (can't post link since I'm still a new user). Please PM me if you have questions.
Hi devs,
Strictly speaking, this is not a development issue, but I thought it warranted some special attention as it sheds a little bit of new light on the "bricking" caused by Clockwork (version unknown).
A new XDA member, SoSickWiTiT, brought back an Eris from the grave. The phone he started with could only be put into RUU mode - initially it would not even start correctly in Hboot or Fastboot mode (weird, right?), and is now fully functional. The long and tortuous thread is here in the Q&A forum.
The essential finding was that the "bricking" was apparently caused by enormous numbers of pages in the flash memory device being marked as bad pages, and that this was correctable by using the "flash_erase" tool of the mtd-util project. (This tool allows you to reclaim flash pages marked as bad if they erase successfully.) I built some of the tools for ARM/Android and posted them up here.. As long as you can get Amon_RA to come up, you can run this tool from Amon_RA (using adb) and erase/reclaim partitions on a partition-by-partition basis.
Also SoSickWiTiT found a useful hack that I hadn't seen before: because he could only get his phone to start in RUU mode, he started the "Official RUU", ran it to the point where it unpacks all files, and then replaced the "rom.zip" file (in the Temp folder the RUU utility unpacks) with the HTC Root-ROM (renaming it to "rom.zip", of course). Because it signed by HTC, it got the 1.49.2000 S-OFF bootloader installed (but the rest of the install failed). SoSickWiTiT was then able to flash Amon_RA via fastboot and continue gaining traction from there. Note that just flashing a ROM from this point would not work - his mtd3 (system) partition appeared as if over 60% of the pages were marked as bad, and I think his boot partition was similarly affected. "flash_erase" was able to reclaim these pages using the "-N" command line option.
Anyway, the behavior of his phone (excluding the RUU-only behavior) was consistent with prior bricking reports of how filesystems appear to be "corrupted", and this causes difficulties flashing new ROMs (largely due to lack of free space). SoSickWiTiT reports that the phone he obtained from a friend had been bricked by "a failed ROM flash in Clockwork/ROM Manager followed up with an attempt to use the RUU" - there have been at least one other report of this exact same scenario causing the "bricking".
So now I am wondering - are there a few "bricks" laying around that might be rescued?
bftb0
Very interesting and good to know, thanks! And thank you for the tool, great work.
Think this could be applied to deleting the NRAM flash on a router? =p
WAIT wait wait!!!
He changed the bootloader from S-On to S-off??? Was it on 1.49? If so couldnt that have been used to root our phones, A LONGGG time ago? lol
Nikolai2.1 said:
WAIT wait wait!!!
He changed the bootloader from S-On to S-off??? Was it on 1.49? If so couldnt that have been used to root our phones, A LONGGG time ago? lol
Click to expand...
Click to collapse
A looooooong time ago - December '09 (circa "MR1") iirc, someone attempted to stuff a different - and unsigned - "rom.zip" file into the running (MR1) RUU.
Naturally, that didn't work, 'cuz it wasn't a HTC-signed PB00IMG.zip file. To my knowledge, this is the first time anybody tried doing things this way (swapping in the validly-signed HTC Root-ROM into the RUU's "rom.zip" location)... maybe it would have worked for the "leakers". I suppose that someone could roll back their phone and give it a shot to see it if works, but that seems sort of academic at this point - hence your "LOL".
There is evidence that both the RUU- and Hboot- based update processes actually end up checking the contents of the "misc" partition for version information TWICE - first before any flashing occurs, and second, only after the bootloader has been flashed and reloaded, but before the remainder of the PB00IMG.zip/rom.zip file has been flashed. I don't think that even at this point in time this behavior is well understood: it is possible that the hboot flash of the bootloader can occur, but then the subsequent flashing of the rest of the PB00IMG.zip file fails due to a "Main Version is Older" error. Sort of hard to understand why that would ever occur (it happened to me once, so I know it occurs).
For anybody that has a brick, but can get RUU mode running, it is certainly worth a try to see if they can replace the bootloader with the S-OFF bootloader - what do they have to lose? In this particular case, it is hard to know what the state of the misc partition was; after all, it was a phone that was previously rooted. The result obtained using the RUU utility likely depends on what was going on in the misc partition on that phone, so it is not obvious that this (RUU utility) "trick" is universal. It might have been that the same phone would have been happy to accept the Root PB00IMG.zip file - but SickWiTiT couldn't get the phone into Hboot mode initially, so that wasn't tried.
cheers
bftb0
So if I have been using Clockwork to flash a few roms do you think I would have any bad pages in my flash memory? Is there an easy way to check this?
xtreme3737 said:
So if I have been using Clockwork to flash a few roms do you think I would have any bad pages in my flash memory? Is there an easy way to check this?
Click to expand...
Click to collapse
I don't think that using Clockwork causes slow growth in bad pages; afaik, when the problem occurs - whatever causes it - only then do you see a catastrophic number of pages marked this way. I mentioned it only in case someone bricks their phone and then asks for advice here - they can check to see if this repair works for them at that time - after they have determined that this is the nature of their problem. In the meantime, there is not much need to worry about it.
Short of actually performing a flash_erase with the "-N" option turned on, I don't know off the top of my head a way to determine the number of bad blocks easily, and there are good reasons why you should not be doing that unless you absolutely have to.
The tool "nanddump" that I compiled actually reports the number of bad blocks - but it also wedges the Amon_RA kernel when you run it. Rats.
bftb0
I just wanted to add my thanks for this very informative and interesting information and tool in case it becomes necessary. I do use Clockwork (loaded from Amon RA), BTW.
Thanks for the useful info as always.
It really seems like a bad idea to use clockwork
Sent from my nonsensikal froyo
SikYou said:
Thanks for the useful info as always.
It really seems like a bad idea to use clockwork
Sent from my nonsensikal froyo
Click to expand...
Click to collapse
bftb0 said:
I don't think that using Clockwork causes slow growth in bad pages; afaik, when the problem occurs - whatever causes it...
Click to expand...
Click to collapse
I haven't once had an issue with Clockwork Mod through ROM Manager, and have been using it for 3+ months now.
thanks for this thread i sort of helped one person put their phone into the grave by telling them to flash an ruu (still feel bad about it)
jamezelle said:
thanks for this thread i sort of helped one person put their phone into the grave by telling them to flash an ruu (still feel bad about it)
Click to expand...
Click to collapse
That cus you are a baddie jamezelle xD
Very informative read, thanks bftb0!
I spent some time tonight fooling around with RomManager (v3.0.0.7) and ClockworkMod (v2.5.0.1 for the Eris). Sort of an eye-opener, actually.
The way it works is that it is actually NEVER "FLASHES" ANYTHING TO THE RECOVERY PARTITION. Instead, when you first tap on the menu item to "flash the recovery", what ROM Manager does is identify your handset type, and then downloads some files to
/sdcard/clockworkmod, e.g.:
/sdcard/clockworkmod:
----rwxr-x 1 system sdcard_r 829658 Jan 17 02:23 recovery-update.zip
/sdcard/clockworkmod/download/koush.tandtgaming.com/recoveries:
----rwxr-x 1 system sdcard_r 829658 Jan 17 00:56 recovery-clockwork-2.5.0.1-desirec.zip
/sdcard/clockworkmod/download/rommanager.appspot.com:
d---rwxr-x 2 system sdcard_r 4096 Jan 17 02:23 manifests
/sdcard/clockworkmod/download/rommanager.appspot.com/manifests:
----rwxr-x 1 system sdcard_r 11492 Jan 17 02:23 devices.js
Note that "recovery-update.zip" and "recovery-clockwork-2.5.0.1-desirec.zip" are the same size - less than 1 MB. In fact, they are identical. It is a signed update package - but too small to even contain an Android kernel.
Here's how ROM Manager works: when you press the button "Reboot into Recovery", what actually takes place is this:
- Rom Manager copies "recovery-update.zip" into /cache/update.zip, and then places the following command into /cache/recovery/command
Code:
"/sbin/recovery" "--update_package=CACHE:update.zip"
and then executes a "reboot recovery" command.
The next thing that happens is that whatever Custom Recovery that IS ALREADY FLASHED to your recovery partition on the phone boots up, and immediately begins to process the /cache/update.zip file
Here's the $64,000 observation:
This update.zip modifies NOTHING IN FLASH MEMORY - IT ONLY MODIFIES THE RAMDISK OF THE BOOTED RECOVERY ALREADY PRESENT.
Towards the end of the updater-script, it kills off the old /sbin/recovery and /sbin/adbd processes; but since these processes are defined as services, they get restarted automatically, using the new "ClockworkMod" version of these program files. Voila! The ClockworkMod recovery menus pop up.
There are two important observations that arise from this analysis:
- It does not have it's own kernel - it uses the kernel of whatever was already present in the recovery partition boot
- To get ClockworkMod to be cold-bootable, you need to COMBINE IT WITH A KERNEL AND BOOTSCRIPTS FROM SOMEPLACE ELSE - but WHERE exactly?
Now, I don't know if ROM Manager formerly worked in a different fashion - but the point is fairly obvious: if you wanted to provide a rooting method which installs "ClockworkMod" as a recovery - well then, you would need to combine the minimal components of "ClockworkMod" (mostly just the /sbin/recovery program !) with someone else's bootable recovery. And you could not use an HTC stock recovery - because then koush's "update.zip" files would have needed to be signed by HTC in order to get processed.
If you accept the hypothesis that the so-called "Clockwork" brickings have been due to a bug in the kernel MTD driver - and nobody ever seems to see those bugs happening with Amon_RA v1.6.2 - then the real problem comes from a kernel which is was kanged into a flashable "Clockwork Mod" recovery by a third party - not koush.
Who is it then - the unrevoked team? Someone else? What kernel is it?
As I recall, nearly every one of the brickings that have been reported here have been folks that got their rooting instructions from outside the XDA Eris community.
Bottom line - it's starting to look like the problem is not really due to Clockwork - its a problem kernel from unknown origins.
Perhaps Rom Manager did not always work this way on the Eris - but the way it works now is that if you install it after already having Amon_RA in the recovery partition, if you cold-boot (Vol-up+End or via HBOOT), what will come up is Amon_RA, not Clockwork.
So - if you can cold-start your phone into recovery, and up pops a ClockworkMod menu instead of a Amon_RA menu - how did you root your phone originally?
bftb0
(sorry if this post is a bit of a ramble - it's pretty late/early)
When I 'cold boot' I get the Clockwork V2.5.0.1 screen.
I rooted originally the day root was discovered here at XDA. I originally loaded Amon. Somewhere in the last year, I may have clicked the 'install Clockwork mod' at the top of ROM Manager, but I don't think I did.
I don't know if this helps, but I found your post interesting.
meanm50 said:
When I 'cold boot' I get the Clockwork V2.5.0.1 screen.
I rooted originally the day root was discovered here at XDA. I originally loaded Amon. Somewhere in the last year, I may have clicked the 'install Clockwork mod' at the top of ROM Manager, but I don't think I did.
I don't know if this helps, but I found your post interesting.
Click to expand...
Click to collapse
Huh.
If you do that, and then fire up an adb session, what kernel string does
Code:
adb shell uname -a
report?
When I click "Flash ClockworkMod Recovery", all it does is ask me to verify the phone model ("Droid Eris (CDMA)"), requests root (SuperUser), goes to the Internet and downloads stuff, and then pops up a message on the screen saying "Successfully downloaded Clockworkmod Recovery!" If I shut down the phone normally and then cold-boot the recovery afterward, what is there is Amon_RA - not clockwork.
Hmmm. Just used it to perform a ROM backup**. For this operation, the same thing happens - Amon_RA comes up first, followed by chaining to ClockworkMod and then the backup starts happening. I note that it also backs up the recovery partition - maybe it only modifies the recovery partition when it is installing a new ROM?
Hmmm (part 2). Just wiped and flashed a clean ROM using Clockwork. Cold start into recovery afterward gives me Amon_RA, not Clockwork.
Maybe koush has changed the basic methodology somehow. I have to say, the way I currently am experiencing it makes a great deal of sense - it means that koush does not need to be in the kernel-making/kernel-collecting business in order to support ROM Manager on a new handset.
Can anyone with a more long-term exposure to Rom Manager/ClockworkMod (on the Eris) shed some light on this?
bftb0
** Interesting side note: CWM backup now backs up (and I presume restores) /sdcard/.android_secure; also, a "wipe" operation will attempt to wipe any SD card ext partition if it is found.
I will adb when I get home...my work comp doesn't have the required programs installed...
bftb0 said:
** Interesting side note: CWM backup now backs up (and I presume restores) /sdcard/.android_secure; also, a "wipe" operation will attempt to wipe any SD card ext partition if it is found.
Click to expand...
Click to collapse
Also the /cache partition.
bftb0 said:
Huh.
If you do that, and then fire up an adb session, what kernel string does
Code:
adb shell uname -a
report?
Click to expand...
Click to collapse
Linux localhost 2.6.29-DecaFuctCFS-dirty-c6271491
meanm50 said:
Linux localhost 2.6.29-DecaFuctCFS-dirty-c6271491
Click to expand...
Click to collapse
Sorry - I meant adb with your recovery booted, not the normal OS. (The above must be from your regular OS right?)
Hi @all,
as my thread was closed but i still want to thank you and share my experiences, i'll create this new thread.
It belongs to http://forum.xda-developers.com/showthread.php?t=926835 but maybe also can help other guys to get root on theire updated unrooted phones.
this weekend i did the work and finaly i can say:
on my phone I AM root!!!
Just to thank you and maybe help some less experienced people here, i will give you a small overview and some hints for changes to be done for the tutorials to work with the desire z.
so thanks for your help, it worked like a charm.
For the backup i used myBackup as it doesnt require root for backing up and it restored my data as i wished. So myBackup is the product i can recomment. It is available as 30days-demo and so is enough for the process of down- and reupgrading.
Another thing to remind in the following steps is: at any time usb-debugging works with the htc-sync-mode, too. so use this mode, as usb-mode at any time, as in another case (harddisk-mode) the phone cant access the sdcard anymore.
After the backup i removed the card from the phone and worked on with a blank one.
The following both tutorials i used:
Goldcard: http://forum.xda-developers.com/showthread.php?t=572683&highlight=gold+card
Down-Reupgrade: http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting
You may also use this thread:
http://forum.xda-developers.com/showthread.php?t=832503
This one describes all the goldcard und down/upgrade-stuff explicitly for the desire z, but it looks a bit more hacky and seems to be good for people already experienced with hex-editors and rooting, also it doesnt mention, that the first 2 chars of the cardcode neet to be converted to "00", thats why i recommended the other tutorials.
I formated it to fat32 and put it into the phone, this step wasnt mentioned in the tutorial, so i tell it to all who dont know.
Then i read the card-ID with adb. Here is another problem with the tutorial. The DesireZ had no mmc1 with valid data, for the desire z you have to read the cid from mmc2!!! (just change the path from the tutorial) (so: adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid)
After that remove the card from the phone and reinster into the cardreader and do the patching with the image and the hexeditor.
Then youre done with the first tutorial (in step 18) and can move on with the cyanogen one (as it seems more trustful )
So now reinsert into the phone and copy the firmwareimage and then "update" to the older version (was very nervouse while that, but succeeded finaly )
If you get an Error in "/data/local/tmp/misc_version -s 1.33.405.5" (i got one like "unable to backup") you have not inserted the sdcard or used the filetransfermode, so the card is not mounted into the phones filesystem.
If so, switch to htc-sync-mode and try the command again.
When in the firmwareupgrade-mode after the reboot, you can navigate with vol-up and vol-down and enter with the powerkey.
After permroot install the rom of your chioce, best one with allready permroot done, that saves work
i decided for the virtuous as it has sense, any other/better rom someone can recomment???
When done that, too, at first reinsert the original sdcard with your backup on and restore that backup, as it overwrites existing data, it would be best to avoid any sms or calls to arrive before you restored the data, as those calls and messages will be lost.
After that you can set up all things you want and finaly you are done with a new 1.72 rooted and unbranded phone.
Thanks all for your help especially to guhl for giving me those links and taking the fear from me of bricking my phone....
Yours TK
tk-germany said:
The following both tutorials i used:
Goldcard: http://forum.xda-developers.com/showthread.php?t=572683&highlight=gold+card
Down-Reupgrade: http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting
I formated it to fat32 and put it into the phone, this step wasnt mentioned in the tutorial, so i tell it to all who dont know.
Then i read the card-ID with adb. Here is another problem with the tutorial. The DesireZ had no mmc1 with valid data, for the desire z you have to read the cid from mmc2!!! (just change the path from the tutorial) (so: adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid)
Click to expand...
Click to collapse
There's a Vision-specific Gold card guide at http://forum.xda-developers.com/showthread.php?t=832503&highlight=debrand , which does uses mmc2, you might want to link that one up instead ?
steviewevie said:
There's a Vision-specific Gold card guide at http://forum.xda-developers.com/showthread.php?t=832503&highlight=debrand , which does uses mmc2, you might want to link that one up instead ?
Click to expand...
Click to collapse
Done that, but also told in the first post, why i used the other ones
btw: why you still use version 1.34? Better than 1.7?
any good desire z roms with sense anyone can recommend?
tk-germany said:
btw: why you still use version 1.34? Better than 1.7?
any good desire z roms with sense anyone can recommend?
Click to expand...
Click to collapse
I only use 1.34 because I haven't got round to trying anything else yet. But it works well enough not for me to want to get away from it as soon as possible. Virtuous is a popular Sense-based ROM, and I may well give that a try (it's based on 1.72 as well).
I use the 1.72 virtuous and feel good with it, as i have the impression that it is a bit smoother and the batteryusage seems to be a bit improved, but dunno if thats realy cuz of the new rom.
Only disadvantage, max volume doesnt seem to be bettered up, hope that gets solved soon
hoped to hear of any other rom with that solved and maybe packed with some nice gimmicks
Sent from my HTC Vision using XDA App
Assalam aleikum,
Hi Iam using a german vodaphone 1.72 rom and want to downgrade to get permaroot and so on for a brother,
I Tried to get the downgrade working with this scripture but it dont works i ve done all the way down from goldcart with hexediting stuff and so on but when i reach the point to flash the 1.3 rom on hboot i get everytime a wrong cid error message and he wont install
is there a way to change the CID? for vodafone phones?
hi
i've been trying to downgrade my girlfriends new desire z (bought in a german store). but everytime i tried to flash the PC10IMG.zip in the bootloader via fastboot, it startet searching for it, found it, checked it and then brought up an error "incorrect CID", which i didn't quite understood. i checked the infocid and it's HTC__102, so i did not have to do the goldcard stuff. but i still did not get it working. solution was: not every PC10IMG.zip you can find in the various threads about downgrading the desire z seems to work, for me only the one found in the thread http://forum.xda-developers.com/showthread.php?t=905261 worked.
just wanted to let you know, in case anyone is searching for a solution for this problem
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 .