Downgrading Froyo 2.2 to 2.1 Eclair - Nexus One General

You might think i'm crazy, but i'm dependent on CoPilot Live for Android, a navigation app, and it doesn't work in 2.2.
So is there a way to go down to 2.1 again? (preferrably without rooting)
would it be possible to just take a "update.zip" from 2.1 and follow the same steps like i recovered to 2.2?
any input is appreciated

You can only go backwards if you've unlocked the bootloader.

Shouldn't he be able to use the signed release image in fastboot?

Nope, it wont let you go backwards.

Are you sure that it doesn't work? What if you connect your phone and download the original rom and use Fastboot to flash this rom would you need an unlocked bootloader?
Greez

Need to be unlocked.

AFAIK using a PASSIMG should do the trick, you'll have to go through the upgrade process too to get to 2.1.
SC

You cannot go backwards with a stock bootloader, how many times do I have to say it?

creepinshadow said:
You might think i'm crazy, but i'm dependent on CoPilot Live for Android, a navigation app, and it doesn't work in 2.2.
So is there a way to go down to 2.1 again? (preferrably without rooting)
would it be possible to just take a "update.zip" from 2.1 and follow the same steps like i recovered to 2.2?
any input is appreciated
Click to expand...
Click to collapse
Does CoPilot not work at all, or is it just not available on the Market? If it's not available, you can find a phone that it works on and is rooted and do an "adb pull" of the application file, then place the file on your phone's SD card and install with a task manager.

ScaredyCat said:
AFAIK using a PASSIMG should do the trick, you'll have to go through the upgrade process too to get to 2.1.
SC
Click to expand...
Click to collapse
See. That's what I was thinking. I thought the signed image would just flash all contents, regardless of the version. . .that's how we gained root on G1s (flashed down to rc29). Pretty sure it related the radio too.

Mi|enko said:
See. That's what I was thinking. I thought the signed image would just flash all contents, regardless of the version. . .that's how we gained root on G1s (flashed down to rc29). Pretty sure it related the radio too.
Click to expand...
Click to collapse
We don't have an NBH file like the RC29 file was. Until you unlock the bootloader, you can only flash the phone using the stock recovery, and it has to be a signed update zip, and it won't let you go backwards.

creepinshadow said:
You might think i'm crazy, but i'm dependent on CoPilot Live for Android, a navigation app, and it doesn't work in 2.2.
So is there a way to go down to 2.1 again? (preferrably without rooting)
would it be possible to just take a "update.zip" from 2.1 and follow the same steps like i recovered to 2.2?
any input is appreciated
Click to expand...
Click to collapse
I have the same concern too with 2.2 and CoPilot. The CoPilot guys said they are currently working on a fix, so I would just wait a bit longer.
If you need GPS right away, then in the meantime just use the Google Maps Navigation or Brut.all's latest version of the hack that works for non-US and non-UK countries.. works fine in Canada for me.

So there's no way to go back to 2.1 at all? Cause that's definitely something I want to do. My battery life (since having 2.2) is HORRENDOUS. Absolutely terrible. I can't deal with it right now.

You have to unlock the bootloader to go back.

Rusty! said:
You have to unlock the bootloader to go back.
Click to expand...
Click to collapse
Any chance you can tell me how to do that? Does that involve rooting?

No, but it is a prerequisite of rooting.
There's a bunch of guides on here though, can explain it miles better than I could.

itslinx said:
Any chance you can tell me how to do that? Does that involve rooting?
Click to expand...
Click to collapse
Do a search there is a tut.
AND I AM BACKING HIM UP...FOR THE LAST TIME YOU HAVE TO UNLOCK THE BOOTLOADER TO REVERT BACK TO 2.1

Thanks to both of you.

For everyone's information, the latest version of copilot also does not work with CM5.0.7 on Dream, however an older version, 8.0.0.606 *does work*. In case the same glitch is hitting them both, you might consider trying the older version with 2.2.
Also, please post the "logcat" for when it crashes.

Is there truly NOBODY interested in trying this?

Related

Full Revert from DamageControl2.0

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

Un-Root my Hero

I need to take my Hero back to factory specs because I'm taking it into a sprint store tomorrow. What all do I need to do... should I just flash my original rom back on there or can I download a rom from htc and it will clear everything? I understand I need to flash a new recovery image too.
Thanks
oh also, I'm running FreshRom.
nautical34 said:
I need to take my Hero back to factory specs because I'm taking it into a sprint store tomorrow. What all do I need to do... should I just flash my original rom back on there or can I download a rom from htc and it will clear everything? I understand I need to flash a new recovery image too.
Thanks
oh also, I'm running FreshRom.
Click to expand...
Click to collapse
You can flash the original rom back on there and be fine. They wont EVER press Home+power and boot into recovery.
If you really want to go back to default.. Run this RUU
http://outboundlink.us/anxo/dr_ta_1.../2uQunBaV/RUU_Hero_C_Sprint_2276515_R_si.html
Running the sprint 2.1 update will un-root your phone.
Sent from my HERO200 using XDA App
neuro_genesis said:
Running the sprint 2.1 update will un-root your phone.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Its not the sprint update.. thats the .5 ruu
Thanks for the link, that worked out great!
Jus10o said:
Its not the sprint update.. thats the .5 ruu
Click to expand...
Click to collapse
Actually newest ruu is .6 I think
after you run this can you re-root?. im new to android and i want to be able to restore to factory settings whenever after root just so i can re-root and practice it, as well as know how to fix it if i do something stupid or just brick the darn thing.
like i said im new and not good with forums where can i get a copy of the original rom? i would like to have that before i attempt to root.
also kinda off topic but do i have to be rooted to make nanoid backup. i would also like to have that before i root.
proman95 said:
after you run this can you re-root?. im new to android and i want to be able to restore to factory settings whenever after root just so i can re-root and practice it, as well as know how to fix it if i do something stupid or just brick the darn thing.
like i said im new and not good with forums where can i get a copy of the original rom? i would like to have that before i attempt to root.
also kinda off topic but do i have to be rooted to make nanoid backup. i would also like to have that before i root.
Click to expand...
Click to collapse
Yes you can re-root after running the .5 RUU
the original rom is contained in the RUU program linked above
You don't have to be rooted to make a nandroid backup, though you do need to flash a custom recovery image. Being rooted means that you basically have administrator access on your phone, can run things like wifi tether and can overwrite the /system/ folder. A recovery image is a little different than that...
ok thanks, i know root is just admin, but a lot of root guides have you flash a recovery image, by doing that you replace the original recovery image? the one that takes you back to factory reset? thats what im not sure about and im really nervous about changing that and messing it up and bricking my device, thought one forum said its almost imposable to brick.
ok so i have that RUU and another one i download. do i just run it or do i need to have a specific program on my pc?
i know i need to Google it and just search the forums but i don't have a lot of time on my hands right now.
If you're planning on going back to root, don't run the .6 RUU. I don't think it's rootable. At least that was the case when it came out. .5 IS rootable.
vidsid said:
If you're planning on going back to root, don't run the .6 RUU. I don't think it's rootable. At least that was the case when it came out. .5 IS rootable.
Click to expand...
Click to collapse
how do you determine what version the RUU is?
proman95 said:
i know i need to Google it and just search the forums but i don't have a lot of time on my hands right now.
Click to expand...
Click to collapse
I am seriously sure it wouldn't hurt to type a couple words into a search query, right? At least people helped you out though. Good luck!
Sent from my HERO200 using XDA App
proman95 said:
how do you determine what version the RUU is?
Click to expand...
Click to collapse
Menu - settings - about phone - software information - software number.
If it is .6, who cares. You can get root by going to the development section and finding the root guide written by regaw_leinad, and the solution for software number .6 is in there, too. Dunno why people make it out to be such a bad thing to have .6... seriously.
Sent from my HERO200 using XDA App
jerry43812 said:
Menu - settings - about phone - software information - software number.
If it is .6, who cares. You can get root by going to the development section and finding the root guide written by regaw_leinad, and the solution for software number .6 is in there, too. Dunno why people make it out to be such a bad thing to have .6... seriously.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Well you still can't root .6 but all you need to do is flash .5. So yeah I don't know why people are making a big deal either
Sent from my HERO200 using XDA App
Exactly. .6 isn't rootable yet but you are losing nothing by flashing back to .5 except for the patch they released to fix root exploit. What a waste of time for them.
cp0020 said:
Well you still can't root .6 but all you need to do is flash .5. So yeah I don't know why people are making a big deal either
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Sent from my HERO200 using XDA App
jerry43812 said:
I am seriously sure it wouldn't hurt to type a couple words into a search query, right? At least people helped you out though. Good luck!
Click to expand...
Click to collapse
thats the thing though most of my search's come up with nothing or so much stuff that its all over the place and dose not help at all, believe me I am trying. I am vary interested in learning as much as i can so when I have to to root/ or flash i can do it easily.
(thats why I don't post that much, I am trying not to sounds like an idiot, thought i probably already have)
jerry43812 said:
Menu - settings - about phone - software information - software number.
Click to expand...
Click to collapse
But thats after you run the RUU.exe I meant how do you know what version of the RUU.exe coincides with what version of the software with out installing or running it. I am still a little confused on what I need to do with the RUU.exe and or what it dose. I have been searching the forums but there is not a Good sticky or wiki about it, its only the definition. I am assuming it re-installs a fresh copy of whatever that version of the OS is, but i don't know for sure.
jerry43812 said:
If it is .6, who cares. You can get root by going to the development section and finding the root guide written by regaw_leinad, and the solution for software number .6 is in there, too. Dunno why people make it out to be such a bad thing to have .6... seriously.
Click to expand...
Click to collapse
sorry I am such a noob and thanks for the help but i just want to clarify that .6 stands for 1.6 or donut?
-Thanks for helping the noob!!!
2.27.651.5 is the original Hero update.
2.27.651.6 is the update that was released solely to disable the ability to root.
The RUU for each was released by Sprint/HTC and flashed your phone from 1.5 to 2.whatever.
If you root, then you can run any of these to revert back to the stock Sprint image. If you chose to go to 2.27.651.6 then the only way to re-root would be to flash back to 2.27.651.5 which would only be a pain in the bum.
Since 2.27.651.6 gives you nothing but the inability to root then it only makes sense to revert to .5.
If this makes no sense to you...feel free to give up on rooting altogether. If it does then good luck.
BTW I only figured out how to root on Monday so these forums are most excellent..if you take the time to search through them.
Thanks its starting to make sense, right now I'm software 2.1 update 1 or 2.6 so i just have to go back to 2.5 . once i have more time i will thanks for the explanation! yes this site is the best and yes i need to search more.

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