Develop Bugs

HELP!!: OTA (1.47) wanting to install upon boot!!

ok, i thought the 1.47 OTA would download to my sdcard...it didn't. But i wasn't quite convinced it was on the device so i clicked "install update" w/ the sd card pulled...as soon as it began i pulled the battery. Now, whenever i boot it automatically goes straight to the black update screen (with the hard drive icon) trying to install the OTA !!!
How can i stop this and boot normally back into 1.32??? w/o forcing the 1.47 update!!
(i am unrooted btw) THANKS FOR ANY TIPS!!

adeyo said:
ok, i thought the 1.47 OTA would download to my sdcard...it didn't. But i wasn't quite convinced it was on the device so i clicked "install update" w/ the sd card pulled...as soon as it began i pulled the battery. Now, whenever i boot it automatically goes straight to the black update screen (with the hard drive icon) trying to install the OTA !!!
How can i stop this and boot normally back into 1.32??? w/o forcing the 1.47 update!!
(i am unrooted btw) THANKS FOR ANY TIPS!!
Click to expand...
Click to collapse
I could be wrong but i dont think there is a way to stop it if unrooted. in good news even if you let it update to 1.47 you can still root (just dont go to 2.2) so not sure why you would want to stay at 1.32

omegasun18 said:
I could be wrong but i dont think there is a way to stop it if unrooted. in good news even if you let it update to 1.47 you can still root (just dont go to 2.2) so not sure why you would want to stay at 1.32
Click to expand...
Click to collapse
thanks. i hadn't backed up everything yet. also, i had unrevoked so i hope this doesn't drop my pri down to 1.32 from 1.40 (i guess i lose free tethering too)...other than those things, i was just about to root and get froyo!
so, you don't think i can boot into recovery and wipe something before it completely installs upon reboot??

adeyo said:
thanks. i hadn't backed up everything yet. also, i had unrevoked so i hope this doesn't drop my pri down to 1.32 from 1.40 (i guess i lose free tethering too)...other than those things, i was just about to root and get froyo!
so, you don't think i can boot into recovery and wipe something before it completely installs upon reboot??
Click to expand...
Click to collapse
Not without root. Whatever is trying to run is almost certainly on /system, which is not writable without root access. Just let it go and root after that.
Also, NEVER PULL THE BATTERY WHILE THE SYSTEM IS FLASHING! That's a real good way to end up with a half-written (bricked) ROM.

Just let it update to 1.47 and then use Simple Root or whitslacks method to gain root again. Then flash back to 1.32 if you so desire. As mentioned before, do not allow it to update to 2.2 as there is not yet a method to gain root for the OTA 2.2.
Furthermore, check the dev forum for the PRI issue. They need someone with an unrooted OTA 1.47 with a PRI 1.40_003. You could be everyone's hero.
Sent from my PC36100 using XDA App

SilverZero said:
Not without root. Whatever is trying to run is almost certainly on /system, which is not writable without root access. Just let it go and root after that.
Also, NEVER PULL THE BATTERY WHILE THE SYSTEM IS FLASHING! That's a real good way to end up with a half-written (bricked) ROM.
Click to expand...
Click to collapse
wow...thanks!!! i hope i didn't screw anything up! i'm letting it finish up now...EHHH...THIS IS WIERD??? this time i was just going to let it flash and so i went ahead and plugged in my usb, but instead of flashing it went to the boot animations and back to my phone????...i'll check to see if i screwed anything up??
**EDIT: wow, it prompted me to install the update again, looks like i am back. I will try cancelling installation this time... (it gives me a discard update option) i click yes, it says "this will wipe the update from your phone" ....so I guess all is well!!!!

adeyo said:
wow...thanks!!! i hope i didn't screw anything up! i'm letting it finish up now...EHHH...THIS IS WIERD??? this time i was just going to let it flash and so i went ahead and plugged in my usb, but instead of flashing it went to the boot animations and back to my phone????...i'll check to see if i screwed anything up??
Click to expand...
Click to collapse
It probably tried to flash, found nothing there, and removed the instructions from the boot process. So you may have gotten away with it. Check your software version in Settings - About Phone to see where you ended up. Also, is your SD card still out of the phone? It may be waiting to spring back on you when you put it back in, but just let it go anyway if that's the case.

