Database Users

Droid Incredible CM6?

Ive been trying for about a week to get CM6 on my incredible. And i see some of the people on this forum have it. Ive contacted developers and users alike but for some reason I'm having trouble. After Root, I downloaded and installed Rom Manager but I'm unsure what to do next. I tried to flash Clockworkmod with the app, but when I boot up into recovery, I dont see The Clockwork menu, or the Nandroid backup option. I dont want to Flash the rom without being able to make a backup or install custom Update.zip files. Does anyone have any suggestions???PLEASE PM me for any suggestions!!!!!!!!!!!

If you aren't seeing the clockwork recovery, then you didn't run the reflash tool after you rooted. Run the reflash tool and it will load the custom recovery correctly.

what reflash tool?

unrEVOked 3, should be a link to it in this forum

I tried to run that but it keeps getting stuck. I might have to manually move files.
Sent from my ADR6300 using XDA App

Chances are if the unrEVOked tool isn't working, you may not have the right drivers installed. Check their wiki to make sure you do. Also, to get the nightly CM6 builds (when they resume, which will likely be shortly) you do have to buy the ROM manager premium license from the Market (which I recommend you do anyways as it goes to Koush who is the one responsible for developing CM6 for the DInc).
Here's the link to the wiki concerning the driver:
http://www.unrevoked.com/rootwiki/doku.php?id=public:windows_hboot_driver_install

Wow is this all I really nerd to do ? I already bought Rom manager, but clockwork isn't working. I guys updating the drivers will let me get clock work ? Do u run a custom Rom? Thanks!!!

Help with installing rom

I am a newbie needing some help. I rooted my vibrant months ago to have the ability for wifi tethering. It went flawlessly. I initially wanted to wait for the official update. Since it doesn't seem to be coming any time soon I decided I prefer to install a rom myself. I decided to install cyanogen because I've heard good things. I went to the instructions and was instantly bombarded with technical lingo o did not understand, starting with nandroid backup. Well I have rom manager, I did a full backup of my current rom but I couldn't find it on my sd card. I tried to download black hole from rom manager and it just took me to recovery with no options except the normal ones, at this point I felt over whelmed and gave up. I am wondering if anyone can simplify this for me and recommend the best rom? Thanks!
Sent from my SGH-T959 using XDA App

Unroot and wait for the OTA. 2.2 OTA is out now. Seriously.
Sent from my SGH-T959 using XDA App

I would either do like the previous post advised and get the official update that is out. From everything I am hearing it is self updated (you have to do it) through Samsung mini kies. Tmonews.com covered the issue, and what you had to do. If you dont want to do that, and want to keep it rooted and put a rom on it, PM me and I will give you further directions and my personal opinion about what rom would be good.
Good luck.

I had a similar issue at first with the recovery. Open rom manager and flash clockworkmod recovery. After that's complete reboot phone into recovery. It might load the regular recovery, if so, use your volume keys until you get to install packages and then click the power button. After that it should run the clockworkmod recovery.
Sent from my SGH-T959 using XDA App

No need to unroot, you NEVER need to unroot, at least with this phone, dunno about others.
Do what xdefied said about recovery.
cynogen is if you want a stock google experience. The official 2.2 update is out, download mini kies or full and update. Go with custom roms if you want a slightly modified samsung experience. Once you get clockwork recovery working it'll be a snap, choose file in rom manager and you're done.
P.s. Wrong section
Sent from my SXY-T959

Thanks for the replies. I know I have a lot to learn but I have to start from somewhere, and I just appreciate the people willing to give a total newbie advice and it's good to know I'm not the only one to have problems initially downloading from rom manager.

[Q] Non rooted Gingerbread Stock - Custom Revery Which one ??

