Database Develop

Build EPF21B to Froyo

Does anyone know how i can get froyo on my phone with the EPF21B build? Could i change to the ERE27 build WITHOUT rooting my phone? Or flash pauls version through the stock recovery image, without voiding my warranty? Thanks for any help

same problem.
my phone is EPE54B
HELP!!!

Gotta root until Google sort it out I'm afraid.

I have ERE36B with locked bootloader. Can I just update or do I need another update file?

You're on an awkward build... I very much doubt there will be an upgrade path for you.
You will most likely need to flash a mainstream PASSIMG.ZIP (AT&T EPE54B or Vodafone EPF21B) and update from that when Google release one.

Rusty! said:
You're on an awkward build... I very much doubt there will be an upgrade path for you.
You will most likely need to flash a mainstream PASSIMG.ZIP (AT&T EPE54B or Vodafone EPF21B) and update from that when Google release one.
Click to expand...
Click to collapse
Edit: Actually, maybe you should listen to him. After clarification it seems that there were un-original roms out in the wild that didn't need an unlocked bootloader. If you updated to that ROM yourself, even without unlocking then you may not see an upgrade at all.
Old post below for continuity's sake.
--------
Don't listen to him. It seems he is telling you that you will need to unlock to upgrade. If you aren't going to unlock yet, just wait, there will be an OTA update for you too, you just have to wait for Google to send it out.
Google will not force you to unlock your phone.

Is there a way to go back to ere27 so i can update now, without unocking?
Dont mind if i have to do a factory reset or something like that

Requiem87 said:
Is there a way to go back to ere27 so i can update now, without unocking?
Dont mind if i have to do a factory reset or something like that
Click to expand...
Click to collapse
EPF21B is the official euro shipping ROM.
You can't change it back to ERE27 without unlocking the phone, period.
If you don't want to unlock, you'll have to wait until Google issues the OTA for the official euro phones.

Clarkster said:
Don't listen to him. It seems he is telling you that you will need to unlock to upgrade. If you aren't going to unlock yet, just wait, there will be an OTA update for you too, you just have to wait for Google to send it out.
Google will not force you to unlock your phone.
Click to expand...
Click to collapse
Thanks for that completely incorrect post.
I am not telling you to unlock, both can be flashed in the same way you flashed ERE36B as they are official released images.
As ERE36B is a release that shouldn't be out in the field, I doubt an update will be made for it.

So, since I am not on Vodafone or AT&T, what should I update to? AT&T EPE54B or Vodafone EPF21B?
There has to be a way to restore the phone to factory state and factory ROM?

Rusty! said:
Thanks for that completely incorrect post.
I am not telling you to unlock, both can be flashed in the same way you flashed ERE36B as they are official released images.
As ERE36B is a release that shouldn't be out in the field, I doubt an update will be made for it.
Click to expand...
Click to collapse
Sorry about that, it seemed to me that you were telling him he would never get an update without unlocking. But he did mention that he was still locked and had that release. I don't know how he got that one, but if he is truly locked wouldn't it make sense that Google knows of the phones out there with that version?
I still don't think it would make sense for Google to not give those phones an update, and to force them to unlock to upgrade.
Am I missing something important here that's really messing up my understanding?

Requiem87 said:
So, since I am not on Vodafone or AT&T, what should I update to? AT&T EPE54B or Vodafone EPF21B?
There has to be a way to restore the phone to factory state and factory ROM?
Click to expand...
Click to collapse
Except that the factory ROM is different from one to another.
Tmobile factory ROM : ERD79 (which can then be updated to ERE27).
ATT factory ROM : not sure but the one before EPE54B
Europe factory ROM : EPF21B.

Clarkster said:
Am I missing something important here that's really messing up my understanding?
Click to expand...
Click to collapse
I think so.
There are certain ROMs that were leaked, these can be installed without unlocking the bootloader as they are release signed. No phone sent out by Google came with ERE36B, you had to install it yourself. There is also no way back to stock ERE27 without unlocking the bootloader.
My reckoning is that as this particluar ROM isn't meant to be in use by the public an upgrade path is unlikely, hence the advice to flash to a 'legitimate' release image (no unlock necessary) which will definitely be upgradable.

Rusty! said:
I think so.
There are certain ROMs that were leaked, these can be installed without unlocking the bootloader as they are release signed. No phone sent out by Google came with ERE36B, you had to install it yourself. There is also no way back to stock ERE27 without unlocking the bootloader.
My reckoning is that as this particluar ROM isn't meant to be in use by the public an upgrade path is unlikely, hence the advice to flash to a 'legitimate' release image (no unlock necessary) which will definitely be upgradable.
Click to expand...
Click to collapse
Thanks for explaining. I'll go edit my original post.

