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.
Related
I need help quick! Im stuck on rc29 and I cant update!!! Everytime i try to unzip the Update.zip folder it tells me Signature (302) failed or something like that. It feels like ive tried every single download possible. Ive tried to go rc29 to rc33. Ive also tried to go rc29 to rc30 but none of them seem to work or is it me? HELP!!!
thanks!
surely you have been here long enough to realise that you get no love when you ask in the wrong section
Did you rooted the device and installed custom recovery image???
It seems like you tried the roms without flashing the custom recovery image as the custom roms cannot be flashed with original recovery..
The best custom recovery is Amon Ra 1.6.2 for the dream and magic..
However you should be able to flash the official OTA updates like cupcake or donut.. straigt from RC29 without rooting the device too..
Thanks!
Moved as not Android Development.
sorry about posting in the wrong section...my bad!
and how would i force and OTA update?
i dont have a option for system updates..
oh and also, i always get the corrupt file with i try to flash a official update...any ideas?
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 got my Nexus One last week and quickly rooted it and flashed CyanogenMod. Before I did, I did a nandroid backup of the original ROM. If I flash that original ROM back, will I get OTA updates again or is there something more I need to do?
kgeissler said:
I got my Nexus One last week and quickly rooted it and flashed CyanogenMod. Before I did, I did a nandroid backup of the original ROM. If I flash that original ROM back, will I get OTA updates again or is there something more I need to do?
Click to expand...
Click to collapse
you will get ota updates again if there is.
wipe, before you restore.
My understanding was once you unlock the bootloader you're done. No more OTA updates.
prettyboy85712 said:
My understanding was once you unlock the bootloader you're done. No more OTA updates.
Click to expand...
Click to collapse
Thats not true. The ROMs cooked here are simply put, blocking updates from TMobile or Google. From what i understand Google will be posting updates on the google.com/phone website.
Its the recovery that is the holdup is my understanding. Any ota that requires the recovery to install will fail because even if you reinstall back to the stock recovery it is no longer officially signed and the ota will only install with an officially signed recovery. An ota that does not use the recovery like the ota 3g update/fix will install fine unless it is blocked by the rom developer. All of this is a non issue anyways. From the point of initial release to when you can download the stock 2.2 rom and flash it yourself should you choose will be a very short.
krabman said:
Its the recovery that is the holdup is my understanding. Any ota that requires the recovery to install will fail because even if you reinstall back to the stock recovery it is no longer officially signed and the ota will only install with an officially signed recovery. An ota that does not use the recovery like the ota 3g update/fix will install fine unless it is blocked by the rom developer. All of this is a non issue anyways. From the point of initial release to when you can download the stock 2.2 rom and flash it yourself should you choose will be a very short.
Click to expand...
Click to collapse
Why wouldn't a restore of the original recovery image not be signed? Isn't the signature part of the image itself?
I dont understand this myself but as I read it something about dumping it strips it of its officially signed status. If I were forced to guess, and this is only a guess, its to prevent modifying it and reinstalling it for the obvious reasons. As it is I can say that despite seeing a thread like this daily at times not a single person has reported having reverted and then beinng able to install the 2.1 ota when it went down on any of them and yet there must of been scads of such people who tried just that. A number of them on the other hand have reported being able to get ota that did not require the recovery to install. In the interest of fairness I am repeating what I have read, I posseess no expertise myself. If this is inaccurate I hope that I will be corrected and we will all learn something.
Well...when 2.2 is released, can you just go to google and download it or is the only way to get the update via OTA?
Nah, that is what I was saying, you can download a stock 2.2 rom here and flash it via recovery like any other rom as soon as the smart types get er whipped up, should be very soon after release. I havnt seen anything official but as said above I have read that it will be up on googles phone site.
You can download the original Rom from Modaco and in fastboot flash the signed system file boot file and recovery if you do that u will receive the ota update from Google its the recovery that effects ota there's detail steps on nexus one forum search rolling back to stock Rom I did it and it works hope this helps
-------------------------------------
Sent from my Nexus One
Did you get the 2.1 that way?
I did I installed the original Rom that was sent on the nexus one after about 5 mins I got the ota update that enables multi touch so it does work and everything works fine
-------------------------------------
Sent from my Nexus One
Anyone got it or know where I can find it? Would like to have it so I can flash official updates. Been searching for it with no luck. Tried using among RA 2.0.0 but still failed.
take the version that suits you from the ones that say (completely stock)
http://android.modaco.com/content/g...build-info-and-repacks-stock-rooted-deodexed/
I suggest the last one if you really want COMPLETELY stock, others are just with root/radio update mixes...although I doubt you need the radio
Is the recovery image from FRG33 the same? Have you tried flashing that one with fastboot? If it doesn't work you can always flash a different one.
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Roms
(The FRG33 package has recovery.img in there)
I don't see any reason to flash a new radio...
ahorriblemess said:
Is the recovery image from FRG33 the same? Have you tried flashing that one with fastboot? If it doesn't work you can always flash a different one.
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Roms
(The FRG33 package has recovery.img in there)
I don't see any reason to flash a new radio...
Click to expand...
Click to collapse
waaahhh sorry I misread the topic XD I thought he wanted a whole rom...
Forget my links then, they don't have a stock recovery in them
Just as a note, you don't need to have a stock recovery to get OTA updates...as long as your recovery does NOT check for signatures...else you can simply install the update manually.
But anyways, if you REALLY want a stock recovery, just find any official update and flash the recovery.img that's included with it.
I tried using among RA 2.0.0 and toggle the signature off so it wouldn't check, but it still failed. I'm trying the frg83 to frg83d from the modaco site.
dls5375 said:
I tried using among RA 2.0.0 and toggle the signature off so it wouldn't check, but it still failed. I'm trying the frg83 to frg83d from the modaco site.
Click to expand...
Click to collapse
If you have RA 2 working, you can grab the update here and flash as zip
http://www.shipped-roms.com/shipped...signed-passion-FRG83D-from-FRG83.ecb21b75.zip
That's the same one I already tried, wont flash even with RA working. The rom I use is stock frg83 but with root. It always seems to fail to update as it trys to verify what I'm currently running.
dls5375 said:
That's the same one I already tried, wont flash even with RA working. The rom I use is stock frg83 but with root. It always seems to fail to update as it trys to verify what I'm currently running.
Click to expand...
Click to collapse
As of my small experience so far i can tell that it is very hard to trace where the error is, when using cooked stuff, just like all of a sudded i got this bloody red trackball all the time, when ever the screen is on.
Ok, if you got some little time, here's how i would go for that: (assuming you want pure stock with root)
- Wipe
- Either fastboot the few images contained in the latest modaco stock rom, or say rather as he described there, alternatively just install the 2 files from shipped rom, one will be named PASSIMG.zip, the other update.zip and proceed as the popular threads describe
- If all is "original" you'll be prompted by google to download the update, once you got the frg83D, you can then use Super Once Click rooting 1.5.1, it still works for the updated thing.
I'm convinced there are a lot of similar threads and solutions to your problem, but you may deliver a bit more description to let the community see you did some research.
I returned completely to stock using the info from another thread on here and it worked perfectly. Also returned to stock recovery. As soon as it booted back up I got the ota for frg83d. I then used super one click root. It was really easy to setup and use. Bring on 2.3!
Just a quick background, I purchased my DS7 at staples and rooted it and installed CWM using the info found on the forums so I could connect to my ad-hoc tether. Last week I attempted to install the HC upgrade and got the mis-match message. I booted into CWM and started looping. In an effort to correct this I mistakenly wiped the memory (big mistake!). I found the instructions on flashing the stock ROM (turned out that it was TMO) and got the unit running again. I called Dell (I have posted in another thread on this) and they are to send a pickup. In the meantime I have found instructions on flashing the OEM stock wfi ROM and have done so. I, like many others, noticed that the service tag was wrong and edited PG23/line220 to reflect my correct tag ( note to posters of ROMs and those who would flash: before doing so write down all the information about your unit so you can make changes later if needed). I now have most everything back to pre-upgrade status, but Gingerbreak v1.2 will not root. When I attempt it the program runs but I get a message “Not sure what happened her. Either the exploit failed or the reboot failed. Please reboot manually and see if you have Superuser!” I reboot and nothing, no Superuser and no root access. Also, before I attempt the “unroot’ option is greyed out so I take it that the unit is not rooted nor can I see root files in file manager One thing I have not tried is the CWM un-install that was included in the stock ROM flash thread. Since I don’t see it and I boot into fastboot I am guessing that it is gone. Any suggestions or has anyone had this issue as well?
Another note, I too have the 338 version and no auto update yet. I am not real sure I want to update now. To those that have updated, can you connect to ad-hoc networks with out changing the WPA?
Big wall of text, if you're on 2.2.x reflash CWM 3.0 and flash Superuser.zip as a update.zip though it.
If you're on HC, flash CWM 4.0 and flash Superuser7.zip on it.
Superuser.zip will always work on 2.x roms.
Superuser7.zip will always work on 3.x roms.
If you try and run the wrong one it will just 'run' and give no error, it will simply not do anything, but it wont damage anything.
Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?
alchrisr01 said:
Thanks, you think cwm is still lurking and giving problems? So I need to reinstall cwm and use it to install the zip? Won't CWM interfere with the HC update?
Click to expand...
Click to collapse
If you have CWM installed you won't get the update automatically no matter if you have a matching ROM or not... you must be FULLY stock... but I see no sense in waiting, TheManii has already posted the releases that are coming out... why not just flash the zip