Database Info

How Long Will a Root for ICS OFFICIAL Take

So here's the deal. I'm running CM9Alpha13. And while I love having my phone rooted and playing around with it, I was really only interested in getting ICS for my phone. No I know I'll miss Francisco.Franco's kernels and I'll miss Koush's awesome ROMs but I just really want a stable ICS.
So my question is how long before I can root my ICS if I do the official downgrade to GB and Upgrade to ICS?
Any guestimate would be great!
Thanks in advance.
Jon

I am sure it wont take long...just give the devs a day or so to play with things and get everything worked out.
Sent from my Nexus S using Tapatalk

I'm wondering about this too... I need a stable one but I need it to be rooted too...

http://www.megaupload.com/?d=S67I9Q0L
EDIT: flashable with CWM.
+ read this: http://forum.xda-developers.com/showpost.php?p=20395808&postcount=25

Chamb' said:
http://www.megaupload.com/?d=S67I9Q0L
Click to expand...
Click to collapse
This is a su-update.zip file flashable with CWM
it did the trick for me, just simply flashed it and now have working root

Anyone else confirmed this working?
EDIT: Oh, and mirrors please?

Read this: http://forum.xda-developers.com/showpost.php?p=20395808&postcount=25

Chamb' said:
http://www.megaupload.com/?d=S67I9Q0L
EDIT: flashable with CWM.
+ read this: http://forum.xda-developers.com/showpost.php?p=20395808&postcount=25
Click to expand...
Click to collapse
rooted~
but superuser fc...

FLyTula said:
So my question is how long before I can root my ICS if I do the official downgrade to GB and Upgrade to ICS?
Click to expand...
Click to collapse
While we're at it, is there a downgrading/upgrading guide somewhere?

fromthestars said:
This is a su-update.zip file flashable with CWM
it did the trick for me, just simply flashed it and now have working root
Click to expand...
Click to collapse
Confirmed that this worked on Google issued phone (same as T-Mobile version). The following is the order I used to come from CM9 Alpha 11:
1. Backup using Titanium, reboot to recovery.
2. Use CWM to flash stock 2.3.6.
3. Use CWM to flash stock ICS 4.0.3.
4. Wipe all user data.
5. Install the linked superuser through CWM (I had previous tried older and newer versions, which did not work).
6. Reboot phone, go through setup, download Titanium, and restore. Phone is definitely rooted (otherwise Titanium is unusable). I did not try to update the su binaries and will avoid doing so.

any way to root with something like superoneclick?
I'd like to avoid flashing custom stuff on it. just need root.

xd4d3v said:
any way to root with something like superoneclick?
I'd like to avoid flashing custom stuff on it. just need root.
Click to expand...
Click to collapse
Then fastboot boot recovery and flash the latest su zip. Even if you flashed the custom recovery it would be overwritten when you boot up the os.

Flashing Roms and rooting phone?

Okay so I have a question I'm rooted on my gf shift 2.3.4 with S-on with clockworks do I need to downgrade to 2.2 or anything to flash any Rom here ??
Sent from my SPH-D700 using xda app-developers app

ivcesar said:
Okay so I have a question I'm rooted on my gf shift 2.3.4 with S-on with clockworks do I need to downgrade to 2.2 or anything to flash any Rom here ??
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
It will make things a lot simpler for you if you are Fully Rooted ( S-Off ) . You can Flash Roms with S-On, but it is a bit more involved. Because you cannot flash any Kernels. Being that most Roms have custom Kernels it creates a bit of an issue. It can be done, it just means you are going to have to modify any Rom that has a Custom Kernel before you try and flash it. You were using THIS THREAD correct? I would recommend finishing the Downgrade process to 2.2 in order to achieve Full Root. It will make life much easier in the long run.

+1!
Sent from my PG06100 using xda premium

prboy1969 said:
It will make things a lot simpler for you if you are Fully Rooted ( S-Off ) . You can Flash Roms with S-On, but it is a bit more involved. Because you cannot flash any Kernels. Being that most Roms have custom Kernels it creates a bit of an issue. It can be done, it just means you are going to have to modify any Rom that has a Custom Kernel before you try and flash it. You were using THIS THREAD correct? I would recommend finishing the Downgrade process to 2.2 in order to achieve Full Root. It will make life much easier in the long run.
Click to expand...
Click to collapse
Thank you for taking your time an swering my questions its my first htc phone trying to root so I'm all lost an all over the place haha well to answer your question yes I'm stuck between 15 an step 18. I wasn't sure how flash misc.img file from adb or phone I was a little lost their
Sent from my SPH-D700 using xda app-developers app