Thanks Rusty. What rom should i update to then? Is there another rom i can downgrade from, or is it generally impossible to go to an older rom with locked bootloader?

Can't go older unfortunately, else it would be a no-brainer.
As for which one, I doubt it matters, but I would expect EPE54B to be the next updated.

cant you just flash pauls prerooted version?

bobdude5 said:
cant you just flash pauls prerooted version?
Click to expand...
Click to collapse
Doesn't work, cancels installation when it doesn't find the right signature.

yeh, tried that, Wont work with locked bootloader. Tried all ERE27 images, renamed to either passimg.zip or update.zip, and same for all frf50.. Only one thing left to do i guess, and that is wait.

Having the Same Problem,
Hi, I have a Nexus One from Vodafone, and have unlocked it, however, I still can't get it to update to Froyo FRF50 so I can then further upgrade it, I am currently on build EPF21B which I think Vodafone have mucked around with, because I have just updated a Friends Nexus Manually with the same file not problems, mine keeps coming up with, first:
Froyo+E:Can't open /cache/recovery/command
Then fails on this:
E:failed to verify whole-file signature
Can any of you kind people out there confirm that there is something slightly odd about the stock Vodafone ROM,
Thanks for your time in this matter, I assure you that it is deeply appreciated
Kind Regards - Ashe

[QUESTION] Root FRF91 without touching boot loader

I know the update was a security fix but am looking for a method to root while remaining as completely stock as humanly possible. I've never rooted before and am still completely stock now.
Best case scenario would be to gain root while leaving everything stock, boot loader, recovery, etc.. maybe even try one of them nice roms for the first time (i hear cyrogen is the best and yes I probably misspelled that)
Thanks
Sent from my Nexus One using XDA App

Same question

There's a couple of tutorials about this in another thread.
If I were you i'd follow one of them and also install a custom recovery. Then play around all you like with rooted roms, stock, custom or otherwise. Once you have a custom recovery you can flash anything. The only down side is that you won't be able to install any OTA roms. But to be honest they appear on XDA in a format you can use on custom recovery way way before you ever receive an OTA notification anyway.
Then if you're sure you only want a stock but rooted rom, then install that and then finally flash the stock recovery back.
However if you're sure you don't want a custom recovery and only want root, you can follow the first half of the same tutorials.
I myself have an unlocked bootloader, but if I didnt, I would root, install a custom recovery and never look back. If anything ever happened to my device i'd just flash the stock recovery and stock firmware and send it back.

Ok, thanks!

That's good information but I'm unsure if I want to unlock at the moment. Thanks but I'll wait a little longer to see if a solution comes out that this my needs.
Sent from my Nexus One using XDA App

viper2g1 said:
That's good information but I'm unsure if I want to unlock at the moment. Thanks but I'll wait a little longer to see if a solution comes out that this my needs.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
No, thats the point. You dont need to unlock to root OR put a custom recovery anymore. See here for example:
http://forum.xda-developers.com/showthread.php?t=710842
So you can root, put on a custom recovery, try different roms and then go back to stock, rooted or not, without unlocking the bootloader at all.

I see what your getting at, that's what I was looking for but wasn't sure it was working for FRF91 the last few posts in that thread indicated an unlocked boot loader last time I looked.
I thought the update was to fix the security hole that allowed that
Sent from my Nexus One using XDA App

I have read a lot of comments on the guide of how root the nexus without unlocking the bootloader and searched in other places but couldn't find an answer to my question...
I've got at&t version nexus unrooted and I updated it to FRF91 OTA.
can I use this guide to root it without unlocking the bootloader?
If I can, how do I do it? some people wrote that I need to use Passimg.zip
but I think It's for T-mo version only because at&t's version doesn't have the erf79 (I hope I wrote it right).
anyway I'm really confused. can someone please explain?
thanks

I've got at&t version nexus unrooted and I updated it to FRF91 OTA.
can I use this guide to root it without unlocking the bootloader?
Click to expand...
Click to collapse
Me too - same question... I didn't see any tuts for rooting FRF91 w/o unlocking the bootloader.

RashaMatt said:
Me too - same question... I didn't see any tuts for rooting FRF91 w/o unlocking the bootloader.
Click to expand...
Click to collapse
they should work in the same way as it did for FRF83 or FRF85B.. you could always try without harm

