Database Info

Rooting G1 holiday edition

Hello all,
I have G1 holiday edition that was given to an employee of google.
current image on this phone isn't rooted.
Can I flash image at http://www.htc.com/www/support/android/adp.html to my phone knowing this my phone has tag "test-keys"? I think yes. am I correct?
my questions are
1. Can I do this without need to wipe all my settings?
2. Is there a way to keep my current image before flashing so that I can return to it in case I am not satisfied with results?
thanks in advance.

minashokry said:
Hello all,
I have G1 holiday edition that was given to an employee of google.
current image on this phone isn't rooted.
Can I flash image at http://www.htc.com/www/support/android/adp.html to my phone knowing this my phone has tag "test-keys"? I think yes. am I correct?
my questions are
1. Can I do this without need to wipe all my settings?
2. Is there a way to keep my current image before flashing so that I can return to it in case I am not satisfied with results?
thanks in advance.
Click to expand...
Click to collapse
No, you have to wipe. If you want to take advantage of root you should get used to the idea of wiping your phone. However once root is achieved you can get the switchrom script that makes wiping a non issue.
You can always unroot and wait for the OTA update if you decide you don't like it.
Also, this thread belongs in Q&A so don't be surprised when it gets locked.

ADP
minashokry said:
Hello all,
I have G1 holiday edition that was given to an employee of google.
current image on this phone isn't rooted.
Can I flash image at http://www.htc.com/www/support/android/adp.html to my phone knowing this my phone has tag "test-keys"? I think yes. am I correct?
my questions are
1. Can I do this without need to wipe all my settings?
2. Is there a way to keep my current image before flashing so that I can return to it in case I am not satisfied with results?
thanks in advance.
Click to expand...
Click to collapse
yes .. you should be able to flash .. go ahead and try it out .. the "holiday edition" as i know it to be is the dev phone so technically you already have root on the phone .. i could be mistaken .. if you flash and it fails then no harm done .. if you flash and it completes then you're good to go

Do NOT change the bootloader on it. It has the engineering bootloader (though it *looks* like the lockdown bootloader -- version number and rainbow stripes). It *does* have fastboot and does NOT enforce firmware signatures.
Also, it *does* have root, just not from within the phone itself. Log in to it using usb/adb and it will have root there, then you can create an su command if you want.
You do NOT need to wipe -- anybody who says so is on crack. You should be able to install a cyanogen or jf mod firmware to it easy -- update.zip to /sdcard/, "reboot recovery", alt-l, alt-s, done.
To keep your current image, "reboot bootloader", then from your computer "fastboot boot recovery.img" <-- use some modified recovery image that includes "nandroid" -- like the "pimp" cyanogen recovery file. This will create a backup that can be restored in the same way as it was created.

Don't Forget To Wipe
lbcoder said:
You do NOT need to wipe -- anybody who says so is on crack.
Click to expand...
Click to collapse
poetry in motion .. LOL .. no better way to put it

lbcoder said:
Also, it *does* have root, just not from within the phone itself. Log in to it using usb/adb and it will have root there, then you can create an su command if you want.
Click to expand...
Click to collapse
are you sure this phone is rooted?
when I issue "adb root" I get "adbd cannot run as root in production builds" and if it rooted, how can I create the su command?
lbcoder said:
You do NOT need to wipe -- anybody who says so is on crack. You should be able to install a cyanogen or jf mod firmware to it easy -- update.zip to /sdcard/, "reboot recovery", alt-l, alt-s, done.
Click to expand...
Click to collapse
I prefer using official images.
lbcoder said:
To keep your current image, "reboot bootloader", then from your computer "fastboot boot recovery.img" <-- use some modified recovery image that includes "nandroid" -- like the "pimp" cyanogen recovery file. This will create a backup that can be restored in the same way as it was created.
Click to expand...
Click to collapse
may you please give more details how could I do this?
what is meaning of "reboot bootloader"? is it a command I have to issue from adb or what?
how to use a modified recovery image? I want to copy the currently installed image to recover to it in case of problems or I don't like the results?
please tell me full details as I am quite beginner in these stuff
thanks again