ivcesar said:
Thank you for taking your time an swering my questions its my first htc phone trying to root so I'm all lost an all over the place haha well to answer your question yes I'm stuck between 15 an step 18. I wasn't sure how flash misc.img file from adb or phone I was a little lost their
Sent from my SPH-D700 using xda app-developers app
Click to expand...
Click to collapse
Make sure the misc.img is on the Root of your SD Card. Also the PG06IMG.zip from the OP. You can Copy and Paste. Or push them there with ADB. I use the Copy and Paste method. Since it sounds like your a little lost on the exact commands, I'll give them to you to do using Terminal Emulator as per the Guide.
Open Terminal Emulator.
Type: su
Hit Enter
Type: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Hit Enter
After that just go to Step #18 of the Guide, and follow the rest of the Instructions. Before you do anything I would suggest that you Reread instructions, and Re-watch the Videos. Just for your own peace of mind . Personally though I would probably if it were me start the Entire process over. RUU back to 2.3.4 and just redo the entire process. But that's just me .

prboy1969 said:
Make sure the misc.img is on the Root of your SD Card. Also the PG06IMG.zip from the OP. You can Copy and Paste. Or push them there with ADB. I use the Copy and Paste method. Since it sounds like your a little lost on the exact commands, I'll give them to you to do using Terminal Emulator as per the Guide.
Open Terminal Emulator.
Type: su
Hit Enter
Type: dd if=/sdcard/misc.img of=/dev/block/mmcblk0p17
Hit Enter
After that just go to Step #18 of the Guide, and follow the rest of the Instructions. Before you do anything I would suggest that you Reread instructions, and Re-watch the Videos. Just for your own peace of mind . Personally though I would probably if it were me start the Entire process over. RUU back to 2.3.4 and just redo the entire process. But that's just me .
Click to expand...
Click to collapse
Hey I just saw the reply thank you again for taking your time i figure it out i when into adb shell since i could get to do anything in terminal for nothing push with adb when to 2.2 root now in a search of a rom lol thank you for you help
Sent from my SPH-D700 using xda app-developers app

Glad you got it sorted out . I would try a few different Roms before settling on one. A few pieces of advice. One is to make sure you Flash the Rom, or Roms of your choosing correctly. Meaning do a Full Wipe, before Flashing. Also after you Flash a Rom, make sure that you give it a least a few days to settle in. That way you have a better idea of how each Rom is, before making a decision on whether you like it or not.

prboy1969 said:
Glad you got it sorted out . I would try a few different Roms before settling on one. A few pieces of advice. One is to make sure you Flash the Rom, or Roms of your choosing correctly. Meaning do a Full Wipe, before Flashing. Also after you Flash a Rom, make sure that you give it a least a few days to settle in. That way you have a better idea of how each Rom is, before making a decision on whether you like it or not.
Click to expand...
Click to collapse
So my question is... I had intentionally 'half rooted' my phone cause i wanted to stick with the stock ROM for the time being and SuperUser granted enough permissions to do some of the things i needed to do. Evervolv came out with a JB build that I wanted to try; so I have to get it to S-OFF now (which I did initially but restored it cause at the time I didn't like the ROM I flashed and ran an RUU). If I made a CWM backup of my current 2.3.4 settings, after I downgrade and root can i revert back to it if I don't like the new ROM?
Thanks

So I'm not sure I follow you. Are you currently " S-Off " ? If you are, and made a Nandroid backup. Then yes you can revert back to the Nandroid backup at any time. But if you ran an RUU, then no you cannot Nandroid back. The Nandroid backup is still on your SD Card, but you cannot access it with the Factory Recovery.

prboy1969 said:
So I'm not sure I follow you. Are you currently " S-Off " ? If you are, and made a Nandroid backup. Then yes you can revert back to the Nandroid backup at any time. But if you ran an RUU, then no you cannot Nandroid back. The Nandroid backup is still on your SD Card, but you cannot access it with the Factory Recovery.
Click to expand...
Click to collapse
Ok, sorry. I rooted it and got s-off when I first got my shift but decided to go back stock via RUU. few weeks later i went back and followed Vicodan's post only halfway to get root when I needed it via SuperUser. So I do have CWM installed and my backups work (I found out when the ROMS i been trying to load won't even boot and restoring from backups work fine). Thanks for clarifying that for me, here I come Evervolv