sombdy said:
Just let it update to 1.47 and then use Simple Root or whitslacks method to gain root again. Then flash back to 1.32 if you so desire. As mentioned before, do not allow it to update to 2.2 as there is not yet a method to gain root for the OTA 2.2.
Furthermore, check the dev forum for the PRI issue. They need someone with an unrooted OTA 1.47 with a PRI 1.40_003. You could be everyone's hero.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
everyone's hero?? haha...that PRI thread is why i was trying to download the 1.47 OTA in the first place anyway, i am still at 1.32 now. do you have a tip as to how i can help them??

SilverZero said:
It probably tried to flash, found nothing there, and removed the instructions from the boot process. So you may have gotten away with it. Check your software version in Settings - About Phone to see where you ended up. Also, is your SD card still out of the phone? It may be waiting to spring back on you when you put it back in, but just let it go anyway if that's the case.
Click to expand...
Click to collapse
ahh...maybe you are right? maybe it was a phantom flash anyway b/c i never put my sd card back in, also, i did delete that update.zip that was on there anyway...so i'll see if anything happens when i put the card back in. my settings show 1.32 still
**UPDATE: no attempt to reload/reboot system with update after sd card is in. Looks good!

Then you're the **** of the walk!

now, should i root and then go straight to 2.2 or go to 1.47 first?? what is the best way to keep my PRI 1.40_003 intact????

adeyo said:
now, should i root and then go straight to 2.2 or go to 1.47 first?? what is the best way to keep my PRI 1.40_003 intact????
Click to expand...
Click to collapse
I don't think you can, that's why there's a bounty out for it. When you root, your PRI will change to 1.34 because you have to use the engineering ROMs. Correct me if I'm wrong.
You don't want to just upgrade to 2.2 OTA . . . unless you WANT to block root until somebody finds a way to root Froyo on the Evo.
PRI aside, you should probably root from 1.32, no reason to go up through 1.47 and you'll avoid the "Main Version is Older" problem.

SilverZero said:
I don't think you can, that's why there's a bounty out for it. When you root, your PRI will change to 1.34 because you have to use the engineering ROMs. Correct me if I'm wrong.
You don't want to just upgrade to 2.2 OTA . . . unless you WANT to block root until somebody finds a way to root Froyo on the Evo.
PRI aside, you should probably root from 1.32, no reason to go up through 1.47 and you'll avoid the "Main Version is Older" problem.
Click to expand...
Click to collapse
great, thanks! i will root and go straight to 2.2. I guess there is no known way to keep PPI 1.4 and actually root. ...it just gets to me that unrevoked users can keep PRI 1.40 and full rooters can't...there should be some way!

adeyo said:
great, thanks! i will root and go straight to 2.2. I guess there is no known way to keep PPI 1.4 and actually root. ...it just gets to me that unrevoked users can keep PRI 1.40 and full rooters can't...there should be some way!
Click to expand...
Click to collapse
I wasn't aware of that, but the reason is probably that Unrevoked users can't flash any ROMs that would update the PRI anyway.

SilverZero said:
I wasn't aware of that, but the reason is probably that Unrevoked users can't flash any ROMs that would update the PRI anyway.
Click to expand...
Click to collapse
oh...what ROMs wouldn't update the PRI? My friend is an unrevoked 2?3? user and i know he has tried a few different ROMs ...one of them being DamageControl, most recently. He has also tried a few different kernels.
***EDIT: Here are the steps he took:
1) Started w/ Unrevoked 1
2) OTA'd 1.47
3) Unrevoked 3 from 1.47 (then was able to flash froyo rooted roms
4) He still doesn't have nand access, but he flashed the following roms: Fresh (most recent), Burnt Droid, the odexed Stock "FINAL" by netarchy, and DamageControl. Burnt droid didn't take, but neither did DamageControl at first, but now works fine. His recovery is ClockworkMod.