RashaMatt said:
Me too - same question... I didn't see any tuts for rooting FRF91 w/o unlocking the bootloader.
Click to expand...
Click to collapse
this link: forum.xda-developers.com/showthread.php?t=717870
is a guide of how to downgrade from FRF91 to FRF85 in an unrooted nexus.
that way you can use this tut and root it w/o touchnig the bootloader

EPE76 to frf85B
Hi,
I am back from frf91 ota to EPE76 by applaing passimg.zip. My question is how can I move to frf85B ? I've tried to download universal frf85B, change name to update.zip and go to recovery, but I only see exclemation mark. Please advise. Thank you.

[Q] how to return to stock recovery with locked bootloader?

im gona send my phone in as a replacement, but i want to make sure everything looks stock before it send it in, i found a couple of ways to return to stock but i keep getting signiture verified failed, and i assume its because i have an unlocked bootloader, can any 1 help?

You should be able to find the stock rom for unlocked users in the development section. Just flash that and you will be back on stock.
But you can't re-lock the bootloader. When you unlocked it you voided the warranty, and it stays that way.
If it is a physical hardware problem, you should be able to still get warranty though.

Sorry, I meant to say my bootloader is locked, I don't have a problem with the rom, but the recovery. I am on ra recovery atm and I want to go back to google's stock. Is there anyway to do that?

Im pretty sure this works for all phones but if you flash Official OTA it will put everything back to stock(except bootloader if it has been unlocked) but doing this you will also loose root as well
i would wait for some one to tell you another way to get back to stock recovery, im sure there is a way to do it in adb or something.. Flashing the official OTA should be like a last thing wanting to do

Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space

codearray said:
Look for the stock recovery Tom for your phone then just flash with fastboot. That's the easiest way that I. Did it.
sent from outter space
Click to expand...
Click to collapse
He cant do fastboot, he has locked Bootloader.

yeah, it saids verification failed and wouldnt let me flash anything onto it

oops my bad. I had an unlocked bootloader. My other phone is locked.
sent from outter space

vvaffles said:
yeah, it saids verification failed and wouldnt let me flash anything onto it
Click to expand...
Click to collapse
Yeah i had the same problem when i tried to revert mine to stock. My bootloader was lock and wouldnt let me reflash the stock rom with verification failed.
NOT SURE IF THIS IS THE CORRECT WAY, DO AT YOUR OWN RISK :
I renamed the image to PASSIMG.zip and booted into bootloader. The bootloader automatically searches for PASSIMG and when it found it went through an update/installing process which took about 5minutes. When it booted phone was unrooted again, and had the stock recovery.
Once that was done, i installed the FRF85 (i think) update.zip from bootloader recovery, then did the same with update.zip for FRF91.
Again not sure if this was the correct way as i have never seen posts directing to do it this way - have posted questions about it in the past week or two, but never got any responses...

I'm gonna bump this thread up again. I tried downloading the original PASSIMG file for the stock and when I try and flash it by putting it on the SD card I get that the main file is older and the install is aborted. I can't fastboot the files because my bootloader is not unlocked. I'm currently running a FRG83 based ROM, does this matter? I'd like to return my phone to stock recovery and stock ROM, but so far every attempt has been met in failure... I guess it's an irony of rooting a phone without unlocking a bootloader. If you have to send it in for repairs you have to unlock the bootloader to return to stock, or you can't return to stock and you're left with custom recovery and root... either way HTC knows you're rooted. I know my issue is a hardware issue, but it would be my luck they decide to void my whole warranty.

You can't just PASSIMG your way back from FRG83, if you have it - since there's no PASSIMG for FRG83 yet (at least I'm not aware of one, and looks like Google isn't either), and the system is designed not to flash older builds. Trying to use PASSIMG to return to older builds requires some heavy preparations (has to be rooted, then downgrading HBOOT and probably flashing initial system.img from an older build through adb in recovery, using flash_image). It's possible and not very hard to do, but most probably beyond "1-click-root"ers' skills. All the relevant info is in the Wiki, so if you want to attempt it - you can try.
Unrooting FRG83 (reflashing stock recovery from FRF91, removing su and Superuser.apk from root shell) might be easier.
Also, put attention that if the phone has SLCD screen - the official stock FRF91 won't work on it.

I actually was able to PASSIMG to FRG33 then OTA back to FRG83. which I thought was odd due to the fact that I was on a FRG83 based rom. Oh well, it's 100% back to stock now. So even though people say that a rooted/unlocked phone only voids your software warranty I don't have to worry about it. Yay for keeping a locked bootloader.

how do i go back to frf91 from frg33?

