I've been running cyanogen for over a month perfectly on my rogers dream. Absolutely nothings gone wrong, and I've updated it several times (gotten kernel and rom zips then going into recovery and flashing the new cyan rom then new kernel). Up until cyan 2.12 this was working, but when I tried to upgrade from 2.10 to 2.12 I was getting stuck on the Rogers screen. I nandroided back each time and tried again, first flashing the new rom then radio kernel. I even refollowed the entire cyanogen guide getting a new system.img and everything using 2.12 but it wouldn't take. I'm clueless. I've done wipe data and it does nothing to fix it.
im running 4.2.13 right now, ive upgraded each time there has been a new update out since 4.2 started. do you apply the 1.6 devphone before the cyanogenmod?
EkostonS said:
im running 4.2.13 right now, ive upgraded each time there has been a new update out since 4.2 started. do you apply the 1.6 devphone before the cyanogenmod?
Click to expand...
Click to collapse
Not before every upgrade, but when I first installed cyanogen mod I used HTC ADP 1.6 "Recovery" (-ota-) image.
should do that for every upgrade
well atleast i do anytime i flash a new cyanogen rom i always do the 1.6 first.
never had a single problem with any rom, not anything like you see people complaining about in his thread. only the ones that he fix's like contact issue.
rarely get FC's ever
EkostonS said:
should do that for every upgrade
well atleast i do anytime i flash a new cyanogen rom i always do the 1.6 first.
never had a single problem with any rom, not anything like you see people complaining about in his thread. only the ones that he fix's like contact issue.
rarely get FC's ever
Click to expand...
Click to collapse
But wouldn't that mean I would have to plug into the computer to fastboot and wipte and reload 1.6 every time?
i have not wiped my phone once since i rooted it.
and i leave 1.6 on my sd card at all times. then just download the newest cyan update from cm updater, and go to recovery.
nana backup
flash 1.6
flash cyan
reboot
and then recovery flash theme reboot
and never have probs
EkostonS said:
i have not wiped my phone once since i rooted it.
and i leave 1.6 on my sd card at all times. then just download the newest cyan update from cm updater, and go to recovery.
nana backup
flash 1.6
flash cyan
reboot
and then recovery flash theme reboot
and never have probs
Click to expand...
Click to collapse
I didn't know you can flash 1.6 from your phone
Can you link me to a flashable version you use?
http://developer.htc.com/adp.html
go down the page and download this
Recovery Image signed-dream_devphone_userdebug-ota-14721.zip 47202626 b3e12b004c155761a10b1a848288e0c3
not the system image.
Hmm, wouldn't that brick my phone, I'm on EBl1 here.
i havent a clue, i got my htc dream from rogers in july
rooted it in november with hy*spelling* root guild for the perfect spl since ihad done update
and always flash that 1.6 then cyanogen rom
EkostonS said:
i havent a clue, i got my htc dream from rogers in july
rooted it in november with hy*spelling* root guild for the perfect spl since ihad done update
and always flash that 1.6 then cyanogen rom
Click to expand...
Click to collapse
I used cyan's method to root, so I need to flash the kernel with the rom.
I couldn't have used hy's method because I need HSPA and I believe that doesn't give it to me. No EDGE coverage here.
my phone works perfect on 3g and edge
have you installed the ebi1 kernel also? try that. (only if your radio is the one that starts with a 3)
EkostonS said:
my phone works perfect on 3g and edge
Click to expand...
Click to collapse
It was to my understanding that only cyan's rogers rooting allowed for me to keep running at 1800mhz. I'm on Bell with my Rogers phone here too, so Bell doesn't even do anything else except HSPA. Maybe the one I'm thinking you did isn't the one you really did. Did you use the one that doesn't make you use a kernel for each new cyan?
jiggidy said:
have you installed the ebi1 kernel also? try that. (only if your radio is the one that starts with a 3)
Click to expand...
Click to collapse
Yes I have, no dice I'm radio 3.22.20.17
i followed hy's guild to getting off the perfect SPL rogers threw at us. then went through the steps after that.
Drea*** PVT 32B
hspl 10.95.3000
cpld-4
radio-2.22.19.261
thats where my phones sitting at.
EkostonS said:
i followed hy's guild to getting off the perfect SPL rogers threw at us. then went through the steps after that.
Drea*** PVT 32B
hspl 10.95.3000
cpld-4
radio-2.22.19.261
thats where my phones sitting at.
Click to expand...
Click to collapse
What the heck? I was was 99% sure if I used a different radio on my rogers dream I couldn't use HSPA
you said ur using the dream on bell?
howd u do that? just unlock and use bell sim?
EkostonS said:
you said ur using the dream on bell?
howd u do that? just unlock and use bell sim?
Click to expand...
Click to collapse
Yes.
I don't think using a radio other the 3 one works with hspa for our phones.
so id have to re-root.
thats fine, im pretty much done with rogers.
i dont know if when you install cyangen rom it installs a different radio
cause it says writing radio when installing the rom.
EkostonS said:
so id have to re-root.
thats fine, im pretty much done with rogers.
i dont know if when you install cyangen rom it installs a different radio
cause it says writing radio when installing the rom.
Click to expand...
Click to collapse
Maybe a dev can come help us here. Really confused
Related
For those who didn't dare to try... I got Froyo running on an AT&T version. All you need is to follow this guide: http://www.androidspin.com/2010/05/...-nexus-one-its-like-it-never-happened-almost/
Flash the ERD79 Release, update to EFE27. Then run the Froyo update through Stock recovery. 3G works fine, radio updated (I think?) and everything is fast.
thanks for your post. but the issue that most ATT N1 users are facing is updating to 2.2/Froyo from their non-rooted, bootloader-locked. devices.
vexingv said:
thanks for your post. but the issue that most ATT N1 users are facing is updating to 2.2/Froyo from their non-rooted, bootloader-locked. devices.
Click to expand...
Click to collapse
I think that rooting and unlocking the bootloader it's the way to go now, since like everybody has done it.
poorg said:
I think that rooting and unlocking the bootloader it's the way to go now, since like everybody has done it.
Click to expand...
Click to collapse
Translation:
"Everybody's doing it, come on. What are you, chicken?"
/peerpressure
I'm one that hasn't rooted, yet. Party due to my phone is less than two weeks old and I don't want to void the warranty just yet.
I just went from KangoRama to full wipe to Froyo...
Having owned several HTC phones, there's no way I'm voiding my warranty
Lot of trouble for nothing, if you are already rooted and have Amon's recovery. Just install Paul's Rooted Froyo and you've got the same thing, except with root.
rooting doesnt void hardware warranty
Experienced it
Froyo using AmonRa recovery - WORKS!
Followed some success off CM's forums in getting Froyo up and running on an AT&T N1. In fact it's been pretty error free (short of a couple apps not behaving with 2.2) and to top it off, no wipe needed.
Paul over on Modaco's site managed to pop up an image that is rooted and works with AmonRa's recovery. All I did was copy the zip to the SD card, ran recovery, flashed from SD, and voila! Froyo without having to painstakingly reinstall all my apps. No issues with 3G so far, but like all stock roms, there's no indication of running HSDPA unless you go into the about phone option in settings.
So far cooling off the hot day with some Froyo here.
Paul's Original Post on Modaco
Edit: And yes, if you didn't boot unlock your phone and want 2.2, then your only choice is waiting for the OTA to eventually hit you... when it goes public instead of press-only.
Are you able to view large images on your browser?
I know I'm not :S
http://forum.xda-developers.com/showthread.php?t=687256
update
I followed the guide and went from erd79 to ere27 but when trying to update to froyo my N1 would not boot completely. Ran adb logcat and watched the log and it looped running the same stuff over and over again.
x986123 said:
For those who didn't dare to try... I got Froyo running on an AT&T version. All you need is to follow this guide: http://www.androidspin.com/2010/05/...-nexus-one-its-like-it-never-happened-almost/
Flash the ERD79 Release, update to EFE27. Then run the Froyo update through Stock recovery. 3G works fine, radio updated (I think?) and everything is fast.
Click to expand...
Click to collapse
Yep, flashed the rooted version of FroYo, works great. Love it!!
----------------------------------------------------
Original Text:
----------------------------------------------------
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU, RUU_Hero_C_Sprint_2.20.651.1_signed_test, and re-push flash_image or does it even really matter which hboot I'm running on (figure hboot is the only thing permanently stuck on phone from RUU)?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Any thoughts welcome
-----------------------------------------
This is sorta deprecated now that we have Root on the Release RUU, so repurposing the thread.
My new question: Now that i've rooted the Official Release version, can I restore my old nandroid backup without breaking my phone?
I did a nandroid backup of my fully-set-up Fresh 2.1.2 Install before I ran the Official RUU to 2.27.651.5 and now I'm wondering if it will break anything to "restore" that backup.
Again, any thoughts are welcome.
diaknia said:
Firstly, I tried to search but if this ends up simply rehashing another thread, mods please direct me to proper thread and delete this.
Now to my question. I am still running the base HBoot of my phone from the 1.56 RUU (I bought phone in December 2009). I'm rooted right now with that and using custom ROM/radio.
Now that the infamous 2.1 official RUU is out, would it be safe to up my phone to the root-included TEST RUU and re-push flash_image or does it even really matter which hboot I'm running on?
Or to put another way, do I gain anything from a higher-version hboot from the Test RUU other than it looking more like the official release so root isn't as obvious?
Click to expand...
Click to collapse
to my knowledge if your hboot changes from 1.56 to the one from the official you will lose root as of now, the test RUU still has root but its super buggy, why would you want to flash the official or the test anyways, theres roms here that blow the stock ones out the water, but once again to my knowledge you WILL lose root. And the test ruu with root has mad issues you should do a search bro as far as upgrading to the newer hboot well im not sure if it has features but the devs are still trying to break root in the new hboot.
check this out bro just in case you already flashed it http://forum.xda-developers.com/showthread.php?t=693449&highlight=hboot
I have not yet flashed the Test RUU.
From what I understand the Test RUU still has su built in, so all I need to do is re-push flash_image to get a custom recovery back on it and I'm golden from there.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.
diaknia said:
I have not yet flashed the Test RUU.
I don't plan on using the stock ROM that comes with the RUU more than I have to, just curious about installing custom ROMs from that base versus the 1.56 base.
I still plan on uploading flash_image and doing the custom ROMs and Radio like now.
Click to expand...
Click to collapse
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain
good to know
dirkydirk23 said:
well from what i heard recently that base doesnt have audio issues that some people deal with on certain roms like the drivers are better, but my old hero i always had audios issues not with this refurb i dont get um anymore. but that 1.56 base is solid theres so much **** to work outta 2.1, until then im rocking darchdroid2.63 the only asop rom out there for our phones!
Im running Godspeed recovery, darchdroid2.63 and the latest 2.1 sprint radio and i cant complain
Click to expand...
Click to collapse
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.
diaknia said:
I've already had audio issues installing custom ROMs based on 2.20.651.1 Test while using the 1.56 base, yet Fresh 2.1.2 based on 2.27.651.5 has yet to glitch on me for audio *crosses fingers*.
I'd still prefer to run a 2.27.651.5-based ROM like Fresh 2.1.2 even after upgrading my HBoot to the one from the 2.20.651.1 Test RUU, if I do so.
Original point of my question was if there was anything buggy in the HBoot itself moving from 1.56 to 2.20 RUU. Correct me if I'm wrong but HBoot is really the only thing that can't be easily flashed. You can flash both ROMs and Radio.
Far as AOSP, it's cool and all, but call me crazy: I actually like Sense.
Click to expand...
Click to collapse
There is nothing wrong w/ the hboot. and the hboot isn't even the thing blocking root. The audio issue seems to differ from phone to phone, I have never had audio issues on my phone.
Thanks for the responses, regaw and dirky.
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
On a side note.... i'm an eager follower of the official RUU ROOT thread on the dev sub-forum, Regaw, keep up the good work. Still feel bad for you that you've been stuck without root so long...
When you crack the thing, and I maintain hope you will, that's when I'll probly go and upgrade to the Release RUU.
diaknia said:
It looks like doesn't matter one way or another which base (rooted 1.56 or rooted 2.20) I use. I should have same functionality either way. I'm just gonna stick with 1.56. Really comes down to "if it ain't broke..."
Click to expand...
Click to collapse
Basically this.
abcdfv said:
Basically this.
Click to expand...
Click to collapse
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol
dirkydirk23 said:
yeah ive yet to run into it but i hear hboots are *****es to downgrade, but yeah i guess you and i both learned something dude, im rollin with your last post, if it aint broke dont fix it lol
Click to expand...
Click to collapse
If you had run the test ruu and already pushed flash_image and custom recovery back to the phone then you can restore the original hboot in about 10 seconds if you want.
From recovery flash the .zip attached here and the hboot will revert to 1.41 instead of 1.47.
Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?
diaknia said:
Cool, moot point now, though.
Now that the release version is rooted, I upgraded to the release RUU and re-rooted. Got Toast's OC recovery kernel rocking already.
Sorta off-topic, but I do have one small question:
I made a nandroid of my install of Fresh 2.1.2 before I upgraded. Would it be safe to restore that nandroid back now that i'm on the 2.27.651.5 RUU?
Click to expand...
Click to collapse
I am curious about this also. Currently running fresh 2.1.1 previously from a 1.5 root and was thinking about updating to the .5 ruu and doing the root and than restoring a nandroid
Hello all, some weeks ago i have load a custom rom in my Magic (2.1 eclair legend), but it runs slow and buggy all time.
I would like to know how i can go back to the official rom!
thank you in advance
There is official 2.1 Rogers Android rom for htc magic 32a only
WoblyGoblin said:
There is official 2.1 Rogers Android rom for htc magic 32a only
Click to expand...
Click to collapse
i mean, dont mind i would like to go back to the latest offical for magic, even 1.6!
Do a search for SAPPIMG.nbh
You also can try installing the last RUU File for the Magic, if you have a 32a!
When your installed Custom-Rom is a CursorSense Rom, like Hero or a modified OTA 2.1 from Rogers for Magic, you can do this way:
boot into fastboot, connect to USB and run the RUU.exe-File, this will get you back to Stock, and 1.5
Worked 100% for me.
For a 32b you maybee need a SAPPIMG.nbh how Phateless said, but i´m not sure.
alk1s said:
Hello all, some weeks ago i have load a custom rom in my Magic (2.1 eclair legend), but it runs slow and buggy all time.
I would like to know how i can go back to the official rom!
thank you in advance
Click to expand...
Click to collapse
tom Green said:
You also can try installing the last RUU File for the Magic, if you have a 32a!
When your installed Custom-Rom is a CursorSense Rom, like Hero or a modified OTA 2.1 from Rogers for Magic, you can do this way:
boot into fastboot, connect to USB and run the RUU.exe-File, this will get you back to Stock, and 1.5
Worked 100% for me.
For a 32b you maybee need a SAPPIMG.nbh how Phateless said, but i´m not sure.
Click to expand...
Click to collapse
Tom Green is right, we really need to know what hardware you're on so we can accurately advise you without worry of bricking your device.
Power the phone off. Then hold the BACK + POWER buttons until you get to a screen with three androids on skateboards.
Type in all the info from that screen. We need to know if you're a 32a or 32b.
hey guys, sorry for answering late to you. I've got the 32a version. So i'll try the method you mentioned in here. hopefully will works
Please post if this method worked or not, or if anyone knows if this method will work on a MyTouch 3g 3.5mm(1.2) USA and get me back to stock. When T Mobile releases the OTA Froyo update for my phone I want to revert back to stock so I can get it. Thanks.
housry23 said:
Please post if this method worked or not, or if anyone knows if this method will work on a MyTouch 3g 3.5mm(1.2) USA and get me back to stock. When T Mobile releases the OTA Froyo update for my phone I want to revert back to stock so I can get it. Thanks.
Click to expand...
Click to collapse
http://theunlockr.com/2009/08/22/how-to-unroot-your-mytouch-3g/
alk1s said:
Hello all, some weeks ago i have load a custom rom in my Magic (2.1 eclair legend), but it runs slow and buggy all time.
I would like to know how i can go back to the official rom!
thank you in advance
Click to expand...
Click to collapse
This link will get you back to Cupcake, but since I'm much more familiar with the 32b I'm not sure if there is a manual update after you restore Cupcake.
http://theunlockr.com/2009/10/06/how-to-unroot-the-htc-magic-non-mytouchget-back-to-cupcake/
Phateless said:
This link will get you back to Cupcake, but since I'm much more familiar with the 32b I'm not sure if there is a manual update after you restore Cupcake.
http://theunlockr.com/2009/10/06/how-to-unroot-the-htc-magic-non-mytouchget-back-to-cupcake/
Click to expand...
Click to collapse
but ru sure that it works? most of the ppl in there mention that didn't work, and they came with errors!
alk1s said:
but ru sure that it works? most of the ppl in there mention that didn't work, and they came with errors!
Click to expand...
Click to collapse
I really don't know a lot about the 32a, sorry...
I'd like to use the new radio with my oem Donut. Is it as simple as taking the file from one of the update guides and flashing it in the traditional manner? I'm kind of noobish so I'm reluctant to try to take one piece of a Froyo update guide and flash the radio. I'm not really in the market for a sleek black paperweight.
I wouln't do it!
This has BAD IDEA written all over it please don't try this. That being said why not upgrade to the official FROYO? I know it's hard to fathom after seeing ECLAIR in action but it truly is a totally different and better experience.
QUESTION: What does DONUT have that you like so much?
Edubyah said:
This has BAD IDEA written all over it please don't try this. That being said why not upgrade to the official FROYO? I know it's hard to fathom after seeing ECLAIR in action but it truly is a totally different and better experience.
Click to expand...
Click to collapse
lol, I agree, that's why I posted first.
QUESTION: What does DONUT have that you like so much?
Click to expand...
Click to collapse
SPEED. I tried the TMUS rom posted up here a few days ago and it was ok, much better than other Froyo ROMs I've tried, but still laggy compared to my oem androoted Donut.
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
I'm scared to try this. Is this the radio that came with the T-MOUS Fro-Yo OTA? I wonder why there isn't a thread for it yet.
Moving to General
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
The hboot? Which hboot are you talking about? The first half of the ota update succeeded but the second half failed so I have the new SPL but not the new radio or OS.
The new radio does work with cm6, well cm6.1 rc1. I flashed it on my wife mt3g 3.5mm awhile ago, everything booted up just fine.
d3vilskid said:
The new radio does work with cm6, well cm6.1 rc1. I flashed it on my wife mt3g 3.5mm awhile ago, everything booted up just fine.
Click to expand...
Click to collapse
Cool, did you or she notice any improvements?
Yea i got to messed with it a little bit more, signal is pretty strong and stays constant, but that might vary from phone to phone, not much to say about the market since it was down a couple days back. Overall she is satisfied with it. Cant wait till it is ported to the 32b phones so we can take advantaged of the extra 10-15mb it frees up.
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
So I just flash this through recovery as I would any other zip file? Any idea if this is compatible with older roms? If I nandroid back to my oem 1.6 without rolling back to 23.02 will my phone explode? How about Eclair?
If I flash this is it just as easy to flash back to 23.02 if I need to for some reason?
Sorry for all the obsessive questions; I've never flashed a radio before so I don't know what it is that I don't know.
aaraya1516 said:
it works with CM4 if you don't use the hboot.
does not work with CM6. look at my sig I made a flashable .zip file.
Click to expand...
Click to collapse
im flashing that radio now onto cm6.1, ill post my results
EDIT: Your .zip file doesnt work. It did nothing, after i flashed and rebooted then shutdown and went into fastboot my radio was still 2.22.23.02.
Foo_Blyat said:
im flashing that radio now onto cm6.1, ill post my results
EDIT: Your .zip file doesnt work. It did nothing, after i flashed and rebooted then shutdown and went into fastboot my radio was still 2.22.23.02.
Click to expand...
Click to collapse
It worked for me, except it caused a bootloop because it's not compatible with the CM6 kernel, or at least ezterry's CM6 kernel. I had to flash back to 2.22.23.02.
If you're not using the oem t-mobile/android kernel, don't flash this radio.
I really want to know if this radio is compatible with oem Donut.
Hello
I'm trying to revert my phone back to the stock ROM from telus. I've downgraded to 1.32 and gave up when i found out that sound on the desire HD doesnt work on CM7.
How do I revert back?
ive searched the forum and tht's all ive found
" just flash a stock RUU? That uses your PC to flash your phone, not bootloader."
any help would be appreciated. Where do i get the RUU file and how do i go about doing this.
A $10 paypal donation will given to anyone who helps. i really need to get the phone back, its my girlfriend's. (
btw i have turned S-air off and done a perm-root with visionary already.. how do i get the cherry back in place?lol
You can flash either Raidroid in clockworkmod, or use Telus RUU. Android Revolution HD is also a good (the best) option if you want performance and good battery life.
Raidroid is a stock ROM that will keep your root and S-OFF, so it is easy to flash a custom ROM in the future. RUU will revert your phone to stock, Radio S-OFF will remain if you used it. Android Revolution HD is the best custom ROM out there. Every option gives you working sound.
jkoljo said:
You can flash either Raidroid in clockworkmod, or use Telus RUU. Android Revolution HD is also a good (the best) option if you want performance and good battery life.
Raidroid is a stock ROM that will keep your root and S-OFF, so it is easy to flash a custom ROM in the future. RUU will revert your phone to stock, Radio S-OFF will remain if you used it. Android Revolution HD is the best custom ROM out there. Every option gives you working sound.
Click to expand...
Click to collapse
are there any issues with android revolution?like sound problems with the CM7?
Nope, Telus users are reporting that it works great. Some users have had small microphone echo while using it, but that can be fixed by flashing a simple zip in clockworkmod just like you would flash a ROM.
http://www.wbakkercomputers.nl/mic_fix.zip
jkoljo said:
Nope, Telus users are reporting that it works great. Some users have had small microphone echo while using it, but that can be fixed by flashing a simple zip in clockworkmod just like you would flash a ROM.
ok, i'll try android revolution hd. Earlier today when i checked the terminal was showing the # instead of $. now when i checked, its back to $. I went on visionary app again, did a temp root and perm root, and checked the terminal again but its still showing the $ sign.
i don't know what the build number is for, but its now on 1.32. I wanna go back to the 1.84. I've noticed that the revolution HD has the 'official HTC RUU 1.84.61.2', so in the process of flashing the ROM, 1.84 should be back, right??
I'm a little bit confused about baseband versions and md5 checksums. mine is 12.28b.60.140eU_26.03.02.26_M. which radio version should i flash with?
I'm totally new to this and I hope to get working by tomorrow night. I really appreciate your help, donation will definitely be made once i get this thing working. i couldnt pick up any calls today..lol
Thanks a lot
Click to expand...
Click to collapse
ziyaad89 said:
Hello
I'm trying to revert my phone back to the stock ROM from telus. I've downgraded to 1.32 and gave up when i found out that sound on the desire HD doesnt work on CM7.
How do I revert back?
ive searched the forum and tht's all ive found
" just flash a stock RUU? That uses your PC to flash your phone, not bootloader."
any help would be appreciated. Where do i get the RUU file and how do i go about doing this.
A $10 paypal donation will given to anyone who helps. i really need to get the phone back, its my girlfriend's. (
b
btw i have turned S-air off and done a perm-root with visionary already.. how do i get the cherry back in place?lol
Click to expand...
Click to collapse
Android Revolution works perfect, and has lots of customization options.
In case you still want Cyanogen, CM7 nightly build 12 worked just fine on my Telus... It has the sound fix built in to it.
ziyaad89 said:
jkoljo said:
ok, i'll try android revolution hd. Earlier today when i checked the terminal was showing the # instead of $. now when i checked, its back to $. I went on visionary app again, did a temp root and perm root, and checked the terminal again but its still showing the $ sign.
i don't know what the build number is for, but its now on 1.32. I wanna go back to the 1.84. I've noticed that the revolution HD has the 'official HTC RUU 1.84.61.2', so in the process of flashing the ROM, 1.84 should be back, right??
I'm a little bit confused about baseband versions and md5 checksums. mine is 12.28b.60.140eU_26.03.02.26_M. which radio version should i flash with?
I'm totally new to this and I hope to get working by tomorrow night. I really appreciate your help, donation will definitely be made once i get this thing working. i couldnt pick up any calls today..lol
Thanks a lot
Click to expand...
Click to collapse
After you flash a ROM with 1.84, you'll be back on 1.84
I wouldn't mess around with radio just yet, it works fine using stock Telus radio. If you notice battery drain or reception issue then flash the recommended radio.
Click to expand...
Click to collapse
cue_32 said:
ziyaad89 said:
After you flash a ROM with 1.84, you'll be back on 1.84
I wouldn't mess around with radio just yet, it works fine using stock Telus radio. If you notice battery drain or reception issue then flash the recommended radio.
Click to expand...
Click to collapse
ok so i'm running revolution HD right now, and the in-call sound quality is really bothering. I've installed that zip file mentioned above that is "supposed" to fix it but still the same
Are you running CM7 on yours?hows the incall sound quality? i might revert back to the stock ROM. Its weird how a slightly modified stock ROM is giving such an issue.
Click to expand...
Click to collapse