[Q] Getting ready for Ota

alrighty so here it is the ota is coming and i silly as i may be rooted like 3-4 days ago. i didnt take the time to s-off just got the custom recovery updated the radio to 2.05 and downloaded sky raider vanilla. hboot is .79.
now from my research that ive gather and correct me if im wrong but all i need to do is :
*s-off
*flash the stock recovery
after that i should be good for the ota correct?
so far i got the s-off done looking for a lil bit of instruction as to how to get the stock recovery flashed safely.
Any and all help is greatly appreciated i thank you all very much.

inessi said:
alrighty so here it is the ota is coming and i silly as i may be rooted like 3-4 days ago. i didnt take the time to s-off just got the custom recovery updated the radio to 2.05 and downloaded sky raider vanilla. hboot is .79.
now from my research that ive gather and correct me if im wrong but all i need to do is :
*s-off
*flash the stock recovery
after that i should be good for the ota correct?
so far i got the s-off done looking for a lil bit of instruction as to how to get the stock recovery flashed safely.
Any and all help is greatly appreciated i thank you all very much.
Click to expand...
Click to collapse
I have attached the stock recovery that needs to be flashed from the HBOOT.
It is my understanding however, that you need to downgrade to the .77 HBOOT, 1.xx radio AND 2.1 system for the update to notify you, give you the option to download, and install successfully. However, I am a few drinks into my night.
If you choose to follow that path. I suggest you read this

awesome stuff really appreciate it man gonna give it a try now, fellow floridian lol

inessi said:
awesome stuff really appreciate it man gonna give it a try now, fellow floridian lol
Click to expand...
Click to collapse
w00t!
If you get hung up anywhere, pm me and I'll give you a number to call me at in the morning/afternoon and I'll walk you through it.

your my hero bud, my freaking hero stock recovery got s-off i think thats all i need to recieve the ota and do it yea?

thnx
See, from this point, I'm not sure if you need the .77 HBOOT 1.xx Radio and 2.1build-1 on your phone (I'm really questioning it, as I beleive I read in a few places that you do, but I'm not sure at this point in the evening). I don't think the Skyraider rom will get a notification when the update is available. I'd say if you don't get a notification for the update when everyone else in the free world is, then you may have to.
As long as you have S-OFF, it doesn't matter either way, you have complete control for the rest of your phone's life. Whatever you do, don't turn it back on lol.

hmmm well if it doesnt show up guess my next set of questions is how to get back to stock everything

inessi said:
hmmm well if it doesnt show up guess my next set of questions is how to get back to stock everything
Click to expand...
Click to collapse
The link I posted above with the "I suggest you read this" line is where you will need to go if it boils down to that.

o haha some how i missed that lil section of text did you just add that recently?
but ok sounds good ill run through it in the morning probably

and holy crap the link you posted makes this all look so simple hah

Well I have stock everything, except for my hboot is .79, im on stock 2.1 stock recovery just have .79 hboot not .77, i think i will still get the update though...

rdmerck said:
thnx
See, from this point, I'm not sure if you need the .77 HBOOT 1.xx Radio and 2.1build-1 on your phone (I'm really questioning it, as I beleive I read in a few places that you do, but I'm not sure at this point in the evening). I don't think the Skyraider rom will get a notification when the update is available. I'd say if you don't get a notification for the update when everyone else in the free world is, then you may have to.
As long as you have S-OFF, it doesn't matter either way, you have complete control for the rest of your phone's life. Whatever you do, don't turn it back on lol.
Click to expand...
Click to collapse
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?

magneto417x said:
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
Click to expand...
Click to collapse
Other than the root, did you modify anything else to your phone?
If not, your still with the .77 HBOOT, 1.xx baseband, and 2.1update-1 system?
Add unrevoked forever to remove s-off, then flash the stock recovery back to your phone. Your goal here is to have S-Off