[ROM] Stock 2.1 Hero Update zip from RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe

Since some people were interested I've made a stock update zip from the RUU_Hero_C_Sprint_2.20.651.1_signed_test.exe so you can flash via recovery.
This is just for those who want a completely stock rom to work off of or those that can't or don't want to run the RUU. If you want something already tweaked then use DamageControl. I'm not trying to start a custom rom I just did this for a couple people that wanted it.
It does not include the new hboot or radio.img included in the RUU and the system is stock except for adding busybox, patched su and sh.
To use su you need to install Superuser.apk.
Busybox is not installed by default you can do that through a terminal app or adb executing su and running "busybox --install /system/xbin".
You must be rooted and flash via Amon_ra recovery. Recommend nandroid backup and wipe/factory reset before flashing.
Here is a link to my post on how to make an update zip from the RUU.
Download link for the update/rom:
http://dl.dropbox.com/u/6022412/zen-hero_0.1b.zip
The link might be down since dropbox just suspended my public links due to excessive traffic.
Alternate download:
http://www.4shared.com/file/YqMmKAzL/zen-hero_01b.html
This is a link to my google code site where i put up some of the binaries/scripts that I use for rom making. These are linux binaries. If you download them put them in your path so you can execute them from anywhere. Also make sure you chmod them to executable. If you don't know how the google can tell you.
http://code.google.com/p/zen-droid/downloads/list
Due to recent events I just want to say that the devs here put a lot of work into getting you guys these leaked roms. They risk their credibility and their sources risk their jobs. So have some respect and remember it's just a phone.

Thank you,I'm sure a lot of people were wanting this.

What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!

Roman G said:
What is the point of making a zip when you can just use the RUU?
My RUU just got done booting!
Click to expand...
Click to collapse
For people not running windows and for people that don't want to risk flashing hboot or the radio.img.

See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!

Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.

obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
crazy, his link says zendroid in it too
http://code.google.com/p/zen-droid/downloads/list

obelisk79 said:
Zenulator: heh I'm working on a rom I titled Zendroid... wonder if people will confuse it as being something related to you.
Click to expand...
Click to collapse
Yea I thought that was kind of funny. Nice name for a rom though

yeah well, I thought it had a nicer ring to it than fengshuidroid.... was going for a rom which was also centered around a nice clean theme to the sense ui. I'm still making headway on the project.

Re: [ROM] Stock 2.1 Hero Update.zip
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app

theclawpr said:
Maybe this is a stupid question but, The phone needs to be rooted to install this rom?
Sent from my HERO200 using xda app
Click to expand...
Click to collapse
yes you need root and a recovery image

Roman G said:
See I did not know it came with the radio image!
Just booted up fine and got the new radio image and a knew PRI# and was able to update my PRL as well!
Click to expand...
Click to collapse
Interesting! What is the new PRI that you have now?

raynda said:
Interesting! What is the new PRI that you have now?
Click to expand...
Click to collapse
2.10_003 I believe it's the one that damage had that no one could figure out where he got it other than the official release!

okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?

rgildoss said:
okay i have a question, i was trying to update the recovery image to the 1.6.2 . but i get an error ..
The img file is in the sd card and when i do flash_image recovery recovery-RA-heroc-v1.6.2.img i get flash_image not found error ...
i tired to go from scratch and do the factory 1.5 image (RUU) but now says can not start bootloader ...any ideas?
Click to expand...
Click to collapse
adb shell
cd /sdcard
flash_image recovery blah.blah.blah

smw6180 said:
adb shell
cd /sdcard
flash_image recovery blah.blah.blah
Click to expand...
Click to collapse
error
flash_image: not found

rgildoss said:
error
flash_image: not found
Click to expand...
Click to collapse
Thats because the flash images is not called blah.blah.blah

VinceOB said:
Thats because the flash images is not called blah.blah.blah
Click to expand...
Click to collapse
i know that ...lol
ever i try i can not load the damn recovery image ...
power + menu gives me a picture of the phone with ! .....
how can i load the recovery image ?
The phone is rooted but just wont take the revory image

