Full Revert from DamageControl2.0 - Hero CDMA General

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

Related

The benefits of root?

I have a new Sprint HTC Hero and was wondering what I would benefit from rooting my new phone.
everything
pretty much anything you would like.
one of my favorite functions is WIFI tether for my laptop and iTouch.
another cool feature is the latest "Fresh" rom. which is currently 1.1
its much faster than the stock sprint rom. plus its pretty!
P.S. and if you ever want to go back to stock you can do that as well!
if nothing else
I rooted my phone for this one reason. I wanted to be able to do back ups of my entire system that way if anything happened, then I didnt have to spend hours redoing everything. eventually though I have become a flash addict. I run fresh 1.1 for my daily rom and I play with AOSP 1.6 and flipzmod and companys 2.1 beta at night. all 3 are great but fresh 1.1 is the most stable
wtphoto said:
I rooted my phone for this one reason. I wanted to be able to do back ups of my entire system that way if anything happened, then I didnt have to spend hours redoing everything. eventually though I have become a flash addict. I run fresh 1.1 for my daily rom and I play with AOSP 1.6 and flipzmod and companys 2.1 beta at night. all 3 are great but fresh 1.1 is the most stable
Click to expand...
Click to collapse
very well put, i forgot about mr nandroid!
Thanks for the info. I have just one more question. If I root my phone can I just update it to software version 2.1 when Sprint releases it in the very near future, or will I need to wait for some kind of release from this site?
Thanks.
you'll most likely need to update using a rom from this site. The good thing is, that there will be a release here of it within 24-48 hours.
obelisk79 said:
you'll most likely need to update using a rom from this site. The good thing is, that there will be a release here of it within 24-48 hours.
Click to expand...
Click to collapse
Why is that? Why can't he flash to an official rom then update?
Well actually you can go ahead and get the 2.1 update from sprint when it's released, that will undo root though, and since no one has seen it re-obtaining root would take a while for someone to figure out again. That and the 2.1 will probably be available here in leaked form before sprint releases it anyway at least all my windows mobile phones saw leaks on XDA before the carrier. Root is good and should be worth it if you are the kind of guy that likes playing with their tech instead of just using it, otherwise you may be getting yourself into more than you're willing to put up with longterm.
If he flashes the official 2.1 rom when it is released, it is very likely that will invalidate current methods to root the cdma hero. Then you'll have to wait for a new root method to be found. It is also very possible/likely that upgrading to 2.1 via the official RUU once released will make it impossible to flash the 1.5 based RUU's to regain root.
So effectively he could update but would lose the capability to root the device and all of the resulting benefits it offers until a new root method is discovered.
Edit: thezero4 beat me to it, and is also very correct.
my bad wrong thread
Thanks for all of your input and information. It was very helpful and my phone is now rooted and running the fresh rom. Awesome.
I'm still new to this.
How do you backup your phone.
How would you put everything back to stock if needed.
Thanks so much for any help.
schultzy001 said:
Thanks for all of your input and information. It was very helpful and my phone is now rooted and running the fresh rom. Awesome.
I'm still new to this.
How do you backup your phone.
How would you put everything back to stock if needed.
Thanks so much for any help.
Click to expand...
Click to collapse
to perform a nandroid backup there are 2 options. you can either use the fresh pre-kitchen and perform your backups and restores from you comp or you can boot into recovery and go to backup/restore and then go to nandroid backup (this is also how you would restore any of your back ups).
as far as returning to stock. If you didn't make a backup before you flashed fresh then you need to download the stock RUU file here.
BTW help support flipz and what he does for us, visit his site and click on the adds.

2.1 official release for rooted users?

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

Bought N1 on eBay - how to "unroot?"