in order to get the OTA (from my understanding) you need the stock recovery, do a little search I have all the faith in the world that you will find what you are looking for. you want to run unrevoked forever BEFORE you accept the OTA2.2, so this is your steps, root, run unrevoked forever getting S-OFF, find the file for the stock recovery, PB..IMG file, flash that in hboot, this will set u back to stock 2.1 update1, stock radio, stock recovery, but still have S-OFF to regain root, after the OTA comes.

So if I have stock everything, and have hboot .79 will I still get the OTA I don't see why not...

BlazeD OnE said:
in order to get the OTA (from my understanding) you need the stock recovery, do a little search I have all the faith in the world that you will find what you are looking for. you want to run unrevoked forever BEFORE you accept the OTA2.2, so this is your steps, root, run unrevoked forever getting S-OFF, find the file for the stock recovery, PB..IMG file, flash that in hboot, this will set u back to stock 2.1 update1, stock radio, stock recovery, but still have S-OFF to regain root, after the OTA comes.
Click to expand...
Click to collapse
Currently the only thing I have done was rooted and removed CityID and but have not changed the radio or anything else. I have installed Unrevoked forever now. So do I still need to flash stock recovery even though I haven't changed the boot files or radio files at all?

Yes from what I've read you HAVE to have the stock recovery. what is your HBOOT once u get stock recovery?

BlazeD OnE said:
Yes from what I've read you HAVE to have the stock recovery. what is your HBOOT once u get stock recovery?
Click to expand...
Click to collapse
My HBOOT is 0.79.0000
Radio 1.00.03.04.06
Any input would be helpful as to whether I will get OTA or do I need to do something.

once in hboot, go to recovery, if you have clockwork you wont get it i dont think, if you get a red triangle you have stock recovery and you are good to go.

magneto417x said:
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
Click to expand...
Click to collapse
Yes, install unrevoked forever. The fact that you are rooted will not affect the ability of your upgrade, it is the lack of the stock recovery that will halt you.
Unrevoked forever will allow you to flash ANY zip file you want to the phone (namely a zip that has su and Superuser.apk) and will allow you to regain root in the event that it is ever lost due to an OTA or user error.
S-OFF is a beautiful thing.
I would love to take my phone to Verizon right now with a manufactured problem, let him see the Superuser, official 2.2 system and then stock recovery. Could be priceless!

GPS doesn't work after loading froyo

loaded the leaked froyo in rom form, but ever since then i can't get a pinpoint gps connection. i always get either the big blue circle or "searching for gps" when in navigator. i have since reverted back to 2.1, confirmed gps works. checked with a few other friends, not experiencing the issue. loaded froyo rom again, no restore of settings or user files, same issue existed. what would cause this? anyone else experience this? how can i fix it?
thanks

since you installed via a rom did you update your radio from 1.00? if you dont have atleast a 2.05 radio... but you should really have teh 2.15 radio alot of stuff wont work properly

two_cents said:
since you installed via a rom did you update your radio from 1.00? if you dont have atleast a 2.05 radio... but you should really have teh 2.15 radio alot of stuff wont work properly
Click to expand...
Click to collapse
that's prolly what it was. it totally slipped my mind! i'll try that and see if it helps. thanks...
btw, can i just use a restore and update the radio with that already restored file? what's the best practice for doing something like this?

patches152 said:
that's prolly what it was. it totally slipped my mind! i'll try that and see if it helps. thanks...
btw, can i just use a restore and update the radio with that already restored file? what's the best practice for doing something like this?
Click to expand...
Click to collapse
do you have unrevoked:forever? with s_off? you can't just flash a radio without it... you need to do that and search for the 2.15 radio file then flash it via Hboot... as a PB31IMG.zip file... dont be too hasty read the instructions and go slow and you should be fine

[Q] 2.2 OTA update issues