Hi,
My warranty has just run out on my Nexus One so I've decided to unlock the bootloader.
My Aim is to get from stock non rooted Gingerbread to rooted Gingerbread with busybox, SU, and ultimately being able to boot into ubunto in chroot, I've been reading up on all this for a few days now but just need a small amount of help with Recovery, Gingerbread ROM choice, and the order that thing should be done, by someone who's done this before.
I take it the first thing is to install SDK and get The USB Driver working on PC, its running XP by the way.
Then I unlock the bootloader, !HELP! to do this do I enter hboot or fastboot, before connecting the phone to the PC? I have to copy 3 files somewhere and use ADB and run command for **** OEM unlock, can't remember the exact command, (I've got instructions for this) and then agree to void my warranty etc.
I then find and download the correct custom recovery image and copy this into the tools folder of the SDK. And install (got instructions for this to).
!HELP!
Which custom recovery image should I use? and which Rooted Gingerbread ROM is most popular ?
After installing the custom Recovery can I just flash a custom ROM? I've seen something about SU.zip mentioned, is this necessary?
If I can just flash a custom ROM, I do this by downloading and copying the custom ROM of choice to the root of my SD card. Start phone in recovery mode and install from SD? I then install the google add ons .zip (if required) using the same method.
Sorry for such a long post and so many questions but I can find all the information for what I'd like to achieve but not in one place and nowhere in any chronological order.
Any advice appreciated .

Please read the Wiki, "Root" guides, "Unlock bootloader and install custom ROM" thread. Execute until the point of installing custom ROM.
Look in "Recovery" section for recoveries, install the latest Amon_RA.

Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/

GB ROM
Im running CM7RC4 and am happy w/ it

MouseIdt said:
Ive Successfully Rooted Gingerbread by following this method http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
Click to expand...
Click to collapse
Thanks everyone, but this looks like the one for me, going to unlock bootloader now install custom recovery and flash su.zip.
I'll post back with how I went on. Wish me look
A apprehensive newbie ;-)

Flash this as well, otherwise you will lose your custom recovery...
http://db.tt/cp7De8G
Sent from my Nexus One using XDA Premium App

Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.

Nooooo
Rusty! said:
Good show with unlocking the bootloader, it's the best way.
However... looking at your flag, you're in the UK... this means your phone is still in warranty, as we get 24 months.
Click to expand...
Click to collapse
My understanding was 12 months but, your probably right. I've unlocked the bootloader now and fortunately my N1 is in good condition, funtioning correctly ( well at least for now, I'll have to cross that bridge if and when I get to it )
Getting on to custom recovery, I realised something wasn't quite right after my first attempt. I installed custom recovery but without su.zip on my SD card. I managed after rebooting my PC to complete the custom recovery with su.zip on the SD card and was successful in that I've got SU on my N1. However I am quite sure I do need to fix something with the recovery, can someone explain what method or how I do this now. I've unlocked the bootloader, I am rooted with gingerbread but with a dodgy recovery.
Or do I do exactly the same as I did with su.zip and push recovery from ADB and flash from SD card, making sure that fix-recovery.zip is indeed on the SD card.
Hope this makes sence?
Any help appreciated.

After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App

sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I've got ROM Manager installed and if I want to try anything it tells me I have to flash clockwork mod recovery, I was unsure if It was safe to do this after using a completely different recovery image to get where I am now.
Sorry for being such a paranoid newbie, but we all got to start somewhere ;-)

sparkyryan said:
After I unlocked my n1 I used rom manager for everything else, first flashing clockwork mod, then selecting a stable cm 7 build and flashing that, since then I've done everything through recovery, flashing custom kernels and nightlie builds, I'm currently using cm7 rc4 highly recommend rover theme too!
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I think CM7 rc4 is next, I do want to get Linux up and running though, even if it's in a virtual environment (chroot). and deffinately would like to check some nice themes out, I've not even looked at themes yet, I suppose it's quite easy after unlocking bootloader, installing custom recovery then flashing su.zip though. But still any pointers where to start my quest wouldn't go a miss ;-)

Recovery
its safe to let rom manager flash clockwork,ive done it

I heared about amonRA but it seemed like clockworkmod was more commonly used so I went for that, but yeah it's fine to flash a new recovery, just remember that whilst it's rare things can go wrong, it's YOUR fault not anyone's here regardless of the advice you may get here if your phone gets bricked or screwed up.
That said I'm still new to this but I'm learning as I'm going, just remember to backup your phone using rom manager before doing anything major so that you can always recover your phone/rom.
I started out hacking my nokia 5800 so was keen to have a go with the android platform.
Sent from my Nexus One using XDA Premium App