I flashed 33 and my phone is stock. I need paid apps plus this build is bugging out on me alot. Stuff freezes, its just a bad build. How do I undo this without rooting?

Pretty sure you have to root.

If its like FRF91. Then it wont let you downgrade because it sees FRF91 as an "old version."

Download ere27 as passimg.zip. place in your sdcard root. Boot into recovery. Restore. Let it do its work. Put frf91 into sd card. Boot into recovery and load from zip. Ta da. You are on Frf 91
Sent from my Nexus One using Tapatalk

Or, if you want a shorter and more correct route:
Nexus One Wiki, "Restore", PASSIMG.ZIP method, use FRF91 complete stock image found in one of the threads in Q&A from the last day (or Google).
Don't use FRF91 update, since it's only an update - it's not a complete image.

whatever. Just use a passimg.zip to clean out all the crap. its basically the "do-over" method. Think etch-a-sketch flip and shake.

i tried passimg from http://forum.xda-developers.com/showthread.php?t=717870
it said failure because it was an older version. If i find that ere one will it let me do it? i dont mind going way back and working my way back to froyo, but i dont think i can passimg anything since its considered "older"

search the forum for how to downgrade your hboot- it exists just search for the thread

http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258

androidjedi said:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=726258
Click to expand...
Click to collapse
Thank you. Looks like ill have to root for it which im sure ill find if i search how to root 33 so ill wait for a while to see if something else comes up but at least I know there's a way

There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.

Jack_R1 said:
There is no other way but to root.
Since you're erasing the system you're rooting anyway, why do you care?
The full guide is now in the Wiki, including reverting HBOOT for those that need it.
Click to expand...
Click to collapse
i dont know, i did 1 click root a few times but every rom i tried- cyan, eno, modac, whatever were great but there was always some bug or something that was annoying enough that i just wanted stock instead. So i dont know how much i like the idea of permanent root, but theres probably a stock rom i can use so its not the end of the world. SDK/Terminal i did all that crap with my g1, personally i found it to be more of a hassle than it was worth. But not having protected apps is not going to cut it so ill cave soon im sure

Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?

Jack_R1 said:
Again, maybe this time it'll be understood:
There is no "permanent root". The only "permanent" thing is unlocking the bootloader, which you don't have to do - the guide doesn't require it. The system you root will be erased in the PASSIMG method and replaced with a completely stock system of your choice. So, what's exactly stopping you from rooting?
Click to expand...
Click to collapse
the only way to go back from FRG33 is to unlock the bootloader at this stage, the PASSIMG method does not work

When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?

Why people can't understand?At this moment,if you've flashed stock FRG33 rom,using PASSIMG method,you can't root anymore!The only method to roll back to FRF91 is to unlock your bootloader,which is permanent and can't be un-done!
Cheers

Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".

Jack_R1 said:
When you revert HBOOT, it should work fine. Just the same as it works with Korean FRF91 version, which also has a new HBOOT. People in the FRG33 thread don't know it?
Click to expand...
Click to collapse
Code:
[HOW-TO] Revert HBOOT 0.35.0017 to 0.33.0012
I CAN'T RELOCK THE BOOTLOADER!!!
This only reverts your SPL/HBOOT back to 0.33.0012 after you've installed the Korean FRF91 files and ended up stuck with 0.35.0017 SPL.
Thanks to the guys in the Desire forums and help from the Nexus Q&A, I have reverted my phone to the original HBOOT so I can apply custom roms again.
First you need to root the Korean FRF91 that's on your phone using Paul's instructions for superboot FRF83.
If you are rooted already, skip this step.
http://android.modaco.com/content/go...the-nexus-one/
Code:
How to use Superboot - Windows, Linux and OSX
- Download the Superboot zip file above and extract to a directory
- Put your device in bootloader mode - Turn off the phone then press and hold the trackball to enter the bootloader
- WINDOWS - double click 'install-superboot-windows.bat'
- MAC - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-mac.sh' followed by './install-superboot-mac.sh'
- LINUX - Open a terminal window to the directory containing the files, and type 'chmod +x install-superboot-linux.sh' followed by './install-superboot-linux.sh'
Note: If you are using a retail Nexus One, you may need to unlock the bootloader first, as detailed here.