Now this might be a stupid question, but do we need Root for this? I have a friend who's terrified of Rooting but really wants 2.1, so could he just Flash this through the Stock Recovery Image, or should I force him to Root?
Edit: NVM sorry I just read the 1st post on page 2. Told you it was a stupid question.

It seems like the flash_image command is missing.

Recovery

Ok, so clockwork recovery has worked without fail for 8 months...
then today i tried to reboot into recovery (using power menu, adb etc) and it just sits on the google screen.
I have reflashed a few different recovery images and locked/unlocked the loader.
I can get into recovery only after straight after flashing the recovery, by going to the bootloader and selecting reboot (not recovery)
something is balked here, any ideas?
(i would just lock the bootloader again and take it back as faulty, but when that is done, it boots straight into recovery, i assume because there is no ROM there)

Lock the bootloader then unlock it again then reflash Clockwork.
Have you tried using the modded one on the dev forums at 4.0.0.2?

yep, im afraid ive done that... any way to reinstall the bootloader itself?

slimjimwoods said:
yep, im afraid ive done that... any way to reinstall the bootloader itself?
Click to expand...
Click to collapse
Yeah you can find the images (there was a update to the bootloader in 2.3.2 or something) and go into bootloader mode and type.
fastboot flash bootloader whatever-the-bootloader-name-is.img
My bootloader is: I9020XXKA3

any chance you could point me in the right direction of the images, google is seeming fruitless...

slimjimwoods said:
any chance you could point me in the right direction of the images, google is seeming fruitless...
Click to expand...
Click to collapse
Yup, no problem. I was just looking for it. Is the KA3 bootloader the version you currently have? Because I know it was optional to update the bootloader, especially for non-stock ROM'ers.
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90

currently I have I9020XXJK1...

slimjimwoods said:
currently I have I9020XXJK1...
Click to expand...
Click to collapse
Yeah thats the older bootloader that came with the stock phone. The KA3 bootloader is the newest bootloader that was included with the 2.3.3 OTA. Just make sure you're using a I9020 model. Which you probably are since you're in the UK so you shouldn't have anything to worry about.

excellent thankyou, and im right in saying
fastboot flash boot *above file*...

slimjimwoods said:
excellent thankyou, and im right in saying
fastboot flash boot *above file*...
Click to expand...
Click to collapse
1. put bootloader.img into \android-sdk-windows\tools\
2. command prompt, cd C:\android-sdk-windows\tools\ (or where ever your SDK folder is)
3. put phone into bootloader mode if it isnt already
4. fastboot flash bootloader bootloader.img
5. reboot bootloader
6. check bootloader version
p.s. verify its MD5 hash before you fastboot it

aha! thankyou, it was flash bootloader... ok thats done, I shall try clockwork and get back to you

slimjimwoods said:
aha! thankyou, it was flash bootloader... ok thats done, I shall try clockwork and get back to you
Click to expand...
Click to collapse
good luck

clockwork is fine now, flashed CM7 nightly but it just sat on the black Google screen again... going to try something a bit more stable... thankyou for your help on this

its booted
[ROM-AOSP GRJ22][NS+NS4G] Oxygen-2.1.6,

slimjimwoods said:
its booted
[ROM-AOSP GRJ22][NS+NS4G] Oxygen-2.1.6,
Click to expand...
Click to collapse
congrats CM7 nightly should of flashed too. just have to wipe dalvik,cache,factory and it should be fine afterwards.
Oxygen is pretty nice though. I manipulated the ROM to be like Cyanogen by copying over Cyanbread. More lightweight and less bloat compared to CM7.

would that add in DSP manager?

slimjimwoods said:
would that add in DSP manager?
Click to expand...
Click to collapse
Nope. have to separately add it in, Voodoo Sound is better anyways.

That's true, but I tend to run them alongside each other, dsp doing the equalizer... (like to give the treble a boost)

slimjimwoods said:
That's true, but I tend to run them alongside each other, dsp doing the equalizer... (like to give the treble a boost)
Click to expand...
Click to collapse
Just add the app in, see what happens.

