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
Related
I have been checking the massive froyo thread since it was on page 7 (now its > 120 pages) but still no love for AT&T/Rogers Nexus one.
My phone is unrooted and running stock rom with Firmware on 2.1-update1 and build EPE54B. Can people who have froyo on their at&t nexus one please post a step by step guide?
Should be the same method and file as that used for the T-mobile compatible phones.
id really like this answered too..i dont want to take a risk and brick my N1.. so far all the guides are ERE27..
The update zip as it stands is only for ERE27-FroYo... sorry.
unleashed12 said:
id really like this answered too..i dont want to take a risk and brick my N1.. so far all the guides are ERE27..
Click to expand...
Click to collapse
pjcforpres said:
The update zip as it stands is only for ERE27-FroYo... sorry.
Click to expand...
Click to collapse
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
I saw many at&t owners have froyo successfully flashed. They flashed to ERE27 first. Does that need rooting?
Thank you for this information.
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
Anyone tried this?
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
the update file is labeled signed-passion-FRF50-from-ERE27.1e519a24.zip
ATT/Rogers version is running build EPE54B. The update is from ERE27 to FRF50
uansari1 said:
That makes no sense.
The guides are ERE27 only because that's the latest Eclair update. You need 2.1 update 1 to be able to jump to Froyo. You guys have the AT&T/Rogers version, which has a newer radio than those of us with the T-mobile compatible versions. If you're on the AT&T version, you already have the most recent update and can simply flash the file everyone's talking about. If it weren't compatible for some reason, the file would not flash and simply give you an error message. So there's no risk here.
Click to expand...
Click to collapse
I guess the 20 pages of 100% stock AT&T guys not being able to flash this are just morons then.
The update zip only lets you go from ERE27 to FroYo. Those with an "AT&T version" and FroYo had to flash ERE27 first... that also means unlocking the boot loader.
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
pjcforpres said:
I guess the 20 pages of 100% stock AT&T guys not being able to flash this are just morons then.
The update zip only lets you go from ERE27 to FroYo. Those with an "AT&T version" and FroYo had to flash ERE27 first... that also means unlocking the boot loader.
Click to expand...
Click to collapse
jasrups said:
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
Click to expand...
Click to collapse
That sucks.
Same problem with the european stock shipping ROM (EPF21B).
Can't wait to be able to get Froyo without unlocking.
my bootloader is unlocked..going to go ahead and try to flash pauls rooted version.
jasrups said:
Yup, AT&T/Rogers folks are going to have to wait unless they want to unlock their bootloader, flash to the 27 build and then update to FroYo.
At this point there's no point to unlock the bootloader if you've waited this long already. Keep your warranty and wait a little longer, I'm sure an update for the Rogers build will surface soon.
Click to expand...
Click to collapse
What a bummer! Yeah I have waited this long to preserve my phone's virgini.. I mean warranty so I guess I'll wait longer.
At least its good to know that the build for at&t and rogers is the same!
I have the AT&T N1, and earlier today I flashed and formatted my phone back to new. I now have Froyo and it's working fine.
Kpow said:
I have the AT&T N1, and earlier today I flashed and formatted my phone back to new. I now have Froyo and it's working fine.
Click to expand...
Click to collapse
is your N1 rooted or stock?
MEGABYTEPR said:
is your N1 rooted or stock?
Click to expand...
Click to collapse
Clearly rooted and unlocked bootloader, otherwise he wouldn't have been flashing anything.
thread title misled me.
eric b
I have successfully flashed Froyo on my (AT&T) N1 with this:
http://android.modaco.com/content/g...com/309286/frf50-froyo-pre-rooted-update-zip/
I previously was on CM 5.0.6 with Amon RA Recovery v1.7.0.
I wiped and installed the update, it did flash a new radio. Rebooted and Froyo was waiting for me!
Hope this helps anyone that is not sure.
Hi All,
A friend of mine has a Vodafone uk Nexus One (whilst I have a Three UK Desire lol), and I used to have a T-Mobile UK G1. One of the things you could do with that (and from experiences with friends' Heros) was create a goldcard and flash a google unbranded image.
Question is, can that be done with the Nexus one? I know how to create goldcards, but I don't see any RUU exe files anywhere. Obviously he'd like to get froyo asap and avoid the voda delays in future too.
So, he doesn't want to do custom roms, just would like to have the option of stock roms and ideally OTA updates when google give them not when voda mess about with them and eventualy release them. He doesn't want to void the warranty though, so as I understand it, fastbooting a .img file is out as he'd have to unlock the bootloader?
--
Martyn
Hmm, unrooted nexii one are able to flash froyo without a goldcard, no idea about branded handsets. I'd suggest finding the link for frf91(latest froyo build) somewhere around these boards, chucking it on the sdcard as update.zip and hope for the best.
Maybe get the noradio .zip first, just incase it goes terribly wrong. I doubt it will though, it will either work or not flash at all, so give it a try.
We tried using a goldcard with an frf91 universal rom (i.e. the direct from google signed zip), but it failed verifiation on the phone's update system. I'm assuming RUU checked for goldcard but the standard recovery ignores goldcards
Anyone got any more suggestions?
Root the phone / unlock the bootloader, and flash whatever you want. There is no "unbranding", since Nexus isn't branded. It's just that there is no stock update that is based on your version (EPF21?), so no update will be executed.
He can try the "non-voiding-warranty" root, though it's specified to work for Froyo. If it doesn't work for him - he can try the PASSIMG.zip way of upgrading to some version that will allow root. If that fails too - oh well... Either root the usual way, unlocking bootloader, or accept the fate.
ranyardm said:
Hi All,
A friend of mine has a Vodafone uk Nexus One (whilst I have a Three UK Desire lol), and I used to have a T-Mobile UK G1. One of the things you could do with that (and from experiences with friends' Heros) was create a goldcard and flash a google unbranded image.
Question is, can that be done with the Nexus one? I know how to create goldcards, but I don't see any RUU exe files anywhere. Obviously he'd like to get froyo asap and avoid the voda delays in future too.
So, he doesn't want to do custom roms, just would like to have the option of stock roms and ideally OTA updates when google give them not when voda mess about with them and eventualy release them. He doesn't want to void the warranty though, so as I understand it, fastbooting a .img file is out as he'd have to unlock the bootloader?
--
Martyn
Click to expand...
Click to collapse
You can try the tutorial at http://bloginblack.de/2010/07/how-t...e-google-nexus-one-from-epf30-to-froyo-today/
I had same issues as my N1 was EPF30 build probably a EU one and the above tutorial helped me get all the new updates OTA, because to the best of my knowledge Froyo is not yet available OTA in EU, atleast that's what i found in google
Cheers
So this morning there was a thread on androidcentral that the official ICS upgrade for the vivid was being pushed out. I got the OTA update, 3.26.502.56, and copied it to my sdcard......but I have no idea what to do with it. If this is not different from the leak floating around feel free to delete this thread
Where did it save it to cause I got it and want to save it before I upgrade.
Sent from my HTC PH39100 using XDA
jsramirez27 said:
So this morning there was a thread on androidcentral that the official ICS upgrade for the vivid was being pushed out. I got the OTA update and copied it to my sdcard......but I have no idea what to do with it.
Click to expand...
Click to collapse
Yeah, maybe try reading or searching. This topic belongs in General, blah blah blah.
Anyway, there's a thread with instructions, but since I'm operating under the presumption that you're not going to follow it, download this RUU, run it, and follow the directions it gives you.
Link.
I doubt you've unlocked your bootloader either, by the sound of it, so I'm not going to tell you to "fastboot oem lock".
I am rooted and unlocked. I know how to perform the update but I copied it to my sdcard so that it could be used for dev purposes. FYI i tried to perform the update and it gave me an error, probly because I am rooted and unlocked
tbone22 said:
Where did it save it to cause I got it and want to save it before I upgrade.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
In downloads, I just copied and pasted using a file manager
jsramirez27 said:
I am rooted and unlocked. I know how to perform the update but I copied it to my sdcard so that it could be used for dev purposes. FYI i tried to perform the update and it gave me an error, probly because I am rooted and unlocked
Click to expand...
Click to collapse
I have absolutely no idea what you're on about.
So you downloaded VIVID_ICS_OTA_ROOT.zip or whatever and you tried to CWM it?
The instructions from where you downloaded it from should have either given you a PH39100.zip to update your HBOOT before you reflash recovery and then the ICS zip. You MUST lock your bootloader before you use the PH39100 update zip.
If you have only a PH39100.zip image, you MUST LOCK YOUR BOOTLOADER, otherwise it will not work. Again, it should have been very clear from wherever you got the zip from.
What sort of crap site didn't tell you these things?
EDIT: Did you get this from ATT Software Update? That's probably the worst way to get this update. I'm also pretty sure you need to relock for that too.
Aus_Azn said:
I have absolutely no idea what you're on about.
So you downloaded VIVID_ICS_OTA_ROOT.zip or whatever and you tried to CWM it?
The instructions from where you downloaded it from should have either given you a PH39100.zip to update your HBOOT before you reflash recovery and then the ICS zip. You MUST lock your bootloader before you use the PH39100 update zip.
If you have only a PH39100.zip image, you MUST LOCK YOUR BOOTLOADER, otherwise it will not work. Again, it should have been very clear from wherever you got the zip from.
What sort of crap site didn't tell you these things?
EDIT: Did you get this from ATT Software Update? That's probably the worst way to get this update. I'm also pretty sure you need to relock for that too.
Click to expand...
Click to collapse
I dont think ure understanding what I am saying, I am not referring to the leak, this is the official OTA ICS update from AT&T. I know that I need to relock to install, I dont want to do that because I dont want to lose root. I'm posting so that devs can root and do whatever else with this.
Aus_Azn said:
I have absolutely no idea what you're on about.
So you downloaded VIVID_ICS_OTA_ROOT.zip or whatever and you tried to CWM it?
The instructions from where you downloaded it from should have either given you a PH39100.zip to update your HBOOT before you reflash recovery and then the ICS zip. You MUST lock your bootloader before you use the PH39100 update zip.
If you have only a PH39100.zip image, you MUST LOCK YOUR BOOTLOADER, otherwise it will not work. Again, it should have been very clear from wherever you got the zip from.
What sort of crap site didn't tell you these things?
EDIT: Did you get this from ATT Software Update? That's probably the worst way to get this update. I'm also pretty sure you need to relock for that too.
Click to expand...
Click to collapse
No, he was just wondering if it is the same one that is one here. because the ones we have been using are leaks. There have been rumors that some are sense 4.0 instead of 3.6
jsramirez27 said:
I dont think ure understanding what I am saying, I am not referring to the leak, this is the official OTA ICS update from AT&T.
Click to expand...
Click to collapse
There was no leak... The RUU is the official HTC RUU for the ICS update.
The "leak" you speak of was made from an OTA update pushed to one of the first recipients of the Vivid's ICS. Versions .52, .54 and .56 are all essentially identical.
Aus_Azn said:
There was no leak... The RUU is the official HTC RUU for the ICS update.
The "leak" you speak of was made from an OTA update pushed to one of the first recipients of the Vivid's ICS. Versions .52, .54 and .56 are all essentially identical.
Click to expand...
Click to collapse
This is what I was trying to find out. So this OTA is nothing new.
jsramirez27 said:
This is what I was trying to find out. So this OTA is nothing new.
Click to expand...
Click to collapse
That's what I am wondering too. Why we have 3 versions of a 2 week old update?
As some of you may know my Razr i had mysteriously ended up stuck on 29004 retail.en.GB, which is apparently earlier than what GB phones shipped with (blame ebay).
I'm happy to unlock the bootloader etc but it would help if I knew exactly how to get from my current version to the latest JB release. I wasn't sure about flashing the upgrades as usual since none of them have a step to get from this version to any further.
Any help?:silly:
Thanks,
Addam.
addam360 said:
As some of you may know my Razr i had mysteriously ended up stuck on 29004 retail.en.GB, which is apparently earlier than what GB phones shipped with (blame ebay).
I'm happy to unlock the bootloader etc but it would help if I knew exactly how to get from my current version to the latest JB release. I wasn't sure about flashing the upgrades as usual since none of them have a step to get from this version to any further.
Any help?:silly:
Thanks,
Addam.
Click to expand...
Click to collapse
Just flash the fastboot files from Mattgrof, they are very safe to use and you don't have to worry about updating in a specific order.
arceles said:
Just flash the fastboot files from Mattgrof, they are very safe to use and you don't have to worry about updating in a specific order.
Click to expand...
Click to collapse
Thank you. It was mainly the order I was worried about.:good:
I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance
pokedroid said:
I am currently on 5.1 but work for at&t. I just put my work email on my phone that also requires a monitoring service called mobile iron that monitors my phone. My company now thinks my phone i rooted because I have "prerelease" software on my phone and am in danger of getting in some pretty serious trouble. I talked it over with my manager and they're giving me time to fix it, but I need to get off 5.1 as fast as possible.
I can't root and I can't unlock bootloader but I need to get off 5.1.... can i just flash a 5.0.1 ota zip? Really not sure what to do but don't want my company phone taken from me. all my clients know this number.
Thanks in advance
Click to expand...
Click to collapse
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.
You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?
ac3theone said:
I think the only way to downgrade the version is to flash through the bootloader or flash a custom rom but you can't do either, but 5.1 is officially out so its no longer pre release software.
Click to expand...
Click to collapse
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
rootSU said:
You have to unlock the bootloader to flash anything. No you cannot flash an older ota (ota patch existing files to new versions, not replace entire files) and as mentioned l, 5.1 is not pre-release.
How did you get 5.1 in the first place?
Click to expand...
Click to collapse
I just installed it as an update.zip using adb. No unlock required.
pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
FYI, AT&T have no control over the update process. The update comes directly from Google, for all carriers. As long as you didn't install M or I, you're fine. There is nothing that AT&T could do to prevent anyone getting the update. Except maybe sending a memo out to a staff saying "you'll receive an update from Google. Please, please, please don't accept it"
pokedroid said:
At&t hasn't approved the software I guess, so by their standards it's considered prerelease. I honestly don't see why it's even an issue, we use the exact same images that gpe versions get so it shouldn't matter. Not sure what to do at this point.
I just installed it as an update.zip using adb. No unlock required.
Click to expand...
Click to collapse
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.
ac3theone said:
Id say get a tmobile sim card and use that and that way they cant say your on lre release software since tmo just pushed the 5.1 update.
Click to expand...
Click to collapse
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung
rootSU said:
Again, the carriers don't push the updates. They all come from google. Its not the same as other OEMs like Samsung
Click to expand...
Click to collapse
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?
ac3theone said:
Can't you root and go back to 5.0 and relock bootloader and reinstall the mobile iron app?
Click to expand...
Click to collapse
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0
rootSU said:
Doesn't need root. He could unlock the bootloader, willing the device and then flash the system.img and ROM.img for a 5.0 ROM. Then relock
But its pointless. 5.1 has been released to both versions on the nexus 6. The north American one and the international one. AT&T do not.control updates going to their "branded" nexus 6 device. They're coming from Google directly.
Edit..
Hmm maybe I'm wrong...
http://www.phonearena.com/news/Turn...akes-a-little-extra-effort--heres-how_id67599
Maybe like tmo, Google will be releasing a different 5.1 for at&t. This is disappointing news for nexus devices.
So yeah, unlock BL and flash system.img and boot.img from 5.0
Click to expand...
Click to collapse
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*
pokedroid said:
Its not a different 5.1, but they delay the updates. As soon as the update is apppved it won't be considered "prerelease" and everything will be fine. It's a complete formality. But, it is what it is. I guess I'm going to just pull my email off my device and hope the "trackability" breaks. Not willing to risk boot loader unlock as I'll have to give the device back at some point. Again, as long as I don't put any "at-risk" firmware on the device and relock it shouldn't make any difference, but it does.
*sigh*
Click to expand...
Click to collapse
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,
rootSU said:
You can unlock the bootloader and relock it (so long as you check it boots first). There isn't a flag or trip or anything that they will see.,
Click to expand...
Click to collapse
Oh, I was thinking the boot loader status would show "relocked" when in fastboot