Database Users

Have to admit I need some help with rooting

Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.

This means you are on the leaked version now and there is nothing that can be done as of right now.

K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?

ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.

sounds like you got a bad pb001.img file.

ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?

nevermind addressed my issue

As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5

ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.

af man...seriously!

out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"

HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA

ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!

[Q] All I want is Frodo 2.2 + root...but how???

All I want to do is upgrade to Froyo 2.2 and retain root so that I can use Wireless Tether. I've been reading several different EVO/Android forums but it seems like the more I read, the more confusing it gets. I'm still a noob, but here are my questions so I hope someone can lay it all out in the open for me.
Currently, my EVO has Unrevoked3 applied so I'm running on the "updated" 2.1, and I have root access and wireless tether is working as of now. Phone specs are:
Firmware version: 2.1-update1
Baseband version: 2.05.00.06.10
Build/Software number: 1.47.651.1
PRI version: 1.40_003
PRL version: 60665
1) What is the best/most reliable way for me to update to 2.2? Can I use Unrevoked Forever to do so? Or do I have to use some manual method? Toast's method? ROM Manager?
2) I read the steps for installing on the Unrevoked site, but I don't understand the terms it uses. It says to "flash from custom recovery". First of all, how do I access this custom recovery tool or whatever? Second, some ppl said they use a ROM Manager. Other sites say to "boot into recovery". Still, some instructions say boot into Clockwork....How do these method differ? Or are they the same? Which do I use???
3) One post says "After you unrevoke4, you can use your custom recovery image to flash a rooted 2.2 stock rom". I dont understand. A ROM is an image...so how can I use an image to flash another image?? makes no sense =\
4) Is "recovery" an app/tool that is already on the phone (or needs to be downloaded), and if so how do I access it? Or is it a ROM image?
5) After unrevoked is done, do I accept the OTA firmware update (i think it's the ugrade to Froyo update that keeps popping up)?
6) Which ROM needs to be installed? The zip that Unrevoked is going to install, or HTC Stock Froyo 3.26.651.6 [Rooted][Deodex'd], or both?
7) What is PRI and PRL and why are ppl so concerned about getting those updated? Will they get updated automatically once Frodo is installed?
8) Same deal with the Wimax and Radio updates. What do they do? Why do ppl want to retain them so badly, and if they are so important, why don't the updated ROMs or OTAs have them included?
9) What's the difference b/t a Nandroid backup and a Titanium backup? And which one should I do?
Please help! Thanks!

one does not simply walk into Mordor.

So I can identify with the OP. I don't know many of those same things, but I am slowly learning through reading these forums.........
However........that comment was quite amusing, also very accurate......... Ya that made my night
Sent from my PC36100 using XDA App

1) What is the best/most reliable way for me to update to 2.2? Can I use Unrevoked Forever to do so? Or do I have to use some manual method? Toast's method? ROM Manager?
Use Simpleroot to fully root. Then flash SteelH's 2.2 Stock Rooted ROM/
2) I read the steps for installing on the Unrevoked site, but I don't understand the terms it uses. It says to "flash from custom recovery". First of all, how do I access this custom recovery tool or whatever? Second, some ppl said they use a ROM Manager. Other sites say to "boot into recovery". Still, some instructions say boot into Clockwork....How do these method differ? Or are they the same? Which do I use???
Power + Volume Down while the phone is off boots your into the bootloader. You can then enter your custom recovery from there. Or you can use Rom Manager/Spare Parts to boot into recovery directly within your phone. Clockwork is a custom recovery; AmonRa is the other custom recovery. Use either one.
3) One post says "After you unrevoke4, you can use your custom recovery image to flash a rooted 2.2 stock rom". I dont understand. A ROM is an image...so how can I use an image to flash another image?? makes no sense =\
You need to install a custom recovery, ie AmonRa or Clockwork (an image) so you can flash a ROM (another image)
4) Is "recovery" an app/tool that is already on the phone (or needs to be downloaded), and if so how do I access it? Or is it a ROM image?
Recovery is already in your phone, but you need to flash a custom recovery after you root. Simpleroot will allow you to flash a custom recovery on the last step.
5) After unrevoked is done, do I accept the OTA firmware update (i think it's the ugrade to Froyo update that keeps popping up)?
Not relevant, when you are on 2.2, you won't be notified of OTA updates. After you root, NEVER accept any OTA. Wait for the updated rooted roms.
6) Which ROM needs to be installed? The zip that Unrevoked is going to install, or HTC Stock Froyo 3.26.651.6 [Rooted][Deodex'd], or both?
Don't use Unrevoked. Root using Simpleroot and flash your downloaded ROM afterwords.
7) What is PRI and PRL and why are ppl so concerned about getting those updated? Will they get updated automatically once Frodo is installed?
No one can really prove that an updated RPI/RPL affects your phone in positive ways. Your RPL will be updated. RPI will be 1.34 after Simpleroot, this forum just figured out how to get 1.40 RPI today (go read the dev forum)
8) Same deal with the Wimax and Radio updates. What do they do? Why do ppl want to retain them so badly, and if they are so important, why don't the updated ROMs or OTAs have them included?
Wimax and Radio updates improves your 4G/Radio/Data performance. They should be flashed after you flash your rom.
9) What's the difference b/t a Nandroid backup and a Titanium backup? And which one should I do?
Nandroid backup creates a complete image of your phone. Titanium backup only backs up your apps.