[Q] Need Fix To Green Bot of ! Problem

A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?

microi said:
A problem currently exists with newer Xooms when attempts are made to flash ClockworkMod 3.2.0.0 (R4c) (CMW) into the Recovery partition. This issue has been mentioned in several threads with no resolution to date.
This is what the problem seems to be:
- Fact: There was no problem flashing ClockWorkMod (CWM) to older (earlier versions than 3.2.1).
- Fact: The problem occurred with attempts to flash later versions of Android, e.g., 3.2.1 following update via OTA.
- Fact: The OTA has an incompatibility with CWM. Joe Ferreira identified the problem as one of the following files being present that will prevent CWM from working:
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
- Fact: The proposed fix involves reverting to an earlier version, i.e., 3.0 and updating to 3.2.1 via OTA. This fix is yet unproven.
- Fact: Owners of newer Xooms are being prevented from achieving root because of this problem (including myself)
To summarize:
1) Recent OTAs which bring the Xoom to 3.2.1 are incompatible with the ClockworkMod 3.2.0.0 (R4c) image (CWM)
2) Once flashed CWM is inaccessible.
This is the problem that needs to be resolved.
Note: Epic118 has suggested reverting to 3.0; updating via OTA to 3.2.1; and rerunning Xoot. I don't understand this since attempting to flash CWM on 3.2.1 updated via OTA will repeat the same issue. Perhaps EPIC118 can provide clarification.
Does anyone have a solution/fix to this problem?
Click to expand...
Click to collapse
How about reverting to stock 3.0.1, then OTA updating to 3.2 and then rooting/flashing recovery and custom rom/kernel. I would think the issue is with the 3.2.1 OTA update itself.

I'm not completely sure I understand but if u can try this,
Download the universal root update zip and put it on your xoom
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Flash the universal root.zip and boot up and use a root file manager to delete those two file and clockwork should stick through a reboot
Sent from my ADR6400L using Tapatalk

Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?

bandit197 said:
Hi
I have a UK Xoom and I am interested in putting a custom ICS on it. I have read through all of the pages of the excellent guide to unlocking and rooting etc started by okantomi. Fair play to all involved, its a great source of information.
My Xoom is showing 3.2 as the current version. When I bought it a few months ago it had 3.0 installed. I updated OTA to 3.1 and more recently to 3.2. I then got a small update a few weeks back but Android version is still showing as 3.2. Am I good to go ahead?
Click to expand...
Click to collapse
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.

okantomi said:
I'm not sure what update (after the 3.2 update) added the security "fix" that seems to cause the problem, but you might as well try to root. If it doesn't work, at least you have a potential work-around, but hopefully it will be fine.
Good luck.
Click to expand...
Click to collapse
Cheers, I went ahead with it and it worked out no problems, unlocked, rooted and I can access recovery. Ill post the details in the guide thread to keep everything in the one place.

Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
Flash clockwork through fastboot and then reboot into recovery, don't let it boot or the install recovery.sh will delete clockwork!
Click to expand...
Click to collapse
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
adb reboot bootloader
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
Click to expand...
Click to collapse
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi

microi said:
Superchilpil,
Thank you for your reply.
There are a few points I don't fully understand.
You indicate,
1) Should I reboot into recovery using fastboot or simply reboot the Xoom using "Vol+ and Power"?
2) You indicate, "Don't let it boot". I don't understand; if I initiate a 'reboot', it reboots. How can I prevent it from rebooting???
This is the code I will use to flash Clockwork:
What code should I use to effect your suggested approach?
One last question. The objective of this question is to understand if I can simply flash the "Universal Root Update Zip" to obtain root using the stock Recovery Mode, then install ClockworkMod Recovery; then remove one or the other of two problematic security files which are currently causing a problem. This will theoretically resolve the "Green Bot of !" issue Xoom users with 3.2.1 are currently experiencing.
After unlocking the bootloader, is it possible to:
1) Flash Update.zip (from the MicroSD card) using the stock Recovery Mode
2) Flash ClockworkMod Recovery through fastboot
3) Obtain root from this procedure
Thank you in advance.
Microi
Click to expand...
Click to collapse
by not letting it boot I mean don't let it boot into the rom, and both of those methods u stated will work just fine to reboot
And flash it using whatever method you desire, but I forgot to mention that you may need to flash clockwork again after you boot and delete those files because the install recovery.sh obviously flashes the stock recovery and the point of my method is to keep a custom recovery on your device
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Sent from my Xoom using Tapatalk

superchilpil said:
I know for a fact that the stock recovery mode won't flash anything you will find here in the forums that I know of
Click to expand...
Click to collapse
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.

teameos said:
Correct, the stock recovery requires that the zip files be signed with keys that only the manufacturers have access to. This is the whole reason why we have to flash a third party recovery to begin with.
Click to expand...
Click to collapse
I'm getting more and more confused the more times I read this.!!
I have done the update then unlocked to find I now have the green bot!!!!!
Someone please send a simple step by step with some file links to revert back to stock 3.2!
Thanks

I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.

willysp said:
I was HC stock, locked, unrooted, had accepted all OTA's - and therefore had the problem with the 2 files mentioned in the OP. I updated to ICS just fine. In order to root, I did the following (the differences from the standard instructions are underlined)
unlock
flash recovery
boot into recovery
root
then while still in CWM, no reboot, but instead:
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
reboot with CWM
Only had to flash CWM once.
Click to expand...
Click to collapse
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?

Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G

okantomi said:
Thanks. This makes a lot of sense. I would like to edit my rooting guide and give this procedure as the preferred approach. Is there anything you would want to add to it?
Click to expand...
Click to collapse
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
bwcorvus said:
Just as a Fyi, these files are on all Android os, not something new. You can also flash an insecure boot image, and it will stop these from running.
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.

willysp said:
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.

