I've had my N1 rooted pretty much since day one. Installing Froyo (at the time) wasn't as smooth as I have come to except of Google products, since the OTA updates wouldn't install and I needed to use repackaged versions. Recently my phone started nagging me to install 2.2.1. I got fed up and finally re-flashed the stock recovery image (I didn't restore anything else).
Ever since, I haven't been promoted to install the the update. Additionally, trying to update manually (using the original file) resulted in an android guy and an exclamation mark - but nothing further.
From my understanding, as long as you have the stock recovery, you should be able to flash original packages. Am I mistaking?
UPDATE: So the update was pushed to my phone again. After clicking install, the phone rebooted and the update started installing. At some point however, it froze with the android guy and an exclamation point development. I had to remove the battery to reboot.
Was re-flashing the recover image not enough?
I believe you have to be on stock recovery and stock rom.
I believe I'm on both. I cant get a checkin to indicate that there is an update. Is that normal?
I'm in the same boat but can't even reflash the original rom through vol- power.
In on this!
Related
Is there a way to stop my Droid from updating OTA to FroYo? I have flashed my Droid over to Cricket and have Bugless Beast v0.4 installed, and now since the 2.2 OTA update has been released I get a constant notification that the update is available. The only options I get are to install now or to install later, but what if I don't want to install it all and just get rid of the pesky notification that keeps popping up every so often after I press install later. I already have 2.2 on my system with Bugless Beast so I'm not really missing out on anything. I don't want to update and have to reroot, reinstall Bugless Beast, and reflash my Droid to Cricket again. I'm happy where my system is at
If you have a custom recovery, then as soon as you reboot into the installation your phone thinks that you've accepted, but the custom recovery blocks the installation and you stay on BB.
What do you mean by reboot into installation?
I've booted into clockwork recovery and then restarted the phone, but nothing seemed to change. Is that what you meant to do?
Flash SPRecovery. Then select "install now". It will send a notification that it has been installed on your phone to the servers that send out the OTA but SPRecovery will block the installation of it onto your phone, thus stopping the notifications of an update and keeping you on BB v.04 w/ Cricket. You can flash back to CW Recovery if you want to afterwards.
Sent from my Droid using XDA App
Im also running BB.04 and got the OTA notification today. Glad I found this thread because I was starting to get worried. I clicked 'install now', rebooted and so far no notification and I am still on BB.04. Woot!
Thank you for this!
Running BB 0.4. I saw the verizon 2.2 Froyo upgrade this morning, and for a second I was psyched verizon finally pushed it out... then I was a little worried about what was going to happen to mine since it was rooted and running a 2.2 Rom I was already happy with. Just like this thread says, I clicked install, and the phone rebooted right back up to my BB 0.4 without any issues.
I'd hate to say I'm a leech, but you guys have so much information here, and I cannot stop reading lol. I commend everyone one of you Devs for all the work you do!
Thank you again,
-Dano
Yup, it worked perfectly! Thank you!
Interesting. I was able to block it the first time but it popped up again. Anyone know why? Maybe there is another update to the 2.2 OTA update?
I was having the same issue with the ota update until I came across this:
http://www.peteralfonso.com/2010/08/how-to-stop-ota-notifications-on.html#more
it says it is for Buggles rom but I am using a different rom and it worked just fine
I had received this notification about four times before it recognized that I'm updated without rebooting the phone for it to be blocked. Nothing else had to be done except for saying yes.
stephen730 said:
whatchoo mean able to block it? You mean you clicked install later? Or you let it run and it goes away?
If you let it run/fail it will just come back again a day later, a week later, next time you reboot, next time you come out of screen off, etc... Its done it to me and it sucks cause it won't go away number 1, and number 2, i hate to keep rebooting to fail and possibly missing calls/texts... especially when you first wake up and the message is there like a nagscreen or advert.
Click to expand...
Click to collapse
I clicked install now and my recovery image blocks the installation when rebooted. It shows the Android guy with the exclamtion point but it doesnt finish the install. Reboot then im back to the way I was. Im running BBv.4 btw. I havent got another prompt yet.
Hopefully you guys know there is a software fix out from at&t and samsung that fixes gps problems and etc...
goes without saying you can't just straight update if you're rooted. That's where i'm stuck.
Before i touched anything, it would get to 50% and reboot, says the update was not applied.
Then I tried "unrooting" even though it said it was unrooted, and apps requiring SU backed this up saying my phone was unrooted.
Then during the update, it stops even sooner at "preparing".
So... how do we get around this without doing the master clear with odin3???
I DON'T want to lose all my data. I'm too lazy.
Mine said failed at 100%. I def got the jh7 update though. My phone was unable to reboot into recovery using the three button method. Now I can. My phone was rooted with stock rom.
Mine is rooted with the Voodoo fix and it failed during the update (I was at work so don't know at what step during the update).
Will have to do the voodoo-lag unfix - restore back to factory defaults and try it again..
Unless of course someone pops out a tweaked ROM before then!
check out this thread, http://forum.xda-developers.com/showthread.php?t=789546 so we can get everyone with this issue together in one thread
I decided to try out rooting my device using superoneclick on Friday, then I also manually installed the latest OTA update yesterday. And now my device is not happy. Before all this, the thing was solid, has never once crashed or rebooted on me. In the last 24 hours, I've had to remove the battery about 10 times so far, as it has locked up completely. Seems something is off with GPS, as using geo-location related functions from within apps seems to cause this. The bootloader is still locked, and I haven't installed any recovery images or anything like that, just rooted and updated using the update.zip method, but something has not gone well.
So, my question is, how can I restore everything back to how it was? I want stock, 100% unfucked-with everything back in the device. Factory wipe hasn't helped, and hasn't removed root (which surprised me, but seems obvious now I think about it). I have a copy of the Nexus One FRG83 system image (73.9mb) from HTC, but don't know how to install it. Once I install this, I will update using the ota updates, and try root again.
What do I do?
Read my signature.
Rename the the system image to PASSIMG.zip. Boot into the bootloader and it should detect it automatically. Update, restart, done.
Thanks guys/
I just rooted my Bionic after finally getting tired of any OTA updates from Moto/Verizon. When I went to root it I noticed my build number was 5.5.886, and when I clicked on System Updates, it said it wasn't available and to retry again later. So I found a root method and the files for builds as old as mine and went ahead and rooted.
I used Safestrap and installed a ROM, the CM10 for ICS Leak by DH from here. Well it didn't work. I cleared cache/data, put it into safeboot and flashed it. It said it installed correctly and everything but after I rebooted the phone it did the droid bootloader then a blank screen with the keys and backlight on. I left it there for around 20 min to see if it was just taking awhile to boot.
I then rebooted back into recovery and turned safeboot off. I didn't restore my pre-root rom, rather went back to factory. This time when i clicked on System Updates, it found one and updated. So I figured maybe that was the problem. I repeated the procedure and still got the blank screen. I figured it may be the ROM not working with my phone so I tried another one, and 4 more after that, all with the same result.
Is there something I did wrong? I can still get my phone working by turning safeboot off, but no ROMs have worked yet. Could it be that I updated with an OTA after rooting?
Got it figured out. Just used RSDlite to flash .902 then OTA to .905.
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.