CM7 stable
Have you upgraded to cm 7 stable? its a definate upgrade

Running Rooted 3.2.1 to ICS? Do I unroot?

I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks

tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Same question here
Sent from my A500 using XDA

3d0rr said:
Same question here
Sent from my A500 using XDA
Click to expand...
Click to collapse
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.

Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?

tu3218 said:
Apparently the root doesn't matter. It will just be removed when we install the ota ICS. What worries me is recovery. Because it has to boot into a recovery to install ICS. I had CWM installed then flashed to stock by acer recovery tool in the play store. But when I manually boot into recovery, I get a exclamation point inside a triangle. What recovery are you guys running?
Click to expand...
Click to collapse
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA

3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
Yeah I think so as well. I flashed stock via the Acer recovery tool but I get nothing when I boot into recovery except what I stated above. I'm not sure if that's right or not.
Sent from my Galaxy Nexus using XDA

I was happily running timmydean's rooted 3.2.1 based on the leaked OTA. The ICS upgrade came through and installed just fine. No loss of data and the programs I tried all worked. I was on stock 4.0.4 unrooted.
However, I'm now borked. I rebooted into recovery (Power, Vol -) to see about rooting via the backdoor I'd installed. I had thor's 1.7 Touch CWM recovery installed. I got some weird message that recovery was broken. (Don't recall the exact msg.)
After that, it hung on the "android" screen. Soft-bricked.
So I did a factory reset (Power, vol+, rock screen switch) and ended up back on 3.2.1. Now, the Settings > About > Check update results in the "Network coverage is currently poor. Please move to a location with better coverage to continue." message.
My WiFi is fine, speedtest.net reports a 20 Mbps download. All other apps function well. I'm pulling a DCHP address from my router.
I'm fairly sure this is a badly-worded error message from Acer and actually refers to server overload or some other issue on their end.
Also, installing the latest Acer Iconia Update preps the system for ICS. At one point, installing it allowed the update to proceed, but not to ICS. Uninstalling/reinstalling that update seemed to jog the system at one time.
So I tried wiping data/cache/dalvik and went back to stock 3.2. Same error message when updating. Wiped again and went back to stock 3.0.1. Same error message.
So I'm stuck and am going to give it a few days to see if Acer can sort out their upgrade path. If not, I will probably load CM9 or Thor's ICS ROM. (I do have a Nandroid, so I can get back to where I was pre-ICS.)
All in all, I'm very disappointed in Acer for borking my tablet.
________
Update: So now a day later, the "poor coverage" message was replaced by an "update available". Installed A500_7.014.03_com_gen1, after reboot, another update A500_7.014.15_com_gen1 installed. I am now on stock 3.2.1.
System update shows "Your device is up to date".
Will see what tomorrow brings, but this is certainly frustrating.

thorne75 said:
I am in the same camp.
I'm running a rooted 3.2 stock by Timmy Dean.
I'm happy I didn't jump the gun when I Saw the update last night, because it seems I would have truly been screwed.
What I would like to know is if a rooted 3.2 can simply be unrooted. Seems this would the simplest thing to do.
Thanks in advance for any and all help.
Click to expand...
Click to collapse
********************************************
Could you guys running the backdoor and still rooted please try this:
1) Try and capture the build no. of the update
2) See if the update will download BUT do not install yet
3) Go to /cache/fota/ and find the zip -
4) copy it to yr external sd
5) post back the build no.
thanks!!!
Procedure for manual install:
1/ rename the file as : update.zip
2/ place the file on the micro sd card
3/ turn off the tablet
4/ press the down volume key and the power button at the same time untill the tablets turns on
5/ the iconia will start the upgrade process by itself.
OR just redownload the update and it install
*********************************************
I had trouble when i reverted to stock in the weekend
and it was a bit of a process to get the OTA's to 3.2.1.
I did manage to hold "full root" but had to revert a couple of times
by putting stock recovery back and using backdoor .
I accidentally factory reset and everything went a bit pear shaped from there...oops!!
Im still waiting for the OTA ICS - getting network coverage error -one good thing
is my partners tab is only 5 days old and still pure factory,
her tab shows same error so at least we know its not root/backdoor problem
So yeah if u gonna take the OTA best to get rid of the backdoor unless you wanna play guinea pig for us all>>>>
dunno why we aint found one of those yet
I dont think you can cause too much of a problem where a "hard reset" pwr/vol -/rotation lock/ combo wont fix...you can then root from there.
---------- Post added at 12:45 PM ---------- Previous post was at 12:36 PM ----------
3d0rr said:
I have CWM recovery by thor2002. I think we can't update via ITS unless we flash original recovery
Sent from my A500 using XDA
Click to expand...
Click to collapse
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:

