• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Confused - Upgrading rooted ERE27 to rooted FRF91

vitalyb

Newbie
May 29, 2010
19
0
Hi guys,

I am sure it's been answered but I failed completely in finding what directions for my exact state and being a n00b when it comes to rooting, I've decided to ask first.

I am currently on rooted T-Mobile's ERE27. This morning I got OTA upgrade, however, when I tried to install it I got the "verification failed" message. After I restarted the phone, I looked at the SD card and found no Update.zip of any kind.

Several questions:
1) Should I wait for an OTA? Will an OTA update work on rooted Nexus?
2) If I have to do it manually, can someone please explain the steps I should take or link me to a guide that fits my state?
3) Will an upgrade, manual or OTA, wipe the phone?

Thanks,
Vitlay
 
1. An OTA will only work with a stock recovery image, one of the first things to go when a phone is rooted. So probably not.
2. Here's a link to xda with a link to frf91 for root users with different recoveries. Download the file and apply as explained in the sticky at the top of this forum (replace update.zip with root.zip)
3. The update SHOULD leave your entire phone intact. However, you are rooted and thus have a greater chance of f'ing something up that'll ruin your phone. Be sure to make a thorough backup.

Good luck!

Sent from Mianus
 
Upvote 0
1. An OTA will only work with a stock recovery image, one of the first things to go when a phone is rooted. So probably not.
2. Here's a link to xda with a link to frf91 for root users with different recoveries. Download the file and apply as explained in the sticky at the top of this forum (replace update.zip with root.zip)
3. The update SHOULD leave your entire phone intact. However, you are rooted and thus have a greater chance of f'ing something up that'll ruin your phone. Be sure to make a thorough backup.
Good luck!
Sent from Mianus

Err, thanks for the answer, but where is the link? :thinking:
 
Upvote 0
Thanks for the link :)

Now it says here (linked from your link):

Update.zip to flash with custom recovery

This is the totally stock FRF91 repacked as update.zip. The radio hasn't changed since FRF50, so if you are using it, you can keep it and install the noradio version.

Download:
- without radio image: multiupload (md5sum: 041b1e21433e636340ca6b56f141a315)

Root

To root FRF91, just flash this update.zip (contains busybox, superuser.apk, su, unsecured boot.img) (md5sum: c6c27598c210576792d6d56738a2edde)

He says The radio hasn't changed since FRF50, so if you are using it, you can keep it and install the noradio version. and supplies the link without the radio update. The way I understand, it means I can't use this link since I am using ERE27 in which the radio IS different than FRF50/91.

Am I correct? In that case should I look for a link to FRF50 and then upgrade to FRF91?

Thanks!
 
Upvote 0
Hi vitalyb.
How did upgrading go from rooted ere27 to frf91?
I have a rooted ere27 and I wannt to upgrade to frf91 as well.
Can you please give me the actual steps you followed?

I've decided to postpone it for a few days to let it settle down more... I was sure that the OTA is going to work for me, didn't realize that rooting will also disable OTA updates =\. I will gladly update the thread as soon as I make the move.
 
Upvote 0
hi did you get a chance to perform the upgrade?

Hey,
Yep, I eventually flashed it with the file from here and it worked fine. I was holding out for no reason, it was truly painless.

Just make sure to take the correct file, if you're rooted, you need the one here:

Root

To root FRF91, just flash this update.zip (contains busybox, superuser.apk, su, unsecured boot.img) (md5sum: c6c27598c210576792d6d56738a2edde)
 
Upvote 0
Hi. I rebooted to recovery mode and the message "E: can't open /cache/recovery/command" showed. I disregarded it and proceeded to install the update.zip file you mentioned above.
But then the following messages showed:

--install from sdcard
finding update package
opening update package
verifying update package
e: signature verification failed
installation aborted

I checked the file's md5 checksum and is ok.
Any ideas as to what may be wrong?
Is the message "E: can't open /cache/recovery/command" related?
I remind you that I have an ERE27 rooted nexus one.

Thanks
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones