Related
[SIZE=+3]FlashBack21 v2 - Return to Factory 2.1 Stock - March 2011 OTA[/SIZE]
Note1: This ROM supersedes the (former) "FlashBack15" ROM as of 2010/10/20. This step was taken because it appears that VZW/Google are no longer providing Cupcake->Eclair OTA downloads for the Eris.
Note2: The V2 FlashBack21 ROM installs the stock HTC software corresponding to the March 2011 OTA version V2.41.605.6. The V1 FlashBack21 ROM installs the stock HTC software corresponding to the July 2010 OTA - version V2.37.605.4
[SIZE=+2]Last Updated: March 06 2011[/SIZE]
This ROM is intended for reverting a rooted Eris with a custom recovery to the HTC stock software: March 2011 2.1 OTA ROM - v 2.41.605.6. There are many other ways to do this; but this way uses Amon_RA for the installation as a convenience for less experienced rooters. (And only Amon_RA v1.6.2 - the installer will refuse to work with any other recovery.)
Two versions are provided: one which flashes the radio firmware version 2.42.01.04.27, and one which does not flash the radio; other than this difference, they are identical. (The same radio firmware - v2.42.01.04.27 - was used in both the July 2010 & March 2011 OTA releases.) Choose the ROM which best fits your needs. If you already have the most recent radio installed (2.42.01.04.27), there is no need to reflash the radio.
File name: "FlashBack21_v2.zip" (download link and md5 sigs below).
File name: "FlashBack21_v2_noRadioFlash.zip" (download link and md5 sigs below).
Derived from the Eris "March 2011 OTA" (2.41.605.6) release, this ROM repackages the last official 2.1 ("Eclair") release for the Eris from HTC/VZW so that it can be installed with Amon_RA recovery - you flash it just like any other dev ROM. There are essentially no customizations, and no built-in root or extra tools; it is 99.99% stock, with the following difference:
- This ROM also performs jcase's "Flash Any RUU" patch to the misc partition during the flashing process.
This step is performed so that the Eris responds well to flashing operations involving the use of any PB00IMG.zip file (via HBOOT), or application of any RUU utility for the Eris. So, even though this is an "unrooting" ROM, pains are taken to make sure that it is easy as possible to re-root or manipulate with existing methods.
This ROM does not touch the bootloader (or "Hboot" or "IPL/SPL"). If you want to install a different bootloader, do it first before applying this ROM.
[SIZE=+1]Please Note: THE RECOVERY BOOT PARTITION IS REPLACED BY THE MATCHING VERSION OF THE STOCK RECOVERY PARTITION (V2: March 2011 OTA; V1: July 2010 OTA) in this ROM. This means that you will need to re-root your phone if you use this ROM, should you later decide that you want to restore a different ROM.[/SIZE]
[SIZE=+1]Please Note 2: ONE OF THESE ROMs FLASHES A RADIO. This is different than nearly 99% of all Eris dev ROMs. You will see some activity at the conclusion of your Amon_RA recovery session as a result of this - if you choose to use the ROM version that flashes the radio firmware.[/SIZE]
[SIZE=+2]Instructions[/SIZE]
- Read this whole post all the way through before you begin
- Charge your phone completely
- Download the .zip file you need to the top-most folder of your SD card
- Verify the length and/or MD5 checksums (of the copy of the ROM file on the SD card)
- Boot into the Amon_RA recovery, Wipe, and then flash the FlashBack21 ROM (of your choosing)
IF YOU ARE FLASHING THE RADIO:
- When flashing is complete, you will see the message at the bottom of the screen:
"Reboot via vol-up+vol-down or menu to complete installation"
- Make sure to exit Amon_RA after the ROM has finished flashing by selecting the "Reboot now" top-level menu item. Don't do something stupid like pulling the battery.
- You will see two successive splash screens that you do not normally see when using Amon_RA - these indicate that the factory recovery boot is performing the radio flashing operation. Do not interrupt - the phone will reboot on it is own when this step completes.
[SIZE=+2]Acknowledgments[/SIZE]
- Amon_RA for his recovery boot
- jcase for his disclosure to the Eris community of the misc partition "main version number" patch
- hundreds of others on XDA and AF too numerous to mention
- doogald for re-hosting the ROMs (2/15/2012)
[SIZE=+2]Downloads - V2 - March 2011 OTA - v 2.41.605.6[/SIZE]
(Thanks to XDA user doogald for hosting these downloads!)
[SIZE=+1]Flashes Radio !!!![/SIZE]
FlashBack21_v2.zip ( 109,245,758 Bytes; MD5: 3c770473e18e539afe5d090b4a5462ca )
[SIZE=+1]Same ROM, but does NOT flash Radio[/SIZE]
FlashBack21_v2_noRadioFlash.zip ( 102,181,672 Bytes; MD5: d0137efb10dd714cf3770e5ff7b842f5 )
[SIZE=+2]Downloads - V1 - July 2010 OTA - v 2.37.605.4[/SIZE]
(Thanks to XDA user doogald for hosting these downloads!)
[SIZE=+1]Flashes Radio !!!![/SIZE]
FlashBack21_v1.zip ( 108,784,952 Bytes; MD5: 416a92afe52d87beccbef29380a2009f )
[SIZE=+1]Same ROM, but does NOT flash Radio[/SIZE]
FlashBack21_v1_noRadioFlash.zip ( 108,784,967 Bytes; MD5: 44bff966290bb02c0b70ae06ef95d719 )
(Note that both V1 ROM files include the radio image, even though the latter does not flash this firmware - that is why the file sizes are nearly identical.)
OBSOLETE & DEPRECATED - Flashback15_v1
Thanks to XDA user doogald for hosting this download!
- This is here for historical purposes only.
- Note this now ONLY provides a Cupcake (Android 1.5) Factory roll-back for the Eris, as VZW/Google are no longer providing OTAs for the Eris.
- Do not use unless you specifically want a stock "Cupcake" (Android 1.5) Eris
- Note this ROM also UNROOTS YOUR PHONE by replacing the custom recovery with the stock recovery
FlashBack15_v1.zip ( 94,011,341 Bytes; MD5: e5e7ab9f3bc3314f28543fd88ae296fd )
bftb0
Thanks, sounds like this could come in handy!
Yep thanks .... will make it easy when I send this phone back for my 5th eris
This should be stickied up to...Good work!
Nice. Agree this should be sticky
Very nice thank you!
Sent from my Eris using XDA App
Awesome work
Awesome. I agree - lets make this a sticky.
Sent from my nonsensikal froyo using XDA App
Just used this... Worked like a charm. Excellent work and thanks.
This is gonna help out alot of people.
ill be using this in the next few days, got to return my eris cuz trackball is going out :/
TopazAaron said:
ill be using this in the next few days, got to return my eris cuz trackball is going out :/
Click to expand...
Click to collapse
Note that this ROM does not replace the bootloader - so, if you have the engineering bootloader on your phone, you might just want to flash the MR2 RUU (or the corresponding PB00IMG.zip) immediately after booting this (no point in doing the OTA twice). Or, for folks that know their way around fastboot, if they have the S-OFF bootloader, there is always the option to put an S-ON bootloader back onto the phone thusly[SIZE=+1]**[/SIZE]:
Code:
fastboot flash hboot hboot_7501a_1.47.0000_091023.nb0
I did things this way (no replacement of the bootloader) because most of the folks that did their Eris rooting the "old school" way - and have the Engineering bootloader on their phone (1.49.2000 S-OFF) are comfortable using adb or fastboot, et cetera - and probably have enough knowledge to manually replace their bootloader; whereas the late-comers to the rooting party (leakers and others) that are not familiar with these methods probably used "one click" or similar, so they probably don't have the S-OFF bootloader on their phone anyway.
If I was going to return a phone to VZW, and was concerned that a computer forensics expert was going to examine my phone (I'm 99.999% confident that this does NOT happen), I would apply the MR2 and then take the OTA after that.
Here are the reasons why (these are really only motivations for the ultra-paranoid):
- None of the dev ROMs have ever touched the "NVRAM" area of the phone, whereas the "leak" PB00IMG.zip ROMs did manipulate that. So, phones that went through a leak-flash install still have evidence (in NVRAM) that they have been flashed with unofficial software releases (from HTC), even if the so-called "ROM" has been replaced. The only way to over-write that is to re-write the NVRAM using a VZW-sponsored RUU (or corresponding PB00IMG.zip file). In my mind, that is the MR2, not the "Official" ( == Leak-V3) RUU.
- The same thing is true of the "misc" partition - evidence of fooling around with HBOOT+PB00IMG.zip files persists in the misc partition if you do not take steps to overwrite it. (I flashed and rooted my phone an absurd number of times yesterday (for testing), and right now my misc partition reports "2.19.605.1" because the last thing that I did was install the S-OFF bootloader using HBOOT and the battery-pull trick).
- Forensic evidence in the form of directory or file timestamps probably can determine if a phone has a non-factory, or non-RUU software on it. The same thing is probably true of very low-level (yaffs2) filesystem storage order - there is no reason to believe that the file storage order (relative to the linear page layout of flash memory) will be preserved with a non-stock installer.
But, as I said, the above considerations are for the truly paranoid. VZW doesn't look at phones that carefully, and probably can not for economic reasons - and all the things I mentioned above can not be determined easily (for instance by a retail clerk looking at the booted phone)
But in a way, it doesn't matter anyway - because of the "checkin" process that happens every time the phone boots up, and the pattern of phone activations or market history, Google and VZW have enough information available (between them) in the form of user activity that they could identify every rooted Android user on the VZW network - if they cared enough to do so.
As I said, if I were going to return a phone, I would do the "misc" partition hack, install the MR2 RUU (or matching PB00IMG.zip file), and then take the OTA - and then finally perform a factory reset. But even that is probably far more effort than is necessary.
bftb0
[SIZE=+1]**[/SIZE] Flashing the bootloader is the single most dangerous operation you can perform. Make damn sure the file you are planning on flashing has the correct MD5 signature, as "fastboot" does not check a single thing - it will allow you to flash total garbage to the phone.
I'm shipping back an Eris which I used this method on to remove root, but don't have time to do the 2. 1 update, do you think VZW cares that its running 1. 5?
Sent from my FroyoEris using Tapatalk
eriscentro said:
I'm shipping back an Eris which I used this method on to remove root, but don't have time to do the 2. 1 update, do you think VZW cares that its running 1. 5?
Click to expand...
Click to collapse
Doubt it matters. It takes about 20 minutes for the full OTA 2.1 update, but once you kick it off, the entire process requires no interaction - go do something else for 20 minutes.
You might also want to do a factory reset using the the phone's menu - that will clear the activation status of the phone.
ok... I read bftb0's post... but not sure I'm following
I did the universal one click root method to root my phone and I'm not sure if I need to go to the trouble of flashing something to fix the bootloader or w/e...(not sure if I even messed with the bootloader, maybe I did but this is the noob coming out in me)
If I wanted to send my eris back today to verizon, wouldn't flashing this new zip fix everything I need it to fix and make it comepletely back to its original stock settings??
NPH- said:
ok... I read bftb0's post... but not sure I'm following
I did the universal one click root method to root my phone and I'm not sure if I need to go to the trouble of flashing something to fix the bootloader or w/e...(not sure if I even messed with the bootloader, maybe I did but this is the noob coming out in me)
If I wanted to send my eris back today to verizon, wouldn't flashing this new zip fix everything I need it to fix and make it comepletely back to its original stock settings??
Click to expand...
Click to collapse
Except the bootloader and radio.
Sent from my xtrSENSE Eris using XDA App
NPH- said:
ok... I read bftb0's post... but not sure I'm following
I did the universal one click root method to root my phone and I'm not sure if I need to go to the trouble of flashing something to fix the bootloader or w/e...(not sure if I even messed with the bootloader, maybe I did but this is the noob coming out in me)
If I wanted to send my eris back today to verizon, wouldn't flashing this new zip fix everything I need it to fix and make it comepletely back to its original stock settings??
Click to expand...
Click to collapse
You will be fine. The radio gets flashed by the 2.1 OTA, and you never replaced your bootloader with the one-click method, so that is already stock.
If it happens that you were one of the "leakers", then you have the 1.49.0000 S-ON bootloader, and VZW has shipped phones with that, too.
Be happy.
bftb0
I found that I couldnt re-root the phone with this flashback. I ended up using the PB00IMG.zip file on the SD card and let the phone do itself over. No luck on this one.
Used this today, walked into Verizon store. They looked at it. Sending me a new one as we speak. THANK YOU!!!
on my 5th
rvpartsguy said:
Yep thanks .... will make it easy when I send this phone back for my 5th eris
Click to expand...
Click to collapse
This will make it easier when i get my 6th..
Just received my 5th...lol
Heard as stock runs low for replacements, in certain areas, they are receiving a Droid 2... Can anyone confirm????
I just got my droid X, and heard that the froyo update ota was having a lot of bugs and such, but that was a while back. My droid is still in 2.1, is it best to leap onto 2.2, or just stay at 2.1 until 2.2 bugfixes are made? thanks.
It's got its bugs. Battery Manager details crashes most of the time (Vz found the issue in early Oct and will inlcude in a soon to happen maintenance release) and exchange push doesn't work unless you're on E2K10. Most everything else reported (slowness/lag) is because ppl didn't hard reset after the OTA push.
Not the best release on the planet but worth it IMO.
I'd update and the do a factory reset (wipe data/cache). If you don't want to reset your phone don't bother. It will have issues.
I've noticed huge improvements regarding battery life. Also, having Flash has been nice, I've used it quite a bit with Local News sites. But yes, there are bugs. You will definitely want to do a hard reset after update, or else you'll constantly get apps needing to be forced closed and it will run sluggish.
Get Appbrain before hard reset, it will sync and push all your apps back after reset. Quite nice for lazy people like me.
Same kinds of questions. Droid X, still at 2.1, rooted with EasyRoot, and I have heard all kinds of conflicting info on the upgrade to Froyo and its many variations.
I know enough to be dangerous, and not enough to feel safe.
First, I have downloaded all the TeamBlackHat ROMs including their deodexed 2.3.1.5, and I think I perhaps would like to try that one first, if it is any better than the Verizon standard upgrade.
It is, or does it have the same issues?
Is any other ROM better and more stable ... eg the Tranquility 3 from the BlackHatters?
I hear that the EasyRoot does not work with the Froyo ... and does the phone stay rooted if I do the ROM, does it risk a crash and burn in the middle of the process, should I do the SuperOneClick rooter either now to replace EasyRoot or later or both or.....??
Can I start from where I am, or do I need the Verizon upgrade first or some other way to go?
Am I asking the right questions here? I have read so much about bricks on the upgrade process, especially with the early Froyo leak, and do not know just what to do. The answers on the web keep changing.
Thanks for any help and advice!
Don't worry about bricks. That's why we have the SBF. It fixes that. Also, upgrade to OTA then swap ROMs. If I'm not mistaken, the new ROMs run on the newest bootloader.
Verizon upgrade to Froyo and then ROM remaining questions
Thanks ... am downloading the SBF now in the form of the_gift2.zip so I have it if I need it.
So I understand that I do the Verizon official Froyo update, then I guess I need to reroot the phone as mentioned above (?). Then I can do ROM installs from that point, and have the SBF as a failsafe if it messes up (?)
Anything else that I need to know or be ready for?
Does re-doing the root now with SuperOneClick do any good, or will it all need to be redone after the Verizon update? The root issue is my biggest question. Do I need to kill EasyRoot , and should I go to superoneclick now, and will it hold through the Vz upgrade?
Seems I need the hard reset in the middle of this, after Vz install, with data/cache wipe, as Sleuth225 and Toddman mentioned above, (preceeded by Appbrain backup of the data), ... but is it needed if I will go to a subsequent ROM install such as the TeamBlackHat 2.3.1.5 anyway (That is, will the ROM install fix the issues mentioned by Toddman and Zehkaiser above?).
Maybe this is a dumb question, but I am just trying to understand the steps. I have Titanium backup rooted, but again, if I loose root, will that one leave me hanging without a way to get back? Is Appbrain the one that is most reliable for this situation?
I really appreciate the help ... am a noob at this and tying to learn as fast as I can. Want to be sure I get it right the first time.
So first of all my tablet is brand new and not rooted and I don't want to root it.
When I got it I could update it instantly from 3.0.whateverwastheversionatthetime to android 3.2 (build 7.006.01_COM_GEN1) but it won't go from there to 3.2.1 which I hear is available for my location (France) The update tool tells me that my firmware is up to date.
I've tried a factory reset as advised by Acer customer care services but it wouldn't change. Also no matter what I do (empty cache etc.) the market won't update to Google Play Store and I think the two issues are related.
So I have two (or rather 3) questions:
1) Does anyone know a way around to force the update? (I doubt it's possible but hey "l'espoir fait vivre")
2) If not can I install a stock ROM without root and NOT compromise the warranty?
3) Where can I get such a ROM? I have searched here and here but 3.2.1 is not on the first thread and the links on the second thread are broken, plus I want to make sure that the ROM is the proper one for my region and that comes the ICS OTA update I will have no troubles doing the update.
Thanks in advance to those who will answer.
lunaticwraith said:
So I have two (or rather 3) questions:
1) Does anyone know a way around to force the update? (I doubt it's possible but hey "l'espoir fait vivre")
2) If not can I install a stock ROM without root and NOT compromise the warranty?
3) Where can I get such a ROM? I have searched here and here but 3.2.1 is not on the first thread and the links on the second thread are broken, plus I want to make sure that the ROM is the proper one for my region and that comes the ICS OTA update I will have no troubles doing the update.
Thanks in advance to those who will answer.
Click to expand...
Click to collapse
1) No you cannot force an OTA
2) It depends - others have reported returning there acer with no probs -, i think someone has even returned it rooted and been ok. These things are fairly bulletproof, and really hard to 'brick'. As long as you can read, follow a few steps you shouldnt have any probs. The worse thing you can do is try 2 or 3 different methods all at once because something isnt working right. You're best to pick one and stick with it, if you have probs ask for help in the thread you got the rom from or start your own like you have here
3) The update.zip method from the first link you posted "should" work. Did you "decrypt" the file you downloaded before extracting the update.zip??
You could try timmyDeans v4 method- it will install a stock 3.2.1, it is rooted but you can remove root using the tools he provides. Beware though this will wipe all data so backup anything essential.
The update.zip method will leave your data and settings intact
As always the choice is yours, there are some really excellent custom roms out there - I enjoy the best of both worlds with a backup of my trusty stock 3.2.1, I flash to my hearts content knowing I can always go back to it when the OTA update is out!!! Oh the joys of root priveleges
Thanks for your input, I'll make sure to try all this when I get back from work. I've a few additional questions:
1) If I install a custom rom, will the OTA work from this ROM or, comes the OTA, will I have to restore my actual Stock rom and then proceed with the OTA?
2) I haven't tried the rom on the first link I gave because it is modified and I was searching for the original, pristine, untouched stock ROM for 3.2.1
I've seen such roms around here on xda for 3.2 but none for 3.2.1, if anyone stumbles upon one please let me know.
3) Since I'm still looking for a pristine ROM before trying anything else, I have a friend whose tablet (same brand and model) safely updated to 3.2.1, is there a way to make a rom from is gear? If yes, how to?
4) (related to 3) how can I backup my actual ROM, do I have to be a root user to do so?
THX again!
lunaticwraith said:
Thanks for your input, I'll make sure to try all this when I get back from work. I've a few additional questions:
1) If I install a custom rom, will the OTA work from this ROM or, comes the OTA, will I have to restore my actual Stock rom and then proceed with the OTA?
2) I haven't tried the rom on the first link I gave because it is modified and I was searching for the original, pristine, untouched stock ROM for 3.2.1
I've seen such roms around here on xda for 3.2 but none for 3.2.1, if anyone stumbles upon one please let me know.
3) Since I'm still looking for a pristine ROM before trying anything else, I have a friend whose tablet (same brand and model) safely updated to 3.2.1, is there a way to make a rom from is gear? If yes, how to?
4) (related to 3) how can I backup my actual ROM, do I have to be a root user to do so?
THX again!
Click to expand...
Click to collapse
1. Typically, most people do not take OTA's when running a custom rom, as basically the OTA installs a totally fresh factory Rom. This is true with the 3.2.1 update, which contains a new bootloader. Usually, this means you lose root, and Recovery, then stuck with downgrading to get these things back.
Timmy Deans root tool supposedly maintains a back door method, which s supposed to protect root, in case of an OTA. No, I haven't used this method, as I run my own 501 roms.
2. Vache has a thread "full package and updates" in the 500 Dev forum. There are several factory Roms and Updates. You'll have to look. Chances are, he may not have the specific Com Gen version you want, but probably one close enough.
3. If your friend can get adb running, you can pull a "system dump", which will dump all files/folders in the system folder. The boot.img would be nice to get, but you can probably use the current one you have. Unfortunately, he already rebooted, so you probably can't get the original full update file. If he's rooted, you can use an app called Rom Factory, to get most of what you need. It's always a good time to become familiar with ADB.
4. Well, you can back it up internally, but it's sort of useless if you can't get into your OS You will need to Root, and install a custom recovery to keep your backup externally.
Moscow Desire said:
2. Vache has a thread "full package and updates" in the 500 Dev forum. There are several factory Roms and Updates. You'll have to look. Chances are, he may not have the specific Com Gen version you want, but probably one close enough.
Click to expand...
Click to collapse
ok, as Moscow has pointed out, in vaches thread not all roms are listed. My stock roms (1.016.01 and 1.139.04) for instance weren't - so I spent the last hour or two trying the "EUU gen1" listed at the bottom of the page. Well, it actually worked!! It gave me an OTA to 1.139.04 straight away. After that installed i got the 4.010.40 to 3.2 and then the next 2 for 3.2.1 - 7.006.03 and 7.014.15. So its given me the correct updates for my country AND kept my data and settings too.
SO, since you're on a Gen1 Rom this should work for you too, but still no gaurantee you will get the OTA to 3.2.1, no harm in trying though
btw timmydeans method is a gen2 rom so you can rule that out...
---------- Post added at 11:25 PM ---------- Previous post was at 11:16 PM ----------
just came across this link for an update to stock 3.2.1 build 7.014.14 here - orignal thread here but you need cwm to install it....
unless you can make it into an update.zip???
but thats way outta my league,
moscow may be able to suggest something though
Thank you very much, your answers help a lot! Just a few precisions and I'll stop being a pain in the ass!
1. Typically, most people do not take OTA's when running a custom rom, as basically the OTA installs a totally fresh factory Rom. This is true with the 3.2.1 update, which contains a new bootloader. Usually, this means you lose root, and Recovery, then stuck with downgrading to get these things back.
Click to expand...
Click to collapse
==> @ Moscow, when you say "lose recovery" does it mean I lose the green thingy with gears when I start with volume down and power pressed/ and when I reset to factory settings?
==> @dibb_nz your method is the closest to what I'm looking for, I also hope it will give me the correct updates for my country and since Vache is a fellow countryman it might just be ok.
Anyways thanks again, I'll give a thorough look to all of your solutions and try and do a few things tomorrow afternoon. I'll keep you posted in case this thread interests anyone else.
lunaticwraith said:
==> @ Moscow, when you say "lose recovery" does it mean I lose the green thingy with gears when I start with volume down and power pressed/ and when I reset to factory settings?
Click to expand...
Click to collapse
No, what I meant to say, is when you run a rooted "custom" Rom, and use a "custom" recovery such as RA Recovery or CWM, getting an OTA update, usually wipes that out, and installs the factory bootloader. Your factory recovery....cough cough.... will still be there.
If you are only concerned about stock factory, then don't worry about it. You;re ok. Your factory/stock recovery will be just fine
The reason we root and install custom recoveries, is so we can do 3 primary things.
1. Flash a custom rom
2. Create a complete system backup to our external SD card.
3. Get rid of pre-installed useless apps.
There are other things we can do with it, but these are the primary reasons.
When you have a default factory stock system, the only protection you have, is a factory reset (hope it works), and a couple other methods which require a touch more knowledge.
Anyhow, don't worry about your factory recovery. It's just fine.
1) Just for the sake of knowledge what's the difference between GEN_1 and GEN_2? (and GEN3 and CUS7 and EMEA_TMLP)?
2) @Dibb_nz when you tried with the stock rom from Vache, was it because you encountered the same no FOTA update problem as I did? Or just to try...?
3) Something's still unclear to me after browsing through the forums: If I get an unmodified stock ROM can I flash it with the stock recovery? (so without rooting) Or do I need CWM (so root is needed)
4) What's EUU? (on Vache's thread some roms are listed as EUU)
lunaticwraith said:
1) Just for the sake of knowledge what's the difference between GEN_1 and GEN_2? (and GEN3 and CUS7 and EMEA_TMLP)?
2) @Dibb_nz when you tried with the stock rom from Vache, was it because you encountered the same no FOTA update problem as I did? Or just to try...?
3) Something's still unclear to me after browsing through the forums: If I get an unmodified stock ROM can I flash it with the stock recovery? (so without rooting) Or do I need CWM (so root is needed)
4) What's EUU? (on Vache's thread some roms are listed as EUU)
Click to expand...
Click to collapse
1. The Gen's usually signify regional based roms. More specifically language support, sometimes a wifi tweak, and maybe a couple other things. Mostly though, ComGen1's are for the US and probably canada, and offer about 12 different languages. TMPL is for East Europe mostly, with polish as the default language. All roms contain the english language as far as I know.
3. You basically can't install a full rom on an unrooted tablet without CWM or RA Recovery. You will have to run the update (decrypt the file, remove the update.zip)
4. EUU is a pc based install. Plug in the USB, set your tab to APX mode and run the EUU.
If you did the root, and install a custom recovery, then you could run just about all the full roms. Your custom recovery would be overwritten, and you would lose root access. You would have a stock tablet with the version rom you selected.
You can always wait a week or so. Am sure if the update has been pushed to your country, it's just a matter of time till you get it. It's common for the update process for specific roms, to get fully done in 2-3 weeks. It took well over a week just for users in california to mostly start getting updates.
Well the official release date for the ICS FOTA in France is May 3rd, so I'll wait until then but having other options and the know-how to take actions is always a good basis. (plus I'm really not the patient type ^^)
Stupid question but I'm guessing EUU needs root too?
and also APX means rebooting while holding power and volume - right?
lunaticwraith said:
Well the official release date for the ICS FOTA in France is May 3rd, so I'll wait until then but having other options and the know-how to take actions is always a good basis. (plus I'm really not the patient type ^^)
Stupid question but I'm guessing EUU needs root too?
and also APX means rebooting while holding power and volume - right?
Click to expand...
Click to collapse
I tried the EUU just to see if it would keep me on my regions OTA upgrade path.
Sometimes you can have probs OTA'ing if you aren't using the rom from your region.
But in this case it gave me the correct OTA's.
APX is Acer Download mode, where the OTA upgrades are flashed - this EUU will do it via your PC. Button push method (power/reset button) not required.
No, the EUU does not need root which is why I tried it out for you
You will need to be on 3.2.1 before you will receive the ICS update
I used this EUU from vaches thread -
EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
late for work will check back later
That's really helpful thanks I'm downloading the same EUU you used and will try it today or tomorrow depending on how much time I have, will keep you posted!
Ok so I did the EUU install and it worked fine, the tablet then allowed me to upgrade to 3.01 and then 3.1 then 3.2 via FOTA without any problem. But once I reached 3.2, the update tool informs me that there's no update available and my gear is up to date
So my guess is Acer France are not pushing the 3.2.1 FOTA update anymore...
Any other explanation?
lunaticwraith said:
Ok so I did the EUU install and it worked fine, the tablet then allowed me to upgrade to 3.01 and then 3.1 then 3.2 via FOTA without any problem. But once I reached 3.2, the update tool informs me that there's no update available and my gear is up to date
So my guess is Acer France are not pushing the 3.2.1 FOTA update anymore...
Any other explanation?
Click to expand...
Click to collapse
Glad to hear u got thru the EUU process OK, not so great u still can't ota to 3.2.1
Others have reported similar issues not sure if/how they were ever resolved. As moscow posted earlier,ota,s are not made available to all users in all regions, all at once, so it may be just a matter of waiting for the next "push cycle" to roll round.
At least you know you can always get back to stock if you ever decide to root and go custom There no direct root method for 3.2, just use that same euu to get back to 3.1 and use iconia root and Acer recovery installer from the market and you're ready to flash your rom of choice
Pls post back if u do get the ota - best of luck
rgds Donna
Yeah I was just browsing the XDA forums, contemplating the idea to rollback and root and then installing this
I wonder if it's worth waiting for the OTA... as for what you said about waiting for the next "push cycle" I've been waiting since I got the tablet and the update hasn't come yet, which is strange because the ICS update is due on May 3rd in France and I'd guess they'd have everyone up to date and ready for the update by now!
Rooting seems pretty straightforward and much easier than what it was on my Samsung Galaxy Spica: I found this
, a file called iconiaroot.apk on the sdcard aswell, rebooting your tablet while pushing the volume down button so its starts flashing the buggy honeycomb version.
Then start up the tablet again, rush to the market, download some file manager, with that filemanager explore your sdcard, and install the iconiaroot.apk file, once thats done, rush back to the market and download and install acer recovery installer. At that point you will have CWM (clockworkmod) installed.
Click to expand...
Click to collapse
is that all there is to it?
In any case I'll keep you posted just so it can help anyone with the same issue!
alsoe FYI and just for the anecdote: the reason I'm so cautious about everything and scared ****less of rooting is that the tablet is a present from my girlfriend for my 30th birthday, and she'll hang me with my guts if I brick it.
Ok I rooted and flashed the above-mentioned rom and it works! I'm now under 3.2.1!
Thanks to everyone who helped me! When the ICS update comes I will post here to signal how the FOTA went.
Thanks again!
Lol, good onya for taking the plunge! Yeh acer recovery installer is brilliant, along with iconia root, makes the whole process stress free.
Will be interesting to see if you get a notification for ICS OTA with that rom.
Can always flash one of the leaks if u get impatient??
Glad everything's worked out and yr g/f still talking 2 u
rgds Donna
thx! I will post here when/if I get the OTA. and my love life is safe thanksnto iconia root
okay so the ota has been rolling for over a week and a half now and still nothing for me
Today i decided to finally update to 4.2.1 and there after 4.2.2, but when i tried to update with OTA, it stopped 1/3 into the updateting process. Then showed a red exclamation thingy. I tried several times, but all with the same result.
Then i tried to update manually to 4.2 with adb sideload, but that did not work. It stopped after displaying "Verifying system" and then it displayed the following:
assert failed: apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:5013504:c48f8e86c73fb2c2ba1794f5ec98e27c9e206ed5:5060608:319331fae14fec8a88063751475fce26bae328e0")
Installation aborted
I am sure if have done anything right, but still can't make it work. The device is completely stock. Please help me D:
You didn't mention the starting condition of the tablet, and that is incredibly important information.
Additionally, you didn't really say whether the first upgrade succeeded. Please be specific and detailed.
The OTAs are patching kits - not full replacements - and thus they:
- must each be applied to a SPECIFIC starting condition, and
- can not be "skipped over"; they need to be performed in sequence.
You should be able to avoid OTAs altogether and flash a full factory image (at least up to JOP40D/4.2.1), but only if you are willing to wipe away all your data (factory reset)
So, say what your current version is - use the "J" release version (e.g. JOP40D, etc) , don't say four-point-whatever.
bftb0 said:
You didn't mention the starting condition of the tablet, and that is incredibly important information.
Additionally, you didn't really say whether the first upgrade succeeded. Please be specific and detailed.
The OTAs are patching kits - not full replacements - and thus they:
- must each be applied to a SPECIFIC starting condition, and
- can not be "skipped over"; they need to be performed in sequence.
You should be able to avoid OTAs altogether and flash a full factory image (at least up to JOP40D/4.2.1), but only if you are willing to wipe away all your data (factory reset)
So, say what your current version is - use the "J" release version (e.g. JOP40D, etc) , don't say four-point-whatever.
Click to expand...
Click to collapse
I am running Build JZO54K and tried to update OTA to JOP40D. All of my attempts of updating have failed. Both OTA and manual.
What do you mean by starting condition?
It would help to know if you have a wi-fi only model or 3g. They take different update files. You have to have the update specific to your model (wi-fi v. 3g). The amount of memory doesn't matter.
Groid said:
It would help to know if you have a wi-fi only model or 3g. They take different update files. You have to have the update specific to your model (wi-fi v. 3g). The amount of memory doesn't matter.
Click to expand...
Click to collapse
It is a 32gb wifi
henrikpw said:
I am running Build JZO54K and tried to update OTA to JOP40D.
Click to expand...
Click to collapse
Thanks, much better info.
henrikpw said:
What do you mean by starting condition?
Click to expand...
Click to collapse
Exactly what you stated above - thanks. In your OP, it wasn't clear whether it was the first OTA or the second OTA that was failing.
The assert fail message you provided revolves around the boot image (LNX partition). It implies a modified boot partition ... but I believe you when you say unmodified stock. (A different user reported a similar case a few days ago, but with a different stock ROM installed... and therefore a different OTA file)
Is it correct to assume this failure occurs when attempting to apply the JZO54K -> JOP40D OTA update?
Let me poke around a little bit, I will respond back. You may have to do a full factory flash - in the meantime have a look at the Carbon app video on Koush's (ClockworkMod) site to see if you are comfortable with doing that process.
bftb0 said:
Is it correct to assume this failure occurs when attempting to apply the JZO54K -> JOP40D OTA update?.
Click to expand...
Click to collapse
Yes.
bftb0 said:
Let me poke around a little bit, I will respond back. You may have to do a full factory flash - in the meantime have a look at the Carbon app video on Koush's (ClockworkMod) site to see if you are comfortable with doing that process.
Click to expand...
Click to collapse
I do not want to do anything that voids my warrenty
henrikpw said:
I do not want to do anything that voids my warrenty
Click to expand...
Click to collapse
Well, if you consider unlocking your bootloader, installing stock software, and then re-locking your bootloader to be a warranty-voiding situation, then there is really only one path available to you: back up all your market apps & data using Carbon, install the (full) factory software**, perform the 4.2.2 OTA, and then restore apps & data with Carbon.
**actually, I'm not completely sure if the factory (full-install) software bundle requires bootloader unlocking or not - I suspect that it might require an unlocked bootloader.
If you have never been through any of this before, I can see that it appears intimidating, esp. because of the number of newbs showing up every day asking "did I just brick my device?"
But using custom recoveries - even temporarily - provides some flexibility even when you want to run pure stock.
For instance, in your case, I believe that boot image check is the very last thing which is checked in your OTA prior to starting. That suggests that removing that check - AND the corresponding boot image patching - would allow everything else in the OTA patch to succeed; after that the complete boot.img file from the JOP40D distro could be manually flashed; and from there you would no doubt be able to proceed to an additional OTA install to get to 4.2.2
But because a modified/re-zipped OTA bundle could not be flashed by the stock recovery due to lack of signing, this flashing would have to be performed by a custom recovery (that has signature checking supressed).
Lastly, I will say this - I doubt that Google made a mistake with their assert() checks in their OTA update package. That suggests that either
- your boot image actually did get mysteriously modified somehow, or
- your device developed a media flaw in it's boot partition, so the checksum validation fails because of this problem.
In the latter instance, that portends a small risk involving future flashing or booting from that partition.
Well, this post has gotten long; maybe you should say something about what risks you *are* willing to take...
Here are some people who have the same problem: http://code.google.com/p/android/issues/detail?id=41819
henrikpw said:
Here are some people who have the same problem: http://code.google.com/p/android/issues/detail?id=41819
Click to expand...
Click to collapse
That's a lot of reports.
The thing that strikes me about this is that the check which fails (boot partition) is the very last item checked before the patching begins. In the case of folks trying the patch manually, it is hard to believe they simply picked the wrong OTA file (corresponding to the wrong release version) - because in that case a whole bunch of files would be mismatched: they would get a very early error in the list of things checked.
It's almost as if a bunch of units escaped Asus with a variation in the boot image.
There might be something more subtle going on too - here's someone on xda who reported the very same syndrome, but was trying to update a completely different OTA - the starting point was JRO03S
Well, as I said, the problem can be overcome manually. But you would probably need to unlock the bootloader, even if you planned on staying with a full stock setup.
< include generic disclaimer here >
TL;DR
Since update 3.1, Nvidia can force updates (such as the one that bricks your tablet) to be downloaded and installed silently. No guarantees, but:
If you're on stock, delete TegraOTA (/system/app/TegraOTA or /system/priv-app/TegraOTA if you're on 5.0 or newer, or /system/app/TegraOTA.apk if you're still on 4.4) before booting into Android (the attached ZIP file does this for you, but please check with the file manager in recovery before rebooting and let me know if it didn't work), then reboot
Note: you also will need to delete TegraOTA again if you ever install an OTA from Nvidia or a recovery image
If you're not on stock, you're probably safe
EDIT: The urgent OTA is currently not getting sent out to any devices anymore, not even to those who have been getting it before.
EDIT 2: The urgent OTA is now being delivered again, this time named "ST - yy"!
What if my tablet is already deactivated?
Unless you can still boot into fastboot mode (in which case your tablet isn't really deactivated yet), your tablet is probably gone for good. The only way to fix this would be through nvflash, and using it requires the SBK that is unique to each device and that only Nvidia knows, so it's pretty unlikely that we'll ever be able to fix these deactivated tablets.
What/why/how?
In the last OTA (Update 3.1), Nvidia has made some changes to their TegraOTA application. The most important/interesting/suspicious of which is the ability for them to mark OTAs as "urgent". What this means is that these updates will be downloaded without ever notifying the user, and they will be installed without asking the user for permission first. If this is how the kill switch is delivered, all users will see is the tablet randomly rebooting and installing an update, then the tablet would never boot again. As some of you might notice, this would match what has been happening to a few users already, both here and on reddit.
But that's not all. I've been connecting to the OTA servers using various serial numbers (both found and provided to me by a few people) in hopes of actually finding the update that bricks the device. The first serial number I've tried that wasn't mine was the serial number from the screenshot on the recall page. It revealed an interesting "urgent" OTA, named "SHIELD Tablet xx - LTE", which does nothing but flash a blob (which, among other things, contains the bootloader). Many more questions appear now, but the main one is: if this is nothing but a routine bootloader update, why is it marked urgent? And why is it not attached to any Android update? But this by itself is not enough to prove anything, as I could only obtain it with one serial number, so as far as I could have known, it might had just been an internal update or something similar. (update is linked and analysed in the second post below)
Today, however, one of the serial numbers I've been given by some of the people here (thanks for the help guys!) turned out to have the same update waiting for it the next time it connected to the Internet. This rules out the possibility of an internal update, so the next somewhat obvious possibility is that this is the kill switch. Mind you, I still have no direct way of proving this without flashing the ZIP to see what happens (which I'm not planning to do myself), but I will keep checking on the other serial numbers I've gotten to see if this update turns up for them too.
The same person who has given me this serial number has also tested running the old tablet on the latest stock Android version but with TegraOTA removed, and, as expected, the tablet is still working perfectly fine now. Your mileage may vary.
How can I know if the kill switch has been triggered for my tablet?
Go to http://shield.bogdacutu.me/ and enter the full serial number of your old tablet. If the next OTA returned is "SHIELD Tablet xx" "ST - yy", the kill switch has been triggered for your tablet.
Warning: the serial number from the box of the tablet and the one etched on the side of the tablet are not complete, as they only contain the first 13 characters of the full (20 characters) serial number. You can get the full serial number from Android (Settings -> About -> Status), from the bootloader (it will be on the screen when you boot into bootloader mode), or from your computer if the tablet is or (in some cases) if it was previously connected, using various tools such as USBDeview. Example: 0413714803249000a4cf (you can try this on the page and it will return that the kill switch is activated).
Why would I want to also do the fix on my new tablet too?
The update is signed by Nvidia, and communication with the OTA server does not use HTTPS, so, for example, a malicious WiFi network could MITM your connection and cause this update (as well as any other signed update) to be flashed to your new tablet without your permission, thus permanently disabling it too. If you have the stock recovery, only updates signed by Nvidia can run. The story might be slightly different if your recovery doesn't enforce signature verification (such as TWRP and CWM by default).
Can I still get updates from Nvidia after doing this?
Not directly, but people will post OTA download links here on xda when new updates get released. I'd personally recommend that you wait before flashing though until someone here checks the new update to confirm that there's no new way for Nvidia to kill your tablet.
Many hours of work have gone into investigating this. Even if it doesn't help your specific scenario, consider hitting that Thanks button, so that I can at least know it wasn't for nothing.
I'd also like to thank the people who have given me their serial numbers to use for testing again, this wouldn't have been possible without their help: @Beauenheim, @Jackill, and @runandhide05 (who has even volunteered to test removing TegraOTA with the latest update on his old tablet :highfive
Fragments of code from TegraOTA.apk
< screenshots temporarily removed >
Also, from what I've seen so far, the update isn't delivered instantly after activating the new tablet. I don't know exactly what the rule is, but out of the 4 serial numbers that I have, only 2 have this update waiting for them.
EDIT: One more serial number from the ones I have has gotten the xx update. Only one left...
EDIT 2: All the serial numbers I have have the urgent OTA waiting for them now.
"SHIELD Tablet xx" - Update Analysis
OTA URL: http://ota.nvidia.com/ota/data/post...wf-full_ota-32256_554.0168.20150624152335.zip
yy OTA URL: http://ota.nvidia.com/ota/data/posted-roms/uploaded/st---yy--092704233775---7294.20150819152732.zip (if you don't know what you're doing, DO NOT DOWNLOAD THIS, it's very likely that this will permanently brick your device upon flashing it!!!) - also attached to this post in case this link becomes invalid
updater-script is the first file we check:
Code:
getprop("ro.product.device") == "shieldtablet" || abort("This package is for \"shieldtablet\" devices; this is a \"" + getprop("ro.product.device") + "\".");
nv_copy_blob_file("blob", "/staging");
reboot_now("/dev/block/platform/sdhci-tegra.3/by-name/MSC", "");
Suspiciously enough, this only flashes a blob to the staging partition. But what exactly does this blob do, you might ask? Well, the blob actually contains data for 9 partitions, which are automatically replaced during the next boot (before the bootloader does anything else at all, so once you've rebooted, there's no going back) with the contents present in this blob. The 9 partitions are as follows (also detailing comparison with files from update 3.1):
BCT (Boot Configuration Table) - stores some information that is needed for the device to find the bootloader stored on the other partitions, initialize the RAM and some other stuff
Status after update: probably corrupted - the previous OTAs have binary BCTs, but this update replaces it with a text file (which, while it does contain somewhat relevant information, is likely not a valid format). If this is corrupted, it's enough for the device not to be able to boot anymore.
BMP (boot logo) - intact
DTB - intact
EBT (part of the bootloader) - has a zeroed out region
NVC (part of the bootloader) - intact
RBL (part of the bootloader) - has a zeroed out region
RP4 (landscape boot logo) - intact
TOS (Trusted OS - probably part of the bootloader too) - has a zeroed out region
WB0 (related to the boot process, source file is named "nvbootwb0.bin") - has a zeroed out region
The update also contains a few other files, but those are not used at all (probably leftovers from the 5.1 AOSP update template that they are using).
DO NOT DOWNLOAD THE ATTACHMENT IF YOU DON'T KNOW WHAT YOU'RE DOING. THIS IS THE XX OTA, NOT THE ZIP THAT REMOVES TEGRAOTA!
Just as I suspected!!
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
CWM and TWRP are both compatible with OTAs, so yes, it can. If you completely erase the recovery (fastboot erase recovery), the update can't get flashed, but the tablet will still reboot (which is at least annoying).
You can flash the provided ZIP through CWM or TWRP (but please check through the file manager if /system/app/TegraOTA still exists after installing it, the ZIP hasn't gone through a lot of testing so it might not work properly in all cases)
tecnoworld said:
Thanks a lot this is great. So the silent updater can force updating even with a custom recovery like cwm?
How to install the provided zip?
Thanks again.
Click to expand...
Click to collapse
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
bluegizmo83 said:
This was to be my question too... Normal ota updates will not flash if you have a custom recovery, so how would this silent ota update?
Click to expand...
Click to collapse
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Bogdacutu said:
Normal OTAs don't work through custom recoveries because they do various checks that usually fail when you have a custom recovery (such as if the system partition is modified, by rooting for example), this urgent OTA has none of those checks
Click to expand...
Click to collapse
Oh ok! Great explaination. Thanks for all your hard work on this! I'm flashing the zip now, i'll report back if it removes the file
Edit: Ok I flashed the zip, and TegraOTA is gone. Now I will finally turn on my new tablet and set it up!
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Great post. Hopefully that's as far as Nvidia is going to go. I flashed a custom rom on my old tablet. I'm keeping my new one stock but deleting the system app per your post. Just in case Nvidia is spiteful when I don't return the old tablet. I don't want to leave them any option of nuking the new one.
fkofilee said:
So out of interest, what do you think the chances are that thisll work?
How did you find out if the update is waiting? FYI I flashed the ZIP... All is good and it booted fine on LTE 32Gb...
Click to expand...
Click to collapse
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Bogdacutu said:
Decompiled the OTA application. Using information from there I can connect to the OTA server directly from my PC, and request updates for any given serial number and Android version combination.
I wouldn't have posted this if I weren't relatively confident in my findings
Click to expand...
Click to collapse
I know fella I appreciate it. Could you check my second point? 2 x Nvidia Shields would be awesome! One for Work, One For Home
fkofilee said:
Plus the deleting of the TegraOTA File has gone through... So you really think the TegraOTA removal has stopped it?
How do i check if i have downloaded randomly that update?
Click to expand...
Click to collapse
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Bogdacutu said:
Yes, I think it did. If that update was downloaded on your device, it would have been too late (as it reboots instantly after the update is downloaded), so I wouldn't worry about that.
Click to expand...
Click to collapse
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
fkofilee said:
So heres an interesting one for you, using a logical mindset, if you receive your new tablet, activate it, the next time that the old one connects to the network, it downloads this update and bricks it? But it wont technically do this until the new tablet is turned on?
Click to expand...
Click to collapse
As mentioned in the OP, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Bogdacutu said:
As mentioned in the first post, the update doesn't get delivered immediately after you activate the new tablet. But yes, the old tablet shouldn't get the update before the new one is activated.
Click to expand...
Click to collapse
Sorry fella missed that part, I will be donating some funds when i get paid later this month Mucho Gracias!
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
bluegizmo83 said:
Totally not related to this thread, but I just went to setup my new tablet and it's not letting me restore apps & settings from my old Shield Tablet... It doesn't show my old tablet as a restore option. I doubt checked and the old tablet is setup to backup all settings and apps though. Anyone else have this issue when setting up they're new tablet?
Click to expand...
Click to collapse
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Bogdacutu said:
Upgrade to 5.1 on the new tablet without restoring any data, then do a factory reset and you should get the option to restore
Click to expand...
Click to collapse
AWESOME man, thank you!!