Yes, I know. Why do I want to unroot? Well, the AT&T Nexus One is stuck on 2.1 update 1 and the baseband of the phone is unlocked.
How can I return to bone stock so that I receive all OTA updates. I'm good with what google pushes out and really don't want to fool with homebaked updates.
Thanks!
Read my signature, follow "unroot/restore" guide.
Your bootloader has been unlocked, not baseband. So follow the guide for unlocked bootloader. Use FRG83G ROM straight from HTC.
Thanks. Doing this now.
Actually, do I just follow the "fastboot" method and that's it?
Yes. Having unlocked bootloader makes things easier...
Jack_R1 said:
Yes. Having unlocked bootloader makes things easier...
Click to expand...
Click to collapse
How so? I'm not really certain I am good with the method in the FAQ. I'm not familiar with adb and fastboot. In fact, I have no idea how to do these methods.
I am googling and reading as much as I can, but it's a bit intimidating. Any video walkthrough or idiot proof document that shows exactly what to type, etc?
Sorry, I'm just not as into this as most here (but I'm very eager to learn).
ericshmerick said:
How so? I'm not really certain I am good with the method in the FAQ. I'm not familiar with adb and fastboot. In fact, I have no idea how to do these methods.
I am googling and reading as much as I can, but it's a bit intimidating. Any video walkthrough or idiot proof document that shows exactly what to type, etc?
Sorry, I'm just not as into this as most here (but I'm very eager to learn).
Click to expand...
Click to collapse
Try and follow these instructions, I think it may be the easiest way for a beginner. It doesnt unlock boot loader but it roots your phone and gets 2.3 on it. Good luck
http://forum.xda-developers.com/showthread.php?p=11087674#post11087674
arastamon said:
Try and follow these instructions, I think it may be the easiest way for a beginner. It doesnt unlock boot loader but it roots your phone and gets 2.3 on it. Good luck
http://forum.xda-developers.com/showthread.php?p=11087674#post11087674
Click to expand...
Click to collapse
Thanks.
The phone I have already has an unlocked boot loader (there is an "unlocked" lock image below the nexus image upon reboot).
I believe returning to stock is as easy as downloading a factory N1 image, re-naming it to update.zip (or is it passimg.zip?) and running it from the boot loader...right?
I'm actually afraid to do this for fear of bricking this thing. All I want to do is go to a stock version of Android from the current 2.1-update1 Build EPE54B rom that came with this N1 so I can OTA up to the current 2.2.2 (or whatever) official google version is out. I'd like to go OTA from here on out, which the phone will not do now (stuck on 2.1 and saying "your software is up to date").
Is it as easy as what I suggested or am I a mega-noob?
Sorry for giving you the wrong info, I miss read the thread. I havent ever unrooted would hate to give you the wrong advice on the proccess. Sorry Im not more help
Since you are rooted and nervous about bricking your phone you can do this.
Flash a custom recovery if there is not one already on the phone via rom manager. Then in rom manager back up your rom (nandroid) . There is even a stock rom in rom manager that you can download and install all in rom manager. That will put the default recovery back as well. The phone will then the OTA's to the latest one.
Or you can just flash any other rom etc. It is really hard to actually brick the phone.
Sent from my Nexus One using XDA App
Thanks. Downloaded the Rom Manager, and guess what? The phone isn't rooted (I don't know anything about it .... just received it used from eBay).
The boot loader is definitely unlocked though and it's stuck on 2.1.
I will figure out the one-click root and go from there. Is that the best advice?
ericshmerick said:
Thanks. Downloaded the Rom Manager, and guess what? The phone isn't rooted (I don't know anything about it .... just received it used from eBay).
The boot loader is definitely unlocked though and it's stuck on 2.1.
I will figure out the one-click root and go from there. Is that the best advice?
Click to expand...
Click to collapse
I would go that route if I was you. It is very quick and simple and noob friendly. You could also use the guides the other posters put up to learn some things as well.
Not sure why your phone is "stuck" at 2.1 in the first place. But yeah rooting/rom manager should do the trick quickly and easy.
Turns out I was able to install superuser, so it's rooted. Not sure why Rom manager complained about it not being rooted.
This is a pain in the ass so far. I will just try to flash to a ~light~ 2.3 ROM. Don't want a bunch of battery draining stuff. Recommendations?
Also, I still want to go to bone stock so I can get google OTAs. Oh well. Maybe I'll figure it out one day.
ericshmerick said:
Turns out I was able to install superuser, so it's rooted. Not sure why Rom manager complained about it not being rooted.
This is a pain in the ass so far. I will just try to flash to a ~light~ 2.3 ROM. Don't want a bunch of battery draining stuff. Recommendations?
Also, I still want to go to bone stock so I can get google OTAs. Oh well. Maybe I'll figure it out one day.
Click to expand...
Click to collapse
The 2.3 ROMs aren't really "ready" yet, and I don't know if I would really recommend them to a new user. Very buggy. If you can get ROM Manager to work (which should be as easy as installing it from the Market if you have root), then go to "Download ROM" and find your way to CyanogenMod 6.1.1. It will ask you if you want to install gapps as well, and you should select yes.
Once a phone has been unlocked and had custom roms installed on it, there's no way to ever go back to completely stock with OTA updates unfortunately. CyanogenMod is probably the cleanest and most supported rom you can find, but another would be Enomther's (http://forum.xda-developers.com/showthread.php?t=614427).
PrawnPoBoy said:
The 2.3 ROMs aren't really "ready" yet, and I don't know if I would really recommend them to a new user. Very buggy. If you can get ROM Manager to work (which should be as easy as installing it from the Market if you have root), then go to "Download ROM" and find your way to CyanogenMod 6.1.1. It will ask you if you want to install gapps as well, and you should select yes.
Once a phone has been unlocked and had custom roms installed on it, there's no way to ever go back to completely stock with OTA updates unfortunately. CyanogenMod is probably the cleanest and most supported rom you can find, but another would be Enomther's (http://forum.xda-developers.com/showthread.php?t=614427).
Click to expand...
Click to collapse
Thanks. Well, I'm a total idiot. My passion.zip was passion.zip.zip. Nonetheless, the FAQ .zip original image file was "older than the currently installed version."
I'm done. I'm just going to play in the rooted 2.3 world. Currently downloading CyanogenMod's latest nightly for passion.
So, I am curious. Does this file I'm downloading update the radio and everything else? I'm certain the firmware versions for the radio, etc, are outdated.
Thanks.
EDIT: On second thought, is there a large reason not to go with a nightly? The latest stable version is two months old...I want clean and fast with minimal battery drain, etc.
You can always go back to stock and get the OTAs from Google. Only thing you can't do is relock the bootloader. ALWAYS can do it.
Sent from my Nexus One using XDA App
ericshmerick said:
EDIT: On second thought, is there a large reason not to go with a nightly? The latest stable version is two months old...I want clean and fast with minimal battery drain, etc.
Click to expand...
Click to collapse
The only reason not to go with the nightly build is stability. CM7 isn't ready for general use yet, and there are a lot of problems still. Last time I used it the phone app was almost completely unusable and would lock up whenever someone called. It doesn't hurt to try it out though. You can always flash something else if it's not stable enough for you.
albundy2010 said:
You can always go back to stock and get the OTAs from Google. Only thing you can't do is relock the bootloader. ALWAYS can do it.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Nope, this isn't true. Once the signed boot loader is replaced, there's no more OTA's. You can get the notification that an update is available, but they wont install. Once the clockwork or ra_recovery are installed, OTAs will never work again. There is currently NO way to go back to 100% stock on a Nexus One.
Jesus. I'm going to jump off a bridge.
I successfully installed the STABLE CM6 update (radio update, google apps). My GD N1 keeps rebooting.
WHERE can I find a stable 2.2.2 or 2.2.1 stock ROM and end this madness. All I want to do is use this phone. It's currently possessed.
(I'm beginning to think it's defective...)
ericshmerick said:
Jesus. I'm going to jump off a bridge.
I successfully installed the STABLE CM6 update (radio update, google apps). My GD N1 keeps rebooting.
WHERE can I find a stable 2.2.2 or 2.2.1 stock ROM and end this madness. All I want to do is use this phone. It's currently possessed.
(I'm beginning to think it's defective...)
Click to expand...
Click to collapse
its not defective and at this point its just a matter of time until you fix it.
If you still want to be stock, ignore below and follow the links to restoring the stock rom above.
a) do you have a custom recovery installed? (i.e a nice navigable menu) if not flash one from a terminal/shell (on your desktop) in fastboot mode (power+trackball to start the phone, choose fastboot)
b)since you dont have much to lose, wipe everything after rebooting into recovery mode.
c)flash any ROM that works with your phone. (the LCD nexus ones need a different version I think)
When you install a stock rom it overwrites the custom recovery everytime it boots. It always does this. The unlocked boot loader is irrelevant the OTA's.
He or anybody else can flash a stock rom and get the ota.
Sent from my Nexus One using XDA App
ericshmerick said:
Jesus. I'm going to jump off a bridge.
I successfully installed the STABLE CM6 update (radio update, google apps). My GD N1 keeps rebooting.
WHERE can I find a stable 2.2.2 or 2.2.1 stock ROM and end this madness. All I want to do is use this phone. It's currently possessed.
(I'm beginning to think it's defective...)
Click to expand...
Click to collapse
Try this: http://www.shipped-roms.com/downloa...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip

Rooting With The 2.3 O.T.A. Update

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.

How much do I need to reset to stock before taking it into the store?

My HTC Evo Shift's touch screen stopped working partially.
Above 70% of the screen won't work vertically anymore. (Horizontal is fine).
I am going to take it into the store.
Do I need to get rid of everything including root and recovery?
What will they check?
nullstring2 said:
My HTC Evo Shift's touch screen stopped working partially.
Above 70% of the screen won't work vertically anymore. (Horizontal is fine).
I am going to take it into the store.
Do I need to get rid of everything including root and recovery?
What will they check?
Click to expand...
Click to collapse
Never take a Device in for service while Rooted. Some Techs will check, others will not. But if they do find that it's Rooted they can flag your account. Not what you want . Also they may try and say that the issue is because you rooted your device. If you are going to RUU I would use the RUU HERE. That way it will be easier to re-root your device afterward. One question, did you Update your Radio's and Touchscreen Firmware yet?
Why will it be easier to root my device?
Do I need to flash stock recovery? Or will they not check for this?
It will be easier to Re-Root your device if you RUU to 2.2, as opposed to 2.3.4 . Mostly because there are less steps involved. Once you RUU it will take the device to Factory fresh out of the box. Stock everything.
You don't think they'll be suspicious that I am still running froyo?
I am thinking about just calling sprint instead and seeing if they'll agree to do a replacement ahead of time. In that case, I can just RUU to 2.3.4 and not care since I'm not getting it back.
It depends on the Tech. Some techs don't care, as long as the device is not Rooted. Some may ask, but you just tell them you've never taken an Update. Calling Sprint ahead of time will most likely not do anything. They're going to want to check the device anyway. You can RUU to 2.3.4 then re-root later. It will just take a few more steps.
TEAM MiK
MikROMs Since 3/13/11
nullstring2 said:
You don't think they'll be suspicious that I am still running froyo?
I am thinking about just calling sprint instead and seeing if they'll agree to do a replacement ahead of time. In that case, I can just RUU to 2.3.4 and not care since I'm not getting it back.
Click to expand...
Click to collapse
Yes, majority of the techs will be suspicious about you being on froyo... Android users are anal about their ota updates and very few users skip ota updates except rooted users... I state this from experience, as I brought in a shift unrooted on froyo a few months ago and than ended up at sprint for over an hour answering their questions... I got my replacement device but I will NEVER bring in a device not running the latest firmware...
Sent from my PG06100
In my experience it depends where you take it to have it serviced. If you go to a Corporate store, they check out stuff a lot more. But the up side is they are quicker to resolve an issue. The privately owned stores usually do not check the device out that in depth. If they can't fix the issue immediately, they usually just give you some options about getting another.
prboy1969 said:
In my experience it depends where you take it to have it serviced. If you go to a Corporate store, they check out stuff a lot more. But the up side is they are quicker to resolve an issue. The privately owned stores usually do not check the device out that in depth. If they can't fix the issue immediately, they usually just give you some options about getting another.
Click to expand...
Click to collapse
I agree... The stores around my area are all corporate...
Sent from my PG06100
So, where do I get the stock 2.3.3 (or 2.3.4) RUU or zip file?
I can only find the 2.2 version.
Just run the exe then do the software upgrade
Sent from my PG06100 using Tapatalk 2
Thats kind of a pain.
I used http://goo.im/stock/speedy/ruu/PG06..._1.88_0128_PRL60674_release_196686_signed.zip
However, after it updated to S-ON, it says "Main Version is older! Update fail"
Do I need to use the 2.2 RUU?
EDIT:fastboot getvar version-main
2.77.651.3
Hrm. Did I screw up here?
Can I still use the 2.2 RUU?
Do I need to use the downgrade techniques to get it to downgrade?
EDIT2: I flashed the misc.img in order to trick hboot into installing 2.3.4 stock.
I'm not sure if I was suppose to have to do that.. but whatever, it worked.
nullstring2 said:
Thats kind of a pain.
I used http://goo.im/stock/speedy/ruu/PG06..._1.88_0128_PRL60674_release_196686_signed.zip
However, after it updated to S-ON, it says "Main Version is older! Update fail"
Do I need to use the 2.2 RUU?
EDIT:fastboot getvar version-main
2.77.651.3
Hrm. Did I screw up here?
Can I still use the 2.2 RUU?
Do I need to use the downgrade techniques to get it to downgrade?
EDIT2: I flashed the misc.img in order to trick hboot into installing 2.3.4 stock.
I'm not sure if I was suppose to have to do that.. but whatever, it worked.
Click to expand...
Click to collapse
Wait . What are you trying to accomplish? I thought you wanted to take it in for service. If you still want to take it in just run the 2.3.4 .exe RUU I've attached below. It will Update your device to 2.3.4 ,and done . Then you can take it in for service.
2.3.4 SPEEDY GB .exe RUU
prboy1969 said:
Wait . What are you trying to accomplish? I thought you wanted to take it in for service. If you still want to take it in just run the 2.3.4 .exe RUU I've attached below. It will Update your device to 2.3.4 ,and done . Then you can take it in for service.
2.3.4 SPEEDY GB .exe RUU
Click to expand...
Click to collapse
I already got it flashed... so the issue is solved.
But, are you sure just using the RUU will work?
I was having issues because I was trying to install 2.76 "main-version" when the installed version was 2.77 or something, and it wouldn't let me downgrade.
As far as I understand both the file I linked and the one you posted validate against the version.
Therefore, I had to flash the misc.img for the TB (like you do to downgrade to 2.2), and then i was able to do it fine.
Glad you got it sorted. Yes, any of the Speedy RUU's should work. So long as you are Fully Rooted ( S-OFF ). If not then you can only Upgrade RUU.
TEAM MiK
MikROMs Since 3/13/11
prboy1969 said:
Glad you got it sorted. Yes, any of the Speedy RUU's should work. So long as you are Fully Rooted ( S-OFF ). If not then you can only Upgrade RUU.
Click to expand...
Click to collapse
I see. The issue with the PG06IMG is that the first thing it does is flash the bootlooder to S-ON, and then you can only upgrade.
Thank goodness for that TB misc.img exploit!
Could have really screwed myself over there. I'll have to be more careful in the future.
Always here to help
Where's the RUU for 2.2? Prboy, the link you posted was for 2.3 if its possible, can some post a link for 2.2? I tried searching but didn't find it. I'm on mobile so that's why
Shifted from my EVO
Enraged21 said:
Where's the RUU for 2.2? Prboy, the link you posted was for 2.3 if its possible, can some post a link for 2.2? I tried searching but didn't find it. I'm on mobile so that's why
Shifted from my EVO
Click to expand...
Click to collapse
No worries . What your looking for is HERE.
prboy1969 said:
No worries . What your looking for is HERE.
Click to expand...
Click to collapse
You're the man... Appreciate it
Shifted from my EVO

Categories

Resources