Hi guys,
I have a Desire I bought unlocked on eBay. Though initially thinking it was factory unlocked, and having bought it under that pretense, I now think it's been unlocked by some other means. It doesn't appear to be rooted, having no superuser app but I'm not sure how else it could have been unlocked? If any one can shed some light here, that would be great.
I received the OTA update tonight, and after downloading and resetting it simply wouldn't get past 90% on the install before resetting itself. After about 15 minutes I switched it off and switched it on again, and it booted into my homescreen, with a "loading" alert and a rotating circle, no percentage.
Eventually that stopped, and it looked like everything was ok. I checked the version and it said I was running 2.2. Awesome, so I go about my business and realise I have no 3G or wireless connections. I check the settings and under WiFi it says "error", and I can't enable it. My APN is gone too. I can get that online, but it seems like there's an issue with the radio so I haven't bothered. It doesn't connect to the network anyway. It also resets occasionally, it seems when it has to load SenseUI but I can't confirm this.
What could it be? I'm not sure where the phone came from. It's a Black a8181 model with the Orange case branding, but the OS is unbranded. The locale is English (Singapore/Taiwan/a few others), though I thought the Black model was only in the UK. I'm in Australia, on vodafoneAU.
Is there anything I can do?
Cheers guys, I really hope I haven't (basically) bricked it.

Firstly, removing the SIM lock from the phone has nothing to do with rooting. Usually, you just stick in an "incorrect" SIM, and it will ask for an unlock code which you can buy online.
Given that the OTA update was a patch, it sounds to me like you have a partially patched ROM and this is causing your problems.
However, since it basically boots up and works to a fashion, it isn't bricked and chances are it is fairly easily recovered.
IMHO, you have two options.
1. Install a 2.1 RUU to downgrade your phone.
2. Root the phone using UnreEVOked and load a custom 2.2 ROM.
Both of these should be quite easily so long as your previous attempt to upgrade hasn't already updated HBOOT.
Turn you phone off and then power on again whilst holding down the volume down button - your phone should boot into HBOOT.
Look for the HBOOT version on the second line and post back what it says here.
Regards,
Dave

You've received a branded phone that has been debranded (you should have been told this) - you can't upgrade these without a goldcard. What's happened is part of the upgrade has worked, but other parts failed.
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.

teppic74 said:
To recover you'll need a goldcard, which will be more difficult to make with the phone rebooting all the time.
Click to expand...
Click to collapse
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave

foxmeister said:
If the OP can get UnrEVOked running, and doesn't mind having a custom recovery image (good thing!), he/she shouldn't need a goldcard.
Regards,
Dave
Click to expand...
Click to collapse
That's true, though it does mean going down the custom ROM route, which might not be wanted.

Thanks guys, that's really good info.
I'm not too concerned about running custom ROMs, I've been thinking about doing it for a while, just don't know enough about how to root and flash. There are some good guides here, I'm just a bit nervous about doing it. I also don't know what the best ROM would be. I'm really just after a factory standard Desire with Sense ROM, the most out of the box it could be.
I assume an RUU is like a rollback? In which case, what would I be rolling back to. I have no idea how it was debranded, so I don't know what ROM I'd need to roll back to.
As for the goldcard, what would that do? Is that rolling back, or fixing what I have now? It doesn't crash too often, I can probably baby it through.
Sorry for the questions guys, just want to know my options. I didn't think it was too badly bricked, but you never know. I bricked my XDA Mini II trying to flash a new ROM, so you can see my hesitation :/

An RUU is an official way to flash the phone with HTC's own software. That is how the phone was debranded in the first place, and you can do the same to get it back to normal. It does require a goldcard though, which is a minor software patch on the sdcard.
If you root and install a custom ROM (and update the radio) you'll have a working phone again, and you can make a goldcard in your own time.

If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
foxmeister said:
Look for the HBOOT version on the second line and post back what it says here.
Click to expand...
Click to collapse
Hboot - 0.80.0000

papalazarou said:
If I go with an RUU, will OTA updates work? That's really the only thing I'd miss about a custom ROM, the convenience of OTA.
Hboot - 0.80.0000
Click to expand...
Click to collapse
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.

