Looking for a definitive answer on FRF85B to FRF91, carrying Root!
i am on FRF85B (rooted)
I read this instructions,
http://forum.xda-developers.com/showpost.php?p=7075094&postcount=379
But as I am new to these things, how do i do the following:
"*Installed the FRF91 package from ......
*Without rebooting, installed the root package"
How do I install the FRF91 package? I am AmonRa recovery it wont allow me to install it.
Where ya from?
What i did was installing stock 2.1 from HERE and then just let it update naturally OTA update itself to 2.2. After that just apply root from HERE Just fastboot Amon-Ra again.
Anyways, Lox update didn't work for me either.
The top option requires stock recovery, not Amon-Ra.
At the time it was released, european Nexuses couldn't load several updates that popped up. Don't know if Lox updated the link'
If i was you i would just flash Geo411m's ROM, pretty much stock with ChrometoPhone thrown in. If you don't need it just remove it with adb.
To me the batterylife was a bit better with that and best of all, it has black status bar.
Sindroid said:
Where ya from?
What i did was installing stock 2.1 from HERE and then just let it update naturally OTA update itself to 2.2. After that just apply root from HERE Just fastboot Amon-Ra again.
Anyways, Lox update didn't work for me either.
The top option requires stock recovery, not Amon-Ra.
At the time it was released, european Nexuses couldn't load several updates that popped up. Don't know if Lox updated the link'
If i was you i would just flash Geo411m's ROM, pretty much stock with ChrometoPhone thrown in. If you don't need it just remove it with adb.
To me the batterylife was a bit better with that and best of all, it has black status bar.
Click to expand...
Click to collapse
Thanks, I will be going with Geo411m's blackstatus too!
Related
Hi all,
I have gone through the rooting for dummies guide, but as my intentions are slightly different can anyone help me by briefly writing down the steps for Rooting and Keeping Stock Rom and keeping Stock Recovery so that I can update it when google releases 2.2.
Would highly appreciate it.
You shouldn't have any problems updating to 2.2 if you flash amon's recovery.
Which recovery you have has no bearing; so long as you're rooted, you'll be able to download 2.2 and flash it. If your goal is to make the transition from 2.1 to stock 2.2 as easy as possible then, sure, stay with stock. I figure CM will probably have a 2.2 ROM out faster than most stock phones would have been able to download it via OTA, though, so I'm sticking with CM5.0.6 and will update whenever CM does.
same here.
trusting cyanogen
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I am using Enom. With Titanium backup it really doesn't mean much to switch roms
My understanding is that once you install a custom recovery you can not get ota. They show up as available and are clickable but fail. This was the experience described at the last ota. Are you folks that are saying you can still get ota after installing a recovery speaking from experience? In other words did you have a custom recovery installed and sucssesfully update at the last ota?
Thanks guys for the input, but like krabman said, i also heard if you put a custom recovery you cannot get the ota to work! Any confirmation on that?
with custom ROMs and custom recoverys, you will not be able to install OTAs. Most custom ROMs disable OTAs since they kinda break the custom ROM functionality like root access. Most OTAs reboot the phone into recovery to update the software. A custom recovery like Amon RAs recovery can only accept ROMs and updates signed with test keys. Any update released by Google/HTC which is officially signed will not work.
But this should not prevent anyone from installing custom ROMs and recoverys since most cooks include the latest updates very soon, sometimes even before the official releases...
What if you follow the Original Shipping Tutorial to restore you phone's original recovery system?
http://forum.xda-developers.com/showthread.php?t=614850
I would imagine if you followed that you would be back to a completely stock phone that would work with OTA updates.
But, if you don't plan on running any custom roms, why bother unlocking the boot loader at all? If you haven't already done it, I wouldn't.
Amon ra recovery can only accept ROMs and updates signed with test keys. Any update released by Google/HTC which is officially signed will not work. Nor will the stock recovery work since it loses its official signature when it gets ripped so the ota cant use it because it requires an officially signed recovery to install itself with. If this is incorrect then I look forward to being properly schooled. I can say that I have yet to find anyone that had a custom recovery on at the ota last time that was able to get the update and install it ota.
krabman said:
Amon ra recovery can only accept ROMs and updates signed with test keys. Any update released by Google/HTC which is officially signed will not work. Nor will the stock recovery work since it loses its official signature when it gets ripped so the ota cant use it because it requires an officially signed recovery to install itself with. If this is incorrect then I look forward to being properly schooled. I can say that I have yet to find anyone that had a custom recovery on at the ota last time that was able to get the update and install it.
Click to expand...
Click to collapse
Well that's great news. I regret unlocking my phone more every day.
To be honest this is pretty much a non issue as far as ota goes. The stock rom with the ota on it, or in other words the lastest official release, will be available to download here within hours of its release and you can flash it like any other rom. If they do a rolling release it may well be you can download it before it becomes available over the air.
PrawnPoBoy said:
What if you follow the Original Shipping Tutorial to restore you phone's original recovery system?
http://forum.xda-developers.com/showthread.php?t=614850
I would imagine if you followed that you would be back to a completely stock phone that would work with OTA updates.
But, if you don't plan on running any custom roms, why bother unlocking the boot loader at all? If you haven't already done it, I wouldn't.
Click to expand...
Click to collapse
The reason I want to unlock the boot loader is to only use the metamorph and a few other launchers. I am a theme-freak so I could customize the look of the stock rom, but now that you all mention it, I guess I will stick with the Stock find other ways to theme it.
Thanks everyone.
PrawnPoBoy said:
What if you follow the Original Shipping Tutorial to restore you phone's original recovery system?
http://forum.xda-developers.com/showthread.php?t=614850
I would imagine if you followed that you would be back to a completely stock phone that would work with OTA updates.
But, if you don't plan on running any custom roms, why bother unlocking the boot loader at all? If you haven't already done it, I wouldn't.
Click to expand...
Click to collapse
After flashing CM's ROM, I was able to completely restore my phone to shipping state (sans relocked bootloader, of course), and then perform the 2.1-update1 OTA.
So yes, you will be able to update to 2.2 as soon as Google releases the OTA, but you'll have to completely revert back to stock in order to do it?
I'm not really sure about what I'm talking about, but I just wanted to confirm that you CAN perform OTA updates even after flashing a custom recovery image/ROM.
I'm currently trying to get a completely clean orginal Froyo install on my phone. I tried to search here, but what I found doesn't fix my problems.
My Nexus One was on ERE27 when I got it (bought used). I unlocked and rooted it, flashed Amun's recovery 1.5.3 (later 1.7.0) and after trying Cyanogen 5.0.6 and installing the EPE54B radio I finally went to Enomther 1.8.1 and later 1.9.2.
Now I'm trying to get a completely stock Froyo on my phone.
I flashed an ERD79 stock image using the PASSIMG.zip method, figuring I'd then get the OTA update to FRF85B, maybe with an intermediary step via ERE27.
When I dial *#*#checkin#*#*, it just says "checkin succeeded", though, and doesn't provide an update.
Unfortunately, my original nandroid backup was lost in an sd-card screwup, so I can't go back to my original ERE27 system, either.
So I tried to update to ERE27 using the stock recovery and the update.zip from ERD79 to ERE27, but I only get the <!> sign and a green android, nothing like "apply update.zip" to choose. (I never used stock recovery, so I don't know how this is actually supposed to look like.)
I could do this using the custom recovery again, but with that I can't flash the original Froyo update. I couldn't find a stock recovery image for ERE27 anywhere, but the update ERD79->ERE27 contains stuff for the recovery partition, and I don't know how to get that updated correctly.
Any hints/links?
What puzzles me most is why I don't get OTA updates on stock ERD79. Any ideas on that?
Stock ERD79 stopped giving updates a couple of weeks before Froyo started.
Head over to Developers section, download stock FRF85B build for flashing on non-stock recoveries, from Lox's thread. Flash it and you're set.
Ah, ok, so that's why I don't get updates. Thanks.
The bar has not filled up...What to do? Quit and try again?
USed Clockwork mod to find and install OTA'JH7.zip
Searched for it
found it
Installing hangup and nothing in the bar indicating anything is being done
Did you have any lagfixes installed prior to trying to update?
Rhiannon224 said:
Did you have any lagfixes installed prior to trying to update?
Click to expand...
Click to collapse
My history is as follows:
Stock to Root
Back to stock
Installed JH7 via mini Kies
BAck to stock
(Learned how to use adb to get into download mode)
Loaded Froyo "Officical beta"
Wanted to try the Clockwork mod so I went back to stock using ODIN
Installed the Zip files in proceeded to install Clockwork then searched for and found the OTA file
There are two files out there. JH7_OTA.zip and JTA_OTA_STOCK.zip
The latter did not work and hung up on install..I loaded the former and it installed.
Now a few questions regarding Clockwork
I dropped the Cognition 2.2 5 in my root directory..Can I load that in the same way? Then go back to the JH7 when the Official 2.2 froyo comes out? Whether rooted or not?
If I want to root the phone I will have two update.zips in the root directory (Clockwork and the root upadate.zip)...Must I remove Clockwork? IS it loaded or does it execute from the zip every time? Can I rename the Root update.zip to something else now that I can "find" it with Clickwork?
I like the clockworkmod and will definitely pay for it if it allows me to change ROMS I place on the SD on the fly rooted or unrooted (would never need to go back to JH6 and deal with adb if so)
Final question,,,Shoudl I use clockwork to "reset the battery?"
I do not intend to do any lagfixing beyond whatever is in Cognition since that seems to be more of a problem than it may be worth
Thanks...Its been two weeks since i became an Andriod fan and i have learned alot.....and still am
Read the Cog wiki, there have been so many versions I can't remember all of them and the install instructions, some you needed to flash through Clockwork. Cog 2.2 5 Is Froyo whicj means you can not use Clockwork to flash anything with Froyo running because Froyo is not an official release and is BETA it is not signed, Koush hasn't found a way to sign it in order for Clockwork to work with it yet. Clockwork is worth having the paid version yes. You must be rooted to use ROM Manager so unrooting you loose access.
If you are using JH7 that you flashed check if you have SuperUser in your apps drawer, if so you are rooted. Get used to Odin if you are going to mod your phone you will use it more than you think and it becomes less scarey the more you use it.
You've already modded your phone so OTA updates will not work for you, mini kies will so go ahead and flash away, you will eventually have to flash with Odin to update with mini kies so go have fun. Also, those guys on the dev section will have the official up as soon as it comes out. We had JH7 within a few hours, none of us could do the OTA and AT&T bricked a lot of phones so I will only use stuff from Samsung anyways.
Rhiannon224 said:
Read the Cog wiki, there have been so many versions I can't remember all of them and the install instructions, some you needed to flash through Clockwork. Cog 2.2 5 Is Froyo whicj means you can not use Clockwork to flash anything with Froyo running because Froyo is not an official release and is BETA it is not signed, Koush hasn't found a way to sign it in order for Clockwork to work with it yet. Clockwork is worth having the paid version yes. You must be rooted to use ROM Manager so unrooting you loose access.
If you are using JH7 that you flashed check if you have SuperUser in your apps drawer, if so you are rooted. Get used to Odin if you are going to mod your phone you will use it more than you think and it becomes less scarey the more you use it.
You've already modded your phone so OTA updates will not work for you, mini kies will so go ahead and flash away, you will eventually have to flash with Odin to update with mini kies so go have fun. Also, those guys on the dev section will have the official up as soon as it comes out. We had JH7 within a few hours, none of us could do the OTA and AT&T bricked a lot of phones so I will only use stuff from Samsung anyways.
Click to expand...
Click to collapse
Yeah I have two phones and one is the guinea pig. I have my main phone on the pre release of Froyo. I am practicing getting the second phone eventually from Cognition2.2 5 to Samsung's official release. I have used ODIN probably 10 times to get back to JH6 where I have to use the adb SDK to get into recovery/Download modes.
The OTA updates did not work for either phone which is why I began modding and learning, Mini Kies was the only way to get JH7 until now with Clockwork.
I just got a Nexus One that was ROMed and rooted (has RA-nexus-v2.0.0 recovery) and enom's 2.14.2 ROM. I don't very much like it (seems slow). I am trying to go back to STOCK Android 2.2.2, with Root access, in preparation for 2.3's release. I know how to use ADB so that's not my problem. I've downloaded FRG91 in hopes that I will get an OTA to FRG83G. Now here's where I start getting problems. I go into Recovery, go to Flash Zip from SD card, and try to flash it, but it says it doesn't have signatures. md5sum is correct so that's not it. Can anyone help me out? I've tried doing about 10 different things so far and none of them have worked. Maybe someone else has seen this? TIA.
Have you try to toggle signature verification off?
Here's a rooted 2.2.2 rom
http://forum.xda-developers.com/showthread.php?t=927935
I haven't. I think I might have found a way to get this baby working. I'm working on it now. If I need anymore help, I will re-ask in this thread. Thanks for the tip though, didn't think of that!
Alright. I think I got it to work. Had to do some fenagelling, but I got it back to stock 2.2.2 Official.
Admin, can you delete this post?
You can't flash stock roms without stock recovery, Google's signature is on the stock roms so only stock recovery recognizes it. There is also a option in your custom recovery to turn of signature verification. I wouldn't recommend that you try, because I don't know what would happen. But it's a option, if your that hard pressed to go back to stock. Another note, since the G1 days the devs built their roms to stop OTA updates. So if you flash stock recovery, then you may need a stock rom to receive a OTA. I wouldn't get my hopes up about getting Gingerbread or Honeycomb OTA. I don't see anything on any android forum about this happening, I could be wrong though. If you can get your hands on a stock recovery image then you can flash with adb or fastboot commands. Good luck.
Go here for further assistance
http://forum.xda-developers.com/showthread.php?t=614850
blas4me said:
You can't flash stock roms without stock recovery, Google's signature is on the stock roms so only stock recovery recognizes it. There is also a option in your custom recovery to turn of signature verification. I wouldn't recommend that you try, because I don't know what would happen. But it's a option, if your that hard pressed to go back to stock.
Click to expand...
Click to collapse
Turning off signature verification works fine. No problems whatsoever flashing stock ROM/updates.
blas4me said:
Another note, since the G1 days the devs built their roms to stop OTA updates. So if you flash stock recovery, then you may need a stock rom to receive a OTA. I wouldn't get my hopes up about getting Gingerbread or Honeycomb OTA. I don't see anything on any android forum about this happening, I could be wrong though. If you can get your hands on a stock recovery image then you can flash with adb or fastboot commands. Good luck.
Go here for further assistance
http://forum.xda-developers.com/showthread.php?t=614850
Click to expand...
Click to collapse
OTA updates have nothing to do with a stock recovery. All newer versions of Amon_RA and CWM custom recoveries have signature verification toggles, so you can install OTA updates without problems.
The only thing is that you need to have a stock ROM (not de-odexed, and not an AOSP build) for the OTA update to install.
I just got a used N1 and am using it on TMO as an upgrade from a MyTouch 3G. It was sold as being fully stock (no root, no unlocked bootloader, but I don't know how to verify that), and it is the holiday model (with the QR code on the back)
When I booted it up, it came to the main launcher (it didn't take me through the setup wizard). It looks like the last user did a full wipe (maybe not, because I thoguht that would make the setup wizard popup if they did). It was running 2.2.1 (I think) and had an update for 2.2.2 immediately ready to install. So, I let it install the update, which went smoothly and it's now running 2.2.2, with baseband 32.36.00.28U_4.06.00.12_7 and kernel 2.6.32.9-27240-gbca5320android-build apa26 #1.
I have been patiently waiting for my gingerbread update, and it has not arrived. I figured since 2.3.4 was rolling out, they stopped 2.3.3 updates and that was why I didn't get it. Now that 2.3.4 has rolled out, I still haven't got any updates, even after doing a checkin.
Does anyone have any ideas why I am being forgotten, and how I can go about updating my phone? I will not root or unlock the bootloader - I'm keeping this thing 100% stock and not willing to take any risks with it.
Thanks in advance,
Mike
Update don't get push to everyone at the same time. Be patient
OK, thanks. So it might be normal that I haven't gotten 2.2.3, let alone 2.3.3 yet? From what I've been seeing in other threads, the OTA update being pushed out now is from 2.3.3 to 2.3.4, so that wouldn't work directly from 2.2.2
You can always do a manual update and not have to wait for the OTA. Just download the corresponding files and rename it to "update.zip" and place on your SD card. Boot into recovery and apply update.zip. You remain 100% stock, but no wait.
And no, you need to go to 2.2 before going to 2.3.3 before going to 2.3.4. The OTA's are generally incremental updates.