dibb_nz said:
********************************************
hi 3d0rr!!
i think those of us with the backdoor should be meticulous if/when taking the OTA.
we shouldnt need to unroot and use stock recovery as the ota should get rid of that in the flash. But to ensure a stress free OTA it may pay to do it anyway.
i know you previously told me u were stock gen 1 - but is that from factory, just finished reading a very interesting post regarding the different 'gens' so i for one am sticking with factory build gen :just for the official OTA anyway:
Click to expand...
Click to collapse
Dibb_nz, I was stock gen 2. I don't wanna take OTA until be sure it's safe. Unless now I know that a hard factory reset may save my tab if something happen.
Can you tell us where did you read that post about 'gens'? I still a little confuse about that
Sent from my A500 using XDA

BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA

3d0rr said:
BTW, the network coverage errors seems to be an Acer's error. First I received OTA and a day after that I see that error on my tab. And a couple of hours later I have OTA again. So, don't worry, you should get OTA asap
Sent from my A500 using XDA
Click to expand...
Click to collapse
oh sounds promising, although I just read another post from someone across the ditch in OZ he reckoned acer said they were working on a patch for the problems theyre havin with the first update...who knows
now m8, sorry to confuse you, that wasnt my intention, but i try to make sure that i;m not suggesting things which may end with you or others borkin or brickin yr tab. Ive spent the last few days reading thousands of posts (just like everyone else) thankfully we are fortunate in being able to learn from the mistakes of others I know a bit more about ics than i did 3 days ago let me tell you, lol.
i just finished helpin out a fellow "timmy-ite" stuck with no way of getting in to apx mode to get un-borked...well didnt really help just a sounding board more than anything
he got himself up and running, used the apx tool in my sig, unlocked the bootloader, rooted, flashed custom recovery did a nand and is now running flexreaper - with the tools and knowledge he gained he now has the choice to go back to HC to get the OTA or not....he's one happy camper!!!
Have a read have a read thru the threadhere. ask him a question or two if you want - but dont get too hung up "maybe doing something wrong" you won't be the only person ever to experience that uhh-ohh sinking feeling when you know you shouldnt have just done whatever it was that u just did
Theres always someone round here who will help - usually cos they done the same silly lthings themselves - why ya think i'm always posting

what is the backdoor program you guys talk about?

tu3218 said:
what is the backdoor program you guys talk about?
Click to expand...
Click to collapse
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.

jpinsl said:
timmydean's root method also allows you to install a backdoor to re-root after accepting an OTA. You have to manually install it during the rooting process, so you would know if you had it.
Click to expand...
Click to collapse
timmyDean How to root stock 3.2.1
Summary:
Version V4 is the same as V3 with the only difference being that there is a NEW backdoor script which has some additional features to protect root(#) from getting broken when you do an OTA. I also applied these to this flash image so you wouldn't have to add the additional protection yourself. V4 also has the drivers for XP included. However, when taking an OTA you should also install the backdoor for additional protection. However, you cannot leave the backdoor installed as it turns off sound. So having a little more protection just might save your root in case you take an OTA and forget to install the backdoor.
Click to expand...
Click to collapse
beat me to it
its a completely stock gen2 rooted and cwm - you can use to unbrick, or go back to stock. only for HC bootloaders though.....

This worked to me
tu3218 said:
I'm running completely stock, no rom anything. Just flashed updates from users here to update me to the latest HC. I received the ICS update but pretty sure it won't work since I'm rooted and running CWM recovery. What do I need to do to install ICS? thanks
Click to expand...
Click to collapse
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method.
1) Go to play market and install Acer Recovery Installer.
2) Open Acer Recovery and verify with recovery do you have. In my case it was CWM recovery by thor2002ro 1.5
3) Install stock recovery. Make a backup of your old recovery when ask.
4) Factory reset: in my case, I made a backup of all my data and used Titanium to backup some apps. Then I harded reset my tab by turning it off and the combo pwd + vol(+) then lock-unlock switch 3 times until I saw "eraing user data" in the top-left corner.
5) turn on the tab and go to google play. Search for acer and install Update enhancement.
6) Go to settings-> about-> system update and aply the OTA update.
You will lost root, but everything should work fine.
To gain root access again, you can follow this thread -> http://forum.xda-developers.com/showthread.php?t=1546593
Now I have rooted stock ICS and I'm so happy