teppic74 said:
You'll get ota updates if you use an ruu. Just make sure you have your goldcard in when you apply them.
Click to expand...
Click to collapse
Cool, will the process in the link in your sig do the trick? And the goldcard, will I need to keep it in permanently, or only when updating? Trying to decide if I should use a dedicated card for it, or include it on the card I keep in there.
Thanks for the help, I'll run the RUU tomorrow morning.

I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.

papalazarou said:
I'm trying to run unrevoked to root and reflash it, but it get's to a point and fails, saying "failed to flash recovery image".
Any thoughts?
EDIT:
I've now created a goldcard and am trying the downgrade process in the link in your sig. I've followed all the instructions, but when I ran the downgrade util, after asking for my password, nothing happens.
Click to expand...
Click to collapse
Yeah, that's my fault for leaving a testing point in the Mac/Linux version of the utility. It was mentioned in the bugs section, but probably not made clear enough. It's fixed now.

[Q] Official Update Not Working

Hey guys, I should have posted this about a month (maybe even longer) ago, but I've been dealing with some health issues and couldn't be bothered. First off I have a rooted phone (with S-OFF) but I like keeping the stock sense build. I upgraded OTA to 2.2 some time ago, then there was an OTA update a few months after that (which I was able to install without any problems after I replaced a couple of files that had gotten modified), now this newer OTA update refuses to install.
It tells me it needs to reboot to start installing so I click the button to reboot and it counts down, but it never reboots. Is it somehow detecting that my phone is rooted? I would like to have the most up to date OTA update installed on my phone at all times so any help or ideas would be great (also I'm sorry if this has been covered before, I did search but I've been afk for a bit so I might have missed some things).
- DeeBG

Read this thread, it tells you how to get back to 2.2 stock, then download the latest Unrevoked to root again and obtain s-off...

RMarkwald said:
Read this thread, it tells you how to get back to 2.2 stock, then download the latest Unrevoked to root again and obtain s-off...
Click to expand...
Click to collapse
Blah I have to go back to 2.2 stock? Oh well, it's not the worse thing in the world (I already had to do it once) and those are great instructions (plus I've wanted to have the latest version of Clockworkmod installed for a while and using Unrevoked means I won't have to mess with the payload/su/etc files). Thanks!

I also thought of something (kind of late though). I was using a custom kernel, which might have been the issue too. But I went ahead and re-enabled S-On, however now for some reason my phone is checking for errors on my SD card (no idea how long it will take, or why it's doing that), but does anyone have a link for that 17.7mb file of the 3.26.605.1 update? I found the full RUU, but it's huge and I rather just upgrade than possibly wipe everything out (and I don't know when my phone will have the OTA ready again). Thanks for any help!

Is it necessary to update or downgrade then upgrade the OS?
sent from my Ultimate 2.33 Incredible

bigsapz said:
Is it necessary to update or downgrade then upgrade the OS?
sent from my Ultimate 2.33 Incredible
Click to expand...
Click to collapse
That seems to be what that linked thread says, but I don't believe that is correct (that's why I am looking for that 17.7mb OTA file). I was able to install the first 2.2 update (aka 2.2.1) without issue after I restored some files that were altered (either by rooting or installing the wireless tether app that's hosted on Google Code). However this OTA update (aka 2.2.2) isn't popping up again for me to install, so I am going to see if I can extract just the upgrade data from the official RUU. I have to wait until later tonight because I need my phone to be operational for another few hours but I'll post back with results (and files if need be =).

Yeah I tried the RUU update and as expected it did a total wipe... bringing back system via nandroid and will try something else.
Edit: http://forum.xda-developers.com/showthread.php?t=969973 <= using Jay's thread, which is much like the post that was first given to me in this thread. Not re-enabling S-ON seems to be the problem... lesson learned, don't try shortcuts unless you know what you are doing (and I've been afk from the "Dinc Scene" too long for that =p.
Edit 2: Up to date and 100% working!