Just curious as to why you do not want Full Root ? Also if your still " S-On " trying to flash Roms can become a PIA . Reason being, most Roms have custom kernels. Which if you are not Full Root " S-Off " becomes an issue.

To flash any ROM while s-on unlocked you will need to use fastboot for the kernel. So have adb and fastboot setup and drag the boot.img from the ROM your flashing into your fastboot folder. Boot into recovery and do a full wipe as always and flash the ROM, Once the ROM is flashed plug the phone in and open a command prompt, cd to your platform-tools folder and type adb reboot bootloader, once it reboots into bootloader make sure it says fastboot usb in red. If it don't choose fastboot, then use this command fastboot flash boot boot.img and once it says it's done reboot to enjoy the custom ROM/KERNEL combo
Sent from my myTouch_4G_Slide using Tapatalk 2

strapped365 said:
To flash any ROM while s-on unlocked you will need to use fastboot for the kernel. So have adb and fastboot setup and drag the boot.img from the ROM your flashing into your fastboot folder. Boot into recovery and do a full wipe as always and flash the ROM, Once the ROM is flashed plug the phone in and open a command prompt, cd to your platform-tools folder and type adb reboot bootloader, once it reboots into bootloader make sure it says fastboot usb in red. If it don't choose fastboot, then use this command fastboot flash boot boot.img and once it says it's done reboot to enjoy the custom ROM/KERNEL combo
Sent from my myTouch_4G_Slide using Tapatalk 2
Click to expand...
Click to collapse
Yes Sir that's what he'd have to do every time he flashed a Rom with a custom kernel. Like I said, more involved than the way you would normally Flash a Rom . It's easier to be Fully Rooted, if your able to be IMO.
TEAM MiK
MikROMs Since 3/13/11

prboy1969 said:
Yes Sir that's what he'd have to do every time he flashed a Rom with a custom kernel. Like I said, more involved than the way you would normally Flash a Rom . It's easier to be Fully Rooted, if your able to be IMO.
TEAM MiK
MikROMs Since 3/13/11
Click to expand...
Click to collapse
Oh definitely, because if he wanted to test a kernel he would have to flash the new kernel in recovery so the modules for wifi/wimax are placed correctly then go into fastboot to flash the boot.img and that is just way to damn much work.
The advantages to s-off are endless IMHO
Sent from my myTouch_4G_Slide using Tapatalk 2

He'll yes to much work. Not mention you don't really gain anything by not having Full Root " S-Off " . In almost every case it makes things more difficult
TEAM MiK
MikROMs Since 3/13/11

prboy1969 said:
Just curious as to why you do not want Full Root ? Also if your still " S-On " trying to flash Roms can become a PIA . Reason being, most Roms have custom kernels. Which if you are not Full Root " S-Off " becomes an issue.
Click to expand...
Click to collapse
After going s-off and trying some roms initially, I reverted back and for a while I liked the stock 2.3.4, so I just rolled with that and was content with not having full root (the few things i wanted to tweak, superuser could do). Seeing now that there is finally a somewhat usable ICS build (4g is a non issue since I live in a fringe area anyways) I tried to load it to no avail. So it was time to be full s-off again :laugh:
Anyhow, I got s-off quickly and now running a new ROM :good:

Good to hear . I'm a big advocate of being Full Rooted " S-Off " on any Android device. Even if your running the Stock Rooted Rom. Which BTW since you said you liked it, did you see THIS thread. It's the latest OTA Stock Rooted.

prboy1969 said:
Good to hear . I'm a big advocate of being Full Rooted " S-Off " on any Android device. Even if your running the Stock Rooted Rom. Which BTW since you said you liked it, did you see THIS thread. It's the latest OTA Stock Rooted.
Click to expand...
Click to collapse
Thanks - I wanted to get away from GB for the time being and try the new ICS/JB stuff but I'll keep this one just in case

