Related
This post for anyone who knows how to root the new updated Rogers HTC Magic with the new:
32A
HBoot - 1.76.0010
Radio - 6.35.10.18
Please post any comments or suggestions if they are applicable.
Thank you.
Rogers HTC Magic (32A)
HBoot - 1.76.0010
Radio - 6.35.10.18
I'm in the same boat. Updated my phone with the Rogers updater, and 1.76.0010 seems to be a perfected SPL. I'm going to attempt the gold card method once I get the necessary hardware this weekend. I'm just concerned I might brick my phone, since all the gold card tutorials are pretty old...
+1
Any results?
Diddo, same problem. Tried the "One Click Root", no joy.
I thought that the data connection issue was b/c of the new radio so I foolishly listened to Rogers. Last time I make that mistake.
I am also in dire ned of a method to root this, or even reverse Rogers....
Maybe try the full version of the Relenless Rooter plus (the one for perfected SPL) software? It seems that 1.76.0010 is a perfect SPL.
Thankfully, I read all over the web and decided not to use the security patch that Rogers suggested and did not update. I kept the 1.33.0009 SPL and was able to use the normal Relenless Rooter software. Don't know it the full software will work for the 1.76.0010 SPL but why don't give it a try.
i'm pretty sure it has already been tried, and doesn't work
i too, am in the same boat
rogers kind of bullied us into this update, and i feel really stupid for falling for it.
i hope someone is working on a fix, tho i am yet to read one post saying that someone is.
Not to be mean or rude or a troll, but there were several warnings against updating with the official RUU.
In fact the "Rogers Mandatory Update Thread" many people mentioned many times to just wait till it was rooted then flash the rooted ROM.
But some people had to be hasty...
Taknarosh said:
Not to be mean or rude or a troll, but there were several warnings against updating with the official RUU.
In fact the "Rogers Mandatory Update Thread" many people mentioned many times to just wait till it was rooted then flash the rooted ROM.
But some people had to be hasty...
Click to expand...
Click to collapse
Yes and no. What do you expect when Rogers cut off your data if you don't update. If you went to Android forums or here, you'll find what kind of saga people with rooted phones went in order to obtain data back.
So, at that time, people with the original cupcake had three choices: Root the phone and go through curse droid's complicated process to get his rom, root and find another Rom + patch so as to trick Rogers into believing that the phone has been updated, or just go ahead and flash the official rom (and then hope someone can root it).
visitador02 said:
Yes and no. What do you expect when Rogers cut off your data if you don't update. If you went to Android forums or here, you'll find what kind of saga people with rooted phones went in order to obtain data back.
So, at that time, people with the original cupcake had three choices: Root the phone and go through curse droid's complicated process to get his rom, root and find another Rom + patch so as to trick Rogers into believing that the phone has been updated, or just go ahead and flash the official rom (and then hope someone can root it).
Click to expand...
Click to collapse
Complicated procedure? You are mixing up two methods that made it possible to keep root. For cursor, all u needed to do was flash spl and radio, then his Rom, that's it. There is another method that allows u to keep original radio and. Spl, this one uses a script after applying a new rom. Just giving the facts, I do feel sorry for those that jumped the gun though, i was really close myself
visitador02 said:
Yes and no. What do you expect when Rogers cut off your data if you don't update. If you went to Android forums or here, you'll find what kind of saga people with rooted phones went in order to obtain data back.
So, at that time, people with the original cupcake had three choices: Root the phone and go through curse droid's complicated process to get his rom, root and find another Rom + patch so as to trick Rogers into believing that the phone has been updated, or just go ahead and flash the official rom (and then hope someone can root it).
Click to expand...
Click to collapse
Rogers cut off my data. I rooted phone and applied CursorSense ROM and now i'm good.
I would be happy to help any Roger customers who want to apply this ROM. The steps are pretty straight forward as long as you have some computer knowledge.
how do you root your phone after it has been updated? or how do you undo the update to root it? any help would be appreciated
crystalbellaboo said:
how do you root your phone after it has been updated? or how do you undo the update to root it? any help would be appreciated
Click to expand...
Click to collapse
That's the reason for this thread. The update includes a new radio and no developer have found a way around it. Maybe the main developers (aka chefs) have moved on to newer and more exciting devices, like the Nexus One.
Who knows, maybe you guys can band together and pay a developer to do this?
visitador02 said:
That's the reason for this thread. The update includes a new radio and no developer have found a way around it. Maybe the main developers (aka chefs) have moved on to newer and more exciting devices, like the Nexus One.
Who knows, maybe you guys can band together and pay a developer to do this?
Click to expand...
Click to collapse
It's the SPL that's perfected. Not the radio. And most devs for the 32A are still here. It's mostly G1/Dream devs namely Cyanogen who have moved on to the Nexus One.
Amon_RA is still giving updates to the G1/Dream and MT3G/Magic and Hero.
crystalbellaboo said:
how do you root your phone after it has been updated? or how do you undo the update to root it? any help would be appreciated
Click to expand...
Click to collapse
I didn't update my phone. I didn't realise that this was a problem. Sorry to get your hopes up.
Taknarosh said:
It's the SPL that's perfected. Not the radio. And most devs for the 32A are still here. It's mostly G1/Dream devs namely Cyanogen who have moved on to the Nexus One.
Amon_RA is still giving updates to the G1/Dream and MT3G/Magic and Hero.
Click to expand...
Click to collapse
You are right about the SPL. I meant that too. I mixed Radio and SPL because Rogers is scanning for the new radio even for those who have root, as the developers page show.
Anyway, best of luck to those who upgraded and got the perfected SPL. Maybe someone can ask a favor from one of the developers?
Some help with rooting the 32A magic from rogers
Already asked for help via PM, no dice. I suspect that after the update the devs are inundated with requests. I'm happy to pay for someone to figure this out, but don't really know who to approach. Anyone?
So still no luck on anyone rooting this update... This is taking a lot longer then I thought it would. I only did the update because I was sure someone would be willing to jump right on and root this new SPL but no dice.
FoTwoZero said:
So still no luck on anyone rooting this update... This is taking a lot longer then I thought it would. I only did the update because I was sure someone would be willing to jump right on and root this new SPL but no dice.
Click to expand...
Click to collapse
I know what you mean... hopefully someone comes through for us.
novadoc said:
I know what you mean... hopefully someone comes through for us.
Click to expand...
Click to collapse
If we dont get root within the month then I'm calling Rogers and complaining to them about random misc stuff that I'll make up about the phone to get rid of it and get a new(better) phone.
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
You have to use either Sprint 1.29 RUU or Fresh's 1.56 RUU. That will make it stock again.
jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
Yeah I believe I used the 1.29 RUU from the stock rom
jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
I used 1.56 RUU and went back to stock. Worked fine on mine w/ stock radio.
jdgiotta said:
I'm looking to root and flash my Hero to DamageControl 2.0, but has anyone successfully restored the device back to factory defaults after flashing to DC2.0?
Click to expand...
Click to collapse
Some people do, and some don't. There is a fix if you brick it while RUUing. However if you are wanted to go back to stock for the 2.1 "official" release you might not be able to root again. They seem to leave the door open on the first round of software, but then close the hole on the next round. Seems the case for every phone
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
jdgiotta said:
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
Click to expand...
Click to collapse
Yea give it like 24 hours after the release, someone will do a nand dump, root it and post it on here. One thing I would reccomend people stay away from would be a new version of an RUU based off of 2.1, as that would put you up a **** creek if a root isn't found. I hear lots of problems trying to .29 RUU after a .56 RUU, I'm sure the same will be said for whatever the next version is.
jdgiotta said:
So the ability to root maybe lost if I was to update to a "official" release. Hmm... okay, good to know. Thanks.
Click to expand...
Click to collapse
They may, or may not close the exploit that was found in 1.5 but if so it will only be a matter of time before some of these guys who are far more talented than I find a way to root 2.1, 1.5 was not rootable when it was released. Regardless the 2.1's you will see later today will be far superior to whatever sprint ends up releasing.
You should be able to RUU without any issues. However, you might still not be able to see protected apps in the market. I used the steps in this thread to fix that:
http://forum.xda-developers.com/showthread.php?t=605028
xanadu1979 said:
You should be able to RUU without any issues. However, you might still not be able to see protected apps in the market. I used the steps in this thread to fix that:
http://forum.xda-developers.com/showthread.php?t=605028
Click to expand...
Click to collapse
This fix didn't work for me, however I was able to RUU, update to DamageControl 1.0, download some protected apps, and then upgrade to DC2.0r2 (without wiping between DC1 and DC2). This opened up protected apps and solved the black on black contact problem for me.
-obviously do so at your own risk and all-
&RoidRage said:
Some people do, and some don't. There is a fix if you brick it while RUUing. However if you are wanted to go back to stock for the 2.1 "official" release you might not be able to root again. They seem to leave the door open on the first round of software, but then close the hole on the next round. Seems the case for every phone
Click to expand...
Click to collapse
Speaking of this, I am currently rooted, but running stock 1.5(don't ask)will I still be able to get the update or do I have to be completely unrooted to do so!
Also as far as the update is concerned, I know on the droid forums there were instructions on saving the update before installation so all could get it! What is the procedure for doing so!
It seems with the current state of affairs the update could come in a minute or a day or a month, basically no one know, so it could be anytime, so I just wanna be prepared for when it drop to hand it off to the real DEV.!
Roman
Eh, you could go ahead and flash a new ROM right now if you want. A fix was found for people getting bricked from the RUU, so you're safe to use the RUU now without fear of having a permanent brick on your hands.
Roman G said:
Speaking of this, I am currently rooted, but running stock 1.5(don't ask)will I still be able to get the update or do I have to be completely unrooted to do so!
Click to expand...
Click to collapse
Good question
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
I don't think they can actually push a OTW update.....
barnacles10 said:
This is not a 2.1 speculation thread, I just thought I'd ask it here with all that knowledge floating around.
WHEN (May 7th?) the 2.1 update is OFFICIALLY dropped, will rooted users be pushed the update? Or will it only go out to models registered as running 1.56.
ASSUMING one might want to upgrade and that push comes, you guys think updating might cause any harm to the phone? I'm thinking 1.56RUU..
I don't think I will partake in the official release, I can't imagine it being any better then what I have now, and what will come after that official release is dropped, however I have had this question for a while. So what do you guys think?
Click to expand...
Click to collapse
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other potential nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found. This fully depends on whether old method is patched.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
danknee said:
It is not going to be OTA. It will not matter if you are running custom whatever or stock.
If you run the ruu.exe it will load the official 2.1 release on your phone. The only reason it may not work would be if you ran the 2.1 test ruu.exe and for some reason the official release's hboot is lower than 1.47.000 (the hboot that came with the test release).
Other nasty side effects you could get with your official release:
No root
Possibly never be able to root again, or at least stuck with no root until a new work around is found.
No custom recovery, no custom roms, no ability to flash .zips from recovery. This goes along with the lack of root.
Inability to run 1.56 ruu ever again due to updated hboot.
Click to expand...
Click to collapse
Couldn't have said it better myself! I would just suggest waiting until the cook of your preference updates his to include items from the official release.
And the single most important reason: No nandroid. Having a point in time backup is insanely important to me. If I ever have to return my phone and get a refurb, it's nice to know I've got a nandroid that will get me right back to where I was before I turned in my phone.
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
I for one will not be updating to it. My phone is working perfectly as is and this would give me no additional functionality so why bother?
As for the whole rooting issue, I wish folks wouldn't be so scared of the new hboot. I used the RUU and I have custom recovery and can flash any ROM I want. Yes, I know the leaked RUU had root already, but I rerooted it properly and installed busybox and all that so I could use the phone how I wanted.
Anyway, sorry to get sidetracked there, my comment about being so scared of the new hboot is simply this...There is no way the new version will not be rooted sooner or later. Obviously Sprint and HTC would like us to not be able to root any phones but someone always finds a way. There is no way that the new firmware will not be rooted sooner or later. Just like how the Evo will get rooted, as will any newer phone released after it. It is inevitable that someone will figure it out especially with all the talented and experienced folks here working on it as soon as it's released.
Click to expand...
Click to collapse
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
cicada said:
Correct me if I'm wrong, but won't we be able to simply use an older RUU (1.52, etc) to get the phone rootable again?
My intention was going to be to try out the new stock RUU for a bit, then re-flash with an older RUU, get root and RA recovery back on, then go back to Fresh Toast. Will this not be possible?
Click to expand...
Click to collapse
Not possible if the Hboot updates, which it probably will. Those here who tried the test leak 2.1 ruu.exe were unable to run the 1.56 ruu after.
There is an alternative to restore everything except the hboot from the 1.56 ruu here, but you cannot simply run the .exe. This method won't work if the official build has patched the ability to gain root (you won't be able to nandroid). In that case you will be stuck with official 2.1 only.
BTW, speaking from experience with the test build, ruu, hboot, etc.
Kcarpenter said:
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one. So you are correct, my assumption is that we will find a root for it one day. BUT I do think that if the EVO drops soon after, all of the talent that can find one will be on it. Then again, some people are of the mind set "Leave no device un hacked" and it would bother people if they knew we didn't have root LOL
Click to expand...
Click to collapse
Open source is never a disadvantage. Ever.
Good to know, would've been awful to have to wait for new root hack just because I tried the new and shiny!
Guess I will sit back and wait for dev magic before I jump the gun.
Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
Mater of semantics, politics, and Ideaologies.
Google has a half belief here, they like open, but they protect that damn search algorithim like its a sacred scripture - Last count I think 8 people on earth knew exactly how it worked.
So the disadvantage to google would be ungodly competition if it was released. Proprietary stuff is a win if you look for profits. Again...depends on which side of the spectrum you are on. Points can be argued either way.
jlem26 said:
It won't be OTA as I have read in more than one place that Sprint limits OTA updates to 9MB. Since this will be close to or over 100MB it's going to be OTW.
Click to expand...
Click to collapse
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
ramiss said:
I think the OP is asking about an OTA 'notification' that the official update is available. If so then yes, everyone with a Hero will get a text message regardless of what rom we have installed.
Click to expand...
Click to collapse
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Kcarpenter said:
THAT BETTER NOT COUNT AGAINST MY TEXT LIMIT!!!!
Click to expand...
Click to collapse
ROFL. . . you don't have unlimited text?
lol I would hope having a hero you would have unlimited data and texts
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
yeah, but I still keep track of them. Habitual addiction to knowing everything LOL.
Click to expand...
Click to collapse
lol! that's great.. ever since sprint gave us that free mobile to mobile in any network I do not bother checking minutes or texts. unless my bill changes.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
One big disadvantage/advantage in our case, is that Linux is open source. Anyone who wants to find a root exploit, and is smart enough has the ability to find out where there is potential code to allow for one.
Click to expand...
Click to collapse
Why is it that people still think open source means insecure? I don't claim to know how previous rooting techniques exploit Android, but I do know that 2 Linux distros have a higher government security rating than any other operating system. I assume most weaknesses in android have to do with the recovery and/or update code, which has nothing to do with Linux.
Sawawa said:
Open source is never a disadvantage. Ever.
Click to expand...
Click to collapse
It IS when HTC bogards it from us and hordes it like cookie monster does cookies. I thought open source meant OPEN SOURCE. Ahh, who knows i probably misunderstood the whole concept
OK a nice simple one,
had my dhd a few weeks now very pleased with it. Am a massive fan of cyanogenmod roms, previously had a magic 32b and his roms were the best thing to happen to the phone, so am holding out for a cyanogenmod dhd rom - fingers crossed!
So if I install OTA updates will it stop me from getting root with S-OFF in the future. Golden rule of flashing anything (apart from backing up first!!) is not to update to the latest system software. Well this has always been the case with anyhing I have flashed in the past (psp, ps3, magic 32b, ipod, iphones etc...) is that also the case with the DHD?????
DHD on T-Mobile UK.
nop, its not like "apple" devices, you can install otas from htc and hack your device, the ota include some software issue that fix (bugs and so).
btw: if you have root and recovery - you will not get any OTA, the recovery blocks it,
but you will get it from your costom rom vision.
As I thought, same deal as my old magic 32b then. Still think i'm going to sit on the fence for a while an watch what roms get developed or ported over.
I just miss a few of the mods in CM roms, silly thing like being able to enter a custom field in the add contact menu. Im sure i'll get over it. Although I believe that was a wysie mod to the phone book.
Thanks for the quick response.
Just gotta say how nice this phone is after my magic 32b, its like upgarading the ram and processor on your PC, it flies!!
An afterthought,
it seems it would be sensible to install the first few OTA updates before rooting so any stock software bugs are fixed before you loose the ability to update OTA.
Unless of course you are flashing a custom ROM which I assume the devs would include the bugfixes within their ROMS.
Why dont you try the CM rom now and if you dont want to keep it unroot the phone ?
Its brilliant by the way
I didnt realise there was a CM rom for the DHD, i couldnt see a category on his site for the DHD
But I do see it on the first page here in the dev section. Very pleased CM for the DHD and the phone has only been out a short while!
http://forum.xda-developers.com/showthread.php?t=844703
liorra3 said:
nop, its not like "apple" devices, you can install otas from htc and hack your device, the ota include some software issue that fix (bugs and so)...
Click to expand...
Click to collapse
Untrue: OTAs can and surely will fix the exploit used to root our DHD. Once rooted, never install an OTA and wait for a custom rom with the fix(es).
f.
Sent from The Galactic Empire using the Dark Side of The Force
forelli said:
Untrue: OTAs can and surely will fix the exploit used to root our DHD. Once rooted, never install an OTA and wait for a custom rom with the fix(es).
f.
Sent from The Galactic Empire using the Dark Side of The Force
Click to expand...
Click to collapse
Although if they do screw us over it is still possible to restore an older ruu image and re-root. I have archived myself a copy of the original WWE just in case.
dr.m0x said:
Although if they do screw us over it is still possible to restore an older ruu image and re-root. I have archived myself a copy of the original WWE just in case.
Click to expand...
Click to collapse
No, because they usually update the hboot, and when they do that, you're properly f#@&!d because Devs have to find a new exploit.
f.
Sent from The Galactic Empire using the Dark Side of The Force
forelli said:
No, because they usually update the hboot, and when they do that, you're properly f#@&!d because Devs have to find a new exploit.
f.
Sent from The Galactic Empire using the Dark Side of The Force
Click to expand...
Click to collapse
Couldn't you make a goldcard with sdk and a HxD hex editor??...then flash the ruu and you should be able to OTA..
Not as I see a need to do this as the Devs will always make new custom roms with the updated offical roms anyway..
For everyone who's been wondering and asking,
As of right now there is NO WAY to root your phone if you accepted the 2.3 Gingerbread OTA update and there is no way to revert back to 2.2.
For all the people who have accepted it, you are stuck with a non-rootable phone until a dev can produce a new root method.
With that being said, temp-root is also NOT available.
Also, flashing anything like a different ROM or a new kernel is NOT possible at this time.
If you accidentally updated or just got the phone from Sprint, you are out of luck for now.
thanks for the info. i have been waiting to update because i suspected as much. For all those that updated to 2.3, is it awesome????
Sent from my PG06100 using XDA App
How long did it take for 2.2 to be rooted? Hopefully 2.3 should take the same amount of time/less time.
-CM7 ADR6300
Caiaphas said:
there is no way to revert back to 2.2.
Click to expand...
Click to collapse
The old official RUUs don't work on the phone?
x99percent said:
The old official RUUs don't work on the phone?
Click to expand...
Click to collapse
Nope, they don't.
Lancerz said:
Nope, they don't.
Click to expand...
Click to collapse
Any more of an explanation than that? ...like the error message you get?
People had to RUU back to an older version of Froyo when the latest update plugged up what was the latest root exploit, and that old RUU always worked without a problem. It would be a shame if HTC/Sprint didn't "allow" people to revert back to the older OS.
I think the error code was error 170 when running the RUU, but I have tried all the ways just like everyone else and none of them work.
dpwhitty11 said:
How long did it take for 2.2 to be rooted? Hopefully 2.3 should take the same amount of time/less time.
-CM7 ADR6300
Click to expand...
Click to collapse
FOREVER!!!! At least it felt that way. More people should have the phone now so shouldn't be too long.
Lancerz said:
I think the error code was error 170 when running the RUU, but I have tried all the ways just like everyone else and none of them work.
Click to expand...
Click to collapse
I would guess that booting into the bootloader to load the old Froyo RUU would still work. I always thought the RUU was looking for the proper phone, regardless of its firmware/OS versions.
Nope, in order for a ruu to run, the phone has to have the same or older hboot
Sent from my PG06100 using XDA App
I wish it was that easy because I forgot how much the GPS sucks on sense roms. Got a trip out of town coming up this weekend also, grrrr.
Lancerz said:
I wish it was that easy because I forgot how much the GPS sucks on sense roms. Got a trip out of town coming up this weekend also, grrrr.
Click to expand...
Click to collapse
Really? I always thought Sense was great, but AOSP roms sucked at GPS.
Just used the gps in the 2.3 rom and it worked out great. It was a short distance though so might need more testing fyi
I think the GPS on sense (stock at least) tends to take a little longer to lock on, that's all.
Hopefully this gets rooted soon since I've got to send my current phone back in a couple of days, and it wouldn't surprise me if the new one has the update already
danaff37 said:
Nope, in order for a ruu to run, the phone has to have the same or older hboot
Click to expand...
Click to collapse
So is this "170" error seen in the RUU program or on the phone itself?
Forgive me if I'm way behind the ball on this: The Froyo RUU contains a "rom.zip" that looks like it could simply be renamed to PG06IMG.zip and flashed from the bootloader.
x99percent said:
So is this "170" error seen in the RUU program or on the phone itself?
Forgive me if I'm way behind the ball on this: The Froyo RUU contains a "rom.zip" that looks like it could simply be renamed to PG06IMG.zip and flashed from the bootloader.
Click to expand...
Click to collapse
I don't know bout that error but when I tried twice to ruu my wife's phoneI think the error was 104 bootloader not new enuff something like that.
Well when you run the RUU it goes through all the motions like its going to be successful. Then it reboots into the bootloader and you get the all black HTC screen on your phone while its updating. The RUU on your pc screen is at the part where it says updating your rom image may take 10 minutes etc. Then you get the error [140] Bootloader version error. "The rom update utility cannot update your Android phone, please get the correct ROM update utility and try again."The error [170] is when it doesnt find your phone connected to the usb.
This should be done uploading in about 3 minutes. Rename to PG06IMG.zip, place it in the root of your SD card, and boot up in the bootloader. If it doesn't work, I'll have another to try tomorrow.
BACK UP YOUR DATA/APPS/CONTACTS FIRST (I recommend using Titanium Backup, SMS Backup & Restore, and Call Logs Backup & Restore... and you should be syncing your contacts to a google account)
http://www.4shared.com/file/ADnrxUXB/Stock-Froyo-ROM-1176511.html
I'll give it a try now
Edit: Nope, that doesn't work.
great.
i guess i am stuck with this buggy 2.3 rom until a root solution is found and i can get this crappy rom off my phone. i am tired of the apps not working. locking up & same with the OS.
do the world a favor and steer clear of the RUU 2.3 rom. dont be stuck like the rest of us with a rom we cant do anything with.