Guys, I just have a question on the OTA update.
I have a stock unrooted N1 running ERE27 currently.
Got the OTA update 10 mins ago.
Clicked on 'Restart and Install'.
Then the phone came back up with the android robot and an exclamation mark on the screen (sorta like it is writing to system memory or something), but it stayed on that screen for 20 mins.
I panicked and removed the battery, now it is booted normally into 2.1 ERE27 again, has anybody seen this?
If it helps, my radio is: 32.24.00.22U_4.03.00.21_2
I hope I get the OTA message again. And if I do,
Should I wait longer this time? Is that normal?
Thanks in advance,
KG
I have exactly the same situation: I see that "android robot and an exclamation mark on the screen", but I'm still waiting for completetion of the update: nothing new happens for about 40 minutes...
BTW, when I first ran Froyo in emulator's "virtual device" two days ago, it didn't load at the first run. I had to turn the virtual device off. Second start was OK.
Update 1. I waited for an hour - nothing changed. No button worked, so I had to remove battery for some seconds. Assemlbed, turned on - I'm still having ERE27 working OK and "Your system is currently up to date" message in Settings->About phone->System updates
:-(
Update 2. I've opened an issue at googlecode: "Froyo OTA update freezes on Nexus One" (I will post a link when I have permission for this ;-) )
Update 3. Ten hours after first failed update I've got the same prompt. This time I was very careful to confirm update one once
...And this time the update succeeded!
Exactly the same happened to me, though i did not took out the battery, i pressed power & up instead, to get to the following screen:
Android System recovery <2e>
and the error message as below:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") =="google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys"
E: Error in /cache/signed-passion-FRF91-from-FRF50.836691a1.zip
(status 7)
Installation aborted
Any hints on what was wrong and what to do please?
Second trial was successful, so i advice users above to retry...everything went fine & now running on 2.2 ;-)
tiborakos said:
Second trial was successful, so i advice users above to retry...everything went fine & now running on 2.2 ;-)
Click to expand...
Click to collapse
You're lucky
How did you "retried"?
Did you receive second prompt for update or what?
Received second promt for update, 1-2 hours after rebooting from the first failed one.
Sure u will hv the same.
Then u see a small android with a pack & a bar below, 5 mins are ok to phone get back to where it was -apps & data all like they were- and 2.2 running...
Related
I had a small mishap with my G1, i out it in a wet cup holder and it got the bottom area of the phone wet (buttons/trackball area). I dried the phone out for a couple of days (used the rice method) and started it up...
The phone charges and powers on but I get the triangle with an exclamation mark icon. I've tried putting different firmware versions onto the SD card and naming them update then used the Alt+S and I get errors. I've tried probably around 40 different RC's ranging from RC 29 to God knows what...
an example of the errors I'm getting is:
E: Can't open /cache/recovery/command
--Install from sdcard....
Finding update package...
Opening update package...
Verifying update package...
Installing update....
E:Error in check_prereq (status 256)
E:Failure at line 1:
run_program PACKAGE:check_prereq 1242268990
Installation aborted
I would greatly appreciate any help with this! I NEED to fix this phone! Thank you in advance!
PS: sorry for posting this in the sticky thread, i did it by mistake while reading that thread!
I did not know there was 40 rc s, try getting yourself the rc29 dreaimg.nbh, do not rename to update.zip, put it on the root of your sd and enter the bootloader by pressing power and camera and see if that will load it
where can i download the rc29 dreaimg.nbh?
Check out one of the threads for rooting your phone, should find a good d/l there, it's the one that you use to downgrade your phone, you will lose root and have to unroot it the old fashioned way now
oh ok, thank you! my phone was never rooted so that's not an issue. i just need it up and running so i can live my life again... I'll give it a shot!
Well I hope it works for you, now would be a good time to think about rooting your phone since you will already have done the first step, if you want stock, you will have to wait for the ota updates which can take up to 72 hours to receive, so you will have none of the cupcake goodness like auto rotate or widgets. There is ways to get the update quicker but I am unaware of them
Download the RC29 dreaimg.nbh HERE.
Let us know if this flashes for you. Remember, you just put this file on the root of your SD card and enter bootloader by holding Power+Camera.
thank you for everybody's help, but i still haven't resolved the solution. i put dreaimg.nbh on the root of my SD, held camera and power. the G1 logo screen shows up, then the phone just goes back to the trianlge with the exclamation mark...
I was updating my firmware for the Galaxy S and it said something along the lines of not being able to be completed because I don't have 'rapi.dll', so naturally I downloaded that file and shoved it in the System32 folder. After doing so, it said in order for the changes to take effect I'd need to reboot. At first I was a bit iffy because Kies stated specifically not to disconnect etc during the process, but seeing as I had no choice I did so. After I rebooted, I tried to open Kies and it just kept coming up with "Mainstage has stopped working" and crashing. Right now, I've uninstalled Kies, downloaded the newest version from the site and installed it. It's opening fine, however it can't detect my phone and my phone is stuck on this screen: (because I'm a new user and can't post outside links, I'll just describe it)
(Little alien man in triangle sign digging... lol)
"Downloading... Do not turn off Target!!!"
Any help would be hugelyyyyyy appreciated, thank-you!
ok so here's what's going on. my g1 has been off and in storage for a month now because i had the mytouch 3.5mm. i figured maybe i can just use my g1 as a device for around the house. so i plug it in let it juice up unplug it and turn the power on. it goes past the g1 screen and directly to the yellow exclamation with the g1 in front.now i aint no newb. ive rooted my phone a couple times and know how to search the forums for help. so i tried to update it press alt+l the alt+w to wipe and also tried to wipe cache..then update from zip. it reads the update gets all the way to installing update and then just aborts the installlation. now ive tried multiple updates and it does it to all of them. this is what i get
Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
installing update....
installation aborted..
so is stock g1 cant say anything else cause really cant get any where else..
also when i choose rebot phone it takes me to recovery page then to a bluee screen telling me to press send to restore phone to stock i press send and nothing happens.. read on this site to wait 8-12 mins cause it takes that long to write stuff and load.i waited 1/2 hr to an hr and still nothing happens..any one got a idea to help me out...i've tried alot of stuff and if u wnt me to get in details i can.. also if u want screen shots i can post them as soon as i get home..
thanks in advance.. i love this site like i said i come here for all the know how to stuff that i've learned and even refrerred some friends looking to root there phone to come here as well..
I bought an unlocked HTC One. I get the notification for OTA, I download it as well. When the installation starts, the phone reboots, and installation starts. Around 25% later, it reboots again, tries to install again and after 25%, it stops and gives that warninign error sign and stays there. If I leave the phone alone, it will reboot and start working again after 3-4 mins. Then I will again get the OTA notification and the saga continues. I have tried doing many things like resetting, erasing phone and starting afresh etc. I have not done any mod on the phone...Please help someone...
Is a custom recovery installed?
Sent from my HTC One using xda app-developers app
Nope....I have not changed anything on the phone. Its whatever it had when I bought it brand new off the shelf....
Hey all,
I just got a notification on PC companion that a new update was available. "Jolly good!" I thought, and without hesitation, I clicked "update". Alas, that turned out to be a bad idea. My PC gave me an error: " An error has occurred and the phone / tablet software update was aborted. Click retry to restart the phone / tablet software.". I clicked retry, followed the steps presented to me, but got the same exact result on the second and the third try. When I try to start my phone now, it says "software update failed, please connect to you computer" or something of the sorts. Has anyone run into the same issue? And if so, have you managed to fix it?
The phone is a Dutch T-mobile branded version.
edit: I'm ashamed to admit I hadn't properly searched around, and thus I didn't know the update service existed. Currently, I'm trying to replicate the success this post spawned. Will report back with results.
update: no luck yet. The update service has been stuck on this position for about 20 minutes now. Not good. Any ideas?
2nd update: failure. I get this screen. Again, any ideas?
3rd update: When I plug the phone into a wall charger, it goes into a loop of completely off -> red led -> sony logo -> "software update failed, make sure the phone is connected to the computer and try again." -> repeat. This means I'm probably just discharging it at the moment. I have no idea what the current battery level is, because it wont start to a single screen showing it. I cant be sure it's above 50% like this.
Thank you in advance.
StLouis said:
Hey all,
I just got a notification on PC companion that a new update was available. "Jolly good!" I thought, and without hesitation, I clicked "update". Alas, that turned out to be a bad idea. My PC gave me an error: " An error has occurred and the phone / tablet software update was aborted. Click retry to restart the phone / tablet software.". I clicked retry, followed the steps presented to me, but got the same exact result on the second and the third try. When I try to start my phone now, it says "software update failed, please connect to you computer" or something of the sorts. Has anyone run into the same issue? And if so, have you managed to fix it?
The phone is a Dutch T-mobile branded version (C6903).
Thank you in advance.
Click to expand...
Click to collapse
I get the same issue when i tried to update OTA to the .593 O2 UK branded firmware. I am rooted though (but still locked bootloader) so just assumed that was the problem but perhaps not.
Anyone any ideas?
Try with Sony update service.
Sent from my C6603 using xda premium
I'm ashamed to admit I hadn't properly searched around, and thus I didn't know the update service existed. Currently, I'm trying to replicate the success this post spawned. Will report back with results.
update: no luck yet. The update service has been stuck on this position for about 20 minutes now. Not good. Any ideas?
2nd update: failure. I get this screen. Again, any ideas?
3rd update: When I plug the phone into a wall charger, it goes into a loop of completely off -> red led -> sony logo -> "software update failed, make sure the phone is connected to the computer and try again." -> repeat. This means I'm probably just discharging it at the moment. I have no idea what the current battery level is, because it wont start to a single screen showing it. I cant be sure it's above 50% like this.
Use flashtool and flash your phone, http://forum.xda-developers.com/showthread.php?t=2464389
Sent from my C6603 using xda premium
It turned out to be a driver problem; fixed by using another computer. For some more details, see this thread.
This thread can be closed.
Thread closed as described above