Speak friend and enter...
Speak friend and enter!
OK then, all the LOTR references aside, I was in your shoes not to long ago. You could have done a little more reading or googling (something like "how to root EVO"), as these forums usually contain a number of threads with titles something like "Moron-proof guide to....."
Anyway. Unrevoked seems to be considered a somewhat incomplete root according to most ROM threads (I don't know the details to speak intelligently on
the matter).
Here is what I did, and it worked well.
1) Get SimpleRoot. This will let you root your phone for real.
NOTE: I don't know if you need to get rid of unrevoked before this; maybe someone more knowledgeable can chime in on this one.
2) Step 2 of SimpleRoot is to flash recovery. There are two options; I chose RA. There are a few threads that talk about pros/cons of each.
For simplicity sake, I think of "recovery" as a program that lets you do lower lever system stuff, like flash files, do backups, etc. The general way to reach it is to hold VolDown while powering up you phone, then selecting "recovery".
Anyways, after you've flashed recovery, you'll be able to flash whatever ROM you want.
3)If you want stock 2.2 get THIS. Get the radios as well. Generally there are instructions with the ROMS, READ THEM.
You should have three zips. Put them on your sdcard. Then in recovery select flash from zip file (or something like that). Do that for all three with reboots in between.
You should now have the latest stock ROM and radios.
There are a ton of other ROMs out there. NO one will be able to tell you which one is the best, so don't ask.
Wireless Tether - the newest version is floating around here somewhere (pre7). It works well with the rooted stock 2.2
The PRL/PRI debate is still going on. You can read the million threads and see if you want to worry about it. I don't.
As far as backup goes, the more knowledgeable folks can speak to the details. A simple way of describing it is nand backup (from recovery) is like a ghost of your system, where as Titanium is more of an apps/settings kinda thing.
I strongly suggest reading the guide threads to gain more insight.
And, of course, I didn't come up with any of this stuff. If you find anyone's work helpful, then you should thank/donate to them.
EDIT: Hehe, looks like I was second in the helpful line.

That pretty much answers it all.
I can address #7.
Once Frodo is installed into mount doom he must cast the ring into the fiya.
Quickly though. For the creature gollum lays await in the shadows of every crevice left behind.
You must upgrade your puke ridden leggings and ingest some pain reducing ibuprofen for maximum connectivity with the force.
There I go switching epics again..

PLEEEASE STICKY!!!!!!!!
Then I could always find this thread in a hurry when I'm in a bad mood and need a pick me up.
This thread has brought great joy to my life. Expect me to bump it about once a week.
It's funny that I have no clue how to do this, because I full-rooted my EVO with the first firmware and never looked back. I've just been running custom recovery and custom roms ever since. I need to root a friends phone soon, so I guess I'll have to learn.

After much lurking and wiki reading I would like this stickied as well.

To get Frodo 2.2, you would have to write a novel, placing him in a setting similar to The Terminator. From there, create a back story on how his first version was inferior and lacking superior abilities, dubbing the need for a new version. After that have a fight scene of him going against his creator, thus needing to make him version 2.2. The non violent version. From there he would have the dramatic speech in a weird code of language.
Simple root, click click, RA, click. Power button volume down. Wipe, wipe. wipe. rooted rom zip, radio zip, reboot, power button volume down wimax zip, reboot.
After that Frodo will walk away into the sunset, in search of the future version of him, Frodo 3.0 - Fighting in the conquest of his arch nemesis, Apple Conner.

Quiksmage said:
one does not simply walk into Mordor.
Click to expand...
Click to collapse
Dammit Bilbo, you beat me to punch

Can I get frodo as well?will this give me wifis?
Sent from my HTC Evo using Tapatalk.

[ROM][03/06/2011]FlashBack21 v2 -Return to Factory Stock - March 2011 OTA

[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????

Update issues with latest OTA update from ASUS - Rooted with CWM

I Have a tf101 with first the ics upgrade. I recently got notice of the ota update. I ran OTA Rootkeeper and then ran the update. It bombed after reboot with the downed robot. After that would only boot into cwm, unless i cold boot. Even then the update is not applied. How do ii fix this without starting from scratch with a new or factory rom? If i have to restore factory, where/how do i do it Assn how do i then get my phone back to its current state?
Thanks all
Sent from rmy SAMSUNG-SGH-I717 using XDA

Go here. http://forum.xda-developers.com/showthread.php?t=1530337

ssl123 said:
Go here. http://forum.xda-developers.com/showthread.php?t=1530337
Click to expand...
Click to collapse
Thanks for the link, but it's not really helping me.
Firstly, it says nothing about the OTA update and how to address installing it on a rooted system.
Second, that thread has 23 pages and there seem to be a LOT of questions about the integrity of the process they have there.
I would figure that MANY people are in my situation and that there would be a more straightforward answer.

Why are you trying to get update with CWM.?

At this point, this thing is so messed up I want to toss it out the window! I have tried so many fixes! Nothing is working like it should. What is the best way to restore it back to factory...even if it means going pre-ICS and going through the upgrades? I just want the hours of time i'm spending on this to end.

Wait. You had root + CWM with stock 9.2.1.11 and you installed OTA update?
What version of CWM do you have?

Try this thread, I did it and it worked no bother, had to go back to Roach2010 CWM 3.2.0.1 first though --- http://forum.xda-developers.com/showthread.php?t=1545965

Get an Assert Failed error: apply_patch_check (long string of numbers)
E:Error in /sdcard/patch-edited.zip
(status 7)
Installation aborted

[Q]Won't update to Android 3.2.1 over FOTA / need original stock ROM

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