Xoom bricked

Hi there everyone,
I have a huge problem. Last night i bricked my xoom. I was following a tutorial on this forum. and after unlocking the bootloader it told to flash a file called boot.img after doing so and typing fastboot reboot, the device wouldnt start behind the motorola logo. i tried allot of thing and also did flash some other stock android 4.0.4 boot.img files now with the last one mentioned i managed to get the xoom (wifi) to boot a little further. because the ripple movie with the motorola logo is shown. but it stucks at that movie.
Does anyone know if i can flash an image on the xoom that will atleast fix the problem of not rebooting so i can try another tutorial.
I have searched the internet for solutions, many of them linked to threads on this forum. but almost all download links in these tutorials are old and broken.
Can someone please help me unbrick my device? And maybe a link to a good working unroot tutorial for my xoom wifi with android 4.0.4.

Try get back to Stock.
Download from HERE
and do some OTA updates afterwards so everything will be up to date.
Then wipe and try again from scratch..
Worked for me perfectly just a few days ago.

If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.

Cubanluke88 said:
If you can still get into fastboot, then its not bricked.
Get some stock images and flash them via fastboot and you'll be fine.
Click to expand...
Click to collapse
Indeed it worked. i downloaded the official images and flashed them im on android 3.0.1 again and all seems to work just fine now.
Next problem is i cant find a descent tutorial on this forum how to root the xoom. all download links are either removed due to copyright issues or the links are just broken.
How does it work actually?
1. I unlocked the boot loader wich is very easy.
but then? Do i need to flash a rooted image over the existing? i dont really understand how this works. I rooted my Desire HD with a good tutorial in minutes. Not many people seems to really know how to root the Xoom.
Also i would like to know if the different tutorials are for different android versions or can i aply all tutorials of rooting when i stay on android 3.0.1?
I also tried to flash a recovery.img to the recovery partition and press volume down 3 seconds after the moto logo apears but when i do i get an android robot with a big " ! " on his belly and it takes 5 minutes to load the menu. when im in it tells me there is no sdcard present when i try to flash a rooted rom (zip file).
Is there someone reading this thats willin to explain to me how to do a root the easiest way? Please if links are posted be sure everything on that thread is working. Im pretty sure i will pull it off with some push in the right direction.
Thank you!
(edit) omg im stupid, offcourse the sdcard wont work... it never worked at 3.0.1. on the xoom. can i follow this tutorial:
http://rootzwiki.com/topic/451-how-to-root-the-wifi-only-xoom-301/
Could someone read over it and see if this is a good tutorial? last time i flashed a boot.img the whole xoom got stuck... is that because i had the wrong boot.img on the wrong android version? or should boot.img always work?

Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.

Cubanluke88 said:
Do you plan on flashing to a custom rom after rooting? If so, you can just skip rooting altogether.
I say this because I'm not particularly familiar with that rooting method you linked (though reading through it, it makes sense, all its doing is pushing the necessary files for root access to the xoom via adb). I used a rooting script flashed through a custom recovery over a year ago - unfortunately the download link seems to be broken (I might have a copy at home).
So there's a few things you can do:
1. If you just want a custom rom - download the rom zip file and store on your device. Flash TWRP (my preferred recovery) in fastboot. Boot into TWRP and flash the rom zip file.
2. If you want stock OS root access -
a) Follow those steps you linked and see what happens. If things go wrong, you should be able to just flash those stock images again.
b) Wait for me to get home and see if I have the root script. You'll need to flash a custom recovery though in order to use it.
Click to expand...
Click to collapse
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?

eos 4.1.1 is simply awesome and its also pre rooted' so your bootloader is unlocked, all you gotta do now is install twrp recovery via fastboot ( my preffered recovery) then flash eos via recovery
Sent from my Xoom using XDA Premium App

sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
EOS is a pretty AOSP rom. No theme, though you can apply one if you like and change a few colors. There are various toggle additions you can add that make the user experience much better. It also comes with an overclockable kernel and is very very stable (despite being a nightly) The team has been supporting the Xoom for over a year and is very committed to the Xoom.
---------- Post added at 01:15 PM ---------- Previous post was at 01:11 PM ----------
sygys said:
Ok thanks for your answer. Ill try to unroot with that method flashing directly to the recovery.img i also know now what i did wrong. i flashed the recovery.img not to the recovery partition but to the boot partition LOL. thats why the xoom didnt boot anymore
I see allot about Nightlies Eos, 4.1.1. is that a good rom? Does it look like the stock version?
Click to expand...
Click to collapse
As for flashing, just gotta make sure your text is good before hitting the enter key. Recovery flash should look something like this:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Some instructions for flashing can be found here
While that page is specifically for locking and flashing to return to stock, the commands are universal for fastboot. Hell, if you wanted to, you could manually restore a nandroid backup via fastboot and flashing images.

Can someone help me understand what it means to flash an RUU?

I am currently running Jelly Bean AOKP, but it's a bit crashy. I have a couple favorite apps that I wish would work again. Am I correct in understanding that the RUU is the factory ROM?

Yup, factory Rom. It's actually a program that runs on your pc that flashes the factory Rom. Make sure you dont use a newer one since it also flashes hboot.
Sent from my HTC One XL using xda app-developers app

How far back would one need to go to avoid flashing hboot?

hcricket said:
How far back would one need to go to avoid flashing hboot?
Click to expand...
Click to collapse
2.20 contains the new hboot. If you run it, you can no longer flash radios to your phone and you have to flash boot.img manually (which means no flashing phone back ups on the go to switch ROMs). Just go with the 1.85 RUU. Doesn't matter if you are going to root/rom anyway. Side Note, if your phone already has the 2.20 hboot, do not run the 1.85 RUU!
Btw, why are you running an RUU anyway if I may ask?

If away from a pc, I'm guessing you could actually use terminal emulator and dd the boot.IMG corresponding to the Rom or backup you want to flash, reboot recovery, flash Rom/backup then reboot...I'm unrooted so I can't confirm, but would be a fun test confirm if it works or not

18th.abn said:
If away from a pc, I'm guessing you could actually use terminal emulator and dd the boot.IMG corresponding to the Rom or backup you want to flash, reboot recovery, flash Rom/backup then reboot...I'm unrooted so I can't confirm, but would be a fun test confirm if it works or not
Click to expand...
Click to collapse
Don't you have to use clockwork to flash image from terminal emulator?
Edit: I guess that's only if I want the easy way with "flash_image"

RUU will not run when bootloader is unlocked. So remember to relock the bootloader before running the RUU.
Also RUU = ROM update utility

Butters619 said:
Don't you have to use clockwork to flash image from terminal emulator?
Edit: I guess that's only if I want the easy way with "flash_image"
Click to expand...
Click to collapse
Terminal emulator is ran from android as an app. It's a linux terminal to use a shell command to dd the .img to the proper partition.......I would actually love to see somebody test to ser if it sticks or not. If it did we could write a simple script that people could use so they could easily flash on the go without needing a pc to fastboot flash the image

You could always just flash a stock rom, like this one: http://forum.xda-developers.com/showthread.php?t=1872842. It is way easier than ruu-ing and you don't risk losing root

Thank you everyone for the replies. I ended up flashing CleanRom 4.5 and all is well. The RUU stuff looks like perhaps a bit more than I'm prepared for.

18th.abn said:
Terminal emulator is ran from android as an app. It's a linux terminal to use a shell command to dd the .img to the proper partition.......I would actually love to see somebody test to ser if it sticks or not. If it did we could write a simple script that people could use so they could easily flash on the go without needing a pc to fastboot flash the image
Click to expand...
Click to collapse
Do you happen to know what partition the boot.img is in?
I know it. Going to try this now. Wish me luck!!

Awesome...make sure you do rom change from aosp based to sense or vice versa. That way you know the boot.imgs are not compatible and you don't get a false result that the boot.img sticks thanks for testing it out
Sent from my SCH-R720 using xda premium

18th.abn said:
Awesome...make sure you do rom change from aosp based to sense or vice versa. That way you know the boot.imgs are not compatible and you don't get a false result that the boot.img sticks thanks for testing it out
Sent from my SCH-R720 using xda premium
Click to expand...
Click to collapse
Awwwww yeah. It worked. Going to try one more time to make sure

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