Hey great write up, will try this as soon as I'm off work. Anyway to confirm stock recovery is installed? Because I have done what you said(just the flash stock recovery part) an when I boot into recovery I just get a triangle an exclamation point. Not sure if thats right or not. But I will definitely give this a go since you were running exactly what I'm running now.
Sent from my Galaxy Nexus using XDA

3d0rr said:
Well my friend, this worked to me... I hope this can help somebody else:
Original ROM: Acer A500 3.2.1 COM_GEN2 Rooted and with CWM using Timmy's method...
...To gain root access again, you can follow this thread - ...xda-developers.com/showthread...
Now I have rooted stock ICS and I'm so happy
Click to expand...
Click to collapse
yay for 3d0rr you finally took the plunge congrats!!!!!
@tu3218
That download link is no longer available
instead download blackthund3r's one-click-root,
google "ICS Root for Windows"
At step 3 - After you have backed up -
Copy the uid.txt file from the backup folder - this holds your cpu id -
you're probably gonna need it at sum stage

I followed your instructions and it went perfect!!! Rocking ics now. Thanks for the help. First thing I notice, soooo much faster an full of butter.
Sent from my Galaxy Nexus using XDA

[Guide] How to root Stock ICS rom without binary count

I'm no longer providing support for this thread due to time constrains with school, thank you for your support and it been nice sharing this method with you all. I may be gone but this method has still been reported as working, but it is possible that the next updates pushed to your phone might break the rooting and this method might not work anymore. But there is no harm in trying, at most you get an error in recovery saying file is invalid.
This method works on the released ICS rom from Germany and I would expect it to work for the rest of the ICS roms due for release..
This method does not increase the binary counter or causes a yellow exclamation mark
Update :
Due to rising numbers of phone being bricked based on rumors and stuff, I strongly suggest NOT trying to use any nandroid backup or restore on this CWM and it is best we keep CWM out of our devices to do major I/O stuff. So far I have never seen anyone bricked their devices on this small rooting/unrooting process but JUST DO NOT MAKE BACKUPS OR RESTORES!
Rooting
Download the Files first and put in your EXTERNAL SD
Reboot to stock recovery. - Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage. - Touch the screen as if you are using the phone to choose the options.
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Unroot
Download this File first and put in your EXTERNAL SD
Reboot to recovery.- Shutdown your device completely, press and hold Vol Up + Power button + Home, releasing the power buttons once you see the Samsung GALAXY Note N7000 screen but continue to hold the Vol Up and Power buttons still until you enter recovery
Choose apply update from external storage.- Touch the screen as if you are using the phone to choose the options
Choose CWM.zip and wait until CWM recovery appear.
( From this point on, the volume rockers and power buttons do not work! It is now a Touch interface like how you use the phone normally )
Choose install zip from External SD
Choose and Install SU-Uninstaller-Signed.zip
Reboot
You are done and now your device is Unrooted
Partial Root
Alright i managed to obtain partial root myself and a fix for the Partial root is quite simple. You can install SuperSU by Chainfire and update the root. would fix the Partial root. Once you install this.. DO NOT USE the Superuser app and DO NOT uninstall the SuperUser app. Use SuperSU from now.
SuperSU - https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
MOD Edit: cwm.zip removed from the attachments, read Entropy512's post.

Thanks, but does this install CWM as well? id like to know so that I can go straight to flashing roms from it