ydaraishy said:
These are a _function_ of the OTA process. When there are kernel or recovery updates required, the stock recovery partition requires patching, hence these files.
Click to expand...
Click to collapse
Thanks, that helps explain what they are. So, if an OTA (like 3.2 apparently) wants to patch/replace stock recovery, those are the files that do it on next boot. Would be nice if they deleted themselves when done (from a hacker's POV), but for people running stock, I guess it makes sense for the OS to check the recovery partition at each boot and overwrite it with stock recovery if needed.

willysp said:
Hi,
First - thanks for your rooting guide - I used it with the exception of my underlined steps which were a synthesis of what I saw in a few other places.
Nothing to add - except perhaps really emphasize to keep the USB cable connected, and after rooting, do not reboot, stay in CWM, and use adb to run the 3 commands. You wrote a very detailed guide, so know you'll do a great job writing the expanded version of my short underlined additions. As you obviously know, many of the less technical users need a more detailed explanation of my underlined changes.
Thanks again for the help your guide gave me!
---------- Post added at 07:19 AM ---------- Previous post was at 07:14 AM ----------
Yes, I saw them mentioned re several devices as I googled.
But - are you saying they were present in stock Xoom HC? Everything I've read says they were added in the 3.2 OTA, since people who are on 3.1 don't have these files to deal with.
Click to expand...
Click to collapse
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.

okantomi said:
I'm no expert, but I will try to put it together based on the info in this thread, but please correct me if I'm wrong.
Click to expand...
Click to collapse
Sure - glad to.

Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G

bwcorvus said:
Yes these files were on the stock Xoom. Infact it helped us get some of the dumps. We would flash cwm, then dump, then let the OS rebuild the recovery. We then flashed cwm to boot and dumped the stock recovery.
Sent from my Nexus S 4G
Click to expand...
Click to collapse
Thanks for the info.

[Q] Steps to root and flash a new rom

Coming from a DX, the process to root / flash on the galaxy doesn't seem that much different. Although, there seems to be greater risk for issues around imei information, etc....
So, I've read about everything I can on the forums, trying to make sure I understand all of the ins and outs and I'm starting to feel pretty comfortable with the process, however I would like someone to just confirm that i've got everything correct......
Based on this guide ( [GUIDE][VZW Edition]How to root your Galaxy SIII & More!(ROMs/CWM/Stock)) , this is how I understand things if somone could either comfirm or correct my information I would greatly appreciate it!
1. using section 2 in the guide for windows users, I use the RootDebugFS bat file to root the phone.
2. After rooting, and prior to unlocking the boot loader, I backup my IMEI using Comprehensive IMEI/EFS Backup method listed in the guide.
3. From here I can unlock the bootloader and install CWM reovery.
4. At this point, back in the droid X world I would take a back up of my system so I have a semi - stock image to go back to.
5. Now I can download any of the different custom roms listed and follow the instructions in the OP to flash that rom.
Going back to stock.
1. Should I need to go back to Stock, I would just use the ODIN tool to flash one of the stock images.
Again, If someone could just let me know if i've missed anything or if I'm WAY off base I would appreciate it.
Thanks again, and I love the forum and the community!

yep you got it correct...also if you have any questions feel free to post in my thread!

droidstyle said:
yep you got it correct...also if you have any questions feel free to post in my thread!
Click to expand...
Click to collapse
Thank you very much, I really appreciate it!! Can't wait to get started.
I did try to post in your thread, but apparently I'm to much of a NOOB to do so LOL!

nickjensz said:
Thank you very much, I really appreciate it!! Can't wait to get started.
I did try to post in your thread, but apparently I'm to much of a NOOB to do so LOL!
Click to expand...
Click to collapse
I've got 2 more questions....
1. I tried to flash the synergy backup for the IMEI/EFS using stock recovery as per the instructions and I got a message that the signatures or something like that wasn't correct and it was aborted.... Thoughts?
2. As far as custom recoveries go.... I'm used to CWM, but I've heard a lot of good things about TWRP. Which would you recommend?

nickjensz said:
I've got 2 more questions....
1. I tried to flash the synergy backup for the IMEI/EFS using stock recovery as per the instructions and I got a message that the signatures or something like that wasn't correct and it was aborted.... Thoughts?
2. As far as custom recoveries go.... I'm used to CWM, but I've heard a lot of good things about TWRP. Which would you recommend?
Click to expand...
Click to collapse
#1-Have never had to use it as I have never lost IEMI. May be a way to disable signature check in recovery. Can do permanent fix with terminal emulator.
Type:
su (enter)
reboot nvbackup (enter)
#2- Recovery is personal choice. I have been using TWRP since pre-order release and never had a bad flash or backup. As far as I'm concerned it rocks. Easier navigation and looks good. Some prefer CWM. To each their own. Don't recommend flashing via Rom Manager. Flash straight from recovery.

prdog1 said:
#1-Have never had to use it as I have never lost IEMI. May be a way to disable signature check in recovery. Can do permanent fix with terminal emulator.
Type:
su (enter)
reboot nvbackup (enter)
#2- Recovery is personal choice. I have been using TWRP since pre-order release and never had a bad flash or backup. As far as I'm concerned it rocks. Easier navigation and looks good. Some prefer CWM. To each their own. Don't recommend flashing via Rom Manager. Flash straight from recovery.
Click to expand...
Click to collapse
Thank you very much for the advice! I really appreciate it!

signature verification error means you were in stock blue recovery and not cwm recovery.

droidstyle said:
signature verification error means you were in stock blue recovery and not cwm recovery.
Click to expand...
Click to collapse
Thanks DroidStyle Wouldn't have gotten this far without the help! Finally got CWM on and flashed i that way and it worked great!
Speaking of CWM though.... in EZRecovery, do I need to hit "FLASH" and then "Reboot" recovery everytime I want to go into CWM or TWRP? If I don't it just takes me to stock recovery.

nickjensz said:
Thanks DroidStyle Wouldn't have gotten this far without the help! Finally got CWM on and flashed i that way and it worked great!
Speaking of CWM though.... in EZRecovery, do I need to hit "FLASH" and then "Reboot" recovery everytime I want to go into CWM or TWRP? If I don't it just takes me to stock recovery.
Click to expand...
Click to collapse
you should only need to flash cwm or twrp once, then reboot recovery to get into cwm. im not sure why its not sticking but it should.