Ok, let's make some order:
1) PASSIMG can flash versions with the same or higher HBOOT version - to check: will the same version flash? I believe so.
The official FRF91 has HBOOT 0.33.0012, the Korean FRF91 has 0.35.0017, and I suppose the FRG33 also has 0.35.0017 - correct?
2) Rooting isn't possible on FRG33 yet. 1 report doesn't count.
So, looking at this:
Using PASSIMG with the Korean FRF91 (complete with HBOOT 0.35.0017) will work over FRG33, if the HBOOT is indeed the same version.
Korean FRF91 is rootable.
Rooting Korean FRF91 allows to downgrade HBOOT, which in order allows to use PASSIMG method to flash official FRF91 with older HBOOT.
So, did anyone try PASSIMG with Korean FRF91?

Jack_R1 said:
Did you see that?
http://androidforums.com/1533396-post14.html
Or is it the only report? (in that case, the guy probably didn't try to run root).
Anyway, being unable to root makes you unable to flash PASSIMG of anything with bootloader lower than 0.35 - but did anyone try PASSIMG with Korean FRF91? It has the same HBOOT as FRG33, so it shouldn't be reported "older".
Click to expand...
Click to collapse
Downloading and testing, thanks for the tip, will report back.

[Q] What is d6096cac5e9f.signed-hboot-0.35.0017.zip ?

Hi,
I'm on MoDaCo r21 (FRF91). Every few days, I get alerts that there's an update. There seem to be some problems that haven't quite been worked out with MoDaCo r22 (FRG83), so I'm holding off on upgrading. So every few days, I get an alert that there's an OTA update available. I go into /cache and delete the .zip file that was downloaded, then "accept" the update, which of course fails because the file isn't there, and then I proceed on my way until it happens again.
Up until recently, it always said the update was "Android 2.2 Update" or something and the filename was
Code:
c8847c98b948.signed-passion-FRG83-from-FRF91.c8847c98.zip
This was, as far as I know, a few minor fixes and was just an update to the /system partition.
Now, I've just noticed that the file I was pushed is
Code:
d6096cac5e9f.signed-hboot-0.35.0017.zip
and this appears to have an hboot.img embedded in it. I don't know how to crack open an .img file, so my question is, what the heck is this update? The update screen says "Update 1 of 2: This is the first part of an update and it must be installed before the second part is installed" or something like that.
I'm getting paranoid here. Is this some trick from HTC to get me to update my bootloader with a locked-down one like the G2?
The thing I love about the Nexus One is that the whole thing can be legitimately unlocked -- so I hope there's not an update that will change that.
I actually rooted my phone without doing the "fastboot oem unlock" as I didn't want to void my warranty (despite the many claims that HTC still honors claims for things that are clearly hardware-related), but I've always felt safe that I have that option in my back pocket in case I ever screw up so bad that I can only recover via fastboot.
Or maybe this is just a new radio and I'm over-reacting
Can anyone confirm? Or point me to some info on how to examine an .img file?
Thanks

I got exactly the same update and I thought it was Gingerbread since this became a 2-part update. I searched around and the new hboot has always been shipped with Korean and SLCD Nexus One(s), and I guess they wanted to update our hboot to the new one as well.
I updated to it, but well you can still install custom roms when you're rooted, and it doesn't affect your current rom as well. So I guess it's perfectly fine, or if someone else wants to correct me.
My bootloader now displays:
NEXUSONE PVT SHIP S-ON
HBOOT-0.35.0017
MICROP-0b15
TOUCH PANEL-SYNT0103
RADIO-4.06.00.12_7
Oct 12 2010,14:33:16

Thread moved to Q&A.

I never got an on-screen prompt about it but I did notice while watching ddms after flashing a new rom that hboot-0.35.0017 was pushed to my phone and the verification failed.
I'm oem fastboot unlocked and running CM 6.1 nightly build 262.
Has anyone determined the new bootloader is needed for future things? i.e. Gingerbread?

can someone please confirm if it is safe to flash to the new 0.35 hboot if I rooted my phone using a locked bootloader method? will flashing the new hboot undo my root or cause any issues?

hayden1987 said:
can someone please confirm if it is safe to flash to the new 0.35 hboot if I rooted my phone using a locked bootloader method? will flashing the new hboot undo my root or cause any issues?
Click to expand...
Click to collapse
Yes, it is safe. And no,you will not lose root.

hayden1987 said:
can someone please confirm if it is safe to flash to the new 0.35 hboot if I rooted my phone using a locked bootloader method? will flashing the new hboot undo my root or cause any issues?
Click to expand...
Click to collapse
Well, so far, the 0.35 hboot won't let you use the PASSIMG method to re-image your phone, and doesn't appear to like Amon Ra 2.0 (not confirmed, but I've noticed a few issues). I've also seen potentially related problems with fastboot privileges...
Sent from my Nexus One using XDA App