are you sure this works ? can anyone confirm ?

nightfox11 said:
are you sure this works ? can anyone confirm ?
Click to expand...
Click to collapse
Works perfectly. Just rooted stock ICS.

Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium

kvanlier said:
Works perfectly. Just rooted stock ICS.
Click to expand...
Click to collapse
thanks man!

Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.

Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.

akenis said:
Got a brand new Note in the box here.....
Trying to get things straight. Seems like I have two options now for rooted official ICS.
1. This method. Update official ICS Via PC odin (no binary counter, ect) and then follow above instructions.
2. Root stock gb via old method (not sure what that is yet) and then use the mobile odin proceedures w/ new ICS CF kernel?
Is the end result gonna be the same?
Bonus question for noob: what is binary counter and red triangle/exclamation point?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yes you will end up with the same result if you take either one of the 2 ways to root
Binary counter is a Samsung measurement of how many times you flashed custom firmwares using PC Odin, and the yellow (not red ) triangle is just a logo to further show that you indeed flashed custom firmware
However, the binary counter will not increase (and therefore no yellow triangle will appear) if you:
1. Flash stock firmware with PC Odin
2. Flash using Mobile Odin app by ChainfireXDA
3. Flash using CWM recovery

I got binary counted to 1 with yellow triangle after flashing ics stock from alba.can i use this method to erase counter and triangle?
Sent from my GT-N7000 using Tapatalk 2

So this gives cwm too looks easy
Sent from my GT-N7000 using Tapatalk 2

Drat?
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?

victorator said:
Did you just copy this thread?
Oh well. No harm done I guess. Of course it works. It's a method for all android phones. Temporary cwm so you can copy busybox to /system.
Click to expand...
Click to collapse
LordManhattan said:
Yeah it looks like it, but since it actually works i can't see why that would be a bad thing. But i would give the original author credits in the first post; that is if you copied it.
Click to expand...
Click to collapse
Not many ways to have a drastic difference from the method but hey it works well.
p51d007 said:
I didn't have GB root because my previous version had root, but I $%*^ screwed
up and let KIES update it to 2.3.6 and I've got too much work to screw around with back flashing wiping etc.
I went ahead and let kies update to ics, now, my question, will this method work, or will I still have to go though all the other to get it to work.
I see it works on stock ICS, but is that after kies, or after you update via pc odin?
Click to expand...
Click to collapse
This method works as long as you are on Stock ICS.. Can't really go wrong really.

so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!

how come i only got partial root? i cannot paste into system

deathst said:
This method works as long as you are on Stock ICS.. Can't really go wrong really.
Click to expand...
Click to collapse
You are right, finally got my root back ICS, after the 2.3.6 update, been a while, now I have to remember how to use the freeze program, LBE security etc...all over again LOL. THANKS!

elijahtan said:
how come i only got partial root? i cannot paste into system
Click to expand...
Click to collapse
Try rooting again.. Are you sure your file manager app was given permission? Cause this thing is practically fool proof.
nandihno said:
so i did and have root and root works..
now my question is....
given that we get temp CWM..can i use the temp CWM to flash radios?
AND so if i want to flash LP6 radio via CWM will the steps be.
load Stock recovery
flash CWM.zip in stock recovery
load CWM
flash lp6 radio
will that work?
=============================
After no one answered i took the plunge...
Yes
so can confirm that the above procedure will work
PS: Am amazed how this is not in the sticky
Can anyone tell me any issues with using the CWM offered in this thread??? as in any issues with flashing other roms?? etc??
I fail to see?
The only issue is that CWM is not permanent but u can easily re-enable it by flashing it again...
again..dont understand why ppl are not paying attention to this thread as is great!
Click to expand...
Click to collapse
Glad it works for you Yes I wonder why is not many people taking notice.. :S

...and i thought I was screwed
THANKS MAN. works perfect. much faster than having to redownload the odex vrs

Worked perfectly thanks !
Sent from my HTC One X using xda premium

hmmm.... didn't work for me. CWM looks for update.zip so i renamed it as such. installed and rebooted to CWMR, no touch menu. same old blue colored menu. install su-binary, stuck at unmounting /system = not rooted.